1 Changes in version 0.4.5.12 - 2022-02-04
2 This version contains mostly minor bugfixes for which you can find the
3 details below. The previous release (0.4.5.11) was suppose to update the
4 GeoIP and fallbackdir lists but a problem in our release pipeline prevented
5 those files to be updated correctly. Thus, this release regenerates up to
6 date lists. Furthermore, another fix to highlight is that relays don't
7 advertise onion service v2 support at the protocol version level.
9 o Minor feature (reproducible build):
10 - The repository can now build reproducible tarballs which adds the
11 build command "make dist-reprod" for that purpose. Closes
14 o Minor features (compilation):
15 - Give an error message if trying to build with a version of
16 LibreSSL known not to work with Tor. (There's an incompatibility
17 with LibreSSL versions 3.2.1 through 3.4.0 inclusive because of
18 their incompatibility with OpenSSL 1.1.1's TLSv1.3 APIs.) Closes
21 o Minor features (fallbackdir):
22 - Regenerate fallback directories generated on February 04, 2022.
24 o Minor features (geoip data):
25 - Update the geoip files to match the IPFire Location Database, as
26 retrieved on 2022/02/04.
28 o Minor bugfix (logging):
29 - Update a log notice dead URL to a working one. Fixes bug 40544;
30 bugfix on 0.3.5.1-alpha.
32 o Minor bugfix (relay):
33 - Remove the HSDir and HSIntro onion service v2 protocol versions so
34 relay stop advertising that they support them. Fixes bug 40509;
37 o Minor bugfixes (compilation):
38 - Fix a compilation error when trying to build Tor with a compiler
39 that does not support expanding statitically initialized const
40 values in macro's. Fixes bug 40410; bugfix on 0.4.5.1-alpha
41 - Fix our configuration logic to detect whether we had OpenSSL 3:
42 previously, our logic was reversed. This has no other effect than
43 to change whether we suppress deprecated API warnings. Fixes bug
44 40429; bugfix on 0.3.5.13.
46 o Minor bugfixes (MetricsPort, Prometheus):
47 - Add double quotes to the label values of the onion service
48 metrics. Fixes bug 40552; bugfix on 0.4.5.1-alpha.
50 o Minor bugfixes (relay):
51 - Reject IPv6-only DirPorts. Our reachability self-test forces
52 DirPorts to be IPv4, but our configuration parser allowed them to
53 be IPv6-only, which led to an assertion failure. Fixes bug 40494;
54 bugfix on 0.4.5.1-alpha.
57 Changes in version 0.4.5.11 - 2021-10-26
58 The major change in this version is that v2 onion services are now
59 disabled at the client, service, and relay: any Tor nodes running this
60 version and onward will stop supporting v2 onion services. This is the
61 last step in the long deprecation process of v2 onion services.
62 Everyone running an earlier version, whether as a client, a relay, or
63 an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11,
66 o Major feature (onion service v2):
67 - See https://blog.torproject.org/v2-deprecation-timeline for
68 details on how to transition from v2 to v3.
69 - The control port commands HSFETCH and HSPOST no longer allow
70 version 2, and it is no longer possible to create a v2 service
72 - Tor no longer allows creating v2 services, or connecting as a
73 client to a v2 service. Relays will decline to be a v2 HSDir or
74 introduction point. This effectively disables onion service
75 version 2 Tor-wide. Closes ticket 40476.
77 o Minor features (bridge, backport from 0.4.6.8):
78 - We now announce the URL to Tor's new bridge status at
79 https://bridges.torproject.org/ when Tor is configured to run as a
80 bridge relay. Closes ticket 30477.
82 o Minor features (fallbackdir):
83 - Regenerate fallback directories for October 2021. Closes
86 o Minor features (logging, diagnostic, backport from 0.4.6.5):
87 - Log decompression failures at a higher severity level, since they
88 can help provide missing context for other warning messages. We
89 rate-limit these messages, to avoid flooding the logs if they
90 begin to occur frequently. Closes ticket 40175.
92 o Minor features (testing, backport from 0.4.6.8):
93 - On a testing network, relays can now use the
94 TestingMinTimeToReportBandwidth option to change the smallest
95 amount of time over which they're willing to report their observed
96 maximum bandwidth. Previously, this was fixed at 1 day. For
97 safety, values under 2 hours are only supported on testing
98 networks. Part of a fix for ticket 40337.
99 - Relays on testing networks no longer rate-limit how frequently
100 they are willing to report new bandwidth measurements. Part of a
101 fix for ticket 40337.
102 - Relays on testing networks now report their observed bandwidths
103 immediately from startup. Previously, they waited until they had
104 been running for a full day. Closes ticket 40337.
106 o Minor bugfix (CI, onion service):
107 - Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500;
108 bugfix on 0.3.2.1-alpha.
110 o Minor bugfix (onion service, backport from 0.4.6.8):
111 - Do not flag an HSDir as non-running in case the descriptor upload
112 or fetch fails. An onion service closes pending directory
113 connections before uploading a new descriptor which can thus lead
114 to wrongly flagging many relays and thus affecting circuit building
115 path selection. Fixes bug 40434; bugfix on 0.2.0.13-alpha.
117 o Minor bugfixes (compatibility, backport from 0.4.6.8):
118 - Fix compatibility with the most recent Libevent versions, which no
119 longer have an evdns_set_random_bytes() function. Because this
120 function has been a no-op since Libevent 2.0.4-alpha, it is safe
121 for us to just stop calling it. Fixes bug 40371; bugfix
124 o Minor bugfixes (consensus handling, backport from 0.4.6.4-rc):
125 - Avoid a set of bugs that could be caused by inconsistently
126 preferring an out-of-date consensus stored in a stale directory
127 cache over a more recent one stored on disk as the latest
128 consensus. Fixes bug 40375; bugfix on 0.3.1.1-alpha.
130 o Minor bugfixes (onion service, TROVE-2021-008, backport from 0.4.6.8):
131 - Only log v2 access attempts once total, in order to not pollute
132 the logs with warnings and to avoid recording the times on disk
133 when v2 access was attempted. Note that the onion address was
134 _never_ logged. This counts as a Low-severity security issue.
135 Fixes bug 40474; bugfix on 0.4.5.8.
138 Changes in version 0.4.5.10 - 2021-08-16
139 This version fixes several bugs from earlier versions of Tor,
140 including one that could lead to a denial-of-service attack. Everyone
141 running an earlier version, whether as a client, a relay, or an onion
142 service, should upgrade to Tor 0.3.5.16, 0.4.5.10, or 0.4.6.7.
144 o Major bugfixes (cryptography, security):
145 - Resolve an assertion failure caused by a behavior mismatch between
146 our batch-signature verification code and our single-signature
147 verification code. This assertion failure could be triggered
148 remotely, leading to a denial of service attack. We fix this issue
149 by disabling batch verification. Fixes bug 40078; bugfix on
150 0.2.6.1-alpha. This issue is also tracked as TROVE-2021-007 and
151 CVE-2021-38385. Found by Henry de Valence.
153 o Minor feature (fallbackdir):
154 - Regenerate fallback directories list. Closes ticket 40447.
156 o Minor features (geoip data):
157 - Update the geoip files to match the IPFire Location Database, as
158 retrieved on 2021/08/12.
160 o Minor features (testing):
161 - Enable the deterministic RNG for unit tests that covers the
162 address set bloomfilter-based API's. Fixes bug 40419; bugfix
165 o Minor bugfix (crypto, backport from 0.4.6.7):
166 - Disable the unused batch verification feature of ed25519-donna.
167 Fixes bug 40078; bugfix on 0.2.6.1-alpha. Found by Henry
170 o Minor bugfixes (relay, backport from 0.4.6.7):
171 - Reduce the compression level for data streaming from HIGH to LOW.
172 Fixes bug 40301; bugfix on 0.3.5.1-alpha.
174 o Minor bugfixes (timekeeping, backport from 0.4.6.7):
175 - Calculate the time of day correctly on systems where the time_t
176 type includes leap seconds. (This is not the case on most
177 operating systems, but on those where it occurs, our tor_timegm
178 function did not correctly invert the system's gmtime function,
179 which could result in assertion failures when calculating voting
180 schedules.) Fixes bug 40383; bugfix on 0.2.0.3-alpha.
182 o Minor bugfixes (warnings, portability, backport from 0.4.6.6):
183 - Suppress a strict-prototype warning when building with some
184 versions of NSS. Fixes bug 40409; bugfix on 0.3.5.1-alpha.
187 Changes in version 0.4.5.9 - 2021-06-14
188 Tor 0.4.5.9 fixes several security issues, including a
189 denial-of-service attack against onion service clients, and another
190 denial-of-service attack against relays. Everybody should upgrade to
191 one of 0.3.5.15, 0.4.4.9, 0.4.5.9, or 0.4.6.5.
193 o Major bugfixes (security, backport from 0.4.6.5):
194 - Don't allow relays to spoof RELAY_END or RELAY_RESOLVED cell on
195 half-closed streams. Previously, clients failed to validate which
196 hop sent these cells: this would allow a relay on a circuit to end
197 a stream that wasn't actually built with it. Fixes bug 40389;
198 bugfix on 0.3.5.1-alpha. This issue is also tracked as TROVE-2021-
199 003 and CVE-2021-34548.
201 o Major bugfixes (security, defense-in-depth, backport from 0.4.6.5):
202 - Detect more failure conditions from the OpenSSL RNG code.
203 Previously, we would detect errors from a missing RNG
204 implementation, but not failures from the RNG code itself.
205 Fortunately, it appears those failures do not happen in practice
206 when Tor is using OpenSSL's default RNG implementation. Fixes bug
207 40390; bugfix on 0.2.8.1-alpha. This issue is also tracked as
208 TROVE-2021-004. Reported by Jann Horn at Google's Project Zero.
210 o Major bugfixes (security, denial of service, backport from 0.4.6.5):
211 - Resist a hashtable-based CPU denial-of-service attack against
212 relays. Previously we used a naive unkeyed hash function to look
213 up circuits in a circuitmux object. An attacker could exploit this
214 to construct circuits with chosen circuit IDs, to create
215 collisions and make the hash table inefficient. Now we use a
216 SipHash construction here instead. Fixes bug 40391; bugfix on
217 0.2.4.4-alpha. This issue is also tracked as TROVE-2021-005 and
218 CVE-2021-34549. Reported by Jann Horn from Google's Project Zero.
219 - Fix an out-of-bounds memory access in v3 onion service descriptor
220 parsing. An attacker could exploit this bug by crafting an onion
221 service descriptor that would crash any client that tried to visit
222 it. Fixes bug 40392; bugfix on 0.3.0.1-alpha. This issue is also
223 tracked as TROVE-2021-006 and CVE-2021-34550. Reported by Sergei
224 Glazunov from Google's Project Zero.
226 o Minor features (compatibility, backport from 0.4.6.4-rc):
227 - Remove an assertion function related to TLS renegotiation. It was
228 used nowhere outside the unit tests, and it was breaking
229 compilation with recent alpha releases of OpenSSL 3.0.0. Closes
232 o Minor features (geoip data):
233 - Update the geoip files to match the IPFire Location Database, as
234 retrieved on 2021/06/10.
236 o Minor bugfixes (control, sandbox, backport from 0.4.6.4-rc):
237 - Allow the control command SAVECONF to succeed when the seccomp
238 sandbox is enabled, and make SAVECONF keep only one backup file to
239 simplify implementation. Previously SAVECONF allowed a large
240 number of backup files, which made it incompatible with the
241 sandbox. Fixes bug 40317; bugfix on 0.2.5.4-alpha. Patch by
244 o Minor bugfixes (metrics port, backport from 0.4.6.4-rc):
245 - Fix a bug that made tor try to re-bind() on an already open
246 MetricsPort every 60 seconds. Fixes bug 40370; bugfix
250 Changes in version 0.4.5.8 - 2021-05-10
251 Tor 0.4.5.8 fixes several bugs in earlier version, backporting fixes
252 from the 0.4.6.x series.
254 o Minor features (compatibility, Linux seccomp sandbox, backport from 0.4.6.3-rc):
255 - Add a workaround to enable the Linux sandbox to work correctly
256 with Glibc 2.33. This version of Glibc has started using the
257 fstatat() system call, which previously our sandbox did not allow.
258 Closes ticket 40382; see the ticket for a discussion of trade-offs.
260 o Minor features (compilation, backport from 0.4.6.3-rc):
261 - Make the autoconf script build correctly with autoconf versions
262 2.70 and later. Closes part of ticket 40335.
264 o Minor features (fallback directory list, backport from 0.4.6.2-alpha):
265 - Regenerate the list of fallback directories to contain a new set
266 of 200 relays. Closes ticket 40265.
268 o Minor features (geoip data):
269 - Update the geoip files to match the IPFire Location Database, as
270 retrieved on 2021/05/07.
272 o Minor features (onion services):
273 - Add warning message when connecting to now deprecated v2 onion
274 services. As announced, Tor 0.4.5.x is the last series that will
275 support v2 onions. Closes ticket 40373.
277 o Minor bugfixes (bridge, pluggable transport, backport from 0.4.6.2-alpha):
278 - Fix a regression that made it impossible start Tor using a bridge
279 line with a transport name and no fingerprint. Fixes bug 40360;
280 bugfix on 0.4.5.4-rc.
282 o Minor bugfixes (build, cross-compilation, backport from 0.4.6.3-rc):
283 - Allow a custom "ar" for cross-compilation. Our previous build
284 script had used the $AR environment variable in most places, but
285 it missed one. Fixes bug 40369; bugfix on 0.4.5.1-alpha.
287 o Minor bugfixes (channel, DoS, backport from 0.4.6.2-alpha):
288 - Fix a non-fatal BUG() message due to a too-early free of a string,
289 when listing a client connection from the DoS defenses subsystem.
290 Fixes bug 40345; bugfix on 0.4.3.4-rc.
292 o Minor bugfixes (compiler warnings, backport from 0.4.6.3-rc):
293 - Fix an indentation problem that led to a warning from GCC 11.1.1.
294 Fixes bug 40380; bugfix on 0.3.0.1-alpha.
296 o Minor bugfixes (controller, backport from 0.4.6.1-alpha):
297 - Fix a "BUG" warning that would appear when a controller chooses
298 the first hop for a circuit, and that circuit completes. Fixes bug
299 40285; bugfix on 0.3.2.1-alpha.
301 o Minor bugfixes (onion service, client, memory leak, backport from 0.4.6.3-rc):
302 - Fix a bug where an expired cached descriptor could get overwritten
303 with a new one without freeing it, leading to a memory leak. Fixes
304 bug 40356; bugfix on 0.3.5.1-alpha.
306 o Minor bugfixes (testing, BSD, backport from 0.4.6.2-alpha):
307 - Fix pattern-matching errors when patterns expand to invalid paths
308 on BSD systems. Fixes bug 40318; bugfix on 0.4.5.1-alpha. Patch by
312 Changes in version 0.4.5.7 - 2021-03-16
313 Tor 0.4.5.7 fixes two important denial-of-service bugs in earlier
316 One of these vulnerabilities (TROVE-2021-001) would allow an attacker
317 who can send directory data to a Tor instance to force that Tor
318 instance to consume huge amounts of CPU. This is easiest to exploit
319 against authorities, since anybody can upload to them, but directory
320 caches could also exploit this vulnerability against relays or clients
321 when they download. The other vulnerability (TROVE-2021-002) only
322 affects directory authorities, and would allow an attacker to remotely
323 crash the authority with an assertion failure. Patches have already
324 been provided to the authority operators, to help ensure
327 We recommend that everybody upgrade to one of the releases that fixes
328 these issues (0.3.5.14, 0.4.4.8, or 0.4.5.7) as they become available
331 This release also updates our GeoIP data source, and fixes a few
332 smaller bugs in earlier releases.
334 o Major bugfixes (security, denial of service):
335 - Disable the dump_desc() function that we used to dump unparseable
336 information to disk. It was called incorrectly in several places,
337 in a way that could lead to excessive CPU usage. Fixes bug 40286;
338 bugfix on 0.2.2.1-alpha. This bug is also tracked as TROVE-2021-
339 001 and CVE-2021-28089.
340 - Fix a bug in appending detached signatures to a pending consensus
341 document that could be used to crash a directory authority. Fixes
342 bug 40316; bugfix on 0.2.2.6-alpha. Tracked as TROVE-2021-002
345 o Minor features (geoip data):
346 - We have switched geoip data sources. Previously we shipped IP-to-
347 country mappings from Maxmind's GeoLite2, but in 2019 they changed
348 their licensing terms, so we were unable to update them after that
349 point. We now ship geoip files based on the IPFire Location
350 Database instead. (See https://location.ipfire.org/ for more
351 information). This release updates our geoip files to match the
352 IPFire Location Database as retrieved on 2021/03/12. Closes
355 o Minor bugfixes (directory authority):
356 - Now that exit relays don't allow exit connections to directory
357 authority DirPorts (to prevent network reentry), disable
358 authorities' reachability self test on the DirPort. Fixes bug
359 40287; bugfix on 0.4.5.5-rc.
361 o Minor bugfixes (documentation):
362 - Fix a formatting error in the documentation for
363 VirtualAddrNetworkIPv6. Fixes bug 40256; bugfix on 0.2.9.4-alpha.
365 o Minor bugfixes (Linux, relay):
366 - Fix a bug in determining total available system memory that would
367 have been triggered if the format of Linux's /proc/meminfo file
368 had ever changed to include "MemTotal:" in the middle of a line.
369 Fixes bug 40315; bugfix on 0.2.5.4-alpha.
371 o Minor bugfixes (metrics port):
372 - Fix a BUG() warning on the MetricsPort for an internal missing
373 handler. Fixes bug 40295; bugfix on 0.4.5.1-alpha.
375 o Minor bugfixes (onion service):
376 - Remove a harmless BUG() warning when reloading tor configured with
377 onion services. Fixes bug 40334; bugfix on 0.4.5.1-alpha.
379 o Minor bugfixes (portability):
380 - Fix a non-portable usage of "==" with "test" in the configure
381 script. Fixes bug 40298; bugfix on 0.4.5.1-alpha.
383 o Minor bugfixes (relay):
384 - Remove a spammy log notice falsely claiming that the IPv4/v6
385 address was missing. Fixes bug 40300; bugfix on 0.4.5.1-alpha.
386 - Do not query the address cache early in the boot process when
387 deciding if a relay needs to fetch early directory information
388 from an authority. This bug resulted in a relay falsely believing
389 it didn't have an address and thus triggering an authority fetch
390 at each boot. Related to our fix for 40300.
392 o Removed features (mallinfo deprecated):
393 - Remove mallinfo() usage entirely. Libc 2.33+ now deprecates it.
397 Changes in version 0.4.5.6 - 2021-02-15
398 The Tor 0.4.5.x release series is dedicated to the memory of Karsten
399 Loesing (1979-2020), Tor developer, cypherpunk, husband, and father.
400 Karsten is best known for creating the Tor metrics portal and leading
401 the metrics team, but he was involved in Tor from the early days. For
402 example, while he was still a student he invented and implemented the
403 v2 onion service directory design, and he also served as an ambassador
404 to the many German researchers working in the anonymity field. We
405 loved him and respected him for his patience, his consistency, and his
406 welcoming approach to growing our community.
408 This release series introduces significant improvements in relay IPv6
409 address discovery, a new "MetricsPort" mechanism for relay operators
410 to measure performance, LTTng support, build system improvements to
411 help when using Tor as a static library, and significant bugfixes
412 related to Windows relay performance. It also includes numerous
413 smaller features and bugfixes.
415 Below are the changes since 0.4.4.4-rc. For a complete list of changes
416 since 0.4.4.7, see the ReleaseNotes file.
418 o Major bugfixes (IPv6, relay):
419 - Fix a bug that prevented a relay from publishing its descriptor if
420 an auto-discovered IPv6 that was found unreachable. Fixes bug
421 40279; bugfix on 0.4.5.1-alpha.
423 o Minor features (protocol versions):
424 - Stop claiming to support the "DirCache=1" subprotocol version.
425 Technically, we stopped supporting this subprotocol back in
426 0.4.5.1-alpha, but we needed to wait for the authorities to stop
427 listing it as "required" before we could drop it from the list.
430 o Minor bugfixes (logging):
431 - Avoid a spurious log message about missing subprotocol versions,
432 when the consensus that we're reading from is older than the
433 current release. Previously we had made this message nonfatal, but
434 in practice, it is never relevant when the consensus is older than
435 the current release. Fixes bug 40281; bugfix on 0.4.0.1-alpha.
437 o Minor bugfixes (metrics port):
438 - Fix a bug warning when a metrics port socket was unexpectedly
439 closed. Fixes bug 40257; bugfix on 0.4.5.1-alpha
441 o Minor bugfixes (relay):
442 - Allow relays to have a RFC1918 address if PublishServerDescriptor
443 is set to 0 and AssumeReachable is set to 1. This is to support
444 the use case of a bridge on a local network, exposed via a
445 pluggable transport. Fixes bug 40208; bugfix on 0.4.5.1-alpha.
447 o Minor bugfixes (relay, config):
448 - Fix a problem in the removal of duplicate ORPorts from the
449 internal port list when loading the config file. We were removing
450 the wrong ports, breaking valid torrc uses cases for multiple
451 ORPorts of the same address family. Fixes bug 40289; bugfix
455 Changes in version 0.4.5.5-rc - 2021-02-01
456 Tor 0.4.5.5-rc is the third release candidate in its series. We're
457 coming closer and closer to a stable release series. This release
458 fixes an annoyance with address detection code, and somewhat mitigates
459 an ongoing denial-of-service attack.
461 We anticipate no more code changes between this and the stable
462 release, though of course that could change.
464 o Major feature (exit):
465 - Re-entry into the network is now denied at the Exit level to all
466 relays' ORPorts and authorities' ORPorts and DirPorts. This change
467 should help mitgate a set of denial-of-service attacks. Closes
470 o Minor bugfixes (relay, configuration):
471 - Don't attempt to discover our address (IPv4 or IPv6) if no ORPort
472 for it can be found in the configuration. Fixes bug 40254; bugfix
476 Changes in version 0.4.5.4-rc - 2021-01-22
477 Tor 0.4.5.4-rc is the second release candidate in its series. It fixes
478 several bugs present in previous releases.
480 We expect that the stable release will be the same, or almost the
481 same, as this release candidate, unless serious bugs are found.
483 o Major bugfixes (authority, IPv6):
484 - Do not consider multiple relays in the same IPv6 /64 network to be
485 sybils. Fixes bug 40243; bugfix on 0.4.5.1-alpha.
487 o Major bugfixes (directory cache, performance, windows):
488 - Limit the number of items in the consensus diff cache to 64 on
489 Windows. We hope this will mitigate an issue where Windows relay
490 operators reported Tor using 100% CPU, while we investigate better
491 solutions. Fixes bug 24857; bugfix on 0.3.1.1-alpha.
493 o Minor feature (build system):
494 - New "make lsp" command to generate the compile_commands.json file
495 used by the ccls language server. The "bear" program is needed for
496 this. Closes ticket 40227.
498 o Minor features (authority, logging):
499 - Log more information for directory authority operators during the
500 consensus voting process, and while processing relay descriptors.
502 - Reject obsolete router/extrainfo descriptors earlier and more
503 quietly, to avoid spamming the logs. Fixes bug 40238; bugfix
506 o Minor bugfixes (compilation):
507 - Fix another warning about unreachable fallthrough annotations when
508 building with "--enable-all-bugs-are-fatal" on some compilers.
509 Fixes bug 40241; bugfix on 0.4.5.3-rc.
510 - Change the linker flag ordering in our library search code so that
511 it works for compilers that need the libraries to be listed in the
512 right order. Fixes bug 33624; bugfix on 0.1.1.0-alpha.
514 o Minor bugfixes (config, bridge):
515 - Don't initiate a connection to a bridge configured to use a
516 missing transport. This change reverts an earlier fix that would
517 try to avoid such situations during configuration chcecking, but
518 which doesn't work with DisableNetwork. Fixes bug 40106; bugfix
521 o Minor bugfixes (onion services):
522 - Avoid a non-fatal assertion in certain edge-cases when
523 establishing a circuit to an onion service. Fixes bug 32666;
524 bugfix on 0.3.0.3-alpha.
526 o Minor bugfixes (relay):
527 - If we were unable to build our descriptor, don't mark it as having
528 been advertised. Also remove an harmless BUG(). Fixes bug 40231;
529 bugfix on 0.4.5.1-alpha.
532 Changes in version 0.4.5.3-rc - 2021-01-12
533 Tor 0.4.5.3-rc is the first release candidate in its series. It fixes
534 several bugs, including one that broke onion services on certain older
537 Though we anticipate that we'll be doing a bit more clean-up between
538 now and the stable release, we expect that our remaining changes will
539 be fairly simple. There will be at least one more release candidate
540 before 0.4.5.x is stable.
542 o Major bugfixes (onion service v3):
543 - Stop requiring a live consensus for v3 clients and services, and
544 allow a "reasonably live" consensus instead. This allows v3 onion
545 services to work even if the authorities fail to generate a
546 consensus for more than 2 hours in a row. Fixes bug 40237; bugfix
549 o Minor features (crypto):
550 - Fix undefined behavior on our Keccak library. The bug only
551 appeared on platforms with 32-byte CPU cache lines (e.g. armv5tel)
552 and would result in wrong digests. Fixes bug 40210; bugfix on
553 0.2.8.1-alpha. Thanks to Bernhard Übelacker, Arnd Bergmann and
554 weasel for diagnosing this.
556 o Minor features (documentation):
557 - Mention the "!badexit" directive that can appear in an authority's
558 approved-routers file, and update the description of the
559 "!invalid" directive. Closes ticket 40188.
561 o Minor bugfixes (compilation):
562 - Fix a compilation warning about unreachable fallthrough
563 annotations when building with "--enable-all-bugs-are-fatal" on
564 some compilers. Fixes bug 40241; bugfix on 0.3.5.4-alpha.
565 - Fix the "--enable-static-tor" switch to properly set the "-static"
566 compile option onto the tor binary only. Fixes bug 40111; bugfix
569 o Minor bugfixes (config, bridge):
570 - Really fix the case where torrc has a missing ClientTransportPlugin
571 but is configured with a Bridge line and UseBridges. Previously,
572 we didn't look at the managed proxy list and thus would fail for
573 the "exec" case. Fixes bug 40106; bugfix on 0.4.5.1-alpha.
575 o Minor bugfixes (logging, relay):
576 - Log our address as reported by the directory authorities, if none
577 was configured or detected before. Fixes bug 40201; bugfix
579 - When a launching bandwidth testing circuit, don't incorrectly call
580 it a reachability test, or trigger a "CHECKING_REACHABILITY"
581 control event. Fixes bug 40205; bugfix on 0.4.5.1-alpha.
583 o Minor bugfixes (relay, statistics):
584 - Report the correct connection statistics in our extrainfo
585 documents. Previously there was a problem in the file loading
586 function which would wrongly truncate a state file, causing the
587 wrong information to be reported. Fixes bug 40226; bugfix
590 o Minor bugfixes (SOCKS5):
591 - Handle partial SOCKS5 messages correctly. Previously, our code
592 would send an incorrect error message if it got a SOCKS5 request
593 that wasn't complete. Fixes bug 40190; bugfix on 0.3.5.1-alpha.
596 Changes in version 0.4.5.2-alpha - 2020-11-23
597 Tor 0.4.5.2-alpha is the second alpha release in the 0.4.5.x series.
598 It fixes several bugs present in earlier releases, including one that
599 made it impractical to run relays on Windows. It also adds a few small
600 safety features to improve Tor's behavior in the presence of strange
601 compile-time options, misbehaving proxies, and future versions
604 o Major bugfixes (relay, windows):
605 - Fix a bug in our implementation of condition variables on Windows.
606 Previously, a relay on Windows would use 100% CPU after running
607 for some time. Because of this change, Tor now require Windows
608 Vista or later to build and run. Fixes bug 30187; bugfix on
609 0.2.6.3-alpha. (This bug became more serious in 0.3.1.1-alpha with
610 the introduction of consensus diffs.) Patch by Daniel Pinto.
612 o Minor features (compilation):
613 - Disable deprecation warnings when building with OpenSSL 3.0.0 or
614 later. There are a number of APIs newly deprecated in OpenSSL
615 3.0.0 that Tor still requires. (A later version of Tor will try to
616 stop depending on these APIs.) Closes ticket 40165.
618 o Minor features (protocol, proxy support, defense in depth):
619 - Respond more deliberately to misbehaving proxies that leave
620 leftover data on their connections, so as to make Tor even less
621 likely to allow the proxies to pass their data off as having come
622 from a relay. Closes ticket 40017.
624 o Minor features (safety):
625 - Log a warning at startup if Tor is built with compile-time options
626 that are likely to make it less stable or reliable. Closes
629 o Minor bugfixes (circuit, handshake):
630 - In the v3 handshaking code, use connection_or_change_state() to
631 change the state. Previously, we changed the state directly, but
632 this did not pass the state change to the pubsub or channel
633 objects, potentially leading to bugs. Fixes bug 32880; bugfix on
634 0.2.3.6-alpha. Patch by Neel Chauhan.
636 o Minor bugfixes (compilation):
637 - Use the correct 'ranlib' program when building libtor.a.
638 Previously we used the default ranlib, which broke some kinds of
639 cross-compilation. Fixes bug 40172; bugfix on 0.4.5.1-alpha.
640 - Remove a duplicate typedef in metrics_store.c. Fixes bug 40177;
641 bugfix on 0.4.5.1-alpha.
642 - When USDT tracing is enabled, and STAP_PROBEV() is missing, don't
643 attempt to build. Linux supports that macro but not the BSDs.
644 Fixes bug 40174; bugfix on 0.4.5.1-alpha.
646 o Minor bugfixes (configuration):
647 - Exit Tor on a misconfiguration when the Bridge line is configured
648 to use a transport but no corresponding ClientTransportPlugin can
649 be found. Prior to this fix, Tor would attempt to connect to the
650 bridge directly without using the transport, making it easier for
651 adversaries to notice the bridge. Fixes bug 25528; bugfix
653 - Fix an issue where an ORPort was compared with other kinds of
654 ports, when it should have been only checked against other
655 ORPorts. This bug would lead to "DirPort auto" getting ignored.
656 Fixes bug 40195; bugfix on 0.4.5.1-alpha.
657 - Fix a bug where a second non-ORPort with a variant family (ex:
658 SocksPort [::1]:9050) would be ignored due to a configuration
659 parsing error. Fixes bug 40183; bugfix on 0.4.5.1-alpha.
661 o Minor bugfixes (crash, relay, signing key):
662 - Avoid assertion failures when we run Tor from the command line
663 with `--key-expiration sign`, but an ORPort is not set. Fixes bug
664 40015; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
666 o Minor bugfixes (logging):
667 - Remove trailing whitespace from control event log messages. Fixes
668 bug 32178; bugfix on 0.1.1.1-alpha. Based on a patch by
670 - Turn warning-level log message about SENDME failure into a debug-
671 level message. (This event can happen naturally, and is no reason
672 for concern). Fixes bug 40142; bugfix on 0.4.1.1-alpha.
674 o Minor bugfixes (relay, address discovery):
675 - Don't trigger an IP change when no new valid IP can be found.
676 Fixes bug 40071; bugfix on 0.4.5.1-alpha.
677 - When attempting to discover our IP, use a simple test circuit,
678 rather than a descriptor fetch: the same address information is
679 present in NETINFO cells, and is better authenticated there. Fixes
680 bug 40071; bugfix on 0.4.5.1-alpha.
682 o Minor bugfixes (testing):
683 - Fix the `config/parse_tcp_proxy_line` test so that it works
684 correctly on systems where the DNS provider hijacks invalid
685 queries. Fixes part of bug 40179; bugfix on 0.4.3.1-alpha.
686 - Fix unit tests that used newly generated list of routers so that
687 they check them with respect to the date when they were generated,
688 not with respect to the current time. Fixes bug 40187; bugfix
690 - Fix our Python reference-implementation for the v3 onion service
691 handshake so that it works correctly with the version of hashlib
692 provided by Python 3.9. Fixes part of bug 40179; bugfix
694 - Fix the `tortls/openssl/log_one_error` test to work with OpenSSL
695 3.0.0. Fixes bug 40170; bugfix on 0.2.8.1-alpha.
697 o Removed features (controller):
698 - Remove the "GETINFO network-status" controller command. It has
699 been deprecated since 0.3.1.1-alpha. Closes ticket 22473.
702 Changes in version 0.4.4.6 - 2020-11-12
703 Tor 0.4.4.6 is the second stable release in the 0.4.4.x series. It
704 backports fixes from later releases, including a fix for TROVE-2020-
705 005, a security issue that could be used, under certain cases, by an
706 adversary to observe traffic patterns on a limited number of circuits
707 intended for a different relay.
709 o Major bugfixes (security, backport from 0.4.5.1-alpha):
710 - When completing a channel, relays now check more thoroughly to
711 make sure that it matches any pending circuits before attaching
712 those circuits. Previously, address correctness and Ed25519
713 identities were not checked in this case, but only when extending
714 circuits on an existing channel. Fixes bug 40080; bugfix on
715 0.2.7.2-alpha. Resolves TROVE-2020-005.
717 o Minor features (directory authorities, backport from 0.4.5.1-alpha):
718 - Authorities now list a different set of protocols as required and
719 recommended. These lists have been chosen so that only truly
720 recommended and/or required protocols are included, and so that
721 clients using 0.2.9 or later will continue to work (even though
722 they are not supported), whereas only relays running 0.3.5 or
723 later will meet the requirements. Closes ticket 40162.
724 - Make it possible to specify multiple ConsensusParams torrc lines.
725 Now directory authority operators can for example put the main
726 ConsensusParams config in one torrc file and then add to it from a
727 different torrc file. Closes ticket 40164.
729 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
730 - Tor no longer allows subprotocol versions larger than 63.
731 Previously version numbers up to UINT32_MAX were allowed, which
732 significantly complicated our code. Implements proposal 318;
735 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
736 - Fix a rendezvous cache unit test that was triggering an underflow
737 on the global rend cache allocation. Fixes bug 40125; bugfix
739 - Fix another rendezvous cache unit test that was triggering an
740 underflow on the global rend cache allocation. Fixes bug 40126;
741 bugfix on 0.2.8.1-alpha.
743 o Minor bugfixes (compilation, backport from 0.4.5.1-alpha):
744 - Fix compiler warnings that would occur when building with
745 "--enable-all-bugs-are-fatal" and "--disable-module-relay" at the
746 same time. Fixes bug 40129; bugfix on 0.4.4.1-alpha.
747 - Resolve a compilation warning that could occur in
748 test_connection.c. Fixes bug 40113; bugfix on 0.2.9.3-alpha.
750 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
751 - Remove a debug logging statement that uselessly spammed the logs.
752 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
754 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
755 - Avoid a fatal assert() when failing to create a listener
756 connection for an address that was in use. Fixes bug 40073; bugfix
759 o Minor bugfixes (v2 onion services, backport from 0.4.5.1-alpha):
760 - For HSFETCH commands on v2 onion services addresses, check the
761 length of bytes decoded, not the base32 length. Fixes bug 34400;
762 bugfix on 0.4.1.1-alpha. Patch by Neel Chauhan.
765 Changes in version 0.4.3.7 - 2020-11-12
766 Tor 0.4.3.7 backports several bugfixes from later releases. It
767 includes a fix for TROVE-2020-005, a security issue that could be
768 used, under certain cases, by an adversary to observe traffic patterns
769 on a limited number of circuits intended for a different relay.
771 Please be aware that support for the 0.4.3.x series will end on 15
772 February 2021. Please upgrade to 0.4.4.x or 0.4.5.x before then, or
773 downgrade to 0.3.5.x, which will be supported until at least 1
776 o Major features (fallback directory list, backport form 0.4.4.3-alpha):
777 - Replace the 148 fallback directories originally included in Tor
778 0.4.1.4-rc (of which around 105 are still functional) with a list
779 of 144 fallbacks generated in July 2020. Closes ticket 40061.
781 o Major bugfixes (security, backport from 0.4.5.1-alpha):
782 - When completing a channel, relays now check more thoroughly to
783 make sure that it matches any pending circuits before attaching
784 those circuits. Previously, address correctness and Ed25519
785 identities were not checked in this case, but only when extending
786 circuits on an existing channel. Fixes bug 40080; bugfix on
787 0.2.7.2-alpha. Resolves TROVE-2020-005.
789 o Major bugfixes (NSS, backport from 0.4.4.3-alpha):
790 - When running with NSS enabled, make sure that NSS knows to expect
791 nonblocking sockets. Previously, we set our TCP sockets as
792 nonblocking, but did not tell NSS, which in turn could lead to
793 unexpected blocking behavior. Fixes bug 40035; bugfix
796 o Minor features (security, backport from 0.4.4.4-rc):
797 - Channels using obsolete versions of the Tor link protocol are no
798 longer allowed to circumvent address-canonicity checks. (This is
799 only a minor issue, since such channels have no way to set ed25519
800 keys, and therefore should always be rejected for circuits that
801 specify ed25519 identities.) Closes ticket 40081.
803 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
804 - Tor no longer allows subprotocol versions larger than 63.
805 Previously version numbers up to UINT32_MAX were allowed, which
806 significantly complicated our code. Implements proposal 318;
809 o Minor features (tests, backport from 0.4.4.5):
810 - Our "make check" target now runs the unit tests in 8 parallel
811 chunks. Doing this speeds up hardened CI builds by more than a
812 factor of two. Closes ticket 40098.
814 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
815 - Fix a rendezvous cache unit test that was triggering an underflow
816 on the global rend cache allocation. Fixes bug 40125; bugfix
818 - Fix another rendezvous cache unit test that was triggering an
819 underflow on the global rend cache allocation. Fixes bug 40126;
820 bugfix on 0.2.8.1-alpha.
822 o Minor bugfixes (correctness, buffers, backport from 0.4.4.4-rc):
823 - Fix a correctness bug that could cause an assertion failure if we
824 ever tried using the buf_move_all() function with an empty input
825 buffer. As far as we know, no released versions of Tor do this.
826 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
828 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
829 - Remove a debug logging statement that uselessly spammed the logs.
830 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
832 o Minor bugfixes (rate limiting, bridges, pluggable transports, backport from 0.4.4.4-rc):
833 - On a bridge, treat all connections from an ExtORPort as remote by
834 default for the purposes of rate-limiting. Previously, bridges
835 would treat the connection as local unless they explicitly
836 received a "USERADDR" command. ExtORPort connections still count
837 as local if there is a USERADDR command with an explicit local
838 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
840 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
841 - Avoid a fatal assert() when failing to create a listener
842 connection for an address that was in use. Fixes bug 40073; bugfix
845 o Minor bugfixes (relay, usability, backport from 0.4.4.3-alpha):
846 - Adjust the rules for when to warn about having too many
847 connections to other relays. Previously we'd tolerate up to 1.5
848 connections per relay on average. Now we tolerate more connections
849 for directory authorities, and raise the number of total
850 connections we need to see before we warn. Fixes bug 33880; bugfix
853 o Minor bugfixes (tests, 0.4.4.5):
854 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
855 on its own. Previously, it would exit with an error. Fixes bug
856 40099; bugfix on 0.2.8.1-alpha.
858 o Minor bugfixes (v2 onion services, backport from 0.4.5.1-alpha):
859 - For HSFETCH commands on v2 onion services addresses, check the
860 length of bytes decoded, not the base32 length. Fixes bug 34400;
861 bugfix on 0.4.1.1-alpha. Patch by Neel Chauhan.
863 o Minor bugfixes (windows, backport from 0.4.4.4-rc):
864 - Fix a bug that prevented Tor from starting if its log file grew
865 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
867 o Deprecated features (onion service v2, backport form 0.4.4.2-alpha):
868 - Add a deprecation warning for version 2 onion services. Closes
871 o Removed features (backport from 0.4.4.3-alpha):
872 - Our "check-local" test target no longer tries to use the
873 Coccinelle semantic patching tool parse all the C files. While it
874 is a good idea to try to make sure Coccinelle works on our C
875 before we run a Coccinelle patch, doing so on every test run has
876 proven to be disruptive. You can still run this tool manually with
877 "make check-cocci". Closes ticket 40030. ticket 40030.
880 Changes in version 0.3.5.12 - 2020-11-12
881 Tor 0.4.3.7 backports several bugfixes from later releases. It
882 includes a fix for TROVE-2020-005, a security issue that could be
883 used, under certain cases, by an adversary to observe traffic patterns
884 on a limited number of circuits intended for a different relay.
886 o Major features (fallback directory list, backport form 0.4.4.3-alpha):
887 - Replace the 148 fallback directories originally included in Tor
888 0.4.1.4-rc (of which around 105 are still functional) with a list
889 of 144 fallbacks generated in July 2020. Closes ticket 40061.
891 o Major bugfixes (security, backport from 0.4.5.1-alpha):
892 - When completing a channel, relays now check more thoroughly to
893 make sure that it matches any pending circuits before attaching
894 those circuits. Previously, address correctness and Ed25519
895 identities were not checked in this case, but only when extending
896 circuits on an existing channel. Fixes bug 40080; bugfix on
897 0.2.7.2-alpha. Resolves TROVE-2020-005.
899 o Major bugfixes (NSS, backport from 0.4.4.3-alpha):
900 - When running with NSS enabled, make sure that NSS knows to expect
901 nonblocking sockets. Previously, we set our TCP sockets as
902 nonblocking, but did not tell NSS, which in turn could lead to
903 unexpected blocking behavior. Fixes bug 40035; bugfix
906 o Minor features (security, backport from 0.4.4.4-rc):
907 - Channels using obsolete versions of the Tor link protocol are no
908 longer allowed to circumvent address-canonicity checks. (This is
909 only a minor issue, since such channels have no way to set ed25519
910 keys, and therefore should always be rejected for circuits that
911 specify ed25519 identities.) Closes ticket 40081.
913 o Minor features (debugging, directory system):
914 - Don't crash when we find a non-guard with a guard-fraction value
915 set. Instead, log a bug warning, in an attempt to figure out how
916 this happened. Diagnostic for ticket 32868.
918 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
919 - Tor no longer allows subprotocol versions larger than 63.
920 Previously version numbers up to UINT32_MAX were allowed, which
921 significantly complicated our code. Implements proposal 318;
924 o Minor features (tests, backport from 0.4.4.5):
925 - Our "make check" target now runs the unit tests in 8 parallel
926 chunks. Doing this speeds up hardened CI builds by more than a
927 factor of two. Closes ticket 40098.
929 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
930 - Fix a rendezvous cache unit test that was triggering an underflow
931 on the global rend cache allocation. Fixes bug 40125; bugfix
933 - Fix another rendezvous cache unit test that was triggering an
934 underflow on the global rend cache allocation. Fixes bug 40126;
935 bugfix on 0.2.8.1-alpha.
937 o Minor bugfixes (correctness, buffers, backport from 0.4.4.4-rc):
938 - Fix a correctness bug that could cause an assertion failure if we
939 ever tried using the buf_move_all() function with an empty input
940 buffer. As far as we know, no released versions of Tor do this.
941 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
943 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
944 - Remove a debug logging statement that uselessly spammed the logs.
945 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
947 o Minor bugfixes (rate limiting, bridges, pluggable transports, backport from 0.4.4.4-rc):
948 - On a bridge, treat all connections from an ExtORPort as remote by
949 default for the purposes of rate-limiting. Previously, bridges
950 would treat the connection as local unless they explicitly
951 received a "USERADDR" command. ExtORPort connections still count
952 as local if there is a USERADDR command with an explicit local
953 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
955 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
956 - Avoid a fatal assert() when failing to create a listener
957 connection for an address that was in use. Fixes bug 40073; bugfix
960 o Minor bugfixes (relay, usability, backport from 0.4.4.3-alpha):
961 - Adjust the rules for when to warn about having too many
962 connections to other relays. Previously we'd tolerate up to 1.5
963 connections per relay on average. Now we tolerate more connections
964 for directory authorities, and raise the number of total
965 connections we need to see before we warn. Fixes bug 33880; bugfix
968 o Minor bugfixes (relays, backport from 0.4.4.1-alpha):
969 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
970 descriptors, when the IPv6 port was configured as "auto". Fixes
971 bug 32588; bugfix on 0.2.3.9-alpha.
973 o Minor bugfixes (tests, 0.4.4.5):
974 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
975 on its own. Previously, it would exit with an error. Fixes bug
976 40099; bugfix on 0.2.8.1-alpha.
978 o Minor bugfixes (windows, backport from 0.4.4.4-rc):
979 - Fix a bug that prevented Tor from starting if its log file grew
980 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
982 o Deprecated features (onion service v2, backport form 0.4.4.2-alpha):
983 - Add a deprecation warning for version 2 onion services. Closes
987 Changes in version 0.4.5.1-alpha - 2020-11-01
988 Tor 0.4.5.1-alpha is the first alpha release in the 0.4.5.x series. It
989 improves support for IPv6, address discovery and self-testing, code
992 This release also fixes TROVE-2020-005, a security issue that could be
993 used, under certain cases, by an adversary to observe traffic patterns
994 on a limited number of circuits intended for a different relay. To
995 mount this attack, the adversary would need to actively extend
996 circuits to an incorrect address, as well as compromise a relay's
997 legacy RSA-1024 key. We'll be backporting this fix to other release
998 series soon, after it has had some testing.
1000 Here are the changes since 0.4.4.5.
1002 o Major features (build):
1003 - When building Tor, first link all object files into a single
1004 static library. This may help with embedding Tor in other
1005 programs. Note that most Tor functions do not constitute a part of
1006 a stable or supported API: only those functions in tor_api.h
1007 should be used if embedding Tor. Closes ticket 40127.
1009 o Major features (metrics):
1010 - Introduce a new MetricsPort which exposes, through an HTTP
1011 interface, a series of metrics that tor collects at runtime. At
1012 the moment, the only supported output format is Prometheus data
1013 model. Closes ticket 40063. See the manual page for more
1014 information and security considerations.
1015 o Major features (relay, IPv6):
1016 - The torrc option Address now supports IPv6. This unifies our
1017 address discovery interface to support IPv4, IPv6, and hostnames.
1018 Closes ticket 33233.
1019 - Launch IPv4 and IPv6 ORPort self-test circuits on relays and
1020 bridges. Closes ticket 33222.
1021 - Relays now automatically bind on IPv6 for their ORPort, unless
1022 specified otherwise with the IPv4Only flag. Closes ticket 33246.
1023 - When a relay with IPv6 support is told to open a connection to
1024 another relay, and the extend cell lists both IPv4 and IPv6
1025 addresses, the first relay now picks randomly which address to
1026 use. Closes ticket 33220.
1027 - Relays now track their IPv6 ORPort reachability separately from
1028 the reachability of their IPv4 ORPort. They will not publish a
1029 descriptor unless _both_ ports appear to be externally reachable.
1030 Closes ticket 34067.
1032 o Major features (tracing):
1033 - Add event-tracing library support for USDT and LTTng-UST, and a
1034 few tracepoints in the circuit subsystem. More will come
1035 incrementally. This feature is compiled out by default: it needs
1036 to be enabled at configure time. See documentation in
1037 doc/HACKING/Tracing.md. Closes ticket 32910.
1039 o Major bugfixes (security):
1040 - When completing a channel, relays now check more thoroughly to
1041 make sure that it matches any pending circuits before attaching
1042 those circuits. Previously, address correctness and Ed25519
1043 identities were not checked in this case, but only when extending
1044 circuits on an existing channel. Fixes bug 40080; bugfix on
1045 0.2.7.2-alpha. Resolves TROVE-2020-005.
1047 o Major bugfixes (TLS, buffer):
1048 - When attempting to read N bytes on a TLS connection, really try to
1049 read all N bytes. Previously, Tor would stop reading after the
1050 first TLS record, which can be smaller than the N bytes requested,
1051 and not check for more data until the next mainloop event. Fixes
1052 bug 40006; bugfix on 0.1.0.5-rc.
1054 o Minor features (address discovery):
1055 - If no Address statements are found, relays now prioritize guessing
1056 their address by looking at the local interface instead of the
1057 local hostname. If the interface address can't be found, the local
1058 hostname is used. Closes ticket 33238.
1060 o Minor features (admin tools):
1061 - Add a new --format argument to -key-expiration option to allow
1062 specifying the time format of the expiration date. Adds Unix
1063 timestamp format support. Patch by Daniel Pinto. Closes
1066 o Minor features (bootstrap reporting):
1067 - When reporting bootstrapping status on a relay, do not consider
1068 connections that have never been the target of an origin circuit.
1069 Previously, all connection failures were treated as potential
1070 bootstrapping failures, including connections that had been opened
1071 because of client requests. Closes ticket 25061.
1073 o Minor features (build):
1074 - When running the configure script, try to detect version
1075 mismatches between the OpenSSL headers and libraries, and suggest
1076 that the user should try "--with-openssl-dir". Closes 40138.
1077 - If the configure script has given any warnings, remind the user
1078 about them at the end of the script. Related to 40138.
1080 o Minor features (configuration):
1081 - Allow using wildcards (* and ?) with the %include option on
1082 configuration files. Closes ticket 25140. Patch by Daniel Pinto.
1083 - Allow the configuration options EntryNodes, ExcludeNodes,
1084 ExcludeExitNodes, ExitNodes, MiddleNodes, HSLayer2Nodes and
1085 HSLayer3Nodes to be specified multiple times. Closes ticket 28361.
1086 Patch by Daniel Pinto.
1088 o Minor features (control port):
1089 - Add a DROPTIMEOUTS command to drop circuit build timeout history
1090 and reset the current timeout. Closes ticket 40002.
1091 - When a stream enters the AP_CONN_STATE_CONTROLLER_WAIT status,
1092 send a control port event. Closes ticket 32190. Patch by
1094 - Introduce GETINFO "stats/ntor/{assigned/requested}" and
1095 "stats/tap/{assigned/requested}" to get the NTor and TAP circuit
1096 onion handshake counts respectively. Closes ticket 28279. Patch by
1099 o Minor features (control port, IPv6):
1100 - Tor relays now try to report to the controller when they are
1101 launching an IPv6 self-test. Closes ticket 34068.
1102 - Introduce "GETINFO address/v4" and "GETINFO address/v6" in the
1103 control port to fetch the Tor host's respective IPv4 or IPv6
1104 address. We keep "GETINFO address" for backwards-compatibility.
1105 Closes ticket 40039. Patch by Neel Chauhan.
1107 o Minor features (directory authorities):
1108 - Authorities now list a different set of protocols as required and
1109 recommended. These lists have been chosen so that only truly
1110 recommended and/or required protocols are included, and so that
1111 clients using 0.2.9 or later will continue to work (even though
1112 they are not supported), whereas only relays running 0.3.5 or
1113 later will meet the requirements. Closes ticket 40162.
1114 - Add a new consensus method 30 that removes the unnecessary "="
1115 padding from ntor-onion-key. Closes ticket 7869. Patch by
1117 - Directory authorities now reject descriptors from relays running
1118 Tor versions from the obsolete 0.4.1 series. Resolves ticket
1119 34357. Patch by Neel Chauhan.
1120 - Make it possible to specify multiple ConsensusParams torrc lines.
1121 Now directory authority operators can for example put the main
1122 ConsensusParams config in one torrc file and then add to it from a
1123 different torrc file. Closes ticket 40164.
1124 - The AssumeReachable option no longer stops directory authorities
1125 from checking whether other relays are running. A new
1126 AuthDirTestReachability option can be used to disable these
1127 checks. Closes ticket 34445.
1128 - When looking for possible Sybil attacks, also consider IPv6
1129 addresses. Two routers are considered to have "the same" address
1130 by this metric if they are in the same /64 network. Patch from
1131 Maurice Pibouin. Closes ticket 7193.
1133 o Minor features (directory authorities, IPv6):
1134 - Make authorities add their IPv6 ORPort (if any) to the trusted
1135 servers list. Authorities previously added only their IPv4
1136 addresses. Closes ticket 32822.
1138 o Minor features (ed25519, relay):
1139 - Save a relay's base64-encoded ed25519 identity key to the data
1140 directory in a file named fingerprint-ed25519. Closes ticket
1141 30642. Patch by Neel Chauhan.
1143 o Minor features (heartbeat):
1144 - Include the total number of inbound and outbound IPv4 and IPv6
1145 connections in the heartbeat message. Closes ticket 29113.
1147 o Minor features (IPv6, ExcludeNodes):
1148 - Handle IPv6 addresses in ExcludeNodes; previously they were
1149 ignored. Closes ticket 34065. Patch by Neel Chauhan.
1151 o Minor features (logging):
1152 - Add the running glibc version to the log, and the compiled glibc
1153 version to the library list returned when using --library-versions.
1154 Patch from Daniel Pinto. Closes ticket 40047.
1155 - Consider an HTTP 301 response to be an error (like a 404) when
1156 processing a directory response. Closes ticket 40053.
1157 - Log directory fetch statistics as a single line. Closes
1159 - Provide more complete descriptions of our connections when logging
1160 about them. Closes ticket 40041.
1161 - When describing a relay in the logs, we now include its ed25519
1162 identity. Closes ticket 22668.
1164 o Minor features (onion services):
1165 - Only overwrite an onion service's existing hostname file if its
1166 contents are wrong. This enables read-only onion-service
1167 directories. Resolves ticket 40062. Patch by Neel Chauhan.
1169 o Minor features (pluggable transports):
1170 - Add an OutboundBindAddressPT option to allow users to specify
1171 which IPv4 and IPv6 address pluggable transports should use for
1172 outgoing IP packets. Tor does not have a way to enforce that the
1173 pluggable transport honors this option, so each pluggable transport
1174 needs to implement support on its own. Closes ticket 5304.
1176 o Minor features (relay address tracking):
1177 - We now store relay addresses for OR connections in a more logical
1178 way. Previously we would sometimes overwrite the actual address of
1179 a connection with a "canonical address", and then store the "real
1180 address" elsewhere to remember it. We now track the "canonical
1181 address" elsewhere for the cases where we need it, and leave the
1182 connection's address alone. Closes ticket 33898.
1184 o Minor features (relay):
1185 - If a relay is unable to discover its address, attempt to learn it
1186 from the NETINFO cell. Closes ticket 40022.
1187 - Log immediately when launching a relay self-check. Previously we
1188 would try to log before launching checks, or approximately when we
1189 intended to launch checks, but this tended to be error-prone.
1190 Closes ticket 34137.
1192 o Minor features (relay, address discovery):
1193 - If Address option is not found in torrc, attempt to learn our
1194 address with the configured ORPort address if any. Closes
1197 o Minor features (relay, IPv6):
1198 - Add an AssumeReachableIPv6 option to disable self-checking IPv6
1199 reachability. Closes part of ticket 33224.
1200 - Add new "assume-reachable" and "assume-reachable-ipv6" consensus
1201 parameters to be used in an emergency to tell relays that they
1202 should publish even if they cannot complete their ORPort self-
1203 checks. Closes ticket 34064 and part of 33224.
1204 - Allow relays to send IPv6-only extend cells. Closes ticket 33222.
1205 - Declare support for the Relay=3 subprotocol version. Closes
1207 - When launching IPv6 ORPort self-test circuits, make sure that the
1208 second-last hop can initiate an IPv6 extend. Closes ticket 33222.
1210 o Minor features (specification update):
1211 - Several fields in microdescriptors, router descriptors, and
1212 consensus documents that were formerly optional are now required.
1213 Implements proposal 315; closes ticket 40132.
1215 o Minor features (state management):
1216 - When loading the state file, remove entries from the statefile
1217 that have been obsolete for a long time. Ordinarily Tor preserves
1218 unrecognized entries in order to keep forward-compatibility, but
1219 these entries have not actually been used in any release since
1220 before 0.3.5.x. Closes ticket 40137.
1222 o Minor features (statistics, ipv6):
1223 - Relays now publish IPv6-specific counts of single-direction versus
1224 bidirectional relay connections. Closes ticket 33264.
1225 - Relays now publish their IPv6 read and write statistics over time,
1226 if statistics are enabled. Closes ticket 33263.
1228 o Minor features (subprotocol versions):
1229 - Tor no longer allows subprotocol versions larger than 63.
1230 Previously version numbers up to UINT32_MAX were allowed, which
1231 significantly complicated our code. Implements proposal 318;
1232 closes ticket 40133.
1233 - Use the new limitations on subprotocol versions due to proposal
1234 318 to simplify our implementation. Part of ticket 40133.
1236 o Minor features (testing configuration):
1237 - The TestingTorNetwork option no longer implicitly sets
1238 AssumeReachable to 1. This change allows us to test relays' self-
1239 testing mechanisms, and to test authorities' relay-testing
1240 functionality. Closes ticket 34446.
1242 o Minor features (testing):
1243 - Added unit tests for channel_matches_target_addr_for_extend().
1244 Closes Ticket 33919. Patch by MrSquanchee.
1246 o Minor features (tests, v2 onion services):
1247 - Fix a rendezvous cache unit test that was triggering an underflow
1248 on the global rend cache allocation. Fixes bug 40125; bugfix
1250 - Fix another rendezvous cache unit test that was triggering an
1251 underflow on the global rend cache allocation. Fixes bug 40126;
1252 bugfix on 0.2.8.1-alpha.
1254 o Minor bugfixes (circuit padding):
1255 - When circpad_send_padding_cell_for_callback is called,
1256 `is_padding_timer_scheduled` flag was not reset. Now it is set to
1257 0 at the top of that function. Fixes bug 32671; bugfix
1259 - Add a per-circuit padding machine instance counter, so we can
1260 differentiate between shutdown requests for old machines on a
1261 circuit. Fixes bug 30992; bugfix on 0.4.1.1-alpha.
1262 - Add the ability to keep circuit padding machines if they match a
1263 set of circuit states or purposes. This allows us to have machines
1264 that start up under some conditions but don't shut down under
1265 others. We now use this mask to avoid starting up introduction
1266 circuit padding again after the machines have already completed.
1267 Fixes bug 32040; bugfix on 0.4.1.1-alpha.
1269 o Minor bugfixes (compatibility):
1270 - Strip '\r' characters when reading text files on Unix platforms.
1271 This should resolve an issue where a relay operator migrates a
1272 relay from Windows to Unix, but does not change the line ending of
1273 Tor's various state files to match the platform, and the CRLF line
1274 endings from Windows end up leaking into other files such as the
1275 extra-info document. Fixes bug 33781; bugfix on 0.0.9pre5.
1277 o Minor bugfixes (compilation):
1278 - Fix compiler warnings that would occur when building with
1279 "--enable-all-bugs-are-fatal" and "--disable-module-relay" at the
1280 same time. Fixes bug 40129; bugfix on 0.4.4.1-alpha.
1281 - Resolve a compilation warning that could occur in
1282 test_connection.c. Fixes bug 40113; bugfix on 0.2.9.3-alpha.
1284 o Minor bugfixes (configuration):
1285 - Fix bug where %including a pattern ending with */ would include
1286 files and folders (instead of folders only) in versions of glibc <
1287 2.19. Fixes bug 40141; bugfix on 0.4.5.0-alpha-dev. Patch by
1290 o Minor bugfixes (control port):
1291 - Make sure we send the SOCKS request address in relay begin cells
1292 when a stream is attached with the purpose
1293 CIRCUIT_PURPOSE_CONTROLLER. Fixes bug 33124; bugfix on 0.0.5.
1294 Patch by Neel Chauhan.
1296 o Minor bugfixes (logging):
1297 - Remove a debug logging statement that uselessly spammed the logs.
1298 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
1299 - When logging a rate-limited message about how many messages have
1300 been suppressed in the last N seconds, give an accurate value for
1301 N, rounded up to the nearest minute. Previously we would report
1302 the size of the rate-limiting interval, regardless of when the
1303 messages started to occur. Fixes bug 19431; bugfix
1306 o Minor bugfixes (relay configuration, crash):
1307 - Avoid a fatal assert() when failing to create a listener
1308 connection for an address that was in use. Fixes bug 40073; bugfix
1311 o Minor bugfixes (rust, protocol versions):
1312 - Declare support for the onion service introduction point denial of
1313 service extensions when building with Rust. Fixes bug 34248;
1314 bugfix on 0.4.2.1-alpha.
1315 - Make Rust protocol version support checks consistent with the
1316 undocumented error behavior of the corresponding C code. Fixes bug
1317 34251; bugfix on 0.3.3.5-rc.
1319 o Minor bugfixes (self-testing):
1320 - When receiving an incoming circuit, only accept it as evidence
1321 that we are reachable if the declared address of its channel is
1322 the same address we think that we have. Otherwise, it could be
1323 evidence that we're reachable on some other address. Fixes bug
1324 20165; bugfix on 0.1.0.1-rc.
1326 o Minor bugfixes (spec conformance):
1327 - Use the correct key type when generating signing->link
1328 certificates. Fixes bug 40124; bugfix on 0.2.7.2-alpha.
1330 o Minor bugfixes (subprotocol versions):
1331 - Consistently reject extra commas, instead of only rejecting
1332 leading commas. Fixes bug 27194; bugfix on 0.2.9.4-alpha.
1333 - In summarize_protover_flags(), treat empty strings the same as
1334 NULL. This prevents protocols_known from being set. Previously, we
1335 treated empty strings as normal strings, which led to
1336 protocols_known being set. Fixes bug 34232; bugfix on
1337 0.3.3.2-alpha. Patch by Neel Chauhan.
1339 o Minor bugfixes (v2 onion services):
1340 - For HSFETCH commands on v2 onion services addresses, check the
1341 length of bytes decoded, not the base32 length. Fixes bug 34400;
1342 bugfix on 0.4.1.1-alpha. Patch by Neel Chauhan.
1344 o Code simplification and refactoring:
1345 - Add and use a set of functions to perform down-casts on constant
1346 connection and channel pointers. Closes ticket 40046.
1347 - Refactor our code that logs descriptions of connections, channels,
1348 and the peers on them, to use a single call path. This change
1349 enables us to refactor the data types that they use, and eliminates
1350 many confusing usages of those types. Closes ticket 40041.
1351 - Refactor some common node selection code into a single function.
1352 Closes ticket 34200.
1353 - Remove the now-redundant 'outbuf_flushlen' field from our
1354 connection type. It was previously used for an older version of
1355 our rate-limiting logic. Closes ticket 33097.
1356 - Rename "fascist_firewall_*" identifiers to "reachable_addr_*"
1357 instead, for consistency with other code. Closes ticket 18106.
1358 - Rename functions about "advertised" ports which are not in fact
1359 guaranteed to return the ports that have been advertised. Closes
1361 - Split implementation of several command line options from
1362 options_init_from_torrc into smaller isolated functions. Patch by
1363 Daniel Pinto. Closes ticket 40102.
1364 - When an extend cell is missing an IPv4 or IPv6 address, fill in
1365 the address from the extend info. This is similar to what was done
1366 in ticket 33633 for ed25519 keys. Closes ticket 33816. Patch by
1369 o Deprecated features:
1370 - The "non-builtin" argument to the "--dump-config" command is now
1371 deprecated. When it works, it behaves the same as "short", which
1372 you should use instead. Closes ticket 33398.
1375 - Replace URLs from our old bugtracker so that they refer to the new
1376 bugtracker and wiki. Closes ticket 40101.
1379 - We no longer ship or build a "tor.service" file for use with
1380 systemd. No distribution included this script unmodified, and we
1381 don't have the expertise ourselves to maintain this in a way that
1382 all the various systemd-based distributions can use. Closes
1384 - We no longer ship support for the Android logging API. Modern
1385 versions of Android can use the syslog API instead. Closes
1387 - The "optimistic data" feature is now always on; there is no longer
1388 an option to disable it from the torrc file or from the consensus
1389 directory. Closes part of 40139.
1390 - The "usecreatefast" network parameter is now removed; there is no
1391 longer an option for authorities to turn it off. Closes part
1395 - Add unit tests for bandwidth statistics manipulation functions.
1396 Closes ticket 33812. Patch by MrSquanchee.
1398 o Code simplification and refactoring (autoconf):
1399 - Remove autoconf checks for unused funcs and headers. Closes ticket
1400 31699; Patch by @bduszel
1402 o Code simplification and refactoring (maintainer scripts):
1403 - Disable by default the pre-commit hook. Use the environment
1404 variable TOR_EXTRA_PRE_COMMIT_CHECKS in order to run it.
1405 Furthermore, stop running practracker in the pre-commit hook and
1406 make check-local. Closes ticket 40019.
1408 o Code simplification and refactoring (relay address):
1409 - Most of IPv4 representation was using "uint32_t". It has now been
1410 moved to use the internal "tor_addr_t" interface instead. This is
1411 so we can properly integrate IPv6 along IPv4 with common
1412 interfaces. Closes ticket 40043.
1414 o Documentation (manual page):
1415 - Move them from doc/ to doc/man/. Closes ticket 40044.
1416 - Describe the status of the "Sandbox" option more accurately. It is
1417 no longer "experimental", but it _is_ dependent on kernel and libc
1418 versions. Closes ticket 23378.
1420 o Documentation (tracing):
1421 - Document in depth the circuit subsystem trace events in the new
1422 doc/tracing/EventsCircuit.md. Closes ticket 40036.
1425 Changes in version 0.4.4.5 - 2020-09-15
1426 Tor 0.4.4.5 is the first stable release in the 0.4.4.x series. This
1427 series improves our guard selection algorithms, adds v3 onion balance
1428 support, improves the amount of code that can be disabled when running
1429 without relay support, and includes numerous small bugfixes and
1430 enhancements. It also lays the ground for some IPv6 features that
1431 we'll be developing more in the next (0.4.5) series.
1433 Per our support policy, we support each stable release series for nine
1434 months after its first stable release, or three months after the first
1435 stable release of the next series: whichever is longer. This means
1436 that 0.4.4.x will be supported until around June 2021--or later, if
1437 0.4.5.x is later than anticipated.
1439 Note also that support for 0.4.2.x has just ended; support for 0.4.3
1440 will continue until Feb 15, 2021. We still plan to continue supporting
1441 0.3.5.x, our long-term stable series, until Feb 2022.
1443 Below are the changes since 0.4.4.4-rc. For a complete list of changes
1444 since 0.4.3.6, see the ReleaseNotes file.
1446 o Major bugfixes (onion services, DoS):
1447 - Correct handling of parameters for the onion service DoS defense.
1448 Previously, the consensus parameters for the onion service DoS
1449 defenses were overwriting the parameters set by the service
1450 operator using HiddenServiceEnableIntroDoSDefense. Fixes bug
1451 40109; bugfix on 0.4.2.1-alpha.
1453 o Major bugfixes (stats, onion services):
1454 - Fix a bug where we were undercounting the Tor network's total
1455 onion service traffic, by ignoring any traffic originating from
1456 clients. Now we count traffic from both clients and services.
1457 Fixes bug 40117; bugfix on 0.2.6.2-alpha.
1459 o Minor features (control port):
1460 - If a ClientName was specified in ONION_CLIENT_AUTH_ADD for an
1461 onion service, display it when we use ONION_CLIENT_AUTH_VIEW.
1462 Closes ticket 40089. Patch by Neel Chauhan.
1464 o Minor features (denial-of-service memory limiter):
1465 - Allow the user to configure even lower values for the
1466 MaxMemInQueues parameter. Relays now enforce a minimum of 64 MB,
1467 when previously the minimum was 256 MB. On clients, there is no
1468 minimum. Relays and clients will both warn if the value is set so
1469 low that Tor is likely to stop working. Closes ticket 24308.
1471 o Minor features (tests):
1472 - Our "make check" target now runs the unit tests in 8 parallel
1473 chunks. Doing this speeds up hardened CI builds by more than a
1474 factor of two. Closes ticket 40098.
1476 o Minor bugfixes (guard selection algorithm):
1477 - Avoid needless guard-related warning when upgrading from 0.4.3 to
1478 0.4.4. Fixes bug 40105; bugfix on 0.4.4.1-alpha.
1480 o Minor bugfixes (tests):
1481 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
1482 on its own. Previously, it would exit with an error. Fixes bug
1483 40099; bugfix on 0.2.8.1-alpha.
1486 Changes in version 0.4.4.3-alpha - 2020-07-27
1487 Tor 0.4.4.3-alpha fixes several annoyances in previous versions,
1488 including one affecting NSS users, and several affecting the Linux
1491 o Major features (fallback directory list):
1492 - Replace the 148 fallback directories originally included in Tor
1493 0.4.1.4-rc (of which around 105 are still functional) with a list
1494 of 144 fallbacks generated in July 2020. Closes ticket 40061.
1496 o Major bugfixes (NSS):
1497 - When running with NSS enabled, make sure that NSS knows to expect
1498 nonblocking sockets. Previously, we set our TCP sockets as
1499 nonblocking, but did not tell NSS, which in turn could lead to
1500 unexpected blocking behavior. Fixes bug 40035; bugfix
1503 o Minor bugfixes (linux seccomp2 sandbox):
1504 - Fix a regression on sandboxing rules for the openat() syscall. The
1505 fix for bug 25440 fixed the problem on systems with glibc >= 2.27
1506 but broke with versions of glibc. We now choose a rule based on
1507 the glibc version. Patch from Daniel Pinto. Fixes bug 27315;
1509 - Makes the seccomp sandbox allow the correct syscall for opendir
1510 according to the running glibc version. This fixes crashes when
1511 reloading torrc with sandbox enabled when running on glibc 2.15 to
1512 2.21 and 2.26. Patch from Daniel Pinto. Fixes bug 40020; bugfix
1515 o Minor bugfixes (relay, usability):
1516 - Adjust the rules for when to warn about having too many
1517 connections to other relays. Previously we'd tolerate up to 1.5
1518 connections per relay on average. Now we tolerate more connections
1519 for directory authorities, and raise the number of total
1520 connections we need to see before we warn. Fixes bug 33880; bugfix
1524 - Replace most http:// URLs in our code and documentation with
1525 https:// URLs. (We have left unchanged the code in src/ext/, and
1526 the text in LICENSE.) Closes ticket 31812. Patch from Jeremy Rand.
1529 - Our "check-local" test target no longer tries to use the
1530 Coccinelle semantic patching tool parse all the C files. While it
1531 is a good idea to try to make sure Coccinelle works on our C
1532 before we run a Coccinelle patch, doing so on every test run has
1533 proven to be disruptive. You can still run this tool manually with
1534 "make check-cocci". Closes ticket 40030.
1537 Changes in version 0.3.5.11 - 2020-07-09
1538 Tor 0.3.5.11 backports fixes from later tor releases, including several
1539 usability, portability, and reliability fixes.
1541 This release also fixes TROVE-2020-001, a medium-severity denial of
1542 service vulnerability affecting all versions of Tor when compiled with
1543 the NSS encryption library. (This is not the default configuration.)
1544 Using this vulnerability, an attacker could cause an affected Tor
1545 instance to crash remotely. This issue is also tracked as CVE-2020-
1546 15572. Anybody running a version of Tor built with the NSS library
1547 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
1550 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
1551 - Fix a crash due to an out-of-bound memory access when Tor is
1552 compiled with NSS support. Fixes bug 33119; bugfix on
1553 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
1556 o Major bugfixes (DoS defenses, bridges, pluggable transport, backport from 0.4.3.4-rc):
1557 - Fix a bug that was preventing DoS defenses from running on bridges
1558 with a pluggable transport. Previously, the DoS subsystem was not
1559 given the transport name of the client connection, thus failed to
1560 find the GeoIP cache entry for that client address. Fixes bug
1561 33491; bugfix on 0.3.3.2-alpha.
1563 o Minor features (testing, backport from 0.4.3.4-rc):
1564 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
1565 variable to specify a list of space-separated test cases that
1566 should not be executed. We will use this to disable certain tests
1567 that are failing on Appveyor because of mismatched OpenSSL
1568 libraries. Part of ticket 33643.
1570 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
1571 - Use the correct 64-bit printf format when compiling with MINGW on
1572 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
1574 o Minor bugfix (relay, configuration, backport from 0.4.3.3-alpha):
1575 - Warn if the ContactInfo field is not set, and tell the relay
1576 operator that not having a ContactInfo field set might cause their
1577 relay to get rejected in the future. Fixes bug 33361; bugfix
1580 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
1581 - Resume use of preemptively-built circuits when UseEntryGuards is set
1582 to 0. We accidentally disabled this feature with that config
1583 setting, leading to slower load times. Fixes bug 34303; bugfix
1586 o Minor bugfixes (compiler compatibility, backport from 0.4.3.5):
1587 - Avoid compiler warnings from Clang 10 related to the use of GCC-
1588 style "/* falls through */" comments. Both Clang and GCC allow
1589 __attribute__((fallthrough)) instead, so that's what we're using
1590 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
1592 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
1593 - Fix a compiler warning on platforms with 32-bit time_t values.
1594 Fixes bug 40028; bugfix on 0.3.2.8-rc.
1596 o Minor bugfixes (embedded Tor, backport from 0.4.3.1-alpha):
1597 - When starting Tor any time after the first time in a process,
1598 register the thread in which it is running as the main thread.
1599 Previously, we only did this on Windows, which could lead to bugs
1600 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
1603 o Minor bugfixes (key portability, backport from 0.4.3.4-rc):
1604 - When reading PEM-encoded key data, tolerate CRLF line-endings even
1605 if we are not running on Windows. Previously, non-Windows hosts
1606 would reject these line-endings in certain positions, making
1607 certain key files hard to move from one host to another. Fixes bug
1608 33032; bugfix on 0.3.5.1-alpha.
1610 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
1611 - Downgrade a noisy log message that could occur naturally when
1612 receiving an extrainfo document that we no longer want. Fixes bug
1613 16016; bugfix on 0.2.6.3-alpha.
1615 o Minor bugfixes (onion service v3, client, backport from 0.4.3.3-alpha):
1616 - Remove a BUG() warning that would cause a stack trace if an onion
1617 service descriptor was freed while we were waiting for a
1618 rendezvous circuit to complete. Fixes bug 28992; bugfix
1621 o Testing (CI, backport from 0.4.3.4-rc):
1622 - In our Appveyor Windows CI, copy required DLLs to test and app
1623 directories, before running tor's tests. This ensures that tor.exe
1624 and test*.exe use the correct version of each DLL. This fix is not
1625 required, but we hope it will avoid DLL search issues in future.
1626 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
1627 - On Appveyor, skip the crypto/openssl_version test, which is
1628 failing because of a mismatched library installation. Fix
1632 Changes in version 0.4.2.8 - 2020-07-09
1633 Tor 0.4.2.8 backports various fixes from later releases, including
1634 several that affect usability and portability.
1636 This release also fixes TROVE-2020-001, a medium-severity denial of
1637 service vulnerability affecting all versions of Tor when compiled with
1638 the NSS encryption library. (This is not the default configuration.)
1639 Using this vulnerability, an attacker could cause an affected Tor
1640 instance to crash remotely. This issue is also tracked as CVE-2020-
1641 15572. Anybody running a version of Tor built with the NSS library
1642 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
1645 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
1646 - Fix a crash due to an out-of-bound memory access when Tor is
1647 compiled with NSS support. Fixes bug 33119; bugfix on
1648 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
1651 o Major bugfixes (DoS defenses, bridges, pluggable transport, backport from 0.4.3.4-rc):
1652 - Fix a bug that was preventing DoS defenses from running on bridges
1653 with a pluggable transport. Previously, the DoS subsystem was not
1654 given the transport name of the client connection, thus failed to
1655 find the GeoIP cache entry for that client address. Fixes bug
1656 33491; bugfix on 0.3.3.2-alpha.
1658 o Minor feature (sendme, flow control, backport form 0.4.3.4-rc):
1659 - Default to sending SENDME version 1 cells. (Clients are already
1660 sending these, because of a consensus parameter telling them to do
1661 so: this change only affects what clients would do if the
1662 consensus didn't contain a recommendation.) Closes ticket 33623.
1664 o Minor features (diagnostic, backport from 0.4.3.3-alpha):
1665 - Improve assertions and add some memory-poisoning code to try to
1666 track down possible causes of a rare crash (32564) in the EWMA
1667 code. Closes ticket 33290.
1669 o Minor features (testing, backport from 0.4.3.4-rc):
1670 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
1671 variable to specify a list of space-separated test cases that
1672 should not be executed. We will use this to disable certain tests
1673 that are failing on Appveyor because of mismatched OpenSSL
1674 libraries. Part of ticket 33643.
1676 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
1677 - Use the correct 64-bit printf format when compiling with MINGW on
1678 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
1680 o Minor bugfix (relay, configuration, backport from 0.4.3.3-alpha):
1681 - Warn if the ContactInfo field is not set, and tell the relay
1682 operator that not having a ContactInfo field set might cause their
1683 relay to get rejected in the future. Fixes bug 33361; bugfix
1686 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
1687 - Resume use of preemptively-built circuits when UseEntryGuards is set
1688 to 0. We accidentally disabled this feature with that config
1689 setting, leading to slower load times. Fixes bug 34303; bugfix
1692 o Minor bugfixes (compiler compatibility, backport from 0.4.3.5):
1693 - Avoid compiler warnings from Clang 10 related to the use of GCC-
1694 style "/* falls through */" comments. Both Clang and GCC allow
1695 __attribute__((fallthrough)) instead, so that's what we're using
1696 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
1697 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
1700 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
1701 - Fix a compiler warning on platforms with 32-bit time_t values.
1702 Fixes bug 40028; bugfix on 0.3.2.8-rc.
1704 o Minor bugfixes (controller protocol, backport from 0.4.3.2-alpha):
1705 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
1706 report them as SIGNAL events. Previously we would log a bug
1707 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
1709 o Minor bugfixes (embedded Tor, backport from 0.4.3.1-alpha):
1710 - When starting Tor any time after the first time in a process,
1711 register the thread in which it is running as the main thread.
1712 Previously, we only did this on Windows, which could lead to bugs
1713 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
1716 o Minor bugfixes (key portability, backport from 0.4.3.4-rc):
1717 - When reading PEM-encoded key data, tolerate CRLF line-endings even
1718 if we are not running on Windows. Previously, non-Windows hosts
1719 would reject these line-endings in certain positions, making
1720 certain key files hard to move from one host to another. Fixes bug
1721 33032; bugfix on 0.3.5.1-alpha.
1723 o Minor bugfixes (logging, backport from 0.4.3.2-rc):
1724 - When logging a bug, do not say "Future instances of this warning
1725 will be silenced" unless we are actually going to silence them.
1726 Previously we would say this whenever a BUG() check failed in the
1727 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
1729 o Minor bugfixes (logging, backport from 0.4.3.4-rc):
1730 - Flush stderr, stdout, and file logs during shutdown, if supported
1731 by the OS. This change helps make sure that any final logs are
1732 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
1734 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
1735 - Downgrade a noisy log message that could occur naturally when
1736 receiving an extrainfo document that we no longer want. Fixes bug
1737 16016; bugfix on 0.2.6.3-alpha.
1739 o Minor bugfixes (onion service v3, client, backport from 0.4.3.3-alpha):
1740 - Remove a BUG() warning that would cause a stack trace if an onion
1741 service descriptor was freed while we were waiting for a
1742 rendezvous circuit to complete. Fixes bug 28992; bugfix
1745 o Testing (CI, backport from 0.4.3.4-rc):
1746 - In our Appveyor Windows CI, copy required DLLs to test and app
1747 directories, before running tor's tests. This ensures that tor.exe
1748 and test*.exe use the correct version of each DLL. This fix is not
1749 required, but we hope it will avoid DLL search issues in future.
1750 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
1751 - On Appveyor, skip the crypto/openssl_version test, which is
1752 failing because of a mismatched library installation. Fix
1756 Changes in version 0.4.3.6 - 2020-07-09
1757 Tor 0.4.3.6 backports several bugfixes from later releases, including
1758 some affecting usability.
1760 This release also fixes TROVE-2020-001, a medium-severity denial of
1761 service vulnerability affecting all versions of Tor when compiled with
1762 the NSS encryption library. (This is not the default configuration.)
1763 Using this vulnerability, an attacker could cause an affected Tor
1764 instance to crash remotely. This issue is also tracked as CVE-2020-
1765 15572. Anybody running a version of Tor built with the NSS library
1766 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
1769 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
1770 - Fix a crash due to an out-of-bound memory access when Tor is
1771 compiled with NSS support. Fixes bug 33119; bugfix on
1772 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
1775 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
1776 - Use the correct 64-bit printf format when compiling with MINGW on
1777 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
1779 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
1780 - Resume use of preemptively-built circuits when UseEntryGuards is set
1781 to 0. We accidentally disabled this feature with that config
1782 setting, leading to slower load times. Fixes bug 34303; bugfix
1785 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
1786 - Fix a compiler warning on platforms with 32-bit time_t values.
1787 Fixes bug 40028; bugfix on 0.3.2.8-rc.
1789 o Minor bugfixes (linux seccomp sandbox, nss, backport from 0.4.4.1-alpha):
1790 - Fix a startup crash when tor is compiled with --enable-nss and
1791 sandbox support is enabled. Fixes bug 34130; bugfix on
1792 0.3.5.1-alpha. Patch by Daniel Pinto.
1794 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
1795 - Downgrade a noisy log message that could occur naturally when
1796 receiving an extrainfo document that we no longer want. Fixes bug
1797 16016; bugfix on 0.2.6.3-alpha.
1799 o Minor bugfixes (manual page, backport from 0.4.4.1-alpha):
1800 - Update the man page to reflect that MinUptimeHidServDirectoryV2
1801 defaults to 96 hours. Fixes bug 34299; bugfix on 0.2.6.3-alpha.
1803 o Minor bugfixes (onion service v3, backport from 0.4.4.1-alpha):
1804 - Prevent an assert() that would occur when cleaning the client
1805 descriptor cache, and attempting to close circuits for a non-
1806 decrypted descriptor (lacking client authorization). Fixes bug
1807 33458; bugfix on 0.4.2.1-alpha.
1809 o Minor bugfixes (portability, backport from 0.4.4.1-alpha):
1810 - Fix a portability error in the configure script, where we were
1811 using "==" instead of "=". Fixes bug 34233; bugfix on 0.4.3.5.
1813 o Minor bugfixes (relays, backport from 0.4.4.1-alpha):
1814 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
1815 descriptors, when the IPv6 port was configured as "auto". Fixes
1816 bug 32588; bugfix on 0.2.3.9-alpha.
1818 o Documentation (backport from 0.4.4.1-alpha):
1819 - Fix several doxygen warnings related to imbalanced groups. Closes
1823 Changes in version 0.4.4.2-alpha - 2020-07-09
1824 This is the second alpha release in the 0.4.4.x series. It fixes a few
1825 bugs in the previous release, and solves a few usability,
1826 compatibility, and portability issues.
1828 This release also fixes TROVE-2020-001, a medium-severity denial of
1829 service vulnerability affecting all versions of Tor when compiled with
1830 the NSS encryption library. (This is not the default configuration.)
1831 Using this vulnerability, an attacker could cause an affected Tor
1832 instance to crash remotely. This issue is also tracked as CVE-2020-
1833 15572. Anybody running a version of Tor built with the NSS library
1834 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
1837 o Major bugfixes (NSS, security):
1838 - Fix a crash due to an out-of-bound memory access when Tor is
1839 compiled with NSS support. Fixes bug 33119; bugfix on
1840 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
1843 o Minor features (bootstrap reporting):
1844 - Report more detailed reasons for bootstrap failure when the
1845 failure happens due to a TLS error. Previously we would just call
1846 these errors "MISC" when they happened during read, and "DONE"
1847 when they happened during any other TLS operation. Closes
1850 o Minor features (directory authority):
1851 - Authorities now recommend the protocol versions that are supported
1852 by Tor 0.3.5 and later. (Earlier versions of Tor have been
1853 deprecated since January of this year.) This recommendation will
1854 cause older clients and relays to give a warning on startup, or
1855 when they download a consensus directory. Closes ticket 32696.
1857 o Minor features (entry guards):
1858 - Reinstate support for GUARD NEW/UP/DOWN control port events.
1859 Closes ticket 40001.
1861 o Minor features (linux seccomp2 sandbox, portability):
1862 - Allow Tor to build on platforms where it doesn't know how to
1863 report which syscall caused the linux seccomp2 sandbox to fail.
1864 This change should make the sandbox code more portable to less
1865 common Linux architectures. Closes ticket 34382.
1866 - Permit the unlinkat() syscall, which some Libc implementations use
1867 to implement unlink(). Closes ticket 33346.
1869 o Minor bugfix (CI, Windows):
1870 - Use the correct 64-bit printf format when compiling with MINGW on
1871 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
1873 o Minor bugfix (onion service v3 client):
1874 - Remove a BUG() warning that could occur naturally. Fixes bug
1875 34087; bugfix on 0.3.2.1-alpha.
1877 o Minor bugfix (SOCKS, onion service client):
1878 - Detect v3 onion service addresses of the wrong length when
1879 returning the F6 ExtendedErrors code. Fixes bug 33873; bugfix
1882 o Minor bugfixes (compiler warnings):
1883 - Fix a compiler warning on platforms with 32-bit time_t values.
1884 Fixes bug 40028; bugfix on 0.3.2.8-rc.
1886 o Minor bugfixes (control port, onion service):
1887 - Consistently use 'address' in "Invalid v3 address" response to
1888 ONION_CLIENT_AUTH commands. Previously, we would sometimes say
1889 'addr'. Fixes bug 40005; bugfix on 0.4.3.1-alpha.
1891 o Minor bugfixes (logging):
1892 - Downgrade a noisy log message that could occur naturally when
1893 receiving an extrainfo document that we no longer want. Fixes bug
1894 16016; bugfix on 0.2.6.3-alpha.
1896 o Minor bugfixes (onion services v3):
1897 - Avoid a non-fatal assertion failure in certain edge-cases when
1898 opening an intro circuit as a client. Fixes bug 34084; bugfix
1901 o Deprecated features (onion service v2):
1902 - Add a deprecation warning for version 2 onion services. Closes
1905 o Removed features (IPv6, revert):
1906 - Revert the change in the default value of ClientPreferIPv6OrPort:
1907 it breaks the torsocks use case. The SOCKS resolve command has no
1908 mechanism to ask for a specific address family (v4 or v6), and so
1909 prioritizing IPv6 when an IPv4 address is requested on the SOCKS
1910 interface resulted in a failure. Tor Browser explicitly sets
1911 PreferIPv6, so this should not affect the majority of our users.
1912 Closes ticket 33796; bugfix on 0.4.4.1-alpha.
1915 Changes in version 0.4.4.1-alpha - 2020-06-16
1916 This is the first alpha release in the 0.4.4.x series. It improves
1917 our guard selection algorithms, improves the amount of code that
1918 can be disabled when running without relay support, and includes numerous
1919 small bugfixes and enhancements. It also lays the ground for some IPv6
1920 features that we'll be developing more in the next (0.4.5) series.
1922 Here are the changes since 0.4.3.5.
1924 o Major features (Proposal 310, performance + security):
1925 - Implements Proposal 310, "Bandaid on guard selection". Proposal
1926 310 solves load-balancing issues with older versions of the guard
1927 selection algorithm, and improves its security. Under this new
1928 algorithm, a newly selected guard never becomes Primary unless all
1929 previously sampled guards are unreachable. Implements
1930 recommendation from 32088. (Proposal 310 is linked to the CLAPS
1931 project researching optimal client location-aware path selections.
1932 This project is a collaboration between the UCLouvain Crypto Group,
1933 the U.S. Naval Research Laboratory, and Princeton University.)
1935 o Major features (IPv6, relay):
1936 - Consider IPv6-only EXTEND2 cells valid on relays. Log a protocol
1937 warning if the IPv4 or IPv6 address is an internal address, and
1938 internal addresses are not allowed. But continue to use the other
1939 address, if it is valid. Closes ticket 33817.
1940 - If a relay can extend over IPv4 and IPv6, and both addresses are
1941 provided, it chooses between them uniformly at random. Closes
1943 - Re-use existing IPv6 connections for circuit extends. Closes
1945 - Relays may extend circuits over IPv6, if the relay has an IPv6
1946 ORPort, and the client supplies the other relay's IPv6 ORPort in
1947 the EXTEND2 cell. IPv6 extends will be used by the relay IPv6
1948 ORPort self-tests in 33222. Closes ticket 33817.
1950 o Major features (v3 onion services):
1951 - Allow v3 onion services to act as OnionBalance backend instances,
1952 by using the HiddenServiceOnionBalanceInstance torrc option.
1953 Closes ticket 32709.
1955 o Minor feature (developer tools):
1956 - Add a script to help check the alphabetical ordering of option
1957 names in the manual page. Closes ticket 33339.
1959 o Minor feature (onion service client, SOCKS5):
1960 - Add 3 new SocksPort ExtendedErrors (F2, F3, F7) that reports back
1961 new type of onion service connection failures. The semantics of
1962 these error codes are documented in proposal 309. Closes
1965 o Minor feature (onion service v3):
1966 - If a service cannot upload its descriptor(s), log why at INFO
1967 level. Closes ticket 33400; bugfix on 0.3.2.1-alpha.
1969 o Minor feature (python scripts):
1970 - Stop assuming that /usr/bin/python exists. Instead of using a
1971 hardcoded path in scripts that still use Python 2, use
1972 /usr/bin/env, similarly to the scripts that use Python 3. Fixes
1973 bug 33192; bugfix on 0.4.2.
1975 o Minor features (client-only compilation):
1976 - Disable more code related to the ext_orport protocol when
1977 compiling without support for relay mode. Closes ticket 33368.
1978 - Disable more of our self-testing code when support for relay mode
1979 is disabled. Closes ticket 33370.
1981 o Minor features (code safety):
1982 - Check for failures of tor_inet_ntop() and tor_inet_ntoa()
1983 functions in DNS and IP address processing code, and adjust
1984 codepaths to make them less likely to crash entire Tor instances.
1985 Resolves issue 33788.
1987 o Minor features (compilation size):
1988 - Most server-side DNS code is now disabled when building without
1989 support for relay mode. Closes ticket 33366.
1991 o Minor features (continuous integration):
1992 - Run unit-test and integration test (Stem, Chutney) jobs with
1993 ALL_BUGS_ARE_FATAL macro being enabled on Travis and Appveyor.
1994 Resolves ticket 32143.
1996 o Minor features (control port):
1997 - Return a descriptive error message from the 'GETINFO status/fresh-
1998 relay-descs' command on the control port. Previously, we returned
1999 a generic error of "Error generating descriptor". Closes ticket
2000 32873. Patch by Neel Chauhan.
2002 o Minor features (developer tooling):
2003 - Refrain from listing all .a files that are generated by the Tor
2004 build in .gitignore. Add a single wildcard *.a entry that covers
2005 all of them for present and future. Closes ticket 33642.
2006 - Add a script ("git-install-tools.sh") to install git hooks and
2007 helper scripts. Closes ticket 33451.
2009 o Minor features (directory authority, shared random):
2010 - Refactor more authority-only parts of the shared-random scheduling
2011 code to reside in the dirauth module, and to be disabled when
2012 compiling with --disable-module-dirauth. Closes ticket 33436.
2014 o Minor features (directory):
2015 - Remember the number of bytes we have downloaded for each directory
2016 purpose while bootstrapping, and while fully bootstrapped. Log
2017 this information as part of the heartbeat message. Closes
2020 o Minor features (IPv6 support):
2021 - Adds IPv6 support to tor_addr_is_valid(). Adds tests for the above
2022 changes and tor_addr_is_null(). Closes ticket 33679. Patch
2024 - Allow clients and relays to send dual-stack and IPv6-only EXTEND2
2025 cells. Parse dual-stack and IPv6-only EXTEND2 cells on relays.
2026 Closes ticket 33901.
2028 o Minor features (logging):
2029 - When trying to find our own address, add debug-level logging to
2030 report the sources of candidate addresses. Closes ticket 32888.
2032 o Minor features (testing, architecture):
2033 - Our test scripts now double-check that subsystem initialization
2034 order is consistent with the inter-module dependencies established
2035 by our .may_include files. Implements ticket 31634.
2036 - Initialize all subsystems at the beginning of our unit test
2037 harness, to avoid crashes due to uninitialized subsystems. Follow-
2038 up from ticket 33316.
2040 o Minor features (v3 onion services):
2041 - Add v3 onion service status to the dumpstats() call which is
2042 triggered by a SIGUSR1 signal. Previously, we only did v2 onion
2043 services. Closes ticket 24844. Patch by Neel Chauhan.
2045 o Minor features (windows):
2046 - Add support for console control signals like Ctrl+C in Windows.
2047 Closes ticket 34211. Patch from Damon Harris (TheDcoder).
2049 o Minor bugfix (onion service v3):
2050 - Prevent an assert() that would occur when cleaning the client
2051 descriptor cache, and attempting to close circuits for a non-
2052 decrypted descriptor (lacking client authorization). Fixes bug
2053 33458; bugfix on 0.4.2.1-alpha.
2055 o Minor bugfix (refactoring):
2056 - Lift circuit_build_times_disabled() out of the
2057 circuit_expire_building() loop, to save CPU time when there are
2058 many circuits open. Fixes bug 33977; bugfix on 0.3.5.9.
2060 o Minor bugfixes (client performance):
2061 - Resume use of preemptively-built circuits when UseEntryGuards is set
2062 to 0. We accidentally disabled this feature with that config
2063 setting, leading to slower load times. Fixes bug 34303; bugfix
2066 o Minor bugfixes (directory authorities):
2067 - Directory authorities now reject votes that arrive too late. In
2068 particular, once an authority has started fetching missing votes,
2069 it no longer accepts new votes posted by other authorities. This
2070 change helps prevent a consensus split, where only some authorities
2071 have the late vote. Fixes bug 4631; bugfix on 0.2.0.5-alpha.
2073 o Minor bugfixes (git scripts):
2074 - Stop executing the checked-out pre-commit hook from the pre-push
2075 hook. Instead, execute the copy in the user's git directory. Fixes
2076 bug 33284; bugfix on 0.4.1.1-alpha.
2078 o Minor bugfixes (initialization):
2079 - Initialize the subsystems in our code in an order more closely
2080 corresponding to their dependencies, so that every system is
2081 initialized before the ones that (theoretically) depend on it.
2082 Fixes bug 33316; bugfix on 0.4.0.1-alpha.
2084 o Minor bugfixes (IPv4, relay):
2085 - Check for invalid zero IPv4 addresses and ports when sending and
2086 receiving extend cells. Fixes bug 33900; bugfix on 0.2.4.8-alpha.
2088 o Minor bugfixes (IPv6, relay):
2089 - Consider IPv6 addresses when checking if a connection is
2090 canonical. In 17604, relays assumed that a remote relay could
2091 consider an IPv6 connection canonical, but did not set the
2092 canonical flag on their side of the connection. Fixes bug 33899;
2093 bugfix on 0.3.1.1-alpha.
2094 - Log IPv6 addresses on connections where this relay is the
2095 responder. Previously, responding relays would replace the remote
2096 IPv6 address with the IPv4 address from the consensus. Fixes bug
2097 33899; bugfix on 0.3.1.1-alpha.
2099 o Minor bugfixes (linux seccomp sandbox nss):
2100 - Fix a startup crash when tor is compiled with --enable-nss and
2101 sandbox support is enabled. Fixes bug 34130; bugfix on
2102 0.3.5.1-alpha. Patch by Daniel Pinto.
2104 o Minor bugfixes (logging, testing):
2105 - Make all of tor's assertion macros support the ALL_BUGS_ARE_FATAL
2106 and DISABLE_ASSERTS_IN_UNIT_TESTS debugging modes. (IF_BUG_ONCE()
2107 used to log a non-fatal warning, regardless of the debugging
2108 mode.) Fixes bug 33917; bugfix on 0.2.9.1-alpha.
2110 o Minor bugfixes (logs):
2111 - Remove surprising empty line in the INFO-level log about circuit
2112 build timeout. Fixes bug 33531; bugfix on 0.3.3.1-alpha.
2114 o Minor bugfixes (mainloop):
2115 - Better guard against growing a buffer past its maximum 2GB in
2116 size. Fixes bug 33131; bugfix on 0.3.0.4-rc.
2118 o Minor bugfixes (manual page):
2119 - Update the man page to reflect that MinUptimeHidServDirectoryV2
2120 defaults to 96 hours. Fixes bug 34299; bugfix on 0.2.6.3-alpha.
2122 o Minor bugfixes (onion service v3, client):
2123 - Remove a BUG() that was causing a stacktrace when a descriptor
2124 changed at an unexpected time. Fixes bug 28992; bugfix
2127 o Minor bugfixes (onion service, logging):
2128 - Fix a typo in a log message PublishHidServDescriptors is set to 0.
2129 Fixes bug 33779; bugfix on 0.3.2.1-alpha.
2131 o Minor bugfixes (portability):
2132 - Fix a portability error in the configure script, where we were
2133 using "==" instead of "=". Fixes bug 34233; bugfix on 0.4.3.5.
2135 o Minor bugfixes (protocol versions):
2136 - Sort tor's supported protocol version lists, as recommended by the
2137 tor directory specification. Fixes bug 33285; bugfix
2140 o Minor bugfixes (relays):
2141 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
2142 descriptors, when the IPv6 port was configured as "auto". Fixes
2143 bug 32588; bugfix on 0.2.3.9-alpha.
2145 o Code simplification and refactoring:
2146 - Define and use a new constant TOR_ADDRPORT_BUF_LEN which is like
2147 TOR_ADDR_BUF_LEN but includes enough space for an IP address,
2148 brackets, separating colon, and port number. Closes ticket 33956.
2149 Patch by Neel Chauhan.
2150 - Merge the orconn and ocirc events into the "core" subsystem, which
2151 manages or connections and origin circuits. Previously they were
2152 isolated in subsystems of their own.
2153 - Move LOG_PROTOCOL_WARN to app/config. Resolves a dependency
2154 inversion. Closes ticket 33633.
2155 - Move the circuit extend code to the relay module. Split the
2156 circuit extend function into smaller functions. Closes
2158 - Rewrite port_parse_config() to use the default port flags from
2159 port_cfg_new(). Closes ticket 32994. Patch by MrSquanchee.
2160 - Updated comments in 'scheduler.c' to reflect old code changes, and
2161 simplified the scheduler channel state change code. Closes
2165 - Document the limitations of using %include on config files with
2166 seccomp sandbox enabled. Fixes documentation bug 34133; bugfix on
2167 0.3.1.1-alpha. Patch by Daniel Pinto.
2168 - Fix several doxygen warnings related to imbalanced groups. Closes
2172 - Remove the ClientAutoIPv6ORPort option. This option attempted to
2173 randomly choose between IPv4 and IPv6 for client connections, and
2174 wasn't a true implementation of Happy Eyeballs. Often, this option
2175 failed on IPv4-only or IPv6-only connections. Closes ticket 32905.
2176 Patch by Neel Chauhan.
2177 - Stop shipping contrib/dist/rc.subr file, as it is not being used
2178 on FreeBSD anymore. Closes issue 31576.
2181 - Add a basic IPv6 test to "make test-network". This test only runs
2182 when the local machine has an IPv6 stack. Closes ticket 33300.
2183 - Add test-network-ipv4 and test-network-ipv6 jobs to the Makefile.
2184 These jobs run the IPv4-only and dual-stack chutney flavours from
2185 test-network-all. Closes ticket 33280.
2186 - Remove a redundant distcheck job. Closes ticket 33194.
2187 - Run the test-network-ipv6 Makefile target in the Travis CI IPv6
2188 chutney job. This job runs on macOS, so it's a bit slow. Closes
2190 - Sort the Travis jobs in order of speed. Putting the slowest jobs
2191 first takes full advantage of Travis job concurrency. Closes
2193 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2194 previously configured to fast_finish (which requires
2195 allow_failure), to speed up the build. Closes ticket 33195.
2196 - Test v3 onion services to tor's mixed IPv4 chutney network. And
2197 add a mixed IPv6 chutney network. These networks are used in the
2198 test-network-all, test-network-ipv4, and test-network-ipv6 make
2199 targets. Closes ticket 33334.
2200 - Use the "bridges+hs-v23" chutney network flavour in "make test-
2201 network". This test requires a recent version of chutney (mid-
2202 February 2020). Closes ticket 28208.
2203 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2204 tool to produce detailed diagnostic output. Closes ticket 32792.
2206 o Code simplification and refactoring (onion service):
2207 - Refactor configuration parsing to use the new config subsystem
2208 code. Closes ticket 33014.
2210 o Code simplification and refactoring (relay address):
2211 - Move a series of functions related to address resolving into their
2212 own files. Closes ticket 33789.
2214 o Documentation (manual page):
2215 - Add cross reference links and a table of contents to the HTML tor
2216 manual page. Closes ticket 33369. Work by Swati Thacker as part of
2217 Google Season of Docs.
2218 - Alphabetize the Denial of Service Mitigation Options, Directory
2219 Authority Server Options, Hidden Service Options, and Testing
2220 Network Options sections of the tor(1) manual page. Closes ticket
2221 33275. Work by Swati Thacker as part of Google Season of Docs.
2222 - Refrain from mentioning nicknames in manpage section for MyFamily
2223 torrc option. Resolves issue 33417.
2224 - Updated the options set by TestingTorNetwork in the manual page.
2225 Closes ticket 33778.
2228 Changes in version 0.4.3.5 - 2020-05-15
2229 Tor 0.4.3.5 is the first stable release in the 0.4.3.x series. This
2230 series adds support for building without relay code enabled, and
2231 implements functionality needed for OnionBalance with v3 onion
2232 services. It includes significant refactoring of our configuration and
2233 controller functionality, and fixes numerous smaller bugs and
2236 Per our support policy, we support each stable release series for nine
2237 months after its first stable release, or three months after the first
2238 stable release of the next series: whichever is longer. This means
2239 that 0.4.3.x will be supported until around February 2021--later, if
2240 0.4.4.x is later than anticipated.
2242 Note also that support for 0.4.1.x is about to end on May 20 of this
2243 year; 0.4.2.x will be supported until September 15. We still plan to
2244 continue supporting 0.3.5.x, our long-term stable series, until
2247 Below are the changes since 0.4.3.4-rc. For a complete list of changes
2248 since 0.4.2.6, see the ReleaseNotes file.
2250 o Minor bugfixes (compiler compatibility):
2251 - Avoid compiler warnings from Clang 10 related to the use of GCC-
2252 style "/* falls through */" comments. Both Clang and GCC allow
2253 __attribute__((fallthrough)) instead, so that's what we're using
2254 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
2255 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
2258 o Minor bugfixes (logging):
2259 - Stop truncating IPv6 addresses and ports in channel and connection
2260 logs. Fixes bug 33918; bugfix on 0.2.4.4-alpha.
2261 - Fix a logic error in a log message about whether an address was
2262 invalid. Previously, the code would never report that onion
2263 addresses were onion addresses. Fixes bug 34131; bugfix
2267 Changes in version 0.4.3.4-rc - 2020-04-13
2268 Tor 0.4.3.4-rc is the first release candidate in its series. It fixes
2269 several bugs from earlier versions, including one affecting DoS
2270 defenses on bridges using pluggable transports.
2272 o Major bugfixes (DoS defenses, bridges, pluggable transport):
2273 - Fix a bug that was preventing DoS defenses from running on bridges
2274 with a pluggable transport. Previously, the DoS subsystem was not
2275 given the transport name of the client connection, thus failed to
2276 find the GeoIP cache entry for that client address. Fixes bug
2277 33491; bugfix on 0.3.3.2-alpha.
2279 o Minor feature (sendme, flow control):
2280 - Default to sending SENDME version 1 cells. (Clients are already
2281 sending these, because of a consensus parameter telling them to do
2282 so: this change only affects what clients would do if the
2283 consensus didn't contain a recommendation.) Closes ticket 33623.
2285 o Minor features (testing):
2286 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
2287 variable to specify a list of space-separated test cases that
2288 should not be executed. We will use this to disable certain tests
2289 that are failing on Appveyor because of mismatched OpenSSL
2290 libraries. Part of ticket 33643.
2292 o Minor bugfixes (--disable-module-relay):
2293 - Fix an assertion failure when Tor is built without the relay
2294 module, and then invoked with the "User" option. Fixes bug 33668;
2295 bugfix on 0.4.3.1-alpha.
2297 o Minor bugfixes (--disable-module-relay,--disable-module-dirauth):
2298 - Set some output arguments in the relay and dirauth module stubs,
2299 to guard against future stub argument handling bugs like 33668.
2300 Fixes bug 33674; bugfix on 0.4.3.1-alpha.
2302 o Minor bugfixes (build system):
2303 - Correctly output the enabled module in the configure summary.
2304 Before that, the list shown was just plain wrong. Fixes bug 33646;
2305 bugfix on 0.4.3.2-alpha.
2307 o Minor bugfixes (client, IPv6):
2308 - Stop forcing all non-SocksPorts to prefer IPv6 exit connections.
2309 Instead, prefer IPv6 connections by default, but allow users to
2310 change their configs using the "NoPreferIPv6" port flag. Fixes bug
2311 33608; bugfix on 0.4.3.1-alpha.
2312 - Revert PreferIPv6 set by default on the SocksPort because it broke
2313 the torsocks use case. Tor doesn't have a way for an application
2314 to request the hostname to be resolved for a specific IP version,
2315 but torsocks requires that. Up until now, IPv4 was used by default
2316 so torsocks is expecting that, and can't handle a possible IPv6
2317 being returned. Fixes bug 33804; bugfix on 0.4.3.1-alpha.
2319 o Minor bugfixes (key portability):
2320 - When reading PEM-encoded key data, tolerate CRLF line-endings even
2321 if we are not running on Windows. Previously, non-Windows hosts
2322 would reject these line-endings in certain positions, making
2323 certain key files hard to move from one host to another. Fixes bug
2324 33032; bugfix on 0.3.5.1-alpha.
2326 o Minor bugfixes (logging):
2327 - Flush stderr, stdout, and file logs during shutdown, if supported
2328 by the OS. This change helps make sure that any final logs are
2329 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
2330 - Stop closing stderr and stdout during shutdown. Closing these file
2331 descriptors can hide sanitiser logs. Fixes bug 33087; bugfix
2334 o Minor bugfixes (onion services v3):
2335 - Relax severity of a log message that can appear naturally when
2336 decoding onion service descriptors as a relay. Also add some
2337 diagnostics to debug any future bugs in that area. Fixes bug
2338 31669; bugfix on 0.3.0.1-alpha.
2339 - Block a client-side assertion by disallowing the registration of
2340 an x25519 client auth key that's all zeroes. Fixes bug 33545;
2341 bugfix on 0.4.3.1-alpha. Based on patch from "cypherpunks".
2343 o Code simplification and refactoring:
2344 - Disable our coding standards best practices tracker in our git
2345 hooks. (0.4.3 branches only.) Closes ticket 33678.
2348 - Avoid conflicts between the fake sockets in tor's unit tests, and
2349 real file descriptors. Resolves issues running unit tests with
2350 GitHub Actions, where the process that embeds or launches the
2351 tests has already opened a large number of file descriptors. Fixes
2352 bug 33782; bugfix on 0.2.8.1-alpha. Found and fixed by
2356 - In our Appveyor Windows CI, copy required DLLs to test and app
2357 directories, before running tor's tests. This ensures that tor.exe
2358 and test*.exe use the correct version of each DLL. This fix is not
2359 required, but we hope it will avoid DLL search issues in future.
2360 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
2361 - On Appveyor, skip the crypto/openssl_version test, which is
2362 failing because of a mismatched library installation. Fix
2366 Changes in version 0.4.3.3-alpha - 2020-03-18
2367 Tor 0.4.3.3-alpha fixes several bugs in previous releases, including
2368 TROVE-2020-002, a major denial-of-service vulnerability that affected
2369 all released Tor instances since 0.2.1.5-alpha. Using this
2370 vulnerability, an attacker could cause Tor instances to consume a huge
2371 amount of CPU, disrupting their operations for several seconds or
2372 minutes. This attack could be launched by anybody against a relay, or
2373 by a directory cache against any client that had connected to it. The
2374 attacker could launch this attack as much as they wanted, thereby
2375 disrupting service or creating patterns that could aid in traffic
2376 analysis. This issue was found by OSS-Fuzz, and is also tracked
2379 We do not have reason to believe that this attack is currently being
2380 exploited in the wild, but nonetheless we advise everyone to upgrade
2381 as soon as packages are available.
2383 o Major bugfixes (security, denial-of-service):
2384 - Fix a denial-of-service bug that could be used by anyone to
2385 consume a bunch of CPU on any Tor relay or authority, or by
2386 directories to consume a bunch of CPU on clients or hidden
2387 services. Because of the potential for CPU consumption to
2388 introduce observable timing patterns, we are treating this as a
2389 high-severity security issue. Fixes bug 33119; bugfix on
2390 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
2391 as TROVE-2020-002 and CVE-2020-10592.
2393 o Major bugfixes (circuit padding, memory leak):
2394 - Avoid a remotely triggered memory leak in the case that a circuit
2395 padding machine is somehow negotiated twice on the same circuit.
2396 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
2397 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
2399 o Major bugfixes (directory authority):
2400 - Directory authorities will now send a 503 (not enough bandwidth)
2401 code to clients when under bandwidth pressure. Known relays and
2402 other authorities will always be answered regardless of the
2403 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
2405 o Minor features (diagnostic):
2406 - Improve assertions and add some memory-poisoning code to try to
2407 track down possible causes of a rare crash (32564) in the EWMA
2408 code. Closes ticket 33290.
2410 o Minor features (directory authorities):
2411 - Directory authorities now reject descriptors from relays running
2412 Tor versions from the 0.2.9 and 0.4.0 series. The 0.3.5 series is
2413 still allowed. Resolves ticket 32672. Patch by Neel Chauhan.
2415 o Minor features (usability):
2416 - Include more information when failing to parse a configuration
2417 value. This should make it easier to tell what's going wrong when
2418 a configuration file doesn't parse. Closes ticket 33460.
2420 o Minor bugfix (relay, configuration):
2421 - Warn if the ContactInfo field is not set, and tell the relay
2422 operator that not having a ContactInfo field set might cause their
2423 relay to get rejected in the future. Fixes bug 33361; bugfix
2426 o Minor bugfixes (coding best practices checks):
2427 - Allow the "practracker" script to read unicode files when using
2428 Python 2. We made the script use unicode literals in 0.4.3.1-alpha,
2429 but didn't change the codec for opening files. Fixes bug 33374;
2430 bugfix on 0.4.3.1-alpha.
2432 o Minor bugfixes (continuous integration):
2433 - Remove the buggy and unused mirroring job. Fixes bug 33213; bugfix
2436 o Minor bugfixes (onion service v3, client):
2437 - Remove a BUG() warning that would cause a stack trace if an onion
2438 service descriptor was freed while we were waiting for a
2439 rendezvous circuit to complete. Fixes bug 28992; bugfix
2442 o Minor bugfixes (onion services v3):
2443 - Fix an assertion failure that could result from a corrupted
2444 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
2445 bugfix on 0.3.3.1-alpha. This issue is also tracked
2448 o Documentation (manpage):
2449 - Alphabetize the Server and Directory server sections of the tor
2450 manpage. Also split Statistics options into their own section of
2451 the manpage. Closes ticket 33188. Work by Swati Thacker as part of
2452 Google Season of Docs.
2453 - Document the __OwningControllerProcess torrc option and specify
2454 its polling interval. Resolves issue 32971.
2456 o Testing (Travis CI):
2457 - Remove a redundant distcheck job. Closes ticket 33194.
2458 - Sort the Travis jobs in order of speed: putting the slowest jobs
2459 first takes full advantage of Travis job concurrency. Closes
2461 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2462 previously configured to fast_finish (which requires
2463 allow_failure), to speed up the build. Closes ticket 33195.
2464 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2465 tool to produce detailed diagnostic output. Closes ticket 32792.
2468 Changes in version 0.4.2.7 - 2020-03-18
2469 This is the third stable release in the 0.4.2.x series. It backports
2470 numerous fixes from later releases, including a fix for TROVE-2020-
2471 002, a major denial-of-service vulnerability that affected all
2472 released Tor instances since 0.2.1.5-alpha. Using this vulnerability,
2473 an attacker could cause Tor instances to consume a huge amount of CPU,
2474 disrupting their operations for several seconds or minutes. This
2475 attack could be launched by anybody against a relay, or by a directory
2476 cache against any client that had connected to it. The attacker could
2477 launch this attack as much as they wanted, thereby disrupting service
2478 or creating patterns that could aid in traffic analysis. This issue
2479 was found by OSS-Fuzz, and is also tracked as CVE-2020-10592.
2481 We do not have reason to believe that this attack is currently being
2482 exploited in the wild, but nonetheless we advise everyone to upgrade
2483 as soon as packages are available.
2485 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
2486 - Fix a denial-of-service bug that could be used by anyone to
2487 consume a bunch of CPU on any Tor relay or authority, or by
2488 directories to consume a bunch of CPU on clients or hidden
2489 services. Because of the potential for CPU consumption to
2490 introduce observable timing patterns, we are treating this as a
2491 high-severity security issue. Fixes bug 33119; bugfix on
2492 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
2493 as TROVE-2020-002 and CVE-2020-10592.
2495 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
2496 - Avoid a remotely triggered memory leak in the case that a circuit
2497 padding machine is somehow negotiated twice on the same circuit.
2498 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
2499 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
2501 o Major bugfixes (directory authority, backport from 0.4.3.3-alpha):
2502 - Directory authorities will now send a 503 (not enough bandwidth)
2503 code to clients when under bandwidth pressure. Known relays and
2504 other authorities will always be answered regardless of the
2505 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
2507 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
2508 - Stop allowing failures on the Travis CI stem tests job. It looks
2509 like all the stem hangs we were seeing before are now fixed.
2510 Closes ticket 33075.
2512 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
2513 - Lowercase the configured value of BridgeDistribution before adding
2514 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
2516 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
2517 - If we encounter a bug when flushing a buffer to a TLS connection,
2518 only log the bug once per invocation of the Tor process.
2519 Previously we would log with every occurrence, which could cause
2520 us to run out of disk space. Fixes bug 33093; bugfix
2523 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
2524 - Fix an assertion failure that could result from a corrupted
2525 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
2526 bugfix on 0.3.3.1-alpha. This issue is also tracked
2529 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
2530 - Fix a syntax warning given by newer versions of Rust that was
2531 creating problems for our continuous integration. Fixes bug 33212;
2532 bugfix on 0.3.5.1-alpha.
2534 o Testing (Travis CI, backport from 0.4.3.3-alpha):
2535 - Remove a redundant distcheck job. Closes ticket 33194.
2536 - Sort the Travis jobs in order of speed: putting the slowest jobs
2537 first takes full advantage of Travis job concurrency. Closes
2539 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2540 previously configured to fast_finish (which requires
2541 allow_failure), to speed up the build. Closes ticket 33195.
2542 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2543 tool to produce detailed diagnostic output. Closes ticket 32792.
2546 Changes in version 0.4.1.9 - 2020-03-18
2547 Tor 0.4.1.9 backports important fixes from later Tor releases,
2548 including a fix for TROVE-2020-002, a major denial-of-service
2549 vulnerability that affected all released Tor instances since
2550 0.2.1.5-alpha. Using this vulnerability, an attacker could cause Tor
2551 instances to consume a huge amount of CPU, disrupting their operations
2552 for several seconds or minutes. This attack could be launched by
2553 anybody against a relay, or by a directory cache against any client
2554 that had connected to it. The attacker could launch this attack as
2555 much as they wanted, thereby disrupting service or creating patterns
2556 that could aid in traffic analysis. This issue was found by OSS-Fuzz,
2557 and is also tracked as CVE-2020-10592.
2559 We do not have reason to believe that this attack is currently being
2560 exploited in the wild, but nonetheless we advise everyone to upgrade
2561 as soon as packages are available.
2563 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
2564 - Fix a denial-of-service bug that could be used by anyone to
2565 consume a bunch of CPU on any Tor relay or authority, or by
2566 directories to consume a bunch of CPU on clients or hidden
2567 services. Because of the potential for CPU consumption to
2568 introduce observable timing patterns, we are treating this as a
2569 high-severity security issue. Fixes bug 33119; bugfix on
2570 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
2571 as TROVE-2020-002 and CVE-2020-10592.
2573 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
2574 - Avoid a remotely triggered memory leak in the case that a circuit
2575 padding machine is somehow negotiated twice on the same circuit.
2576 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
2577 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
2579 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
2580 - Lowercase the configured value of BridgeDistribution before adding
2581 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
2583 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
2584 - If we encounter a bug when flushing a buffer to a TLS connection,
2585 only log the bug once per invocation of the Tor process.
2586 Previously we would log with every occurrence, which could cause
2587 us to run out of disk space. Fixes bug 33093; bugfix
2590 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
2591 - Fix an assertion failure that could result from a corrupted
2592 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
2593 bugfix on 0.3.3.1-alpha. This issue is also tracked
2596 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
2597 - Fix a syntax warning given by newer versions of Rust that was
2598 creating problems for our continuous integration. Fixes bug 33212;
2599 bugfix on 0.3.5.1-alpha.
2601 o Testing (Travis CI, backport from 0.4.3.3-alpha):
2602 - Remove a redundant distcheck job. Closes ticket 33194.
2603 - Sort the Travis jobs in order of speed: putting the slowest jobs
2604 first takes full advantage of Travis job concurrency. Closes
2606 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2607 previously configured to fast_finish (which requires
2608 allow_failure), to speed up the build. Closes ticket 33195.
2609 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2610 tool to produce detailed diagnostic output. Closes ticket 32792.
2613 Changes in version 0.3.5.10 - 2020-03-18
2614 Tor 0.3.5.10 backports many fixes from later Tor releases, including a
2615 fix for TROVE-2020-002, a major denial-of-service vulnerability that
2616 affected all released Tor instances since 0.2.1.5-alpha. Using this
2617 vulnerability, an attacker could cause Tor instances to consume a huge
2618 amount of CPU, disrupting their operations for several seconds or
2619 minutes. This attack could be launched by anybody against a relay, or
2620 by a directory cache against any client that had connected to it. The
2621 attacker could launch this attack as much as they wanted, thereby
2622 disrupting service or creating patterns that could aid in traffic
2623 analysis. This issue was found by OSS-Fuzz, and is also tracked
2626 We do not have reason to believe that this attack is currently being
2627 exploited in the wild, but nonetheless we advise everyone to upgrade
2628 as soon as packages are available.
2630 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
2631 - Fix a denial-of-service bug that could be used by anyone to
2632 consume a bunch of CPU on any Tor relay or authority, or by
2633 directories to consume a bunch of CPU on clients or hidden
2634 services. Because of the potential for CPU consumption to
2635 introduce observable timing patterns, we are treating this as a
2636 high-severity security issue. Fixes bug 33119; bugfix on
2637 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
2638 as TROVE-2020-002 and CVE-2020-10592.
2640 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
2641 - Correct how we use libseccomp. Particularly, stop assuming that
2642 rules are applied in a particular order or that more rules are
2643 processed after the first match. Neither is the case! In
2644 libseccomp <2.4.0 this lead to some rules having no effect.
2645 libseccomp 2.4.0 changed how rules are generated, leading to a
2646 different ordering, which in turn led to a fatal crash during
2647 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
2650 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
2651 - Stop allowing failures on the Travis CI stem tests job. It looks
2652 like all the stem hangs we were seeing before are now fixed.
2653 Closes ticket 33075.
2655 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
2656 - Lowercase the configured value of BridgeDistribution before adding
2657 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
2659 o Minor bugfixes (crash, backport from 0.4.2.4-rc):
2660 - When running Tor with an option like --verify-config or
2661 --dump-config that does not start the event loop, avoid crashing
2662 if we try to exit early because of an error. Fixes bug 32407;
2663 bugfix on 0.3.3.1-alpha.
2665 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
2666 - If we encounter a bug when flushing a buffer to a TLS connection,
2667 only log the bug once per invocation of the Tor process.
2668 Previously we would log with every occurrence, which could cause
2669 us to run out of disk space. Fixes bug 33093; bugfix
2672 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
2673 - Fix an assertion failure that could result from a corrupted
2674 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
2675 bugfix on 0.3.3.1-alpha. This issue is also tracked
2678 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
2679 - Fix a syntax warning given by newer versions of Rust that was
2680 creating problems for our continuous integration. Fixes bug 33212;
2681 bugfix on 0.3.5.1-alpha.
2683 o Testing (backport from 0.4.3.1-alpha):
2684 - Re-enable the Travis CI macOS Chutney build, but don't let it
2685 prevent the Travis job from finishing. (The Travis macOS jobs are
2686 slow, so we don't want to have it delay the whole CI process.)
2687 Closes ticket 32629.
2688 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
2689 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
2690 fix the sandbox errors in 32722. Closes ticket 32240.
2692 o Testing (continuous integration, backport from 0.4.3.1-alpha):
2693 - Use zstd in our Travis Linux builds. Closes ticket 32242.
2695 o Testing (Travis CI, backport from 0.4.3.3-alpha):
2696 - Remove a redundant distcheck job. Closes ticket 33194.
2697 - Sort the Travis jobs in order of speed: putting the slowest jobs
2698 first takes full advantage of Travis job concurrency. Closes
2700 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2701 previously configured to fast_finish (which requires
2702 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2703 tool to produce detailed diagnostic output. Closes ticket 32792.
2706 Changes in version 0.4.3.2-alpha - 2020-02-10
2707 This is the second stable alpha release in the Tor 0.4.3.x series. It
2708 fixes several bugs present in the previous alpha release. Anybody
2709 running the previous alpha should upgrade, and look for bugs in this
2712 o Major bugfixes (onion service client, authorization):
2713 - On a NEWNYM signal, purge entries from the ephemeral client
2714 authorization cache. The permanent ones are kept. Fixes bug 33139;
2715 bugfix on 0.4.3.1-alpha.
2717 o Minor features (best practices tracker):
2718 - Practracker now supports a --regen-overbroad option to regenerate
2719 the exceptions file, but only to revise exceptions to be _less_
2720 tolerant of best-practices violations. Closes ticket 32372.
2722 o Minor features (continuous integration):
2723 - Run Doxygen Makefile target on Travis, so we can learn about
2724 regressions in our internal documentation. Closes ticket 32455.
2725 - Stop allowing failures on the Travis CI stem tests job. It looks
2726 like all the stem hangs we were seeing before are now fixed.
2727 Closes ticket 33075.
2729 o Minor bugfixes (build system):
2730 - Revise configure options that were either missing or incorrect in
2731 the configure summary. Fixes bug 32230; bugfix on 0.4.3.1-alpha.
2733 o Minor bugfixes (controller protocol):
2734 - Fix a memory leak introduced by refactoring of control reply
2735 formatting code. Fixes bug 33039; bugfix on 0.4.3.1-alpha.
2736 - Fix a memory leak in GETINFO responses. Fixes bug 33103; bugfix
2738 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
2739 report them as SIGNAL events. Previously we would log a bug
2740 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
2742 o Minor bugfixes (logging):
2743 - If we encounter a bug when flushing a buffer to a TLS connection,
2744 only log the bug once per invocation of the Tor process.
2745 Previously we would log with every occurrence, which could cause
2746 us to run out of disk space. Fixes bug 33093; bugfix
2748 - When logging a bug, do not say "Future instances of this warning
2749 will be silenced" unless we are actually going to silence them.
2750 Previously we would say this whenever a BUG() check failed in the
2751 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
2753 o Minor bugfixes (onion service v2):
2754 - Move a series of v2 onion service warnings to protocol-warning
2755 level because they can all be triggered remotely by a malformed
2756 request. Fixes bug 32706; bugfix on 0.1.1.14-alpha.
2758 o Minor bugfixes (onion service v3, client authorization):
2759 - When removing client authorization credentials using the control
2760 port, also remove the associated descriptor, so the onion service
2761 can no longer be contacted. Fixes bug 33148; bugfix
2764 o Minor bugfixes (pluggable transports):
2765 - When receiving a message on standard error from a pluggable
2766 transport, log it at info level, rather than as a warning. Fixes
2767 bug 33005; bugfix on 0.4.0.1-alpha.
2769 o Minor bugfixes (rust, build):
2770 - Fix a syntax warning given by newer versions of Rust that was
2771 creating problems for our continuous integration. Fixes bug 33212;
2772 bugfix on 0.3.5.1-alpha.
2774 o Minor bugfixes (TLS bug handling):
2775 - When encountering a bug in buf_read_from_tls(), return a "MISC"
2776 error code rather than "WANTWRITE". This change might help avoid
2777 some CPU-wasting loops if the bug is ever triggered. Bug reported
2778 by opara. Fixes bug 32673; bugfix on 0.3.0.4-alpha.
2780 o Code simplification and refactoring (mainloop):
2781 - Simplify the ip_address_changed() function by removing redundant
2782 checks. Closes ticket 33091.
2784 o Documentation (manpage):
2785 - Split "Circuit Timeout" options and "Node Selection" options into
2786 their own sections of the tor manpage. Closes tickets 32928 and
2787 32929. Work by Swati Thacker as part of Google Season of Docs.
2790 Changes in version 0.4.2.6 - 2020-01-30
2791 This is the second stable release in the 0.4.2.x series. It backports
2792 several bugfixes from 0.4.3.1-alpha, including some that had affected
2793 the Linux seccomp2 sandbox or Windows services. If you're running with
2794 one of those configurations, you'll probably want to upgrade;
2795 otherwise, you should be fine with 0.4.2.5.
2797 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
2798 - Correct how we use libseccomp. Particularly, stop assuming that
2799 rules are applied in a particular order or that more rules are
2800 processed after the first match. Neither is the case! In
2801 libseccomp <2.4.0 this led to some rules having no effect.
2802 libseccomp 2.4.0 changed how rules are generated, leading to a
2803 different ordering, which in turn led to a fatal crash during
2804 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
2806 - Fix crash when reloading logging configuration while the
2807 experimental sandbox is enabled. Fixes bug 32841; bugfix on
2808 0.4.1.7. Patch by Peter Gerber.
2810 o Minor bugfixes (correctness checks, backport from 0.4.3.1-alpha):
2811 - Use GCC/Clang's printf-checking feature to make sure that
2812 tor_assertf() arguments are correctly typed. Fixes bug 32765;
2813 bugfix on 0.4.1.1-alpha.
2815 o Minor bugfixes (logging, crash, backport from 0.4.3.1-alpha):
2816 - Avoid a possible crash when trying to log a (fatal) assertion
2817 failure about mismatched magic numbers in configuration objects.
2818 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
2820 o Minor bugfixes (testing, backport from 0.4.3.1-alpha):
2821 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
2822 test_practracker.sh script. Doing so caused a test failure. Fixes
2823 bug 32705; bugfix on 0.4.2.1-alpha.
2824 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
2825 skipping practracker checks. Fixes bug 32705; bugfix
2828 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
2829 - Initialize the publish/subscribe system when running as a windows
2830 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
2832 o Testing (backport from 0.4.3.1-alpha):
2833 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
2834 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
2835 fix the sandbox errors in 32722. Closes ticket 32240.
2836 - Re-enable the Travis CI macOS Chutney build, but don't let it
2837 prevent the Travis job from finishing. (The Travis macOS jobs are
2838 slow, so we don't want to have it delay the whole CI process.)
2839 Closes ticket 32629.
2841 o Testing (continuous integration, backport from 0.4.3.1-alpha):
2842 - Use zstd in our Travis Linux builds. Closes ticket 32242.
2845 Changes in version 0.4.1.8 - 2020-01-30
2846 This release backports several bugfixes from later release series,
2847 including some that had affected the Linux seccomp2 sandbox or Windows
2848 services. If you're running with one of those configurations, you'll
2849 probably want to upgrade; otherwise, you should be fine with your
2850 current version of 0.4.1.x.
2852 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
2853 - Correct how we use libseccomp. Particularly, stop assuming that
2854 rules are applied in a particular order or that more rules are
2855 processed after the first match. Neither is the case! In
2856 libseccomp <2.4.0 this led to some rules having no effect.
2857 libseccomp 2.4.0 changed how rules are generated, leading to a
2858 different ordering, which in turn led to a fatal crash during
2859 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
2861 - Fix crash when reloading logging configuration while the
2862 experimental sandbox is enabled. Fixes bug 32841; bugfix on
2863 0.4.1.7. Patch by Peter Gerber.
2865 o Minor bugfixes (crash, backport form 0.4.2.4-rc):
2866 - When running Tor with an option like --verify-config or
2867 --dump-config that does not start the event loop, avoid crashing
2868 if we try to exit early because of an error. Fixes bug 32407;
2869 bugfix on 0.3.3.1-alpha.
2871 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
2872 - Initialize the publish/subscribe system when running as a windows
2873 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
2875 o Testing (backport from 0.4.3.1-alpha):
2876 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
2877 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
2878 fix the sandbox errors in 32722. Closes ticket 32240.
2879 - Re-enable the Travis CI macOS Chutney build, but don't let it
2880 prevent the Travis job from finishing. (The Travis macOS jobs are
2881 slow, so we don't want to have it delay the whole CI process.)
2882 Closes ticket 32629.
2884 o Testing (continuous integration, backport from 0.4.3.1-alpha):
2885 - Use zstd in our Travis Linux builds. Closes ticket 32242.
2888 Changes in version 0.4.3.1-alpha - 2020-01-22
2889 This is the first alpha release in the 0.4.3.x series. It includes
2890 improved support for application integration of onion services, support
2891 for building in a client-only mode, and newly improved internal
2892 documentation (online at https://src-ref.docs.torproject.org/tor/). It
2893 also has numerous other small bugfixes and features, as well as
2894 improvements to our code's internal organization that should help us
2895 write better code in the future.
2897 o New system requirements:
2898 - When building Tor, you now need to have Python 3 in order to run
2899 the integration tests. (Python 2 is officially unsupported
2900 upstream, as of 1 Jan 2020.) Closes ticket 32608.
2902 o Major features (build system):
2903 - The relay code can now be disabled using the --disable-module-relay
2904 configure option. When this option is set, we also disable the
2905 dirauth module. Closes ticket 32123.
2906 - When Tor is compiled --disable-module-relay, we also omit the code
2907 used to act as a directory cache. Closes ticket 32487.
2909 o Major features (directory authority, ed25519):
2910 - Add support for banning a relay's ed25519 keys in the approved-
2911 routers file. This will help us migrate away from RSA keys in the
2912 future. Previously, only RSA keys could be banned in approved-
2913 routers. Resolves ticket 22029. Patch by Neel Chauhan.
2915 o Major features (onion service, controller):
2916 - New control port commands to manage client-side onion service
2917 authorization credentials. The ONION_CLIENT_AUTH_ADD command adds
2918 a credential, ONION_CLIENT_AUTH_REMOVE deletes a credential, and
2919 ONION_CLIENT_AUTH_VIEW lists the credentials. Closes ticket 30381.
2921 o Major features (onion service, SOCKS5):
2922 - Introduce a new SocksPort flag, ExtendedErrors, to support more
2923 detailed error codes in information for applications that support
2924 them. Closes ticket 30382; implements proposal 304.
2926 o Major features (proxy):
2927 - In addition to its current supported proxy types (HTTP CONNECT,
2928 SOCKS4, and SOCKS5), Tor can now make its OR connections through a
2929 HAProxy server. A new torrc option was added to specify the
2930 address/port of the server: TCPProxy <protocol> <host>:<port>.
2931 Currently the only supported protocol for the option is haproxy.
2932 Closes ticket 31518. Patch done by Suphanat Chunhapanya (haxxpop).
2934 o Major bugfixes (linux seccomp sandbox):
2935 - Correct how we use libseccomp. Particularly, stop assuming that
2936 rules are applied in a particular order or that more rules are
2937 processed after the first match. Neither is the case! In
2938 libseccomp <2.4.0 this led to some rules having no effect.
2939 libseccomp 2.4.0 changed how rules are generated, leading to a
2940 different ordering, which in turn led to a fatal crash during
2941 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
2943 - Fix crash when reloading logging configuration while the
2944 experimental sandbox is enabled. Fixes bug 32841; bugfix on
2945 0.4.1.7. Patch by Peter Gerber.
2947 o Major bugfixes (networking):
2948 - Correctly handle IPv6 addresses in SOCKS5 RESOLVE_PTR requests,
2949 and accept strings as well as binary addresses. Fixes bug 32315;
2950 bugfix on 0.3.5.1-alpha.
2952 o Major bugfixes (onion service):
2953 - Report HS circuit failure back into the HS subsystem so we take
2954 appropriate action with regards to the client introduction point
2955 failure cache. This improves reachability of onion services, since
2956 now clients notice failing introduction circuits properly. Fixes
2957 bug 32020; bugfix on 0.3.2.1-alpha.
2959 o Minor feature (configure, build system):
2960 - Output a list of enabled/disabled features at the end of the
2961 configure process in a pleasing way. Closes ticket 31373.
2963 o Minor feature (heartbeat, onion service):
2964 - Add the DoS INTRODUCE2 defenses counter to the heartbeat DoS
2965 message. Closes ticket 31371.
2967 o Minor features (configuration validation):
2968 - Configuration validation can now be done by per-module callbacks,
2969 rather than a global validation function. This will let us reduce
2970 the size of config.c and some of its more cumbersome functions.
2971 Closes ticket 31241.
2973 o Minor features (configuration):
2974 - If a configured hardware crypto accelerator in AccelName is
2975 prefixed with "!", Tor now exits when it cannot be found. Closes
2977 - We now use flag-driven logic to warn about obsolete configuration
2978 fields, so that we can include their names. In 0.4.2, we used a
2979 special type, which prevented us from generating good warnings.
2980 Implements ticket 32404.
2982 o Minor features (controller):
2983 - Add stream isolation data to STREAM event. Closes ticket 19859.
2984 - Implement a new GETINFO command to fetch microdescriptor
2985 consensus. Closes ticket 31684.
2987 o Minor features (debugging, directory system):
2988 - Don't crash when we find a non-guard with a guard-fraction value
2989 set. Instead, log a bug warning, in an attempt to figure out how
2990 this happened. Diagnostic for ticket 32868.
2992 o Minor features (defense in depth):
2993 - Add additional checks around tor_vasprintf() usage, in case the
2994 function returns an error. Patch by Tobias Stoeckmann. Fixes
2997 o Minor features (developer tooling):
2998 - Remove the 0.2.9.x series branches from git scripts (git-merge-
2999 forward.sh, git-pull-all.sh, git-push-all.sh, git-setup-dirs.sh).
3000 Closes ticket 32772.
3002 o Minor features (developer tools):
3003 - Add a check_cocci_parse.sh script that checks that new code is
3004 parseable by Coccinelle. Add an exceptions file for unparseable
3005 files, and run the script from travis CI. Closes ticket 31919.
3006 - Call the check_cocci_parse.sh script from a 'check-cocci' Makefile
3007 target. Closes ticket 31919.
3008 - Add a rename_c_identifiers.py tool to rename a bunch of C
3009 identifiers at once, and generate a well-formed commit message
3010 describing the change. This should help with refactoring. Closes
3012 - Add some scripts in "scripts/coccinelle" to invoke the Coccinelle
3013 semantic patching tool with the correct flags. These flags are
3014 fairly easy to forget, and these scripts should help us use
3015 Coccinelle more effectively in the future. Closes ticket 31705.
3017 o Minor features (Doxygen):
3018 - Update Doxygen configuration file to a more recent template (from
3019 1.8.15). Closes ticket 32110.
3020 - "make doxygen" now works with out-of-tree builds. Closes
3022 - Make sure that doxygen outputs documentation for all of our C
3023 files. Previously, some were missing @file declarations, causing
3024 them to be ignored. Closes ticket 32307.
3025 - Our "make doxygen" target now respects --enable-fatal-warnings by
3026 default, and does not warn about items that are missing
3027 documentation. To warn about missing documentation, run configure
3028 with the "--enable-missing-doc-warnings" flag: doing so suspends
3029 fatal warnings for doxygen. Closes ticket 32385.
3031 o Minor features (git scripts):
3032 - Add TOR_EXTRA_CLONE_ARGS to git-setup-dirs.sh for git clone
3033 customisation. Closes ticket 32347.
3034 - Add git-setup-dirs.sh, which sets up an upstream git repository
3035 and worktrees for tor maintainers. Closes ticket 29603.
3036 - Add TOR_EXTRA_REMOTE_* to git-setup-dirs.sh for a custom extra
3037 remote. Closes ticket 32347.
3038 - Call the check_cocci_parse.sh script from the git commit and push
3039 hooks. Closes ticket 31919.
3040 - Make git-push-all.sh skip unchanged branches when pushing to
3041 upstream. The script already skipped unchanged test branches.
3042 Closes ticket 32216.
3043 - Make git-setup-dirs.sh create a master symlink in the worktree
3044 directory. Closes ticket 32347.
3045 - Skip unmodified source files when doing some existing git hook
3046 checks. Related to ticket 31919.
3048 o Minor features (IPv6, client):
3049 - Make Tor clients tell dual-stack exits that they prefer IPv6
3050 connections. This change is equivalent to setting the PreferIPv6
3051 flag on SOCKSPorts (and most other listener ports). Tor Browser
3052 has been setting this flag for some time, and we want to remove a
3053 client distinguisher at exits. Closes ticket 32637.
3055 o Minor features (portability, android):
3056 - When building for Android, disable some tests that depend on $HOME
3057 and/or pwdb, which Android doesn't have. Closes ticket 32825.
3058 Patch from Hans-Christoph Steiner.
3060 o Minor features (relay modularity):
3061 - Split the relay and server pluggable transport config code into
3062 separate files in the relay module. Disable this code when the
3063 relay module is disabled. Closes part of ticket 32213.
3064 - When the relay module is disabled, reject attempts to set the
3065 ORPort, DirPort, DirCache, BridgeRelay, ExtORPort, or
3066 ServerTransport* options, rather than ignoring the values of these
3067 options. Closes part of ticket 32213.
3069 o Minor features (relay):
3070 - When the relay module is disabled, change the default config so
3071 that DirCache is 0, and ClientOnly is 1. Closes ticket 32410.
3073 o Minor features (release tools):
3074 - Port our ChangeLog formatting and sorting tools to Python 3.
3075 Closes ticket 32704.
3077 o Minor features (testing):
3078 - Detect some common failure cases for test_parseconf.sh in
3079 src/test/conf_failures. Closes ticket 32451.
3080 - Allow test_parseconf.sh to test expected log outputs for successful
3081 configs, as well as failed configs. Closes ticket 32451.
3082 - The test_parseconf.sh script now supports result variants for any
3083 combination of the optional libraries lzma, nss, and zstd. Closes
3086 o Minor features (tests, Android):
3087 - When running the unit tests on Android, create temporary files in
3088 a subdirectory of /data/local/tmp. Closes ticket 32172. Based on a
3089 patch from Hans-Christoph Steiner.
3091 o Minor bugfixes (bridges):
3092 - Lowercase the configured value of BridgeDistribution before adding
3093 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
3095 o Minor bugfixes (build system):
3096 - Fix "make autostyle" for out-of-tree builds. Fixes bug 32370;
3097 bugfix on 0.4.1.2-alpha.
3099 o Minor bugfixes (configuration handling):
3100 - Make control_event_conf_changed() take in a config_line_t instead
3101 of a smartlist of alternating key/value entries. Fixes bug 31531;
3102 bugfix on 0.2.3.3-alpha. Patch by Neel Chauhan.
3104 o Minor bugfixes (configuration):
3105 - Check for multiplication overflow when parsing memory units inside
3106 configuration. Fixes bug 30920; bugfix on 0.0.9rc1.
3107 - When dumping the configuration, stop adding a trailing space after
3108 the option name when there is no option value. This issue only
3109 affects options that accept an empty value or list. (Most options
3110 reject empty values, or delete the entire line from the dumped
3111 options.) Fixes bug 32352; bugfix on 0.0.9pre6.
3112 - Avoid changing the user's value of HardwareAccel as stored by
3113 SAVECONF, when AccelName is set but HardwareAccel is not. Fixes
3114 bug 32382; bugfix on 0.2.2.1-alpha.
3115 - When creating a KeyDirectory with the same location as the
3116 DataDirectory (not recommended), respect the DataDirectory's
3117 group-readable setting if one has not been set for the
3118 KeyDirectory. Fixes bug 27992; bugfix on 0.3.3.1-alpha.
3120 o Minor bugfixes (controller):
3121 - In routerstatus_has_changed(), check all the fields that are
3122 output over the control port. Fixes bug 20218; bugfix
3125 o Minor bugfixes (correctness checks):
3126 - Use GCC/Clang's printf-checking feature to make sure that
3127 tor_assertf() arguments are correctly typed. Fixes bug 32765;
3128 bugfix on 0.4.1.1-alpha.
3130 o Minor bugfixes (developer tools):
3131 - Allow paths starting with ./ in scripts/add_c_file.py. Fixes bug
3132 31336; bugfix on 0.4.1.2-alpha.
3134 o Minor bugfixes (dirauth module):
3135 - Split the dirauth config code into a separate file in the dirauth
3136 module. Disable this code when the dirauth module is disabled.
3137 Closes ticket 32213.
3138 - When the dirauth module is disabled, reject attempts to set the
3139 AuthoritativeDir option, rather than ignoring the value of the
3140 option. Fixes bug 32213; bugfix on 0.3.4.1-alpha.
3142 o Minor bugfixes (embedded Tor):
3143 - When starting Tor any time after the first time in a process,
3144 register the thread in which it is running as the main thread.
3145 Previously, we only did this on Windows, which could lead to bugs
3146 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
3149 o Minor bugfixes (git scripts):
3150 - Avoid sleeping before the last push in git-push-all.sh. Closes
3152 - Forward all unrecognised arguments in git-push-all.sh to git push.
3153 Closes ticket 32216.
3155 o Minor bugfixes (hidden service v3):
3156 - Do not rely on a "circuit established" flag for intro circuits but
3157 instead always query the HS circuit map. This is to avoid sync
3158 issue with that flag and the map. Fixes bug 32094; bugfix
3161 o Minor bugfixes (logging, crash):
3162 - Avoid a possible crash when trying to log a (fatal) assertion
3163 failure about mismatched magic numbers in configuration objects.
3164 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
3166 o Minor bugfixes (onion service v2):
3167 - When sending the INTRO cell for a v2 Onion Service, look at the
3168 failure cache alongside timeout values to check if the intro point
3169 is marked as failed. Previously, we only looked at the relay
3170 timeout values. Fixes bug 25568; bugfix on 0.2.7.3-rc. Patch by
3173 o Minor bugfixes (onion services v3, client):
3174 - Properly handle the client rendezvous circuit timeout. Previously
3175 Tor would sometimes timeout a rendezvous circuit awaiting the
3176 introduction ACK, and find itself unable to re-establish all
3177 circuits because the rendezvous circuit timed out too early. Fixes
3178 bug 32021; bugfix on 0.3.2.1-alpha.
3180 o Minor bugfixes (onion services):
3181 - In cancel_descriptor_fetches(), use
3182 connection_list_by_type_purpose() instead of
3183 connection_list_by_type_state(). Fixes bug 32639; bugfix on
3184 0.3.2.1-alpha. Patch by Neel Chauhan.
3186 o Minor bugfixes (scripts):
3187 - Fix update_versions.py for out-of-tree builds. Fixes bug 32371;
3188 bugfix on 0.4.0.1-alpha.
3190 o Minor bugfixes (test):
3191 - Use the same code to find the tor binary in all of our test
3192 scripts. This change makes sure we are always using the coverage
3193 binary when coverage is enabled. Fixes bug 32368; bugfix
3196 o Minor bugfixes (testing):
3197 - Stop ignoring "tor --dump-config" errors in test_parseconf.sh.
3198 Fixes bug 32468; bugfix on 0.4.2.1-alpha.
3199 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
3200 test_practracker.sh script. Doing so caused a test failure. Fixes
3201 bug 32705; bugfix on 0.4.2.1-alpha.
3202 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
3203 skipping practracker checks. Fixes bug 32705; bugfix
3206 o Minor bugfixes (tests):
3207 - Our option-validation tests no longer depend on specially
3208 configured non-default, non-passing sets of options. Previously,
3209 the tests had been written to assume that options would _not_ be
3210 set to their defaults, which led to needless complexity and
3211 verbosity. Fixes bug 32175; bugfix on 0.2.8.1-alpha.
3213 o Minor bugfixes (windows service):
3214 - Initialize the publish/subscribe system when running as a windows
3215 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
3217 o Deprecated features:
3218 - Deprecate the ClientAutoIPv6ORPort option. This option was not
3219 true "Happy Eyeballs", and often failed on connections that
3220 weren't reliably dual-stack. Closes ticket 32942. Patch by
3224 - Provide a quickstart guide for a Circuit Padding Framework, and
3225 documentation for researchers to implement and study circuit
3226 padding machines. Closes ticket 28804.
3227 - Add documentation in 'HelpfulTools.md' to describe how to build a
3228 tag file. Closes ticket 32779.
3229 - Create a high-level description of the long-term software
3230 architecture goals. Closes ticket 32206.
3231 - Describe the --dump-config command in the manual page. Closes
3233 - Unite coding advice from this_not_that.md in torguts repo into our
3234 coding standards document. Resolves ticket 31853.
3237 - Our Doxygen configuration no longer generates LaTeX output. The
3238 reference manual produced by doing this was over 4000 pages long,
3239 and generally unusable. Closes ticket 32099.
3240 - The option "TestingEstimatedDescriptorPropagationTime" is now
3241 marked as obsolete. It has had no effect since 0.3.0.7, when
3242 clients stopped rejecting consensuses "from the future". Closes
3244 - We no longer support consensus methods before method 28; these
3245 methods were only used by authorities running versions of Tor that
3246 are now at end-of-life. In effect, this means that clients,
3247 relays, and authorities now assume that authorities will be
3248 running version 0.3.5.x or later. Closes ticket 32695.
3251 - Add more test cases for tor's UTF-8 validation function. Also,
3252 check the arguments passed to the function for consistency. Closes
3254 - Improve test coverage for relay and dirauth config code, focusing
3255 on option validation and normalization. Closes ticket 32213.
3256 - Improve the consistency of test_parseconf.sh output, and run all
3257 the tests, even if one fails. Closes ticket 32213.
3258 - Re-enable the Travis CI macOS Chutney build, but don't let it
3259 prevent the Travis job from finishing. (The Travis macOS jobs are
3260 slow, so we don't want to have it delay the whole CI process.)
3261 Closes ticket 32629.
3262 - Run the practracker unit tests in the pre-commit git hook. Closes
3264 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
3265 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
3266 fix the sandbox errors in 32722. Closes ticket 32240.
3268 o Code simplification and refactoring (channel):
3269 - Channel layer had a variable length cell handler that was not used
3270 and thus removed. Closes ticket 32892.
3272 o Code simplification and refactoring (configuration):
3273 - Immutability is now implemented as a flag on individual
3274 configuration options rather than as part of the option-transition
3275 checking code. Closes ticket 32344.
3276 - Instead of keeping a list of configuration options to check for
3277 relative paths, check all the options whose type is "FILENAME".
3278 Solves part of ticket 32339.
3279 - Our default log (which ordinarily sends NOTICE-level messages to
3280 standard output) is now handled in a more logical manner.
3281 Previously, we replaced the configured log options if they were
3282 empty. Now, we interpret an empty set of log options as meaning
3283 "use the default log". Closes ticket 31999.
3284 - Remove some unused arguments from the options_validate() function,
3285 to simplify our code and tests. Closes ticket 32187.
3286 - Simplify the options_validate() code so that it looks at the
3287 default options directly, rather than taking default options as an
3288 argument. This change lets us simplify its interface. Closes
3290 - Use our new configuration architecture to move most authority-
3291 related options to the directory authority module. Closes
3293 - When parsing the command line, handle options that determine our
3294 "quiet level" and our mode of operation (e.g., --dump-config and
3295 so on) all in one table. Closes ticket 32003.
3297 o Code simplification and refactoring (controller):
3298 - Create a new abstraction for formatting control protocol reply
3299 lines based on key-value pairs. Refactor some existing control
3300 protocol code to take advantage of this. Closes ticket 30984.
3301 - Create a helper function that can fetch network status or
3302 microdesc consensuses. Closes ticket 31684.
3304 o Code simplification and refactoring (dirauth modularization):
3305 - Remove the last remaining HAVE_MODULE_DIRAUTH inside a function.
3306 Closes ticket 32163.
3307 - Replace some confusing identifiers in process_descs.c. Closes
3309 - Simplify some relay and dirauth config code. Closes ticket 32213.
3311 o Code simplification and refactoring (misc):
3312 - Make all the structs we declare follow the same naming convention
3313 of ending with "_t". Closes ticket 32415.
3314 - Move and rename some configuration-related code for clarity.
3315 Closes ticket 32304.
3316 - Our include.am files are now broken up by subdirectory.
3317 Previously, src/core/include.am covered all of the subdirectories
3318 in "core", "feature", and "app". Closes ticket 32137.
3319 - Remove underused NS*() macros from test code: they make our tests
3320 more confusing, especially for code-formatting tools. Closes
3323 o Code simplification and refactoring (relay modularization):
3324 - Disable relay_periodic when the relay module is disabled. Closes
3326 - Disable relay_sys when the relay module is disabled. Closes
3329 o Code simplification and refactoring (tool support):
3330 - Add numerous missing dependencies to our include files, so that
3331 they can be included in different reasonable orders and still
3332 compile. Addresses part of ticket 32764.
3333 - Fix some parts of our code that were difficult for Coccinelle to
3334 parse. Related to ticket 31705.
3335 - Fix some small issues in our code that prevented automatic
3336 formatting tools from working. Addresses part of ticket 32764.
3338 o Documentation (manpage):
3339 - Alphabetize the Client Options section of the tor manpage. Closes
3341 - Alphabetize the General Options section of the tor manpage. Closes
3343 - In the tor(1) manpage, reword and improve formatting of the
3344 COMMAND-LINE OPTIONS and DESCRIPTION sections. Closes ticket
3345 32277. Based on work by Swati Thacker as part of Google Season
3347 - In the tor(1) manpage, reword and improve formatting of the FILES,
3348 SEE ALSO, and BUGS sections. Closes ticket 32176. Based on work by
3349 Swati Thacker as part of Google Season of Docs.
3351 o Testing (circuit, EWMA):
3352 - Add unit tests for circuitmux and EWMA subsystems. Closes
3355 o Testing (continuous integration):
3356 - Use zstd in our Travis Linux builds. Closes ticket 32242.
3359 Changes in version 0.4.2.5 - 2019-12-09
3360 This is the first stable release in the 0.4.2.x series. This series
3361 improves reliability and stability, and includes several stability and
3362 correctness improvements for onion services. It also fixes many smaller
3363 bugs present in previous series.
3365 Per our support policy, we will support the 0.4.2.x series for nine
3366 months, or until three months after the release of a stable 0.4.3.x:
3367 whichever is longer. If you need longer-term support, please stick
3368 with 0.3.5.x, which will we plan to support until Feb 2022.
3370 Per our support policy, we will support the 0.4.2.x series for nine
3371 months, or until three months after the release of a stable 0.4.3.x:
3372 whichever is longer. If you need longer-term support, please stick
3373 with 0.3.5.x, which will we plan to support until Feb 2022.
3375 Below are the changes since 0.4.1.4-rc. For a complete list of changes
3376 since 0.4.1.5, see the ReleaseNotes file.
3378 o Minor features (geoip):
3379 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
3380 Country database. Closes ticket 32685.
3383 - Require C99 standards-conforming code in Travis CI, but allow GNU
3384 gcc extensions. Also activates clang's -Wtypedef-redefinition
3385 warnings. Build some jobs with -std=gnu99, and some jobs without.
3386 Closes ticket 32500.
3389 Changes in version 0.4.1.7 - 2019-12-09
3390 This release backports several bugfixes to improve stability and
3391 correctness. Anyone experiencing build problems or crashes with 0.4.1.6,
3392 including all relays relying on AccountingMax, should upgrade.
3394 o Major features (directory authorities, backport from 0.4.2.2-alpha):
3395 - Directory authorities now reject relays running all currently
3396 deprecated release series. The currently supported release series
3397 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
3399 o Major bugfixes (embedded Tor, backport from 0.4.2.2-alpha):
3400 - Avoid a possible crash when restarting Tor in embedded mode and
3401 enabling a different set of publish/subscribe messages. Fixes bug
3402 31898; bugfix on 0.4.1.1-alpha.
3404 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
3405 - Relays now respect their AccountingMax bandwidth again. When
3406 relays entered "soft" hibernation (which typically starts when
3407 we've hit 90% of our AccountingMax), we had stopped checking
3408 whether we should enter hard hibernation. Soft hibernation refuses
3409 new connections and new circuits, but the existing circuits can
3410 continue, meaning that relays could have exceeded their configured
3411 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
3413 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
3414 - Stop ignoring torrc options after an %include directive, when the
3415 included directory ends with a file that does not contain any
3416 config options (but does contain comments or whitespace). Fixes
3417 bug 31408; bugfix on 0.3.1.1-alpha.
3419 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
3420 - Onion services now always use the exact number of intro points
3421 configured with the HiddenServiceNumIntroductionPoints option (or
3422 fewer if nodes are excluded). Before, a service could sometimes
3423 pick more intro points than configured. Fixes bug 31548; bugfix
3426 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
3427 - When building on Appveyor and Travis, pass the "-k" flag to make,
3428 so that we are informed of all compilation failures, not just the
3429 first one or two. Closes ticket 31372.
3431 o Minor features (geoip, backport from 0.4.2.5):
3432 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
3433 Country database. Closes ticket 32685.
3435 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
3436 - Avoid spurious errors when Appveyor CI fails before the install step.
3437 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
3439 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
3440 - Fix a BUG() assertion that occurs within a very small race window
3441 between when a client intro circuit opens and when its descriptor
3442 gets cleaned up from the cache. The circuit is now closed early,
3443 which will trigger a re-fetch of the descriptor and continue the
3444 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
3446 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
3447 - Avoid trying to read data from closed connections, which can cause
3448 needless loops in Libevent and infinite loops in Shadow. Fixes bug
3449 30344; bugfix on 0.1.1.1-alpha.
3451 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
3452 - On abort, try harder to flush the output buffers of log messages.
3453 On some platforms (macOS), log messages could be discarded when
3454 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3455 - Report the tor version whenever an assertion fails. Previously, we
3456 only reported the Tor version on some crashes, and some non-fatal
3457 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3458 - When tor aborts due to an error, close log file descriptors before
3459 aborting. Closing the logs makes some OSes flush log file buffers,
3460 rather than deleting buffered log lines. Fixes bug 31594; bugfix
3463 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
3464 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
3465 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
3466 - Disable backtrace signal handlers when shutting down tor. Fixes
3467 bug 31614; bugfix on 0.2.5.2-alpha.
3468 - Rate-limit our the logging message about the obsolete .exit
3469 notation. Previously, there was no limit on this warning, which
3470 could potentially be triggered many times by a hostile website.
3471 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
3473 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
3474 - Do not log a nonfatal assertion failure when receiving a VERSIONS
3475 cell on a connection using the obsolete v1 link protocol. Log a
3476 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
3478 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
3479 - Reset the periodic events' "enabled" flag when Tor is shut down
3480 cleanly. Previously, this flag was left on, which caused periodic
3481 events not to be re-enabled when Tor was relaunched in-process
3482 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
3485 o Minor bugfixes (multithreading, backport from 0.4.2.2-alpha):
3486 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
3487 31736; bugfix on 0.0.7.
3489 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
3490 - Remove overly strict assertions that triggered when a pluggable
3491 transport failed to launch. Fixes bug 31091; bugfix
3493 - Remove an assertion in the Unix process backend. This assertion
3494 would trigger when we failed to find the executable for a child
3495 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
3497 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
3498 - Avoid crashing when starting with a corrupt keys directory where
3499 the old ntor key and the new ntor key are identical. Fixes bug
3500 30916; bugfix on 0.2.4.8-alpha.
3502 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
3503 - When testing port rebinding, don't busy-wait for tor to log.
3504 Instead, actually sleep for a short time before polling again.
3505 Also improve the formatting of control commands and log messages.
3506 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
3508 o Minor bugfixes (tests, SunOS, backport from 0.4.2.2-alpha):
3509 - Avoid a map_anon_nofork test failure due to a signed/unsigned
3510 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
3512 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
3513 - Log bugs about the TLS read buffer's length only once, rather than
3514 filling the logs with similar warnings. Fixes bug 31939; bugfix
3517 o Documentation (backport from 0.4.2.2-alpha):
3518 - Explain why we can't destroy the backtrace buffer mutex. Explain
3519 why we don't need to destroy the log mutex. Closes ticket 31736.
3521 o Testing (continuous integration, backport from 0.4.2.3-alpha):
3522 - Disable all but one Travis CI macOS build, to mitigate slow
3523 scheduling of Travis macOS jobs. Closes ticket 32177.
3524 - Run the chutney IPv6 networks as part of Travis CI. Closes
3526 - Simplify the Travis CI build matrix, and optimise for build time.
3527 Closes ticket 31859.
3528 - Use Windows Server 2019 instead of Windows Server 2016 in our
3529 Appveyor builds. Closes ticket 32086.
3531 o Testing (continuous integration, backport from 0.4.2.4-rc):
3532 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
3533 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
3534 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
3535 until we can fix some Bionic permissions issues (see ticket
3536 32240). Related to ticket 31919.
3537 - Install the mingw OpenSSL package in Appveyor. This makes sure
3538 that the OpenSSL headers and libraries match in Tor's Appveyor
3539 builds. (This bug was triggered by an Appveyor image update.)
3540 Fixes bug 32449; bugfix on 0.3.5.6-rc.
3542 o Testing (continuous integration, backport from 0.4.2.5):
3543 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
3544 extensions. Also activates clang's -Wtypedef-redefinition warnings.
3545 Build some jobs with -std=gnu99, and some jobs without.
3546 Closes ticket 32500.
3549 Changes in version 0.4.0.6 - 2019-12-09
3550 This is the second stable release in the 0.4.0.x series. This release
3551 backports several bugfixes to improve stability and correctness. Anyone
3552 experiencing build problems or crashes with 0.4.0.5, including all relays
3553 relying on AccountingMax, should upgrade.
3555 Note that, per our support policy, support for the 0.4.0.x series will end
3556 on 2 Feb 2020. Anyone still running 0.4.0.x should plan to upgrade to the
3557 latest stable release, or downgrade to 0.3.5.x, which will get long-term
3558 support until 1 Feb 2022.
3560 o Directory authority changes (backport from 0.4.1.5):
3561 - The directory authority "dizum" has a new IP address. Closes
3564 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
3565 - Consider our directory information to have changed when our list
3566 of bridges changes. Previously, Tor would not re-compute the
3567 status of its directory information when bridges changed, and
3568 therefore would not realize that it was no longer able to build
3569 circuits. Fixes part of bug 29875.
3570 - Do not count previously configured working bridges towards our
3571 total of working bridges. Previously, when Tor's list of bridges
3572 changed, it would think that the old bridges were still usable,
3573 and delay fetching router descriptors for the new ones. Fixes part
3574 of bug 29875; bugfix on 0.3.0.1-alpha.
3576 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
3577 - When considering upgrading circuits from "waiting for guard" to
3578 "open", always ignore circuits that are marked for close. Otherwise,
3579 we can end up in the situation where a subsystem is notified that
3580 a closing circuit has just opened, leading to undesirable
3581 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
3583 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
3584 - Properly clean up the introduction point map when circuits change
3585 purpose from onion service circuits to pathbias, measurement, or
3586 other circuit types. This should fix some service-side instances
3587 of introduction point failure. Fixes bug 29034; bugfix
3590 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
3591 - Fix an unreachable bug in which an introduction point could try to
3592 send an INTRODUCE_ACK with a status code that Trunnel would refuse
3593 to encode, leading the relay to assert(). We've consolidated the
3594 ABI values into Trunnel now. Fixes bug 30454; bugfix
3596 - Clients can now handle unknown status codes from INTRODUCE_ACK
3597 cells. (The NACK behavior will stay the same.) This will allow us
3598 to extend status codes in the future without breaking the normal
3599 client behavior. Fixes another part of bug 30454; bugfix
3602 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
3603 - Relays now respect their AccountingMax bandwidth again. When
3604 relays entered "soft" hibernation (which typically starts when
3605 we've hit 90% of our AccountingMax), we had stopped checking
3606 whether we should enter hard hibernation. Soft hibernation refuses
3607 new connections and new circuits, but the existing circuits can
3608 continue, meaning that relays could have exceeded their configured
3609 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
3611 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
3612 - Stop ignoring torrc options after an %include directive, when the
3613 included directory ends with a file that does not contain any
3614 config options (but does contain comments or whitespace). Fixes
3615 bug 31408; bugfix on 0.3.1.1-alpha.
3617 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
3618 - Onion services now always use the exact number of intro points
3619 configured with the HiddenServiceNumIntroductionPoints option (or
3620 fewer if nodes are excluded). Before, a service could sometimes
3621 pick more intro points than configured. Fixes bug 31548; bugfix
3624 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
3625 - Add a "--list-modules" command to print a list of which compile-
3626 time modules are enabled. Closes ticket 30452.
3628 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
3629 - Remove sudo configuration lines from .travis.yml as they are no
3630 longer needed with current Travis build environment. Resolves
3633 o Minor features (continuous integration, backport from 0.4.1.4-rc):
3634 - Our Travis configuration now uses Chutney to run some network
3635 integration tests automatically. Closes ticket 29280.
3637 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
3638 - When building on Appveyor and Travis, pass the "-k" flag to make,
3639 so that we are informed of all compilation failures, not just the
3640 first one or two. Closes ticket 31372.
3642 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
3643 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
3644 in December 2018 (of which ~122 were still functional), with a
3645 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
3646 in June 2019. Closes ticket 28795.
3648 o Minor features (geoip, backport from 0.4.2.5):
3649 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
3650 Country database. Closes ticket 32685.
3652 o Minor features (stem tests, backport from 0.4.2.1-alpha):
3653 - Change "make test-stem" so it only runs the stem tests that use
3654 tor. This change makes test-stem faster and more reliable. Closes
3657 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
3658 - Avoid spurious errors when Appveyor CI fails before the install step.
3659 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
3661 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
3662 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
3663 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
3665 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
3666 - Fix a logic error that prevented the SessionGroup sub-option from
3667 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
3669 o Minor bugfixes (circuit padding, backport from 0.4.1.4-rc):
3670 - On relays, properly check that a padding machine is absent before
3671 logging a warning about it being absent. Fixes bug 30649; bugfix
3674 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
3675 - Fix a BUG() assertion that occurs within a very small race window
3676 between when a client intro circuit opens and when its descriptor
3677 gets cleaned up from the cache. The circuit is now closed early,
3678 which will trigger a re-fetch of the descriptor and continue the
3679 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
3681 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
3682 - Don't believe clock skew results from NETINFO cells that appear to
3683 arrive before we sent the VERSIONS cells they are responding to.
3684 Previously, we would accept them up to 3 minutes "in the past".
3685 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3687 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
3688 - Fix a compilation warning on Windows about casting a function
3689 pointer for GetTickCount64(). Fixes bug 31374; bugfix
3692 o Minor bugfixes (compilation, backport from 0.4.1.5):
3693 - Avoid using labs() on time_t, which can cause compilation warnings
3694 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3696 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
3697 - Suppress spurious float-conversion warnings from GCC when calling
3698 floating-point classifier functions on FreeBSD. Fixes part of bug
3699 31687; bugfix on 0.3.1.5-alpha.
3701 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
3702 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
3703 due to missing declarations of abort(), and prevent other such
3704 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
3706 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
3707 - Fix a bug that prevented us from supporting SOCKS5 proxies that
3708 want authentication along with configured (but unused!)
3709 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
3711 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
3712 - Avoid trying to read data from closed connections, which can cause
3713 needless loops in Libevent and infinite loops in Shadow. Fixes bug
3714 30344; bugfix on 0.1.1.1-alpha.
3716 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
3717 - Allow the test-stem job to fail in Travis, because it sometimes
3718 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
3719 - Skip test_rebind on macOS in Travis, because it is unreliable on
3720 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3721 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
3722 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3724 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
3725 - Avoid a set of possible code paths that could try to use freed
3726 memory in routerlist_free() while Tor was exiting. Fixes bug
3727 31003; bugfix on 0.1.2.2-alpha.
3729 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
3730 - Stop crashing after parsing an unknown descriptor purpose
3731 annotation. We think this bug can only be triggered by modifying a
3732 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
3734 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
3735 - Move the "bandwidth-file-headers" line in directory authority
3736 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
3739 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
3740 - On abort, try harder to flush the output buffers of log messages.
3741 On some platforms (macOS), log messages could be discarded when
3742 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3743 - Report the tor version whenever an assertion fails. Previously, we
3744 only reported the Tor version on some crashes, and some non-fatal
3745 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3747 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
3748 - When extracting an IPv6 address from a PF-based proxy, verify that
3749 we are actually configured to receive an IPv6 address, and log an
3750 internal error if not. Fixes part of bug 31687; bugfix
3753 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
3754 - When tor is missing descriptors for some primary entry guards,
3755 make the log message less alarming. It's normal for descriptors to
3756 expire, as long as tor fetches new ones soon after. Fixes bug
3757 31657; bugfix on 0.3.3.1-alpha.
3759 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
3760 - Do not log a warning when running with an OpenSSL version other
3761 than the one Tor was compiled with, if the two versions should be
3762 compatible. Previously, we would warn whenever the version was
3763 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
3765 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
3766 - Change log level of message "Hash of session info was not as
3767 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
3770 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
3771 - Rate-limit our the logging message about the obsolete .exit
3772 notation. Previously, there was no limit on this warning, which
3773 could potentially be triggered many times by a hostile website.
3774 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
3776 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
3777 - Do not log a nonfatal assertion failure when receiving a VERSIONS
3778 cell on a connection using the obsolete v1 link protocol. Log a
3779 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
3781 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
3782 - Reset the periodic events' "enabled" flag when Tor is shut down
3783 cleanly. Previously, this flag was left on, which caused periodic
3784 events not to be re-enabled when Tor was relaunched in-process
3785 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
3788 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
3789 - Avoid a minor memory leak that could occur on relays when failing
3790 to create a "keys" directory. Fixes bug 30148; bugfix
3793 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
3794 - Fix a trivial memory leak when parsing an invalid value
3795 from a download schedule in the configuration. Fixes bug
3796 30894; bugfix on 0.3.4.1-alpha.
3798 o Minor bugfixes (NetBSD, backport from 0.4.1.2-alpha):
3799 - Fix usage of minherit() on NetBSD and other platforms that define
3800 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
3801 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
3803 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
3804 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
3805 implemenation) when failing to load an onion service client
3806 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
3808 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
3809 - When purging the DNS cache because of an out-of-memory condition,
3810 try purging just the older entries at first. Previously, we would
3811 always purge the whole thing. Fixes bug 29617; bugfix
3814 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
3815 - Avoid crashing in our tor_vasprintf() implementation on systems
3816 that define neither vasprintf() nor _vscprintf(). (This bug has
3817 been here long enough that we question whether people are running
3818 Tor on such systems, but we're applying the fix out of caution.)
3819 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
3822 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
3823 - Remove overly strict assertions that triggered when a pluggable
3824 transport failed to launch. Fixes bug 31091; bugfix
3826 - Remove an assertion in the Unix process backend. This assertion
3827 would trigger when we failed to find the executable for a child
3828 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
3830 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
3831 - Avoid crashing when starting with a corrupt keys directory where
3832 the old ntor key and the new ntor key are identical. Fixes bug
3833 30916; bugfix on 0.2.4.8-alpha.
3835 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
3836 - Correctly exclude a redundant rust build job in Travis. Fixes bug
3837 31463; bugfix on 0.3.5.4-alpha.
3839 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
3840 - When testing port rebinding, don't busy-wait for tor to log.
3841 Instead, actually sleep for a short time before polling again.
3842 Also improve the formatting of control commands and log messages.
3843 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
3845 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
3846 - Log bugs about the TLS read buffer's length only once, rather than
3847 filling the logs with similar warnings. Fixes bug 31939; bugfix
3850 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
3851 - Always retry v2 single onion service intro and rend circuits with
3852 a 3-hop path. Previously, v2 single onion services used a 3-hop
3853 path when rendezvous circuits were retried after a remote or
3854 delayed failure, but a 1-hop path for immediate retries. Fixes bug
3855 23818; bugfix on 0.2.9.3-alpha.
3856 - Make v3 single onion services fall back to a 3-hop intro, when all
3857 intro points are unreachable via a 1-hop path. Previously, v3
3858 single onion services failed when all intro nodes were unreachable
3859 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
3861 o Documentation (backport from 0.4.2.1-alpha):
3862 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
3863 notice.html so that operators no longer have to host it
3864 themselves. Closes ticket 31089.
3866 o Testing (backport from 0.4.1.2-alpha):
3867 - Specify torrc paths (with empty files) when launching tor in
3868 integration tests; refrain from reading user and system torrcs.
3869 Resolves issue 29702.
3871 o Testing (continuous integration, backport from 0.4.1.1-alpha):
3872 - In Travis, show stem's tor log after failure. Closes ticket 30234.
3874 o Testing (continuous integration, backport from 0.4.1.5):
3875 - In Travis, make stem log a controller trace to the console, and
3876 tail stem's tor log after failure. Closes ticket 30591.
3877 - In Travis, only run the stem tests that use a tor binary. Closes
3880 o Testing (continuous integration, backport from 0.4.2.3-alpha):
3881 - Disable all but one Travis CI macOS build, to mitigate slow
3882 scheduling of Travis macOS jobs. Closes ticket 32177.
3883 - Run the chutney IPv6 networks as part of Travis CI. Closes
3885 - Simplify the Travis CI build matrix, and optimise for build time.
3886 Closes ticket 31859.
3887 - Use Windows Server 2019 instead of Windows Server 2016 in our
3888 Appveyor builds. Closes ticket 32086.
3890 o Testing (continuous integration, backport from 0.4.2.4-rc):
3891 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
3892 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
3893 until we can fix some Bionic permissions issues (see ticket
3894 32240). Related to ticket 31919.
3895 - Install the mingw OpenSSL package in Appveyor. This makes sure
3896 that the OpenSSL headers and libraries match in Tor's Appveyor
3897 builds. (This bug was triggered by an Appveyor image update.)
3898 Fixes bug 32449; bugfix on 0.3.5.6-rc.
3899 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
3901 o Testing (continuous integration, backport from 0.4.2.5):
3902 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
3903 extensions. Also activates clang's -Wtypedef-redefinition warnings.
3904 Build some jobs with -std=gnu99, and some jobs without.
3905 Closes ticket 32500.
3907 Changes in version 0.3.5.9 - 2019-12-09
3908 Tor 0.3.5.9 backports serveral fixes from later releases, including
3909 several that affect bridge users, relay stability, onion services,
3912 o Directory authority changes (backport from 0.4.1.5):
3913 - The directory authority "dizum" has a new IP address. Closes
3916 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
3917 - Consider our directory information to have changed when our list
3918 of bridges changes. Previously, Tor would not re-compute the
3919 status of its directory information when bridges changed, and
3920 therefore would not realize that it was no longer able to build
3921 circuits. Fixes part of bug 29875.
3922 - Do not count previously configured working bridges towards our
3923 total of working bridges. Previously, when Tor's list of bridges
3924 changed, it would think that the old bridges were still usable,
3925 and delay fetching router descriptors for the new ones. Fixes part
3926 of bug 29875; bugfix on 0.3.0.1-alpha.
3928 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
3929 - When considering upgrading circuits from "waiting for guard" to
3930 "open", always ignore circuits that are marked for close. Otherwise,
3931 we can end up in the situation where a subsystem is notified that
3932 a closing circuit has just opened, leading to undesirable
3933 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
3935 o Major bugfixes (NSS, relay, backport from 0.4.0.4-rc):
3936 - When running with NSS, disable TLS 1.2 ciphersuites that use
3937 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
3938 these ciphersuites don't work -- which caused relays to fail to
3939 handshake with one another when these ciphersuites were enabled.
3940 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
3942 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
3943 - Properly clean up the introduction point map when circuits change
3944 purpose from onion service circuits to pathbias, measurement, or
3945 other circuit types. This should fix some service-side instances
3946 of introduction point failure. Fixes bug 29034; bugfix
3949 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
3950 - Fix an unreachable bug in which an introduction point could try to
3951 send an INTRODUCE_ACK with a status code that Trunnel would refuse
3952 to encode, leading the relay to assert(). We've consolidated the
3953 ABI values into Trunnel now. Fixes bug 30454; bugfix
3955 - Clients can now handle unknown status codes from INTRODUCE_ACK
3956 cells. (The NACK behavior will stay the same.) This will allow us
3957 to extend status codes in the future without breaking the normal
3958 client behavior. Fixes another part of bug 30454; bugfix
3961 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
3962 - Stop ignoring torrc options after an %include directive, when the
3963 included directory ends with a file that does not contain any
3964 config options (but does contain comments or whitespace). Fixes
3965 bug 31408; bugfix on 0.3.1.1-alpha.
3967 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
3968 - Onion services now always use the exact number of intro points
3969 configured with the HiddenServiceNumIntroductionPoints option (or
3970 fewer if nodes are excluded). Before, a service could sometimes
3971 pick more intro points than configured. Fixes bug 31548; bugfix
3974 o Minor features (address selection, backport from 0.4.0.3-alpha):
3975 - Treat the subnet 100.64.0.0/10 as public for some purposes;
3976 private for others. This subnet is the RFC 6598 (Carrier Grade
3977 NAT) IP range, and is deployed by many ISPs as an alternative to
3978 RFC 1918 that does not break existing internal networks. Tor now
3979 blocks SOCKS and control ports on these addresses and warns users
3980 if client ports or ExtORPorts are listening on a RFC 6598 address.
3981 Closes ticket 28525. Patch by Neel Chauhan.
3983 o Minor features (bandwidth authority, backport from 0.4.0.4-rc):
3984 - Make bandwidth authorities ignore relays that are reported in the
3985 bandwidth file with the flag "vote=0". This change allows us to
3986 report unmeasured relays for diagnostic reasons without including
3987 their bandwidth in the bandwidth authorities' vote. Closes
3990 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
3991 - Add a "--list-modules" command to print a list of which compile-
3992 time modules are enabled. Closes ticket 30452.
3994 o Minor features (continuous integration, backport from 0.4.0.4-rc):
3995 - On Travis Rust builds, cleanup Rust registry and refrain from
3996 caching the "target/" directory to speed up builds. Resolves
3999 o Minor features (continuous integration, backport from 0.4.0.5):
4000 - In Travis, tell timelimit to use stem's backtrace signals, and
4001 launch python directly from timelimit, so python receives the
4002 signals from timelimit, rather than make. Closes ticket 30117.
4004 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
4005 - Remove sudo configuration lines from .travis.yml as they are no
4006 longer needed with current Travis build environment. Resolves
4009 o Minor features (continuous integration, backport from 0.4.1.4-rc):
4010 - Our Travis configuration now uses Chutney to run some network
4011 integration tests automatically. Closes ticket 29280.
4013 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
4014 - When building on Appveyor and Travis, pass the "-k" flag to make,
4015 so that we are informed of all compilation failures, not just the
4016 first one or two. Closes ticket 31372.
4018 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
4019 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
4020 in December 2018 (of which ~122 were still functional), with a
4021 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
4022 in June 2019. Closes ticket 28795.
4024 o Minor features (geoip, backport from 0.4.2.5):
4025 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
4026 Country database. Closes ticket 32685.
4028 o Minor features (NSS, diagnostic, backport from 0.4.0.4-rc):
4029 - Try to log an error from NSS (if there is any) and a more useful
4030 description of our situation if we are using NSS and a call to
4031 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
4033 o Minor features (stem tests, backport from 0.4.2.1-alpha):
4034 - Change "make test-stem" so it only runs the stem tests that use
4035 tor. This change makes test-stem faster and more reliable. Closes
4038 o Minor bugfixes (security, backport from 0.4.0.4-rc):
4039 - Verify in more places that we are not about to create a buffer
4040 with more than INT_MAX bytes, to avoid possible OOB access in the
4041 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
4042 fixed by Tobias Stoeckmann.
4043 - Fix a potential double free bug when reading huge bandwidth files.
4044 The issue is not exploitable in the current Tor network because
4045 the vulnerable code is only reached when directory authorities
4046 read bandwidth files, but bandwidth files come from a trusted
4047 source (usually the authorities themselves). Furthermore, the
4048 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
4049 which are not used by any of the current authorities. Fixes bug
4050 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
4053 o Minor bugfix (continuous integration, backport from 0.4.0.4-rc):
4054 - Reset coverage state on disk after Travis CI has finished. This
4055 should prevent future coverage merge errors from causing the test
4056 suite for the "process" subsystem to fail. The process subsystem
4057 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
4059 - Terminate test-stem if it takes more than 9.5 minutes to run.
4060 (Travis terminates the job after 10 minutes of no output.)
4061 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
4063 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
4064 - Avoid spurious errors when Appveyor CI fails before the install step.
4065 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
4067 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
4068 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
4069 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
4071 o Minor bugfixes (C correctness, backport from 0.4.0.4-rc):
4072 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
4073 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
4076 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
4077 - Fix a logic error that prevented the SessionGroup sub-option from
4078 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
4080 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
4081 - Fix a BUG() assertion that occurs within a very small race window
4082 between when a client intro circuit opens and when its descriptor
4083 gets cleaned up from the cache. The circuit is now closed early,
4084 which will trigger a re-fetch of the descriptor and continue the
4085 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
4087 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
4088 - Don't believe clock skew results from NETINFO cells that appear to
4089 arrive before we sent the VERSIONS cells they are responding to.
4090 Previously, we would accept them up to 3 minutes "in the past".
4091 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
4093 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
4094 - Fix a compilation warning on Windows about casting a function
4095 pointer for GetTickCount64(). Fixes bug 31374; bugfix
4098 o Minor bugfixes (compilation, backport from 0.4.0.2-alpha):
4099 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
4100 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
4102 o Minor bugfixes (compilation, backport from 0.4.1.5):
4103 - Avoid using labs() on time_t, which can cause compilation warnings
4104 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
4106 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
4107 - Suppress spurious float-conversion warnings from GCC when calling
4108 floating-point classifier functions on FreeBSD. Fixes part of bug
4109 31687; bugfix on 0.3.1.5-alpha.
4111 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
4112 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
4113 due to missing declarations of abort(), and prevent other such
4114 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
4116 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
4117 - Fix a bug that prevented us from supporting SOCKS5 proxies that
4118 want authentication along with configured (but unused!)
4119 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
4121 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
4122 - Avoid trying to read data from closed connections, which can cause
4123 needless loops in Libevent and infinite loops in Shadow. Fixes bug
4124 30344; bugfix on 0.1.1.1-alpha.
4126 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
4127 - Allow the test-stem job to fail in Travis, because it sometimes
4128 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
4129 - Skip test_rebind on macOS in Travis, because it is unreliable on
4130 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
4131 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
4132 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
4134 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
4135 - Avoid a set of possible code paths that could try to use freed
4136 memory in routerlist_free() while Tor was exiting. Fixes bug
4137 31003; bugfix on 0.1.2.2-alpha.
4139 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
4140 - Stop crashing after parsing an unknown descriptor purpose
4141 annotation. We think this bug can only be triggered by modifying a
4142 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
4144 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
4145 - Move the "bandwidth-file-headers" line in directory authority
4146 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
4149 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
4150 - On abort, try harder to flush the output buffers of log messages.
4151 On some platforms (macOS), log messages could be discarded when
4152 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
4153 - Report the tor version whenever an assertion fails. Previously, we
4154 only reported the Tor version on some crashes, and some non-fatal
4155 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
4157 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
4158 - When extracting an IPv6 address from a PF-based proxy, verify that
4159 we are actually configured to receive an IPv6 address, and log an
4160 internal error if not. Fixes part of bug 31687; bugfix
4163 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
4164 - When tor is missing descriptors for some primary entry guards,
4165 make the log message less alarming. It's normal for descriptors to
4166 expire, as long as tor fetches new ones soon after. Fixes bug
4167 31657; bugfix on 0.3.3.1-alpha.
4169 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
4170 - Avoid logging that we are relaxing a circuit timeout when that
4171 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
4173 o Minor bugfixes (logging, backport from 0.4.0.3-alpha):
4174 - Correct a misleading error message when IPv4Only or IPv6Only is
4175 used but the resolved address can not be interpreted as an address
4176 of the specified IP version. Fixes bug 13221; bugfix on
4177 0.2.3.9-alpha. Patch from Kris Katterjohn.
4178 - Log the correct port number for listening sockets when "auto" is
4179 used to let Tor pick the port number. Previously, port 0 was
4180 logged instead of the actual port number. Fixes bug 29144; bugfix
4181 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
4182 - Stop logging a BUG() warning when Tor is waiting for exit
4183 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
4185 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
4186 - Do not log a warning when running with an OpenSSL version other
4187 than the one Tor was compiled with, if the two versions should be
4188 compatible. Previously, we would warn whenever the version was
4189 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
4191 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
4192 - Change log level of message "Hash of session info was not as
4193 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
4196 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
4197 - Rate-limit our the logging message about the obsolete .exit
4198 notation. Previously, there was no limit on this warning, which
4199 could potentially be triggered many times by a hostile website.
4200 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
4202 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
4203 - Do not log a nonfatal assertion failure when receiving a VERSIONS
4204 cell on a connection using the obsolete v1 link protocol. Log a
4205 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
4207 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
4208 - Reset the periodic events' "enabled" flag when Tor is shut down
4209 cleanly. Previously, this flag was left on, which caused periodic
4210 events not to be re-enabled when Tor was relaunched in-process
4211 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
4214 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
4215 - Avoid a minor memory leak that could occur on relays when failing
4216 to create a "keys" directory. Fixes bug 30148; bugfix
4219 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
4220 - Fix a trivial memory leak when parsing an invalid value
4221 from a download schedule in the configuration. Fixes bug
4222 30894; bugfix on 0.3.4.1-alpha.
4224 o Minor bugfixes (memory management, backport from 0.4.0.3-alpha):
4225 - Refactor the shared random state's memory management so that it
4226 actually takes ownership of the shared random value pointers.
4227 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
4229 o Minor bugfixes (memory management, testing, backport from 0.4.0.3-alpha):
4230 - Stop leaking parts of the shared random state in the shared-random
4231 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
4233 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
4234 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
4235 implemenation) when failing to load an onion service client
4236 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
4238 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
4239 - When purging the DNS cache because of an out-of-memory condition,
4240 try purging just the older entries at first. Previously, we would
4241 always purge the whole thing. Fixes bug 29617; bugfix
4244 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
4245 - Avoid crashing in our tor_vasprintf() implementation on systems
4246 that define neither vasprintf() nor _vscprintf(). (This bug has
4247 been here long enough that we question whether people are running
4248 Tor on such systems, but we're applying the fix out of caution.)
4249 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
4252 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
4253 - Avoid crashing when starting with a corrupt keys directory where
4254 the old ntor key and the new ntor key are identical. Fixes bug
4255 30916; bugfix on 0.2.4.8-alpha.
4257 o Minor bugfixes (rust, backport from 0.4.0.5):
4258 - Abort on panic in all build profiles, instead of potentially
4259 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
4261 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
4262 - Correctly exclude a redundant rust build job in Travis. Fixes bug
4263 31463; bugfix on 0.3.5.4-alpha.
4265 o Minor bugfixes (single onion services, backport from 0.4.0.3-alpha):
4266 - Allow connections to single onion services to remain idle without
4267 being disconnected. Previously, relays acting as rendezvous points
4268 for single onion services were mistakenly closing idle rendezvous
4269 circuits after 60 seconds, thinking that they were unused
4270 directory-fetching circuits that had served their purpose. Fixes
4271 bug 29665; bugfix on 0.2.1.26.
4273 o Minor bugfixes (stats, backport from 0.4.0.3-alpha):
4274 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
4275 relay and bridge extra-info documents. Fixes bug 29017; bugfix
4278 o Minor bugfixes (testing, backport from 0.4.0.3-alpha):
4279 - Downgrade some LOG_ERR messages in the address/* tests to
4280 warnings. The LOG_ERR messages were occurring when we had no
4281 configured network. We were failing the unit tests, because we
4282 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
4283 29530; bugfix on 0.3.5.8.
4284 - Fix our gcov wrapper script to look for object files at the
4285 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
4287 o Minor bugfixes (testing, backport from 0.4.0.4-rc):
4288 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
4289 recent test-network.sh to use new chutney features in CI. Fixes
4290 bug 29703; bugfix on 0.2.9.1-alpha.
4291 - Fix a test failure on Windows caused by an unexpected "BUG"
4292 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
4295 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
4296 - When testing port rebinding, don't busy-wait for tor to log.
4297 Instead, actually sleep for a short time before polling again.
4298 Also improve the formatting of control commands and log messages.
4299 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
4301 o Minor bugfixes (TLS protocol, backport form 0.4.0.4-rc):
4302 - When classifying a client's selection of TLS ciphers, if the
4303 client ciphers are not yet available, do not cache the result.
4304 Previously, we had cached the unavailability of the cipher list
4305 and never looked again, which in turn led us to assume that the
4306 client only supported the ancient V1 link protocol. This, in turn,
4307 was causing Stem integration tests to stall in some cases. Fixes
4308 bug 30021; bugfix on 0.2.4.8-alpha.
4310 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
4311 - Log bugs about the TLS read buffer's length only once, rather than
4312 filling the logs with similar warnings. Fixes bug 31939; bugfix
4315 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
4316 - Always retry v2 single onion service intro and rend circuits with
4317 a 3-hop path. Previously, v2 single onion services used a 3-hop
4318 path when rendezvous circuits were retried after a remote or
4319 delayed failure, but a 1-hop path for immediate retries. Fixes bug
4320 23818; bugfix on 0.2.9.3-alpha.
4321 - Make v3 single onion services fall back to a 3-hop intro, when all
4322 intro points are unreachable via a 1-hop path. Previously, v3
4323 single onion services failed when all intro nodes were unreachable
4324 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
4326 o Minor bugfixes (Windows, CI, backport from 0.4.0.3-alpha):
4327 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
4328 Windows Server 2012 R2 job. The remaining 2 jobs still provide
4329 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
4330 fast_finish, so failed jobs terminate the build immediately. Fixes
4331 bug 29601; bugfix on 0.3.5.4-alpha.
4333 o Documentation (backport from 0.4.2.1-alpha):
4334 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
4335 notice.html so that operators no longer have to host it
4336 themselves. Closes ticket 31089.
4338 o Testing (backport from 0.4.1.2-alpha):
4339 - Specify torrc paths (with empty files) when launching tor in
4340 integration tests; refrain from reading user and system torrcs.
4341 Resolves issue 29702.
4343 o Testing (continuous integration, backport from 0.4.1.1-alpha):
4344 - In Travis, show stem's tor log after failure. Closes ticket 30234.
4346 o Testing (continuous integration, backport from 0.4.1.5):
4347 - In Travis, make stem log a controller trace to the console, and
4348 tail stem's tor log after failure. Closes ticket 30591.
4349 - In Travis, only run the stem tests that use a tor binary. Closes
4352 o Testing (continuous integration, backport from 0.4.2.3-alpha):
4353 - Disable all but one Travis CI macOS build, to mitigate slow
4354 scheduling of Travis macOS jobs. Closes ticket 32177.
4355 - Run the chutney IPv6 networks as part of Travis CI. Closes
4357 - Simplify the Travis CI build matrix, and optimise for build time.
4358 Closes ticket 31859.
4359 - Use Windows Server 2019 instead of Windows Server 2016 in our
4360 Appveyor builds. Closes ticket 32086.
4362 o Testing (continuous integration, backport from 0.4.2.4-rc):
4363 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
4364 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
4365 until we can fix some Bionic permissions issues (see ticket
4366 32240). Related to ticket 31919.
4367 - Install the mingw OpenSSL package in Appveyor. This makes sure
4368 that the OpenSSL headers and libraries match in Tor's Appveyor
4369 builds. (This bug was triggered by an Appveyor image update.)
4370 Fixes bug 32449; bugfix on 0.3.5.6-rc.
4371 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
4373 o Testing (continuous integration, backport from 0.4.2.5):
4374 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
4375 extensions. Also activates clang's -Wtypedef-redefinition warnings.
4376 Build some jobs with -std=gnu99, and some jobs without.
4377 Closes ticket 32500.
4379 Changes in version 0.4.2.4-rc - 2019-11-15
4380 Tor 0.4.2.4-rc is the first release candidate in its series. It fixes
4381 several bugs from earlier versions, including a few that would result in
4382 stack traces or incorrect behavior.
4384 o Minor features (build system):
4385 - Make pkg-config use --prefix when cross-compiling, if
4386 PKG_CONFIG_PATH is not set. Closes ticket 32191.
4388 o Minor features (geoip):
4389 - Update geoip and geoip6 to the November 6 2019 Maxmind GeoLite2
4390 Country database. Closes ticket 32440.
4392 o Minor bugfixes (client, onion service v3):
4393 - Fix a BUG() assertion that occurs within a very small race window
4394 between when a client intro circuit opens and when its descriptor
4395 gets cleaned up from the cache. The circuit is now closed early,
4396 which will trigger a re-fetch of the descriptor and continue the
4397 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
4399 o Minor bugfixes (code quality):
4400 - Fix "make check-includes" so it runs correctly on out-of-tree
4401 builds. Fixes bug 31335; bugfix on 0.3.5.1-alpha.
4403 o Minor bugfixes (configuration):
4404 - Log the option name when skipping an obsolete option. Fixes bug
4405 32295; bugfix on 0.4.2.1-alpha.
4407 o Minor bugfixes (crash):
4408 - When running Tor with an option like --verify-config or
4409 --dump-config that does not start the event loop, avoid crashing
4410 if we try to exit early because of an error. Fixes bug 32407;
4411 bugfix on 0.3.3.1-alpha.
4413 o Minor bugfixes (directory):
4414 - When checking if a directory connection is anonymous, test if the
4415 circuit was marked for close before looking at its channel. This
4416 avoids a BUG() stacktrace if the circuit was previously closed.
4417 Fixes bug 31958; bugfix on 0.4.2.1-alpha.
4419 o Minor bugfixes (shellcheck):
4420 - Fix minor shellcheck errors in the git-*.sh scripts. Fixes bug
4421 32402; bugfix on 0.4.2.1-alpha.
4422 - Start checking most scripts for shellcheck errors again. Fixes bug
4423 32402; bugfix on 0.4.2.1-alpha.
4425 o Testing (continuous integration):
4426 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
4427 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
4428 until we can fix some Bionic permissions issues (see ticket
4429 32240). Related to ticket 31919.
4430 - Install the mingw OpenSSL package in Appveyor. This makes sure
4431 that the OpenSSL headers and libraries match in Tor's Appveyor
4432 builds. (This bug was triggered by an Appveyor image update.)
4433 Fixes bug 32449; bugfix on 0.3.5.6-rc.
4434 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
4437 Changes in version 0.4.2.3-alpha - 2019-10-24
4438 This release fixes several bugs from the previous alpha release, and
4439 from earlier versions of Tor.
4441 o Major bugfixes (relay):
4442 - Relays now respect their AccountingMax bandwidth again. When
4443 relays entered "soft" hibernation (which typically starts when
4444 we've hit 90% of our AccountingMax), we had stopped checking
4445 whether we should enter hard hibernation. Soft hibernation refuses
4446 new connections and new circuits, but the existing circuits can
4447 continue, meaning that relays could have exceeded their configured
4448 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
4450 o Major bugfixes (v3 onion services):
4451 - Onion services now always use the exact number of intro points
4452 configured with the HiddenServiceNumIntroductionPoints option (or
4453 fewer if nodes are excluded). Before, a service could sometimes
4454 pick more intro points than configured. Fixes bug 31548; bugfix
4457 o Minor feature (onion services, control port):
4458 - The ADD_ONION command's keyword "BEST" now defaults to ED25519-V3
4459 (v3) onion services. Previously it defaulted to RSA1024 (v2).
4460 Closes ticket 29669.
4462 o Minor features (testing):
4463 - When running tests that attempt to look up hostnames, replace the
4464 libc name lookup functions with ones that do not actually touch
4465 the network. This way, the tests complete more quickly in the
4466 presence of a slow or missing DNS resolver. Closes ticket 31841.
4468 o Minor features (testing, continuous integration):
4469 - Disable all but one Travis CI macOS build, to mitigate slow
4470 scheduling of Travis macOS jobs. Closes ticket 32177.
4471 - Run the chutney IPv6 networks as part of Travis CI. Closes
4473 - Simplify the Travis CI build matrix, and optimise for build time.
4474 Closes ticket 31859.
4475 - Use Windows Server 2019 instead of Windows Server 2016 in our
4476 Appveyor builds. Closes ticket 32086.
4478 o Minor bugfixes (build system):
4479 - Interpret "--disable-module-dirauth=no" correctly. Fixes bug
4480 32124; bugfix on 0.3.4.1-alpha.
4481 - Interpret "--with-tcmalloc=no" correctly. Fixes bug 32124; bugfix
4483 - Stop failing when jemalloc is requested, but tcmalloc is not
4484 found. Fixes bug 32124; bugfix on 0.3.5.1-alpha.
4485 - When pkg-config is not installed, or a library that depends on
4486 pkg-config is not found, tell the user what to do to fix the
4487 problem. Fixes bug 31922; bugfix on 0.3.1.1-alpha.
4489 o Minor bugfixes (connections):
4490 - Avoid trying to read data from closed connections, which can cause
4491 needless loops in Libevent and infinite loops in Shadow. Fixes bug
4492 30344; bugfix on 0.1.1.1-alpha.
4494 o Minor bugfixes (error handling):
4495 - Always lock the backtrace buffer before it is used. Fixes bug
4496 31734; bugfix on 0.2.5.3-alpha.
4498 o Minor bugfixes (mainloop, periodic events, in-process API):
4499 - Reset the periodic events' "enabled" flag when Tor is shut down
4500 cleanly. Previously, this flag was left on, which caused periodic
4501 events not to be re-enabled when Tor was relaunched in-process
4502 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
4505 o Minor bugfixes (process management):
4506 - Remove overly strict assertions that triggered when a pluggable
4507 transport failed to launch. Fixes bug 31091; bugfix
4509 - Remove an assertion in the Unix process backend. This assertion
4510 would trigger when we failed to find the executable for a child
4511 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
4513 o Minor bugfixes (testing):
4514 - Avoid intermittent test failures due to a test that had relied on
4515 inconsistent timing sources. Fixes bug 31995; bugfix
4517 - When testing port rebinding, don't busy-wait for tor to log.
4518 Instead, actually sleep for a short time before polling again.
4519 Also improve the formatting of control commands and log messages.
4520 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
4522 o Minor bugfixes (tls, logging):
4523 - Log bugs about the TLS read buffer's length only once, rather than
4524 filling the logs with similar warnings. Fixes bug 31939; bugfix
4527 o Minor bugfixes (v3 onion services):
4528 - Fix an implicit conversion from ssize_t to size_t discovered by
4529 Coverity. Fixes bug 31682; bugfix on 0.4.2.1-alpha.
4530 - Fix a memory leak in an unlikely error code path when encoding HS
4531 DoS establish intro extension cell. Fixes bug 32063; bugfix
4533 - When cleaning up intro circuits for a v3 onion service, don't
4534 remove circuits that have an established or pending circuit, even
4535 if they ran out of retries. This way, we don't remove a circuit on
4536 its last retry. Fixes bug 31652; bugfix on 0.3.2.1-alpha.
4539 - Correct the description of "GuardLifetime". Fixes bug 31189;
4540 bugfix on 0.3.0.1-alpha.
4541 - Make clear in the man page, in both the bandwidth section and the
4542 AccountingMax section, that Tor counts in powers of two, not
4543 powers of ten: 1 GByte is 1024*1024*1024 bytes, not one billion
4544 bytes. Resolves ticket 32106.
4547 Changes in version 0.4.2.2-alpha - 2019-10-07
4548 This release fixes several bugs from the previous alpha release, and
4549 from earlier versions. It also includes a change in authorities, so
4550 that they begin to reject the currently unsupported release series.
4552 o Major features (directory authorities):
4553 - Directory authorities now reject relays running all currently
4554 deprecated release series. The currently supported release series
4555 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
4557 o Major bugfixes (embedded Tor):
4558 - Avoid a possible crash when restarting Tor in embedded mode and
4559 enabling a different set of publish/subscribe messages. Fixes bug
4560 31898; bugfix on 0.4.1.1-alpha.
4562 o Major bugfixes (torrc parsing):
4563 - Stop ignoring torrc options after an %include directive, when the
4564 included directory ends with a file that does not contain any
4565 config options (but does contain comments or whitespace). Fixes
4566 bug 31408; bugfix on 0.3.1.1-alpha.
4568 o Minor features (auto-formatting scripts):
4569 - When annotating C macros, never generate a line that our check-
4570 spaces script would reject. Closes ticket 31759.
4571 - When annotating C macros, try to remove cases of double-negation.
4572 Closes ticket 31779.
4574 o Minor features (continuous integration):
4575 - When building on Appveyor and Travis, pass the "-k" flag to make,
4576 so that we are informed of all compilation failures, not just the
4577 first one or two. Closes ticket 31372.
4579 o Minor features (geoip):
4580 - Update geoip and geoip6 to the October 1 2019 Maxmind GeoLite2
4581 Country database. Closes ticket 31931.
4583 o Minor features (maintenance scripts):
4584 - Add a Coccinelle script to detect bugs caused by incrementing or
4585 decrementing a variable inside a call to log_debug(). Since
4586 log_debug() is a macro whose arguments are conditionally
4587 evaluated, it is usually an error to do this. One such bug was
4588 30628, in which SENDME cells were miscounted by a decrement
4589 operator inside a log_debug() call. Closes ticket 30743.
4591 o Minor features (onion services v3):
4592 - Assist users who try to setup v2 client authorization in v3 onion
4593 services by pointing them to the right documentation. Closes
4596 o Minor bugfixes (Appveyor continuous integration):
4597 - Avoid spurious errors when Appveyor CI fails before the install
4598 step. Fixes bug 31884; bugfix on 0.3.4.2-alpha.
4600 o Minor bugfixes (best practices tracker):
4601 - When listing overbroad exceptions, do not also list problems, and
4602 do not list insufficiently broad exceptions. Fixes bug 31338;
4603 bugfix on 0.4.2.1-alpha.
4605 o Minor bugfixes (controller protocol):
4606 - Fix the MAPADDRESS controller command to accept one or more
4607 arguments. Previously, it required two or more arguments, and
4608 ignored the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
4610 o Minor bugfixes (logging):
4611 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
4612 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
4613 - Disable backtrace signal handlers when shutting down tor. Fixes
4614 bug 31614; bugfix on 0.2.5.2-alpha.
4615 - Rate-limit our the logging message about the obsolete .exit
4616 notation. Previously, there was no limit on this warning, which
4617 could potentially be triggered many times by a hostile website.
4618 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
4619 - When initialising log domain masks, only set known log domains.
4620 Fixes bug 31854; bugfix on 0.2.1.1-alpha.
4622 o Minor bugfixes (logging, protocol violations):
4623 - Do not log a nonfatal assertion failure when receiving a VERSIONS
4624 cell on a connection using the obsolete v1 link protocol. Log a
4625 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
4627 o Minor bugfixes (modules):
4628 - Explain what the optional Directory Authority module is, and what
4629 happens when it is disabled. Fixes bug 31825; bugfix
4632 o Minor bugfixes (multithreading):
4633 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
4634 31736; bugfix on 0.0.7.
4636 o Minor bugfixes (relay):
4637 - Avoid crashing when starting with a corrupt keys directory where
4638 the old ntor key and the new ntor key are identical. Fixes bug
4639 30916; bugfix on 0.2.4.8-alpha.
4641 o Minor bugfixes (tests, SunOS):
4642 - Avoid a map_anon_nofork test failure due to a signed/unsigned
4643 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
4645 o Code simplification and refactoring:
4646 - Refactor connection_control_process_inbuf() to reduce the size of
4647 a practracker exception. Closes ticket 31840.
4648 - Refactor the microdescs_parse_from_string() function into smaller
4649 pieces, for better comprehensibility. Closes ticket 31675.
4650 - Use SEVERITY_MASK_IDX() to find the LOG_* mask indexes in the unit
4651 tests and fuzzers, rather than using hard-coded values. Closes
4653 - Interface for function `decrypt_desc_layer` cleaned up. Closes
4657 - Document the signal-safe logging behaviour in the tor man page.
4658 Also add some comments to the relevant functions. Closes
4660 - Explain why we can't destroy the backtrace buffer mutex. Explain
4661 why we don't need to destroy the log mutex. Closes ticket 31736.
4662 - The Tor source code repository now includes a (somewhat dated)
4663 description of Tor's modular architecture, in doc/HACKING/design.
4664 This is based on the old "tor-guts.git" repository, which we are
4665 adopting and superseding. Closes ticket 31849.
4668 Changes in version 0.4.1.6 - 2019-09-19
4669 This release backports several bugfixes to improve stability and
4670 correctness. Anyone experiencing build problems or crashes with 0.4.1.5,
4671 or experiencing reliability issues with single onion services, should
4674 o Major bugfixes (crash, Linux, Android, backport from 0.4.2.1-alpha):
4675 - Tolerate systems (including some Android installations) where
4676 madvise and MADV_DONTDUMP are available at build-time, but not at
4677 run time. Previously, these systems would notice a failed syscall
4678 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
4679 - Tolerate systems (including some Linux installations) where
4680 madvise and/or MADV_DONTFORK are available at build-time, but not
4681 at run time. Previously, these systems would notice a failed
4682 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
4684 o Minor features (stem tests, backport from 0.4.2.1-alpha):
4685 - Change "make test-stem" so it only runs the stem tests that use
4686 tor. This change makes test-stem faster and more reliable. Closes
4689 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
4690 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
4691 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
4693 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
4694 - Add more stub functions to fix compilation on Android with link-
4695 time optimization when --disable-module-dirauth is used.
4696 Previously, these compilation settings would make the compiler
4697 look for functions that didn't exist. Fixes bug 31552; bugfix
4699 - Suppress spurious float-conversion warnings from GCC when calling
4700 floating-point classifier functions on FreeBSD. Fixes part of bug
4701 31687; bugfix on 0.3.1.5-alpha.
4703 o Minor bugfixes (controller protocol):
4704 - Fix the MAPADDRESS controller command to accept one or more
4705 arguments. Previously, it required two or more arguments, and ignored
4706 the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
4708 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
4709 - When extracting an IPv6 address from a PF-based proxy, verify that
4710 we are actually configured to receive an IPv6 address, and log an
4711 internal error if not. Fixes part of bug 31687; bugfix
4714 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
4715 - When tor is missing descriptors for some primary entry guards,
4716 make the log message less alarming. It's normal for descriptors to
4717 expire, as long as tor fetches new ones soon after. Fixes bug
4718 31657; bugfix on 0.3.3.1-alpha.
4720 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
4721 - Change log level of message "Hash of session info was not as
4722 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
4725 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
4726 - Correctly exclude a redundant rust build job in Travis. Fixes bug
4727 31463; bugfix on 0.3.5.4-alpha.
4729 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
4730 - Always retry v2 single onion service intro and rend circuits with
4731 a 3-hop path. Previously, v2 single onion services used a 3-hop
4732 path when rendezvous circuits were retried after a remote or
4733 delayed failure, but a 1-hop path for immediate retries. Fixes bug
4734 23818; bugfix on 0.2.9.3-alpha.
4736 o Minor bugfixes (v3 single onion services, backport from 0.4.2.1-alpha):
4737 - Always retry v3 single onion service intro and rend circuits with
4738 a 3-hop path. Previously, v3 single onion services used a 3-hop
4739 path when rend circuits were retried after a remote or delayed
4740 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
4741 bugfix on 0.3.2.1-alpha.
4742 - Make v3 single onion services fall back to a 3-hop intro, when all
4743 intro points are unreachable via a 1-hop path. Previously, v3
4744 single onion services failed when all intro nodes were unreachable
4745 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
4747 o Documentation (backport from 0.4.2.1-alpha):
4748 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
4749 notice.html so that operators no longer have to host it
4750 themselves. Closes ticket 31089.
4753 Changes in version 0.4.2.1-alpha - 2019-09-17
4754 This is the first alpha release in the 0.4.2.x series. It adds new
4755 defenses for denial-of-service attacks against onion services. It also
4756 includes numerous kinds of bugfixes and refactoring to help improve
4757 Tor's stability and ease of development.
4759 o Major features (onion service v3, denial of service):
4760 - Add onion service introduction denial of service defenses. Intro
4761 points can now rate-limit client introduction requests, using
4762 parameters that can be sent by the service within the
4763 ESTABLISH_INTRO cell. If the cell extension for this is not used,
4764 the intro point will honor the consensus parameters. Closes
4767 o Major bugfixes (circuit build, guard):
4768 - When considering upgrading circuits from "waiting for guard" to
4769 "open", always ignore circuits that are marked for close.
4770 Previously we could end up in the situation where a subsystem is
4771 notified of a circuit opening, but the circuit is still marked for
4772 close, leading to undesirable behavior. Fixes bug 30871; bugfix
4775 o Major bugfixes (crash, Linux, Android):
4776 - Tolerate systems (including some Android installations) where
4777 madvise and MADV_DONTDUMP are available at build-time, but not at
4778 run time. Previously, these systems would notice a failed syscall
4779 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
4780 - Tolerate systems (including some Linux installations) where
4781 madvise and/or MADV_DONTFORK are available at build-time, but not
4782 at run time. Previously, these systems would notice a failed
4783 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
4785 o Minor features (best practices tracker):
4786 - Our best-practices tracker now integrates with our include-checker
4787 tool to keep track of how many layering violations we have not yet
4788 fixed. We hope to reduce this number over time to improve Tor's
4789 modularity. Closes ticket 31176.
4790 - Add a TOR_PRACTRACKER_OPTIONS variable for passing arguments to
4791 practracker from the environment. We may want this for continuous
4792 integration. Closes ticket 31309.
4793 - Give a warning rather than an error when a practracker exception
4794 is violated by a small amount, add a --list-overbroad option to
4795 practracker that lists exceptions that are stricter than they need
4796 to be, and provide an environment variable for disabling
4797 practracker. Closes ticket 30752.
4798 - Our best-practices tracker now looks at headers as well as C
4799 files. Closes ticket 31175.
4801 o Minor features (build system):
4802 - Add --disable-manpage and --disable-html-manual options to
4803 configure script. This will enable shortening build times by not
4804 building documentation. Resolves issue 19381.
4806 o Minor features (compilation):
4807 - Log a more useful error message when we are compiling and one of
4808 the compile-time hardening options we have selected can be linked
4809 but not executed. Closes ticket 27530.
4811 o Minor features (configuration):
4812 - The configuration code has been extended to allow splitting
4813 configuration data across multiple objects. Previously, all
4814 configuration data needed to be kept in a single object, which
4815 tended to become bloated. Closes ticket 31240.
4817 o Minor features (continuous integration):
4818 - When running CI builds on Travis, put some random data in
4819 ~/.torrc, to make sure no tests are reading the Tor configuration
4820 file from its default location. Resolves issue 30102.
4822 o Minor features (debugging):
4823 - Log a nonfatal assertion failure if we encounter a configuration
4824 line whose command is "CLEAR" but which has a nonempty value. This
4825 should be impossible, according to the rules of our configuration
4826 line parsing. Closes ticket 31529.
4828 o Minor features (git hooks):
4829 - Our pre-commit git hook now checks for a special file before
4830 running practracker, so that practracker only runs on branches
4831 that are based on master. Since the pre-push hook calls the pre-
4832 commit hook, practracker will also only run before pushes of
4833 branches based on master. Closes ticket 30979.
4835 o Minor features (git scripts):
4836 - Add a "--" command-line argument, to separate git-push-all.sh
4837 script arguments from arguments that are passed through to git
4838 push. Closes ticket 31314.
4839 - Add a -r <remote-name> argument to git-push-all.sh, so the script
4840 can push test branches to a personal remote. Closes ticket 31314.
4841 - Add a -t <test-branch-prefix> argument to git-merge-forward.sh and
4842 git-push-all.sh, which makes these scripts create, merge forward,
4843 and push test branches. Closes ticket 31314.
4844 - Add a -u argument to git-merge-forward.sh, so that the script can
4845 re-use existing test branches after a merge failure and fix.
4846 Closes ticket 31314.
4847 - Add a TOR_GIT_PUSH env var, which sets the default git push
4848 command and arguments for git-push-all.sh. Closes ticket 31314.
4849 - Add a TOR_PUSH_DELAY variable to git-push-all.sh, which makes the
4850 script push master and maint branches with a delay between each
4851 branch. These delays trigger the CI jobs in a set order, which
4852 should show the most likely failures first. Also make pushes
4853 atomic by default, and make the script pass any command-line
4854 arguments to git push. Closes ticket 29879.
4855 - Call the shellcheck script from the pre-commit hook. Closes
4857 - Skip pushing test branches that are the same as a remote
4858 maint/release/master branch in git-push-all.sh by default. Add a
4859 -s argument, so git-push-all.sh can push all test branches. Closes
4862 o Minor features (IPv6, logging):
4863 - Log IPv6 addresses as well as IPv4 addresses when describing
4864 routerinfos, routerstatuses, and nodes. Closes ticket 21003.
4866 o Minor features (onion service v3):
4867 - Do not allow single hop clients to fetch or post an HS descriptor
4868 from an HSDir. Closes ticket 24964.
4870 o Minor features (onion service):
4871 - Disallow single-hop clients at the introduction point. We've
4872 removed Tor2web support a while back and single-hop rendezvous
4873 attempts are blocked at the relays. This change should remove load
4874 off the network from spammy clients. Close ticket 24963.
4876 o Minor features (stem tests):
4877 - Change "make test-stem" so it only runs the stem tests that use
4878 tor. This change makes test-stem faster and more reliable. Closes
4881 o Minor features (testing):
4882 - Add a script to invoke "tor --dump-config" and "tor
4883 --verify-config" with various configuration options, and see
4884 whether tor's resulting configuration or error messages are what
4885 we expect. Use it for integration testing of our +Option and
4886 /Option flags. Closes ticket 31637.
4887 - Improve test coverage for our existing configuration parsing and
4888 management API. Closes ticket 30893.
4889 - Add integration tests to make sure that practracker gives the
4890 outputs we expect. Closes ticket 31477.
4891 - The practracker self-tests are now run as part of the Tor test
4892 suite. Closes ticket 31304.
4894 o Minor features (token bucket):
4895 - Implement a generic token bucket that uses a single counter, for
4896 use in anti-DoS onion service work. Closes ticket 30687.
4898 o Minor bugfixes (best practices tracker):
4899 - Fix a few issues in the best-practices script, including tests,
4900 tab tolerance, error reporting, and directory-exclusion logic.
4901 Fixes bug 29746; bugfix on 0.4.1.1-alpha.
4902 - When running check-best-practices, only consider files in the src
4903 subdirectory. Previously we had recursively considered all
4904 subdirectories, which made us get confused by the temporary
4905 directories made by "make distcheck". Fixes bug 31578; bugfix
4908 o Minor bugfixes (build system):
4909 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
4910 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
4912 o Minor bugfixes (chutney, makefiles, documentation):
4913 - "make test-network-all" now shows the warnings from each test-
4914 network.sh run on the console, so developers see new warnings
4915 early. We've also improved the documentation for this feature, and
4916 renamed a Makefile variable so the code is self-documenting. Fixes
4917 bug 30455; bugfix on 0.3.0.4-rc.
4919 o Minor bugfixes (compilation):
4920 - Add more stub functions to fix compilation on Android with link-
4921 time optimization when --disable-module-dirauth is used.
4922 Previously, these compilation settings would make the compiler
4923 look for functions that didn't exist. Fixes bug 31552; bugfix
4925 - Suppress spurious float-conversion warnings from GCC when calling
4926 floating-point classifier functions on FreeBSD. Fixes part of bug
4927 31687; bugfix on 0.3.1.5-alpha.
4929 o Minor bugfixes (configuration):
4930 - Invalid floating-point values in the configuration file are now
4931 treated as errors in the configuration. Previously, they were
4932 ignored and treated as zero. Fixes bug 31475; bugfix on 0.0.1.
4934 o Minor bugfixes (coverity):
4935 - Add an assertion when parsing a BEGIN cell so that coverity can be
4936 sure that we are not about to dereference a NULL address. Fixes
4937 bug 31026; bugfix on 0.2.4.7-alpha. This is CID 1447296.
4938 - In our siphash implementation, when building for coverity, use
4939 memcpy in place of a switch statement, so that coverity can tell
4940 we are not accessing out-of-bounds memory. Fixes bug 31025; bugfix
4941 on 0.2.8.1-alpha. This is tracked as CID 1447293 and 1447295.
4942 - Fix several coverity warnings from our unit tests. Fixes bug
4943 31030; bugfix on 0.2.4.1-alpha, 0.3.2.1-alpha, and 0.4.0.1-alpha.
4945 o Minor bugfixes (developer tooling):
4946 - Only log git script changes in the post-merge script when the
4947 merge was to the master branch. Fixes bug 31040; bugfix
4950 o Minor bugfixes (directory authorities):
4951 - Return a distinct status when formatting annotations fails. Fixes
4952 bug 30780; bugfix on 0.2.0.8-alpha.
4954 o Minor bugfixes (error handling):
4955 - On abort, try harder to flush the output buffers of log messages.
4956 On some platforms (macOS), log messages could be discarded when
4957 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
4958 - Report the tor version whenever an assertion fails. Previously, we
4959 only reported the Tor version on some crashes, and some non-fatal
4960 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
4961 - When tor aborts due to an error, close log file descriptors before
4962 aborting. Closing the logs makes some OSes flush log file buffers,
4963 rather than deleting buffered log lines. Fixes bug 31594; bugfix
4966 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6):
4967 - When extracting an IPv6 address from a PF-based proxy, verify that
4968 we are actually configured to receive an IPv6 address, and log an
4969 internal error if not. Fixes part of bug 31687; bugfix
4972 o Minor bugfixes (git hooks):
4973 - Remove a duplicate call to practracker from the pre-push hook. The
4974 pre-push hook already calls the pre-commit hook, which calls
4975 practracker. Fixes bug 31462; bugfix on 0.4.1.1-alpha.
4977 o Minor bugfixes (git scripts):
4978 - Stop hard-coding the bash path in the git scripts. Some OSes don't
4979 have bash in /usr/bin, others have an ancient bash at this path.
4980 Fixes bug 30840; bugfix on 0.4.0.1-alpha.
4981 - Stop hard-coding the tor master branch name and worktree path in
4982 the git scripts. Fixes bug 30841; bugfix on 0.4.0.1-alpha.
4983 - Allow git-push-all.sh to be run from any directory. Previously,
4984 the script only worked if run from an upstream worktree directory.
4985 Closes ticket 31678.
4987 o Minor bugfixes (guards):
4988 - When tor is missing descriptors for some primary entry guards,
4989 make the log message less alarming. It's normal for descriptors to
4990 expire, as long as tor fetches new ones soon after. Fixes bug
4991 31657; bugfix on 0.3.3.1-alpha.
4993 o Minor bugfixes (ipv6):
4994 - Check for private IPv6 addresses alongside their IPv4 equivalents
4995 when authorities check descriptors. Previously, we only checked
4996 for private IPv4 addresses. Fixes bug 31088; bugfix on
4997 0.2.3.21-rc. Patch by Neel Chauhan.
4998 - When parsing microdescriptors, we should check the IPv6 exit
4999 policy alongside IPv4. Previously, we checked both exit policies
5000 for only router info structures, while microdescriptors were
5001 IPv4-only. Fixes bug 27284; bugfix on 0.2.3.1-alpha. Patch by
5004 o Minor bugfixes (logging):
5005 - Change log level of message "Hash of session info was not as
5006 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
5008 - Fix a code issue that would have broken our parsing of log domains
5009 as soon as we had 33 of them. Fortunately, we still only have 29.
5010 Fixes bug 31451; bugfix on 0.4.1.4-rc.
5012 o Minor bugfixes (memory management):
5013 - Stop leaking a small amount of memory in nt_service_install(), in
5014 unreachable code. Fixes bug 30799; bugfix on 0.2.0.7-alpha. Patch
5017 o Minor bugfixes (networking, IP addresses):
5018 - When parsing addresses via Tor's internal DNS lookup API, reject
5019 IPv4 addresses in square brackets, and accept IPv6 addresses in
5020 square brackets. This change completes the work started in 23082,
5021 making address parsing consistent between tor's internal DNS
5022 lookup and address parsing APIs. Fixes bug 30721; bugfix
5024 - When parsing addresses via Tor's internal address:port parsing and
5025 DNS lookup APIs, require IPv6 addresses with ports to have square
5026 brackets. But allow IPv6 addresses without ports, whether or not
5027 they have square brackets. Fixes bug 30721; bugfix
5030 o Minor bugfixes (onion service v3):
5031 - When purging the client descriptor cache, close any introduction
5032 point circuits associated with purged cache entries. This avoids
5033 picking those circuits later when connecting to the same
5034 introduction points. Fixes bug 30921; bugfix on 0.3.2.1-alpha.
5036 o Minor bugfixes (onion services):
5037 - In the hs_ident_circuit_t data structure, remove the unused field
5038 circuit_type and the respective argument in hs_ident_circuit_new().
5039 This field was set by clients (for introduction) and services (for
5040 introduction and rendezvous) but was never used afterwards. Fixes
5041 bug 31490; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
5043 o Minor bugfixes (operator tools):
5044 - Make tor-print-ed-signing-cert(1) print certificate expiration
5045 date in RFC 1123 and UNIX timestamp formats, to make output
5046 machine readable. Fixes bug 31012; bugfix on 0.3.5.1-alpha.
5048 o Minor bugfixes (rust):
5049 - Correctly exclude a redundant rust build job in Travis. Fixes bug
5050 31463; bugfix on 0.3.5.4-alpha.
5051 - Raise the minimum rustc version to 1.31.0, as checked by configure
5052 and CI. Fixes bug 31442; bugfix on 0.3.5.4-alpha.
5054 o Minor bugfixes (sendme, code structure):
5055 - Rename the trunnel SENDME file definition from sendme.trunnel to
5056 sendme_cell.trunnel to avoid having twice sendme.{c|h} in the
5057 repository. Fixes bug 30769; bugfix on 0.4.1.1-alpha.
5059 o Minor bugfixes (statistics):
5060 - Stop removing the ed25519 signature if the extra info file is too
5061 big. If the signature data was removed, but the keyword was kept,
5062 this could result in an unparseable extra info file. Fixes bug
5063 30958; bugfix on 0.2.7.2-alpha.
5065 o Minor bugfixes (subsystems):
5066 - Make the subsystem init order match the subsystem module
5067 dependencies. Call windows process security APIs as early as
5068 possible. Initialize logging before network and time, so that
5069 network and time can use logging. Fixes bug 31615; bugfix
5072 o Minor bugfixes (testing):
5073 - Teach the util/socketpair_ersatz test to work correctly when we
5074 have no network stack configured. Fixes bug 30804; bugfix
5077 o Minor bugfixes (v2 single onion services):
5078 - Always retry v2 single onion service intro and rend circuits with
5079 a 3-hop path. Previously, v2 single onion services used a 3-hop
5080 path when rendezvous circuits were retried after a remote or
5081 delayed failure, but a 1-hop path for immediate retries. Fixes bug
5082 23818; bugfix on 0.2.9.3-alpha.
5084 o Minor bugfixes (v3 single onion services):
5085 - Always retry v3 single onion service intro and rend circuits with
5086 a 3-hop path. Previously, v3 single onion services used a 3-hop
5087 path when rend circuits were retried after a remote or delayed
5088 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
5089 bugfix on 0.3.2.1-alpha.
5090 - Make v3 single onion services fall back to a 3-hop intro, when all
5091 intro points are unreachable via a 1-hop path. Previously, v3
5092 single onion services failed when all intro nodes were unreachable
5093 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
5096 - Improve documentation in circuit padding subsystem. Patch by
5097 Tobias Pulls. Closes ticket 31113.
5098 - Include an example usage for IPv6 ORPort in our sample torrc.
5099 Closes ticket 31320; patch from Ali Raheem.
5100 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
5101 notice.html so that operators no longer have to host it
5102 themselves. Closes ticket 31089.
5105 - No longer include recommended package digests in votes as detailed
5106 in proposal 301. The RecommendedPackages torrc option is
5107 deprecated and will no longer have any effect. "package" lines
5108 will still be considered when computing consensuses for consensus
5109 methods that include them. (This change has no effect on the list
5110 of recommended Tor versions, which is still in use.) Closes
5112 - Remove torctl.in from contrib/dist directory. Resolves
5116 - Run shellcheck for all non-third-party shell scripts that are
5117 shipped with Tor. Closes ticket 29533.
5118 - When checking shell scripts, ignore any user-created directories.
5119 Closes ticket 30967.
5121 o Code simplification and refactoring (config handling):
5122 - Extract our variable manipulation code from confparse.c to a new
5123 lower-level typedvar.h module. Closes ticket 30864.
5124 - Lower another layer of object management from confparse.c to a
5125 more general tool. Now typed structure members are accessible via
5126 an abstract type. Implements ticket 30914.
5127 - Move our backend logic for working with configuration and state
5128 files into a lower-level library, since it no longer depends on
5129 any tor-specific functionality. Closes ticket 31626.
5130 - Numerous simplifications in configuration-handling logic: remove
5131 duplicated macro definitions, replace magical names with flags,
5132 and refactor "TestingTorNetwork" to use the same default-option
5133 logic as the rest of Tor. Closes ticket 30935.
5134 - Replace our ad-hoc set of flags for configuration variables and
5135 configuration variable types with fine-grained orthogonal flags
5136 corresponding to the actual behavior we want. Closes ticket 31625.
5138 o Code simplification and refactoring (misc):
5139 - Eliminate some uses of lower-level control reply abstractions,
5140 primarily in the onion_helper functions. Closes ticket 30889.
5141 - Rework bootstrap tracking to use the new publish-subscribe
5142 subsystem. Closes ticket 29976.
5143 - Rewrite format_node_description() and router_get_verbose_nickname()
5144 to use strlcpy() and strlcat(). The previous implementation used
5145 memcpy() and pointer arithmetic, which was error-prone. Closes
5146 ticket 31545. This is CID 1452819.
5147 - Split extrainfo_dump_to_string() into smaller functions. Closes
5149 - Use the ptrdiff_t type consistently for expressing variable
5150 offsets and pointer differences. Previously we incorrectly (but
5151 harmlessly) used int and sometimes off_t for these cases. Closes
5153 - Use the subsystems mechanism to manage the main event loop code.
5154 Closes ticket 30806.
5155 - Various simplifications and minor improvements to the circuit
5156 padding machines. Patch by Tobias Pulls. Closes tickets 31112
5159 o Documentation (hard-coded directories):
5160 - Improve the documentation for the DirAuthority and FallbackDir
5161 torrc options. Closes ticket 30955.
5163 o Documentation (tor.1 man page):
5164 - Fix typo in tor.1 man page: the option is "--help", not "-help".
5165 Fixes bug 31008; bugfix on 0.2.2.9-alpha.
5168 Changes in version 0.4.1.5 - 2019-08-20
5169 This is the first stable release in the 0.4.1.x series. This series
5170 adds experimental circuit-level padding, authenticated SENDME cells to
5171 defend against certain attacks, and several performance improvements
5172 to save on CPU consumption. It fixes bugs in bootstrapping and v3
5173 onion services. It also includes numerous smaller features and
5174 bugfixes on earlier versions.
5176 Per our support policy, we will support the 0.4.1.x series for nine
5177 months, or until three months after the release of a stable 0.4.2.x:
5178 whichever is longer. If you need longer-term support, please stick
5179 with 0.3.5.x, which will we plan to support until Feb 2022.
5181 Below are the changes since 0.4.1.4-rc. For a complete list of changes
5182 since 0.4.0.5, see the ReleaseNotes file.
5184 o Directory authority changes:
5185 - The directory authority "dizum" has a new IP address. Closes
5188 o Minor features (circuit padding logging):
5189 - Demote noisy client-side warn logs about circuit padding to
5190 protocol warnings. Add additional log messages and circuit ID
5191 fields to help with bug 30992 and any other future issues.
5193 o Minor bugfixes (circuit padding negotiation):
5194 - Bump the circuit padding protocol version to explicitly signify
5195 that the HS setup machine support is finalized in 0.4.1.x-stable.
5196 This also means that 0.4.1.x-alpha clients will not negotiate
5197 padding with 0.4.1.x-stable relays, and 0.4.1.x-stable clients
5198 will not negotiate padding with 0.4.1.x-alpha relays (or 0.4.0.x
5199 relays). Fixes bug 31356; bugfix on 0.4.1.1-alpha.
5201 o Minor bugfixes (circuit padding):
5202 - Ignore non-padding cells on padding circuits. This addresses
5203 various warning messages from subsystems that were not expecting
5204 padding circuits. Fixes bug 30942; bugfix on 0.4.1.1-alpha.
5206 o Minor bugfixes (clock skew detection):
5207 - Don't believe clock skew results from NETINFO cells that appear to
5208 arrive before we sent the VERSIONS cells they are responding to.
5209 Previously, we would accept them up to 3 minutes "in the past".
5210 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
5212 o Minor bugfixes (compatibility, standards compliance):
5213 - Fix a bug that would invoke undefined behavior on certain
5214 operating systems when trying to asprintf() a string exactly
5215 INT_MAX bytes long. We don't believe this is exploitable, but it's
5216 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
5217 Found and fixed by Tobias Stoeckmann.
5219 o Minor bugfixes (compilation warning):
5220 - Fix a compilation warning on Windows about casting a function
5221 pointer for GetTickCount64(). Fixes bug 31374; bugfix
5224 o Minor bugfixes (compilation):
5225 - Avoid using labs() on time_t, which can cause compilation warnings
5226 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
5228 o Minor bugfixes (distribution):
5229 - Do not ship any temporary files found in the
5230 scripts/maint/practracker directory. Fixes bug 31311; bugfix
5233 o Testing (continuous integration):
5234 - In Travis, make stem log a controller trace to the console, and
5235 tail stem's tor log after failure. Closes ticket 30591.
5236 - In Travis, only run the stem tests that use a tor binary. Closes
5240 Changes in version 0.4.1.4-rc - 2019-07-25
5241 Tor 0.4.1.4-rc fixes a few bugs from previous versions of Tor, and
5242 updates to a new list of fallback directories. If no new bugs are
5243 found, the next release in the 0.4.1.x serious should be stable.
5245 o Major bugfixes (circuit build, guard):
5246 - When considering upgrading circuits from "waiting for guard" to
5247 "open", always ignore circuits that are marked for close. Otherwise,
5248 we can end up in the situation where a subsystem is notified that
5249 a closing circuit has just opened, leading to undesirable
5250 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
5252 o Minor features (continuous integration):
5253 - Our Travis configuration now uses Chutney to run some network
5254 integration tests automatically. Closes ticket 29280.
5256 o Minor features (fallback directory list):
5257 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
5258 in December 2018 (of which ~122 were still functional), with a
5259 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
5260 in June 2019. Closes ticket 28795.
5262 o Minor bugfixes (circuit padding):
5263 - On relays, properly check that a padding machine is absent before
5264 logging a warning about it being absent. Fixes bug 30649; bugfix
5266 - Add two NULL checks in unreachable places to silence Coverity (CID
5267 144729 and 1447291) and better future-proof ourselves. Fixes bug
5268 31024; bugfix on 0.4.1.1-alpha.
5270 o Minor bugfixes (crash on exit):
5271 - Avoid a set of possible code paths that could try to use freed
5272 memory in routerlist_free() while Tor was exiting. Fixes bug
5273 31003; bugfix on 0.1.2.2-alpha.
5275 o Minor bugfixes (logging):
5276 - Fix a conflict between the flag used for messaging-domain log
5277 messages, and the LD_NO_MOCK testing flag. Fixes bug 31080; bugfix
5280 o Minor bugfixes (memory leaks):
5281 - Fix a trivial memory leak when parsing an invalid value from a
5282 download schedule in the configuration. Fixes bug 30894; bugfix
5285 o Code simplification and refactoring:
5286 - Remove some dead code from circpad_machine_remove_token() to fix
5287 some Coverity warnings (CID 1447298). Fixes bug 31027; bugfix
5291 Changes in version 0.4.1.3-alpha - 2019-06-25
5292 Tor 0.4.1.3-alpha resolves numerous bugs left over from the previous
5293 alpha, most of them from earlier release series.
5295 o Major bugfixes (Onion service reachability):
5296 - Properly clean up the introduction point map when circuits change
5297 purpose from onion service circuits to pathbias, measurement, or
5298 other circuit types. This should fix some service-side instances
5299 of introduction point failure. Fixes bug 29034; bugfix
5302 o Minor features (geoip):
5303 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
5304 Country database. Closes ticket 30852.
5306 o Minor features (logging):
5307 - Give a more useful assertion failure message if we think we have
5308 minherit() but we fail to make a region non-inheritable. Give a
5309 compile-time warning if our support for minherit() is incomplete.
5310 Closes ticket 30686.
5312 o Minor bugfixes (circuit isolation):
5313 - Fix a logic error that prevented the SessionGroup sub-option from
5314 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
5316 o Minor bugfixes (continuous integration):
5317 - Allow the test-stem job to fail in Travis, because it sometimes
5318 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
5319 - Skip test_rebind on macOS in Travis, because it is unreliable on
5320 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
5321 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
5322 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
5324 o Minor bugfixes (directory authorities):
5325 - Stop crashing after parsing an unknown descriptor purpose
5326 annotation. We think this bug can only be triggered by modifying a
5327 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
5329 o Minor bugfixes (pluggable transports):
5330 - When running as a bridge with pluggable transports, always publish
5331 pluggable transport information in our extrainfo descriptor, even
5332 if ExtraInfoStatistics is 0. This information is needed by
5333 BridgeDB. Fixes bug 30956; bugfix on 0.4.1.1-alpha.
5336 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
5337 Closes ticket 30630.
5340 Changes in version 0.4.1.2-alpha - 2019-06-06
5341 Tor 0.4.1.2-alpha resolves numerous bugs--some of them from the
5342 previous alpha, and some much older. It also contains minor testing
5343 improvements, and an improvement to the security of our authenticated
5344 SENDME implementation.
5346 o Major bugfixes (bridges):
5347 - Consider our directory information to have changed when our list
5348 of bridges changes. Previously, Tor would not re-compute the
5349 status of its directory information when bridges changed, and
5350 therefore would not realize that it was no longer able to build
5351 circuits. Fixes part of bug 29875.
5352 - Do not count previously configured working bridges towards our
5353 total of working bridges. Previously, when Tor's list of bridges
5354 changed, it would think that the old bridges were still usable,
5355 and delay fetching router descriptors for the new ones. Fixes part
5356 of bug 29875; bugfix on 0.3.0.1-alpha.
5358 o Major bugfixes (flow control, SENDME):
5359 - Decrement the stream-level package window after packaging a cell.
5360 Previously, it was done inside a log_debug() call, meaning that if
5361 debug logs were not enabled, the decrement would never happen, and
5362 thus the window would be out of sync with the other end point.
5363 Fixes bug 30628; bugfix on 0.4.1.1-alpha.
5365 o Major bugfixes (onion service reachability):
5366 - Properly clean up the introduction point map and associated state
5367 when circuits change purpose from onion service circuits to
5368 pathbias, measurement, or other circuit types. This may fix some
5369 instances of introduction point failure. Fixes bug 29034; bugfix
5372 o Minor features (authenticated SENDME):
5373 - Ensure that there is enough randomness on every circuit to prevent
5374 an attacker from successfully predicting the hashes they will need
5375 to include in authenticated SENDME cells. At a random interval, if
5376 we have not sent randomness already, we now leave some extra space
5377 at the end of a cell that we can fill with random bytes. Closes
5380 o Minor features (continuous integration):
5381 - When running coverage builds on Travis, we now set
5382 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
5385 o Minor features (maintenance):
5386 - Add a new "make autostyle" target that developers can use to apply
5387 all automatic Tor style and consistency conversions to the
5388 codebase. Closes ticket 30539.
5390 o Minor features (testing):
5391 - The circuitpadding tests now use a reproducible RNG implementation,
5392 so that if a test fails, we can learn why. Part of ticket 28878.
5393 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
5394 to set the RNG seed for tests that use a reproducible RNG. Part of
5396 - When running tests in coverage mode, take additional care to make
5397 our coverage deterministic, so that we can accurately track
5398 changes in code coverage. Closes ticket 30519.
5400 o Minor bugfixes (configuration, proxies):
5401 - Fix a bug that prevented us from supporting SOCKS5 proxies that
5402 want authentication along with configured (but unused!)
5403 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
5405 o Minor bugfixes (controller):
5406 - POSTDESCRIPTOR requests should work again. Previously, they were
5407 broken if a "purpose=" flag was specified. Fixes bug 30580; bugfix
5409 - Repair the HSFETCH command so that it works again. Previously, it
5410 expected a body when it shouldn't have. Fixes bug 30646; bugfix
5413 o Minor bugfixes (developer tooling):
5414 - Fix pre-push hook to allow fixup and squash commits when pushing
5415 to non-upstream git remote. Fixes bug 30286; bugfix
5418 o Minor bugfixes (directory authority):
5419 - Move the "bandwidth-file-headers" line in directory authority
5420 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
5423 o Minor bugfixes (NetBSD):
5424 - Fix usage of minherit() on NetBSD and other platforms that define
5425 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
5426 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
5428 o Minor bugfixes (out-of-memory handler):
5429 - When purging the DNS cache because of an out-of-memory condition,
5430 try purging just the older entries at first. Previously, we would
5431 always purge the whole thing. Fixes bug 29617; bugfix
5434 o Minor bugfixes (portability):
5435 - Avoid crashing in our tor_vasprintf() implementation on systems
5436 that define neither vasprintf() nor _vscprintf(). (This bug has
5437 been here long enough that we question whether people are running
5438 Tor on such systems, but we're applying the fix out of caution.)
5439 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
5442 o Minor bugfixes (shutdown, libevent, memory safety):
5443 - Avoid use-after-free bugs when shutting down, by making sure that
5444 we shut down libevent only after shutting down all of its users.
5445 We believe these are harmless in practice, since they only occur
5446 on the shutdown path, and do not involve any attacker-controlled
5447 data. Fixes bug 30629; bugfix on 0.4.1.1-alpha.
5449 o Minor bugfixes (static analysis):
5450 - Fix several spurious Coverity warnings about the unit tests, to
5451 lower our chances of missing real warnings in the future. Fixes
5452 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
5455 - Specify torrc paths (with empty files) when launching tor in
5456 integration tests; refrain from reading user and system torrcs.
5457 Resolves issue 29702.
5460 Changes in version 0.4.1.1-alpha - 2019-05-22
5461 This is the first alpha in the 0.4.1.x series. It introduces
5462 lightweight circuit padding to make some onion-service circuits harder
5463 to distinguish, includes a new "authenticated SENDME" feature to make
5464 certain denial-of-service attacks more difficult, and improves
5465 performance in several areas.
5467 o Major features (circuit padding):
5468 - Onion service clients now add padding cells at the start of their
5469 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
5470 look more like general purpose Exit traffic. The overhead for this
5471 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
5472 extra upstream cell and 10 downstream cells for INTRODUCE
5473 circuits. This feature is only enabled when also supported by the
5474 circuit's middle node. (Clients may specify fixed middle nodes
5475 with the MiddleNodes option, and may force-disable this feature
5476 with the CircuitPadding option.) Closes ticket 28634.
5478 o Major features (code organization):
5479 - Tor now includes a generic publish-subscribe message-passing
5480 subsystem that we can use to organize intermodule dependencies. We
5481 hope to use this to reduce dependencies between modules that don't
5482 need to be related, and to generally simplify our codebase. Closes
5485 o Major features (controller protocol):
5486 - Controller commands are now parsed using a generalized parsing
5487 subsystem. Previously, each controller command was responsible for
5488 parsing its own input, which led to strange inconsistencies.
5489 Closes ticket 30091.
5491 o Major features (flow control):
5492 - Implement authenticated SENDMEs as detailed in proposal 289. A
5493 SENDME cell now includes the digest of the traffic that it
5494 acknowledges, so that once an end point receives the SENDME, it
5495 can confirm the other side's knowledge of the previous cells that
5496 were sent, and prevent certain types of denial-of-service attacks.
5497 This behavior is controlled by two new consensus parameters: see
5498 the proposal for more details. Fixes ticket 26288.
5500 o Major features (performance):
5501 - Our node selection algorithm now excludes nodes in linear time.
5502 Previously, the algorithm was quadratic, which could slow down
5503 heavily used onion services. Closes ticket 30307.
5505 o Major features (performance, RNG):
5506 - Tor now constructs a fast secure pseudorandom number generator for
5507 each thread, to use when performance is critical. This PRNG is
5508 based on AES-CTR, using a buffering construction similar to
5509 libottery and the (newer) OpenBSD arc4random() code. It
5510 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
5511 small outputs. Although we believe it to be cryptographically
5512 strong, we are only using it when necessary for performance.
5513 Implements tickets 29023 and 29536.
5515 o Major bugfixes (onion service v3):
5516 - Fix an unreachable bug in which an introduction point could try to
5517 send an INTRODUCE_ACK with a status code that Trunnel would refuse
5518 to encode, leading the relay to assert(). We've consolidated the
5519 ABI values into Trunnel now. Fixes bug 30454; bugfix
5521 - Clients can now handle unknown status codes from INTRODUCE_ACK
5522 cells. (The NACK behavior will stay the same.) This will allow us
5523 to extend status codes in the future without breaking the normal
5524 client behavior. Fixes another part of bug 30454; bugfix
5527 o Minor features (circuit padding):
5528 - We now use a fast PRNG when scheduling circuit padding. Part of
5530 - Allow the padding machine designer to pick the edges of their
5531 histogram instead of trying to compute them automatically using an
5532 exponential formula. Resolves some undefined behavior in the case
5533 of small histograms and allows greater flexibility on machine
5534 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
5535 - Allow circuit padding machines to hold a circuit open until they
5536 are done padding it. Closes ticket 28780.
5538 o Minor features (compile-time modules):
5539 - Add a "--list-modules" command to print a list of which compile-
5540 time modules are enabled. Closes ticket 30452.
5542 o Minor features (continuous integration):
5543 - Remove sudo configuration lines from .travis.yml as they are no
5544 longer needed with current Travis build environment. Resolves
5546 - In Travis, show stem's tor log after failure. Closes ticket 30234.
5548 o Minor features (controller):
5549 - Add onion service version 3 support to the HSFETCH command.
5550 Previously, only version 2 onion services were supported. Closes
5551 ticket 25417. Patch by Neel Chauhan.
5553 o Minor features (debugging):
5554 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
5555 logging of additional information during assert failure. Now we
5556 can use format strings to include information for trouble
5557 shooting. Resolves ticket 29662.
5559 o Minor features (defense in depth):
5560 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
5561 case a bug causes them to be used later. Closes ticket 30176.
5562 Patch from Tobias Stoeckmann.
5563 - Tor now uses a cryptographically strong PRNG even for decisions
5564 that we do not believe are security-sensitive. Previously, for
5565 performance reasons, we had used a trivially predictable linear
5566 congruential generator algorithm for certain load-balancing and
5567 statistical sampling decisions. Now we use our fast RNG in those
5568 cases. Closes ticket 29542.
5570 o Minor features (developer tools):
5571 - Tor's "practracker" test script now checks for files and functions
5572 that seem too long and complicated. Existing overlong functions
5573 and files are accepted for now, but should eventually be
5574 refactored. Closes ticket 29221.
5575 - Add some scripts used for git maintenance to scripts/git. Closes
5577 - Call practracker from pre-push and pre-commit git hooks to let
5578 developers know if they made any code style violations. Closes
5580 - Add a script to check that each header has a well-formed and
5581 unique guard macro. Closes ticket 29756.
5583 o Minor features (geoip):
5584 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
5585 Country database. Closes ticket 30522.
5587 o Minor features (HTTP tunnel):
5588 - Return an informative web page when the HTTPTunnelPort is used as
5589 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
5591 o Minor features (IPv6, v3 onion services):
5592 - Make v3 onion services put IPv6 addresses in service descriptors.
5593 Before this change, service descriptors only contained IPv4
5594 addresses. Implements 26992.
5596 o Minor features (modularity):
5597 - The "--disable-module-dirauth" compile-time option now disables
5598 even more dirauth-only code. Closes ticket 30345.
5600 o Minor features (performance):
5601 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
5602 1.1.1 and later), since they tend to be faster than tiny-keccak.
5603 Closes ticket 28837.
5605 o Minor features (testing):
5606 - Tor's unit test code now contains helper functions to replace the
5607 PRNG with a deterministic or reproducible version for testing.
5608 Previously, various tests implemented this in various ways.
5609 Implements ticket 29732.
5610 - We now have a script, cov-test-determinism.sh, to identify places
5611 where our unit test coverage has become nondeterministic. Closes
5613 - Check that representative subsets of values of `int` and `unsigned
5614 int` can be represented by `void *`. Resolves issue 29537.
5616 o Minor bugfixes (bridge authority):
5617 - Bridge authorities now set bridges as running or non-running when
5618 about to dump their status to a file. Previously, they set bridges
5619 as running in response to a GETINFO command, but those shouldn't
5620 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
5621 Patch by Neel Chauhan.
5623 o Minor bugfixes (channel padding statistics):
5624 - Channel padding write totals and padding-enabled totals are now
5625 counted properly in relay extrainfo descriptors. Fixes bug 29231;
5626 bugfix on 0.3.1.1-alpha.
5628 o Minor bugfixes (circuit padding):
5629 - Add a "CircuitPadding" torrc option to disable circuit padding.
5630 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
5631 - Allow circuit padding machines to specify that they do not
5632 contribute much overhead, and provide consensus flags and torrc
5633 options to force clients to only use these low overhead machines.
5634 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
5635 - Provide a consensus parameter to fully disable circuit padding, to
5636 be used in emergency network overload situations. Fixes bug 30173;
5637 bugfix on 0.4.0.1-alpha.
5638 - The circuit padding subsystem will no longer schedule padding if
5639 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
5640 - Inspect a circuit-level cell queue before sending padding, to
5641 avoid sending padding while too much data is already queued. Fixes
5642 bug 29204; bugfix on 0.4.0.1-alpha.
5643 - Avoid calling monotime_absolute_usec() in circuit padding machines
5644 that do not use token removal or circuit RTT estimation. Fixes bug
5645 29085; bugfix on 0.4.0.1-alpha.
5647 o Minor bugfixes (compilation, unusual configurations):
5648 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
5649 due to missing declarations of abort(), and prevent other such
5650 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
5652 o Minor bugfixes (controller protocol):
5653 - Teach the controller parser to distinguish an object preceded by
5654 an argument list from one without. Previously, it couldn't
5655 distinguish an argument list from the first line of a multiline
5656 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
5658 o Minor bugfixes (directory authority, ipv6):
5659 - Directory authorities with IPv6 support now always mark themselves
5660 as reachable via IPv6. Fixes bug 24338; bugfix on 0.2.4.1-alpha.
5661 Patch by Neel Chauhan.
5663 o Minor bugfixes (documentation):
5664 - Improve the documentation for using MapAddress with ".exit". Fixes
5665 bug 30109; bugfix on 0.1.0.1-rc.
5666 - Improve the monotonic time module and function documentation to
5667 explain what "monotonic" actually means, and document some results
5668 that have surprised people. Fixes bug 29640; bugfix
5670 - Use proper formatting when providing an example on quoting options
5671 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
5673 o Minor bugfixes (logging):
5674 - Do not log a warning when running with an OpenSSL version other
5675 than the one Tor was compiled with, if the two versions should be
5676 compatible. Previously, we would warn whenever the version was
5677 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
5678 - Warn operators when the MyFamily option is set but ContactInfo is
5679 missing, as the latter should be set too. Fixes bug 25110; bugfix
5682 o Minor bugfixes (memory leak):
5683 - Avoid a minor memory leak that could occur on relays when failing
5684 to create a "keys" directory. Fixes bug 30148; bugfix
5687 o Minor bugfixes (onion services):
5688 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
5689 implemenation) when failing to load an onion service client
5690 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
5691 - When refusing to launch a controller's HSFETCH request because of
5692 rate-limiting, respond to the controller with a new response,
5693 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
5694 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
5696 - When relaunching a circuit to a rendezvous service, mark the
5697 circuit as needing high-uptime routers as appropriate. Fixes bug
5698 17357; bugfix on 0.1.0.1-rc. Patch by Neel Chauhan.
5699 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
5700 (IPv6 support for v3 onion services is still incomplete: see
5701 ticket 23493 for details.) Fixes bug 23588; bugfix on
5702 0.3.2.1-alpha. Patch by Neel Chauhan.
5704 o Minor bugfixes (onion services, performance):
5705 - When building circuits to onion services, call tor_addr_parse()
5706 less often. Previously, we called tor_addr_parse() in
5707 circuit_is_acceptable() even if its output wasn't used. This
5708 change should improve performance when building circuits. Fixes
5709 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
5711 o Minor bugfixes (performance):
5712 - When checking whether a node is a bridge, use a fast check to make
5713 sure that its identity is set. Previously, we used a constant-time
5714 check, which is not necessary in this case. Fixes bug 30308;
5715 bugfix on 0.3.5.1-alpha.
5717 o Minor bugfixes (pluggable transports):
5718 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
5719 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
5721 o Minor bugfixes (probability distributions):
5722 - Refactor and improve parts of the probability distribution code
5723 that made Coverity complain. Fixes bug 29805; bugfix
5726 o Minor bugfixes (python):
5727 - Stop assuming that /usr/bin/python3 exists. For scripts that work
5728 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
5729 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
5731 o Minor bugfixes (relay):
5732 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
5733 is auto, act as if ExitRelay is 1. Previously, we would ignore
5734 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
5735 0.3.5.1-alpha. Patch by Neel Chauhan.
5737 o Minor bugfixes (stats):
5738 - When ExtraInfoStatistics is 0, stop including bandwidth usage
5739 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
5740 bridge statistics by country in extra-info documents. Fixes bug
5741 29018; bugfix on 0.2.4.1-alpha.
5743 o Minor bugfixes (testing):
5744 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
5745 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
5746 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
5747 - Fix some incorrect code in the v3 onion service unit tests. Fixes
5748 bug 29243; bugfix on 0.3.2.1-alpha.
5749 - In the "routerkeys/*" tests, check the return values of mkdir()
5750 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
5751 Found by Coverity as CID 1444254.
5752 - Split test_utils_general() into several smaller test functions.
5753 This makes it easier to perform resource deallocation on assert
5754 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
5755 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
5757 o Minor bugfixes (tor-resolve):
5758 - Fix a memory leak in tor-resolve that could happen if Tor gave it
5759 a malformed SOCKS response. (Memory leaks in tor-resolve don't
5760 actually matter, but it's good to fix them anyway.) Fixes bug
5761 30151; bugfix on 0.4.0.1-alpha.
5763 o Code simplification and refactoring:
5764 - Abstract out the low-level formatting of replies on the control
5765 port. Implements ticket 30007.
5766 - Add several assertions in an attempt to fix some Coverity
5767 warnings. Closes ticket 30149.
5768 - Introduce a connection_dir_buf_add() helper function that checks
5769 for compress_state of dir_connection_t and automatically writes a
5770 string to directory connection with or without compression.
5771 Resolves issue 28816.
5772 - Make the base32_decode() API return the number of bytes written,
5773 for consistency with base64_decode(). Closes ticket 28913.
5774 - Move most relay-only periodic events out of mainloop.c into the
5775 relay subsystem. Closes ticket 30414.
5776 - Refactor and encapsulate parts of the codebase that manipulate
5777 crypt_path_t objects. Resolves issue 30236.
5778 - Refactor several places in our code that Coverity incorrectly
5779 believed might have memory leaks. Closes ticket 30147.
5780 - Remove redundant return values in crypto_format, and the
5781 associated return value checks elsewhere in the code. Make the
5782 implementations in crypto_format consistent, and remove redundant
5783 code. Resolves ticket 29660.
5784 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
5785 it is not a constant-time function. Closes ticket 30309.
5786 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
5787 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
5788 bugfix on 0.3.2.1-alpha.
5789 - Simplify v3 onion service link specifier handling code. Fixes bug
5790 23576; bugfix on 0.3.2.1-alpha.
5791 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
5792 code. Resolves ticket 29108.
5793 - Split control.c into several submodules, in preparation for
5794 distributing its current responsibilities throughout the codebase.
5795 Closes ticket 29894.
5796 - Start to move responsibility for knowing about periodic events to
5797 the appropriate subsystems, so that the mainloop doesn't need to
5798 know all the periodic events in the rest of the codebase.
5799 Implements tickets 30293 and 30294.
5802 - Document how to find git commits and tags for bug fixes in
5803 CodingStandards.md. Update some file documentation. Closes
5807 - Remove the linux-tor-prio.sh script from contrib/operator-tools
5808 directory. Resolves issue 29434.
5809 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
5810 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
5813 o Code simplification and refactoring (shell scripts):
5814 - Clean up many of our shell scripts to fix shellcheck warnings.
5815 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
5816 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
5817 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
5818 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
5819 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
5820 nagios-check-tor-authority-cert (ticket 29071),
5821 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
5822 (ticket 29060), test_key_expiration.sh (ticket 30002),
5823 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
5826 o Testing (chutney):
5827 - In "make test-network-all", test IPv6-only v3 single onion
5828 services, using the chutney network single-onion-v23-ipv6-md.
5829 Closes ticket 27251.
5832 Changes in version 0.4.0.5 - 2019-05-02
5833 This is the first stable release in the 0.4.0.x series. It contains
5834 improvements for power management and bootstrap reporting, as well as
5835 preliminary backend support for circuit padding to prevent some kinds
5836 of traffic analysis. It also continues our work in refactoring Tor for
5837 long-term maintainability.
5839 Per our support policy, we will support the 0.4.0.x series for nine
5840 months, or until three months after the release of a stable 0.4.1.x:
5841 whichever is longer. If you need longer-term support, please stick
5842 with 0.3.5.x, which will we plan to support until Feb 2022.
5844 Below are the changes since 0.4.0.4-rc. For a complete list of changes
5845 since 0.3.5.7, see the ReleaseNotes file.
5847 o Minor features (continuous integration):
5848 - In Travis, tell timelimit to use stem's backtrace signals, and
5849 launch python directly from timelimit, so python receives the
5850 signals from timelimit, rather than make. Closes ticket 30117.
5852 o Minor features (diagnostic):
5853 - Add more diagnostic log messages in an attempt to solve the issue
5854 of NUL bytes appearing in a microdescriptor cache. Related to
5857 o Minor features (testing):
5858 - Use the approx_time() function when setting the "Expires" header
5859 in directory replies, to make them more testable. Needed for
5862 o Minor bugfixes (rust):
5863 - Abort on panic in all build profiles, instead of potentially
5864 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
5866 o Minor bugfixes (shellcheck):
5867 - Look for scripts in their correct locations during "make
5868 shellcheck". Previously we had looked in the wrong place during
5869 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
5871 o Minor bugfixes (testing):
5872 - Check the time in the "Expires" header using approx_time(). Fixes
5873 bug 30001; bugfix on 0.4.0.4-rc.
5875 o Minor bugfixes (UI):
5876 - Lower log level of unlink() errors during bootstrap. Fixes bug
5877 29930; bugfix on 0.4.0.1-alpha.
5880 Changes in version 0.4.0.4-rc - 2019-04-11
5881 Tor 0.4.0.4-rc is the first release candidate in its series; it fixes
5882 several bugs from earlier versions, including some that had affected
5883 stability, and one that prevented relays from working with NSS.
5885 o Major bugfixes (NSS, relay):
5886 - When running with NSS, disable TLS 1.2 ciphersuites that use
5887 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
5888 these ciphersuites don't work -- which caused relays to fail to
5889 handshake with one another when these ciphersuites were enabled.
5890 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
5892 o Minor features (bandwidth authority):
5893 - Make bandwidth authorities ignore relays that are reported in the
5894 bandwidth file with the flag "vote=0". This change allows us to
5895 report unmeasured relays for diagnostic reasons without including
5896 their bandwidth in the bandwidth authorities' vote. Closes
5898 - When a directory authority is using a bandwidth file to obtain the
5899 bandwidth values that will be included in the next vote, serve
5900 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
5903 o Minor features (circuit padding):
5904 - Stop warning about undefined behavior in the probability
5905 distribution tests. Float division by zero may technically be
5906 undefined behavior in C, but it's well defined in IEEE 754.
5907 Partial backport of 29298. Closes ticket 29527; bugfix
5910 o Minor features (continuous integration):
5911 - On Travis Rust builds, cleanup Rust registry and refrain from
5912 caching the "target/" directory to speed up builds. Resolves
5915 o Minor features (dormant mode):
5916 - Add a DormantCanceledByStartup option to tell Tor that it should
5917 treat a startup event as cancelling any previous dormant state.
5918 Integrators should use this option with caution: it should only be
5919 used if Tor is being started because of something that the user
5920 did, and not if Tor is being automatically started in the
5921 background. Closes ticket 29357.
5923 o Minor features (geoip):
5924 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
5925 Country database. Closes ticket 29992.
5927 o Minor features (NSS, diagnostic):
5928 - Try to log an error from NSS (if there is any) and a more useful
5929 description of our situation if we are using NSS and a call to
5930 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
5932 o Minor bugfixes (security):
5933 - Fix a potential double free bug when reading huge bandwidth files.
5934 The issue is not exploitable in the current Tor network because
5935 the vulnerable code is only reached when directory authorities
5936 read bandwidth files, but bandwidth files come from a trusted
5937 source (usually the authorities themselves). Furthermore, the
5938 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
5939 which are not used by any of the current authorities. Fixes bug
5940 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
5942 - Verify in more places that we are not about to create a buffer
5943 with more than INT_MAX bytes, to avoid possible OOB access in the
5944 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
5945 fixed by Tobias Stoeckmann.
5947 o Minor bugfix (continuous integration):
5948 - Reset coverage state on disk after Travis CI has finished. This
5949 should prevent future coverage merge errors from causing the test
5950 suite for the "process" subsystem to fail. The process subsystem
5951 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
5953 - Terminate test-stem if it takes more than 9.5 minutes to run.
5954 (Travis terminates the job after 10 minutes of no output.)
5955 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
5957 o Minor bugfixes (bootstrap reporting):
5958 - During bootstrap reporting, correctly distinguish pluggable
5959 transports from plain proxies. Fixes bug 28925; bugfix
5962 o Minor bugfixes (C correctness):
5963 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
5964 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
5967 o Minor bugfixes (circuitpadding testing):
5968 - Minor tweaks to avoid rare test failures related to timers and
5969 monotonic time. Fixes bug 29500; bugfix on 0.4.0.1-alpha.
5971 o Minor bugfixes (directory authorities):
5972 - Actually include the bandwidth-file-digest line in directory
5973 authority votes. Fixes bug 29959; bugfix on 0.4.0.2-alpha.
5975 o Minor bugfixes (logging):
5976 - On Windows, when errors cause us to reload a consensus from disk,
5977 tell the user that we are retrying at log level "notice".
5978 Previously we only logged this information at "info", which was
5979 confusing because the errors themselves were logged at "warning".
5980 Improves previous fix for 28614. Fixes bug 30004; bugfix
5983 o Minor bugfixes (pluggable transports):
5984 - Restore old behavior when it comes to discovering the path of a
5985 given Pluggable Transport executable file. A change in
5986 0.4.0.1-alpha had broken this behavior on paths containing a
5987 space. Fixes bug 29874; bugfix on 0.4.0.1-alpha.
5989 o Minor bugfixes (testing):
5990 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
5991 recent test-network.sh to use new chutney features in CI. Fixes
5992 bug 29703; bugfix on 0.2.9.1-alpha.
5993 - Fix a test failure on Windows caused by an unexpected "BUG"
5994 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
5997 o Minor bugfixes (TLS protocol):
5998 - When classifying a client's selection of TLS ciphers, if the
5999 client ciphers are not yet available, do not cache the result.
6000 Previously, we had cached the unavailability of the cipher list
6001 and never looked again, which in turn led us to assume that the
6002 client only supported the ancient V1 link protocol. This, in turn,
6003 was causing Stem integration tests to stall in some cases. Fixes
6004 bug 30021; bugfix on 0.2.4.8-alpha.
6006 o Code simplification and refactoring:
6007 - Introduce a connection_dir_buf_add() helper function that detects
6008 whether compression is in use, and adds a string accordingly.
6009 Resolves issue 28816.
6010 - Refactor handle_get_next_bandwidth() to use
6011 connection_dir_buf_add(). Implements ticket 29897.
6014 - Clarify that Tor performs stream isolation among *Port listeners
6015 by default. Resolves issue 29121.
6018 Changes in version 0.4.0.3-alpha - 2019-03-22
6019 Tor 0.4.0.3-alpha is the third in its series; it fixes several small
6020 bugs from earlier versions.
6022 o Minor features (address selection):
6023 - Treat the subnet 100.64.0.0/10 as public for some purposes;
6024 private for others. This subnet is the RFC 6598 (Carrier Grade
6025 NAT) IP range, and is deployed by many ISPs as an alternative to
6026 RFC 1918 that does not break existing internal networks. Tor now
6027 blocks SOCKS and control ports on these addresses and warns users
6028 if client ports or ExtORPorts are listening on a RFC 6598 address.
6029 Closes ticket 28525. Patch by Neel Chauhan.
6031 o Minor features (geoip):
6032 - Update geoip and geoip6 to the March 4 2019 Maxmind GeoLite2
6033 Country database. Closes ticket 29666.
6035 o Minor bugfixes (circuitpadding):
6036 - Inspect the circuit-level cell queue before sending padding, to
6037 avoid sending padding when too much data is queued. Fixes bug
6038 29204; bugfix on 0.4.0.1-alpha.
6040 o Minor bugfixes (logging):
6041 - Correct a misleading error message when IPv4Only or IPv6Only is
6042 used but the resolved address can not be interpreted as an address
6043 of the specified IP version. Fixes bug 13221; bugfix on
6044 0.2.3.9-alpha. Patch from Kris Katterjohn.
6045 - Log the correct port number for listening sockets when "auto" is
6046 used to let Tor pick the port number. Previously, port 0 was
6047 logged instead of the actual port number. Fixes bug 29144; bugfix
6048 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
6049 - Stop logging a BUG() warning when Tor is waiting for exit
6050 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
6052 o Minor bugfixes (memory management):
6053 - Refactor the shared random state's memory management so that it
6054 actually takes ownership of the shared random value pointers.
6055 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
6057 o Minor bugfixes (memory management, testing):
6058 - Stop leaking parts of the shared random state in the shared-random
6059 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
6061 o Minor bugfixes (pluggable transports):
6062 - Fix an assertion failure crash bug when a pluggable transport is
6063 terminated during the bootstrap phase. Fixes bug 29562; bugfix
6066 o Minor bugfixes (Rust, protover):
6067 - Add a missing "Padding" value to the Rust implementation of
6068 protover. Fixes bug 29631; bugfix on 0.4.0.1-alpha.
6070 o Minor bugfixes (single onion services):
6071 - Allow connections to single onion services to remain idle without
6072 being disconnected. Previously, relays acting as rendezvous points
6073 for single onion services were mistakenly closing idle rendezvous
6074 circuits after 60 seconds, thinking that they were unused
6075 directory-fetching circuits that had served their purpose. Fixes
6076 bug 29665; bugfix on 0.2.1.26.
6078 o Minor bugfixes (stats):
6079 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
6080 relay and bridge extra-info documents. Fixes bug 29017; bugfix
6083 o Minor bugfixes (testing):
6084 - Downgrade some LOG_ERR messages in the address/* tests to
6085 warnings. The LOG_ERR messages were occurring when we had no
6086 configured network. We were failing the unit tests, because we
6087 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
6088 29530; bugfix on 0.3.5.8.
6089 - Fix our gcov wrapper script to look for object files at the
6090 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
6091 - Decrease the false positive rate of stochastic probability
6092 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
6094 o Minor bugfixes (Windows, CI):
6095 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
6096 Windows Server 2012 R2 job. The remaining 2 jobs still provide
6097 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
6098 fast_finish, so failed jobs terminate the build immediately. Fixes
6099 bug 29601; bugfix on 0.3.5.4-alpha.
6102 Changes in version 0.3.5.8 - 2019-02-21
6103 Tor 0.3.5.8 backports several fixes from later releases, including fixes
6104 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
6107 It also includes a fix for a medium-severity security bug affecting Tor
6108 0.3.2.1-alpha and later. All Tor instances running an affected release
6109 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
6111 o Major bugfixes (cell scheduler, KIST, security):
6112 - Make KIST consider the outbuf length when computing what it can
6113 put in the outbuf. Previously, KIST acted as though the outbuf
6114 were empty, which could lead to the outbuf becoming too full. It
6115 is possible that an attacker could exploit this bug to cause a Tor
6116 client or relay to run out of memory and crash. Fixes bug 29168;
6117 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
6118 TROVE-2019-001 and CVE-2019-8955.
6120 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
6121 - Gracefully handle empty username/password fields in SOCKS5
6122 username/password auth message and allow SOCKS5 handshake to
6123 continue. Previously, we had rejected these handshakes, breaking
6124 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
6126 o Minor features (compilation, backport from 0.4.0.2-alpha):
6127 - Compile correctly when OpenSSL is built with engine support
6128 disabled, or with deprecated APIs disabled. Closes ticket 29026.
6129 Patches from "Mangix".
6131 o Minor features (geoip):
6132 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
6133 Country database. Closes ticket 29478.
6135 o Minor features (testing, backport from 0.4.0.2-alpha):
6136 - Treat all unexpected ERR and BUG messages as test failures. Closes
6139 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
6140 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
6141 connection waiting for a descriptor that we actually have in the
6142 cache. It turns out that this can actually happen, though it is
6143 rare. Now, tor will recover and retry the descriptor. Fixes bug
6144 28669; bugfix on 0.3.2.4-alpha.
6146 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
6147 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
6148 IPv6 socket was bound using an address family of AF_INET instead
6149 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
6152 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
6153 - Update Cargo.lock file to match the version made by the latest
6154 version of Rust, so that "make distcheck" will pass again. Fixes
6155 bug 29244; bugfix on 0.3.3.4-alpha.
6157 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
6158 - Select guards even if the consensus has expired, as long as the
6159 consensus is still reasonably live. Fixes bug 24661; bugfix
6162 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
6163 - Compile correctly on OpenBSD; previously, we were missing some
6164 headers required in order to detect it properly. Fixes bug 28938;
6165 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
6167 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
6168 - Describe the contents of the v3 onion service client authorization
6169 files correctly: They hold public keys, not private keys. Fixes
6170 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
6172 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
6173 - Rework rep_hist_log_link_protocol_counts() to iterate through all
6174 link protocol versions when logging incoming/outgoing connection
6175 counts. Tor no longer skips version 5, and we won't have to
6176 remember to update this function when new link protocol version is
6177 developed. Fixes bug 28920; bugfix on 0.2.6.10.
6179 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
6180 - Log more information at "warning" level when unable to read a
6181 private key; log more information at "info" level when unable to
6182 read a public key. We had warnings here before, but they were lost
6183 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
6185 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
6186 - The amount of total available physical memory is now determined
6187 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
6188 when it is defined and a 64-bit variant is not available. Fixes
6189 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
6191 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
6192 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
6193 than one private key for a hidden service. Fixes bug 29040; bugfix
6195 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
6196 "debug" level. Tor used to log it as a warning, which caused very
6197 long log lines to appear for some users. Fixes bug 29135; bugfix
6199 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
6200 as a warning. Instead, log it as a protocol warning, because there
6201 is nothing that relay operators can do to fix it. Fixes bug 29029;
6202 bugfix on 0.2.5.7-rc.
6204 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
6205 - Mark outdated dirservers when Tor only has a reasonably live
6206 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
6208 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
6209 - Detect and suppress "bug" warnings from the util/time test on
6210 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
6211 - Do not log an error-level message if we fail to find an IPv6
6212 network interface from the unit tests. Fixes bug 29160; bugfix
6215 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
6216 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
6217 Some users took this phrasing to mean that the mentioned guard was
6218 under their control or responsibility, which it is not. Fixes bug
6219 28895; bugfix on Tor 0.3.0.1-alpha.
6222 Changes in version 0.3.4.11 - 2019-02-21
6223 Tor 0.3.4.11 is the third stable release in its series. It includes
6224 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
6225 later. All Tor instances running an affected release should upgrade to
6226 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
6228 o Major bugfixes (cell scheduler, KIST, security):
6229 - Make KIST consider the outbuf length when computing what it can
6230 put in the outbuf. Previously, KIST acted as though the outbuf
6231 were empty, which could lead to the outbuf becoming too full. It
6232 is possible that an attacker could exploit this bug to cause a Tor
6233 client or relay to run out of memory and crash. Fixes bug 29168;
6234 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
6235 TROVE-2019-001 and CVE-2019-8955.
6237 o Minor features (geoip):
6238 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
6239 Country database. Closes ticket 29478.
6241 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
6242 - Update Cargo.lock file to match the version made by the latest
6243 version of Rust, so that "make distcheck" will pass again. Fixes
6244 bug 29244; bugfix on 0.3.3.4-alpha.
6246 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
6247 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
6248 as a warning. Instead, log it as a protocol warning, because there
6249 is nothing that relay operators can do to fix it. Fixes bug 29029;
6250 bugfix on 0.2.5.7-rc.
6253 Changes in version 0.3.3.12 - 2019-02-21
6254 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
6255 0.3.2.1-alpha and later. All Tor instances running an affected release
6256 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
6258 This release marks the end of support for the Tor 0.3.3.x series. We
6259 recommend that users switch to either the Tor 0.3.4 series (supported
6260 until at least 10 June 2019), or the Tor 0.3.5 series, which will
6261 receive long-term support until at least 1 Feb 2022.
6263 o Major bugfixes (cell scheduler, KIST, security):
6264 - Make KIST consider the outbuf length when computing what it can
6265 put in the outbuf. Previously, KIST acted as though the outbuf
6266 were empty, which could lead to the outbuf becoming too full. It
6267 is possible that an attacker could exploit this bug to cause a Tor
6268 client or relay to run out of memory and crash. Fixes bug 29168;
6269 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
6270 TROVE-2019-001 and CVE-2019-8955.
6272 o Minor features (geoip):
6273 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
6274 Country database. Closes ticket 29478.
6276 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
6277 - Update Cargo.lock file to match the version made by the latest
6278 version of Rust, so that "make distcheck" will pass again. Fixes
6279 bug 29244; bugfix on 0.3.3.4-alpha.
6281 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
6282 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
6283 as a warning. Instead, log it as a protocol warning, because there
6284 is nothing that relay operators can do to fix it. Fixes bug 29029;
6285 bugfix on 0.2.5.7-rc.
6288 Changes in version 0.4.0.2-alpha - 2019-02-21
6289 Tor 0.4.0.2-alpha is the second alpha in its series; it fixes several
6290 bugs from earlier versions, including several that had broken
6291 backward compatibility.
6293 It also includes a fix for a medium-severity security bug affecting Tor
6294 0.3.2.1-alpha and later. All Tor instances running an affected release
6295 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
6297 o Major bugfixes (cell scheduler, KIST, security):
6298 - Make KIST consider the outbuf length when computing what it can
6299 put in the outbuf. Previously, KIST acted as though the outbuf
6300 were empty, which could lead to the outbuf becoming too full. It
6301 is possible that an attacker could exploit this bug to cause a Tor
6302 client or relay to run out of memory and crash. Fixes bug 29168;
6303 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
6304 TROVE-2019-001 and CVE-2019-8955.
6306 o Major bugfixes (networking):
6307 - Gracefully handle empty username/password fields in SOCKS5
6308 username/password auth messsage and allow SOCKS5 handshake to
6309 continue. Previously, we had rejected these handshakes, breaking
6310 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
6312 o Major bugfixes (windows, startup):
6313 - When reading a consensus file from disk, detect whether it was
6314 written in text mode, and re-read it in text mode if so. Always
6315 write consensus files in binary mode so that we can map them into
6316 memory later. Previously, we had written in text mode, which
6317 confused us when we tried to map the file on windows. Fixes bug
6318 28614; bugfix on 0.4.0.1-alpha.
6320 o Minor features (compilation):
6321 - Compile correctly when OpenSSL is built with engine support
6322 disabled, or with deprecated APIs disabled. Closes ticket 29026.
6323 Patches from "Mangix".
6325 o Minor features (developer tooling):
6326 - Check that bugfix versions in changes files look like Tor versions
6327 from the versions spec. Warn when bugfixes claim to be on a future
6328 release. Closes ticket 27761.
6329 - Provide a git pre-commit hook that disallows committing if we have
6330 any failures in our code and changelog formatting checks. It is
6331 now available in scripts/maint/pre-commit.git-hook. Implements
6334 o Minor features (directory authority):
6335 - When a directory authority is using a bandwidth file to obtain
6336 bandwidth values, include the digest of that file in the vote.
6337 Closes ticket 26698.
6339 o Minor features (geoip):
6340 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
6341 Country database. Closes ticket 29478.
6343 o Minor features (testing):
6344 - Treat all unexpected ERR and BUG messages as test failures. Closes
6347 o Minor bugfixes (build, compatibility, rust):
6348 - Update Cargo.lock file to match the version made by the latest
6349 version of Rust, so that "make distcheck" will pass again. Fixes
6350 bug 29244; bugfix on 0.3.3.4-alpha.
6352 o Minor bugfixes (compilation):
6353 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
6354 29169; bugfix on 0.4.0.1-alpha.
6355 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
6356 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
6358 o Minor bugfixes (documentation):
6359 - Describe the contents of the v3 onion service client authorization
6360 files correctly: They hold public keys, not private keys. Fixes
6361 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
6363 o Minor bugfixes (linux seccomp sandbox):
6364 - Fix startup crash when experimental sandbox support is enabled.
6365 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
6367 o Minor bugfixes (logging):
6368 - Avoid logging that we are relaxing a circuit timeout when that
6369 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
6370 - Log more information at "warning" level when unable to read a
6371 private key; log more information at "info" level when unable to
6372 read a public key. We had warnings here before, but they were lost
6373 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
6375 o Minor bugfixes (misc):
6376 - The amount of total available physical memory is now determined
6377 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
6378 when it is defined and a 64-bit variant is not available. Fixes
6379 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
6381 o Minor bugfixes (onion services):
6382 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
6383 than one private key for a hidden service. Fixes bug 29040; bugfix
6385 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
6386 "debug" level. Tor used to log it as a warning, which caused very
6387 long log lines to appear for some users. Fixes bug 29135; bugfix
6389 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
6390 as a warning. Instead, log it as a protocol warning, because there
6391 is nothing that relay operators can do to fix it. Fixes bug 29029;
6392 bugfix on 0.2.5.7-rc.
6394 o Minor bugfixes (scheduler):
6395 - When re-adding channels to the pending list, check the correct
6396 channel's sched_heap_idx. This issue has had no effect in mainline
6397 Tor, but could have led to bugs down the road in improved versions
6398 of our circuit scheduling code. Fixes bug 29508; bugfix
6401 o Minor bugfixes (tests):
6402 - Fix intermittent failures on an adaptive padding test. Fixes one
6403 case of bug 29122; bugfix on 0.4.0.1-alpha.
6404 - Disable an unstable circuit-padding test that was failing
6405 intermittently because of an ill-defined small histogram. Such
6406 histograms will be allowed again after 29298 is implemented. Fixes
6407 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
6408 - Detect and suppress "bug" warnings from the util/time test on
6409 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
6410 - Do not log an error-level message if we fail to find an IPv6
6411 network interface from the unit tests. Fixes bug 29160; bugfix
6415 - In the manpage entry describing MapAddress torrc setting, use
6416 example IP addresses from ranges specified for use in documentation
6417 by RFC 5737. Resolves issue 28623.
6420 - Remove the old check-tor script. Resolves issue 29072.
6423 Changes in version 0.4.0.1-alpha - 2019-01-18
6424 Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It
6425 introduces improved features for power and bandwidth conservation,
6426 more accurate reporting of bootstrap progress for user interfaces, and
6427 an experimental backend for an exciting new adaptive padding feature.
6428 There is also the usual assortment of bugfixes and minor features, all
6431 o Major features (battery management, client, dormant mode):
6432 - When Tor is running as a client, and it is unused for a long time,
6433 it can now enter a "dormant" state. When Tor is dormant, it avoids
6434 network and CPU activity until it is reawoken either by a user
6435 request or by a controller command. For more information, see the
6436 configuration options starting with "Dormant". Implements tickets
6438 - The client's memory of whether it is "dormant", and how long it
6439 has spent idle, persists across invocations. Implements
6441 - There is a DormantOnFirstStartup option that integrators can use
6442 if they expect that in many cases, Tor will be installed but
6445 o Major features (bootstrap reporting):
6446 - When reporting bootstrap progress, report the first connection
6447 uniformly, regardless of whether it's a connection for building
6448 application circuits. This allows finer-grained reporting of early
6449 progress than previously possible, with the improvements of ticket
6450 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
6451 - When reporting bootstrap progress, treat connecting to a proxy or
6452 pluggable transport as separate from having successfully used that
6453 proxy or pluggable transport to connect to a relay. Closes tickets
6456 o Major features (circuit padding):
6457 - Implement preliminary support for the circuit padding portion of
6458 Proposal 254. The implementation supports Adaptive Padding (aka
6459 WTF-PAD) state machines for use between experimental clients and
6460 relays. Support is also provided for APE-style state machines that
6461 use probability distributions instead of histograms to specify
6462 inter-packet delay. At the moment, Tor does not provide any
6463 padding state machines that are used in normal operation: for now,
6464 this feature exists solely for experimentation. Closes
6467 o Major features (refactoring):
6468 - Tor now uses an explicit list of its own subsystems when
6469 initializing and shutting down. Previously, these systems were
6470 managed implicitly in various places throughout the codebase.
6471 (There may still be some subsystems using the old system.) Closes
6474 o Minor features (bootstrap reporting):
6475 - When reporting bootstrap progress, stop distinguishing between
6476 situations where only internal paths are available and situations
6477 where external paths are available. Previously, Tor would often
6478 erroneously report that it had only internal paths. Closes
6481 o Minor features (continuous integration):
6482 - Log Python version during each Travis CI job. Resolves
6485 o Minor features (controller):
6486 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
6487 Implements ticket 28843.
6489 o Minor features (developer tooling):
6490 - Provide a git hook script to prevent "fixup!" and "squash!"
6491 commits from ending up in the master branch, as scripts/main/pre-
6492 push.git-hook. Closes ticket 27993.
6494 o Minor features (directory authority):
6495 - Directory authorities support a new consensus algorithm, under
6496 which the family lines in microdescriptors are encoded in a
6497 canonical form. This change makes family lines more compressible
6498 in transit, and on the client. Closes ticket 28266; implements
6501 o Minor features (directory authority, relay):
6502 - Authorities now vote on a "StaleDesc" flag to indicate that a
6503 relay's descriptor is so old that the relay should upload again
6504 soon. Relays treat this flag as a signal to upload a new
6505 descriptor. This flag will eventually let us remove the
6506 'published' date from routerstatus entries, and make our consensus
6507 diffs much smaller. Closes ticket 26770; implements proposal 293.
6509 o Minor features (fallback directory mirrors):
6510 - Update the fallback whitelist based on operator opt-ins and opt-
6511 outs. Closes ticket 24805, patch by Phoul.
6513 o Minor features (FreeBSD):
6514 - On FreeBSD-based systems, warn relay operators if the
6515 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
6516 Closes ticket 28518.
6518 o Minor features (HTTP standards compliance):
6519 - Stop sending the header "Content-type: application/octet-stream"
6520 along with transparently compressed documents: this confused
6521 browsers. Closes ticket 28100.
6523 o Minor features (IPv6):
6524 - We add an option ClientAutoIPv6ORPort, to make clients randomly
6525 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
6526 every time a node is loaded from a new consensus or bridge config.
6527 We expect that this option will enable clients to bootstrap more
6528 quickly without having to determine whether they support IPv4,
6529 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
6530 - When using addrs_in_same_network_family(), avoid choosing circuit
6531 paths that pass through the same IPv6 subnet more than once.
6532 Previously, we only checked IPv4 subnets. Closes ticket 24393.
6533 Patch by Neel Chauhan.
6535 o Minor features (log messages):
6536 - Improve log message in v3 onion services that could print out
6537 negative revision counters. Closes ticket 27707. Patch
6540 o Minor features (memory usage):
6541 - Save memory by storing microdescriptor family lists with a more
6542 compact representation. Closes ticket 27359.
6543 - Tor clients now use mmap() to read consensus files from disk, so
6544 that they no longer need keep the full text of a consensus in
6545 memory when parsing it or applying a diff. Closes ticket 27244.
6547 o Minor features (parsing):
6548 - Directory authorities now validate that router descriptors and
6549 ExtraInfo documents are in a valid subset of UTF-8, and reject
6550 them if they are not. Closes ticket 27367.
6552 o Minor features (performance):
6553 - Cache the results of summarize_protocol_flags(), so that we don't
6554 have to parse the same protocol-versions string over and over.
6555 This should save us a huge number of malloc calls on startup, and
6556 may reduce memory fragmentation with some allocators. Closes
6558 - Remove a needless memset() call from get_token_arguments, thereby
6559 speeding up the tokenization of directory objects by about 20%.
6560 Closes ticket 28852.
6561 - Replace parse_short_policy() with a faster implementation, to
6562 improve microdescriptor parsing time. Closes ticket 28853.
6563 - Speed up directory parsing a little by avoiding use of the non-
6564 inlined strcmp_len() function. Closes ticket 28856.
6565 - Speed up microdescriptor parsing by about 30%, to help improve
6566 startup time. Closes ticket 28839.
6568 o Minor features (pluggable transports):
6569 - Add support for emitting STATUS updates to Tor's control port from
6570 a pluggable transport process. Closes ticket 28846.
6571 - Add support for logging to Tor's logging subsystem from a
6572 pluggable transport process. Closes ticket 28180.
6574 o Minor features (process management):
6575 - Add a new process API for handling child processes. This new API
6576 allows Tor to have bi-directional communication with child
6577 processes on both Unix and Windows. Closes ticket 28179.
6578 - Use the subsystem manager to initialize and shut down the process
6579 module. Closes ticket 28847.
6581 o Minor features (relay):
6582 - When listing relay families, list them in canonical form including
6583 the relay's own identity, and try to give a more useful set of
6584 warnings. Part of ticket 28266 and proposal 298.
6586 o Minor features (required protocols):
6587 - Before exiting because of a missing required protocol, Tor will
6588 now check the publication time of the consensus, and not exit
6589 unless the consensus is newer than the Tor program's own release
6590 date. Previously, Tor would not check the consensus publication
6591 time, and so might exit because of a missing protocol that might
6592 no longer be required in a current consensus. Implements proposal
6593 297; closes ticket 27735.
6595 o Minor features (testing):
6596 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
6597 networks. Closes ticket 28840. Patch by Rob Jansen.
6599 o Minor bugfixes (client, clock skew):
6600 - Bootstrap successfully even when Tor's clock is behind the clocks
6601 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
6602 - Select guards even if the consensus has expired, as long as the
6603 consensus is still reasonably live. Fixes bug 24661; bugfix
6606 o Minor bugfixes (compilation):
6607 - Compile correctly on OpenBSD; previously, we were missing some
6608 headers required in order to detect it properly. Fixes bug 28938;
6609 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
6611 o Minor bugfixes (directory clients):
6612 - Mark outdated dirservers when Tor only has a reasonably live
6613 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
6615 o Minor bugfixes (directory mirrors):
6616 - Even when a directory mirror's clock is behind the clocks on the
6617 authorities, we now allow the mirror to serve "future"
6618 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
6620 o Minor bugfixes (DNS):
6621 - Gracefully handle an empty or absent resolve.conf file by falling
6622 back to using "localhost" as a DNS server (and hoping it works).
6623 Previously, we would just stop running as an exit. Fixes bug
6624 21900; bugfix on 0.2.1.10-alpha.
6626 o Minor bugfixes (guards):
6627 - In count_acceptable_nodes(), the minimum number is now one bridge
6628 or guard node, and two non-guard nodes for a circuit. Previously,
6629 we had added up the sum of all nodes with a descriptor, but that
6630 could cause us to build failing circuits when we had either too
6631 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
6632 0.2.3.1-alpha. Patch by Neel Chauhan.
6634 o Minor bugfixes (IPv6):
6635 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
6636 IPv6 socket was bound using an address family of AF_INET instead
6637 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
6640 o Minor bugfixes (logging):
6641 - Rework rep_hist_log_link_protocol_counts() to iterate through all
6642 link protocol versions when logging incoming/outgoing connection
6643 counts. Tor no longer skips version 5, and we won't have to
6644 remember to update this function when new link protocol version is
6645 developed. Fixes bug 28920; bugfix on 0.2.6.10.
6647 o Minor bugfixes (networking):
6648 - Introduce additional checks into tor_addr_parse() to reject
6649 certain incorrect inputs that previously were not detected. Fixes
6650 bug 23082; bugfix on 0.2.0.10-alpha.
6652 o Minor bugfixes (onion service v3, client):
6653 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
6654 connection waiting for a descriptor that we actually have in the
6655 cache. It turns out that this can actually happen, though it is
6656 rare. Now, tor will recover and retry the descriptor. Fixes bug
6657 28669; bugfix on 0.3.2.4-alpha.
6659 o Minor bugfixes (periodic events):
6660 - Refrain from calling routerlist_remove_old_routers() from
6661 check_descriptor_callback(). Instead, create a new hourly periodic
6662 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
6664 o Minor bugfixes (pluggable transports):
6665 - Make sure that data is continously read from standard output and
6666 standard error pipes of a pluggable transport child-process, to
6667 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
6668 bugfix on 0.2.3.6-alpha.
6670 o Minor bugfixes (unit tests):
6671 - Instead of relying on hs_free_all() to clean up all onion service
6672 objects in test_build_descriptors(), we now deallocate them one by
6673 one. This lets Coverity know that we are not leaking memory there
6674 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
6676 o Minor bugfixes (usability):
6677 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
6678 Some users took this phrasing to mean that the mentioned guard was
6679 under their control or responsibility, which it is not. Fixes bug
6680 28895; bugfix on Tor 0.3.0.1-alpha.
6682 o Code simplification and refactoring:
6683 - Reimplement NETINFO cell parsing and generation to rely on
6684 trunnel-generated wire format handling code. Closes ticket 27325.
6685 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
6687 - Rework SOCKS wire format handling to rely on trunnel-generated
6688 parsing/generation code. Resolves ticket 27620.
6689 - Split out bootstrap progress reporting from control.c into a
6690 separate file. Part of ticket 27402.
6691 - The .may_include files that we use to describe our directory-by-
6692 directory dependency structure now describe a noncircular
6693 dependency graph over the directories that they cover. Our
6694 checkIncludes.py tool now enforces this noncircularity. Closes
6698 - Mention that you cannot add a new onion service if Tor is already
6699 running with Sandbox enabled. Closes ticket 28560.
6700 - Improve ControlPort documentation. Mention that it accepts
6701 address:port pairs, and can be used multiple times. Closes
6703 - Document the exact output of "tor --version". Closes ticket 28889.
6706 - Stop responding to the 'GETINFO status/version/num-concurring' and
6707 'GETINFO status/version/num-versioning' control port commands, as
6708 those were deprecated back in 0.2.0.30. Also stop listing them in
6709 output of 'GETINFO info/names'. Resolves ticket 28757.
6710 - The scripts used to generate and maintain the list of fallback
6711 directories have been extracted into a new "fallback-scripts"
6712 repository. Closes ticket 27914.
6715 - Run shellcheck for scripts in the in scripts/ directory. Closes
6717 - Add unit tests for tokenize_string() and get_next_token()
6718 functions. Resolves ticket 27625.
6720 o Code simplification and refactoring (onion service v3):
6721 - Consolidate the authorized client descriptor cookie computation
6722 code from client and service into one function. Closes
6725 o Code simplification and refactoring (shell scripts):
6726 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
6728 - Fix issues that shellcheck found in chutney-git-bisect.sh.
6729 Resolves ticket 28006.
6730 - Fix issues that shellcheck found in updateRustDependencies.sh.
6731 Resolves ticket 28012.
6732 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
6733 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
6734 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
6735 - Fix shellcheck warnings in scripts/test/coverage. Resolves
6739 Changes in version 0.3.3.11 - 2019-01-07
6740 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
6741 numerous fixes, including an important fix for anyone using OpenSSL
6742 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
6743 to this version, or to a later series.
6745 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
6746 We anticipate that this will be the last release of Tor 0.3.3, unless
6747 some major bug is before then. Some time between now and then, users
6748 should switch to either the Tor 0.3.4 series (supported until at least
6749 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
6750 support until at least 1 Feb 2022.
6752 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
6753 - Fix our usage of named groups when running as a TLS 1.3 client in
6754 OpenSSL 1.1.1. Previously, we only initialized EC groups when
6755 running as a relay, which caused clients to fail to negotiate TLS
6756 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
6759 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
6760 - Fix a use-after-free error that could be caused by passing Tor an
6761 impossible set of options that would fail during options_act().
6762 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
6764 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
6765 - Only run one online rust build in Travis, to reduce network
6766 errors. Skip offline rust builds on Travis for Linux gcc, because
6767 they're redundant. Implements ticket 27252.
6768 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
6769 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
6770 Linux with default settings, because all the non-default builds
6771 use gcc on Linux. Implements ticket 27252.
6773 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
6774 - Use the Travis Homebrew addon to install packages on macOS during
6775 Travis CI. The package list is the same, but the Homebrew addon
6776 does not do a `brew update` by default. Implements ticket 27738.
6778 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
6779 - Replace the 150 fallbacks originally introduced in Tor
6780 0.3.3.1-alpha in January 2018 (of which ~115 were still
6781 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
6782 removed) generated in December 2018. Closes ticket 24803.
6784 o Minor features (geoip):
6785 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
6786 Country database. Closes ticket 29012.
6788 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
6789 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
6790 key export function from handling long labels. When this bug is
6791 detected, Tor will disable TLS 1.3. We recommend upgrading to a
6792 version of OpenSSL without this bug when it becomes available.
6793 Closes ticket 28973.
6795 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
6796 - Update relay descriptor on bandwidth changes only when the uptime
6797 is smaller than 24h, in order to reduce the efficiency of guard
6798 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
6800 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
6801 - Avoid undefined behavior in an end-of-string check when parsing
6802 the BEGIN line in a directory object. Fixes bug 28202; bugfix
6805 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
6806 - Rewrite our assertion macros so that they no longer suppress the
6807 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
6809 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
6810 - Initialize a variable unconditionally in aes_new_cipher(), since
6811 some compilers cannot tell that we always initialize it before
6812 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
6814 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
6815 - Log additional info when we get a relay that shares an ed25519 ID
6816 with a different relay, instead making a BUG() warning. Fixes bug
6817 27800; bugfix on 0.3.2.1-alpha.
6819 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
6820 - When a user requests a group-readable DataDirectory, give it to
6821 them. Previously, when the DataDirectory and the CacheDirectory
6822 were the same, the default setting (0) for
6823 CacheDirectoryGroupReadable would override the setting for
6824 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
6827 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
6828 - When the onion service directory can't be created or has the wrong
6829 permissions, do not log a stack trace. Fixes bug 27335; bugfix
6832 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
6833 - Close all SOCKS request (for the same .onion) if the newly fetched
6834 descriptor is unusable. Before that, we would close only the first
6835 one leaving the other hanging and let to time out by themselves.
6836 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
6838 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
6839 - Don't warn so loudly when Tor is unable to decode an onion
6840 descriptor. This can now happen as a normal use case if a client
6841 gets a descriptor with client authorization but the client is not
6842 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
6844 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
6845 - When deleting an ephemeral onion service (DEL_ONION), do not close
6846 any rendezvous circuits in order to let the existing client
6847 connections finish by themselves or closed by the application. The
6848 HS v2 is doing that already so now we have the same behavior for
6849 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
6851 o Minor bugfixes (HTTP tunnel):
6852 - Fix a bug warning when closing an HTTP tunnel connection due to
6853 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
6856 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
6857 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
6858 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
6860 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
6861 - Ensure circuitmux queues are empty before scheduling or sending
6862 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
6864 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
6865 - Reject protocol names containing bytes other than alphanumeric
6866 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
6869 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
6870 - Compute protover votes correctly in the rust version of the
6871 protover code. Previously, the protover rewrite in 24031 allowed
6872 repeated votes from the same voter for the same protocol version
6873 to be counted multiple times in protover_compute_vote(). Fixes bug
6874 27649; bugfix on 0.3.3.5-rc.
6875 - Reject protover names that contain invalid characters. Fixes bug
6876 27687; bugfix on 0.3.3.1-alpha.
6878 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
6879 - protover_all_supported() would attempt to allocate up to 16GB on
6880 some inputs, leading to a potential memory DoS. Fixes bug 27206;
6881 bugfix on 0.3.3.5-rc.
6883 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
6884 - Fix a potential null dereference in protover_all_supported(). Add
6885 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
6886 - Return a string that can be safely freed by C code, not one
6887 created by the rust allocator, in protover_all_supported(). Fixes
6888 bug 27740; bugfix on 0.3.3.1-alpha.
6889 - Fix an API mismatch in the rust implementation of
6890 protover_compute_vote(). This bug could have caused crashes on any
6891 directory authorities running Tor with Rust (which we do not yet
6892 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
6894 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
6895 - If a unit test running in a subprocess exits abnormally or with a
6896 nonzero status code, treat the test as having failed, even if the
6897 test reported success. Without this fix, memory leaks don't cause
6898 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
6899 bugfix on 0.2.2.4-alpha.
6901 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
6902 - Treat backtrace test failures as expected on BSD-derived systems
6903 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
6904 (FreeBSD failures have been treated as expected since 18204 in
6905 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
6907 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
6908 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
6909 bugfix on 0.3.0.1-alpha.
6912 Changes in version 0.3.4.10 - 2019-01-07
6913 Tor 0.3.4.9 is the second stable release in its series; it backports
6914 numerous fixes, including an important fix for relays, and for anyone
6915 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
6918 As a reminder, the Tor 0.3.4 series will be supported until 10 June
6919 2019. Some time between now and then, users should switch to the Tor
6920 0.3.5 series, which will receive long-term support until at least 1
6923 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
6924 - Fix our usage of named groups when running as a TLS 1.3 client in
6925 OpenSSL 1.1.1. Previously, we only initialized EC groups when
6926 running as a relay, which caused clients to fail to negotiate TLS
6927 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
6930 o Major bugfixes (relay, directory, backport from 0.3.5.7):
6931 - Always reactivate linked connections in the main loop so long as
6932 any linked connection has been active. Previously, connections
6933 serving directory information wouldn't get reactivated after the
6934 first chunk of data was sent (usually 32KB), which would prevent
6935 clients from bootstrapping. Fixes bug 28912; bugfix on
6936 0.3.4.1-alpha. Patch by "cypherpunks3".
6938 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
6939 - Always show the configure and test logs, and upload them as build
6940 artifacts, when building for Windows using Appveyor CI.
6943 o Minor features (controller, backport from 0.3.5.1-alpha):
6944 - For purposes of CIRC_BW-based dropped cell detection, track half-
6945 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
6946 bias check cells to arrive without counting it as dropped until
6947 either the END arrives, or the windows are empty. Closes
6950 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
6951 - Replace the 150 fallbacks originally introduced in Tor
6952 0.3.3.1-alpha in January 2018 (of which ~115 were still
6953 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
6954 removed) generated in December 2018. Closes ticket 24803.
6956 o Minor features (geoip):
6957 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
6958 Country database. Closes ticket 28395.
6960 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
6961 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
6962 key export function from handling long labels. When this bug is
6963 detected, Tor will disable TLS 1.3. We recommend upgrading to a
6964 version of OpenSSL without this bug when it becomes available.
6965 Closes ticket 28973.
6967 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
6968 - Initialize a variable unconditionally in aes_new_cipher(), since
6969 some compilers cannot tell that we always initialize it before
6970 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
6972 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
6973 - Avoid a logging a BUG() stacktrace when closing connection held
6974 open because the write side is rate limited but not the read side.
6975 Now, the connection read side is simply shut down until Tor is
6976 able to flush the connection and close it. Fixes bug 27750; bugfix
6979 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
6980 - Manually configure the zstd compiler options, when building using
6981 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
6982 not come with a pkg-config file. Fixes bug 28454; bugfix
6984 - Stop using an external OpenSSL install, and stop installing MSYS2
6985 packages, when building using mingw on Appveyor Windows CI. Fixes
6986 bug 28399; bugfix on 0.3.4.1-alpha.
6988 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
6989 - Explicitly specify the path to the OpenSSL library and do not
6990 download OpenSSL from Pacman, but instead use the library that is
6991 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
6993 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
6994 - When a user requests a group-readable DataDirectory, give it to
6995 them. Previously, when the DataDirectory and the CacheDirectory
6996 were the same, the default setting (0) for
6997 CacheDirectoryGroupReadable would override the setting for
6998 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
7001 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
7002 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
7003 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
7005 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
7006 - Don't warn so loudly when Tor is unable to decode an onion
7007 descriptor. This can now happen as a normal use case if a client
7008 gets a descriptor with client authorization but the client is not
7009 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
7011 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
7012 - When deleting an ephemeral onion service (DEL_ONION), do not close
7013 any rendezvous circuits in order to let the existing client
7014 connections finish by themselves or closed by the application. The
7015 HS v2 is doing that already so now we have the same behavior for
7016 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
7018 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
7019 - Update relay descriptor on bandwidth changes only when the uptime
7020 is smaller than 24h, in order to reduce the efficiency of guard
7021 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
7023 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
7024 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
7025 bugfix on 0.3.0.1-alpha.
7028 Changes in version 0.3.5.7 - 2019-01-07
7029 Tor 0.3.5.7 is the first stable release in its series; it includes
7030 compilation and portability fixes, and a fix for a severe problem
7031 affecting directory caches.
7033 The Tor 0.3.5 series includes several new features and performance
7034 improvements, including client authorization for v3 onion services,
7035 cleanups to bootstrap reporting, support for improved bandwidth-
7036 measurement tools, experimental support for NSS in place of OpenSSL,
7037 and much more. It also begins a full reorganization of Tor's code
7038 layout, for improved modularity and maintainability in the future.
7039 Finally, there is the usual set of performance improvements and
7040 bugfixes that we try to do in every release series.
7042 There are a couple of changes in the 0.3.5 that may affect
7043 compatibility. First, the default version for newly created onion
7044 services is now v3. Use the HiddenServiceVersion option if you want to
7045 override this. Second, some log messages related to bootstrapping have
7046 changed; if you use stem, you may need to update to the latest version
7047 so it will recognize them.
7049 We have designated 0.3.5 as a "long-term support" (LTS) series: we
7050 will continue to patch major bugs in typical configurations of 0.3.5
7051 until at least 1 Feb 2022. (We do not plan to provide long-term
7052 support for embedding, Rust support, NSS support, running a directory
7053 authority, or unsupported platforms. For these, you will need to stick
7054 with the latest stable release.)
7056 Below are the changes since 0.3.5.6-rc. For a complete list of changes
7057 since 0.3.4.9, see the ReleaseNotes file.
7059 o Major bugfixes (relay, directory):
7060 - Always reactivate linked connections in the main loop so long as
7061 any linked connection has been active. Previously, connections
7062 serving directory information wouldn't get reactivated after the
7063 first chunk of data was sent (usually 32KB), which would prevent
7064 clients from bootstrapping. Fixes bug 28912; bugfix on
7065 0.3.4.1-alpha. Patch by "cypherpunks3".
7067 o Minor features (compilation):
7068 - When possible, place our warning flags in a separate file, to
7069 avoid flooding verbose build logs. Closes ticket 28924.
7071 o Minor features (geoip):
7072 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
7073 Country database. Closes ticket 29012.
7075 o Minor features (OpenSSL bug workaround):
7076 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
7077 key export function from handling long labels. When this bug is
7078 detected, Tor will disable TLS 1.3. We recommend upgrading to a
7079 version of OpenSSL without this bug when it becomes available.
7080 Closes ticket 28973.
7082 o Minor features (performance):
7083 - Remove about 96% of the work from the function that we run at
7084 startup to test our curve25519_basepoint implementation. Since
7085 this function has yet to find an actual failure, we now only run
7086 it for 8 iterations instead of 200. Based on our profile
7087 information, this change should save around 8% of our startup time
7088 on typical desktops, and may have a similar effect on other
7089 platforms. Closes ticket 28838.
7090 - Stop re-validating our hardcoded Diffie-Hellman parameters on
7091 every startup. Doing this wasted time and cycles, especially on
7092 low-powered devices. Closes ticket 28851.
7094 o Minor bugfixes (compilation):
7095 - Fix compilation for Android by adding a missing header to
7096 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
7098 o Minor bugfixes (correctness):
7099 - Fix an unreached code path where we checked the value of
7100 "hostname" inside send_resolved_hostname_cell(). Previously, we
7101 used it before checking it; now we check it first. Fixes bug
7102 28879; bugfix on 0.1.2.7-alpha.
7104 o Minor bugfixes (testing):
7105 - Make sure that test_rebind.py actually obeys its timeout, even
7106 when it receives a large number of log messages. Fixes bug 28883;
7107 bugfix on 0.3.5.4-alpha.
7108 - Stop running stem's unit tests as part of "make test-stem", but
7109 continue to run stem's unit and online tests during "make test-
7110 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
7112 o Minor bugfixes (windows services):
7113 - Make Tor start correctly as an NT service again: previously it was
7114 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
7116 o Code simplification and refactoring:
7117 - When parsing a port configuration, make it more obvious to static
7118 analyzer tools that we always initialize the address. Closes
7122 Changes in version 0.3.5.6-rc - 2018-12-18
7123 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
7124 It is the first release candidate in the 0.3.5.x series; if no further
7125 huge bugs are found, our next release may be the stable 0.3.5.x.
7127 o Minor features (continuous integration, Windows):
7128 - Always show the configure and test logs, and upload them as build
7129 artifacts, when building for Windows using Appveyor CI.
7132 o Minor features (fallback directory list):
7133 - Replace the 150 fallbacks originally introduced in Tor
7134 0.3.3.1-alpha in January 2018 (of which ~115 were still
7135 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
7136 removed) generated in December 2018. Closes ticket 24803.
7138 o Minor features (geoip):
7139 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
7140 Country database. Closes ticket 28744.
7142 o Minor bugfixes (compilation):
7143 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
7144 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
7146 o Minor bugfixes (continuous integration, Windows):
7147 - Explicitly specify the path to the OpenSSL library and do not
7148 download OpenSSL from Pacman, but instead use the library that is
7149 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
7151 o Minor bugfixes (onion service v3):
7152 - When deleting an ephemeral onion service (DEL_ONION), do not close
7153 any rendezvous circuits in order to let the existing client
7154 connections finish by themselves or closed by the application. The
7155 HS v2 is doing that already so now we have the same behavior for
7156 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
7158 o Minor bugfixes (restart-in-process, boostrap):
7159 - Add missing resets of bootstrap tracking state when shutting down
7160 (regression caused by ticket 27169). Fixes bug 28524; bugfix
7163 o Minor bugfixes (testing):
7164 - Use a separate DataDirectory for the test_rebind script.
7165 Previously, this script would run using the default DataDirectory,
7166 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
7167 Patch from Taylor R Campbell.
7168 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
7169 bugfix on 0.3.0.1-alpha.
7171 o Minor bugfixes (Windows):
7172 - Correctly identify Windows 8.1, Windows 10, and Windows Server
7173 2008 and later from their NT versions. Fixes bug 28096; bugfix on
7174 0.2.2.34; reported by Keifer Bly.
7175 - On recent Windows versions, the GetVersionEx() function may report
7176 an earlier Windows version than the running OS. To avoid user
7177 confusion, add "[or later]" to Tor's version string on affected
7178 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
7180 - Remove Windows versions that were never supported by the
7181 GetVersionEx() function. Stop duplicating the latest Windows
7182 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
7183 reported by Keifer Bly.
7186 - Increase logging and tag all log entries with timestamps in
7187 test_rebind.py. Provides diagnostics for issue 28229.
7189 o Code simplification and refactoring (shared random, dirauth):
7190 - Change many tor_assert() to use BUG() instead. The idea is to not
7191 crash a dirauth but rather scream loudly with a stacktrace and let
7192 it continue run. The shared random subsystem is very resilient and
7193 if anything wrong happens with it, at worst a non coherent value
7194 will be put in the vote and discarded by the other authorities.
7195 Closes ticket 19566.
7197 o Documentation (onion services):
7198 - Document in the man page that changing ClientOnionAuthDir value or
7199 adding a new file in the directory will not work at runtime upon
7200 sending a HUP if Sandbox 1. Closes ticket 28128.
7201 - Note in the man page that the only real way to fully revoke an
7202 onion service v3 client authorization is by restarting the tor
7203 process. Closes ticket 28275.
7206 Changes in version 0.3.5.5-alpha - 2018-11-16
7207 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
7208 including several that we hope to backport to older release series in
7211 o Major bugfixes (OpenSSL, portability):
7212 - Fix our usage of named groups when running as a TLS 1.3 client in
7213 OpenSSL 1.1.1. Previously, we only initialized EC groups when
7214 running as a relay, which caused clients to fail to negotiate TLS
7215 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
7218 o Minor features (geoip):
7219 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
7220 Country database. Closes ticket 28395.
7222 o Minor bugfixes (compilation):
7223 - Initialize a variable unconditionally in aes_new_cipher(), since
7224 some compilers cannot tell that we always initialize it before
7225 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
7227 o Minor bugfixes (connection, relay):
7228 - Avoid a logging a BUG() stacktrace when closing connection held
7229 open because the write side is rate limited but not the read side.
7230 Now, the connection read side is simply shut down until Tor is
7231 able to flush the connection and close it. Fixes bug 27750; bugfix
7234 o Minor bugfixes (continuous integration, Windows):
7235 - Manually configure the zstd compiler options, when building using
7236 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
7237 not come with a pkg-config file. Fixes bug 28454; bugfix
7239 - Stop using an external OpenSSL install, and stop installing MSYS2
7240 packages, when building using mingw on Appveyor Windows CI. Fixes
7241 bug 28399; bugfix on 0.3.4.1-alpha.
7243 o Minor bugfixes (documentation):
7244 - Make Doxygen work again after the code movement in the 0.3.5
7245 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
7247 o Minor bugfixes (Linux seccomp2 sandbox):
7248 - Permit the "shutdown()" system call, which is apparently used by
7249 OpenSSL under some circumstances. Fixes bug 28183; bugfix
7252 o Minor bugfixes (logging):
7253 - Stop talking about the Named flag in log messages. Clients have
7254 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
7257 o Minor bugfixes (memory leaks):
7258 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
7259 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
7261 o Minor bugfixes (onion services):
7262 - On an intro point for a version 3 onion service, stop closing
7263 introduction circuits on an NACK. This lets the client decide
7264 whether to reuse the circuit or discard it. Previously, we closed
7265 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
7266 0.3.2.1-alpha. Patch by Neel Chaunan.
7267 - When replacing a descriptor in the client cache, make sure to
7268 close all client introduction circuits for the old descriptor, so
7269 we don't end up with unusable leftover circuits. Fixes bug 27471;
7270 bugfix on 0.3.2.1-alpha.
7273 Changes in version 0.3.5.4-alpha - 2018-11-08
7274 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
7275 improves our continuous integration support. It continues our attempts
7276 to stabilize this alpha branch and build it into a foundation for an
7277 acceptable long-term-support release.
7279 o Major bugfixes (compilation, rust):
7280 - Rust tests can now build and run successfully with the
7281 --enable-fragile-hardening option enabled. Doing this currently
7282 requires the rust beta channel; it will be possible with stable
7283 rust once Rust version 1.31 is released. Patch from Alex Crichton.
7284 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
7286 o Major bugfixes (embedding, main loop):
7287 - When DisableNetwork becomes set, actually disable periodic events
7288 that are already enabled. (Previously, we would refrain from
7289 enabling new ones, but we would leave the old ones turned on.)
7290 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
7292 o Minor features (continuous integration):
7293 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
7295 - Add new CI job to Travis configuration to run stem-based
7296 integration tests. Closes ticket 27913.
7298 o Minor features (Windows, continuous integration):
7299 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
7300 Appveyor's CI. Closes ticket 28318.
7302 o Minor bugfixes (C correctness, also in 0.3.4.9):
7303 - Avoid undefined behavior in an end-of-string check when parsing
7304 the BEGIN line in a directory object. Fixes bug 28202; bugfix
7307 o Minor bugfixes (compilation):
7308 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
7309 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
7311 o Minor bugfixes (compilation, OpenSolaris):
7312 - Fix compilation on OpenSolaris and its descendants by adding a
7313 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
7316 o Minor bugfixes (configuration):
7317 - Refuse to start with relative file paths and RunAsDaemon set
7318 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
7321 o Minor bugfixes (directory authority, also in 0.3.4.9):
7322 - Log additional info when we get a relay that shares an ed25519 ID
7323 with a different relay, instead of a BUG() warning with a
7324 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
7326 o Minor bugfixes (onion service v3):
7327 - Build the service descriptor's signing key certificate before
7328 uploading, so we always have a fresh one: leaving no chances for
7329 it to expire service side. Fixes bug 27838; bugfix
7332 o Minor bugfixes (onion service v3, client authorization):
7333 - Fix an assert() when adding a client authorization for the first
7334 time and then sending a HUP signal to the service. Before that,
7335 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
7337 o Minor bugfixes (onion services):
7338 - Unless we have explicitly set HiddenServiceVersion, detect the
7339 onion service version and then look for invalid options.
7340 Previously, we did the reverse, but that broke existing configs
7341 which were pointed to a v2 service and had options like
7342 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
7343 0.3.5.1-alpha. Patch by Neel Chauhan.
7345 o Minor bugfixes (portability):
7346 - Make the OPE code (which is used for v3 onion services) run
7347 correctly on big-endian platforms. Fixes bug 28115; bugfix
7350 o Minor bugfixes (protover, rust):
7351 - Reject extra commas in version strings. Fixes bug 27197; bugfix
7354 o Minor bugfixes (relay shutdown, systemd):
7355 - Notify systemd of ShutdownWaitLength so it can be set to longer
7356 than systemd's TimeoutStopSec. In Tor's systemd service file, set
7357 TimeoutSec to 60 seconds to allow Tor some time to shut down.
7358 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
7360 o Minor bugfixes (rust, also in 0.3.4.9):
7361 - Fix a potential null dereference in protover_all_supported(). Add
7362 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
7363 - Return a string that can be safely freed by C code, not one
7364 created by the rust allocator, in protover_all_supported(). Fixes
7365 bug 27740; bugfix on 0.3.3.1-alpha.
7367 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
7368 - Fix an API mismatch in the rust implementation of
7369 protover_compute_vote(). This bug could have caused crashes on any
7370 directory authorities running Tor with Rust (which we do not yet
7371 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
7373 o Minor bugfixes (testing):
7374 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
7375 27968; bugfix on 0.3.5.1-alpha.
7377 o Minor bugfixes (testing, also in 0.3.4.9):
7378 - Treat backtrace test failures as expected on BSD-derived systems
7379 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
7380 (FreeBSD failures have been treated as expected since 18204 in
7381 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
7383 o Documentation (onion service manpage):
7384 - Improve HSv3 client authorization by making some options more
7385 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
7388 Changes in version 0.3.4.9 - 2018-11-02
7389 Tor 0.3.4.9 is the second stable release in its series; it backports
7390 numerous fixes, including a fix for a bandwidth management bug that
7391 was causing memory exhaustion on relays. Anyone running an earlier
7392 version of Tor 0.3.4.9 should upgrade.
7394 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
7395 - Fix compilation on ARM (and other less-used CPUs) when compiling
7396 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
7398 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
7399 - Make sure Tor bootstraps and works properly if only the
7400 ControlPort is set. Prior to this fix, Tor would only bootstrap
7401 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
7402 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
7404 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
7405 - When our write bandwidth limit is exhausted, stop writing on the
7406 connection. Previously, we had a typo in the code that would make
7407 us stop reading instead, leading to relay connections being stuck
7408 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
7411 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
7412 - Fix a use-after-free error that could be caused by passing Tor an
7413 impossible set of options that would fail during options_act().
7414 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
7416 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
7417 - Don't do a distcheck with --disable-module-dirauth in Travis.
7418 Implements ticket 27252.
7419 - Only run one online rust build in Travis, to reduce network
7420 errors. Skip offline rust builds on Travis for Linux gcc, because
7421 they're redundant. Implements ticket 27252.
7422 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
7423 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
7424 Linux with default settings, because all the non-default builds
7425 use gcc on Linux. Implements ticket 27252.
7427 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
7428 - Use the Travis Homebrew addon to install packages on macOS during
7429 Travis CI. The package list is the same, but the Homebrew addon
7430 does not do a `brew update` by default. Implements ticket 27738.
7432 o Minor features (geoip):
7433 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
7434 Country database. Closes ticket 27991.
7436 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
7437 - Fix an integer overflow bug in our optimized 32-bit millisecond-
7438 difference algorithm for 32-bit Apple platforms. Previously, it
7439 would overflow when calculating the difference between two times
7440 more than 47 days apart. Fixes part of bug 27139; bugfix
7442 - Improve the precision of our 32-bit millisecond difference
7443 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
7444 bugfix on 0.3.4.1-alpha.
7445 - Relax the tolerance on the mainloop/update_time_jumps test when
7446 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
7449 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
7450 - Avoid undefined behavior in an end-of-string check when parsing
7451 the BEGIN line in a directory object. Fixes bug 28202; bugfix
7454 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
7455 - Only install the necessary mingw packages during our appveyor
7456 builds. This change makes the build a little faster, and prevents
7457 a conflict with a preinstalled mingw openssl that appveyor now
7458 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
7460 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
7461 - Rewrite our assertion macros so that they no longer suppress the
7462 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
7464 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
7465 - Stop reinstalling identical packages in our Windows CI. Fixes bug
7466 27464; bugfix on 0.3.4.1-alpha.
7468 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
7469 - Log additional info when we get a relay that shares an ed25519 ID
7470 with a different relay, instead making a BUG() warning. Fixes bug
7471 27800; bugfix on 0.3.2.1-alpha.
7473 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
7474 - Avoid a double-close when shutting down a stalled directory
7475 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
7477 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
7478 - Fix a bug warning when closing an HTTP tunnel connection due to an
7479 HTTP request we couldn't handle. Fixes bug 26470; bugfix
7482 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
7483 - Ensure circuitmux queues are empty before scheduling or sending
7484 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
7486 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
7487 - When the onion service directory can't be created or has the wrong
7488 permissions, do not log a stack trace. Fixes bug 27335; bugfix
7491 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
7492 - Close all SOCKS request (for the same .onion) if the newly fetched
7493 descriptor is unusable. Before that, we would close only the first
7494 one leaving the other hanging and let to time out by themselves.
7495 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
7497 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
7498 - When selecting a v3 rendezvous point, don't only look at the
7499 protover, but also check whether the curve25519 onion key is
7500 present. This way we avoid picking a relay that supports the v3
7501 rendezvous but for which we don't have the microdescriptor. Fixes
7502 bug 27797; bugfix on 0.3.2.1-alpha.
7504 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
7505 - Reject protocol names containing bytes other than alphanumeric
7506 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
7509 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
7510 - Compute protover votes correctly in the rust version of the
7511 protover code. Previously, the protover rewrite in 24031 allowed
7512 repeated votes from the same voter for the same protocol version
7513 to be counted multiple times in protover_compute_vote(). Fixes bug
7514 27649; bugfix on 0.3.3.5-rc.
7515 - Reject protover names that contain invalid characters. Fixes bug
7516 27687; bugfix on 0.3.3.1-alpha.
7518 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
7519 - protover_all_supported() would attempt to allocate up to 16GB on
7520 some inputs, leading to a potential memory DoS. Fixes bug 27206;
7521 bugfix on 0.3.3.5-rc.
7523 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
7524 - Fix an API mismatch in the rust implementation of
7525 protover_compute_vote(). This bug could have caused crashes on any
7526 directory authorities running Tor with Rust (which we do not yet
7527 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
7529 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
7530 - Fix a potential null dereference in protover_all_supported(). Add
7531 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
7532 - Return a string that can be safely freed by C code, not one
7533 created by the rust allocator, in protover_all_supported(). Fixes
7534 bug 27740; bugfix on 0.3.3.1-alpha.
7536 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
7537 - If a unit test running in a subprocess exits abnormally or with a
7538 nonzero status code, treat the test as having failed, even if the
7539 test reported success. Without this fix, memory leaks don't cause
7540 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
7541 bugfix on 0.2.2.4-alpha.
7543 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
7544 - Make the hs_service tests use the same time source when creating
7545 the introduction point and when testing it. Now tests work better
7546 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
7549 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
7550 - Treat backtrace test failures as expected on BSD-derived systems
7551 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
7552 (FreeBSD failures have been treated as expected since 18204 in
7553 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
7556 Changes in version 0.3.5.3-alpha - 2018-10-17
7557 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
7558 versions. One important fix for relays addresses a problem with rate-
7559 limiting code from back in 0.3.4.x: If the fix works out, we'll be
7560 backporting it soon. This release is still an alpha, but we hope it's
7561 getting closer and closer to stability.
7563 o Major features (onion services):
7564 - Version 3 onion services can now use the per-service
7565 HiddenServiceExportCircuitID option to differentiate client
7566 circuits. It communicates with the service by using the HAProxy
7567 protocol to assign virtual IP addresses to inbound client
7568 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
7570 o Major bugfixes (compilation):
7571 - Fix compilation on ARM (and other less-used CPUs) when compiling
7572 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
7574 o Major bugfixes (initialization, crash):
7575 - Fix an assertion crash that would stop Tor from starting up if it
7576 tried to activate a periodic event too early. Fixes bug 27861;
7577 bugfix on 0.3.5.1-alpha.
7579 o Major bugfixes (mainloop, bootstrap):
7580 - Make sure Tor bootstraps and works properly if only the
7581 ControlPort is set. Prior to this fix, Tor would only bootstrap
7582 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
7583 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
7585 o Major bugfixes (relay):
7586 - When our write bandwidth limit is exhausted, stop writing on the
7587 connection. Previously, we had a typo in the code that would make
7588 us stop reading instead, leading to relay connections being stuck
7589 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
7592 o Minor features (continuous integration):
7593 - Use the Travis Homebrew addon to install packages on macOS during
7594 Travis CI. The package list is the same, but the Homebrew addon
7595 does not do a `brew update` by default. Implements ticket 27738.
7596 - Report what program produced the mysterious core file that we
7597 occasionally see on Travis CI during make distcheck. Closes
7600 o Minor features (geoip):
7601 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
7602 Country database. Closes ticket 27991.
7604 o Minor bugfixes (code safety):
7605 - Rewrite our assertion macros so that they no longer suppress the
7606 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
7609 o Minor bugfixes (compilation):
7610 - Compile the ed25519-donna code with a correct declaration of
7611 crypto_strongest_rand(). Previously, we built it with one type,
7612 but linked it against another in the unit tests, which caused
7613 compilation failures with LTO enabled. This could have caused
7614 other undefined behavior in the tests. Fixes bug 27728; bugfix
7617 o Minor bugfixes (compilation, netbsd):
7618 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
7621 o Minor bugfixes (continuous integration, appveyor):
7622 - Install only the necessary mingw packages during our appveyor
7623 builds. This change makes the build a little faster, and prevents
7624 a conflict with a preinstalled mingw openssl that appveyor now
7625 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
7627 o Minor bugfixes (directory permissions):
7628 - When a user requests a group-readable DataDirectory, give it to
7629 them. Previously, when the DataDirectory and the CacheDirectory
7630 were the same, the default setting (0) for
7631 CacheDirectoryGroupReadable would override the setting for
7632 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
7635 o Minor bugfixes (memory leaks):
7636 - Fix a small memory leak when calling Tor with --dump-config. Fixes
7637 bug 27893; bugfix on 0.3.2.1-alpha.
7639 o Minor bugfixes (networking):
7640 - In retry_listeners_ports(), make sure that we're removing a member
7641 of old_conns smartlist at most once. Fixes bug 27808; bugfix
7643 - Refrain from attempting socket rebinding when old and new
7644 listeners are in different address families. Fixes bug 27928;
7645 bugfix on 0.3.5.1-alpha.
7647 o Minor bugfixes (onion service v3):
7648 - Stop dumping a stack trace when trying to connect to an intro
7649 point without having a descriptor for it. Fixes bug 27774; bugfix
7651 - Don't warn so loudly when Tor is unable to decode an onion
7652 descriptor. This can now happen as a normal use case if a client
7653 gets a descriptor with client authorization but the client is not
7654 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
7655 - When selecting a v3 rendezvous point, don't only look at the
7656 protover, but also check whether the curve25519 onion key is
7657 present. This way we avoid picking a relay that supports the v3
7658 rendezvous but for which we don't have the microdescriptor. Fixes
7659 bug 27797; bugfix on 0.3.2.1-alpha.
7661 o Minor bugfixes (protover):
7662 - Reject protocol names containing bytes other than alphanumeric
7663 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
7666 o Minor bugfixes (testing):
7667 - Make the hs_service tests use the same time source when creating
7668 the introduction point and when testing it. Now tests work better
7669 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
7671 - In test_rebind.py, check if the Python version is in the supported
7672 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
7674 o Code simplification and refactoring:
7675 - Divide more large Tor source files -- especially ones that span
7676 multiple areas of functionality -- into smaller parts, including
7677 onion.c and main.c. Closes ticket 26747.
7678 - Divide the "routerparse.c" module into separate modules for each
7679 group of parsed objects. Closes ticket 27924.
7680 - Move protover_rust.c to the same place protover.c was moved to.
7681 Closes ticket 27814.
7682 - Split directory.c into separate pieces for client, server, and
7683 common functionality. Closes ticket 26744.
7684 - Split the non-statistics-related parts from the rephist.c and
7685 geoip.c modules. Closes ticket 27892.
7686 - Split the router.c file into relay-only and shared components, to
7687 help with future modularization. Closes ticket 27864.
7690 - In the tor-resolve(1) manpage, fix the reference to socks-
7691 extensions.txt by adding a web URL. Resolves ticket 27853.
7692 - Mention that we require Python to be 2.7 or newer for some
7693 integration tests that we ship with Tor. Resolves ticket 27677.
7696 Changes in version 0.3.5.2-alpha - 2018-09-21
7697 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
7698 that made Tor think it had run out of sockets. Anybody running a relay
7699 or an onion service on 0.3.5.1-alpha should upgrade.
7701 o Major bugfixes (relay bandwidth statistics):
7702 - When we close relayed circuits, report the data in the circuit
7703 queues as being written in our relay bandwidth stats. This
7704 mitigates guard discovery and other attacks that close circuits
7705 for the explicit purpose of noticing this discrepancy in
7706 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
7708 o Major bugfixes (socket accounting):
7709 - In our socket accounting code, count a socket as closed even when
7710 it is closed indirectly by the TLS layer. Previously, we would
7711 count these sockets as still in use, and incorrectly believe that
7712 we had run out of sockets. Fixes bug 27795; bugfix
7715 o Minor bugfixes (32-bit OSX and iOS, timing):
7716 - Fix an integer overflow bug in our optimized 32-bit millisecond-
7717 difference algorithm for 32-bit Apple platforms. Previously, it
7718 would overflow when calculating the difference between two times
7719 more than 47 days apart. Fixes part of bug 27139; bugfix
7721 - Improve the precision of our 32-bit millisecond difference
7722 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
7723 bugfix on 0.3.4.1-alpha.
7724 - Relax the tolerance on the mainloop/update_time_jumps test when
7725 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
7728 o Minor bugfixes (onion service v3):
7729 - Close all SOCKS request (for the same .onion) if the newly fetched
7730 descriptor is unusable. Before that, we would close only the first
7731 one leaving the other hanging and let to time out by themselves.
7732 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
7734 o Minor bugfixes (memory leak):
7735 - Fix an unlikely memory leak when trying to read a private key from
7736 a ridiculously large file. Fixes bug 27764; bugfix on
7737 0.3.5.1-alpha. This is CID 1439488.
7739 o Minor bugfixes (NSS):
7740 - Correctly detect failure to open a dummy TCP socket when stealing
7741 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
7744 o Minor bugfixes (rust):
7745 - protover_all_supported() would attempt to allocate up to 16GB on
7746 some inputs, leading to a potential memory DoS. Fixes bug 27206;
7747 bugfix on 0.3.3.5-rc.
7749 o Minor bugfixes (testing):
7750 - Revise the "conditionvar_timeout" test so that it succeeds even on
7751 heavily loaded systems where the test threads are not scheduled
7752 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
7754 o Code simplification and refactoring:
7755 - Divide the routerlist.c and dirserv.c modules into smaller parts.
7756 Closes ticket 27799.
7759 Changes in version 0.3.5.1-alpha - 2018-09-18
7760 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
7761 client authorization for modern (v3) onion services, improves
7762 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
7763 support for NSS in place of OpenSSL, and much more.
7765 o Major features (onion services, UI change):
7766 - For a newly created onion service, the default version is now 3.
7767 Tor still supports existing version 2 services, but the operator
7768 now needs to set "HiddenServiceVersion 2" in order to create a new
7769 version 2 service. For existing services, Tor now learns the
7770 version by reading the key file. Closes ticket 27215.
7772 o Major features (relay, UI change):
7773 - Relays no longer run as exits by default. If the "ExitRelay"
7774 option is auto (or unset), and no exit policy is specified with
7775 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
7776 Previously in this case, we allowed exit traffic and logged a
7777 warning message. Closes ticket 21530. Patch by Neel Chauhan.
7778 - Tor now validates that the ContactInfo config option is valid UTF-
7779 8 when parsing torrc. Closes ticket 27428.
7781 o Major features (bootstrap):
7782 - Don't report directory progress until after a connection to a
7783 relay or bridge has succeeded. Previously, we'd report 80%
7784 progress based on cached directory information when we couldn't
7785 even connect to the network. Closes ticket 27169.
7787 o Major features (new code layout):
7788 - Nearly all of Tor's source code has been moved around into more
7789 logical places. The "common" directory is now divided into a set
7790 of libraries in "lib", and files in the "or" directory have been
7791 split into "core" (logic absolutely needed for onion routing),
7792 "feature" (independent modules in Tor), and "app" (to configure
7793 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
7794 more information. Closes ticket 26481.
7796 This refactoring is not complete: although the libraries have been
7797 refactored to be acyclic, the main body of Tor is still too
7798 interconnected. We will attempt to improve this in the future.
7800 o Major features (onion services v3):
7801 - Implement onion service client authorization at the descriptor
7802 level: only authorized clients can decrypt a service's descriptor
7803 to find out how to contact it. A new torrc option was added to
7804 control this client side: ClientOnionAuthDir <path>. On the
7805 service side, if the "authorized_clients/" directory exists in the
7806 onion service directory path, client configurations are read from
7807 the files within. See the manpage for more details. Closes ticket
7808 27547. Patch done by Suphanat Chunhapanya (haxxpop).
7809 - Improve revision counter generation in next-gen onion services.
7810 Onion services can now scale by hosting multiple instances on
7811 different hosts without synchronization between them, which was
7812 previously impossible because descriptors would get rejected by
7813 HSDirs. Addresses ticket 25552.
7815 o Major features (portability, cryptography, experimental, TLS):
7816 - Tor now has the option to compile with the NSS library instead of
7817 OpenSSL. This feature is experimental, and we expect that bugs may
7818 remain. It is mainly intended for environments where Tor's
7819 performance is not CPU-bound, and where NSS is already known to be
7820 installed. To try it out, configure Tor with the --enable-nss
7821 flag. Closes tickets 26631, 26815, and 26816.
7823 If you are experimenting with this option and using an old cached
7824 consensus, Tor may fail to start. To solve this, delete your
7825 "cached-consensus" and "cached-microdesc-consensus" files,
7826 (if present), and restart Tor.
7828 o Major bugfixes (directory authority):
7829 - Actually check that the address we get from DirAuthority
7830 configuration line is valid IPv4. Explicitly disallow DirAuthority
7831 address to be a DNS hostname. Fixes bug 26488; bugfix
7834 o Major bugfixes (restart-in-process):
7835 - Fix a use-after-free error that could be caused by passing Tor an
7836 impossible set of options that would fail during options_act().
7837 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
7839 o Minor features (admin tools):
7840 - Add a new --key-expiration option to print the expiration date of
7841 the signing cert in an ed25519_signing_cert file. Resolves
7844 o Minor features (build):
7845 - If you pass the "--enable-pic" option to configure, Tor will try
7846 to tell the compiler to build position-independent code suitable
7847 to link into a dynamic library. (The default remains -fPIE, for
7848 code suitable for a relocatable executable.) Closes ticket 23846.
7850 o Minor features (code correctness, testing):
7851 - Tor's build process now includes a "check-includes" make target to
7852 verify that no module of Tor relies on any headers from a higher-
7853 level module. We hope to use this feature over time to help
7854 refactor our codebase. Closes ticket 26447.
7856 o Minor features (code layout):
7857 - We have a new "lowest-level" error-handling API for use by code
7858 invoked from within the logging module. With this interface, the
7859 logging code is no longer at risk of calling into itself if a
7860 failure occurs while it is trying to log something. Closes
7863 o Minor features (compilation):
7864 - Tor's configure script now supports a --with-malloc= option to
7865 select your malloc implementation. Supported options are
7866 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
7867 default). Addresses part of ticket 20424. Based on a patch from
7870 o Minor features (config):
7871 - The "auto" keyword in torrc is now case-insensitive. Closes
7874 o Minor features (continuous integration):
7875 - Don't do a distcheck with --disable-module-dirauth in Travis.
7876 Implements ticket 27252.
7877 - Install libcap-dev and libseccomp2-dev so these optional
7878 dependencies get tested on Travis CI. Closes ticket 26560.
7879 - Only run one online rust build in Travis, to reduce network
7880 errors. Skip offline rust builds on Travis for Linux gcc, because
7881 they're redundant. Implements ticket 27252.
7882 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
7883 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
7884 Linux with default settings, because all the non-default builds
7885 use gcc on Linux. Implements ticket 27252.
7887 o Minor features (controller):
7888 - Emit CIRC_BW events as soon as we detect that we processed an
7889 invalid or otherwise dropped cell on a circuit. This allows
7890 vanguards and other controllers to react more quickly to dropped
7891 cells. Closes ticket 27678.
7892 - For purposes of CIRC_BW-based dropped cell detection, track half-
7893 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
7894 bias check cells to arrive without counting it as dropped until
7895 either the END arrives, or the windows are empty. Closes
7897 - Implement a 'GETINFO md/all' controller command to enable getting
7898 all known microdescriptors. Closes ticket 8323.
7899 - The GETINFO command now support an "uptime" argument, to return
7900 Tor's uptime in seconds. Closes ticket 25132.
7902 o Minor features (denial-of-service avoidance):
7903 - Make our OOM handler aware of the DNS cache so that it doesn't
7904 fill up the memory. This check is important for our DoS mitigation
7905 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
7907 o Minor features (development):
7908 - Tor's makefile now supports running the "clippy" Rust style tool
7909 on our Rust code. Closes ticket 22156.
7911 o Minor features (directory authority):
7912 - There is no longer an artificial upper limit on the length of
7913 bandwidth lines. Closes ticket 26223.
7914 - When a bandwidth file is used to obtain the bandwidth measurements,
7915 include this bandwidth file headers in the votes. Closes
7917 - Improved support for networks with only a single authority or a
7918 single fallback directory. Patch from Gabriel Somlo. Closes
7921 o Minor features (embedding API):
7922 - The Tor controller API now supports a function to launch Tor with
7923 a preconstructed owning controller FD, so that embedding
7924 applications don't need to manage controller ports and
7925 authentication. Closes ticket 24204.
7926 - The Tor controller API now has a function that returns the name
7927 and version of the backend implementing the API. Closes
7930 o Minor features (geoip):
7931 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
7932 Country database. Closes ticket 27631.
7934 o Minor features (memory management):
7935 - Get Libevent to use the same memory allocator as Tor, by calling
7936 event_set_mem_functions() during initialization. Resolves
7939 o Minor features (memory usage):
7940 - When not using them, store legacy TAP public onion keys in DER-
7941 encoded format, rather than as expanded public keys. This should
7942 save several megabytes on typical clients. Closes ticket 27246.
7944 o Minor features (OpenSSL):
7945 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
7946 than our own. Resolves ticket 19979.
7948 o Minor features (Rust, code quality):
7949 - Improve rust code quality in the rust protover implementation by
7950 making it more idiomatic. Includes changing an internal API to
7951 take &str instead of &String. Closes ticket 26492.
7953 o Minor features (testing):
7954 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
7955 chutney. Implements ticket 27211.
7957 o Minor features (tor-resolve):
7958 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
7959 Side-effect of the refactoring for ticket 26526.
7961 o Minor features (UI):
7962 - Log each included configuration file or directory as we read it,
7963 to provide more visibility about where Tor is reading from. Patch
7964 from Unto Sten; closes ticket 27186.
7965 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
7966 Closes ticket 26703.
7968 o Minor bugfixes (bootstrap):
7969 - Try harder to get descriptors in non-exit test networks, by using
7970 the mid weight for the third hop when there are no exits. Fixes
7971 bug 27237; bugfix on 0.2.6.2-alpha.
7973 o Minor bugfixes (C correctness):
7974 - Avoid casting smartlist index to int implicitly, as it may trigger
7975 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
7976 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
7977 - Use time_t for all values in
7978 predicted_ports_prediction_time_remaining(). Rework the code that
7979 computes difference between durations/timestamps. Fixes bug 27165;
7980 bugfix on 0.3.1.1-alpha.
7982 o Minor bugfixes (client, memory usage):
7983 - When not running as a directory cache, there is no need to store
7984 the text of the current consensus networkstatus in RAM.
7985 Previously, however, clients would store it anyway, at a cost of
7986 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
7989 o Minor bugfixes (client, reachableaddresses):
7990 - Instead of adding a "reject *:*" line to ReachableAddresses when
7991 loading the configuration, add one to the policy after parsing it
7992 in parse_reachable_addresses(). This prevents extra "reject *.*"
7993 lines from accumulating on reloads. Fixes bug 20874; bugfix on
7994 0.1.1.5-alpha. Patch by Neel Chauhan.
7996 o Minor bugfixes (code quality):
7997 - Rename sandbox_getaddrinfo() and other functions to no longer
7998 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
7999 bugfix on 0.2.7.1-alpha.
8001 o Minor bugfixes (configuration, Onion Services):
8002 - In rend_service_parse_port_config(), disallow any input to remain
8003 after address-port pair was parsed. This will catch address and
8004 port being whitespace-separated by mistake of the user. Fixes bug
8005 27044; bugfix on 0.2.9.10.
8007 o Minor bugfixes (continuous integration):
8008 - Stop reinstalling identical packages in our Windows CI. Fixes bug
8009 27464; bugfix on 0.3.4.1-alpha.
8011 o Minor bugfixes (controller):
8012 - Consider all routerinfo errors other than "not a server" to be
8013 transient for the purpose of "GETINFO exit-policy/*" controller
8014 request. Print stacktrace in the unlikely case of failing to
8015 recompute routerinfo digest. Fixes bug 27034; bugfix
8018 o Minor bugfixes (directory connection shutdown):
8019 - Avoid a double-close when shutting down a stalled directory
8020 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
8022 o Minor bugfixes (HTTP tunnel):
8023 - Fix a bug warning when closing an HTTP tunnel connection due to an
8024 HTTP request we couldn't handle. Fixes bug 26470; bugfix
8027 o Minor bugfixes (ipv6):
8028 - In addrs_in_same_network_family(), we choose the subnet size based
8029 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
8030 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
8031 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
8033 o Minor bugfixes (logging):
8034 - As a precaution, do an early return from log_addr_has_changed() if
8035 Tor is running as client. Also, log a stack trace for debugging as
8036 this function should only be called when Tor runs as server. Fixes
8037 bug 26892; bugfix on 0.1.1.9-alpha.
8038 - Refrain from mentioning bug 21018 in the logs, as it is already
8039 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
8041 o Minor bugfixes (logging, documentation):
8042 - When SafeLogging is enabled, scrub IP address in
8043 channel_tls_process_netinfo_cell(). Also, add a note to manpage
8044 that scrubbing is not guaranteed on loglevels below Notice. Fixes
8045 bug 26882; bugfix on 0.2.4.10-alpha.
8047 o Minor bugfixes (netflow padding):
8048 - Ensure circuitmux queues are empty before scheduling or sending
8049 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
8051 o Minor bugfixes (onion service v2):
8052 - Log at level "info", not "warning", in the case that we do not
8053 have a consensus when a .onion request comes in. This can happen
8054 normally while bootstrapping. Fixes bug 27040; bugfix
8057 o Minor bugfixes (onion service v3):
8058 - When the onion service directory can't be created or has the wrong
8059 permissions, do not log a stack trace. Fixes bug 27335; bugfix
8062 o Minor bugfixes (OS compatibility):
8063 - Properly handle configuration changes that move a listener to/from
8064 wildcard IP address. If the first attempt to bind a socket fails,
8065 close the old listener and try binding the socket again. Fixes bug
8066 17873; bugfix on 0.0.8pre-1.
8068 o Minor bugfixes (performance)::
8069 - Rework node_is_a_configured_bridge() to no longer call
8070 node_get_all_orports(), which was performing too many memory
8071 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
8073 o Minor bugfixes (relay statistics):
8074 - Update relay descriptor on bandwidth changes only when the uptime
8075 is smaller than 24h, in order to reduce the efficiency of guard
8076 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
8078 o Minor bugfixes (relays):
8079 - Consider the fact that we'll be making direct connections to our
8080 entry and guard nodes when computing the fraction of nodes that
8081 have their descriptors. Also, if we are using bridges and there is
8082 at least one bridge with a full descriptor, treat the fraction of
8083 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
8084 Patch by Neel Chauhan.
8085 - Update the message logged on relays when DirCache is disabled.
8086 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
8087 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
8089 o Minor bugfixes (rust, protover):
8090 - Compute protover votes correctly in the rust version of the
8091 protover code. Previously, the protover rewrite in 24031 allowed
8092 repeated votes from the same voter for the same protocol version
8093 to be counted multiple times in protover_compute_vote(). Fixes bug
8094 27649; bugfix on 0.3.3.5-rc.
8095 - Reject protover names that contain invalid characters. Fixes bug
8096 27687; bugfix on 0.3.3.1-alpha.
8098 o Minor bugfixes (testing):
8099 - Fix two unit tests to work when HOME environment variable is not
8100 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
8101 - If a unit test running in a subprocess exits abnormally or with a
8102 nonzero status code, treat the test as having failed, even if the
8103 test reported success. Without this fix, memory leaks don't cause
8104 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
8105 bugfix on 0.2.2.4-alpha.
8106 - When logging a version mismatch in our openssl_version tests,
8107 report the actual offending version strings. Fixes bug 26152;
8108 bugfix on 0.2.9.1-alpha.
8109 - Fix forking tests on Windows when there is a space somewhere in
8110 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
8112 o Code simplification and refactoring:
8113 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
8114 longer needed. Closes ticket 26502.
8115 - Include paths to header files within Tor are now qualified by
8116 directory within the top-level src directory.
8117 - Many structures have been removed from the centralized "or.h"
8118 header, and moved into their own headers. This will allow us to
8119 reduce the number of places in the code that rely on each
8120 structure's contents and layout. Closes ticket 26383.
8121 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
8122 - Remove GetAdaptersAddresses_fn_t. The code that used it was
8123 removed as part of the 26481 refactor. Closes ticket 27467.
8124 - Rework Tor SOCKS server code to use Trunnel and benefit from
8125 autogenerated functions for parsing and generating SOCKS wire
8126 format. New implementation is cleaner, more maintainable and
8127 should be less prone to heartbleed-style vulnerabilities.
8128 Implements a significant fraction of ticket 3569.
8129 - Split sampled_guards_update_from_consensus() and
8130 select_entry_guard_for_circuit() into subfunctions. In
8131 entry_guards_update_primary() unite three smartlist enumerations
8132 into one and move smartlist comparison code out of the function.
8133 Closes ticket 21349.
8134 - Tor now assumes that you have standards-conformant stdint.h and
8135 inttypes.h headers when compiling. Closes ticket 26626.
8136 - Unify our bloom filter logic. Previously we had two copies of this
8137 code: one for routerlist filtering, and one for address set
8138 calculations. Closes ticket 26510.
8139 - Use the simpler strcmpstart() helper in
8140 rend_parse_v2_service_descriptor instead of strncmp(). Closes
8142 - Utility functions that can perform a DNS lookup are now wholly
8143 separated from those that can't, in separate headers and C
8144 modules. Closes ticket 26526.
8147 - Copy paragraph and URL to Tor's code of conduct document from
8148 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
8149 - Remove old instructions from INSTALL document. Closes ticket 26588.
8150 - Warn users that they should not include MyFamily line(s) in their
8151 torrc when running Tor bridge. Closes ticket 26908.
8154 - Tor no longer supports building with the dmalloc library. For
8155 debugging memory issues, we suggest using gperftools or msan
8156 instead. Closes ticket 26426.
8157 - Tor no longer attempts to run on Windows environments without the
8158 GetAdaptersAddresses() function. This function has existed since
8159 Windows XP, which is itself already older than we support.
8160 - Remove Tor2web functionality for version 2 onion services. The
8161 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
8162 (This feature was never shipped in vanilla Tor and it was only
8163 possible to use this feature by building the support at compile
8164 time. Tor2webMode is not implemented for version 3 onion services.)
8165 Closes ticket 26367.
8168 Changes in version 0.2.9.17 - 2018-09-10
8169 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
8171 o Minor features (compatibility, backport from 0.3.4.8):
8172 - Tell OpenSSL to maintain backward compatibility with previous
8173 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
8174 ciphers are disabled by default. Closes ticket 27344.
8176 o Minor features (continuous integration, backport from 0.3.4.7-rc):
8177 - Enable macOS builds in our Travis CI configuration. Closes
8179 - Install libcap-dev and libseccomp2-dev so these optional
8180 dependencies get tested on Travis CI. Closes ticket 26560.
8181 - Run asciidoc during Travis CI. Implements ticket 27087.
8182 - Use ccache in our Travis CI configuration. Closes ticket 26952.
8184 o Minor features (geoip):
8185 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
8186 Country database. Closes ticket 27089.
8188 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
8189 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
8190 tell the compiler not to include the system malloc implementation.
8191 Fixes bug 20424; bugfix on 0.2.0.20-rc.
8193 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
8194 - Silence a spurious compiler warning on the GetAdaptersAddresses
8195 function pointer cast. This issue is already fixed by 26481 in
8196 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
8197 bugfix on 0.2.3.11-alpha.
8198 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
8199 supported, and always fails. Some compilers warn about the
8200 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
8203 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
8204 - Don't link or search for pthreads when building for Windows, even
8205 if we are using build environment (like mingw) that provides a
8206 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
8208 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
8209 - Skip a pair of unreliable key generation tests on Windows, until
8210 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
8211 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
8213 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
8214 - Pass the module flags to distcheck configure, and log the flags
8215 before running configure. (Backported to 0.2.9 and later as a
8216 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
8218 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
8219 - When a Travis build fails, and showing a log fails, keep trying to
8220 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
8221 - When we use echo in Travis, don't pass a --flag as the first
8222 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
8224 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
8225 - When voting for recommended versions, make sure that all of the
8226 versions are well-formed and parsable. Fixes bug 26485; bugfix
8229 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
8230 - Fix a bug in out sandboxing rules for the openat() syscall.
8231 Previously, no openat() call would be permitted, which would break
8232 filesystem operations on recent glibc versions. Fixes bug 25440;
8233 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
8235 o Minor bugfixes (onion services, backport from 0.3.4.8):
8236 - Silence a spurious compiler warning in
8237 rend_client_send_introduction(). Fixes bug 27463; bugfix
8240 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
8241 - Log a protocol warning when single onion services or Tor2web clients
8242 fail to authenticate direct connections to relays.
8243 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
8245 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
8246 - Disable core dumps in test_bt.sh, to avoid failures in "make
8247 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
8249 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
8250 - Before running make test-network-all, delete old logs and test
8251 result files, to avoid spurious failures. Fixes bug 27295; bugfix
8254 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
8255 - Our "tortls/cert_matches_key" unit test no longer relies on
8256 OpenSSL internals. Previously, it relied on unsupported OpenSSL
8257 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
8258 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
8260 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
8261 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
8262 27185; bugfix on 0.2.2.2-alpha.
8265 Changes in version 0.3.2.12 - 2018-09-10
8266 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
8268 o Minor features (compatibility, backport from 0.3.4.8):
8269 - Tell OpenSSL to maintain backward compatibility with previous
8270 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
8271 ciphers are disabled by default. Closes ticket 27344.
8273 o Minor features (continuous integration, backport from 0.3.4.7-rc):
8274 - Enable macOS builds in our Travis CI configuration. Closes
8276 - Install libcap-dev and libseccomp2-dev so these optional
8277 dependencies get tested on Travis CI. Closes ticket 26560.
8278 - Run asciidoc during Travis CI. Implements ticket 27087.
8279 - Use ccache in our Travis CI configuration. Closes ticket 26952.
8281 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
8282 - Use cargo cache in our Travis CI configuration. Closes
8285 o Minor features (controller, backport from 0.3.4.6-rc):
8286 - The control port now exposes the list of HTTPTunnelPorts and
8287 ExtOrPorts via GETINFO net/listeners/httptunnel and
8288 net/listeners/extor respectively. Closes ticket 26647.
8290 o Minor features (directory authorities, backport from 0.3.4.7-rc):
8291 - Authorities no longer vote to make the subprotocol version
8292 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
8293 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
8295 o Minor features (geoip):
8296 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
8297 Country database. Closes ticket 27089.
8299 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
8300 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
8301 tell the compiler not to include the system malloc implementation.
8302 Fixes bug 20424; bugfix on 0.2.0.20-rc.
8303 - Don't try to use a pragma to temporarily disable the
8304 -Wunused-const-variable warning if the compiler doesn't support
8305 it. Fixes bug 26785; bugfix on 0.3.2.11.
8307 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
8308 - Silence a spurious compiler warning on the GetAdaptersAddresses
8309 function pointer cast. This issue is already fixed by 26481 in
8310 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
8311 bugfix on 0.2.3.11-alpha.
8312 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
8313 supported, and always fails. Some compilers warn about the
8314 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
8317 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
8318 - Don't link or search for pthreads when building for Windows, even
8319 if we are using build environment (like mingw) that provides a
8320 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
8322 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
8323 - Skip a pair of unreliable key generation tests on Windows, until
8324 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
8325 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
8327 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
8328 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
8329 - Pass the module flags to distcheck configure, and log the flags
8330 before running configure. (Backported to 0.2.9 and later as a
8331 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
8333 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
8334 - When a Travis build fails, and showing a log fails, keep trying to
8335 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
8336 - When we use echo in Travis, don't pass a --flag as the first
8337 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
8339 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
8340 - When voting for recommended versions, make sure that all of the
8341 versions are well-formed and parsable. Fixes bug 26485; bugfix
8344 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
8345 - Fix a bug in out sandboxing rules for the openat() syscall.
8346 Previously, no openat() call would be permitted, which would break
8347 filesystem operations on recent glibc versions. Fixes bug 25440;
8348 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
8350 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
8351 - Improve the log message when connection initiators fail to
8352 authenticate direct connections to relays. Fixes bug 26927; bugfix
8355 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
8356 - Fix bug that causes services to not ever rotate their descriptors
8357 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
8360 o Minor bugfixes (onion services, backport from 0.3.4.8):
8361 - Silence a spurious compiler warning in
8362 rend_client_send_introduction(). Fixes bug 27463; bugfix
8365 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
8366 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
8368 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
8369 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
8370 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
8371 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
8373 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
8374 - Log a protocol warning when single onion services or Tor2web clients
8375 fail to authenticate direct connections to relays.
8376 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
8378 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
8379 - Disable core dumps in test_bt.sh, to avoid failures in "make
8380 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
8382 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
8383 - When running make test-network-all, use the mixed+hs-v2 network.
8384 (A previous fix to chutney removed v3 onion services from the
8385 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
8386 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
8387 - Before running make test-network-all, delete old logs and test
8388 result files, to avoid spurious failures. Fixes bug 27295; bugfix
8391 o Minor bugfixes (testing, openssl compatibility):
8392 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
8393 internals. Previously, it relied on unsupported OpenSSL behavior in
8394 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
8395 bugfix on 0.2.5.1-alpha.
8397 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
8398 - Our "tortls/cert_matches_key" unit test no longer relies on
8399 OpenSSL internals. Previously, it relied on unsupported OpenSSL
8400 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
8401 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
8403 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
8404 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
8405 27185; bugfix on 0.2.2.2-alpha.
8408 Changes in version 0.3.3.10 - 2018-09-10
8409 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
8411 o Minor features (bug workaround, backport from 0.3.4.7-rc):
8412 - Compile correctly on systems that provide the C11 stdatomic.h
8413 header, but where C11 atomic functions don't actually compile.
8414 Closes ticket 26779; workaround for Debian issue 903709.
8416 o Minor features (compatibility, backport from 0.3.4.8):
8417 - Tell OpenSSL to maintain backward compatibility with previous
8418 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
8419 ciphers are disabled by default. Closes ticket 27344.
8421 o Minor features (continuous integration, backport from 0.3.4.7-rc):
8422 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
8423 - Enable macOS builds in our Travis CI configuration. Closes
8425 - Install libcap-dev and libseccomp2-dev so these optional
8426 dependencies get tested on Travis CI. Closes ticket 26560.
8427 - Run asciidoc during Travis CI. Implements ticket 27087.
8428 - Use ccache in our Travis CI configuration. Closes ticket 26952.
8430 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
8431 - Use cargo cache in our Travis CI configuration. Closes
8434 o Minor features (controller, backport from 0.3.4.6-rc):
8435 - The control port now exposes the list of HTTPTunnelPorts and
8436 ExtOrPorts via GETINFO net/listeners/httptunnel and
8437 net/listeners/extor respectively. Closes ticket 26647.
8439 o Minor features (directory authorities, backport from 0.3.4.7-rc):
8440 - Authorities no longer vote to make the subprotocol version
8441 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
8442 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
8444 o Minor features (geoip):
8445 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
8446 Country database. Closes ticket 27089.
8448 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
8449 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
8450 tell the compiler not to include the system malloc implementation.
8451 Fixes bug 20424; bugfix on 0.2.0.20-rc.
8452 - Don't try to use a pragma to temporarily disable the
8453 -Wunused-const-variable warning if the compiler doesn't support
8454 it. Fixes bug 26785; bugfix on 0.3.2.11.
8456 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
8457 - Silence a spurious compiler warning on the GetAdaptersAddresses
8458 function pointer cast. This issue is already fixed by 26481 in
8459 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
8460 bugfix on 0.2.3.11-alpha.
8461 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
8462 supported, and always fails. Some compilers warn about the
8463 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
8466 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
8467 - Don't link or search for pthreads when building for Windows, even
8468 if we are using build environment (like mingw) that provides a
8469 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
8471 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
8472 - Skip a pair of unreliable key generation tests on Windows, until
8473 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
8474 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
8476 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
8477 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
8478 - Pass the module flags to distcheck configure, and log the flags
8479 before running configure. (Backported to 0.2.9 and later as a
8480 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
8482 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
8483 - When a Travis build fails, and showing a log fails, keep trying to
8484 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
8485 - When we use echo in Travis, don't pass a --flag as the first
8486 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
8488 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
8489 - When voting for recommended versions, make sure that all of the
8490 versions are well-formed and parsable. Fixes bug 26485; bugfix
8493 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
8494 - Always call tor_free_all() when leaving tor_run_main(). When we
8495 did not, restarting tor in-process would cause an assertion
8496 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
8498 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
8499 - Fix a bug in our sandboxing rules for the openat() syscall.
8500 Previously, no openat() call would be permitted, which would break
8501 filesystem operations on recent glibc versions. Fixes bug 25440;
8502 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
8504 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
8505 - Improve the log message when connection initiators fail to
8506 authenticate direct connections to relays. Fixes bug 26927; bugfix
8509 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
8510 - Fix bug that causes services to not ever rotate their descriptors
8511 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
8514 o Minor bugfixes (onion services, backport from 0.3.4.8):
8515 - Silence a spurious compiler warning in
8516 rend_client_send_introduction(). Fixes bug 27463; bugfix
8519 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
8520 - Work around two different bugs in the OS X 10.10 and later SDKs
8521 that would prevent us from successfully targeting earlier versions
8522 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
8524 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
8525 - Fix compilation of the unit tests on GNU/Hurd, which does not
8526 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
8529 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
8530 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
8532 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
8533 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
8534 - Protover parsing was accepting the presence of whitespace in
8535 version strings, which the C implementation would choke on, e.g.
8536 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
8537 - Protover parsing was ignoring a 2nd hyphen and everything after
8538 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
8540 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
8541 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
8542 - cd to ${abs_top_builddir}/src/rust before running cargo in
8543 src/test/test_rust.sh. This makes the working directory consistent
8544 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
8546 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
8547 - Log a protocol warning when single onion services or Tor2web clients
8548 fail to authenticate direct connections to relays.
8549 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
8551 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
8552 - Disable core dumps in test_bt.sh, to avoid failures in "make
8553 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
8555 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
8556 - When running make test-network-all, use the mixed+hs-v2 network.
8557 (A previous fix to chutney removed v3 onion services from the
8558 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
8559 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
8560 - Before running make test-network-all, delete old logs and test
8561 result files, to avoid spurious failures. Fixes bug 27295; bugfix
8564 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
8565 - Our "tortls/cert_matches_key" unit test no longer relies on
8566 OpenSSL internals. Previously, it relied on unsupported OpenSSL
8567 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
8568 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
8570 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
8571 - Stop sending ed25519 link specifiers in v3 onion service introduce
8572 cells and descriptors, when the rendezvous or introduction point
8573 doesn't support ed25519 link authentication. Fixes bug 26627;
8574 bugfix on 0.3.2.4-alpha.
8576 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
8577 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
8578 27185; bugfix on 0.2.2.2-alpha.
8581 Changes in version 0.3.4.8 - 2018-09-10
8582 Tor 0.3.4.8 is the first stable release in its series; it includes
8583 compilation and portability fixes.
8585 The Tor 0.3.4 series includes improvements for running Tor in
8586 low-power and embedded environments, which should help performance in
8587 general. We've begun work on better modularity, and included preliminary
8588 changes on the directory authority side to accommodate a new bandwidth
8589 measurement system. We've also integrated more continuous-integration
8590 systems into our development process, and made corresponding changes to
8591 Tor's testing infrastructure. Finally, we've continued to refine
8592 our anti-denial-of-service code.
8594 Below are the changes since 0.3.4.7-rc. For a complete list of changes
8595 since 0.3.3.9, see the ReleaseNotes file.
8597 o Minor features (compatibility):
8598 - Tell OpenSSL to maintain backward compatibility with previous
8599 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
8600 ciphers are disabled by default. Closes ticket 27344.
8602 o Minor features (continuous integration):
8603 - Log the compiler path and version during Appveyor builds.
8604 Implements ticket 27449.
8605 - Show config.log and test-suite.log after failed Appveyor builds.
8606 Also upload the zipped full logs as a build artifact. Implements
8609 o Minor bugfixes (compilation):
8610 - Silence a spurious compiler warning on the GetAdaptersAddresses
8611 function pointer cast. This issue is already fixed by 26481 in
8612 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
8613 bugfix on 0.2.3.11-alpha.
8614 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
8615 supported, and always fails. Some compilers warn about the
8616 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
8619 o Minor bugfixes (continuous integration):
8620 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
8621 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
8622 Executables compiled for 64-bit Windows with this version of gcc
8623 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
8624 27460; bugfix on 0.3.4.1-alpha.
8625 - When a Travis build fails, and showing a log fails, keep trying to
8626 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
8627 - When we use echo in Travis, don't pass a --flag as the first
8628 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
8630 o Minor bugfixes (onion services):
8631 - Silence a spurious compiler warning in
8632 rend_client_send_introduction(). Fixes bug 27463; bugfix
8635 o Minor bugfixes (testing, chutney):
8636 - When running make test-network-all, use the mixed+hs-v2 network.
8637 (A previous fix to chutney removed v3 onion services from the
8638 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
8639 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
8640 - Before running make test-network-all, delete old logs and test
8641 result files, to avoid spurious failures. Fixes bug 27295; bugfix
8644 Changes in version 0.3.4.7-rc - 2018-08-24
8645 Tor 0.3.4.7-rc fixes several small compilation, portability, and
8646 correctness issues in previous versions of Tor. This version is a
8647 release candidate: if no serious bugs are found, we expect that the
8648 stable 0.3.4 release will be (almost) the same as this release.
8650 o Minor features (bug workaround):
8651 - Compile correctly on systems that provide the C11 stdatomic.h
8652 header, but where C11 atomic functions don't actually compile.
8653 Closes ticket 26779; workaround for Debian issue 903709.
8655 o Minor features (continuous integration):
8656 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
8657 - Enable macOS builds in our Travis CI configuration. Closes
8659 - Install libcap-dev and libseccomp2-dev so these optional
8660 dependencies get tested on Travis CI. Closes ticket 26560.
8661 - Only post Appveyor IRC notifications when the build fails.
8662 Implements ticket 27275.
8663 - Run asciidoc during Travis CI. Implements ticket 27087.
8664 - Use ccache in our Travis CI configuration. Closes ticket 26952.
8666 o Minor features (continuous integration, rust):
8667 - Use cargo cache in our Travis CI configuration. Closes
8670 o Minor features (directory authorities):
8671 - Authorities no longer vote to make the subprotocol version
8672 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
8673 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
8675 o Minor features (geoip):
8676 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
8677 Country database. Closes ticket 27089.
8679 o Minor bugfixes (compilation, windows):
8680 - Don't link or search for pthreads when building for Windows, even
8681 if we are using build environment (like mingw) that provides a
8682 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
8684 o Minor bugfixes (continuous integration):
8685 - Improve Appveyor CI IRC logging. Generate correct branches and
8686 URLs for pull requests and tags. Use unambiguous short commits.
8687 Fixes bug 26979; bugfix on master.
8688 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
8689 - Pass the module flags to distcheck configure, and log the flags
8690 before running configure. (Backported to 0.2.9 and later as a
8691 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
8693 o Minor bugfixes (in-process restart):
8694 - Always call tor_free_all() when leaving tor_run_main(). When we
8695 did not, restarting tor in-process would cause an assertion
8696 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
8698 o Minor bugfixes (linux seccomp2 sandbox):
8699 - Fix a bug in out sandboxing rules for the openat() syscall.
8700 Previously, no openat() call would be permitted, which would break
8701 filesystem operations on recent glibc versions. Fixes bug 25440;
8702 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
8704 o Minor bugfixes (onion services):
8705 - Fix bug that causes services to not ever rotate their descriptors
8706 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
8709 o Minor bugfixes (portability):
8710 - Fix compilation of the unit tests on GNU/Hurd, which does not
8711 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
8714 o Minor bugfixes (rust):
8715 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
8717 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
8718 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
8719 - Protover parsing was accepting the presence of whitespace in
8720 version strings, which the C implementation would choke on, e.g.
8721 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
8722 - Protover parsing was ignoring a 2nd hyphen and everything after
8723 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
8725 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
8726 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
8727 - cd to ${abs_top_builddir}/src/rust before running cargo in
8728 src/test/test_rust.sh. This makes the working directory consistent
8729 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
8731 o Minor bugfixes (testing, bootstrap):
8732 - When calculating bootstrap progress, check exit policies and the
8733 exit flag. Previously, Tor would only check the exit flag, which
8734 caused race conditions in small and fast networks like chutney.
8735 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
8737 o Minor bugfixes (testing, openssl compatibility):
8738 - Our "tortls/cert_matches_key" unit test no longer relies on
8739 OpenSSL internals. Previously, it relied on unsupported OpenSSL
8740 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
8741 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
8743 o Minor bugfixes (Windows, compilation):
8744 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
8745 27185; bugfix on 0.2.2.2-alpha.
8748 Changes in version 0.3.4.6-rc - 2018-08-06
8749 Tor 0.3.4.6-rc fixes several small compilation, portability, and
8750 correctness issues in previous versions of Tor. This version is a
8751 release candidate: if no serious bugs are found, we expect that the
8752 stable 0.3.4 release will be (almost) the same as this release.
8754 o Major bugfixes (event scheduler):
8755 - When we enable a periodic event, schedule it in the event loop
8756 rather than running it immediately. Previously, we would re-run
8757 periodic events immediately in the middle of (for example)
8758 changing our options, with unpredictable effects. Fixes bug 27003;
8759 bugfix on 0.3.4.1-alpha.
8761 o Minor features (compilation):
8762 - When building Tor, prefer to use Python 3 over Python 2, and more
8763 recent (contemplated) versions over older ones. Closes
8765 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
8766 tell the compiler not to include the system malloc implementation.
8767 Fixes bug 20424; bugfix on 0.2.0.20-rc.
8768 - Don't try to use a pragma to temporarily disable the
8769 -Wunused-const-variable warning if the compiler doesn't support
8770 it. Fixes bug 26785; bugfix on 0.3.2.11.
8772 o Minor bugfixes (continuous integration):
8773 - Skip a pair of unreliable key generation tests on Windows, until
8774 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
8775 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
8777 o Minor features (controller):
8778 - The control port now exposes the list of HTTPTunnelPorts and
8779 ExtOrPorts via GETINFO net/listeners/httptunnel and
8780 net/listeners/extor respectively. Closes ticket 26647.
8782 o Minor bugfixes (directory authority):
8783 - When voting for recommended versions, make sure that all of the
8784 versions are well-formed and parsable. Fixes bug 26485; bugfix
8787 o Minor features (geoip):
8788 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
8789 Country database. Closes ticket 26674.
8791 o Minor features (Rust, portability):
8792 - Rust cross-compilation is now supported. Closes ticket 25895.
8794 o Minor bugfixes (compilation):
8795 - Update build system so that tor builds again with --disable-unittests
8796 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
8797 - Fix a compilation warning on some versions of GCC when building
8798 code that calls routerinfo_get_my_routerinfo() twice, assuming
8799 that the second call will succeed if the first one did. Fixes bug
8800 26269; bugfix on 0.2.8.2-alpha.
8802 o Minor bugfixes (controller):
8803 - Report the port correctly when a port is configured to bind to
8804 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
8805 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
8806 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
8807 on 0.3.3.1-alpha. Patch by "akwizgran".
8809 o Minor bugfixes (correctness, flow control):
8810 - Upon receiving a stream-level SENDME cell, verify that our window
8811 has not grown too large. Fixes bug 26214; bugfix on svn
8814 o Minor bugfixes (memory, correctness):
8815 - Fix a number of small memory leaks identified by coverity. Fixes
8816 bug 26467; bugfix on numerous Tor versions.
8818 o Minor bugfixes (logging):
8819 - Improve the log message when connection initiators fail to
8820 authenticate direct connections to relays. Fixes bug 26927; bugfix
8823 o Minor bugfixes (portability):
8824 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
8825 26994; bugfix on 0.3.4.1-alpha.
8826 - Work around two different bugs in the OS X 10.10 and later SDKs
8827 that would prevent us from successfully targeting earlier versions
8828 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
8830 o Minor bugfixes (single onion services, Tor2web):
8831 - Log a protocol warning when single onion services or Tor2web
8832 clients fail to authenticate direct connections to relays. Fixes
8833 bug 26924; bugfix on 0.2.9.1-alpha.
8835 o Minor bugfixes (testing):
8836 - Disable core dumps in test_bt.sh, to avoid failures in "make
8837 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
8839 o Minor bugfixes (testing, compatibility):
8840 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
8841 only to pass strings (rather than "bytes" objects) to the Python
8842 subprocess module. Python 3 on Windows seems to require this.
8843 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
8844 0.3.1.1-alpha (for hs_ntor_ref.py).
8846 o Minor bugfixes (v3 onion services):
8847 - Stop sending ed25519 link specifiers in v3 onion service introduce
8848 cells and descriptors, when the rendezvous or introduction point
8849 doesn't support ed25519 link authentication. Fixes bug 26627;
8850 bugfix on 0.3.2.4-alpha.
8853 Changes in version 0.3.4.5-rc - 2018-07-13
8854 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
8855 bridge relays should upgrade.
8857 o Directory authority changes:
8858 - The "Bifroest" bridge authority has been retired; the new bridge
8859 authority is "Serge", and it is operated by George from the
8860 TorBSD project. Closes ticket 26771.
8863 Changes in version 0.3.3.9 - 2018-07-13
8864 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
8865 bridge relays should upgrade.
8867 o Directory authority changes:
8868 - The "Bifroest" bridge authority has been retired; the new bridge
8869 authority is "Serge", and it is operated by George from the
8870 TorBSD project. Closes ticket 26771.
8873 Changes in version 0.3.2.11 - 2018-07-13
8874 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
8875 bridge relays should upgrade. We also take this opportunity to backport
8878 o Directory authority changes:
8879 - The "Bifroest" bridge authority has been retired; the new bridge
8880 authority is "Serge", and it is operated by George from the
8881 TorBSD project. Closes ticket 26771.
8883 o Directory authority changes (backport from 0.3.3.7):
8884 - Add an IPv6 address for the "dannenberg" directory authority.
8885 Closes ticket 26343.
8887 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
8888 - When directory authorities read a zero-byte bandwidth file, they
8889 would previously log a warning with the contents of an
8890 uninitialised buffer. They now log a warning about the empty file
8891 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
8893 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
8894 - Correctly detect when onion services get disabled after HUP. Fixes
8895 bug 25761; bugfix on 0.3.2.1.
8897 o Minor features (sandbox, backport from 0.3.3.4-alpha):
8898 - Explicitly permit the poll() system call when the Linux
8899 seccomp2-based sandbox is enabled: apparently, some versions of
8900 libc use poll() when calling getpwnam(). Closes ticket 25313.
8902 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
8903 - Update the Travis CI configuration to use the stable Rust channel,
8904 now that we have decided to require that. Closes ticket 25714.
8906 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
8907 - Our .travis.yml configuration now includes support for testing the
8908 results of "make distcheck". (It's not uncommon for "make check"
8909 to pass but "make distcheck" to fail.) Closes ticket 25814.
8910 - Our Travis CI configuration now integrates with the Coveralls
8911 coverage analysis tool. Closes ticket 25818.
8913 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
8914 - Add several checks to detect whether Tor relays are uploading
8915 their descriptors without specifying why they regenerated them.
8916 Diagnostic for ticket 25686.
8918 o Minor features (compilation, backport from 0.3.4.4-rc):
8919 - When building Tor, prefer to use Python 3 over Python 2, and more
8920 recent (contemplated) versions over older ones. Closes
8923 o Minor features (geoip):
8924 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
8925 Country database. Closes ticket 26674.
8927 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
8928 - Upon receiving a malformed connected cell, stop processing the
8929 cell immediately. Previously we would mark the connection for
8930 close, but continue processing the cell as if the connection were
8931 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
8933 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
8934 - Allow the nanosleep() system call, which glibc uses to implement
8935 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
8937 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
8938 - When running the hs_ntor_ref.py test, make sure only to pass
8939 strings (rather than "bytes" objects) to the Python subprocess
8940 module. Python 3 on Windows seems to require this. Fixes bug
8941 26535; bugfix on 0.3.1.1-alpha.
8942 - When running the ntor_ref.py test, make sure only to pass strings
8943 (rather than "bytes" objects) to the Python subprocess module.
8944 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
8947 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
8948 - Work around a change in OpenSSL 1.1.1 where return values that
8949 would previously indicate "no password" now indicate an empty
8950 password. Without this workaround, Tor instances running with
8951 OpenSSL 1.1.1 would accept descriptors that other Tor instances
8952 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
8954 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
8955 - Document that the PerConnBW{Rate,Burst} options will fall back to
8956 their corresponding consensus parameters only if those parameters
8957 are set. Previously we had claimed that these values would always
8958 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
8960 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
8961 - Fix a compilation warning on some versions of GCC when building
8962 code that calls routerinfo_get_my_routerinfo() twice, assuming
8963 that the second call will succeed if the first one did. Fixes bug
8964 26269; bugfix on 0.2.8.2-alpha.
8966 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
8967 - Don't consider Tor running as a client if the ControlPort is open,
8968 but no actual client ports are open. Fixes bug 26062; bugfix
8971 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
8972 - Prevent a possible out-of-bounds smartlist read in
8973 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
8975 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
8976 - Fix a very unlikely (impossible, we believe) null pointer
8977 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
8978 Coverity; this is CID 1430932.
8980 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
8981 - Fix a memory leak when a v3 onion service is configured and gets a
8982 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
8983 - When parsing the descriptor signature, look for the token plus an
8984 extra white-space at the end. This is more correct but also will
8985 allow us to support new fields that might start with "signature".
8986 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
8988 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
8989 - Relays now correctly block attempts to re-extend to the previous
8990 relay by Ed25519 identity. Previously they would warn in this
8991 case, but not actually reject the attempt. Fixes bug 26158; bugfix
8994 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
8995 - Avoid a crash when running with DirPort set but ORPort turned off.
8996 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
8998 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
8999 - Silence unused-const-variable warnings in zstd.h with some GCC
9000 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
9002 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
9003 - Avoid intermittent test failures due to a test that had relied on
9004 onion service introduction point creation finishing within 5
9005 seconds of real clock time. Fixes bug 25450; bugfix
9008 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
9009 - Fix a C99 compliance issue in our configuration script that caused
9010 compilation issues when compiling Tor with certain versions of
9011 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
9013 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
9014 - Fix a number of small memory leaks identified by coverity. Fixes
9015 bug 26467; bugfix on numerous Tor versions.
9017 o Code simplification and refactoring (backport from 0.3.3.5-rc):
9018 - Move the list of default directory authorities to its own file.
9019 Closes ticket 24854. Patch by "beastr0".
9022 Changes in version 0.2.9.16 - 2018-07-13
9023 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
9024 bridge relays should upgrade. We also take this opportunity to backport
9027 o Directory authority changes:
9028 - The "Bifroest" bridge authority has been retired; the new bridge
9029 authority is "Serge", and it is operated by George from the
9030 TorBSD project. Closes ticket 26771.
9032 o Directory authority changes (backport from 0.3.3.7):
9033 - Add an IPv6 address for the "dannenberg" directory authority.
9034 Closes ticket 26343.
9036 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
9037 - When directory authorities read a zero-byte bandwidth file, they
9038 would previously log a warning with the contents of an
9039 uninitialised buffer. They now log a warning about the empty file
9040 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
9042 o Minor features (sandbox, backport from 0.3.3.4-alpha):
9043 - Explicitly permit the poll() system call when the Linux
9044 seccomp2-based sandbox is enabled: apparently, some versions of
9045 libc use poll() when calling getpwnam(). Closes ticket 25313.
9047 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
9048 - Our .travis.yml configuration now includes support for testing the
9049 results of "make distcheck". (It's not uncommon for "make check"
9050 to pass but "make distcheck" to fail.) Closes ticket 25814.
9051 - Our Travis CI configuration now integrates with the Coveralls
9052 coverage analysis tool. Closes ticket 25818.
9054 o Minor features (compilation, backport from 0.3.4.4-rc):
9055 - When building Tor, prefer to use Python 3 over Python 2, and more
9056 recent (contemplated) versions over older ones. Closes
9059 o Minor features (geoip):
9060 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
9061 Country database. Closes ticket 26674.
9063 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
9064 - Upon receiving a malformed connected cell, stop processing the
9065 cell immediately. Previously we would mark the connection for
9066 close, but continue processing the cell as if the connection were
9067 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
9069 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
9070 - Allow the nanosleep() system call, which glibc uses to implement
9071 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
9073 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
9074 - When running the ntor_ref.py test, make sure only to pass strings
9075 (rather than "bytes" objects) to the Python subprocess module.
9076 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
9079 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
9080 - Work around a change in OpenSSL 1.1.1 where return values that
9081 would previously indicate "no password" now indicate an empty
9082 password. Without this workaround, Tor instances running with
9083 OpenSSL 1.1.1 would accept descriptors that other Tor instances
9084 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
9086 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
9087 - Fix a compilation warning on some versions of GCC when building
9088 code that calls routerinfo_get_my_routerinfo() twice, assuming
9089 that the second call will succeed if the first one did. Fixes bug
9090 26269; bugfix on 0.2.8.2-alpha.
9092 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
9093 - Don't consider Tor running as a client if the ControlPort is open,
9094 but no actual client ports are open. Fixes bug 26062; bugfix
9097 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
9098 - Prevent a possible out-of-bounds smartlist read in
9099 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
9101 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
9102 - Fix a very unlikely (impossible, we believe) null pointer
9103 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
9104 Coverity; this is CID 1430932.
9106 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
9107 - Fix a number of small memory leaks identified by coverity. Fixes
9108 bug 26467; bugfix on numerous Tor versions.
9110 o Code simplification and refactoring (backport from 0.3.3.5-rc):
9111 - Move the list of default directory authorities to its own file.
9112 Closes ticket 24854. Patch by "beastr0".
9115 Changes in version 0.3.4.4-rc - 2018-07-09
9116 Tor 0.3.4.4-rc fixes several small compilation, portability, and
9117 correctness issues in previous versions of Tor. This version is a
9118 release candidate: if no serious bugs are found, we expect that the
9119 stable 0.3.4 release will be (almost) the same as this release.
9121 o Minor features (compilation):
9122 - When building Tor, prefer to use Python 3 over Python 2, and more
9123 recent (contemplated) versions over older ones. Closes
9126 o Minor features (geoip):
9127 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
9128 Country database. Closes ticket 26674.
9130 o Minor features (Rust, portability):
9131 - Rust cross-compilation is now supported. Closes ticket 25895.
9133 o Minor bugfixes (compilation):
9134 - Fix a compilation warning on some versions of GCC when building
9135 code that calls routerinfo_get_my_routerinfo() twice, assuming
9136 that the second call will succeed if the first one did. Fixes bug
9137 26269; bugfix on 0.2.8.2-alpha.
9139 o Minor bugfixes (control port):
9140 - Report the port correctly when a port is configured to bind to
9141 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
9142 - Handle the HSADDRESS= argument to the HSPOST command properly.
9143 (Previously, this argument was misparsed and thus ignored.) Fixes
9144 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
9146 o Minor bugfixes (correctness, flow control):
9147 - Upon receiving a stream-level SENDME cell, verify that our window
9148 has not grown too large. Fixes bug 26214; bugfix on svn
9151 o Minor bugfixes (memory, correctness):
9152 - Fix a number of small memory leaks identified by coverity. Fixes
9153 bug 26467; bugfix on numerous Tor versions.
9155 o Minor bugfixes (testing, compatibility):
9156 - When running the hs_ntor_ref.py test, make sure only to pass
9157 strings (rather than "bytes" objects) to the Python subprocess
9158 module. Python 3 on Windows seems to require this. Fixes bug
9159 26535; bugfix on 0.3.1.1-alpha.
9160 - When running the ntor_ref.py test, make sure only to pass strings
9161 (rather than "bytes" objects) to the Python subprocess module.
9162 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
9166 Changes in version 0.3.3.8 - 2018-07-09
9167 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
9168 fixes for a memory leak affecting directory authorities.
9170 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
9171 - Stop leaking memory on directory authorities when planning to
9172 vote. This bug was crashing authorities by exhausting their
9173 memory. Fixes bug 26435; bugfix on 0.3.3.6.
9175 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
9176 - Make sure that failing tests in Rust will actually cause the build
9177 to fail: previously, they were ignored. Fixes bug 26258; bugfix
9180 o Minor features (compilation, backport from 0.3.4.4-rc):
9181 - When building Tor, prefer to use Python 3 over Python 2, and more
9182 recent (contemplated) versions over older ones. Closes
9185 o Minor features (geoip):
9186 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
9187 Country database. Closes ticket 26674.
9189 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
9190 - Add several checks to detect whether Tor relays are uploading
9191 their descriptors without specifying why they regenerated them.
9192 Diagnostic for ticket 25686.
9194 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
9195 - Don't count path selection failures as circuit build failures.
9196 This change should eliminate cases where Tor blames its guard or
9197 the network for situations like insufficient microdescriptors
9198 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
9201 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
9202 - Fix a compilation warning on some versions of GCC when building
9203 code that calls routerinfo_get_my_routerinfo() twice, assuming
9204 that the second call will succeed if the first one did. Fixes bug
9205 26269; bugfix on 0.2.8.2-alpha.
9207 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
9208 - Handle the HSADDRESS= argument to the HSPOST command properly.
9209 (Previously, this argument was misparsed and thus ignored.) Fixes
9210 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
9212 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
9213 - Fix a number of small memory leaks identified by coverity. Fixes
9214 bug 26467; bugfix on numerous Tor versions.
9216 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
9217 - Relays now correctly block attempts to re-extend to the previous
9218 relay by Ed25519 identity. Previously they would warn in this
9219 case, but not actually reject the attempt. Fixes bug 26158; bugfix
9222 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
9223 - When shutting down, Tor now clears all the flags in the control.c
9224 module. This should prevent a bug where authentication cookies are
9225 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
9227 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
9228 - When running the hs_ntor_ref.py test, make sure only to pass
9229 strings (rather than "bytes" objects) to the Python subprocess
9230 module. Python 3 on Windows seems to require this. Fixes bug
9231 26535; bugfix on 0.3.1.1-alpha.
9232 - When running the ntor_ref.py test, make sure only to pass strings
9233 (rather than "bytes" objects) to the Python subprocess module.
9234 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
9238 Changes in version 0.3.4.3-alpha - 2018-06-26
9239 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
9240 one that was causing stability issues on directory authorities.
9242 o Major bugfixes (directory authority):
9243 - Stop leaking memory on directory authorities when planning to
9244 vote. This bug was crashing authorities by exhausting their
9245 memory. Fixes bug 26435; bugfix on 0.3.3.6.
9247 o Major bugfixes (rust, testing):
9248 - Make sure that failing tests in Rust will actually cause the build
9249 to fail: previously, they were ignored. Fixes bug 26258; bugfix
9252 o Minor feature (directory authorities):
9253 - Stop warning about incomplete bw lines before the first complete
9254 bw line has been found, so that additional header lines can be
9255 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
9257 o Minor features (relay, diagnostic):
9258 - Add several checks to detect whether Tor relays are uploading
9259 their descriptors without specifying why they regenerated them.
9260 Diagnostic for ticket 25686.
9262 o Minor features (unit tests):
9263 - Test complete bandwidth measurements files, and test that
9264 incomplete bandwidth lines only give warnings when the end of the
9265 header has not been detected. Fixes bug 25947; bugfix
9268 o Minor bugfixes (compilation):
9269 - Refrain from compiling unit testing related object files when
9270 --disable-unittests is set to configure script. Fixes bug 24891;
9271 bugfix on 0.2.5.1-alpha.
9272 - When linking the libtor_testing.a library, only include the
9273 dirauth object files once. Previously, they were getting added
9274 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
9275 - The --enable-fatal-warnings flag now affects Rust code as well.
9276 Closes ticket 26245.
9278 o Minor bugfixes (onion services):
9279 - Recompute some consensus information after detecting a clock jump,
9280 or after transitioning from a non-live consensus to a live
9281 consensus. We do this to avoid having an outdated state, and
9282 miscalculating the index for next-generation onion services. Fixes
9283 bug 24977; bugfix on 0.3.2.1-alpha.
9285 o Minor bugfixes (relay):
9286 - Relays now correctly block attempts to re-extend to the previous
9287 relay by Ed25519 identity. Previously they would warn in this
9288 case, but not actually reject the attempt. Fixes bug 26158; bugfix
9291 o Minor bugfixes (testing):
9292 - Fix compilation of the doctests in the Rust crypto crate. Fixes
9293 bug 26415; bugfix on 0.3.4.1-alpha.
9294 - Instead of trying to read the geoip configuration files from
9295 within the unit tests, instead create our own ersatz files with
9296 just enough geoip data in the format we expect. Trying to read
9297 from the source directory created problems on Windows with mingw,
9298 where the build system's paths are not the same as the platform's
9299 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
9300 - Refrain from trying to get an item from an empty smartlist in
9301 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
9302 to catch improper smartlist usage. Furthermore, enable
9303 DEBUG_SMARTLIST globally when build is configured with fragile
9304 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
9307 Changes in version 0.3.3.7 - 2018-06-12
9308 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
9309 fixes for bugs affecting compatibility and stability.
9311 o Directory authority changes:
9312 - Add an IPv6 address for the "dannenberg" directory authority.
9313 Closes ticket 26343.
9315 o Minor features (geoip):
9316 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
9317 Country database. Closes ticket 26351.
9319 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
9320 - Work around a change in OpenSSL 1.1.1 where return values that
9321 would previously indicate "no password" now indicate an empty
9322 password. Without this workaround, Tor instances running with
9323 OpenSSL 1.1.1 would accept descriptors that other Tor instances
9324 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
9326 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
9327 - Silence unused-const-variable warnings in zstd.h with some GCC
9328 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
9330 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
9331 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
9332 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
9333 miscounting the total number of circuits for these field values.)
9334 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
9336 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
9337 - Prevent a possible out-of-bounds smartlist read in
9338 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
9340 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
9341 - Only select relays when they have the descriptors we prefer to use
9342 for them. This change fixes a bug where we could select a relay
9343 because it had _some_ descriptor, but reject it later with a
9344 nonfatal assertion error because it didn't have the exact one we
9345 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
9348 Changes in version 0.3.4.2-alpha - 2018-06-12
9349 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
9350 release, and forward-ports an authority-only security fix from 0.3.3.6.
9352 o Directory authority changes:
9353 - Add an IPv6 address for the "dannenberg" directory authority.
9354 Closes ticket 26343.
9356 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
9357 - Fix a bug that could have allowed an attacker to force a directory
9358 authority to use up all its RAM by passing it a maliciously
9359 crafted protocol versions string. Fixes bug 25517; bugfix on
9360 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
9362 o Minor features (continuous integration):
9363 - Add the necessary configuration files for continuous integration
9364 testing on Windows, via the Appveyor platform. Closes ticket
9365 25549. Patches from Marcin Cieślak and Isis Lovecruft.
9367 o Minor features (geoip):
9368 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
9369 Country database. Closes ticket 26351.
9371 o Minor bugfixes (compatibility, openssl):
9372 - Work around a change in OpenSSL 1.1.1 where return values that
9373 would previously indicate "no password" now indicate an empty
9374 password. Without this workaround, Tor instances running with
9375 OpenSSL 1.1.1 would accept descriptors that other Tor instances
9376 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
9378 o Minor bugfixes (compilation):
9379 - Silence unused-const-variable warnings in zstd.h with some GCC
9380 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
9381 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
9382 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
9383 - Avoid a compiler warning when casting the return value of
9384 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
9385 26283; bugfix on 0.2.4.10-alpha.
9387 o Minor bugfixes (control port):
9388 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
9389 CIRC_BW events. Previously, such cells were counted entirely in
9390 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
9393 o Minor bugfixes (controller):
9394 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
9395 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
9396 miscounting the total number of circuits for these field values.)
9397 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
9399 o Minor bugfixes (hardening):
9400 - Prevent a possible out-of-bounds smartlist read in
9401 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
9403 o Minor bugfixes (onion services):
9404 - Fix a bug that blocked the creation of ephemeral v3 onion
9405 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
9407 o Minor bugfixes (test coverage tools):
9408 - Update our "cov-diff" script to handle output from the latest
9409 version of gcov, and to remove extraneous timestamp information
9410 from its output. Fixes bugs 26101 and 26102; bugfix
9414 Changes in version 0.3.3.6 - 2018-05-22
9415 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
9416 backports several important fixes from the 0.3.4.1-alpha.
9418 The Tor 0.3.3 series includes controller support and other
9419 improvements for v3 onion services, official support for embedding Tor
9420 within other applications, and our first non-trivial module written in
9421 the Rust programming language. (Rust is still not enabled by default
9422 when building Tor.) And as usual, there are numerous other smaller
9423 bugfixes, features, and improvements.
9425 Below are the changes since 0.3.3.5-rc. For a list of all changes
9426 since 0.3.2.10, see the ReleaseNotes file.
9428 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
9429 - When directory authorities read a zero-byte bandwidth file, they
9430 would previously log a warning with the contents of an
9431 uninitialised buffer. They now log a warning about the empty file
9432 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
9434 o Major bugfixes (security, directory authority, denial-of-service):
9435 - Fix a bug that could have allowed an attacker to force a directory
9436 authority to use up all its RAM by passing it a maliciously
9437 crafted protocol versions string. Fixes bug 25517; bugfix on
9438 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
9440 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
9441 - Avoid a rare assertion failure in the circuit build timeout code
9442 if we fail to allow any circuits to actually complete. Fixes bug
9443 25733; bugfix on 0.2.2.2-alpha.
9445 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
9446 - Avoid a crash when testing router reachability on a router that
9447 could have an ed25519 ID, but which does not. Fixes bug 25415;
9448 bugfix on 0.3.3.2-alpha.
9450 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
9451 - Correctly detect when onion services get disabled after HUP. Fixes
9452 bug 25761; bugfix on 0.3.2.1.
9454 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
9455 - Impose a limit on circuit cell queue size. The limit can be
9456 controlled by a consensus parameter. Fixes bug 25226; bugfix
9459 o Minor features (compatibility, backport from 0.3.4.1-alpha):
9460 - Avoid some compilation warnings with recent versions of LibreSSL.
9461 Closes ticket 26006.
9463 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
9464 - Our .travis.yml configuration now includes support for testing the
9465 results of "make distcheck". (It's not uncommon for "make check"
9466 to pass but "make distcheck" to fail.) Closes ticket 25814.
9467 - Our Travis CI configuration now integrates with the Coveralls
9468 coverage analysis tool. Closes ticket 25818.
9470 o Minor features (geoip):
9471 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
9472 database. Closes ticket 26104.
9474 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
9475 - Don't consider Tor running as a client if the ControlPort is open,
9476 but no actual client ports are open. Fixes bug 26062; bugfix
9479 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
9480 - Upon receiving a malformed connected cell, stop processing the
9481 cell immediately. Previously we would mark the connection for
9482 close, but continue processing the cell as if the connection were
9483 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
9485 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
9486 - Stop saying in the manual that clients cache ipv4 dns answers from
9487 exit relays. We haven't used them since 0.2.6.3-alpha, and in
9488 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
9489 we forgot to say so in the man page. Fixes bug 26052; bugfix
9492 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
9493 - Allow the nanosleep() system call, which glibc uses to implement
9494 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
9496 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
9497 - Fix a memory leak when a v3 onion service is configured and gets a
9498 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
9499 - When parsing the descriptor signature, look for the token plus an
9500 extra white-space at the end. This is more correct but also will
9501 allow us to support new fields that might start with "signature".
9502 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
9504 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
9505 - Avoid a crash when running with DirPort set but ORPort turned off.
9506 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
9508 o Documentation (backport from 0.3.4.1-alpha):
9509 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
9510 ticket 25857. Patch from "CTassisF".
9513 Changes in version 0.3.4.1-alpha - 2018-05-17
9514 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
9515 includes refactoring to begin reducing Tor's binary size and idle CPU
9516 usage on mobile, along with prep work for new bandwidth scanners,
9517 improvements to the experimental "vanguards" feature, and numerous
9518 other small features and bugfixes.
9520 o New system requirements:
9521 - Tor no longer tries to support old operating systems without
9522 mmap() or some local equivalent. Apparently, compilation on such
9523 systems has been broken for some time, without anybody noticing or
9524 complaining. Closes ticket 25398.
9526 o Major feature (directory authority, modularization):
9527 - The directory authority subsystem has been modularized. The code
9528 is now located in src/or/dirauth/, and is compiled in by default.
9529 To disable the module, the configure option
9530 --disable-module-dirauth has been added. This module may be
9531 disabled by default in some future release. Closes ticket 25610.
9533 o Major features (main loop, CPU usage):
9534 - When Tor is disabled (via DisableNetwork or via hibernation), it
9535 no longer needs to run any per-second events. This change should
9536 make it easier for mobile applications to disable Tor while the
9537 device is sleeping, or Tor is not running. Closes ticket 26063.
9538 - Tor no longer enables all of its periodic events by default.
9539 Previously, Tor would enable all possible main loop events,
9540 regardless of whether it needed them. Furthermore, many of these
9541 events are now disabled with Tor is hibernating or DisableNetwork
9542 is set. This is a big step towards reducing client CPU usage by
9543 reducing the amount of wake-ups the daemon does. Closes ticket
9545 - The bandwidth-limitation logic has been refactored so that
9546 bandwidth calculations are performed on-demand, rather than every
9547 TokenBucketRefillInterval milliseconds. This change should improve
9548 the granularity of our bandwidth calculations, and limit the
9549 number of times that the Tor process needs to wake up when it is
9550 idle. Closes ticket 25373.
9551 - Move responsibility for many operations from a once-per-second
9552 callback to a callback that is only scheduled as needed. Moving
9553 this functionality has allowed us to disable the callback when
9554 Tor's network is disabled. Once enough items are removed from our
9555 once-per-second callback, we can eliminate it entirely to conserve
9556 CPU when idle. The functionality removed includes: closing
9557 connections, circuits, and channels (ticket 25932); consensus
9558 voting (25937); flushing log callbacks (25951); honoring delayed
9559 SIGNEWNYM requests (25949); rescanning the consensus cache
9560 (25931); saving the state file to disk (25948); warning relay
9561 operators about unreachable ports (25952); and keeping track of
9562 Tor's uptime (26009).
9564 o Major bugfixes (directory authorities, security):
9565 - When directory authorities read a zero-byte bandwidth file, they
9566 would previously log a warning with the contents of an
9567 uninitialised buffer. They now log a warning about the empty file
9568 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
9570 o Major bugfixes (crash):
9571 - Avoid a rare assertion failure in the circuit build timeout code
9572 if we fail to allow any circuits to actually complete. Fixes bug
9573 25733; bugfix on 0.2.2.2-alpha.
9575 o Major bugfixes (directory authority):
9576 - Avoid a crash when testing router reachability on a router that
9577 could have an ed25519 ID, but which does not. Fixes bug 25415;
9578 bugfix on 0.3.3.2-alpha.
9580 o Major bugfixes (onion service):
9581 - Correctly detect when onion services get disabled after HUP. Fixes
9582 bug 25761; bugfix on 0.3.2.1.
9584 o Major bugfixes (protover, voting):
9585 - Revise Rust implementation of protover to use a more memory-
9586 efficient voting algorithm and corresponding data structures, thus
9587 avoiding a potential (but small impact) DoS attack where specially
9588 crafted protocol strings would expand to several potential
9589 megabytes in memory. In the process, several portions of code were
9590 revised to be methods on new, custom types, rather than functions
9591 taking interchangeable types, thus increasing type safety of the
9592 module. Custom error types and handling were added as well, in
9593 order to facilitate better error dismissal/handling in outside
9594 crates and avoid mistakenly passing an internal error string to C
9595 over the FFI boundary. Many tests were added, and some previous
9596 differences between the C and Rust implementations have been
9597 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
9599 o Major bugfixes (relay, denial of service):
9600 - Impose a limit on circuit cell queue size. The limit can be
9601 controlled by a consensus parameter. Fixes bug 25226; bugfix
9604 o Minor features (accounting):
9605 - When Tor becomes dormant, it now uses a scheduled event to wake up
9606 at the right time. Previously, we would use the per-second timer
9607 to check whether to wake up, but we no longer have any per-second
9608 timers enabled when the network is disabled. Closes ticket 26064.
9610 o Minor features (code quality):
9611 - Add optional spell-checking for the Tor codebase, using the
9612 "misspell" program. To use this feature, run "make check-typos".
9613 Closes ticket 25024.
9615 o Minor features (compatibility):
9616 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
9617 the no-deprecated option, and builds correctly with them. Closes
9618 tickets 19429, 19981, and 25353.
9619 - Avoid some compilation warnings with recent versions of LibreSSL.
9620 Closes ticket 26006.
9622 o Minor features (compression, zstd):
9623 - When running with zstd, Tor now considers using advanced functions
9624 that the zstd maintainers have labeled as potentially unstable. To
9625 prevent breakage, Tor will only use this functionality when the
9626 runtime version of the zstd library matches the version with which
9627 Tor was compiled. Closes ticket 25162.
9629 o Minor features (configuration):
9630 - The "DownloadSchedule" options have been renamed to end with
9631 "DownloadInitialDelay". The old names are still allowed, but will
9632 produce a warning. Comma-separated lists are still permitted for
9633 these options, but all values after the first are ignored (as they
9634 have been since 0.2.9). Closes ticket 23354.
9636 o Minor features (continuous integration):
9637 - Our .travis.yml configuration now includes support for testing the
9638 results of "make distcheck". (It's not uncommon for "make check"
9639 to pass but "make distcheck" to fail.) Closes ticket 25814.
9640 - Our Travis CI configuration now integrates with the Coveralls
9641 coverage analysis tool. Closes ticket 25818.
9643 o Minor features (control port):
9644 - Introduce GETINFO "current-time/{local,utc}" to return the local
9645 and UTC times respectively in ISO format. This helps a controller
9646 like Tor Browser detect a time-related error. Closes ticket 25511.
9647 Patch by Neel Chauhan.
9648 - Introduce new fields to the CIRC_BW event. There are two new
9649 fields in each of the read and written directions. The DELIVERED
9650 fields report the total valid data on the circuit, as measured by
9651 the payload sizes of verified and error-checked relay command
9652 cells. The OVERHEAD fields report the total unused bytes in each
9653 of these cells. Closes ticket 25903.
9655 o Minor features (directory authority):
9656 - Directory authorities now open their key-pinning files as O_SYNC,
9657 to limit their chances of accidentally writing partial lines.
9658 Closes ticket 23909.
9660 o Minor features (directory authority, forward compatibility):
9661 - Make the lines of the measured bandwidth file able to contain
9662 their entries in any order. Previously, the node_id entry needed
9663 to come first. Closes ticket 26004.
9665 o Minor features (entry guards):
9666 - Introduce a new torrc option NumPrimaryGuards for controlling the
9667 number of primary guards. Closes ticket 25843.
9669 o Minor features (geoip):
9670 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
9671 database. Closes ticket 26104.
9673 o Minor features (performance):
9674 - Avoid a needless call to malloc() when processing an incoming
9675 relay cell. Closes ticket 24914.
9676 - Make our timing-wheel code run a tiny bit faster on 32-bit
9677 platforms, by preferring 32-bit math to 64-bit. Closes
9679 - Avoid a needless malloc()/free() pair every time we handle an ntor
9680 handshake. Closes ticket 25150.
9682 o Minor features (testing):
9683 - Add a unit test for voting_schedule_get_start_of_next_interval().
9684 Closes ticket 26014, and helps make unit test coverage
9686 - A new unittests module specifically for testing the functions in
9687 the (new-ish) bridges.c module has been created with new
9688 unittests, raising the code coverage percentages. Closes 25425.
9689 - We now have improved testing for addressmap_get_virtual_address()
9690 function. This should improve our test coverage, and make our test
9691 coverage more deterministic. Closes ticket 25993.
9693 o Minor features (timekeeping, circuit scheduling):
9694 - When keeping track of how busy each circuit have been recently on
9695 a given connection, use coarse-grained monotonic timers rather
9696 than gettimeofday(). This change should marginally increase
9697 accuracy and performance. Implements part of ticket 25927.
9699 o Minor bugfixes (bandwidth management):
9700 - Consider ourselves "low on write bandwidth" if we have exhausted
9701 our write bandwidth some time in the last second. This was the
9702 documented behavior before, but the actual behavior was to change
9703 this value every TokenBucketRefillInterval. Fixes bug 25828;
9704 bugfix on 0.2.3.5-alpha.
9706 o Minor bugfixes (C correctness):
9707 - Add a missing lock acquisition in the shutdown code of the control
9708 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
9709 Coverity; this is CID 1433643.
9711 o Minor bugfixes (circuit path selection):
9712 - Don't count path selection failures as circuit build failures.
9713 This change should eliminate cases where Tor blames its guard or
9714 the network for situations like insufficient microdescriptors
9715 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
9718 o Minor bugfixes (client):
9719 - Don't consider Tor running as a client if the ControlPort is open,
9720 but no actual client ports are open. Fixes bug 26062; bugfix
9723 o Minor bugfixes (code style):
9724 - Fixed multiple includes of transports.h in src/or/connection.c
9725 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
9726 - Remove the unused variable n_possible from the function
9727 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
9729 o Minor bugfixes (control interface):
9730 - Respond with more human-readable error messages to GETINFO exit-
9731 policy/* requests. Also, let controller know if an error is
9732 transient (response code 551) or not (response code 552). Fixes
9733 bug 25852; bugfix on 0.2.8.1-alpha.
9735 o Minor bugfixes (controller):
9736 - Make CIRC_BW event reflect the total of all data sent on a
9737 circuit, including padding and dropped cells. Also fix a mis-
9738 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
9739 bugfix on 0.2.5.2-alpha.
9741 o Minor bugfixes (correctness, client):
9742 - Upon receiving a malformed connected cell, stop processing the cell
9743 immediately. Previously we would mark the connection for close, but
9744 continue processing the cell as if the connection were open. Fixes bug
9745 26072; bugfix on 0.2.4.7-alpha.
9747 o Minor bugfixes (directory client):
9748 - When unverified-consensus is verified, rename it to cached-
9749 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
9750 - Fixed launching a certificate fetch always during the scheduled
9751 periodic consensus fetch by fetching only in those cases when
9752 consensus are waiting for certs. Fixes bug 24740; bugfix
9755 o Minor bugfixes (documentation):
9756 - Stop saying in the manual that clients cache ipv4 dns answers from
9757 exit relays. We haven't used them since 0.2.6.3-alpha, and in
9758 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
9759 we forgot to say so in the man page. Fixes bug 26052; bugfix
9762 o Minor bugfixes (error reporting):
9763 - Improve tolerance for directory authorities with skewed clocks.
9764 Previously, an authority with a clock more than 60 seconds ahead
9765 could cause a client with a correct clock to warn that the
9766 client's clock was behind. Now the clocks of a majority of
9767 directory authorities have to be ahead of the client before this
9768 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
9770 o Minor bugfixes (Linux seccomp2 sandbox):
9771 - Allow the nanosleep() system call, which glibc uses to implement
9772 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
9774 o Minor bugfixes (onion service):
9775 - Fix a memory leak when a v3 onion service is configured and gets a
9776 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
9777 - When parsing the descriptor signature, look for the token plus an
9778 extra white-space at the end. This is more correct but also will
9779 allow us to support new fields that might start with "signature".
9780 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
9782 o Minor bugfixes (path selection):
9783 - Only select relays when they have the descriptors we prefer to use
9784 for them. This change fixes a bug where we could select a relay
9785 because it had _some_ descriptor, but reject it later with a
9786 nonfatal assertion error because it didn't have the exact one we
9787 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
9789 o Minor bugfixes (portability):
9790 - Do not align mmap length, as it is not required by POSIX, and the
9791 getpagesize function is deprecated. Fixes bug 25399; bugfix
9794 o Minor bugfixes (portability, FreeBSD):
9795 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
9796 does not stringify on FreeBSD, so we switch to tor_asprintf().
9797 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
9799 o Minor bugfixes (relay statistics):
9800 - When a relay is collecting internal statistics about how many
9801 create cell requests it has seen of each type, accurately count
9802 the requests from relays that temporarily fall out of the
9803 consensus. (To be extra conservative, we were already ignoring
9804 requests from clients in our counts, and we continue ignoring them
9805 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
9807 o Minor bugfixes (relay, crash):
9808 - Avoid a crash when running with DirPort set but ORPort turned off.
9809 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
9811 o Minor bugfixes (restart-in-process):
9812 - When shutting down, Tor now clears all the flags in the control.c
9813 module. This should prevent a bug where authentication cookies are
9814 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
9816 o Minor bugfixes (testing):
9817 - When testing workqueue event-cancellation, make sure that we
9818 actually cancel an event, and that cancel each event with equal
9819 probability. (It was previously possible, though extremely
9820 unlikely, for our event-canceling test not to cancel any events.)
9821 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
9822 - Repeat part of the test in test_client_pick_intro() a number of
9823 times, to give it consistent coverage. Fixes bug 25996; bugfix
9825 - Remove randomness from the hs_common/responsible_hsdirs test, so
9826 that it always takes the same path through the function it tests.
9827 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
9828 - Change the behavior of the "channel/outbound" test so that it
9829 never causes a 10-second rollover for the EWMA circuitmux code.
9830 Previously, this behavior would happen randomly, and result in
9831 fluctuating test coverage. Fixes bug 25994; bugfix
9833 - Use X509_new() to allocate certificates that will be freed later
9834 with X509_free(). Previously, some parts of the unit tests had
9835 used tor_malloc_zero(), which is incorrect, and which caused test
9836 failures on Windows when they were built with extra hardening.
9837 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
9839 - While running the circuit_timeout test, fix the PRNG to a
9840 deterministic AES stream, so that the test coverage from this test
9841 will itself be deterministic. Fixes bug 25995; bugfix
9844 o Minor bugfixes (vanguards):
9845 - Allow the last hop in a vanguard circuit to be the same as our
9846 first, to prevent the adversary from influencing guard node choice
9847 by choice of last hop. Also prevent the creation of A - B - A
9848 paths, or A - A paths, which are forbidden by relays. Fixes bug
9849 25870; bugfix on 0.3.3.1-alpha.
9851 o Code simplification and refactoring:
9852 - Remove duplicate code in parse_{c,s}method_line and bootstrap
9853 their functionalities into a single function. Fixes bug 6236;
9854 bugfix on 0.2.3.6-alpha.
9855 - We remove the PortForwarding and PortForwardingHelper options,
9856 related functions, and the port_forwarding tests. These options
9857 were used by the now-deprecated Vidalia to help ordinary users
9858 become Tor relays or bridges. Closes ticket 25409. Patch by
9860 - In order to make the OR and dir checking function in router.c less
9861 confusing we renamed some functions and
9862 consider_testing_reachability() has been split into
9863 router_should_check_reachability() and
9864 router_do_reachability_checks(). Also we improved the documentation
9865 in some functions. Closes ticket 18918.
9866 - Initial work to isolate Libevent usage to a handful of modules in
9867 our codebase, to simplify our call structure, and so that we can
9868 more easily change event loops in the future if needed. Closes
9870 - Introduce a function to call getsockname() and return tor_addr_t,
9871 to save a little complexity throughout the codebase. Closes
9873 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
9874 as hsdir_index is always present. Also, we move hsdir_index_t into
9875 or.h. Closes ticket 23094. Patch by Neel Chauhan.
9876 - Merge functions used for describing nodes and suppress the
9877 functions that do not allocate memory for the output buffer
9878 string. NODE_DESC_BUF_LEN constant and format_node_description()
9879 function cannot be used externally from router.c module anymore.
9880 Closes ticket 25432. Patch by valentecaio.
9881 - Our main loop has been simplified so that all important operations
9882 happen inside events. Previously, some operations had to happen
9883 outside the event loop, to prevent infinite sequences of event
9884 activations. Closes ticket 25374.
9885 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
9886 it in register_intro_circ() and service_intro_point_new(). This
9887 prevents the digest from being re-calculated each time. Closes
9888 ticket 23107. Patch by Neel Chauhan.
9889 - Refactor token-bucket implementations to use a common backend.
9890 Closes ticket 25766.
9891 - Remove extern declaration of stats_n_seconds_working variable from
9892 main, protecting its accesses with get_uptime() and reset_uptime()
9893 functions. Closes ticket 25081, patch by “valentecaio”.
9894 - Remove our previous logic for "cached gettimeofday()" -- our
9895 coarse monotonic timers are fast enough for this purpose, and far
9896 less error-prone. Implements part of ticket 25927.
9897 - Remove the return value for fascist_firewall_choose_address_base(),
9898 and sister functions such as fascist_firewall_choose_address_node()
9899 and fascist_firewall_choose_address_rs(). Also, while we're here,
9900 initialize the ap argument as leaving it uninitialized can pose a
9901 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
9902 - Rename two fields of connection_t struct. timestamp_lastwritten is
9903 renamed to timestamp_last_write_allowed and timestamp_lastread is
9904 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
9906 - Since Tor requires C99, remove our old workaround code for libc
9907 implementations where free(NULL) doesn't work. Closes ticket 24484.
9908 - Use our standard rate-limiting code to deal with excessive
9909 libevent failures, rather than the hand-rolled logic we had
9910 before. Closes ticket 26016.
9911 - We remove the return value of node_get_prim_orport() and
9912 node_get_prim_dirport(), and introduce node_get_prim_orport() in
9913 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
9914 check for a null address. Closes ticket 23873. Patch by
9916 - We switch to should_record_bridge_info() in
9917 geoip_note_client_seen() and options_need_geoip_info() instead of
9918 accessing the configuration values directly. Fixes bug 25290;
9919 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
9921 o Deprecated features:
9922 - As we are not recommending 0.2.5 anymore, we require relays that
9923 once had an ed25519 key associated with their RSA key to always
9924 have that key, instead of allowing them to drop back to a version
9925 that didn't support ed25519. This means they need to use a new RSA
9926 key if they want to downgrade to an older version of tor without
9927 ed25519. Closes ticket 20522.
9930 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
9931 ticket 25857. Patch from "CTassisF".
9934 - Directory authorities will no longer support voting according to
9935 any consensus method before consensus method 25. This keeps
9936 authorities compatible with all authorities running 0.2.9.8 and
9937 later, and does not break any clients or relays. Implements ticket
9938 24378 and proposal 290.
9939 - The PortForwarding and PortForwardingHelper features have been
9940 removed. The reasoning is, given that implementations of NAT
9941 traversal protocols within common consumer grade routers are
9942 frequently buggy, and that the target audience for a NAT punching
9943 feature is a perhaps less-technically-inclined relay operator,
9944 when the helper fails to setup traversal the problems are usually
9945 deep, ugly, and very router specific, making them horrendously
9946 impossible for technical support to reliable assist with, and thus
9947 resulting in frustration all around. Unfortunately, relay
9948 operators who would like to run relays behind NATs will need to
9949 become more familiar with the port forwarding configurations on
9950 their local router. Closes 25409.
9951 - The TestingEnableTbEmptyEvent option has been removed. It was used
9952 in testing simulations to measure how often connection buckets
9953 were emptied, in order to improve our scheduling, but it has not
9954 been actively used in years. Closes ticket 25760.
9955 - The old "round-robin" circuit multiplexer (circuitmux)
9956 implementation has been removed, along with a fairly large set of
9957 code that existed to support it. It has not been the default
9958 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
9959 but it still required an unreasonable amount of memory and CPU.
9960 Closes ticket 25268.
9963 Changes in version 0.3.3.5-rc - 2018-04-15
9964 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
9965 including some that could affect reliability or correctness.
9967 This is the first release candidate in the 0.3.3 series. If we find no
9968 new bugs or regression here, then the first stable 0.3.3 release will
9969 be nearly identical to this one.
9971 o Major bugfixes (security, protover, voting):
9972 - Revise Rust implementation of protover to use a more memory-
9973 efficient voting algorithm and corresponding data structures, thus
9974 avoiding a potential memory-based DoS attack where specially
9975 crafted protocol strings would expand to fill available memory.
9976 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
9978 o Major bugfixes (performance, load balancing):
9979 - Directory authorities no longer vote in favor of the Guard flag
9980 for relays without directory support. Starting in Tor
9981 0.3.0.1-alpha, clients have been avoiding using such relays in the
9982 Guard position, leading to increasingly broken load balancing for
9983 the 5%-or-so of Guards that don't advertise directory support.
9984 Fixes bug 22310; bugfix on 0.3.0.6.
9986 o Minor feature (continuous integration):
9987 - Update the Travis CI configuration to use the stable Rust channel,
9988 now that we have decided to require that. Closes ticket 25714.
9990 o Minor features (config options):
9991 - Change the way the default value for MaxMemInQueues is calculated.
9992 We now use 40% of the hardware RAM if the system has 8 GB RAM or
9993 more. Otherwise we use the former value of 75%. Closes
9996 o Minor features (geoip):
9997 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
9998 Country database. Closes ticket 25718.
10000 o Minor bugfixes (client):
10001 - When using a listed relay as a bridge, and also using
10002 microdescriptors, and considering that relay as a non-bridge in a
10003 circuit, treat its microdescriptor as a valid source of
10004 information about that relay. This change should prevent a non-
10005 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
10007 o Minor bugfixes (controller):
10008 - Restore the correct operation of the RESOLVE command, which had
10009 been broken since we added the ability to enable/disable DNS on
10010 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
10012 o Minor bugfixes (distribution, compilation, rust):
10013 - Build correctly when the rust dependencies submodule is loaded,
10014 but the TOR_RUST_DEPENDENCIES environment variable is not set.
10015 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
10016 - Actually include all of our Rust source in our source
10017 distributions. (Previously, a few of the files were accidentally
10018 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
10020 o Minor bugfixes (documentation):
10021 - Document that the PerConnBW{Rate,Burst} options will fall back to
10022 their corresponding consensus parameters only if those parameters
10023 are set. Previously we had claimed that these values would always
10024 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
10025 - Revert a misformatting issue in the ExitPolicy documentation.
10026 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
10028 o Minor bugfixes (exit relay DNS retries):
10029 - Re-attempt timed-out DNS queries 3 times before failure, since our
10030 timeout is 5 seconds for them, but clients wait 10-15. Also allow
10031 slightly more timeouts per resolver when an exit has multiple
10032 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
10034 o Minor bugfixes (onion services):
10035 - Re-instate counting the client HSDir fetch circuits against the
10036 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
10038 - Remove underscores from the _HSLayer{2,3}Nodes options. This
10039 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
10040 Fixes bug 25581; bugfix on 0.3.3.1-alpha
10042 o Code simplification and refactoring:
10043 - Move the list of default directory authorities to its own file.
10044 Closes ticket 24854. Patch by "beastr0".
10046 o Documentation (manpage, denial of service):
10047 - Provide more detail about the denial-of-service options, by
10048 listing each mitigation and explaining how they relate. Closes
10052 Changes in version 0.3.3.4-alpha - 2018-03-29
10053 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
10054 the alpha testing of earlier releases in its series. We are
10055 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
10057 o New system requirements:
10058 - When built with Rust, Tor now depends on version 0.2.39 of the
10059 libc crate. Closes tickets 25310 and 25664.
10061 o Major bugfixes (relay, connection):
10062 - If we have failed to connect to a relay and received a connection
10063 refused, timeout, or similar error (at the TCP level), do not try
10064 that same address/port again for 60 seconds after the failure has
10065 occurred. Fixes bug 24767; bugfix on 0.0.6.
10067 o Minor features (geoip):
10068 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
10069 Country database. Closes ticket 25469.
10071 o Minor features (log messages):
10072 - Improve log message in the out-of-memory handler to include
10073 information about memory usage from the different compression
10074 backends. Closes ticket 25372.
10076 o Minor features (sandbox):
10077 - Explicitly permit the poll() system call when the Linux
10078 seccomp2-based sandbox is enabled: apparently, some versions of
10079 libc use poll() when calling getpwnam(). Closes ticket 25313.
10081 o Minor bugfixes (C correctness):
10082 - Fix a very unlikely (impossible, we believe) null pointer
10083 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
10084 Coverity; this is CID 1430932.
10086 o Minor bugfixes (channel, client):
10087 - Better identify client connection when reporting to the geoip
10088 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
10090 o Minor bugfixes (compilation):
10091 - Fix a C99 compliance issue in our configuration script that caused
10092 compilation issues when compiling Tor with certain versions of
10093 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
10095 o Minor bugfixes (controller, reliability):
10096 - Avoid a (nonfatal) assertion failure when extending a one-hop
10097 circuit from the controller to become a multihop circuit. Fixes
10098 bug 24903; bugfix on 0.2.5.2-alpha.
10100 o Major bugfixes (networking):
10101 - Tor will no longer reject IPv6 address strings from Tor Browser
10102 when they are passed as hostnames in SOCKS5 requests. Fixes bug
10103 25036, bugfix on Tor 0.3.1.2.
10105 o Minor bugfixes (networking):
10106 - string_is_valid_hostname() will not consider IP strings to be
10107 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
10109 o Minor bugfixes (onion service v3):
10110 - Avoid an assertion failure when the next onion service
10111 descriptor rotation type is out of sync with the consensus's
10112 valid-after time. Instead, log a warning message with extra
10113 information, so we can better hunt down the cause of this
10114 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
10116 o Minor bugfixes (testing):
10117 - Avoid intermittent test failures due to a test that had relied on
10118 onion service introduction point creation finishing within 5
10119 seconds of real clock time. Fixes bug 25450; bugfix
10121 - Rust crates are now automatically detected and tested. Previously,
10122 some crates were not tested by `make test-rust` due to a static
10123 string in the `src/test/test_rust.sh` script specifying which
10124 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
10126 o Minor bugfixes (testing, benchmarks):
10127 - Fix a crash when running benchmark tests on win32 systems. The
10128 crash was due to a mutex that wasn't initialized before logging
10129 and options were initialized. Fixes bug 25479; bugfix
10132 o Minor bugfixes (warnings, ipv6):
10133 - Avoid a bug warning that could occur when trying to connect to a
10134 relay over IPv6. This warning would occur on a Tor instance that
10135 downloads router descriptors, but prefers to use microdescriptors.
10136 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
10138 o Code simplification and refactoring:
10139 - Remove the old (deterministic) directory retry logic entirely:
10140 We've used exponential backoff exclusively for some time. Closes
10144 - Improved the documentation of AccountingStart parameter. Closes
10146 - Update the documentation for "Log" to include the current list of
10147 logging domains. Closes ticket 25378.
10150 Changes in version 0.3.1.10 - 2018-03-03
10151 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
10154 It includes an important security fix for a remote crash attack
10155 against directory authorities, tracked as TROVE-2018-001.
10157 This release also backports our new system for improved resistance to
10158 denial-of-service attacks against relays.
10160 This release also fixes several minor bugs and annoyances from
10163 All directory authorities should upgrade to one of the versions
10164 released today. Relays running 0.3.1.x may wish to update to one of
10165 the versions released today, for the DoS mitigations.
10167 Please note: according to our release calendar, Tor 0.3.1 will no
10168 longer be supported after 1 July 2018. If you will be running Tor
10169 after that date, you should make sure to plan to upgrade to the latest
10170 stable version, or downgrade to 0.2.9 (which will receive long-term
10173 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
10174 - Fix a protocol-list handling bug that could be used to remotely crash
10175 directory authorities with a null-pointer exception. Fixes bug 25074;
10176 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
10179 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
10180 - Give relays some defenses against the recent network overload. We
10181 start with three defenses (default parameters in parentheses).
10182 First: if a single client address makes too many concurrent
10183 connections (>100), hang up on further connections. Second: if a
10184 single client address makes circuits too quickly (more than 3 per
10185 second, with an allowed burst of 90) while also having too many
10186 connections open (3), refuse new create cells for the next while
10187 (1-2 hours). Third: if a client asks to establish a rendezvous
10188 point to you directly, ignore the request. These defenses can be
10189 manually controlled by new torrc options, but relays will also
10190 take guidance from consensus parameters, so there's no need to
10191 configure anything manually. Implements ticket 24902.
10193 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
10194 - Update the sandbox rules so that they should now work correctly
10195 with Glibc 2.26. Closes ticket 24315.
10197 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
10198 - Fix an "off by 2" error in counting rendezvous failures on the
10199 onion service side. While we thought we would stop the rendezvous
10200 attempt after one failed circuit, we were actually making three
10201 circuit attempts before giving up. Now switch to a default of 2,
10202 and allow the consensus parameter "hs_service_max_rdv_failures" to
10203 override. Fixes bug 24895; bugfix on 0.0.6.
10205 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
10206 - Add Link protocol version 5 to the supported protocols list. Fixes
10207 bug 25070; bugfix on 0.3.1.1-alpha.
10209 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
10210 - Fix a set of false positives where relays would consider
10211 connections to other relays as being client-only connections (and
10212 thus e.g. deserving different link padding schemes) if those
10213 relays fell out of the consensus briefly. Now we look only at the
10214 initial handshake and whether the connection authenticated as a
10215 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
10217 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
10218 - Make our OOM handler aware of the geoip client history cache so it
10219 doesn't fill up the memory. This check is important for IPv6 and
10220 our DoS mitigation subsystem. Closes ticket 25122.
10222 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
10223 - Change relay bandwidth reporting stats interval from 4 hours to 24
10224 hours in order to reduce the efficiency of guard discovery
10225 attacks. Fixes ticket 23856.
10227 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
10228 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
10229 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
10230 since they neither disabled TLS 1.3 nor enabled any of the
10231 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
10232 Closes ticket 24978.
10234 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
10235 - The fallback directory list has been re-generated based on the
10236 current status of the network. Tor uses fallback directories to
10237 bootstrap when it doesn't yet have up-to-date directory
10238 information. Closes ticket 24801.
10239 - Make the default DirAuthorityFallbackRate 0.1, so that clients
10240 prefer to bootstrap from fallback directory mirrors. This is a
10241 follow-up to 24679, which removed weights from the default
10242 fallbacks. Implements ticket 24681.
10244 o Minor features (geoip):
10245 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
10248 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
10249 - Use the actual observed address of an incoming relay connection,
10250 not the canonical address of the relay from its descriptor, when
10251 making decisions about how to handle the incoming connection.
10252 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
10254 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
10255 - Directory authorities, when refusing a descriptor from a rejected
10256 relay, now explicitly tell the relay (in its logs) to set a valid
10257 ContactInfo address and contact the bad-relays@ mailing list.
10258 Fixes bug 25170; bugfix on 0.2.9.1.
10260 o Minor bugfixes (address selection, backport from 0.3.2.9):
10261 - When the fascist_firewall_choose_address_ functions don't find a
10262 reachable address, set the returned address to the null address
10263 and port. This is a precautionary measure, because some callers do
10264 not check the return value. Fixes bug 24736; bugfix
10267 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
10268 - Fetch descriptors aggressively whenever we lack enough to build
10269 circuits, regardless of how many descriptors we are missing.
10270 Previously, we would delay launching the fetch when we had fewer
10271 than 15 missing descriptors, even if some of those descriptors
10272 were blocking circuits from building. Fixes bug 23985; bugfix on
10273 0.1.1.11-alpha. The effects of this bug became worse in
10274 0.3.0.3-alpha, when we began treating missing descriptors from our
10275 primary guards as a reason to delay circuits.
10276 - Don't try fetching microdescriptors from relays that have failed
10277 to deliver them in the past. Fixes bug 23817; bugfix
10280 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
10281 - Fix a signed/unsigned comparison warning introduced by our fix to
10282 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
10284 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
10285 - Avoid a crash when attempting to use the seccomp2 sandbox together
10286 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
10289 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
10290 - Fix a possible crash on malformed consensus. If a consensus had
10291 contained an unparseable protocol line, it could have made clients
10292 and relays crash with a null-pointer exception. To exploit this
10293 issue, however, an attacker would need to be able to subvert the
10294 directory authority system. Fixes bug 25251; bugfix on
10295 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
10297 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
10298 - Recover better from empty or corrupt files in the consensus cache
10299 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
10300 - When a consensus diff calculation is only partially successful,
10301 only record the successful parts as having succeeded. Partial
10302 success can happen if (for example) one compression method fails
10303 but the others succeed. Previously we misrecorded all the
10304 calculations as having succeeded, which would later cause a
10305 nonfatal assertion failure. Fixes bug 24086; bugfix
10308 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
10309 - Tor now updates its guard state when it reads a consensus
10310 regardless of whether it's missing descriptors. That makes tor use
10311 its primary guards to fetch descriptors in some edge cases where
10312 it would previously have used fallback directories. Fixes bug
10313 23862; bugfix on 0.3.0.1-alpha.
10315 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
10316 - Don't treat inability to store a cached consensus object as a bug:
10317 it can happen normally when we are out of disk space. Fixes bug
10318 24859; bugfix on 0.3.1.1-alpha.
10320 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
10321 - When queuing DESTROY cells on a channel, only queue the circuit-id
10322 and reason fields: not the entire 514-byte cell. This fix should
10323 help mitigate any bugs or attacks that fill up these queues, and
10324 free more RAM for other uses. Fixes bug 24666; bugfix
10327 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
10328 - When closing a connection via close_connection_immediately(), we
10329 mark it as "not blocked on bandwidth", to prevent later calls from
10330 trying to unblock it, and give it permission to read. This fixes a
10331 backtrace warning that can happen on relays under various
10332 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
10334 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
10335 - When selecting relays by bandwidth, avoid a rounding error that
10336 could sometimes cause load to be imbalanced incorrectly.
10337 Previously, we would always round upwards; now, we round towards
10338 the nearest integer. This had the biggest effect when a relay's
10339 weight adjustments should have given it weight 0, but it got
10340 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
10341 - When calculating the fraction of nodes that have descriptors, and
10342 all nodes in the network have zero bandwidths, count the number of
10343 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
10344 - Actually log the total bandwidth in compute_weighted_bandwidths().
10345 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
10347 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
10348 - Improve the performance of our consensus-diff application code
10349 when Tor is built with the --enable-fragile-hardening option set.
10350 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
10352 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
10353 - Don't exit the Tor process if setrlimit() fails to change the file
10354 limit (which can happen sometimes on some versions of OSX). Fixes
10355 bug 21074; bugfix on 0.0.9pre5.
10357 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
10358 - Fix a bug in the bit-counting parts of our timing-wheel code on
10359 MSVC. (Note that MSVC is still not a supported build platform, due
10360 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
10363 o Minor bugfixes (relay, partial backport):
10364 - Make the internal channel_is_client() function look at what sort
10365 of connection handshake the other side used, rather than whether
10366 the other side ever sent a create_fast cell to us. Backports part
10367 of the fixes from bugs 22805 and 24898.
10369 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
10370 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
10372 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
10373 bugfix on 0.2.9.4-alpha.
10375 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
10376 - Update the "rust dependencies" submodule to be a project-level
10377 repository, rather than a user repository. Closes ticket 25323.
10380 Changes in version 0.2.9.15 - 2018-03-03
10381 Tor 0.2.9.15 backports important security and stability bugfixes from
10382 later Tor releases.
10384 It includes an important security fix for a remote crash attack
10385 against directory authorities, tracked as TROVE-2018-001.
10387 This release also backports our new system for improved resistance to
10388 denial-of-service attacks against relays.
10390 This release also fixes several minor bugs and annoyances from
10393 All directory authorities should upgrade to one of the versions
10394 released today. Relays running 0.2.9.x may wish to update to one of
10395 the versions released today, for the DoS mitigations.
10397 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
10398 - Fix a protocol-list handling bug that could be used to remotely crash
10399 directory authorities with a null-pointer exception. Fixes bug 25074;
10400 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
10403 o Major features (denial-of-service mitigation):
10404 - Give relays some defenses against the recent network overload. We
10405 start with three defenses (default parameters in parentheses).
10406 First: if a single client address makes too many concurrent
10407 connections (>100), hang up on further connections. Second: if a
10408 single client address makes circuits too quickly (more than 3 per
10409 second, with an allowed burst of 90) while also having too many
10410 connections open (3), refuse new create cells for the next while
10411 (1-2 hours). Third: if a client asks to establish a rendezvous
10412 point to you directly, ignore the request. These defenses can be
10413 manually controlled by new torrc options, but relays will also
10414 take guidance from consensus parameters, so there's no need to
10415 configure anything manually. Implements ticket 24902.
10417 o Major bugfixes (bootstrapping):
10418 - Fetch descriptors aggressively whenever we lack enough to build
10419 circuits, regardless of how many descriptors we are missing.
10420 Previously, we would delay launching the fetch when we had fewer
10421 than 15 missing descriptors, even if some of those descriptors
10422 were blocking circuits from building. Fixes bug 23985; bugfix on
10423 0.1.1.11-alpha. The effects of this bug became worse in
10424 0.3.0.3-alpha, when we began treating missing descriptors from our
10425 primary guards as a reason to delay circuits.
10427 o Major bugfixes (onion services, retry behavior):
10428 - Fix an "off by 2" error in counting rendezvous failures on the
10429 onion service side. While we thought we would stop the rendezvous
10430 attempt after one failed circuit, we were actually making three
10431 circuit attempts before giving up. Now switch to a default of 2,
10432 and allow the consensus parameter "hs_service_max_rdv_failures" to
10433 override. Fixes bug 24895; bugfix on 0.0.6.
10435 o Minor feature (relay statistics):
10436 - Change relay bandwidth reporting stats interval from 4 hours to 24
10437 hours in order to reduce the efficiency of guard discovery
10438 attacks. Fixes ticket 23856.
10440 o Minor features (compatibility, OpenSSL):
10441 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
10442 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
10443 since they neither disabled TLS 1.3 nor enabled any of the
10444 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
10445 Closes ticket 24978.
10447 o Minor features (denial-of-service avoidance):
10448 - Make our OOM handler aware of the geoip client history cache so it
10449 doesn't fill up the memory. This check is important for IPv6 and
10450 our DoS mitigation subsystem. Closes ticket 25122.
10452 o Minor features (fallback directory mirrors):
10453 - The fallback directory list has been re-generated based on the
10454 current status of the network. Tor uses fallback directories to
10455 bootstrap when it doesn't yet have up-to-date directory
10456 information. Closes ticket 24801.
10457 - Make the default DirAuthorityFallbackRate 0.1, so that clients
10458 prefer to bootstrap from fallback directory mirrors. This is a
10459 follow-up to 24679, which removed weights from the default
10460 fallbacks. Implements ticket 24681.
10462 o Minor features (geoip):
10463 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
10466 o Minor features (linux seccomp2 sandbox):
10467 - Update the sandbox rules so that they should now work correctly
10468 with Glibc 2.26. Closes ticket 24315.
10470 o Minor bugfix (channel connection):
10471 - Use the actual observed address of an incoming relay connection,
10472 not the canonical address of the relay from its descriptor, when
10473 making decisions about how to handle the incoming connection.
10474 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
10476 o Minor bugfix (directory authority):
10477 - Directory authorities, when refusing a descriptor from a rejected
10478 relay, now explicitly tell the relay (in its logs) to set a valid
10479 ContactInfo address and contact the bad-relays@ mailing list.
10480 Fixes bug 25170; bugfix on 0.2.9.1.
10482 o Minor bugfixes (address selection):
10483 - When the fascist_firewall_choose_address_ functions don't find a
10484 reachable address, set the returned address to the null address
10485 and port. This is a precautionary measure, because some callers do
10486 not check the return value. Fixes bug 24736; bugfix
10489 o Minor bugfixes (compilation):
10490 - Fix a signed/unsigned comparison warning introduced by our fix to
10491 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
10493 o Minor bugfixes (control port, linux seccomp2 sandbox):
10494 - Avoid a crash when attempting to use the seccomp2 sandbox together
10495 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
10498 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
10499 - Fix a possible crash on malformed consensus. If a consensus had
10500 contained an unparseable protocol line, it could have made clients
10501 and relays crash with a null-pointer exception. To exploit this
10502 issue, however, an attacker would need to be able to subvert the
10503 directory authority system. Fixes bug 25251; bugfix on
10504 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
10506 o Minor bugfixes (memory usage):
10507 - When queuing DESTROY cells on a channel, only queue the circuit-id
10508 and reason fields: not the entire 514-byte cell. This fix should
10509 help mitigate any bugs or attacks that fill up these queues, and
10510 free more RAM for other uses. Fixes bug 24666; bugfix
10513 o Minor bugfixes (network layer):
10514 - When closing a connection via close_connection_immediately(), we
10515 mark it as "not blocked on bandwidth", to prevent later calls from
10516 trying to unblock it, and give it permission to read. This fixes a
10517 backtrace warning that can happen on relays under various
10518 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
10520 o Minor bugfixes (OSX):
10521 - Don't exit the Tor process if setrlimit() fails to change the file
10522 limit (which can happen sometimes on some versions of OSX). Fixes
10523 bug 21074; bugfix on 0.0.9pre5.
10525 o Minor bugfixes (path selection):
10526 - When selecting relays by bandwidth, avoid a rounding error that
10527 could sometimes cause load to be imbalanced incorrectly.
10528 Previously, we would always round upwards; now, we round towards
10529 the nearest integer. This had the biggest effect when a relay's
10530 weight adjustments should have given it weight 0, but it got
10531 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
10532 - When calculating the fraction of nodes that have descriptors, and
10533 all nodes in the network have zero bandwidths, count the number of
10534 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
10535 - Actually log the total bandwidth in compute_weighted_bandwidths().
10536 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
10538 o Minor bugfixes (portability, msvc):
10539 - Fix a bug in the bit-counting parts of our timing-wheel code on
10540 MSVC. (Note that MSVC is still not a supported build platform, due
10541 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
10544 o Minor bugfixes (relay):
10545 - Make the internal channel_is_client() function look at what sort
10546 of connection handshake the other side used, rather than whether
10547 the other side ever sent a create_fast cell to us. Backports part
10548 of the fixes from bugs 22805 and 24898.
10550 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
10551 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
10553 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
10554 bugfix on 0.2.9.4-alpha.
10557 Changes in version 0.3.2.10 - 2018-03-03
10558 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
10559 backports a number of bugfixes, including important fixes for security
10562 It includes an important security fix for a remote crash attack
10563 against directory authorities, tracked as TROVE-2018-001.
10565 Additionally, it backports a fix for a bug whose severity we have
10566 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
10567 triggered in order to crash relays with a use-after-free pattern. As
10568 such, we are now tracking that bug as TROVE-2018-002 and
10569 CVE-2018-0491, and backporting it to earlier releases. This bug
10570 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
10573 This release also backports our new system for improved resistance to
10574 denial-of-service attacks against relays.
10576 This release also fixes several minor bugs and annoyances from
10579 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
10580 today, for the fix to TROVE-2018-002. Directory authorities should
10581 also upgrade. (Relays on earlier versions might want to update too for
10582 the DoS mitigations.)
10584 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
10585 - Fix a protocol-list handling bug that could be used to remotely crash
10586 directory authorities with a null-pointer exception. Fixes bug 25074;
10587 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
10590 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
10591 - Avoid adding the same channel twice in the KIST scheduler pending
10592 list, which could lead to remote denial-of-service use-after-free
10593 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
10595 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
10596 - Give relays some defenses against the recent network overload. We
10597 start with three defenses (default parameters in parentheses).
10598 First: if a single client address makes too many concurrent
10599 connections (>100), hang up on further connections. Second: if a
10600 single client address makes circuits too quickly (more than 3 per
10601 second, with an allowed burst of 90) while also having too many
10602 connections open (3), refuse new create cells for the next while
10603 (1-2 hours). Third: if a client asks to establish a rendezvous
10604 point to you directly, ignore the request. These defenses can be
10605 manually controlled by new torrc options, but relays will also
10606 take guidance from consensus parameters, so there's no need to
10607 configure anything manually. Implements ticket 24902.
10609 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
10610 - Fix an "off by 2" error in counting rendezvous failures on the
10611 onion service side. While we thought we would stop the rendezvous
10612 attempt after one failed circuit, we were actually making three
10613 circuit attempts before giving up. Now switch to a default of 2,
10614 and allow the consensus parameter "hs_service_max_rdv_failures" to
10615 override. Fixes bug 24895; bugfix on 0.0.6.
10616 - New-style (v3) onion services now obey the "max rendezvous circuit
10617 attempts" logic. Previously they would make as many rendezvous
10618 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
10619 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
10621 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
10622 - Add Link protocol version 5 to the supported protocols list. Fixes
10623 bug 25070; bugfix on 0.3.1.1-alpha.
10625 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
10626 - Fix a set of false positives where relays would consider
10627 connections to other relays as being client-only connections (and
10628 thus e.g. deserving different link padding schemes) if those
10629 relays fell out of the consensus briefly. Now we look only at the
10630 initial handshake and whether the connection authenticated as a
10631 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
10633 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
10634 - The scheduler subsystem was failing to promptly notice changes in
10635 consensus parameters, making it harder to switch schedulers
10636 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
10638 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
10639 - Make our OOM handler aware of the geoip client history cache so it
10640 doesn't fill up the memory. This check is important for IPv6 and
10641 our DoS mitigation subsystem. Closes ticket 25122.
10643 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
10644 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
10645 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
10646 since they neither disabled TLS 1.3 nor enabled any of the
10647 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
10648 Closes ticket 24978.
10650 o Minor features (geoip):
10651 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
10654 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
10655 - When logging a failure to create an onion service's descriptor,
10656 also log what the problem with the descriptor was. Diagnostic
10659 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
10660 - Use the actual observed address of an incoming relay connection,
10661 not the canonical address of the relay from its descriptor, when
10662 making decisions about how to handle the incoming connection.
10663 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
10665 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
10666 - Fix a possible crash on malformed consensus. If a consensus had
10667 contained an unparseable protocol line, it could have made clients
10668 and relays crash with a null-pointer exception. To exploit this
10669 issue, however, an attacker would need to be able to subvert the
10670 directory authority system. Fixes bug 25251; bugfix on
10671 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
10673 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
10674 - Directory authorities, when refusing a descriptor from a rejected
10675 relay, now explicitly tell the relay (in its logs) to set a valid
10676 ContactInfo address and contact the bad-relays@ mailing list.
10677 Fixes bug 25170; bugfix on 0.2.9.1.
10679 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
10680 - When building with Rust on OSX, link against libresolv, to work
10681 around the issue at https://github.com/rust-lang/rust/issues/46797.
10682 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
10684 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
10685 - Remove a BUG() statement when a client fetches an onion descriptor
10686 that has a lower revision counter than the one in its cache. This
10687 can happen in normal circumstances due to HSDir desync. Fixes bug
10688 24976; bugfix on 0.3.2.1-alpha.
10690 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
10691 - Don't treat inability to store a cached consensus object as a bug:
10692 it can happen normally when we are out of disk space. Fixes bug
10693 24859; bugfix on 0.3.1.1-alpha.
10695 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
10696 - Improve the performance of our consensus-diff application code
10697 when Tor is built with the --enable-fragile-hardening option set.
10698 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
10700 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
10701 - Don't exit the Tor process if setrlimit() fails to change the file
10702 limit (which can happen sometimes on some versions of OSX). Fixes
10703 bug 21074; bugfix on 0.0.9pre5.
10705 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
10706 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
10708 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
10709 bugfix on 0.2.9.4-alpha.
10711 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
10712 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
10713 25005; bugfix on 0.3.2.7-rc.
10715 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
10716 - Look at the "HSRend" protocol version, not the "HSDir" protocol
10717 version, when deciding whether a consensus entry can support the
10718 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
10719 bugfix on 0.3.2.1-alpha.
10721 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
10722 - Update the "rust dependencies" submodule to be a project-level
10723 repository, rather than a user repository. Closes ticket 25323.
10725 o Documentation (backport from 0.3.3.1-alpha)
10726 - Document that operators who run more than one relay or bridge are
10727 expected to set MyFamily and ContactInfo correctly. Closes
10731 Changes in version 0.3.3.3-alpha - 2018-03-03
10732 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
10733 It includes an important security fix for a remote crash attack
10734 against directory authorities tracked as TROVE-2018-001.
10736 Additionally, with this release, we are upgrading the severity of a
10737 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
10738 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
10739 a use-after-free pattern. As such, we are now tracking that bug as
10740 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
10741 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
10743 This release also fixes several minor bugs and annoyances from
10746 Relays running 0.3.2.x should upgrade to one of the versions released
10747 today, for the fix to TROVE-2018-002. Directory authorities should
10748 also upgrade. (Relays on earlier versions might want to update too for
10749 the DoS mitigations.)
10751 o Major bugfixes (denial-of-service, directory authority):
10752 - Fix a protocol-list handling bug that could be used to remotely crash
10753 directory authorities with a null-pointer exception. Fixes bug 25074;
10754 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
10757 o Minor features (compatibility, OpenSSL):
10758 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
10759 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
10760 since they neither disabled TLS 1.3 nor enabled any of the
10761 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
10762 Closes ticket 24978.
10764 o Minor features (logging):
10765 - Clarify the log messages produced when getrandom() or a related
10766 entropy-generation mechanism gives an error. Closes ticket 25120.
10768 o Minor features (testing):
10769 - Add a "make test-rust" target to run the rust tests only. Closes
10772 o Minor bugfixes (denial-of-service):
10773 - Fix a possible crash on malformed consensus. If a consensus had
10774 contained an unparseable protocol line, it could have made clients
10775 and relays crash with a null-pointer exception. To exploit this
10776 issue, however, an attacker would need to be able to subvert the
10777 directory authority system. Fixes bug 25251; bugfix on
10778 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
10780 o Minor bugfixes (DoS mitigation):
10781 - Add extra safety checks when refilling the circuit creation bucket
10782 to ensure we never set a value above the allowed maximum burst.
10783 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
10784 - When a new consensus arrives, don't update our DoS-mitigation
10785 parameters if we aren't a public relay. Fixes bug 25223; bugfix
10788 o Minor bugfixes (man page, SocksPort):
10789 - Remove dead code from the old "SocksSocket" option, and rename
10790 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
10791 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
10793 o Minor bugfixes (performance):
10794 - Reduce the number of circuits that will be opened at once during
10795 the circuit build timeout phase. This is done by increasing the
10796 idle timeout to 3 minutes, and lowering the maximum number of
10797 concurrent learning circuits to 10. Fixes bug 24769; bugfix
10800 o Minor bugfixes (spec conformance):
10801 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
10803 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
10804 bugfix on 0.2.9.4-alpha.
10806 o Minor bugfixes (spec conformance, rust):
10807 - Resolve a denial-of-service issue caused by an infinite loop in
10808 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
10809 Also tracked as TROVE-2018-003.
10811 o Code simplification and refactoring:
10812 - Update the "rust dependencies" submodule to be a project-level
10813 repository, rather than a user repository. Closes ticket 25323.
10816 Changes in version 0.3.3.2-alpha - 2018-02-10
10817 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
10818 introduces a mechanism to handle the high loads that many relay
10819 operators have been reporting recently. It also fixes several bugs in
10820 older releases. If this new code proves reliable, we plan to backport
10821 it to older supported release series.
10823 o Major features (denial-of-service mitigation):
10824 - Give relays some defenses against the recent network overload. We
10825 start with three defenses (default parameters in parentheses).
10826 First: if a single client address makes too many concurrent
10827 connections (>100), hang up on further connections. Second: if a
10828 single client address makes circuits too quickly (more than 3 per
10829 second, with an allowed burst of 90) while also having too many
10830 connections open (3), refuse new create cells for the next while
10831 (1-2 hours). Third: if a client asks to establish a rendezvous
10832 point to you directly, ignore the request. These defenses can be
10833 manually controlled by new torrc options, but relays will also
10834 take guidance from consensus parameters, so there's no need to
10835 configure anything manually. Implements ticket 24902.
10837 o Major bugfixes (netflow padding):
10838 - Stop adding unneeded channel padding right after we finish
10839 flushing to a connection that has been trying to flush for many
10840 seconds. Instead, treat all partial or complete flushes as
10841 activity on the channel, which will defer the time until we need
10842 to add padding. This fix should resolve confusing and scary log
10843 messages like "Channel padding timeout scheduled 221453ms in the
10844 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
10846 o Major bugfixes (protocol versions):
10847 - Add Link protocol version 5 to the supported protocols list. Fixes
10848 bug 25070; bugfix on 0.3.1.1-alpha.
10850 o Major bugfixes (scheduler, consensus):
10851 - The scheduler subsystem was failing to promptly notice changes in
10852 consensus parameters, making it harder to switch schedulers
10853 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
10855 o Minor features (denial-of-service avoidance):
10856 - Make our OOM handler aware of the geoip client history cache so it
10857 doesn't fill up the memory. This check is important for IPv6 and
10858 our DoS mitigation subsystem. Closes ticket 25122.
10860 o Minor features (directory authority):
10861 - When directory authorities are unable to add signatures to a
10862 pending consensus, log the reason why. Closes ticket 24849.
10864 o Minor features (geoip):
10865 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
10868 o Minor features (logging, diagnostic):
10869 - When logging a failure to create an onion service's descriptor,
10870 also log what the problem with the descriptor was. Diagnostic for
10873 o Minor bugfix (channel connection):
10874 - Use the actual observed address of an incoming relay connection,
10875 not the canonical address of the relay from its descriptor, when
10876 making decisions about how to handle the incoming connection.
10877 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
10879 o Minor bugfix (directory authority):
10880 - Directory authorities, when refusing a descriptor from a rejected
10881 relay, now explicitly tell the relay (in its logs) to set a valid
10882 ContactInfo address and contact the bad-relays@ mailing list.
10883 Fixes bug 25170; bugfix on 0.2.9.1.
10885 o Minor bugfixes (all versions of Tor):
10886 - Use the "misspell" tool to detect and fix typos throughout the
10887 source code. Fixes bug 23650; bugfix on various versions of Tor.
10888 Patch from Deepesh Pathak.
10890 o Minor bugfixes (circuit, cannibalization):
10891 - Don't cannibalize preemptively-built circuits if we no longer
10892 recognize their first hop. This situation can happen if our Guard
10893 relay went off the consensus after the circuit was created. Fixes
10894 bug 24469; bugfix on 0.0.6.
10896 o Minor bugfixes (correctness):
10897 - Remove a nonworking, unnecessary check to see whether a circuit
10898 hop's identity digest was set when the circuit failed. Fixes bug
10899 24927; bugfix on 0.2.4.4-alpha.
10901 o Minor bugfixes (logging):
10902 - Don't treat inability to store a cached consensus object as a bug:
10903 it can happen normally when we are out of disk space. Fixes bug
10904 24859; bugfix on 0.3.1.1-alpha.
10905 - Fix a (mostly harmless) race condition when invoking
10906 LOG_PROTOCOL_WARN message from a subthread while the torrc options
10907 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
10909 o Minor bugfixes (onion services):
10910 - Remove a BUG() statement when a client fetches an onion descriptor
10911 that has a lower revision counter than the one in its cache. This
10912 can happen in normal circumstances due to HSDir desync. Fixes bug
10913 24976; bugfix on 0.3.2.1-alpha.
10914 - If we are configured to offer a single onion service, don't log
10915 long-term established one hop rendezvous points in the heartbeat.
10916 Fixes bug 25116; bugfix on 0.2.9.6-rc.
10918 o Minor bugfixes (performance):
10919 - Avoid calling protocol_list_supports_protocol() from inside tight
10920 loops when running with cached routerinfo_t objects. Instead,
10921 summarize the relevant protocols as flags in the routerinfo_t, as
10922 we do for routerstatus_t objects. This change simplifies our code
10923 a little, and saves a large amount of short-term memory allocation
10924 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
10926 o Minor bugfixes (Rust FFI):
10927 - Fix a minor memory leak which would happen whenever the C code
10928 would call the Rust implementation of
10929 protover_get_supported_protocols(). This was due to the C version
10930 returning a static string, whereas the Rust version newly allocated
10931 a CString to pass across the FFI boundary. Consequently, the C
10932 code was not expecting to need to free() what it was given. Fixes
10933 bug 25127; bugfix on 0.3.2.1-alpha.
10935 o Minor bugfixes (scheduler, KIST):
10936 - Avoid adding the same channel twice in the KIST scheduler pending
10937 list, which would waste CPU cycles. Fixes bug 24700; bugfix
10940 o Minor bugfixes (unit test, monotonic time):
10941 - Increase a constant (1msec to 10msec) in the monotonic time test
10942 that makes sure the nsec/usec/msec times read are synchronized.
10943 This change was needed to accommodate slow systems like armel or
10944 when the clock_gettime() is not a VDSO on the running kernel.
10945 Fixes bug 25113; bugfix on 0.2.9.1.
10947 o Minor bugfixes (v3 onion services):
10948 - Look at the "HSRend" protocol version, not the "HSDir" protocol
10949 version, when deciding whether a consensus entry can support the
10950 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
10951 bugfix on 0.3.2.1-alpha.
10953 o Code simplification and refactoring:
10954 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
10956 - Remove a series of counters used to track circuit extend attempts
10957 and connection status but that in reality we aren't using for
10958 anything other than stats logged by a SIGUSR1 signal. Closes
10961 o Documentation (man page):
10962 - The HiddenServiceVersion torrc option accepts only one number:
10963 either version 2 or 3. Closes ticket 25026; bugfix
10967 Changes in version 0.3.3.1-alpha - 2018-01-25
10968 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
10969 several new features to Tor, including several improvements to
10970 bootstrapping, and support for an experimental "vanguards" feature to
10971 resist guard discovery attacks. This series also includes better
10972 support for applications that need to embed Tor or manage v3
10975 o Major features (embedding):
10976 - There is now a documented stable API for programs that need to
10977 embed Tor. See tor_api.h for full documentation and known bugs.
10978 Closes ticket 23684.
10979 - Tor now has support for restarting in the same process.
10980 Controllers that run Tor using the "tor_api.h" interface can now
10981 restart Tor after Tor has exited. This support is incomplete,
10982 however: we fixed crash bugs that prevented it from working at
10983 all, but many bugs probably remain, including a possibility of
10984 security issues. Implements ticket 24581.
10986 o Major features (IPv6, directory documents):
10987 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
10988 consensus. This information makes it easier for IPv6 clients to
10989 bootstrap and choose reachable entry guards. Implements ticket 23826.
10990 - Add consensus method 28, which removes IPv6 ORPorts from
10991 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
10992 are redundant in microdescs. This change will be used by Tor clients
10993 on 0.2.8.x and later. (That is to say, with all Tor clients that
10994 have IPv6 bootstrap and guard support.) Implements ticket 23828.
10995 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
10996 set by different numbers of authorities. Fixes 23870
10999 o Major features (onion service v3, control port):
11000 - The control port now supports commands and events for v3 onion
11001 services. It is now possible to create ephemeral v3 services using
11002 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
11003 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
11004 DEL_ONION) have been extended to support v3 onion services. Closes
11005 ticket 20699; implements proposal 284.
11007 o Major features (onion services):
11008 - Provide torrc options to pin the second and third hops of onion
11009 service circuits to a list of nodes. The option HSLayer2Guards
11010 pins the second hop, and the option HSLayer3Guards pins the third
11011 hop. These options are for use in conjunction with experiments
11012 with "vanguards" for preventing guard enumeration attacks. Closes
11015 o Major features (rust, portability, experimental):
11016 - Tor now ships with an optional implementation of one of its
11017 smaller modules (protover.c) in the Rust programming language. To
11018 try it out, install a Rust build environment, and configure Tor
11019 with "--enable-rust --enable-cargo-online-mode". This should not
11020 cause any user-visible changes, but should help us gain more
11021 experience with Rust, and plan future Rust integration work.
11022 Implementation by Chelsea Komlo. Closes ticket 22840.
11024 o Minor features (storage, configuration):
11025 - Users can store cached directory documents somewhere other than
11026 the DataDirectory by using the CacheDirectory option. Similarly,
11027 the storage location for relay's keys can be overridden with the
11028 KeyDirectory option. Closes ticket 22703.
11030 o Major features (v3 onion services, ipv6):
11031 - When v3 onion service clients send introduce cells, they now
11032 include the IPv6 address of the rendezvous point, if it has one.
11033 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
11034 in future Tor versions, IPv6-only v3 single onion services will be
11035 able to use IPv6 addresses to connect directly to the rendezvous
11036 point. Closes ticket 23577. Patch by Neel Chauhan.
11038 o Major bugfixes (onion services, retry behavior):
11039 - Fix an "off by 2" error in counting rendezvous failures on the
11040 onion service side. While we thought we would stop the rendezvous
11041 attempt after one failed circuit, we were actually making three
11042 circuit attempts before giving up. Now switch to a default of 2,
11043 and allow the consensus parameter "hs_service_max_rdv_failures" to
11044 override. Fixes bug 24895; bugfix on 0.0.6.
11045 - New-style (v3) onion services now obey the "max rendezvous circuit
11046 attempts" logic. Previously they would make as many rendezvous
11047 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
11048 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
11050 o Major bugfixes (relays):
11051 - Fix a set of false positives where relays would consider
11052 connections to other relays as being client-only connections (and
11053 thus e.g. deserving different link padding schemes) if those
11054 relays fell out of the consensus briefly. Now we look only at the
11055 initial handshake and whether the connection authenticated as a
11056 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
11058 o Minor feature (IPv6):
11059 - Make IPv6-only clients wait for microdescs for relays, even if we
11060 were previously using descriptors (or were using them as a bridge)
11061 and have a cached descriptor for them. Implements ticket 23827.
11062 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
11063 them, rather than waiting to download microdescriptors.
11064 Implements ticket 23827.
11066 o Minor features (cleanup):
11067 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
11068 when it stops. Closes ticket 23271.
11070 o Minor features (defensive programming):
11071 - Most of the functions in Tor that free objects have been replaced
11072 with macros that free the objects and set the corresponding
11073 pointers to NULL. This change should help prevent a large class of
11074 dangling pointer bugs. Closes ticket 24337.
11075 - Where possible, the tor_free() macro now only evaluates its input
11076 once. Part of ticket 24337.
11077 - Check that microdesc ed25519 ids are non-zero in
11078 node_get_ed25519_id() before returning them. Implements ticket
11079 24001, patch by "aruna1234".
11081 o Minor features (embedding):
11082 - Tor can now start with a preauthenticated control connection
11083 created by the process that launched it. This feature is meant for
11084 use by programs that want to launch and manage a Tor process
11085 without allowing other programs to manage it as well. For more
11086 information, see the __OwningControllerFD option documented in
11087 control-spec.txt. Closes ticket 23900.
11088 - On most errors that would cause Tor to exit, it now tries to
11089 return from the tor_main() function, rather than calling the
11090 system exit() function. Most users won't notice a difference here,
11091 but it should be significant for programs that run Tor inside
11092 a separate thread: they should now be able to survive Tor's exit
11093 conditions rather than having Tor shut down the entire process.
11094 Closes ticket 23848.
11095 - Applications that want to embed Tor can now tell Tor not to
11096 register any of its own POSIX signal handlers, using the
11097 __DisableSignalHandlers option. Closes ticket 24588.
11099 o Minor features (fallback directory list):
11100 - Avoid selecting fallbacks that change their IP addresses too
11101 often. Select more fallbacks by ignoring the Guard flag, and
11102 allowing lower cutoffs for the Running and V2Dir flags. Also allow
11103 a lower bandwidth, and a higher number of fallbacks per operator
11104 (5% of the list). Implements ticket 24785.
11105 - Update the fallback whitelist and blacklist based on opt-ins and
11106 relay changes. Closes tickets 22321, 24678, 22527, 24135,
11109 o Minor features (fallback directory mirror configuration):
11110 - Add a nickname to each fallback in a C comment. This makes it
11111 easier for operators to find their relays, and allows stem to use
11112 nicknames to identify fallbacks. Implements ticket 24600.
11113 - Add a type and version header to the fallback directory mirror
11114 file. Also add a delimiter to the end of each fallback entry. This
11115 helps external parsers like stem and Relay Search. Implements
11117 - Add an extrainfo cache flag for each fallback in a C comment. This
11118 allows stem to use fallbacks to fetch extra-info documents, rather
11119 than using authorities. Implements ticket 22759.
11120 - Add the generateFallbackDirLine.py script for automatically
11121 generating fallback directory mirror lines from relay fingerprints.
11122 No more typos! Add the lookupFallbackDirContact.py script for
11123 automatically looking up operator contact info from relay
11124 fingerprints. Implements ticket 24706, patch by teor and atagar.
11125 - Reject any fallback directory mirror that serves an expired
11126 consensus. Implements ticket 20942, patch by "minik".
11127 - Remove commas and equals signs from external string inputs to the
11128 fallback list. This avoids format confusion attacks. Implements
11130 - Remove the "weight=10" line from fallback directory mirror
11131 entries. Ticket 24681 will maintain the current fallback weights
11132 by changing Tor's default fallback weight to 10. Implements
11134 - Stop logging excessive information about fallback netblocks.
11135 Implements ticket 24791.
11137 o Minor features (forward-compatibility):
11138 - If a relay supports some link authentication protocol that we do
11139 not recognize, then include that relay's ed25519 key when telling
11140 other relays to extend to it. Previously, we treated future
11141 versions as if they were too old to support ed25519 link
11142 authentication. Closes ticket 20895.
11144 o Minor features (heartbeat):
11145 - Add onion service information to our heartbeat logs, displaying
11146 stats about the activity of configured onion services. Closes
11149 o Minor features (instrumentation, development):
11150 - Add the MainloopStats option to allow developers to get
11151 instrumentation information from the main event loop via the
11152 heartbeat messages. We hope to use this to improve Tor's behavior
11153 when it's trying to sleep. Closes ticket 24605.
11155 o Minor features (log messages):
11156 - Improve a warning message that happens when we fail to re-parse an
11157 old router because of an expired certificate. Closes ticket 20020.
11158 - Make the log more quantitative when we hit MaxMemInQueues
11159 threshold exposing some values. Closes ticket 24501.
11161 o Minor features (logging, android):
11162 - Added support for the Android logging subsystem. Closes
11165 o Minor features (performance):
11166 - Support predictive circuit building for onion service circuits
11167 with multiple layers of guards. Closes ticket 23101.
11168 - Use stdatomic.h where available, rather than mutexes, to implement
11169 atomic_counter_t. Closes ticket 23953.
11171 o Minor features (performance, 32-bit):
11172 - Improve performance on 32-bit systems by avoiding 64-bit division
11173 when calculating the timestamp in milliseconds for channel padding
11174 computations. Implements ticket 24613.
11175 - Improve performance on 32-bit systems by avoiding 64-bit division
11176 when timestamping cells and buffer chunks for OOM calculations.
11177 Implements ticket 24374.
11179 o Minor features (performance, OSX, iOS):
11180 - Use the mach_approximate_time() function (when available) to
11181 implement coarse monotonic time. Having a coarse time function
11182 should avoid a large number of system calls, and improve
11183 performance slightly, especially under load. Closes ticket 24427.
11185 o Minor features (performance, windows):
11186 - Improve performance on Windows Vista and Windows 7 by adjusting
11187 TCP send window size according to the recommendation from
11188 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
11191 o Major features (relay):
11192 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
11193 operator to use a more reasonable ("reduced") exit policy, rather
11194 than the default one. If you want to run an exit node without
11195 thinking too hard about which ports to allow, this one is for you.
11196 Closes ticket 13605. Patch from Neel Chauhan.
11198 o Minor features (testing, debugging, embedding):
11199 - For development purposes, Tor now has a mode in which it runs for
11200 a few seconds, then stops, and starts again without exiting the
11201 process. This mode is meant to help us debug various issues with
11202 ticket 23847. To use this feature, compile with
11203 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
11204 environment variable. This is expected to crash a lot, and is
11205 really meant for developers only. It will likely be removed in a
11206 future release. Implements ticket 24583.
11208 o Minor bugfix (network IPv6 test):
11209 - Tor's test scripts now check if "ping -6 ::1" works when the user
11210 runs "make test-network-all". Fixes bug 24677; bugfix on
11211 0.2.9.3-alpha. Patch by "ffmancera".
11213 o Minor bugfixes (build, rust):
11214 - Fix output of autoconf checks to display success messages for Rust
11215 dependencies and a suitable rustc compiler version. Fixes bug
11216 24612; bugfix on 0.3.1.3-alpha.
11217 - When building with Rust on OSX, link against libresolv, to work
11218 around the issue at https://github.com/rust-lang/rust/issues/46797.
11219 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
11220 - Don't pass the --quiet option to cargo: it seems to suppress some
11221 errors, which is not what we want to do when building. Fixes bug
11222 24518; bugfix on 0.3.1.7.
11223 - Build correctly when building from outside Tor's source tree with
11224 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
11227 o Minor bugfixes (directory authorities, IPv6):
11228 - When creating a routerstatus (vote) from a routerinfo (descriptor),
11229 set the IPv6 address to the unspecified IPv6 address, and
11230 explicitly initialize the port to zero. Fixes bug 24488; bugfix
11233 o Minor bugfixes (fallback directory mirrors):
11234 - Make updateFallbackDirs.py search harder for python. (Some OSs
11235 don't put it in /usr/bin.) Fixes bug 24708; bugfix
11238 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
11239 - When hibernating, close connections normally and allow them to
11240 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
11242 - Do not attempt to launch self-reachability tests when entering
11243 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
11244 - Resolve several bugs related to descriptor fetching on bridge
11245 clients with bandwidth accounting enabled. (This combination is
11246 not recommended!) Fixes a case of bug 12062; bugfix
11248 - When hibernating, do not attempt to launch DNS checks. Fixes a
11249 case of bug 12062; bugfix on 0.1.2.2-alpha.
11250 - When hibernating, do not try to upload or download descriptors.
11251 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
11253 o Minor bugfixes (IPv6, bridges):
11254 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
11255 bugfix on 0.2.8.2-alpha.
11256 - Tor now sets IPv6 address in the routerstatus as well as in the
11257 router descriptors when updating addresses for a bridge. Closes
11258 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
11260 o Minor bugfixes (linux seccomp2 sandbox):
11261 - When running with the sandbox enabled, reload configuration files
11262 correctly even when %include was used. Previously we would crash.
11263 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
11265 o Minor bugfixes (memory leaks):
11266 - Avoid possible at-exit memory leaks related to use of Libevent's
11267 event_base_once() function. (This function tends to leak memory if
11268 the event_base is closed before the event fires.) Fixes bug 24584;
11269 bugfix on 0.2.8.1-alpha.
11270 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
11273 o Minor bugfixes (OSX):
11274 - Don't exit the Tor process if setrlimit() fails to change the file
11275 limit (which can happen sometimes on some versions of OSX). Fixes
11276 bug 21074; bugfix on 0.0.9pre5.
11278 o Minor bugfixes (performance, fragile-hardening):
11279 - Improve the performance of our consensus-diff application code
11280 when Tor is built with the --enable-fragile-hardening option set.
11281 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
11283 o Minor bugfixes (performance, timeouts):
11284 - Consider circuits for timeout as soon as they complete a hop. This
11285 is more accurate than applying the timeout in
11286 circuit_expire_building() because that function is only called
11287 once per second, which is now too slow for typical timeouts on the
11288 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
11289 - Use onion service circuits (and other circuits longer than 3 hops)
11290 to calculate a circuit build timeout. Previously, Tor only
11291 calculated its build timeout based on circuits that planned to be
11292 exactly 3 hops long. With this change, we include measurements
11293 from all circuits at the point where they complete their third
11294 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
11296 o Minor bugfixes (testing):
11297 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
11298 bugfix on 0.2.3.1-alpha.
11299 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
11300 25005; bugfix on 0.3.2.7-rc.
11302 o Code simplification and refactoring:
11303 - Remove /usr/athena from search path in configure.ac. Closes
11305 - Remove duplicate code in node_has_curve25519_onion_key() and
11306 node_get_curve25519_onion_key(), and add a check for a zero
11307 microdesc curve25519 onion key. Closes ticket 23966, patch by
11308 "aruna1234" and teor.
11309 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
11310 memory allocations with large numbers of OR connections (e.g.
11311 relays). Closes ticket 24119.
11312 - Separate the function that deletes ephemeral files when Tor
11314 - Small changes to Tor's buf_t API to make it suitable for use as a
11315 general-purpose safe string constructor. Closes ticket 22342.
11316 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
11317 avoid source code identifier confusion. Closes ticket 24467.
11318 - The tor_git_revision[] constant no longer needs to be redeclared
11319 by everything that links against the rest of Tor. Done as part of
11320 ticket 23845, to simplify our external API.
11321 - We make extend_info_from_node() use node_get_curve25519_onion_key()
11322 introduced in ticket 23577 to access the curve25519 public keys
11323 rather than accessing it directly. Closes ticket 23760. Patch by
11325 - Add a function to log channels' scheduler state changes to aid
11326 debugging efforts. Closes ticket 24531.
11329 - Add documentation on how to build tor with Rust dependencies
11330 without having to be online. Closes ticket 22907; bugfix
11332 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
11333 traffic. Closes ticket 24318.
11334 - Document that OutboundBindAddress doesn't apply to DNS requests.
11335 Closes ticket 22145. Patch from Aruna Maurya.
11336 - Document that operators who run more than one relay or bridge are
11337 expected to set MyFamily and ContactInfo correctly. Closes
11340 o Code simplification and refactoring (channels):
11341 - Remove the incoming and outgoing channel queues. These were never
11342 used, but still took up a step in our fast path.
11343 - The majority of the channel unit tests have been rewritten and the
11344 code coverage has now been raised to 83.6% for channel.c. Closes
11346 - Remove other dead code from the channel subsystem: All together,
11347 this cleanup has removed more than 1500 lines of code overall and
11348 adding very little except for unit test.
11350 o Code simplification and refactoring (circuit rendezvous):
11351 - Split the client-side rendezvous circuit lookup into two
11352 functions: one that returns only established circuits and another
11353 that returns all kinds of circuits. Closes ticket 23459.
11355 o Code simplification and refactoring (controller):
11356 - Make most of the variables in networkstatus_getinfo_by_purpose()
11357 const. Implements ticket 24489.
11360 Changes in version 0.3.2.9 - 2018-01-09
11361 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
11363 The 0.3.2 series includes our long-anticipated new onion service
11364 design, with numerous security features. (For more information, see
11365 our blog post at https://blog.torproject.org/fall-harvest.) We also
11366 have a new circuit scheduler algorithm for improved performance on
11367 relays everywhere (see https://blog.torproject.org/kist-and-tell),
11368 along with many smaller features and bugfixes.
11370 Per our stable release policy, we plan to support each stable release
11371 series for at least the next nine months, or for three months after
11372 the first stable release of the next series: whichever is longer. If
11373 you need a release with long-term support, we recommend that you stay
11374 with the 0.2.9 series.
11376 Below is a list of the changes since 0.3.2.8-rc. For a list of all
11377 changes since 0.3.1, see the ReleaseNotes file.
11379 o Minor features (fallback directory mirrors):
11380 - The fallback directory list has been re-generated based on the
11381 current status of the network. Tor uses fallback directories to
11382 bootstrap when it doesn't yet have up-to-date directory
11383 information. Closes ticket 24801.
11384 - Make the default DirAuthorityFallbackRate 0.1, so that clients
11385 prefer to bootstrap from fallback directory mirrors. This is a
11386 follow-up to 24679, which removed weights from the default
11387 fallbacks. Implements ticket 24681.
11389 o Minor features (geoip):
11390 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
11393 o Minor bugfixes (address selection):
11394 - When the fascist_firewall_choose_address_ functions don't find a
11395 reachable address, set the returned address to the null address
11396 and port. This is a precautionary measure, because some callers do
11397 not check the return value. Fixes bug 24736; bugfix
11400 o Minor bugfixes (compilation):
11401 - Resolve a few shadowed-variable warnings in the onion service
11402 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
11404 o Minor bugfixes (portability, msvc):
11405 - Fix a bug in the bit-counting parts of our timing-wheel code on
11406 MSVC. (Note that MSVC is still not a supported build platform, due
11407 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
11411 Changes in version 0.3.2.8-rc - 2017-12-21
11412 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
11413 schedulers that had led servers under heavy load to overload their
11414 outgoing connections. All relay operators running earlier 0.3.2.x
11415 versions should upgrade. This version also includes a mitigation for
11416 over-full DESTROY queues leading to out-of-memory conditions: if it
11417 works, we will soon backport it to earlier release series.
11419 This is the second release candidate in the 0.3.2 series. If we find
11420 no new bugs or regression here, then the first stable 0.3.2 release
11421 will be nearly identical to this.
11423 o Major bugfixes (KIST, scheduler):
11424 - The KIST scheduler did not correctly account for data already
11425 enqueued in each connection's send socket buffer, particularly in
11426 cases when the TCP/IP congestion window was reduced between
11427 scheduler calls. This situation lead to excessive per-connection
11428 buffering in the kernel, and a potential memory DoS. Fixes bug
11429 24665; bugfix on 0.3.2.1-alpha.
11431 o Minor features (geoip):
11432 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
11435 o Minor bugfixes (hidden service v3):
11436 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
11437 the probability of reaching a service for a client missing
11438 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
11440 o Minor bugfixes (memory usage):
11441 - When queuing DESTROY cells on a channel, only queue the circuit-id
11442 and reason fields: not the entire 514-byte cell. This fix should
11443 help mitigate any bugs or attacks that fill up these queues, and
11444 free more RAM for other uses. Fixes bug 24666; bugfix
11447 o Minor bugfixes (scheduler, KIST):
11448 - Use a sane write limit for KISTLite when writing onto a connection
11449 buffer instead of using INT_MAX and shoving as much as it can.
11450 Because the OOM handler cleans up circuit queues, we are better
11451 off at keeping them in that queue instead of the connection's
11452 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
11455 Changes in version 0.3.2.7-rc - 2017-12-14
11456 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
11457 including some that could affect reliability or correctness.
11459 This is the first release candidate in the 0.3.2 series. If we find no
11460 new bugs or regression here, then the first stable 0.3.2. release will
11461 be nearly identical to this.
11463 o Major bugfixes (circuit prediction):
11464 - Fix circuit prediction logic so that a client doesn't treat a port
11465 as being "handled" by a circuit if that circuit already has
11466 isolation settings on it. This change should make Tor clients more
11467 responsive by improving their chances of having a pre-created
11468 circuit ready for use when a request arrives. Fixes bug 18859;
11469 bugfix on 0.2.3.3-alpha.
11471 o Minor features (logging):
11472 - Provide better warnings when the getrandom() syscall fails. Closes
11475 o Minor features (portability):
11476 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
11477 (It doesn't yet work with the sandbox enabled.) Closes
11480 o Minor bugfixes (bridge clients, bootstrap):
11481 - Retry directory downloads when we get our first bridge descriptor
11482 during bootstrap or while reconnecting to the network. Keep
11483 retrying every time we get a bridge descriptor, until we have a
11484 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
11485 - Stop delaying bridge descriptor fetches when we have cached bridge
11486 descriptors. Instead, only delay bridge descriptor fetches when we
11487 have at least one reachable bridge. Fixes part of bug 24367;
11488 bugfix on 0.2.0.3-alpha.
11489 - Stop delaying directory fetches when we have cached bridge
11490 descriptors. Instead, only delay bridge descriptor fetches when
11491 all our bridges are definitely unreachable. Fixes part of bug
11492 24367; bugfix on 0.2.0.3-alpha.
11494 o Minor bugfixes (compilation):
11495 - Fix a signed/unsigned comparison warning introduced by our fix to
11496 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
11498 o Minor bugfixes (correctness):
11499 - Fix several places in our codebase where a C compiler would be
11500 likely to eliminate a check, based on assuming that undefined
11501 behavior had not happened elsewhere in the code. These cases are
11502 usually a sign of redundant checking or dubious arithmetic. Found
11503 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
11504 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
11507 o Minor bugfixes (onion service v3):
11508 - Fix a race where an onion service would launch a new intro circuit
11509 after closing an old one, but fail to register it before freeing
11510 the previously closed circuit. This bug was making the service
11511 unable to find the established intro circuit and thus not upload
11512 its descriptor, thus making a service unavailable for up to 24
11513 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
11515 o Minor bugfixes (scheduler, KIST):
11516 - Properly set the scheduler state of an unopened channel in the
11517 KIST scheduler main loop. This prevents a harmless but annoying
11518 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
11519 - Avoid a possible integer overflow when computing the available
11520 space on the TCP buffer of a channel. This had no security
11521 implications; but could make KIST allow too many cells on a
11522 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
11523 - Downgrade to "info" a harmless warning about the monotonic time
11524 moving backwards: This can happen on platform not supporting
11525 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
11528 Changes in version 0.3.2.6-alpha - 2017-12-01
11529 This version of Tor is the latest in the 0.3.2 alpha series. It
11530 includes fixes for several important security issues. All Tor users
11531 should upgrade to this release, or to one of the other releases coming
11534 o Major bugfixes (security):
11535 - Fix a denial of service bug where an attacker could use a
11536 malformed directory object to cause a Tor instance to pause while
11537 OpenSSL would try to read a passphrase from the terminal. (Tor
11538 instances run without a terminal, which is the case for most Tor
11539 packages, are not impacted.) Fixes bug 24246; bugfix on every
11540 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11541 Found by OSS-Fuzz as testcase 6360145429790720.
11542 - Fix a denial of service issue where an attacker could crash a
11543 directory authority using a malformed router descriptor. Fixes bug
11544 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
11546 - When checking for replays in the INTRODUCE1 cell data for a
11547 (legacy) onion service, correctly detect replays in the RSA-
11548 encrypted part of the cell. We were previously checking for
11549 replays on the entire cell, but those can be circumvented due to
11550 the malleability of Tor's legacy hybrid encryption. This fix helps
11551 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11552 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11555 o Major bugfixes (security, onion service v2):
11556 - Fix a use-after-free error that could crash v2 Tor onion services
11557 when they failed to open circuits while expiring introduction
11558 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
11559 also tracked as TROVE-2017-013 and CVE-2017-8823.
11561 o Major bugfixes (security, relay):
11562 - When running as a relay, make sure that we never build a path
11563 through ourselves, even in the case where we have somehow lost the
11564 version of our descriptor appearing in the consensus. Fixes part
11565 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
11566 as TROVE-2017-012 and CVE-2017-8822.
11567 - When running as a relay, make sure that we never choose ourselves
11568 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
11569 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
11571 o Minor feature (relay statistics):
11572 - Change relay bandwidth reporting stats interval from 4 hours to 24
11573 hours in order to reduce the efficiency of guard discovery
11574 attacks. Fixes ticket 23856.
11576 o Minor features (directory authority):
11577 - Add an IPv6 address for the "bastet" directory authority. Closes
11580 o Minor bugfixes (client):
11581 - By default, do not enable storage of client-side DNS values. These
11582 values were unused by default previously, but they should not have
11583 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
11586 Changes in version 0.3.1.9 - 2017-12-01:
11587 Tor 0.3.1.9 backports important security and stability fixes from the
11588 0.3.2 development series. All Tor users should upgrade to this
11589 release, or to another of the releases coming out today.
11591 o Major bugfixes (security, backport from 0.3.2.6-alpha):
11592 - Fix a denial of service bug where an attacker could use a
11593 malformed directory object to cause a Tor instance to pause while
11594 OpenSSL would try to read a passphrase from the terminal. (Tor
11595 instances run without a terminal, which is the case for most Tor
11596 packages, are not impacted.) Fixes bug 24246; bugfix on every
11597 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11598 Found by OSS-Fuzz as testcase 6360145429790720.
11599 - Fix a denial of service issue where an attacker could crash a
11600 directory authority using a malformed router descriptor. Fixes bug
11601 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
11603 - When checking for replays in the INTRODUCE1 cell data for a
11604 (legacy) onion service, correctly detect replays in the RSA-
11605 encrypted part of the cell. We were previously checking for
11606 replays on the entire cell, but those can be circumvented due to
11607 the malleability of Tor's legacy hybrid encryption. This fix helps
11608 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11609 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11612 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
11613 - Fix a use-after-free error that could crash v2 Tor onion services
11614 when they failed to open circuits while expiring introduction
11615 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
11616 also tracked as TROVE-2017-013 and CVE-2017-8823.
11618 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11619 - When running as a relay, make sure that we never build a path
11620 through ourselves, even in the case where we have somehow lost the
11621 version of our descriptor appearing in the consensus. Fixes part
11622 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
11623 as TROVE-2017-012 and CVE-2017-8822.
11624 - When running as a relay, make sure that we never choose ourselves
11625 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
11626 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
11628 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
11629 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
11630 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
11631 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
11632 identifying and finding a workaround to this bug and to Moritz,
11633 Arthur Edelstein, and Roger for helping to track it down and
11636 o Minor features (bridge):
11637 - Bridges now include notice in their descriptors that they are
11638 bridges, and notice of their distribution status, based on their
11639 publication settings. Implements ticket 18329. For more fine-
11640 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11643 o Minor features (directory authority, backport from 0.3.2.6-alpha):
11644 - Add an IPv6 address for the "bastet" directory authority. Closes
11647 o Minor features (geoip):
11648 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11651 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
11652 - Avoid unnecessary calls to directory_fetches_from_authorities() on
11653 relays, to prevent spurious address resolutions and descriptor
11654 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
11655 bugfix on in 0.2.8.1-alpha.
11657 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
11658 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
11659 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
11661 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
11662 - When a circuit is marked for close, do not attempt to package any
11663 cells for channels on that circuit. Previously, we would detect
11664 this condition lower in the call stack, when we noticed that the
11665 circuit had no attached channel, and log an annoying message.
11666 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
11668 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
11669 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
11670 so it matches dir-spec.txt. Fixes bug 24262; bugfix
11673 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
11674 - Avoid a crash when transitioning from client mode to bridge mode.
11675 Previously, we would launch the worker threads whenever our
11676 "public server" mode changed, but not when our "server" mode
11677 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
11680 Changes in version 0.3.0.13 - 2017-12-01
11681 Tor 0.3.0.13 backports important security and stability bugfixes from
11682 later Tor releases. All Tor users should upgrade to this release, or
11683 to another of the releases coming out today.
11685 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
11686 2018. If you need a release with long-term support, please stick with
11687 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11689 o Major bugfixes (security, backport from 0.3.2.6-alpha):
11690 - Fix a denial of service bug where an attacker could use a
11691 malformed directory object to cause a Tor instance to pause while
11692 OpenSSL would try to read a passphrase from the terminal. (Tor
11693 instances run without a terminal, which is the case for most Tor
11694 packages, are not impacted.) Fixes bug 24246; bugfix on every
11695 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11696 Found by OSS-Fuzz as testcase 6360145429790720.
11697 - Fix a denial of service issue where an attacker could crash a
11698 directory authority using a malformed router descriptor. Fixes bug
11699 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
11701 - When checking for replays in the INTRODUCE1 cell data for a
11702 (legacy) onion service, correctly detect replays in the RSA-
11703 encrypted part of the cell. We were previously checking for
11704 replays on the entire cell, but those can be circumvented due to
11705 the malleability of Tor's legacy hybrid encryption. This fix helps
11706 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11707 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11710 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
11711 - Fix a use-after-free error that could crash v2 Tor onion services
11712 when they failed to open circuits while expiring introduction
11713 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
11714 also tracked as TROVE-2017-013 and CVE-2017-8823.
11716 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11717 - When running as a relay, make sure that we never build a path
11718 through ourselves, even in the case where we have somehow lost the
11719 version of our descriptor appearing in the consensus. Fixes part
11720 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
11721 as TROVE-2017-012 and CVE-2017-8822.
11722 - When running as a relay, make sure that we never choose ourselves
11723 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
11724 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
11726 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
11727 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
11728 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
11729 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
11730 identifying and finding a workaround to this bug and to Moritz,
11731 Arthur Edelstein, and Roger for helping to track it down and
11734 o Minor features (security, windows, backport from 0.3.1.1-alpha):
11735 - Enable a couple of pieces of Windows hardening: one
11736 (HeapEnableTerminationOnCorruption) that has been on-by-default
11737 since Windows 8, and unavailable before Windows 7; and one
11738 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
11739 affect us, but shouldn't do any harm. Closes ticket 21953.
11741 o Minor features (bridge, backport from 0.3.1.9):
11742 - Bridges now include notice in their descriptors that they are
11743 bridges, and notice of their distribution status, based on their
11744 publication settings. Implements ticket 18329. For more fine-
11745 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11748 o Minor features (directory authority, backport from 0.3.2.6-alpha):
11749 - Add an IPv6 address for the "bastet" directory authority. Closes
11752 o Minor features (geoip):
11753 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11756 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
11757 - Avoid unnecessary calls to directory_fetches_from_authorities() on
11758 relays, to prevent spurious address resolutions and descriptor
11759 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
11760 bugfix on in 0.2.8.1-alpha.
11762 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
11763 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
11764 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
11766 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
11767 - When a circuit is marked for close, do not attempt to package any
11768 cells for channels on that circuit. Previously, we would detect
11769 this condition lower in the call stack, when we noticed that the
11770 circuit had no attached channel, and log an annoying message.
11771 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
11773 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
11774 - Avoid a crash when transitioning from client mode to bridge mode.
11775 Previously, we would launch the worker threads whenever our
11776 "public server" mode changed, but not when our "server" mode
11777 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
11779 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
11780 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
11781 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
11784 Changes in version 0.2.9.14 - 2017-12-01
11785 Tor 0.3.0.13 backports important security and stability bugfixes from
11786 later Tor releases. All Tor users should upgrade to this release, or
11787 to another of the releases coming out today.
11789 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
11790 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
11791 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
11792 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
11793 identifying and finding a workaround to this bug and to Moritz,
11794 Arthur Edelstein, and Roger for helping to track it down and
11797 o Major bugfixes (security, backport from 0.3.2.6-alpha):
11798 - Fix a denial of service bug where an attacker could use a
11799 malformed directory object to cause a Tor instance to pause while
11800 OpenSSL would try to read a passphrase from the terminal. (Tor
11801 instances run without a terminal, which is the case for most Tor
11802 packages, are not impacted.) Fixes bug 24246; bugfix on every
11803 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11804 Found by OSS-Fuzz as testcase 6360145429790720.
11805 - Fix a denial of service issue where an attacker could crash a
11806 directory authority using a malformed router descriptor. Fixes bug
11807 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
11809 - When checking for replays in the INTRODUCE1 cell data for a
11810 (legacy) onion service, correctly detect replays in the RSA-
11811 encrypted part of the cell. We were previously checking for
11812 replays on the entire cell, but those can be circumvented due to
11813 the malleability of Tor's legacy hybrid encryption. This fix helps
11814 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11815 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11818 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
11819 - Fix a use-after-free error that could crash v2 Tor onion services
11820 when they failed to open circuits while expiring introduction
11821 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
11822 also tracked as TROVE-2017-013 and CVE-2017-8823.
11824 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11825 - When running as a relay, make sure that we never build a path
11826 through ourselves, even in the case where we have somehow lost the
11827 version of our descriptor appearing in the consensus. Fixes part
11828 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
11829 as TROVE-2017-012 and CVE-2017-8822.
11831 o Minor features (bridge, backport from 0.3.1.9):
11832 - Bridges now include notice in their descriptors that they are
11833 bridges, and notice of their distribution status, based on their
11834 publication settings. Implements ticket 18329. For more fine-
11835 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11838 o Minor features (directory authority, backport from 0.3.2.6-alpha):
11839 - Add an IPv6 address for the "bastet" directory authority. Closes
11842 o Minor features (geoip):
11843 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11846 o Minor features (security, windows, backport from 0.3.1.1-alpha):
11847 - Enable a couple of pieces of Windows hardening: one
11848 (HeapEnableTerminationOnCorruption) that has been on-by-default
11849 since Windows 8, and unavailable before Windows 7; and one
11850 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
11851 affect us, but shouldn't do any harm. Closes ticket 21953.
11853 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
11854 - Avoid unnecessary calls to directory_fetches_from_authorities() on
11855 relays, to prevent spurious address resolutions and descriptor
11856 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
11857 bugfix on in 0.2.8.1-alpha.
11859 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
11860 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
11861 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
11863 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
11864 - When a circuit is marked for close, do not attempt to package any
11865 cells for channels on that circuit. Previously, we would detect
11866 this condition lower in the call stack, when we noticed that the
11867 circuit had no attached channel, and log an annoying message.
11868 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
11870 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
11871 - Avoid a crash when transitioning from client mode to bridge mode.
11872 Previously, we would launch the worker threads whenever our
11873 "public server" mode changed, but not when our "server" mode
11874 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
11876 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
11877 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
11878 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
11881 Changes in version 0.2.8.17 - 2017-12-01
11882 Tor 0.2.8.17 backports important security and stability bugfixes from
11883 later Tor releases. All Tor users should upgrade to this release, or
11884 to another of the releases coming out today.
11886 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
11887 2018. If you need a release with long-term support, please upgrade with
11888 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11890 o Major bugfixes (security, backport from 0.3.2.6-alpha):
11891 - Fix a denial of service bug where an attacker could use a
11892 malformed directory object to cause a Tor instance to pause while
11893 OpenSSL would try to read a passphrase from the terminal. (Tor
11894 instances run without a terminal, which is the case for most Tor
11895 packages, are not impacted.) Fixes bug 24246; bugfix on every
11896 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11897 Found by OSS-Fuzz as testcase 6360145429790720.
11898 - When checking for replays in the INTRODUCE1 cell data for a
11899 (legacy) onion service, correctly detect replays in the RSA-
11900 encrypted part of the cell. We were previously checking for
11901 replays on the entire cell, but those can be circumvented due to
11902 the malleability of Tor's legacy hybrid encryption. This fix helps
11903 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11904 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11907 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
11908 - Fix a use-after-free error that could crash v2 Tor onion services
11909 when they failed to open circuits while expiring introduction
11910 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
11911 also tracked as TROVE-2017-013 and CVE-2017-8823.
11913 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11914 - When running as a relay, make sure that we never build a path through
11915 ourselves, even in the case where we have somehow lost the version of
11916 our descriptor appearing in the consensus. Fixes part of bug 21534;
11917 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
11920 o Minor features (bridge, backport from 0.3.1.9):
11921 - Bridges now include notice in their descriptors that they are
11922 bridges, and notice of their distribution status, based on their
11923 publication settings. Implements ticket 18329. For more fine-
11924 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11927 o Minor features (directory authority, backport from 0.3.2.6-alpha):
11928 - Add an IPv6 address for the "bastet" directory authority. Closes
11931 o Minor features (geoip):
11932 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11935 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
11936 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
11937 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
11940 Changes in version 0.2.5.16 - 2017-12-01
11941 Tor 0.2.5.13 backports important security and stability bugfixes from
11942 later Tor releases. All Tor users should upgrade to this release, or
11943 to another of the releases coming out today.
11945 Note: the Tor 0.2.5 series will no longer be supported after 1 May
11946 2018. If you need a release with long-term support, please upgrade to
11947 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11949 o Major bugfixes (security, backport from 0.3.2.6-alpha):
11950 - Fix a denial of service bug where an attacker could use a
11951 malformed directory object to cause a Tor instance to pause while
11952 OpenSSL would try to read a passphrase from the terminal. (Tor
11953 instances run without a terminal, which is the case for most Tor
11954 packages, are not impacted.) Fixes bug 24246; bugfix on every
11955 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11956 Found by OSS-Fuzz as testcase 6360145429790720.
11957 - When checking for replays in the INTRODUCE1 cell data for a
11958 (legacy) onion service, correctly detect replays in the RSA-
11959 encrypted part of the cell. We were previously checking for
11960 replays on the entire cell, but those can be circumvented due to
11961 the malleability of Tor's legacy hybrid encryption. This fix helps
11962 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11963 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11966 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11967 - When running as a relay, make sure that we never build a path
11968 through ourselves, even in the case where we have somehow lost the
11969 version of our descriptor appearing in the consensus. Fixes part
11970 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
11971 as TROVE-2017-012 and CVE-2017-8822.
11973 o Minor features (bridge, backport from 0.3.1.9):
11974 - Bridges now include notice in their descriptors that they are
11975 bridges, and notice of their distribution status, based on their
11976 publication settings. Implements ticket 18329. For more fine-
11977 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11980 o Minor features (geoip):
11981 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11985 Changes in version 0.3.2.5-alpha - 2017-11-22
11986 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
11987 fixes several stability and reliability bugs, including a fix for
11988 intermittent bootstrapping failures that some people have been seeing
11989 since the 0.3.0.x series.
11991 Please test this alpha out -- many of these fixes will soon be
11992 backported to stable Tor versions if no additional bugs are found
11995 o Major bugfixes (bootstrapping):
11996 - Fetch descriptors aggressively whenever we lack enough to build
11997 circuits, regardless of how many descriptors we are missing.
11998 Previously, we would delay launching the fetch when we had fewer
11999 than 15 missing descriptors, even if some of those descriptors
12000 were blocking circuits from building. Fixes bug 23985; bugfix on
12001 0.1.1.11-alpha. The effects of this bug became worse in
12002 0.3.0.3-alpha, when we began treating missing descriptors from our
12003 primary guards as a reason to delay circuits.
12004 - Don't try fetching microdescriptors from relays that have failed
12005 to deliver them in the past. Fixes bug 23817; bugfix
12008 o Minor features (directory authority):
12009 - Make the "Exit" flag assignment only depend on whether the exit
12010 policy allows connections to ports 80 and 443. Previously relays
12011 would get the Exit flag if they allowed connections to one of
12012 these ports and also port 6667. Resolves ticket 23637.
12014 o Minor features (geoip):
12015 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
12018 o Minor features (linux seccomp2 sandbox):
12019 - Update the sandbox rules so that they should now work correctly
12020 with Glibc 2.26. Closes ticket 24315.
12022 o Minor features (logging):
12023 - Downgrade a pair of log messages that could occur when an exit's
12024 resolver gave us an unusual (but not forbidden) response. Closes
12026 - Improve the message we log when re-enabling circuit build timeouts
12027 after having received a consensus. Closes ticket 20963.
12029 o Minor bugfixes (compilation):
12030 - Fix a memory leak warning in one of the libevent-related
12031 configuration tests that could occur when manually specifying
12032 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
12033 Found and patched by Alex Xu.
12034 - When detecting OpenSSL on Windows from our configure script, make
12035 sure to try linking with the ws2_32 library. Fixes bug 23783;
12036 bugfix on 0.3.2.2-alpha.
12038 o Minor bugfixes (control port, linux seccomp2 sandbox):
12039 - Avoid a crash when attempting to use the seccomp2 sandbox together
12040 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
12043 o Minor bugfixes (control port, onion services):
12044 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
12045 HS_DESC event when a service is not able to upload a descriptor.
12046 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
12048 o Minor bugfixes (directory cache):
12049 - Recover better from empty or corrupt files in the consensus cache
12050 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
12051 - When a consensus diff calculation is only partially successful,
12052 only record the successful parts as having succeeded. Partial
12053 success can happen if (for example) one compression method fails
12054 but the others succeed. Previously we misrecorded all the
12055 calculations as having succeeded, which would later cause a
12056 nonfatal assertion failure. Fixes bug 24086; bugfix
12059 o Minor bugfixes (logging):
12060 - Only log once if we notice that KIST support is gone. Fixes bug
12061 24158; bugfix on 0.3.2.1-alpha.
12062 - Suppress a log notice when relay descriptors arrive. We already
12063 have a bootstrap progress for this so no need to log notice
12064 everytime tor receives relay descriptors. Microdescriptors behave
12065 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
12067 o Minor bugfixes (network layer):
12068 - When closing a connection via close_connection_immediately(), we
12069 mark it as "not blocked on bandwidth", to prevent later calls from
12070 trying to unblock it, and give it permission to read. This fixes a
12071 backtrace warning that can happen on relays under various
12072 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
12074 o Minor bugfixes (onion services):
12075 - The introduction circuit was being timed out too quickly while
12076 waiting for the rendezvous circuit to complete. Keep the intro
12077 circuit around longer instead of timing out and reopening new ones
12078 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
12079 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
12080 so it matches dir-spec.txt. Fixes bug 24262; bugfix
12082 - Silence a warning about failed v3 onion descriptor uploads that
12083 can happen naturally under certain edge cases. Fixes part of bug
12084 23662; bugfix on 0.3.2.1-alpha.
12086 o Minor bugfixes (tests):
12087 - Fix a memory leak in one of the bridge-distribution test cases.
12088 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
12089 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
12090 to correctly handle cases where a caller gives it an RSA key of
12091 under 160 bits. (This is not actually a bug in Tor itself, but
12092 rather in our fuzzing code.) Fixes bug 24247; bugfix on
12093 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
12096 - Add notes in man page regarding OS support for the various
12097 scheduler types. Attempt to use less jargon in the scheduler
12098 section. Closes ticket 24254.
12101 Changes in version 0.3.2.4-alpha - 2017-11-08
12102 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
12103 It fixes several stability and reliability bugs, especially including
12104 a major reliability issue that has been plaguing fast exit relays in
12107 o Major bugfixes (exit relays, DNS):
12108 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
12109 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
12110 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
12111 identifying and finding a workaround to this bug and to Moritz,
12112 Arthur Edelstein, and Roger for helping to track it down and
12115 o Major bugfixes (scheduler, channel):
12116 - Stop processing scheduled channels if they closed while flushing
12117 cells. This can happen if the write on the connection fails
12118 leading to the channel being closed while in the scheduler loop.
12119 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
12121 o Minor features (logging, scheduler):
12122 - Introduce a SCHED_BUG() function to log extra information about
12123 the scheduler state if we ever catch a bug in the scheduler.
12124 Closes ticket 23753.
12126 o Minor features (removed deprecations):
12127 - The ClientDNSRejectInternalAddresses flag can once again be set in
12128 non-testing Tor networks, so long as they do not use the default
12129 directory authorities. This change also removes the deprecation of
12130 this flag from 0.2.9.2-alpha. Closes ticket 21031.
12132 o Minor features (testing):
12133 - Our fuzzing tests now test the encrypted portions of v3 onion
12134 service descriptors. Implements more of 21509.
12136 o Minor bugfixes (directory client):
12137 - On failure to download directory information, delay retry attempts
12138 by a random amount based on the "decorrelated jitter" algorithm.
12139 Our previous delay algorithm tended to produce extra-long delays
12140 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
12142 o Minor bugfixes (IPv6, v3 single onion services):
12143 - Remove buggy code for IPv6-only v3 single onion services, and
12144 reject attempts to configure them. This release supports IPv4,
12145 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
12146 stack v3 single onion services. Fixes bug 23820; bugfix
12149 o Minor bugfixes (logging, relay):
12150 - Give only a protocol warning when the ed25519 key is not
12151 consistent between the descriptor and microdescriptor of a relay.
12152 This can happen, for instance, if the relay has been flagged
12153 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
12155 o Minor bugfixes (manpage, onion service):
12156 - Document that the HiddenServiceNumIntroductionPoints option is
12157 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
12158 bugfix on 0.3.2.1-alpha.
12160 o Minor bugfixes (memory leaks):
12161 - Fix a minor memory leak at exit in the KIST scheduler. This bug
12162 should have no user-visible impact. Fixes bug 23774; bugfix
12164 - Fix a memory leak when decrypting a badly formatted v3 onion
12165 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
12166 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
12168 o Minor bugfixes (onion services):
12169 - Cache some needed onion service client information instead of
12170 constantly computing it over and over again. Fixes bug 23623;
12171 bugfix on 0.3.2.1-alpha.
12172 - Properly retry HSv3 descriptor fetches when missing required
12173 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
12175 o Minor bugfixes (path selection):
12176 - When selecting relays by bandwidth, avoid a rounding error that
12177 could sometimes cause load to be imbalanced incorrectly.
12178 Previously, we would always round upwards; now, we round towards
12179 the nearest integer. This had the biggest effect when a relay's
12180 weight adjustments should have given it weight 0, but it got
12181 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
12182 - When calculating the fraction of nodes that have descriptors, and
12183 all nodes in the network have zero bandwidths, count the number of
12184 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
12185 - Actually log the total bandwidth in compute_weighted_bandwidths().
12186 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
12188 o Minor bugfixes (relay, crash):
12189 - Avoid a crash when transitioning from client mode to bridge mode.
12190 Previously, we would launch the worker threads whenever our
12191 "public server" mode changed, but not when our "server" mode
12192 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
12194 o Minor bugfixes (testing):
12195 - Fix a spurious fuzzing-only use of an uninitialized value. Found
12196 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
12197 - Test that IPv6-only clients can use microdescriptors when running
12198 "make test-network-all". Requires chutney master 61c28b9 or later.
12199 Closes ticket 24109.
12202 Changes in version 0.3.2.3-alpha - 2017-10-27
12203 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
12204 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
12205 directory authority, Bastet.
12207 o Directory authority changes:
12208 - Add "Bastet" as a ninth directory authority to the default list.
12209 Closes ticket 23910.
12210 - The directory authority "Longclaw" has changed its IP address.
12211 Closes ticket 23592.
12213 o Minor features (bridge):
12214 - Bridge relays can now set the BridgeDistribution config option to
12215 add a "bridge-distribution-request" line to their bridge
12216 descriptor, which tells BridgeDB how they'd like their bridge
12217 address to be given out. (Note that as of Oct 2017, BridgeDB does
12218 not yet implement this feature.) As a side benefit, this feature
12219 provides a way to distinguish bridge descriptors from non-bridge
12220 descriptors. Implements tickets 18329.
12222 o Minor features (client, entry guards):
12223 - Improve log messages when missing descriptors for primary guards.
12224 Resolves ticket 23670.
12226 o Minor features (geoip):
12227 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
12230 o Minor bugfixes (bridge):
12231 - Overwrite the bridge address earlier in the process of retrieving
12232 its descriptor, to make sure we reach it on the configured
12233 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
12235 o Minor bugfixes (documentation):
12236 - Document better how to read gcov, and what our gcov postprocessing
12237 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
12239 o Minor bugfixes (entry guards):
12240 - Tor now updates its guard state when it reads a consensus
12241 regardless of whether it's missing descriptors. That makes tor use
12242 its primary guards to fetch descriptors in some edge cases where
12243 it would previously have used fallback directories. Fixes bug
12244 23862; bugfix on 0.3.0.1-alpha.
12246 o Minor bugfixes (hidden service client):
12247 - When handling multiple SOCKS request for the same .onion address,
12248 only fetch the service descriptor once.
12249 - When a descriptor fetch fails with a non-recoverable error, close
12250 all pending SOCKS requests for that .onion. Fixes bug 23653;
12251 bugfix on 0.3.2.1-alpha.
12253 o Minor bugfixes (hidden service):
12254 - Always regenerate missing hidden service public key files. Prior
12255 to this, if the public key was deleted from disk, it wouldn't get
12256 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
12258 - Make sure that we have a usable ed25519 key when the intro point
12259 relay supports ed25519 link authentication. Fixes bug 24002;
12260 bugfix on 0.3.2.1-alpha.
12262 o Minor bugfixes (hidden service, v2):
12263 - When reloading configured hidden services, copy all information
12264 from the old service object. Previously, some data was omitted,
12265 causing delays in descriptor upload, and other bugs. Fixes bug
12266 23790; bugfix on 0.2.1.9-alpha.
12268 o Minor bugfixes (memory safety, defensive programming):
12269 - Clear the target address when node_get_prim_orport() returns
12270 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
12272 o Minor bugfixes (relay):
12273 - Avoid a BUG warning when receiving a dubious CREATE cell while an
12274 option transition is in progress. Fixes bug 23952; bugfix
12277 o Minor bugfixes (testing):
12278 - Adjust the GitLab CI configuration to more closely match that of
12279 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
12280 - Prevent scripts/test/coverage from attempting to move gcov output
12281 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
12282 - When running unit tests as root, skip a test that would fail
12283 because it expects a permissions error. This affects some
12284 continuous integration setups. Fixes bug 23758; bugfix
12286 - Stop unconditionally mirroring the tor repository in GitLab CI.
12287 This prevented developers from enabling GitLab CI on master. Fixes
12288 bug 23755; bugfix on 0.3.2.2-alpha.
12289 - Fix the hidden service v3 descriptor decoding fuzzing to use the
12290 latest decoding API correctly. Fixes bug 21509; bugfix
12293 o Minor bugfixes (warnings):
12294 - When we get an HTTP request on a SOCKS port, tell the user about
12295 the new HTTPTunnelPort option. Previously, we would give a "Tor is
12296 not an HTTP Proxy" message, which stopped being true when
12297 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
12301 Changes in version 0.2.5.15 - 2017-10-25
12302 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
12303 series. It also adds a new directory authority, Bastet.
12305 Note: the Tor 0.2.5 series will no longer be supported after 1 May
12306 2018. If you need a release with long-term support, please upgrade to
12307 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
12309 o Directory authority changes:
12310 - Add "Bastet" as a ninth directory authority to the default list.
12311 Closes ticket 23910.
12312 - The directory authority "Longclaw" has changed its IP address.
12313 Closes ticket 23592.
12315 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
12316 - Avoid an assertion failure bug affecting our implementation of
12317 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
12318 handling of "0xx" differs from what we had expected. Fixes bug
12319 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
12321 o Minor features (geoip):
12322 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
12325 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
12326 - Fix a memset() off the end of an array when packing cells. This
12327 bug should be harmless in practice, since the corrupted bytes are
12328 still in the same structure, and are always padding bytes,
12329 ignored, or immediately overwritten, depending on compiler
12330 behavior. Nevertheless, because the memset()'s purpose is to make
12331 sure that any other cell-handling bugs can't expose bytes to the
12332 network, we need to fix it. Fixes bug 22737; bugfix on
12333 0.2.4.11-alpha. Fixes CID 1401591.
12335 o Build features (backport from 0.3.1.5-alpha):
12336 - Tor's repository now includes a Travis Continuous Integration (CI)
12337 configuration file (.travis.yml). This is meant to help new
12338 developers and contributors who fork Tor to a Github repository be
12339 better able to test their changes, and understand what we expect
12340 to pass. To use this new build feature, you must fork Tor to your
12341 Github account, then go into the "Integrations" menu in the
12342 repository settings for your fork and enable Travis, then push
12343 your changes. Closes ticket 22636.
12346 Changes in version 0.2.8.16 - 2017-10-25
12347 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
12348 series, including a bugfix for a crash issue that had affected relays
12349 under memory pressure. It also adds a new directory authority, Bastet.
12351 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
12352 2018. If you need a release with long-term support, please stick with
12353 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
12355 o Directory authority changes:
12356 - Add "Bastet" as a ninth directory authority to the default list.
12357 Closes ticket 23910.
12358 - The directory authority "Longclaw" has changed its IP address.
12359 Closes ticket 23592.
12361 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
12362 - Fix a timing-based assertion failure that could occur when the
12363 circuit out-of-memory handler freed a connection's output buffer.
12364 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
12366 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
12367 - Remove longclaw's IPv6 address, as it will soon change. Authority
12368 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
12369 3/8 directory authorities with IPv6 addresses, but there are also
12370 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
12372 o Minor features (geoip):
12373 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
12377 Changes in version 0.2.9.13 - 2017-10-25
12378 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
12379 series, including a bugfix for a crash issue that had affected relays
12380 under memory pressure. It also adds a new directory authority, Bastet.
12382 o Directory authority changes:
12383 - Add "Bastet" as a ninth directory authority to the default list.
12384 Closes ticket 23910.
12385 - The directory authority "Longclaw" has changed its IP address.
12386 Closes ticket 23592.
12388 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
12389 - Fix a timing-based assertion failure that could occur when the
12390 circuit out-of-memory handler freed a connection's output buffer.
12391 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
12393 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
12394 - Remove longclaw's IPv6 address, as it will soon change. Authority
12395 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
12396 3/8 directory authorities with IPv6 addresses, but there are also
12397 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
12399 o Minor features (geoip):
12400 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
12403 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
12404 - When a directory authority rejects a descriptor or extrainfo with
12405 a given digest, mark that digest as undownloadable, so that we do
12406 not attempt to download it again over and over. We previously
12407 tried to avoid downloading such descriptors by other means, but we
12408 didn't notice if we accidentally downloaded one anyway. This
12409 behavior became problematic in 0.2.7.2-alpha, when authorities
12410 began pinning Ed25519 keys. Fixes bug 22349; bugfix
12413 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
12414 - Clear the address when node_get_prim_orport() returns early.
12415 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
12417 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
12418 - When running as a Windows service, set the ID of the main thread
12419 correctly. Failure to do so made us fail to send log messages to
12420 the controller in 0.2.1.16-rc, slowed down controller event
12421 delivery in 0.2.7.3-rc and later, and crash with an assertion
12422 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
12423 Patch and diagnosis from "Vort".
12426 Changes in version 0.3.0.12 - 2017-10-25
12427 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
12428 series, including a bugfix for a crash issue that had affected relays
12429 under memory pressure. It also adds a new directory authority, Bastet.
12431 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
12432 2018. If you need a release with long-term support, please stick with
12433 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
12435 o Directory authority changes:
12436 - Add "Bastet" as a ninth directory authority to the default list.
12437 Closes ticket 23910.
12438 - The directory authority "Longclaw" has changed its IP address.
12439 Closes ticket 23592.
12441 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
12442 - Fix a timing-based assertion failure that could occur when the
12443 circuit out-of-memory handler freed a connection's output buffer.
12444 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
12446 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
12447 - Remove longclaw's IPv6 address, as it will soon change. Authority
12448 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
12449 3/8 directory authorities with IPv6 addresses, but there are also
12450 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
12452 o Minor features (geoip):
12453 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
12456 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
12457 - When a directory authority rejects a descriptor or extrainfo with
12458 a given digest, mark that digest as undownloadable, so that we do
12459 not attempt to download it again over and over. We previously
12460 tried to avoid downloading such descriptors by other means, but we
12461 didn't notice if we accidentally downloaded one anyway. This
12462 behavior became problematic in 0.2.7.2-alpha, when authorities
12463 began pinning Ed25519 keys. Fixes bug 22349; bugfix
12466 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
12467 - Avoid a possible double close of a circuit by the intro point on
12468 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
12469 bugfix on 0.3.0.1-alpha.
12471 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
12472 - Clear the address when node_get_prim_orport() returns early.
12473 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
12475 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
12476 - When running as a Windows service, set the ID of the main thread
12477 correctly. Failure to do so made us fail to send log messages to
12478 the controller in 0.2.1.16-rc, slowed down controller event
12479 delivery in 0.2.7.3-rc and later, and crash with an assertion
12480 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
12481 Patch and diagnosis from "Vort".
12484 Changes in version 0.3.1.8 - 2017-10-25
12485 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
12486 It includes several bugfixes, including a bugfix for a crash issue
12487 that had affected relays under memory pressure. It also adds
12488 a new directory authority, Bastet.
12490 o Directory authority changes:
12491 - Add "Bastet" as a ninth directory authority to the default list.
12492 Closes ticket 23910.
12493 - The directory authority "Longclaw" has changed its IP address.
12494 Closes ticket 23592.
12496 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
12497 - Fix a timing-based assertion failure that could occur when the
12498 circuit out-of-memory handler freed a connection's output buffer.
12499 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
12501 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
12502 - Remove longclaw's IPv6 address, as it will soon change. Authority
12503 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
12504 3/8 directory authorities with IPv6 addresses, but there are also
12505 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
12507 o Minor features (geoip):
12508 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
12511 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
12512 - Fix a compilation warning when building with zstd support on
12513 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
12514 and fixed by Andreas Stieger.
12516 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
12517 - Handle a pathological case when decompressing Zstandard data when
12518 the output buffer size is zero. Fixes bug 23551; bugfix
12521 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
12522 - Remove the length limit on HTTP status lines that authorities can
12523 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
12525 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
12526 - Avoid a possible double close of a circuit by the intro point on
12527 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
12528 bugfix on 0.3.0.1-alpha.
12530 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
12531 - Clear the address when node_get_prim_orport() returns early.
12532 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
12534 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
12535 - Fix additional channelpadding unit test failures by using mocked
12536 time instead of actual time for all tests. Fixes bug 23608; bugfix
12540 Changes in version 0.3.2.2-alpha - 2017-09-29
12541 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
12542 release fixes several minor bugs in the new scheduler and next-
12543 generation onion services; both features were newly added in the 0.3.2
12544 series. Other fixes in this alpha include several fixes for non-fatal
12545 tracebacks which would appear in logs.
12547 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
12548 alpha does not contain any substantial new features. Minor features
12549 include better testing and logging.
12551 The following comprises the complete list of changes included
12554 o Major bugfixes (relay, crash, assertion failure):
12555 - Fix a timing-based assertion failure that could occur when the
12556 circuit out-of-memory handler freed a connection's output buffer.
12557 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
12559 o Major bugfixes (scheduler):
12560 - If a channel is put into the scheduler's pending list, then it
12561 starts closing, and then if the scheduler runs before it finishes
12562 closing, the scheduler will get stuck trying to flush its cells
12563 while the lower layers refuse to cooperate. Fix that race
12564 condition by giving the scheduler an escape method. Fixes bug
12565 23676; bugfix on 0.3.2.1-alpha.
12567 o Minor features (build, compilation):
12568 - The "check-changes" feature is now part of the "make check" tests;
12569 we'll use it to try to prevent misformed changes files from
12570 accumulating. Closes ticket 23564.
12571 - Tor builds should now fail if there are any mismatches between the
12572 C type representing a configuration variable and the C type the
12573 data-driven parser uses to store a value there. Previously, we
12574 needed to check these by hand, which sometimes led to mistakes.
12575 Closes ticket 23643.
12577 o Minor features (directory authorities):
12578 - Remove longclaw's IPv6 address, as it will soon change. Authority
12579 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
12580 3/8 directory authorities with IPv6 addresses, but there are also
12581 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
12583 o Minor features (hidden service, circuit, logging):
12584 - Improve logging of many callsite in the circuit subsystem to print
12585 the circuit identifier(s).
12586 - Log when we cleanup an intro point from a service so we know when
12587 and for what reason it happened. Closes ticket 23604.
12589 o Minor features (logging):
12590 - Log more circuit information whenever we are about to try to
12591 package a relay cell on a circuit with a nonexistent n_chan.
12592 Attempt to diagnose ticket 8185.
12593 - Improve info-level log identification of particular circuits, to
12594 help with debugging. Closes ticket 23645.
12596 o Minor features (relay):
12597 - When choosing which circuits can be expired as unused, consider
12598 circuits from clients even if those clients used regular CREATE
12599 cells to make them; and do not consider circuits from relays even
12600 if they were made with CREATE_FAST. Part of ticket 22805.
12602 o Minor features (robustness):
12603 - Change several fatal assertions when flushing buffers into non-
12604 fatal assertions, to prevent any recurrence of 23690.
12606 o Minor features (spec conformance, bridge, diagnostic):
12607 - When handling the USERADDR command on an ExtOrPort, warn when the
12608 transports provides a USERADDR with no port. In a future version,
12609 USERADDR commands of this format may be rejected. Detects problems
12610 related to ticket 23080.
12612 o Minor features (testing):
12613 - Add a unit test to make sure that our own generated platform
12614 string will be accepted by directory authorities. Closes
12617 o Minor bugfixes (bootstrapping):
12618 - When warning about state file clock skew, report the correct
12619 direction for the detected skew. Fixes bug 23606; bugfix
12621 - Avoid an assertion failure when logging a state file clock skew
12622 very early in bootstrapping. Fixes bug 23607; bugfix
12625 o Minor bugfixes (build, compilation):
12626 - Fix a compilation warning when building with zstd support on
12627 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
12628 and fixed by Andreas Stieger.
12629 - When searching for OpenSSL, don't accept any OpenSSL library that
12630 lacks TLSv1_1_method(): Tor doesn't build with those versions.
12631 Additionally, look in /usr/local/opt/openssl, if it's present.
12632 These changes together repair the default build on OSX systems
12633 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
12635 o Minor bugfixes (compression):
12636 - Handle a pathological case when decompressing Zstandard data when
12637 the output buffer size is zero. Fixes bug 23551; bugfix
12640 o Minor bugfixes (documentation):
12641 - Fix manpage to not refer to the obsolete (and misspelled)
12642 UseEntryGuardsAsDirectoryGuards parameter in the description of
12643 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
12645 o Minor bugfixes (hidden service v3):
12646 - Don't log an assertion failure when we can't find the right
12647 information to extend to an introduction point. In rare cases,
12648 this could happen, causing a warning, even though tor would
12649 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
12650 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
12651 much bigger so the rendezvous point can't distinguish which hidden
12652 service protocol is being used. Fixes bug 23420; bugfix
12655 o Minor bugfixes (hidden service, relay):
12656 - Avoid a possible double close of a circuit by the intro point on
12657 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
12658 bugfix on 0.3.0.1-alpha.
12660 o Minor bugfixes (logging, relay shutdown, annoyance):
12661 - When a circuit is marked for close, do not attempt to package any
12662 cells for channels on that circuit. Previously, we would detect
12663 this condition lower in the call stack, when we noticed that the
12664 circuit had no attached channel, and log an annoying message.
12665 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
12667 o Minor bugfixes (scheduler):
12668 - When switching schedulers due to a consensus change, we didn't
12669 give the new scheduler a chance to react to the consensus. Fix
12670 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
12671 - Make the KISTSchedRunInterval option a non negative value. With
12672 this, the way to disable KIST through the consensus is to set it
12673 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
12674 - Only notice log the selected scheduler when we switch scheduler
12675 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
12676 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
12677 by a different tv_usec data type. Fixes bug 23575; bugfix
12679 - Make a hard exit if tor is unable to pick a scheduler which can
12680 happen if the user specifies a scheduler type that is not
12681 supported and not other types in Schedulers. Fixes bug 23581;
12682 bugfix on 0.3.2.1-alpha.
12683 - Properly initialize the scheduler last run time counter so it is
12684 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
12686 o Minor bugfixes (testing):
12687 - Capture and detect several "Result does not fit" warnings in unit
12688 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
12690 - Fix additional channelpadding unit test failures by using mocked
12691 time instead of actual time for all tests. Fixes bug 23608; bugfix
12693 - The removal of some old scheduler options caused some tests to
12694 fail on BSD systems. Assume current behavior is correct and make
12695 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
12697 o Code simplification and refactoring:
12698 - Remove various ways of testing circuits and connections for
12699 "clientness"; instead, favor channel_is_client(). Part of
12702 o Deprecated features:
12703 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
12704 now deprecated; they do not apply to relays, and they have had no
12705 effect on clients since 0.2.8.x. Closes ticket 19704.
12708 - HiddenServiceVersion man page entry wasn't mentioning the now
12709 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
12710 - Clarify that the Address option is entirely about setting an
12711 advertised IPv4 address. Closes ticket 18891.
12712 - Clarify the manpage's use of the term "address" to clarify what
12713 kind of address is intended. Closes ticket 21405.
12714 - Document that onion service subdomains are allowed, and ignored.
12715 Closes ticket 18736.
12718 Changes in version 0.3.2.1-alpha - 2017-09-18
12719 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
12720 includes support for our next-generation ("v3") onion service
12721 protocol, and adds a new circuit scheduler for more responsive
12722 forwarding decisions from relays. There are also numerous other small
12723 features and bugfixes here.
12725 Below are the changes since Tor 0.3.1.7.
12727 o Major feature (scheduler, channel):
12728 - Tor now uses new schedulers to decide which circuits should
12729 deliver cells first, in order to improve congestion at relays. The
12730 first type is called "KIST" ("Kernel Informed Socket Transport"),
12731 and is only available on Linux-like systems: it uses feedback from
12732 the kernel to prevent the kernel's TCP buffers from growing too
12733 full. The second new scheduler type is called "KISTLite": it
12734 behaves the same as KIST, but runs on systems without kernel
12735 support for inspecting TCP implementation details. The old
12736 scheduler is still available, under the name "Vanilla". To change
12737 the default scheduler preference order, use the new "Schedulers"
12738 option. (The default preference order is "KIST,KISTLite,Vanilla".)
12740 Matt Traudt implemented KIST, based on research by Rob Jansen,
12741 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
12742 more information, see the design paper at
12743 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
12744 followup implementation paper at https://arxiv.org/abs/1709.01044.
12745 Closes ticket 12541.
12747 o Major features (next-generation onion services):
12748 - Tor now supports the next-generation onion services protocol for
12749 clients and services! As part of this release, the core of
12750 proposal 224 has been implemented and is available for
12751 experimentation and testing by our users. This newer version of
12752 onion services ("v3") features many improvements over the legacy
12755 a) Better crypto (replaced SHA1/DH/RSA1024
12756 with SHA3/ed25519/curve25519)
12758 b) Improved directory protocol, leaking much less information to
12761 c) Improved directory protocol, with smaller surface for
12764 d) Better onion address security against impersonation.
12766 e) More extensible introduction/rendezvous protocol.
12768 f) A cleaner and more modular codebase.
12770 You can identify a next-generation onion address by its length:
12771 they are 56 characters long, as in
12772 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
12774 In the future, we will release more options and features for v3
12775 onion services, but we first need a testing period, so that the
12776 current codebase matures and becomes more robust. Planned features
12777 include: offline keys, advanced client authorization, improved
12778 guard algorithms, and statistics. For full details, see
12781 Legacy ("v2") onion services will still work for the foreseeable
12782 future, and will remain the default until this new codebase gets
12783 tested and hardened. Service operators who want to experiment with
12784 the new system can use the 'HiddenServiceVersion 3' torrc
12785 directive along with the regular onion service configuration
12786 options. We will publish a blog post about this new feature
12789 o Major bugfixes (usability, control port):
12790 - Report trusted clock skew indications as bootstrap errors, so
12791 controllers can more easily alert users when their clocks are
12792 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
12794 o Minor features (bug detection):
12795 - Log a warning message with a stack trace for any attempt to call
12796 get_options() during option validation. This pattern has caused
12797 subtle bugs in the past. Closes ticket 22281.
12799 o Minor features (client):
12800 - You can now use Tor as a tunneled HTTP proxy: use the new
12801 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
12802 requests. Closes ticket 22407.
12803 - Add an extra check to make sure that we always use the newer guard
12804 selection code for picking our guards. Closes ticket 22779.
12805 - When downloading (micro)descriptors, don't split the list into
12806 multiple requests unless we want at least 32 descriptors.
12807 Previously, we split at 4, not 32, which led to significant
12808 overhead in HTTP request size and degradation in compression
12809 performance. Closes ticket 23220.
12811 o Minor features (command line):
12812 - Add a new commandline option, --key-expiration, which prints when
12813 the current signing key is going to expire. Implements ticket
12814 17639; patch by Isis Lovecruft.
12816 o Minor features (control port):
12817 - If an application tries to use the control port as an HTTP proxy,
12818 respond with a meaningful "This is the Tor control port" message,
12819 and log the event. Closes ticket 1667. Patch from Ravi
12821 - Provide better error message for GETINFO desc/(id|name) when not
12822 fetching router descriptors. Closes ticket 5847. Patch by
12824 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
12825 whether Tor will try to download router descriptors and
12826 microdescriptors respectively. Closes ticket 22684.
12827 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
12828 so controllers can tell whether the geoip databases are loaded.
12829 Closes ticket 23237.
12830 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
12831 events. Closes ticket 19254. Patch by "DonnchaC".
12833 o Minor features (development support):
12834 - Developers can now generate a call-graph for Tor using the
12835 "calltool" python program, which post-processes object dumps. It
12836 should work okay on many Linux and OSX platforms, and might work
12837 elsewhere too. To run it, install calltool from
12838 https://gitweb.torproject.org/user/nickm/calltool.git and run
12839 "make callgraph". Closes ticket 19307.
12841 o Minor features (ed25519):
12842 - Add validation function to checks for torsion components in
12843 ed25519 public keys, used by prop224 client-side code. Closes
12844 ticket 22006. Math help by Ian Goldberg.
12846 o Minor features (exit relay, DNS):
12847 - Improve the clarity and safety of the log message from evdns when
12848 receiving an apparently spoofed DNS reply. Closes ticket 3056.
12850 o Minor features (integration, hardening):
12851 - Add a new NoExec option to prevent Tor from running other
12852 programs. When this option is set to 1, Tor will never try to run
12853 another program, regardless of the settings of
12854 PortForwardingHelper, ClientTransportPlugin, or
12855 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
12856 without restarting Tor. Closes ticket 22976.
12858 o Minor features (logging):
12859 - Improve the warning message for specifying a relay by nickname.
12860 The previous message implied that nickname registration was still
12861 part of the Tor network design, which it isn't. Closes
12863 - If the sandbox filter fails to load, suggest to the user that
12864 their kernel might not support seccomp2. Closes ticket 23090.
12866 o Minor features (portability):
12867 - Check at configure time whether uint8_t is the same type as
12868 unsigned char. Lots of existing code already makes this
12869 assumption, and there could be strict aliasing issues if the
12870 assumption is violated. Closes ticket 22410.
12872 o Minor features (relay, configuration):
12873 - Reject attempts to use relative file paths when RunAsDaemon is
12874 set. Previously, Tor would accept these, but the directory-
12875 changing step of RunAsDaemon would give strange and/or confusing
12876 results. Closes ticket 22731.
12878 o Minor features (startup, safety):
12879 - When configured to write a PID file, Tor now exits if it is unable
12880 to do so. Previously, it would warn and continue. Closes
12883 o Minor features (static analysis):
12884 - The BUG() macro has been changed slightly so that Coverity no
12885 longer complains about dead code if the bug is impossible. Closes
12888 o Minor features (testing):
12889 - The default chutney network tests now include tests for the v3
12890 hidden service design. Make sure you have the latest version of
12891 chutney if you want to run these. Closes ticket 22437.
12892 - Add a unit test to verify that we can parse a hardcoded v2 hidden
12893 service descriptor. Closes ticket 15554.
12895 o Minor bugfixes (certificate handling):
12896 - Fix a time handling bug in Tor certificates set to expire after
12897 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
12898 Coverity as CID 1415728.
12900 o Minor bugfixes (client, usability):
12901 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
12902 SOCKS4a requests that contain IP address strings, even when
12903 SafeSocks in enabled, as this prevents user from connecting to
12904 known IP addresses without relying on DNS for resolving. SafeSocks
12905 still rejects SOCKS connections that connect to IP addresses when
12906 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
12907 bugfix on Tor 0.2.6.2-alpha.
12909 o Minor bugfixes (code correctness):
12910 - Call htons() in extend_cell_format() for encoding a 16-bit value.
12911 Previously we used ntohs(), which happens to behave the same on
12912 all the platforms we support, but which isn't really correct.
12913 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
12914 - For defense-in-depth, make the controller's write_escaped_data()
12915 function robust to extremely long inputs. Fixes bug 19281; bugfix
12916 on 0.1.1.1-alpha. Reported by Guido Vranken.
12918 o Minor bugfixes (compilation):
12919 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
12920 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
12922 o Minor bugfixes (consensus expiry):
12923 - Check for adequate directory information correctly. Previously, Tor
12924 would reconsider whether it had sufficient directory information
12925 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
12927 o Minor bugfixes (directory protocol):
12928 - Directory servers now include a "Date:" http header for response
12929 codes other than 200. Clients starting with a skewed clock and a
12930 recent consensus were getting "304 Not modified" responses from
12931 directory authorities, so without the Date header, the client
12932 would never hear about a wrong clock. Fixes bug 23499; bugfix
12934 - Make clients wait for 6 seconds before trying to download a
12935 consensus from an authority. Fixes bug 17750; bugfix
12938 o Minor bugfixes (DoS-resistance):
12939 - If future code asks if there are any running bridges, without
12940 checking if bridges are enabled, log a BUG warning rather than
12941 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
12943 o Minor bugfixes (format strictness):
12944 - Restrict several data formats to decimal. Previously, the
12945 BuildTimeHistogram entries in the state file, the "bw=" entries in
12946 the bandwidth authority file, and the process IDs passed to the
12947 __OwningControllerProcess option could all be specified in hex or
12948 octal as well as in decimal. This was not an intentional feature.
12949 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
12952 o Minor bugfixes (heartbeat):
12953 - If we fail to write a heartbeat message, schedule a retry for the
12954 minimum heartbeat interval number of seconds in the future. Fixes
12955 bug 19476; bugfix on 0.2.3.1-alpha.
12957 o Minor bugfixes (linux seccomp2 sandbox, logging):
12958 - Fix some messages on unexpected errors from the seccomp2 library.
12959 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
12961 o Minor bugfixes (logging):
12962 - Remove duplicate log messages regarding opening non-local
12963 SocksPorts upon parsing config and opening listeners at startup.
12964 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
12965 - Use a more comprehensible log message when telling the user
12966 they've excluded every running exit node. Fixes bug 7890; bugfix
12968 - When logging the number of descriptors we intend to download per
12969 directory request, do not log a number higher than then the number
12970 of descriptors we're fetching in total. Fixes bug 19648; bugfix
12972 - When warning about a directory owned by the wrong user, log the
12973 actual name of the user owning the directory. Previously, we'd log
12974 the name of the process owner twice. Fixes bug 23487; bugfix
12976 - The tor specification says hop counts are 1-based, so fix two log
12977 messages that mistakenly logged 0-based hop counts. Fixes bug
12978 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
12979 Credit to Xiaofan Li for reporting this issue.
12981 o Minor bugfixes (portability):
12982 - Stop using the PATH_MAX variable, which is not defined on GNU
12983 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
12985 o Minor bugfixes (relay):
12986 - When uploading our descriptor for the first time after startup,
12987 report the reason for uploading as "Tor just started" rather than
12988 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
12989 - Avoid unnecessary calls to directory_fetches_from_authorities() on
12990 relays, to prevent spurious address resolutions and descriptor
12991 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
12992 bugfix on in 0.2.8.1-alpha.
12994 o Minor bugfixes (tests):
12995 - Fix a broken unit test for the OutboundAddress option: the parsing
12996 function was never returning an error on failure. Fixes bug 23366;
12997 bugfix on 0.3.0.3-alpha.
12998 - Fix a signed-integer overflow in the unit tests for
12999 dir/download_status_random_backoff, which was untriggered until we
13000 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
13002 o Minor bugfixes (usability, control port):
13003 - Stop making an unnecessary routerlist check in NETINFO clock skew
13004 detection; this was preventing clients from reporting NETINFO clock
13005 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
13007 o Code simplification and refactoring:
13008 - Extract the code for handling newly-open channels into a separate
13009 function from the general code to handle channel state
13010 transitions. This change simplifies our callgraph, reducing the
13011 size of the largest strongly connected component by roughly a
13012 factor of two. Closes ticket 22608.
13013 - Remove dead code for largely unused statistics on the number of
13014 times we've attempted various public key operations. Fixes bug
13015 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
13016 - Remove several now-obsolete functions for asking about old
13017 variants directory authority status. Closes ticket 22311; patch
13019 - Remove some of the code that once supported "Named" and "Unnamed"
13020 routers. Authorities no longer vote for these flags. Closes
13022 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
13023 and old hidden services, to indicate that they aren't suitable for
13024 new protocols or formats. Closes ticket 23026.
13025 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
13026 22521. Patch from Neel Chauhan.
13027 - Split the enormous circuit_send_next_onion_skin() function into
13028 multiple subfunctions. Closes ticket 22804.
13029 - Split the portions of the buffer.c module that handle particular
13030 protocols into separate modules. Part of ticket 23149.
13031 - Use our test macros more consistently, to produce more useful
13032 error messages when our unit tests fail. Add coccinelle patches to
13033 allow us to re-check for test macro uses. Closes ticket 22497.
13035 o Deprecated features:
13036 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
13037 only applies to direct unencrypted HTTP connections to your
13038 directory server, which your Tor probably isn't using. Closes
13042 - Clarify in the manual that "Sandbox 1" is only supported on Linux
13043 kernels. Closes ticket 22677.
13044 - Document all values of PublishServerDescriptor in the manpage.
13045 Closes ticket 15645.
13046 - Improve the documentation for the directory port part of the
13047 DirAuthority line. Closes ticket 20152.
13048 - Restore documentation for the authorities' "approved-routers"
13049 file. Closes ticket 21148.
13051 o Removed features:
13052 - The AllowDotExit option has been removed as unsafe. It has been
13053 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
13054 - The ClientDNSRejectInternalAddresses flag can no longer be set on
13055 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
13056 Closes ticket 21031.
13057 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
13058 nobody was using it any longer. Closes ticket 22377.
13061 Changes in version 0.2.8.15 - 2017-09-18
13062 Tor 0.2.8.15 backports a collection of bugfixes from later
13065 Most significantly, it includes a fix for TROVE-2017-008, a
13066 security bug that affects hidden services running with the
13067 SafeLogging option disabled. For more information, see
13068 https://trac.torproject.org/projects/tor/ticket/23490
13070 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
13071 2018. We suggest that you upgrade to the latest stable release if
13072 possible. If you can't, we recommend that you upgrade at least to
13073 0.2.9, which will be supported until 2020.
13075 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
13076 - Avoid an assertion failure bug affecting our implementation of
13077 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
13078 handling of "0xx" differs from what we had expected. Fixes bug
13079 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
13082 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
13085 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
13086 - Backport a fix for an "unused variable" warning that appeared
13087 in some versions of mingw. Fixes bug 22838; bugfix on
13090 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
13091 - Fix a memset() off the end of an array when packing cells. This
13092 bug should be harmless in practice, since the corrupted bytes are
13093 still in the same structure, and are always padding bytes,
13094 ignored, or immediately overwritten, depending on compiler
13095 behavior. Nevertheless, because the memset()'s purpose is to make
13096 sure that any other cell-handling bugs can't expose bytes to the
13097 network, we need to fix it. Fixes bug 22737; bugfix on
13098 0.2.4.11-alpha. Fixes CID 1401591.
13100 o Build features (backport from 0.3.1.5-alpha):
13101 - Tor's repository now includes a Travis Continuous Integration (CI)
13102 configuration file (.travis.yml). This is meant to help new
13103 developers and contributors who fork Tor to a Github repository be
13104 better able to test their changes, and understand what we expect
13105 to pass. To use this new build feature, you must fork Tor to your
13106 Github account, then go into the "Integrations" menu in the
13107 repository settings for your fork and enable Travis, then push
13108 your changes. Closes ticket 22636.
13111 Changes in version 0.2.9.12 - 2017-09-18
13112 Tor 0.2.9.12 backports a collection of bugfixes from later
13115 Most significantly, it includes a fix for TROVE-2017-008, a
13116 security bug that affects hidden services running with the
13117 SafeLogging option disabled. For more information, see
13118 https://trac.torproject.org/projects/tor/ticket/23490
13120 o Major features (security, backport from 0.3.0.2-alpha):
13121 - Change the algorithm used to decide DNS TTLs on client and server
13122 side, to better resist DNS-based correlation attacks like the
13123 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
13124 Feamster. Now relays only return one of two possible DNS TTL
13125 values, and clients are willing to believe DNS TTL values up to 3
13126 hours long. Closes ticket 19769.
13128 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
13129 - Fix a rare crash when sending a begin cell on a circuit whose
13130 linked directory connection had already been closed. Fixes bug
13131 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
13133 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
13134 - Fix a bug that prevented exit nodes from caching DNS records for
13135 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
13137 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
13138 - Fix a typo that had prevented TPROXY-based transparent proxying
13139 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
13140 Patch from "d4fq0fQAgoJ".
13142 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
13143 - Avoid an assertion failure bug affecting our implementation of
13144 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
13145 handling of "0xx" differs from what we had expected. Fixes bug
13146 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
13148 o Minor features (code style, backport from 0.3.1.3-alpha):
13149 - Add "Falls through" comments to our codebase, in order to silence
13150 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
13151 Stieger. Closes ticket 22446.
13153 o Minor features (geoip):
13154 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
13157 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
13158 - Roll over monthly accounting at the configured hour and minute,
13159 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
13160 Found by Andrey Karpov with PVS-Studio.
13162 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
13163 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
13164 bugfix on 0.2.8.1-alpha.
13165 - Fix warnings when building with libscrypt and openssl scrypt support
13166 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
13167 - When building with certain versions the mingw C header files, avoid
13168 float-conversion warnings when calling the C functions isfinite(),
13169 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
13171 o Minor bugfixes (compilation, backport from 0.3.1.7):
13172 - Avoid compiler warnings in the unit tests for running tor_sscanf()
13173 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
13175 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
13176 - Backport a fix for an "unused variable" warning that appeared
13177 in some versions of mingw. Fixes bug 22838; bugfix on
13180 o Minor bugfixes (controller, backport from 0.3.1.7):
13181 - Do not crash when receiving a HSPOST command with an empty body.
13182 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
13183 - Do not crash when receiving a POSTDESCRIPTOR command with an
13184 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
13186 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
13187 - Avoid Coverity build warnings related to our BUG() macro. By
13188 default, Coverity treats BUG() as the Linux kernel does: an
13189 instant abort(). We need to override that so our BUG() macro
13190 doesn't prevent Coverity from analyzing functions that use it.
13191 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
13193 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
13194 - Fix a memset() off the end of an array when packing cells. This
13195 bug should be harmless in practice, since the corrupted bytes are
13196 still in the same structure, and are always padding bytes,
13197 ignored, or immediately overwritten, depending on compiler
13198 behavior. Nevertheless, because the memset()'s purpose is to make
13199 sure that any other cell-handling bugs can't expose bytes to the
13200 network, we need to fix it. Fixes bug 22737; bugfix on
13201 0.2.4.11-alpha. Fixes CID 1401591.
13203 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
13204 - When setting the maximum number of connections allowed by the OS,
13205 always allow some extra file descriptors for other files. Fixes
13206 bug 22797; bugfix on 0.2.0.10-alpha.
13208 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
13209 - Avoid a sandbox failure when trying to re-bind to a socket and
13210 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
13212 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
13213 - Permit the fchmod system call, to avoid crashing on startup when
13214 starting with the seccomp2 sandbox and an unexpected set of
13215 permissions on the data directory or its contents. Fixes bug
13216 22516; bugfix on 0.2.5.4-alpha.
13218 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
13219 - Avoid a double-marked-circuit warning that could happen when we
13220 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
13223 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
13224 - Reject version numbers with non-numeric prefixes (such as +, -, or
13225 whitespace). Disallowing whitespace prevents differential version
13226 parsing between POSIX-based and Windows platforms. Fixes bug 21507
13227 and part of 21508; bugfix on 0.0.8pre1.
13229 o Build features (backport from 0.3.1.5-alpha):
13230 - Tor's repository now includes a Travis Continuous Integration (CI)
13231 configuration file (.travis.yml). This is meant to help new
13232 developers and contributors who fork Tor to a Github repository be
13233 better able to test their changes, and understand what we expect
13234 to pass. To use this new build feature, you must fork Tor to your
13235 Github account, then go into the "Integrations" menu in the
13236 repository settings for your fork and enable Travis, then push
13237 your changes. Closes ticket 22636.
13240 Changes in version 0.3.0.11 - 2017-09-18
13241 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
13244 Most significantly, it includes a fix for TROVE-2017-008, a
13245 security bug that affects hidden services running with the
13246 SafeLogging option disabled. For more information, see
13247 https://trac.torproject.org/projects/tor/ticket/23490
13249 o Minor features (code style, backport from 0.3.1.7):
13250 - Add "Falls through" comments to our codebase, in order to silence
13251 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
13252 Stieger. Closes ticket 22446.
13255 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
13258 o Minor bugfixes (compilation, backport from 0.3.1.7):
13259 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
13260 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
13262 o Minor bugfixes (controller, backport from 0.3.1.7):
13263 - Do not crash when receiving a HSPOST command with an empty body.
13264 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
13265 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
13266 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
13268 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
13269 - When setting the maximum number of connections allowed by the OS,
13270 always allow some extra file descriptors for other files. Fixes
13271 bug 22797; bugfix on 0.2.0.10-alpha.
13273 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
13274 - Remove a forgotten debugging message when an introduction point
13275 successfully establishes a hidden service prop224 circuit with
13277 - Change three other log_warn() for an introduction point to
13278 protocol warnings, because they can be failure from the network
13279 and are not relevant to the operator. Fixes bug 23078; bugfix on
13280 0.3.0.1-alpha and 0.3.0.2-alpha.
13283 Changes in version 0.3.1.7 - 2017-09-18
13284 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
13286 With the 0.3.1 series, Tor now serves and downloads directory
13287 information in more compact formats, to save on bandwidth overhead. It
13288 also contains a new padding system to resist netflow-based traffic
13289 analysis, and experimental support for building parts of Tor in Rust
13290 (though no parts of Tor are in Rust yet). There are also numerous
13291 small features, bugfixes on earlier release series, and groundwork for
13292 the hidden services revamp of 0.3.2.
13294 This release also includes a fix for TROVE-2017-008, a security bug
13295 that affects hidden services running with the SafeLogging option
13296 disabled. For more information, see
13297 https://trac.torproject.org/projects/tor/ticket/23490
13299 Per our stable release policy, we plan to support each stable release
13300 series for at least the next nine months, or for three months after
13301 the first stable release of the next series: whichever is longer. If
13302 you need a release with long-term support, we recommend that you stay
13303 with the 0.2.9 series.
13305 Below is a list of the changes since 0.3.1.6-rc. For a list of all
13306 changes since 0.3.0, see the ReleaseNotes file.
13308 o Major bugfixes (security, hidden services, loggging):
13309 - Fix a bug where we could log uninitialized stack when a certain
13310 hidden service error occurred while SafeLogging was disabled.
13311 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
13312 TROVE-2017-008 and CVE-2017-0380.
13314 o Minor features (defensive programming):
13315 - Create a pair of consensus parameters, nf_pad_tor2web and
13316 nf_pad_single_onion, to disable netflow padding in the consensus
13317 for non-anonymous connections in case the overhead is high. Closes
13320 o Minor features (diagnostic):
13321 - Add a stack trace to the bug warnings that can be logged when
13322 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
13323 attempt for bug 23105.
13325 o Minor features (geoip):
13326 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
13329 o Minor bugfixes (compilation):
13330 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
13331 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
13333 o Minor bugfixes (controller):
13334 - Do not crash when receiving a HSPOST command with an empty body.
13335 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
13336 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
13337 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
13339 o Minor bugfixes (relay):
13340 - Inform the geoip and rephist modules about all requests, even on
13341 relays that are only fetching microdescriptors. Fixes a bug
13342 related to 21585; bugfix on 0.3.0.1-alpha.
13344 o Minor bugfixes (unit tests):
13345 - Fix a channelpadding unit test failure on slow systems by using
13346 mocked time instead of actual time. Fixes bug 23077; bugfix
13350 Changes in version 0.3.1.6-rc - 2017-09-05
13351 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
13352 release series, including a bug that produced weird behavior on
13353 Windows directory caches.
13355 This is the first release candidate in the Tor 0.3.1 series. If we
13356 find no new bugs or regressions here, the first stable 0.3.1 release
13357 will be nearly identical to it.
13359 o Major bugfixes (windows, directory cache):
13360 - On Windows, do not try to delete cached consensus documents and
13361 diffs before they are unmapped from memory--Windows won't allow
13362 that. Instead, allow the consensus cache directory to grow larger,
13363 to hold files that might need to stay around longer. Fixes bug
13364 22752; bugfix on 0.3.1.1-alpha.
13366 o Minor features (directory authority):
13367 - Improve the message that authorities report to relays that present
13368 RSA/Ed25519 keypairs that conflict with previously pinned keys.
13369 Closes ticket 22348.
13371 o Minor features (geoip):
13372 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
13375 o Minor features (testing):
13376 - Add more tests for compression backend initialization. Closes
13379 o Minor bugfixes (directory cache):
13380 - Fix a memory leak when recovering space in the consensus cache.
13381 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
13383 o Minor bugfixes (hidden service):
13384 - Increase the number of circuits that a service is allowed to
13385 open over a specific period of time. The value was lower than it
13386 should be (8 vs 12) in the normal case of 3 introduction points.
13387 Fixes bug 22159; bugfix on 0.3.0.5-rc.
13388 - Fix a BUG warning during HSv3 descriptor decoding that could be
13389 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
13390 on 0.3.0.1-alpha. Bug found by "haxxpop".
13391 - Rate-limit the log messages if we exceed the maximum number of
13392 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
13394 o Minor bugfixes (logging, relay):
13395 - Remove a forgotten debugging message when an introduction point
13396 successfully establishes a hidden service prop224 circuit with
13398 - Change three other log_warn() for an introduction point to
13399 protocol warnings, because they can be failure from the network
13400 and are not relevant to the operator. Fixes bug 23078; bugfix on
13401 0.3.0.1-alpha and 0.3.0.2-alpha.
13403 o Minor bugfixes (relay):
13404 - When a relay is not running as a directory cache, it will no
13405 longer generate compressed consensuses and consensus diff
13406 information. Previously, this was a waste of disk and CPU. Fixes
13407 bug 23275; bugfix on 0.3.1.1-alpha.
13409 o Minor bugfixes (robustness, error handling):
13410 - Improve our handling of the cases where OpenSSL encounters a
13411 memory error while encoding keys and certificates. We haven't
13412 observed these errors in the wild, but if they do happen, we now
13413 detect and respond better. Fixes bug 19418; bugfix on all versions
13414 of Tor. Reported by Guido Vranken.
13416 o Minor bugfixes (stability):
13417 - Avoid crashing on a double-free when unable to load or process an
13418 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
13419 with the clang static analyzer.
13421 o Minor bugfixes (testing):
13422 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
13423 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
13424 - Port the hs_ntor handshake test to work correctly with recent
13425 versions of the pysha3 module. Fixes bug 23071; bugfix
13428 o Minor bugfixes (Windows service):
13429 - When running as a Windows service, set the ID of the main thread
13430 correctly. Failure to do so made us fail to send log messages to
13431 the controller in 0.2.1.16-rc, slowed down controller event
13432 delivery in 0.2.7.3-rc and later, and crash with an assertion
13433 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
13434 Patch and diagnosis from "Vort".
13437 Changes in version 0.3.0.10 - 2017-08-02
13438 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
13439 from the current Tor alpha series. OpenBSD users and TPROXY users
13440 should upgrade; others are probably okay sticking with 0.3.0.9.
13442 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
13443 - Tor's repository now includes a Travis Continuous Integration (CI)
13444 configuration file (.travis.yml). This is meant to help new
13445 developers and contributors who fork Tor to a Github repository be
13446 better able to test their changes, and understand what we expect
13447 to pass. To use this new build feature, you must fork Tor to your
13448 Github account, then go into the "Integrations" menu in the
13449 repository settings for your fork and enable Travis, then push
13450 your changes. Closes ticket 22636.
13452 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
13453 - Fix a typo that had prevented TPROXY-based transparent proxying
13454 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
13455 Patch from "d4fq0fQAgoJ".
13457 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
13458 - Avoid an assertion failure bug affecting our implementation of
13459 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
13460 handling of "0xbar" differs from what we had expected. Fixes bug
13461 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
13463 o Minor features (backport from 0.3.1.5-alpha):
13464 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
13467 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
13468 - Roll over monthly accounting at the configured hour and minute,
13469 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
13470 Found by Andrey Karpov with PVS-Studio.
13472 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
13473 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
13474 bugfix on 0.2.8.1-alpha.
13475 - Fix warnings when building with libscrypt and openssl scrypt
13476 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
13477 - When building with certain versions of the mingw C header files,
13478 avoid float-conversion warnings when calling the C functions
13479 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
13482 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
13483 - Backport a fix for an "unused variable" warning that appeared
13484 in some versions of mingw. Fixes bug 22838; bugfix on
13487 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
13488 - Avoid Coverity build warnings related to our BUG() macro. By
13489 default, Coverity treats BUG() as the Linux kernel does: an
13490 instant abort(). We need to override that so our BUG() macro
13491 doesn't prevent Coverity from analyzing functions that use it.
13492 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
13494 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
13495 - When rejecting a router descriptor for running an obsolete version
13496 of Tor without ntor support, warn about the obsolete tor version,
13497 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
13499 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
13500 - Avoid a sandbox failure when trying to re-bind to a socket and
13501 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
13503 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
13504 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
13505 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
13508 Changes in version 0.3.1.5-alpha - 2017-08-01
13509 Tor 0.3.1.5-alpha improves the performance of consensus diff
13510 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
13511 several other bugs. If no serious bugs are found in this version, the
13512 next version will be a release candidate.
13514 This release also marks the end of support for the Tor 0.2.4.x,
13515 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
13516 further bug or security fixes. Anyone still running or distributing
13517 one of those versions should upgrade.
13519 o Major features (build system, continuous integration):
13520 - Tor's repository now includes a Travis Continuous Integration (CI)
13521 configuration file (.travis.yml). This is meant to help new
13522 developers and contributors who fork Tor to a Github repository be
13523 better able to test their changes, and understand what we expect
13524 to pass. To use this new build feature, you must fork Tor to your
13525 Github account, then go into the "Integrations" menu in the
13526 repository settings for your fork and enable Travis, then push
13527 your changes. Closes ticket 22636.
13529 o Major bugfixes (openbsd, denial-of-service):
13530 - Avoid an assertion failure bug affecting our implementation of
13531 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
13532 handling of "0xbar" differs from what we had expected. Fixes bug
13533 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
13535 o Major bugfixes (relay, performance):
13536 - Perform circuit handshake operations at a higher priority than we
13537 use for consensus diff creation and compression. This should
13538 prevent circuits from starving when a relay or bridge receives a
13539 new consensus, especially on lower-powered machines. Fixes bug
13540 22883; bugfix on 0.3.1.1-alpha.
13542 o Minor features (bridge authority):
13543 - Add "fingerprint" lines to the networkstatus-bridges file produced
13544 by bridge authorities. Closes ticket 22207.
13546 o Minor features (directory cache, consensus diff):
13547 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
13548 operators with low-resource environments to adjust the number of
13549 consensuses they'll store and generate diffs from. Most cache
13550 operators should leave it unchanged. Helps to work around
13553 o Minor features (geoip):
13554 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
13557 o Minor features (relay, performance):
13558 - Always start relays with at least two worker threads, to prevent
13559 priority inversion on slow tasks. Part of the fix for bug 22883.
13560 - Allow background work to be queued with different priorities, so
13561 that a big pile of slow low-priority jobs will not starve out
13562 higher priority jobs. This lays the groundwork for a fix for
13565 o Minor bugfixes (build system, rust):
13566 - Fix a problem where Rust toolchains were not being found when
13567 building without --enable-cargo-online-mode, due to setting the
13568 $HOME environment variable instead of $CARGO_HOME. Fixes bug
13569 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
13571 o Minor bugfixes (compatibility, zstd):
13572 - Write zstd epilogues correctly when the epilogue requires
13573 reallocation of the output buffer, even with zstd 1.3.0.
13574 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
13575 22927; bugfix on 0.3.1.1-alpha.
13577 o Minor bugfixes (compilation warnings):
13578 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
13579 22915; bugfix on 0.2.8.1-alpha.
13580 - Fix warnings when building with libscrypt and openssl scrypt
13581 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
13582 - Compile correctly when both openssl 1.1.0 and libscrypt are
13583 detected. Previously this would cause an error. Fixes bug 22892;
13584 bugfix on 0.3.1.1-alpha.
13585 - When building with certain versions of the mingw C header files,
13586 avoid float-conversion warnings when calling the C functions
13587 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
13590 o Minor bugfixes (coverity build support):
13591 - Avoid Coverity build warnings related to our BUG() macro. By
13592 default, Coverity treats BUG() as the Linux kernel does: an
13593 instant abort(). We need to override that so our BUG() macro
13594 doesn't prevent Coverity from analyzing functions that use it.
13595 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
13597 o Minor bugfixes (directory authority):
13598 - When a directory authority rejects a descriptor or extrainfo with
13599 a given digest, mark that digest as undownloadable, so that we do
13600 not attempt to download it again over and over. We previously
13601 tried to avoid downloading such descriptors by other means, but we
13602 didn't notice if we accidentally downloaded one anyway. This
13603 behavior became problematic in 0.2.7.2-alpha, when authorities
13604 began pinning Ed25519 keys. Fixes bug 22349; bugfix
13607 o Minor bugfixes (error reporting, windows):
13608 - When formatting Windows error messages, use the English format to
13609 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
13612 o Minor bugfixes (file limits, osx):
13613 - When setting the maximum number of connections allowed by the OS,
13614 always allow some extra file descriptors for other files. Fixes
13615 bug 22797; bugfix on 0.2.0.10-alpha.
13617 o Minor bugfixes (linux seccomp2 sandbox):
13618 - Avoid a sandbox failure when trying to re-bind to a socket and
13619 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
13621 o Minor bugfixes (memory leaks):
13622 - Fix a small memory leak when validating a configuration that uses
13623 two or more AF_UNIX sockets for the same port type. Fixes bug
13624 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
13626 o Minor bugfixes (unit tests):
13627 - test_consdiff_base64cmp would fail on OS X because while OS X
13628 follows the standard of (less than zero/zero/greater than zero),
13629 it doesn't follow the convention of (-1/0/+1). Make the test
13630 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
13631 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
13632 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
13635 Changes in version 0.3.1.4-alpha - 2017-06-29
13636 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
13637 to use a guard that was in the same network family as a chosen exit
13638 relay. This is a security regression; all clients running earlier
13639 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
13642 This release also fixes several other bugs introduced in 0.3.0.x
13643 and 0.3.1.x, including others that can affect bandwidth usage
13646 o New dependencies:
13647 - To build with zstd and lzma support, Tor now requires the
13648 pkg-config tool at build time. (This requirement was new in
13649 0.3.1.1-alpha, but was not noted at the time. Noting it here to
13650 close ticket 22623.)
13652 o Major bugfixes (path selection, security):
13653 - When choosing which guard to use for a circuit, avoid the exit's
13654 family along with the exit itself. Previously, the new guard
13655 selection logic avoided the exit, but did not consider its family.
13656 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
13657 006 and CVE-2017-0377.
13659 o Major bugfixes (compression, zstd):
13660 - Correctly detect a full buffer when decompressing a large zstd-
13661 compressed input. Previously, we would sometimes treat a full
13662 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
13664 o Major bugfixes (directory protocol):
13665 - Ensure that we send "304 Not modified" as HTTP status code when a
13666 client is attempting to fetch a consensus or consensus diff, and
13667 the best one we can send them is one they already have. Fixes bug
13668 22702; bugfix on 0.3.1.1-alpha.
13670 o Major bugfixes (entry guards):
13671 - When starting with an old consensus, do not add new entry guards
13672 unless the consensus is "reasonably live" (under 1 day old). Fixes
13673 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
13675 o Minor features (bug mitigation, diagnostics, logging):
13676 - Avoid an assertion failure, and log a better error message, when
13677 unable to remove a file from the consensus cache on Windows.
13678 Attempts to mitigate and diagnose bug 22752.
13680 o Minor features (geoip):
13681 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
13684 o Minor bugfixes (compression):
13685 - When compressing or decompressing a buffer, check for a failure to
13686 create a compression object. Fixes bug 22626; bugfix
13688 - When decompressing a buffer, check for extra data after the end of
13689 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
13690 - When decompressing an object received over an anonymous directory
13691 connection, if we have already decompressed it using an acceptable
13692 compression method, do not reject it for looking like an
13693 unacceptable compression method. Fixes part of bug 22670; bugfix
13695 - When serving directory votes compressed with zlib, do not claim to
13696 have compressed them with zstd. Fixes bug 22669; bugfix
13698 - When spooling compressed data to an output buffer, don't try to
13699 spool more data when there is no more data to spool and we are not
13700 trying to flush the input. Previously, we would sometimes launch
13701 compression requests with nothing to do, which interferes with our
13702 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
13704 o Minor bugfixes (defensive programming):
13705 - Detect and break out of infinite loops in our compression code. We
13706 don't think that any such loops exist now, but it's best to be
13707 safe. Closes ticket 22672.
13708 - Fix a memset() off the end of an array when packing cells. This
13709 bug should be harmless in practice, since the corrupted bytes are
13710 still in the same structure, and are always padding bytes,
13711 ignored, or immediately overwritten, depending on compiler
13712 behavior. Nevertheless, because the memset()'s purpose is to make
13713 sure that any other cell-handling bugs can't expose bytes to the
13714 network, we need to fix it. Fixes bug 22737; bugfix on
13715 0.2.4.11-alpha. Fixes CID 1401591.
13717 o Minor bugfixes (linux seccomp2 sandbox):
13718 - Permit the fchmod system call, to avoid crashing on startup when
13719 starting with the seccomp2 sandbox and an unexpected set of
13720 permissions on the data directory or its contents. Fixes bug
13721 22516; bugfix on 0.2.5.4-alpha.
13722 - Fix a crash in the LZMA module, when the sandbox was enabled, and
13723 liblzma would allocate more than 16 MB of memory. We solve this by
13724 bumping the mprotect() limit in the sandbox module from 16 MB to
13725 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
13727 o Minor bugfixes (logging):
13728 - When decompressing, do not warn if we fail to decompress using a
13729 compression method that we merely guessed. Fixes part of bug
13730 22670; bugfix on 0.1.1.14-alpha.
13731 - When decompressing, treat mismatch between content-encoding and
13732 actual compression type as a protocol warning. Fixes part of bug
13733 22670; bugfix on 0.1.1.9-alpha.
13734 - Downgrade "assigned_to_cpuworker failed" message to info-level
13735 severity. In every case that can reach it, either a better warning
13736 has already been logged, or no warning is warranted. Fixes bug
13737 22356; bugfix on 0.2.6.3-alpha.
13738 - Demote a warn that was caused by libevent delays to info if
13739 netflow padding is less than 4.5 seconds late, or to notice
13740 if it is more (4.5 seconds is the amount of time that a netflow
13741 record might be emitted after, if we chose the maximum timeout).
13742 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
13744 o Minor bugfixes (process behavior):
13745 - When exiting because of an error, always exit with a nonzero exit
13746 status. Previously, we would fail to report an error in our exit
13747 status in cases related to __OwningControllerProcess failure,
13748 lockfile contention, and Ed25519 key initialization. Fixes bug
13749 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
13750 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
13754 - Add a manpage description for the key-pinning-journal file. Closes
13756 - Correctly note that bandwidth accounting values are stored in the
13757 state file, and the bw_accounting file is now obsolete. Closes
13759 - Document more of the files in the Tor data directory, including
13760 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
13761 approved-routers, sr-random, and diff-cache. Found while fixing
13765 Changes in version 0.3.0.9 - 2017-06-29
13766 Tor 0.3.0.9 fixes a path selection bug that would allow a client
13767 to use a guard that was in the same network family as a chosen exit
13768 relay. This is a security regression; all clients running earlier
13769 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
13772 This release also backports several other bugfixes from the 0.3.1.x
13775 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
13776 - When choosing which guard to use for a circuit, avoid the exit's
13777 family along with the exit itself. Previously, the new guard
13778 selection logic avoided the exit, but did not consider its family.
13779 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
13780 006 and CVE-2017-0377.
13782 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
13783 - Don't block bootstrapping when a primary bridge is offline and we
13784 can't get its descriptor. Fixes bug 22325; fixes one case of bug
13785 21969; bugfix on 0.3.0.3-alpha.
13787 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
13788 - When starting with an old consensus, do not add new entry guards
13789 unless the consensus is "reasonably live" (under 1 day old). Fixes
13790 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
13792 o Minor features (geoip):
13793 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
13796 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
13797 - Reject version numbers with non-numeric prefixes (such as +, -, or
13798 whitespace). Disallowing whitespace prevents differential version
13799 parsing between POSIX-based and Windows platforms. Fixes bug 21507
13800 and part of 21508; bugfix on 0.0.8pre1.
13802 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
13803 - Permit the fchmod system call, to avoid crashing on startup when
13804 starting with the seccomp2 sandbox and an unexpected set of
13805 permissions on the data directory or its contents. Fixes bug
13806 22516; bugfix on 0.2.5.4-alpha.
13808 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
13809 - Fix a memset() off the end of an array when packing cells. This
13810 bug should be harmless in practice, since the corrupted bytes are
13811 still in the same structure, and are always padding bytes,
13812 ignored, or immediately overwritten, depending on compiler
13813 behavior. Nevertheless, because the memset()'s purpose is to make
13814 sure that any other cell-handling bugs can't expose bytes to the
13815 network, we need to fix it. Fixes bug 22737; bugfix on
13816 0.2.4.11-alpha. Fixes CID 1401591.
13819 Changes in version 0.3.1.3-alpha - 2017-06-08
13820 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
13821 remotely crash a hidden service with an assertion failure. Anyone
13822 running a hidden service should upgrade to this version, or to some
13823 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
13825 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
13826 that sometimes made relays unreliable, as well as several other
13827 bugfixes described below.
13829 o Major bugfixes (hidden service, relay, security):
13830 - Fix a remotely triggerable assertion failure when a hidden service
13831 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
13832 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
13833 - Fix a remotely triggerable assertion failure caused by receiving a
13834 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13835 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13838 o Major bugfixes (relay, link handshake):
13839 - When performing the v3 link handshake on a TLS connection, report
13840 that we have the x509 certificate that we actually used on that
13841 connection, even if we have changed certificates since that
13842 connection was first opened. Previously, we would claim to have
13843 used our most recent x509 link certificate, which would sometimes
13844 make the link handshake fail. Fixes one case of bug 22460; bugfix
13847 o Major bugfixes (relays, key management):
13848 - Regenerate link and authentication certificates whenever the key
13849 that signs them changes; also, regenerate link certificates
13850 whenever the signed key changes. Previously, these processes were
13851 only weakly coupled, and we relays could (for minutes to hours)
13852 wind up with an inconsistent set of keys and certificates, which
13853 other relays would not accept. Fixes two cases of bug 22460;
13854 bugfix on 0.3.0.1-alpha.
13855 - When sending an Ed25519 signing->link certificate in a CERTS cell,
13856 send the certificate that matches the x509 certificate that we
13857 used on the TLS connection. Previously, there was a race condition
13858 if the TLS context rotated after we began the TLS handshake but
13859 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
13862 o Major bugfixes (torrc, crash):
13863 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
13864 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
13866 o Minor features (code style):
13867 - Add "Falls through" comments to our codebase, in order to silence
13868 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
13869 Stieger. Closes ticket 22446.
13871 o Minor features (diagnostic):
13872 - Add logging messages to try to diagnose a rare bug that seems to
13873 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
13874 think this is happening because of incorrect system clocks, but
13875 we'd like to know for certain. Diagnostic for bug 22466.
13877 o Minor bugfixes (correctness):
13878 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13879 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13881 o Minor bugfixes (directory protocol):
13882 - Check for libzstd >= 1.1, because older versions lack the
13883 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
13885 o Minor bugfixes (link handshake):
13886 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
13887 months, and regenerate it when it is within one month of expiring.
13888 Previously, we had generated this certificate at startup with a
13889 ten-year lifetime, but that could lead to weird behavior when Tor
13890 was started with a grossly inaccurate clock. Mitigates bug 22466;
13891 mitigation on 0.3.0.1-alpha.
13893 o Minor bugfixes (storage directories):
13894 - Always check for underflows in the cached storage directory usage.
13895 If the usage does underflow, re-calculate it. Also, avoid a
13896 separate underflow when the usage is not known. Fixes bug 22424;
13897 bugfix on 0.3.1.1-alpha.
13899 o Minor bugfixes (unit tests):
13900 - The unit tests now pass on systems where localhost is misconfigured
13901 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
13905 - Clarify the manpage for the (deprecated) torify script. Closes
13908 Changes in version 0.3.0.8 - 2017-06-08
13909 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
13910 remotely crash a hidden service with an assertion failure. Anyone
13911 running a hidden service should upgrade to this version, or to some
13912 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
13914 Tor 0.3.0.8 also includes fixes for several key management bugs
13915 that sometimes made relays unreliable, as well as several other
13916 bugfixes described below.
13918 o Major bugfixes (hidden service, relay, security, backport
13919 from 0.3.1.3-alpha):
13920 - Fix a remotely triggerable assertion failure when a hidden service
13921 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
13922 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
13923 - Fix a remotely triggerable assertion failure caused by receiving a
13924 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13925 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13928 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
13929 - When performing the v3 link handshake on a TLS connection, report
13930 that we have the x509 certificate that we actually used on that
13931 connection, even if we have changed certificates since that
13932 connection was first opened. Previously, we would claim to have
13933 used our most recent x509 link certificate, which would sometimes
13934 make the link handshake fail. Fixes one case of bug 22460; bugfix
13937 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
13938 - Regenerate link and authentication certificates whenever the key
13939 that signs them changes; also, regenerate link certificates
13940 whenever the signed key changes. Previously, these processes were
13941 only weakly coupled, and we relays could (for minutes to hours)
13942 wind up with an inconsistent set of keys and certificates, which
13943 other relays would not accept. Fixes two cases of bug 22460;
13944 bugfix on 0.3.0.1-alpha.
13945 - When sending an Ed25519 signing->link certificate in a CERTS cell,
13946 send the certificate that matches the x509 certificate that we
13947 used on the TLS connection. Previously, there was a race condition
13948 if the TLS context rotated after we began the TLS handshake but
13949 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
13952 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
13953 - Stop rejecting v3 hidden service descriptors because their size
13954 did not match an old padding rule. Fixes bug 22447; bugfix on
13957 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
13958 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
13959 December 2016 (of which ~126 were still functional) with a list of
13960 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
13961 2017. Resolves ticket 21564.
13963 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
13964 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
13965 bug 22252; bugfix on 0.2.9.3-alpha.
13967 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
13968 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13969 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13971 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
13972 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
13973 months, and regenerate it when it is within one month of expiring.
13974 Previously, we had generated this certificate at startup with a
13975 ten-year lifetime, but that could lead to weird behavior when Tor
13976 was started with a grossly inaccurate clock. Mitigates bug 22466;
13977 mitigation on 0.3.0.1-alpha.
13979 o Minor bugfixes (memory leak, directory authority, backport from
13981 - When directory authorities reject a router descriptor due to
13982 keypinning, free the router descriptor rather than leaking the
13983 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
13986 Changes in version 0.2.9.11 - 2017-06-08
13987 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
13988 remotely crash a hidden service with an assertion failure. Anyone
13989 running a hidden service should upgrade to this version, or to some
13990 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
13991 are not affected by TROVE-2017-004.)
13993 Tor 0.2.9.11 also backports fixes for several key management bugs
13994 that sometimes made relays unreliable, as well as several other
13995 bugfixes described below.
13997 o Major bugfixes (hidden service, relay, security, backport
13998 from 0.3.1.3-alpha):
13999 - Fix a remotely triggerable assertion failure caused by receiving a
14000 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
14001 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
14004 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
14005 - When performing the v3 link handshake on a TLS connection, report
14006 that we have the x509 certificate that we actually used on that
14007 connection, even if we have changed certificates since that
14008 connection was first opened. Previously, we would claim to have
14009 used our most recent x509 link certificate, which would sometimes
14010 make the link handshake fail. Fixes one case of bug 22460; bugfix
14013 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
14014 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
14015 December 2016 (of which ~126 were still functional) with a list of
14016 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
14017 2017. Resolves ticket 21564.
14019 o Minor features (future-proofing, backport from 0.3.0.7):
14020 - Tor no longer refuses to download microdescriptors or descriptors if
14021 they are listed as "published in the future". This change will
14022 eventually allow us to stop listing meaningful "published" dates
14023 in microdescriptor consensuses, and thereby allow us to reduce the
14024 resources required to download consensus diffs by over 50%.
14025 Implements part of ticket 21642; implements part of proposal 275.
14027 o Minor features (directory authorities, backport from 0.3.0.4-rc)
14028 - Directory authorities now reject relays running versions
14029 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
14030 suffer from bug 20499 and don't keep their consensus cache
14031 up-to-date. Resolves ticket 20509.
14033 o Minor features (geoip):
14034 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
14037 o Minor bugfixes (control port, backport from 0.3.0.6):
14038 - The GETINFO extra-info/digest/<digest> command was broken because
14039 of a wrong base16 decode return value check, introduced when
14040 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
14042 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
14043 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
14044 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
14046 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
14047 - The getpid() system call is now permitted under the Linux seccomp2
14048 sandbox, to avoid crashing with versions of OpenSSL (and other
14049 libraries) that attempt to learn the process's PID by using the
14050 syscall rather than the VDSO code. Fixes bug 21943; bugfix
14053 o Minor bugfixes (memory leak, directory authority, backport
14054 from 0.3.1.2-alpha):
14055 - When directory authorities reject a router descriptor due to
14056 keypinning, free the router descriptor rather than leaking the
14057 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
14059 Changes in version 0.2.8.14 - 2017-06-08
14060 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
14061 remotely crash a hidden service with an assertion failure. Anyone
14062 running a hidden service should upgrade to this version, or to some
14063 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
14064 are not affected by TROVE-2017-004.)
14066 o Major bugfixes (hidden service, relay, security):
14067 - Fix a remotely triggerable assertion failure caused by receiving a
14068 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
14069 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
14072 o Minor features (geoip):
14073 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
14076 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
14077 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
14078 December 2016 (of which ~126 were still functional) with a list of
14079 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
14080 2017. Resolves ticket 21564.
14082 o Minor bugfixes (correctness):
14083 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
14084 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
14086 Changes in version 0.2.7.8 - 2017-06-08
14087 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
14088 remotely crash a hidden service with an assertion failure. Anyone
14089 running a hidden service should upgrade to this version, or to some
14090 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
14091 are not affected by TROVE-2017-004.)
14093 o Major bugfixes (hidden service, relay, security):
14094 - Fix a remotely triggerable assertion failure caused by receiving a
14095 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
14096 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
14099 o Minor features (geoip):
14100 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
14103 o Minor bugfixes (correctness):
14104 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
14105 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
14108 Changes in version 0.2.6.12 - 2017-06-08
14109 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
14110 remotely crash a hidden service with an assertion failure. Anyone
14111 running a hidden service should upgrade to this version, or to some
14112 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
14113 are not affected by TROVE-2017-004.)
14115 o Major bugfixes (hidden service, relay, security):
14116 - Fix a remotely triggerable assertion failure caused by receiving a
14117 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
14118 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
14121 o Minor features (geoip):
14122 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
14125 o Minor bugfixes (correctness):
14126 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
14127 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
14129 Changes in version 0.2.5.14 - 2017-06-08
14130 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
14131 remotely crash a hidden service with an assertion failure. Anyone
14132 running a hidden service should upgrade to this version, or to some
14133 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
14134 are not affected by TROVE-2017-004.)
14136 o Major bugfixes (hidden service, relay, security):
14137 - Fix a remotely triggerable assertion failure caused by receiving a
14138 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
14139 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
14142 o Minor features (geoip):
14143 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
14146 o Minor bugfixes (correctness):
14147 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
14148 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
14150 Changes in version 0.2.4.29 - 2017-06-08
14151 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
14152 remotely crash a hidden service with an assertion failure. Anyone
14153 running a hidden service should upgrade to this version, or to some
14154 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
14155 are not affected by TROVE-2017-004.)
14157 o Major bugfixes (hidden service, relay, security):
14158 - Fix a remotely triggerable assertion failure caused by receiving a
14159 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
14160 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
14163 o Minor features (geoip):
14164 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
14167 o Minor bugfixes (correctness):
14168 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
14169 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
14172 Changes in version 0.3.1.2-alpha - 2017-05-26
14173 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
14174 fixes a few bugs found while testing 0.3.1.1-alpha, including a
14175 memory corruption bug that affected relay stability.
14177 o Major bugfixes (crash, relay):
14178 - Fix a memory-corruption bug in relays that set MyFamily.
14179 Previously, they would double-free MyFamily elements when making
14180 the next descriptor or when changing their configuration. Fixes
14181 bug 22368; bugfix on 0.3.1.1-alpha.
14183 o Minor bugfixes (logging):
14184 - Log a better message when a directory authority replies to an
14185 upload with an unexpected status code. Fixes bug 11121; bugfix
14188 o Minor bugfixes (memory leak, directory authority):
14189 - When directory authorities reject a router descriptor due to
14190 keypinning, free the router descriptor rather than leaking the
14191 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
14194 Changes in version 0.3.1.1-alpha - 2017-05-22
14195 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
14196 reduces the bandwidth usage for Tor's directory protocol, adds some
14197 basic padding to resist netflow-based traffic analysis and to serve as
14198 the basis of other padding in the future, and adds rust support to the
14201 It also contains numerous other small features and improvements to
14202 security, correctness, and performance.
14204 Below are the changes since 0.3.0.7.
14206 o Major features (directory protocol):
14207 - Tor relays and authorities can now serve clients an abbreviated
14208 version of the consensus document, containing only the changes
14209 since an older consensus document that the client holds. Clients
14210 now request these documents when available. When both client and
14211 server use this new protocol, they will use far less bandwidth (up
14212 to 94% less) to keep the client's consensus up-to-date. Implements
14213 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
14214 - Tor can now compress directory traffic with lzma or with zstd
14215 compression algorithms, which can deliver better bandwidth
14216 performance. Because lzma is computationally expensive, it's only
14217 used for documents that can be compressed once and served many
14218 times. Support for these algorithms requires that tor is built
14219 with the libzstd and/or liblzma libraries available. Implements
14220 proposal 278; closes ticket 21662.
14221 - Relays now perform the more expensive compression operations, and
14222 consensus diff generation, in worker threads. This separation
14223 avoids delaying the main thread when a new consensus arrives.
14225 o Major features (experimental):
14226 - Tor can now build modules written in Rust. To turn this on, pass
14227 the "--enable-rust" flag to the configure script. It's not time to
14228 get excited yet: currently, there is no actual Rust functionality
14229 beyond some simple glue code, and a notice at startup to tell you
14230 that Rust is running. Still, we hope that programmers and
14231 packagers will try building Tor with Rust support, so that we can
14232 find issues and solve portability problems. Closes ticket 22106.
14234 o Major features (traffic analysis resistance):
14235 - Connections between clients and relays now send a padding cell in
14236 each direction every 1.5 to 9.5 seconds (tunable via consensus
14237 parameters). This padding will not resist specialized
14238 eavesdroppers, but it should be enough to make many ISPs' routine
14239 network flow logging less useful in traffic analysis against
14242 Padding is negotiated using Tor's link protocol, so both relays
14243 and clients must upgrade for this to take effect. Clients may
14244 still send padding despite the relay's version by setting
14245 ConnectionPadding 1 in torrc, and may disable padding by setting
14246 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
14247 users with the torrc option ReducedConnectionPadding. Implements
14248 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
14249 - Relays will publish 24 hour totals of padding and non-padding cell
14250 counts to their extra-info descriptors, unless PaddingStatistics 0
14251 is set in torrc. These 24 hour totals are also rounded to
14252 multiples of 10000.
14254 o Major bugfixes (connection usage):
14255 - We use NETINFO cells to try to determine if both relays involved
14256 in a connection will agree on the canonical status of that
14257 connection. We prefer the connections where this is the case for
14258 extend cells, and try to close connections where relays disagree
14259 on their canonical status early. Also, we now prefer the oldest
14260 valid connection for extend cells. These two changes should reduce
14261 the number of long-term connections that are kept open between
14262 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
14263 - Relays now log hourly statistics (look for
14264 "channel_check_for_duplicates" lines) on the total number of
14265 connections to other relays. If the number of connections per
14266 relay is unexpectedly large, this log message is at notice level.
14267 Otherwise it is at info.
14269 o Major bugfixes (entry guards):
14270 - Don't block bootstrapping when a primary bridge is offline and we
14271 can't get its descriptor. Fixes bug 22325; fixes one case of bug
14272 21969; bugfix on 0.3.0.3-alpha.
14274 o Major bugfixes (linux TPROXY support):
14275 - Fix a typo that had prevented TPROXY-based transparent proxying
14276 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
14277 Patch from "d4fq0fQAgoJ".
14279 o Minor features (security, windows):
14280 - Enable a couple of pieces of Windows hardening: one
14281 (HeapEnableTerminationOnCorruption) that has been on-by-default
14282 since Windows 8, and unavailable before Windows 7; and one
14283 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
14284 affect us, but shouldn't do any harm. Closes ticket 21953.
14286 o Minor features (config options):
14287 - Allow "%include" directives in torrc configuration files. These
14288 directives import the settings from other files, or from all the
14289 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
14290 - Make SAVECONF return an error when overwriting a torrc that has
14291 includes. Using SAVECONF with the FORCE option will allow it to
14292 overwrite torrc even if includes are used. Related to ticket 1922.
14293 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
14294 will work without the FORCE option. Related to ticket 1922.
14296 o Minor features (controller):
14297 - Warn the first time that a controller requests data in the long-
14298 deprecated 'GETINFO network-status' format. Closes ticket 21703.
14300 o Minor features (defaults):
14301 - The default value for UseCreateFast is now 0: clients which
14302 haven't yet received a consensus document will now use a proper
14303 ntor handshake to talk to their directory servers whenever they
14304 can. Closes ticket 21407.
14305 - Onion key rotation and expiry intervals are now defined as a
14306 network consensus parameter, per proposal 274. The default
14307 lifetime of an onion key is increased from 7 to 28 days. Old onion
14308 keys will expire after 7 days by default. This change will make
14309 consensus diffs much smaller, and save significant bandwidth.
14310 Closes ticket 21641.
14312 o Minor features (fallback directory list):
14313 - Update the fallback directory mirror whitelist and blacklist based
14314 on operator emails. Closes task 21121.
14315 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
14316 December 2016 (of which ~126 were still functional) with a list of
14317 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
14318 2017. Resolves ticket 21564.
14320 o Minor features (hidden services, logging):
14321 - Log a message when a hidden service descriptor has fewer
14322 introduction points than specified in
14323 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
14324 - Log a message when a hidden service reaches its introduction point
14325 circuit limit, and when that limit is reset. Follow up to ticket
14326 21594; closes ticket 21622.
14327 - Warn user if multiple entries in EntryNodes and at least one
14328 HiddenService are used together. Pinning EntryNodes along with a
14329 hidden service can be possibly harmful; for instance see ticket
14330 14917 or 21155. Closes ticket 21155.
14332 o Minor features (linux seccomp2 sandbox):
14333 - We now have a document storage backend compatible with the Linux
14334 seccomp2 sandbox. This backend is used for consensus documents and
14335 diffs between them; in the long term, we'd like to use it for
14336 unparseable directory material too. Closes ticket 21645
14337 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
14338 from 1MB to 16MB. This was necessary with the glibc allocator in
14339 order to allow worker threads to allocate more memory -- which in
14340 turn is necessary because of our new use of worker threads for
14341 compression. Closes ticket 22096.
14343 o Minor features (logging):
14344 - Log files are no longer created world-readable by default.
14345 (Previously, most distributors would store the logs in a non-
14346 world-readable location to prevent inappropriate access. This
14347 change is an extra precaution.) Closes ticket 21729; patch
14350 o Minor features (performance):
14351 - Our Keccak (SHA-3) implementation now accesses memory more
14352 efficiently, especially on little-endian systems. Closes
14354 - Add an O(1) implementation of channel_find_by_global_id(), to
14355 speed some controller functions.
14357 o Minor features (relay, configuration):
14358 - The MyFamily option may now be repeated as many times as desired,
14359 for relays that want to configure large families. Closes ticket
14360 4998; patch by Daniel Pinto.
14362 o Minor features (safety):
14363 - Add an explicit check to extrainfo_parse_entry_from_string() for
14364 NULL inputs. We don't believe this can actually happen, but it may
14365 help silence a warning from the Clang analyzer. Closes
14368 o Minor features (testing):
14369 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
14370 When Tor is compiled with this option, we disable a number of
14371 redundant memory-safety failsafes that are intended to stop bugs
14372 from becoming security issues. This makes it easier to hunt for
14373 bugs that would be security issues without the failsafes turned
14374 on. Closes ticket 21439.
14375 - Add a general event-tracing instrumentation support to Tor. This
14376 subsystem will enable developers and researchers to add fine-
14377 grained instrumentation to their Tor instances, for use when
14378 examining Tor network performance issues. There are no trace
14379 events yet, and event-tracing is off by default unless enabled at
14380 compile time. Implements ticket 13802.
14381 - Improve our version parsing tests: add tests for typical version
14382 components, add tests for invalid versions, including numeric
14383 range and non-numeric prefixes. Unit tests 21278, 21450, and
14384 21507. Partially implements 21470.
14386 o Minor bugfixes (bandwidth accounting):
14387 - Roll over monthly accounting at the configured hour and minute,
14388 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
14389 Found by Andrey Karpov with PVS-Studio.
14391 o Minor bugfixes (code correctness):
14392 - Accurately identify client connections by their lack of peer
14393 authentication. This means that we bail out earlier if asked to
14394 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
14397 o Minor bugfixes (configuration):
14398 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
14399 bug 22252; bugfix on 0.2.9.3-alpha.
14401 o Minor bugfixes (connection lifespan):
14402 - Allow more control over how long TLS connections are kept open:
14403 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
14404 single option called CircuitsAvailableTimeout. Also, allow the
14405 consensus to control the default values for both this preference
14406 and the lifespan of relay-to-relay connections. Fixes bug 17592;
14407 bugfix on 0.2.5.5-alpha.
14408 - Increase the initial circuit build timeout testing frequency, to
14409 help ensure that ReducedConnectionPadding clients finish learning
14410 a timeout before their orconn would expire. The initial testing
14411 rate was set back in the days of TAP and before the Tor Browser
14412 updater, when we had to be much more careful about new clients
14413 making lots of circuits. With this change, a circuit build timeout
14414 is learned in about 15-20 minutes, instead of 100-120 minutes.
14416 o Minor bugfixes (controller):
14417 - GETINFO onions/current and onions/detached no longer respond with
14418 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
14419 - Trigger HS descriptor events on the control port when the client
14420 fails to pick a hidden service directory for a hidden service.
14421 This can happen if all the hidden service directories are in
14422 ExcludeNodes, or they have all been queried within the last 15
14423 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
14425 o Minor bugfixes (directory authority):
14426 - When rejecting a router descriptor for running an obsolete version
14427 of Tor without ntor support, warn about the obsolete tor version,
14428 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
14429 - Prevent the shared randomness subsystem from asserting when
14430 initialized by a bridge authority with an incomplete configuration
14431 file. Fixes bug 21586; bugfix on 0.2.9.8.
14433 o Minor bugfixes (exit-side DNS):
14434 - Fix an untriggerable assertion that checked the output of a
14435 libevent DNS error, so that the assertion actually behaves as
14436 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
14437 Karpov using PVS-Studio.
14439 o Minor bugfixes (fallback directories):
14440 - Make the usage example in updateFallbackDirs.py actually work, and
14441 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
14442 - Decrease the guard flag average required to be a fallback. This
14443 allows us to keep relays that have their guard flag removed when
14444 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
14445 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
14446 bugfix on 0.2.8.1-alpha.
14447 - Make sure fallback directory mirrors have the same address, port,
14448 and relay identity key for at least 30 days before they are
14449 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
14451 o Minor bugfixes (hidden services):
14452 - Stop printing a cryptic warning when a hidden service gets a
14453 request to connect to a virtual port that it hasn't configured.
14454 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
14455 - Simplify hidden service descriptor creation by using an existing
14456 flag to check if an introduction point is established. Fixes bug
14457 21599; bugfix on 0.2.7.2-alpha.
14459 o Minor bugfixes (memory leak):
14460 - Fix a small memory leak at exit from the backtrace handler code.
14461 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
14463 o Minor bugfixes (protocol, logging):
14464 - Downgrade a log statement about unexpected relay cells from "bug"
14465 to "protocol warning", because there is at least one use case
14466 where it can be triggered by a buggy tor implementation. Fixes bug
14467 21293; bugfix on 0.1.1.14-alpha.
14469 o Minor bugfixes (testing):
14470 - Use unbuffered I/O for utility functions around the
14471 process_handle_t type. This fixes unit test failures reported on
14472 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
14473 - Make display of captured unit test log messages consistent. Fixes
14474 bug 21510; bugfix on 0.2.9.3-alpha.
14475 - Make test-network.sh always call chutney's test-network.sh.
14476 Previously, this only worked on systems which had bash installed,
14477 due to some bash-specific code in the script. Fixes bug 19699;
14478 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
14480 o Minor bugfixes (voting consistency):
14481 - Reject version numbers with non-numeric prefixes (such as +, -, or
14482 whitespace). Disallowing whitespace prevents differential version
14483 parsing between POSIX-based and Windows platforms. Fixes bug 21507
14484 and part of 21508; bugfix on 0.0.8pre1.
14486 o Minor bugfixes (windows, relay):
14487 - Resolve "Failure from drain_fd: No error" warnings on Windows
14488 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
14490 o Code simplification and refactoring:
14491 - Break up the 630-line function connection_dir_client_reached_eof()
14492 into a dozen smaller functions. This change should help
14493 maintainability and readability of the client directory code.
14494 - Isolate our use of the openssl headers so that they are only
14495 included from our crypto wrapper modules, and from tests that
14496 examine those modules' internals. Closes ticket 21841.
14497 - Simplify our API to launch directory requests, making it more
14498 extensible and less error-prone. Now it's easier to add extra
14499 headers to directory requests. Closes ticket 21646.
14500 - Our base64 decoding functions no longer overestimate the output
14501 space that they need when parsing unpadded inputs. Closes
14503 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
14504 Resolves ticket 22213.
14505 - The logic that directory caches use to spool request to clients,
14506 serving them one part at a time so as not to allocate too much
14507 memory, has been refactored for consistency. Previously there was
14508 a separate spooling implementation per type of spoolable data. Now
14509 there is one common spooling implementation, with extensible data
14510 types. Closes ticket 21651.
14511 - Tor's compression module now supports multiple backends. Part of
14512 the implementation for proposal 278; closes ticket 21663.
14515 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
14516 Closes ticket 21873.
14517 - Correct documentation about the default DataDirectory value.
14518 Closes ticket 21151.
14519 - Document the default behavior of NumEntryGuards and
14520 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
14522 - Document key=value pluggable transport arguments for Bridge lines
14523 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
14524 - Note that bandwidth-limiting options don't affect TCP headers or
14525 DNS. Closes ticket 17170.
14527 o Removed features (configuration options, all in ticket 22060):
14528 - These configuration options are now marked Obsolete, and no longer
14529 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
14530 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
14531 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
14532 in 0.2.9.2-alpha and have now been removed. The previous default
14533 behavior is now always chosen; the previous (less secure) non-
14534 default behavior is now unavailable.
14535 - CloseHSClientCircuitsImmediatelyOnTimeout and
14536 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
14537 0.2.9.2-alpha and now have been removed. HS circuits never close
14538 on circuit build timeout; they have a longer timeout period.
14539 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
14540 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
14541 (and others) to configure listen-only and advertise-only addresses.
14543 o Removed features (tools):
14544 - We've removed the tor-checkkey tool from src/tools. Long ago, we
14545 used it to help people detect RSA keys that were generated by
14546 versions of Debian affected by CVE-2008-0166. But those keys have
14547 been out of circulation for ages, and this tool is no longer
14548 required. Closes ticket 21842.
14551 Changes in version 0.3.0.7 - 2017-05-15
14552 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
14553 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
14554 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
14555 clients are not affected.
14557 o Major bugfixes (hidden service directory, security):
14558 - Fix an assertion failure in the hidden service directory code, which
14559 could be used by an attacker to remotely cause a Tor relay process to
14560 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
14561 should upgrade. This security issue is tracked as TROVE-2017-002.
14562 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
14565 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
14568 o Minor features (future-proofing):
14569 - Tor no longer refuses to download microdescriptors or descriptors
14570 if they are listed as "published in the future". This change will
14571 eventually allow us to stop listing meaningful "published" dates
14572 in microdescriptor consensuses, and thereby allow us to reduce the
14573 resources required to download consensus diffs by over 50%.
14574 Implements part of ticket 21642; implements part of proposal 275.
14576 o Minor bugfixes (Linux seccomp2 sandbox):
14577 - The getpid() system call is now permitted under the Linux seccomp2
14578 sandbox, to avoid crashing with versions of OpenSSL (and other
14579 libraries) that attempt to learn the process's PID by using the
14580 syscall rather than the VDSO code. Fixes bug 21943; bugfix
14584 Changes in version 0.3.0.6 - 2017-04-26
14585 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
14587 With the 0.3.0 series, clients and relays now use Ed25519 keys to
14588 authenticate their link connections to relays, rather than the old
14589 RSA1024 keys that they used before. (Circuit crypto has been
14590 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
14591 the guard selection and replacement algorithm to behave more robustly
14592 in the presence of unreliable networks, and to resist guard-
14595 This series also includes numerous other small features and bugfixes,
14596 along with more groundwork for the upcoming hidden-services revamp.
14598 Per our stable release policy, we plan to support the Tor 0.3.0
14599 release series for at least the next nine months, or for three months
14600 after the first stable release of the 0.3.1 series: whichever is
14601 longer. If you need a release with long-term support, we recommend
14602 that you stay with the 0.2.9 series.
14604 Below are the changes since 0.3.0.5-rc. For a list of all changes
14605 since 0.2.9, see the ReleaseNotes file.
14607 o Minor features (geoip):
14608 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
14611 o Minor bugfixes (control port):
14612 - The GETINFO extra-info/digest/<digest> command was broken because
14613 of a wrong base16 decode return value check, introduced when
14614 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
14616 o Minor bugfixes (crash prevention):
14617 - Fix a (currently untriggerable, but potentially dangerous) crash
14618 bug when base32-encoding inputs whose sizes are not a multiple of
14619 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
14622 Changes in version 0.3.0.5-rc - 2017-04-05
14623 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
14624 0.3.0 release series.
14626 This is the second release candidate in the Tor 0.3.0 series, and has
14627 much fewer changes than the first. If we find no new bugs or
14628 regressions here, the first stable 0.3.0 release will be nearly
14631 o Major bugfixes (crash, directory connections):
14632 - Fix a rare crash when sending a begin cell on a circuit whose
14633 linked directory connection had already been closed. Fixes bug
14634 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
14636 o Major bugfixes (guard selection):
14637 - Fix a guard selection bug where Tor would refuse to bootstrap in
14638 some cases if the user swapped a bridge for another bridge in
14639 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
14640 Reported by "torvlnt33r".
14642 o Minor features (geoip):
14643 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
14646 o Minor bugfix (compilation):
14647 - Fix a warning when compiling hs_service.c. Previously, it had no
14648 exported symbols when compiled for libor.a, resulting in a
14649 compilation warning from clang. Fixes bug 21825; bugfix
14652 o Minor bugfixes (hidden services):
14653 - Make hidden services check for failed intro point connections,
14654 even when they have exceeded their intro point creation limit.
14655 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
14656 - Make hidden services with 8 to 10 introduction points check for
14657 failed circuits immediately after startup. Previously, they would
14658 wait for 5 minutes before performing their first checks. Fixes bug
14659 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
14661 o Minor bugfixes (memory leaks):
14662 - Fix a memory leak when using GETCONF on a port option. Fixes bug
14663 21682; bugfix on 0.3.0.3-alpha.
14665 o Minor bugfixes (relay):
14666 - Avoid a double-marked-circuit warning that could happen when we
14667 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
14670 o Minor bugfixes (tests):
14671 - Run the entry_guard_parse_from_state_full() test with the time set
14672 to a specific date. (The guard state that this test was parsing
14673 contained guards that had expired since the test was first
14674 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
14677 - Update the description of the directory server options in the
14678 manual page, to clarify that a relay no longer needs to set
14679 DirPort in order to be a directory cache. Closes ticket 21720.
14683 Changes in version 0.2.8.13 - 2017-03-03
14684 Tor 0.2.8.13 backports a security fix from later Tor
14685 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
14686 this release, if for some reason they cannot upgrade to a later
14687 release series, and if they build Tor with the --enable-expensive-hardening
14690 Note that support for Tor 0.2.8.x is ending next year: we will not issue
14691 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
14692 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
14694 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
14695 - Fix an integer underflow bug when comparing malformed Tor
14696 versions. This bug could crash Tor when built with
14697 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
14698 0.2.9.8, which were built with -ftrapv by default. In other cases
14699 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
14700 on 0.0.8pre1. Found by OSS-Fuzz.
14702 o Minor features (geoip):
14703 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
14707 Changes in version 0.2.7.7 - 2017-03-03
14708 Tor 0.2.7.7 backports a number of security fixes from later Tor
14709 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
14710 this release, if for some reason they cannot upgrade to a later
14713 Note that support for Tor 0.2.7.x is ending this year: we will not issue
14714 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
14715 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
14717 o Directory authority changes (backport from 0.2.8.5-rc):
14718 - Urras is no longer a directory authority. Closes ticket 19271.
14720 o Directory authority changes (backport from 0.2.9.2-alpha):
14721 - The "Tonga" bridge authority has been retired; the new bridge
14722 authority is "Bifroest". Closes tickets 19728 and 19690.
14724 o Directory authority key updates (backport from 0.2.8.1-alpha):
14725 - Update the V3 identity key for the dannenberg directory authority:
14726 it was changed on 18 November 2015. Closes task 17906. Patch
14729 o Major bugfixes (parsing, security, backport from 0.2.9.8):
14730 - Fix a bug in parsing that could cause clients to read a single
14731 byte past the end of an allocated region. This bug could be used
14732 to cause hardened clients (built with --enable-expensive-hardening)
14733 to crash if they tried to visit a hostile hidden service. Non-
14734 hardened clients are only affected depending on the details of
14735 their platform's memory allocator. Fixes bug 21018; bugfix on
14736 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
14737 2016-12-002 and as CVE-2016-1254.
14739 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
14740 - Stop a crash that could occur when a client running with DNSPort
14741 received a query with multiple address types, and the first
14742 address type was not supported. Found and fixed by Scott Dial.
14743 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
14744 - Prevent a class of security bugs caused by treating the contents
14745 of a buffer chunk as if they were a NUL-terminated string. At
14746 least one such bug seems to be present in all currently used
14747 versions of Tor, and would allow an attacker to remotely crash
14748 most Tor instances, especially those compiled with extra compiler
14749 hardening. With this defense in place, such bugs can't crash Tor,
14750 though we should still fix them as they occur. Closes ticket
14751 20384 (TROVE-2016-10-001).
14753 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
14754 - Avoid a difficult-to-trigger heap corruption attack when extending
14755 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
14756 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
14757 Reported by Guido Vranken.
14759 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
14760 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
14761 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
14763 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
14764 - If OpenSSL fails to generate an RSA key, do not retain a dangling
14765 pointer to the previous (uninitialized) key value. The impact here
14766 should be limited to a difficult-to-trigger crash, if OpenSSL is
14767 running an engine that makes key generation failures possible, or
14768 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
14769 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
14772 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
14773 - Fix an integer underflow bug when comparing malformed Tor
14774 versions. This bug could crash Tor when built with
14775 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
14776 0.2.9.8, which were built with -ftrapv by default. In other cases
14777 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
14778 on 0.0.8pre1. Found by OSS-Fuzz.
14780 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
14781 - Make memwipe() do nothing when passed a NULL pointer or buffer of
14782 zero size. Check size argument to memwipe() for underflow. Fixes
14783 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
14786 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
14787 - Make Tor survive errors involving connections without a
14788 corresponding event object. Previously we'd fail with an
14789 assertion; now we produce a log message. Related to bug 16248.
14791 o Minor features (geoip):
14792 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
14796 Changes in version 0.2.6.11 - 2017-03-03
14797 Tor 0.2.6.11 backports a number of security fixes from later Tor
14798 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
14799 this release, if for some reason they cannot upgrade to a later
14802 Note that support for Tor 0.2.6.x is ending this year: we will not issue
14803 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
14804 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
14806 o Directory authority changes (backport from 0.2.8.5-rc):
14807 - Urras is no longer a directory authority. Closes ticket 19271.
14809 o Directory authority changes (backport from 0.2.9.2-alpha):
14810 - The "Tonga" bridge authority has been retired; the new bridge
14811 authority is "Bifroest". Closes tickets 19728 and 19690.
14813 o Directory authority key updates (backport from 0.2.8.1-alpha):
14814 - Update the V3 identity key for the dannenberg directory authority:
14815 it was changed on 18 November 2015. Closes task 17906. Patch
14818 o Major features (security fixes, backport from 0.2.9.4-alpha):
14819 - Prevent a class of security bugs caused by treating the contents
14820 of a buffer chunk as if they were a NUL-terminated string. At
14821 least one such bug seems to be present in all currently used
14822 versions of Tor, and would allow an attacker to remotely crash
14823 most Tor instances, especially those compiled with extra compiler
14824 hardening. With this defense in place, such bugs can't crash Tor,
14825 though we should still fix them as they occur. Closes ticket
14826 20384 (TROVE-2016-10-001).
14828 o Major bugfixes (parsing, security, backport from 0.2.9.8):
14829 - Fix a bug in parsing that could cause clients to read a single
14830 byte past the end of an allocated region. This bug could be used
14831 to cause hardened clients (built with --enable-expensive-hardening)
14832 to crash if they tried to visit a hostile hidden service. Non-
14833 hardened clients are only affected depending on the details of
14834 their platform's memory allocator. Fixes bug 21018; bugfix on
14835 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
14836 2016-12-002 and as CVE-2016-1254.
14838 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
14839 - Stop a crash that could occur when a client running with DNSPort
14840 received a query with multiple address types, and the first
14841 address type was not supported. Found and fixed by Scott Dial.
14842 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
14844 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
14845 - Fix an error that could cause us to read 4 bytes before the
14846 beginning of an openssl string. This bug could be used to cause
14847 Tor to crash on systems with unusual malloc implementations, or
14848 systems with unusual hardening installed. Fixes bug 17404; bugfix
14851 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
14852 - Avoid a difficult-to-trigger heap corruption attack when extending
14853 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
14854 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
14855 Reported by Guido Vranken.
14857 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
14858 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
14859 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
14861 o Major bugfixes (guard selection, backport from 0.2.7.6):
14862 - Actually look at the Guard flag when selecting a new directory
14863 guard. When we implemented the directory guard design, we
14864 accidentally started treating all relays as if they have the Guard
14865 flag during guard selection, leading to weaker anonymity and worse
14866 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
14869 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
14870 - If OpenSSL fails to generate an RSA key, do not retain a dangling
14871 pointer to the previous (uninitialized) key value. The impact here
14872 should be limited to a difficult-to-trigger crash, if OpenSSL is
14873 running an engine that makes key generation failures possible, or
14874 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
14875 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
14878 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
14879 - Fix an integer underflow bug when comparing malformed Tor
14880 versions. This bug could crash Tor when built with
14881 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
14882 0.2.9.8, which were built with -ftrapv by default. In other cases
14883 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
14884 on 0.0.8pre1. Found by OSS-Fuzz.
14886 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
14887 - Make memwipe() do nothing when passed a NULL pointer or buffer of
14888 zero size. Check size argument to memwipe() for underflow. Fixes
14889 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
14892 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
14893 - Make Tor survive errors involving connections without a
14894 corresponding event object. Previously we'd fail with an
14895 assertion; now we produce a log message. Related to bug 16248.
14897 o Minor features (geoip):
14898 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
14901 o Minor bugfixes (compilation, backport from 0.2.7.6):
14902 - Fix a compilation warning with Clang 3.6: Do not check the
14903 presence of an address which can never be NULL. Fixes bug 17781.
14906 Changes in version 0.2.5.13 - 2017-03-03
14907 Tor 0.2.5.13 backports a number of security fixes from later Tor
14908 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
14909 this release, if for some reason they cannot upgrade to a later
14912 Note that support for Tor 0.2.5.x is ending next year: we will not issue
14913 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
14914 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
14916 o Directory authority changes (backport from 0.2.8.5-rc):
14917 - Urras is no longer a directory authority. Closes ticket 19271.
14919 o Directory authority changes (backport from 0.2.9.2-alpha):
14920 - The "Tonga" bridge authority has been retired; the new bridge
14921 authority is "Bifroest". Closes tickets 19728 and 19690.
14923 o Directory authority key updates (backport from 0.2.8.1-alpha):
14924 - Update the V3 identity key for the dannenberg directory authority:
14925 it was changed on 18 November 2015. Closes task 17906. Patch
14928 o Major features (security fixes, backport from 0.2.9.4-alpha):
14929 - Prevent a class of security bugs caused by treating the contents
14930 of a buffer chunk as if they were a NUL-terminated string. At
14931 least one such bug seems to be present in all currently used
14932 versions of Tor, and would allow an attacker to remotely crash
14933 most Tor instances, especially those compiled with extra compiler
14934 hardening. With this defense in place, such bugs can't crash Tor,
14935 though we should still fix them as they occur. Closes ticket
14936 20384 (TROVE-2016-10-001).
14938 o Major bugfixes (parsing, security, backport from 0.2.9.8):
14939 - Fix a bug in parsing that could cause clients to read a single
14940 byte past the end of an allocated region. This bug could be used
14941 to cause hardened clients (built with --enable-expensive-hardening)
14942 to crash if they tried to visit a hostile hidden service. Non-
14943 hardened clients are only affected depending on the details of
14944 their platform's memory allocator. Fixes bug 21018; bugfix on
14945 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
14946 2016-12-002 and as CVE-2016-1254.
14948 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
14949 - Stop a crash that could occur when a client running with DNSPort
14950 received a query with multiple address types, and the first
14951 address type was not supported. Found and fixed by Scott Dial.
14952 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
14954 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
14955 - Fix an error that could cause us to read 4 bytes before the
14956 beginning of an openssl string. This bug could be used to cause
14957 Tor to crash on systems with unusual malloc implementations, or
14958 systems with unusual hardening installed. Fixes bug 17404; bugfix
14961 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
14962 - Avoid a difficult-to-trigger heap corruption attack when extending
14963 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
14964 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
14965 Reported by Guido Vranken.
14967 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
14968 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
14969 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
14971 o Major bugfixes (guard selection, backport from 0.2.7.6):
14972 - Actually look at the Guard flag when selecting a new directory
14973 guard. When we implemented the directory guard design, we
14974 accidentally started treating all relays as if they have the Guard
14975 flag during guard selection, leading to weaker anonymity and worse
14976 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
14979 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
14980 - If OpenSSL fails to generate an RSA key, do not retain a dangling
14981 pointer to the previous (uninitialized) key value. The impact here
14982 should be limited to a difficult-to-trigger crash, if OpenSSL is
14983 running an engine that makes key generation failures possible, or
14984 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
14985 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
14988 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
14989 - Fix an integer underflow bug when comparing malformed Tor
14990 versions. This bug could crash Tor when built with
14991 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
14992 0.2.9.8, which were built with -ftrapv by default. In other cases
14993 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
14994 on 0.0.8pre1. Found by OSS-Fuzz.
14996 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
14997 - Make memwipe() do nothing when passed a NULL pointer or buffer of
14998 zero size. Check size argument to memwipe() for underflow. Fixes
14999 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
15002 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
15003 - Make Tor survive errors involving connections without a
15004 corresponding event object. Previously we'd fail with an
15005 assertion; now we produce a log message. Related to bug 16248.
15007 o Minor features (geoip):
15008 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
15011 o Minor bugfixes (compilation, backport from 0.2.7.6):
15012 - Fix a compilation warning with Clang 3.6: Do not check the
15013 presence of an address which can never be NULL. Fixes bug 17781.
15015 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
15016 - Check for failures from crypto_early_init, and refuse to continue.
15017 A previous typo meant that we could keep going with an
15018 uninitialized crypto library, and would have OpenSSL initialize
15019 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
15020 when implementing ticket 4900. Patch by "teor".
15022 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
15023 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
15024 a client authorized hidden service. Fixes bug 15823; bugfix
15028 Changes in version 0.2.4.28 - 2017-03-03
15029 Tor 0.2.4.28 backports a number of security fixes from later Tor
15030 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
15031 this release, if for some reason they cannot upgrade to a later
15034 Note that support for Tor 0.2.4.x is ending soon: we will not issue
15035 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
15036 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
15038 o Directory authority changes (backport from 0.2.8.5-rc):
15039 - Urras is no longer a directory authority. Closes ticket 19271.
15041 o Directory authority changes (backport from 0.2.9.2-alpha):
15042 - The "Tonga" bridge authority has been retired; the new bridge
15043 authority is "Bifroest". Closes tickets 19728 and 19690.
15045 o Directory authority key updates (backport from 0.2.8.1-alpha):
15046 - Update the V3 identity key for the dannenberg directory authority:
15047 it was changed on 18 November 2015. Closes task 17906. Patch
15050 o Major features (security fixes, backport from 0.2.9.4-alpha):
15051 - Prevent a class of security bugs caused by treating the contents
15052 of a buffer chunk as if they were a NUL-terminated string. At
15053 least one such bug seems to be present in all currently used
15054 versions of Tor, and would allow an attacker to remotely crash
15055 most Tor instances, especially those compiled with extra compiler
15056 hardening. With this defense in place, such bugs can't crash Tor,
15057 though we should still fix them as they occur. Closes ticket
15058 20384 (TROVE-2016-10-001).
15060 o Major bugfixes (parsing, security, backport from 0.2.9.8):
15061 - Fix a bug in parsing that could cause clients to read a single
15062 byte past the end of an allocated region. This bug could be used
15063 to cause hardened clients (built with --enable-expensive-hardening)
15064 to crash if they tried to visit a hostile hidden service. Non-
15065 hardened clients are only affected depending on the details of
15066 their platform's memory allocator. Fixes bug 21018; bugfix on
15067 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
15068 2016-12-002 and as CVE-2016-1254.
15070 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
15071 - Fix an error that could cause us to read 4 bytes before the
15072 beginning of an openssl string. This bug could be used to cause
15073 Tor to crash on systems with unusual malloc implementations, or
15074 systems with unusual hardening installed. Fixes bug 17404; bugfix
15077 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
15078 - Avoid a difficult-to-trigger heap corruption attack when extending
15079 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
15080 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
15081 Reported by Guido Vranken.
15083 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
15084 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
15085 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
15087 o Major bugfixes (guard selection, backport from 0.2.7.6):
15088 - Actually look at the Guard flag when selecting a new directory
15089 guard. When we implemented the directory guard design, we
15090 accidentally started treating all relays as if they have the Guard
15091 flag during guard selection, leading to weaker anonymity and worse
15092 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
15095 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
15096 - If OpenSSL fails to generate an RSA key, do not retain a dangling
15097 pointer to the previous (uninitialized) key value. The impact here
15098 should be limited to a difficult-to-trigger crash, if OpenSSL is
15099 running an engine that makes key generation failures possible, or
15100 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
15101 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
15104 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
15105 - Fix an integer underflow bug when comparing malformed Tor
15106 versions. This bug could crash Tor when built with
15107 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
15108 0.2.9.8, which were built with -ftrapv by default. In other cases
15109 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
15110 on 0.0.8pre1. Found by OSS-Fuzz.
15112 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
15113 - Make memwipe() do nothing when passed a NULL pointer or buffer of
15114 zero size. Check size argument to memwipe() for underflow. Fixes
15115 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
15118 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
15119 - Make Tor survive errors involving connections without a
15120 corresponding event object. Previously we'd fail with an
15121 assertion; now we produce a log message. Related to bug 16248.
15123 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
15124 - Make it harder for attackers to overload hidden services with
15125 introductions, by blocking multiple introduction requests on the
15126 same circuit. Resolves ticket 15515.
15128 o Minor features (geoip):
15129 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
15132 o Minor bugfixes (compilation, backport from 0.2.7.6):
15133 - Fix a compilation warning with Clang 3.6: Do not check the
15134 presence of an address which can never be NULL. Fixes bug 17781.
15136 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
15137 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
15138 a client authorized hidden service. Fixes bug 15823; bugfix
15142 Changes in version 0.3.0.4-rc - 2017-03-01
15143 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
15144 0.3.0 release series, and introduces a few reliability features to
15145 keep them from coming back.
15147 This is the first release candidate in the Tor 0.3.0 series. If we
15148 find no new bugs or regressions here, the first stable 0.3.0 release
15149 will be nearly identical to it.
15151 o Major bugfixes (bridges):
15152 - When the same bridge is configured multiple times with the same
15153 identity, but at different address:port combinations, treat those
15154 bridge instances as separate guards. This fix restores the ability
15155 of clients to configure the same bridge with multiple pluggable
15156 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
15158 o Major bugfixes (hidden service directory v3):
15159 - Stop crashing on a failed v3 hidden service descriptor lookup
15160 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
15162 o Major bugfixes (parsing):
15163 - When parsing a malformed content-length field from an HTTP
15164 message, do not read off the end of the buffer. This bug was a
15165 potential remote denial-of-service attack against Tor clients and
15166 relays. A workaround was released in October 2016, to prevent this
15167 bug from crashing Tor. This is a fix for the underlying issue,
15168 which should no longer matter (if you applied the earlier patch).
15169 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
15170 using AFL (http://lcamtuf.coredump.cx/afl/).
15171 - Fix an integer underflow bug when comparing malformed Tor
15172 versions. This bug could crash Tor when built with
15173 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
15174 0.2.9.8, which were built with -ftrapv by default. In other cases
15175 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
15176 on 0.0.8pre1. Found by OSS-Fuzz.
15178 o Minor feature (protocol versioning):
15179 - Add new protocol version for proposal 224. HSIntro now advertises
15180 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
15182 o Minor features (directory authorities):
15183 - Directory authorities now reject descriptors that claim to be
15184 malformed versions of Tor. Helps prevent exploitation of
15186 - Reject version numbers with components that exceed INT32_MAX.
15187 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
15188 Fixes bug 21450; bugfix on 0.0.8pre1.
15189 - Directory authorities now reject relays running versions
15190 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
15191 suffer from bug 20499 and don't keep their consensus cache
15192 up-to-date. Resolves ticket 20509.
15194 o Minor features (geoip):
15195 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
15198 o Minor features (reliability, crash):
15199 - Try better to detect problems in buffers where they might grow (or
15200 think they have grown) over 2 GB in size. Diagnostic for
15203 o Minor features (testing):
15204 - During 'make test-network-all', if tor logs any warnings, ask
15205 chutney to output them. Requires a recent version of chutney with
15206 the 21572 patch. Implements 21570.
15208 o Minor bugfixes (certificate expiration time):
15209 - Avoid using link certificates that don't become valid till some
15210 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
15212 o Minor bugfixes (code correctness):
15213 - Repair a couple of (unreachable or harmless) cases of the risky
15214 comparison-by-subtraction pattern that caused bug 21278.
15215 - Remove a redundant check for the UseEntryGuards option from the
15216 options_transition_affects_guards() function. Fixes bug 21492;
15217 bugfix on 0.3.0.1-alpha.
15219 o Minor bugfixes (directory mirrors):
15220 - Allow relays to use directory mirrors without a DirPort: these
15221 relays need to be contacted over their ORPorts using a begindir
15222 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
15223 - Clarify the message logged when a remote relay is unexpectedly
15224 missing an ORPort or DirPort: users were confusing this with a
15225 local port. Fixes another case of bug 20711; bugfix
15228 o Minor bugfixes (guards):
15229 - Don't warn about a missing guard state on timeout-measurement
15230 circuits: they aren't supposed to be using guards. Fixes an
15231 instance of bug 21007; bugfix on 0.3.0.1-alpha.
15232 - Silence a BUG() warning when attempting to use a guard whose
15233 descriptor we don't know, and make this scenario less likely to
15234 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
15236 o Minor bugfixes (hidden service):
15237 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
15238 cells. Previously, we were using sizeof() on a pointer, instead of
15239 the real destination buffer. Fortunately, that value was only used
15240 to double-check that there was enough room--which was already
15241 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
15243 o Minor bugfixes (testing):
15244 - Fix Raspbian build issues related to missing socket errno in
15245 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
15247 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
15248 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
15249 - Use bash in src/test/test-network.sh. This ensures we reliably
15250 call chutney's newer tools/test-network.sh when available. Fixes
15251 bug 21562; bugfix on 0.2.9.1-alpha.
15254 - Small fixes to the fuzzing documentation. Closes ticket 21472.
15257 Changes in version 0.2.9.10 - 2017-03-01
15258 Tor 0.2.9.10 backports a security fix from later Tor release. It also
15259 includes fixes for some major issues affecting directory authorities,
15260 LibreSSL compatibility, and IPv6 correctness.
15262 The Tor 0.2.9.x release series is now marked as a long-term-support
15263 series. We intend to backport security fixes to 0.2.9.x until at
15264 least January of 2020.
15266 o Major bugfixes (directory authority, 0.3.0.3-alpha):
15267 - During voting, when marking a relay as a probable sybil, do not
15268 clear its BadExit flag: sybils can still be bad in other ways
15269 too. (We still clear the other flags.) Fixes bug 21108; bugfix
15272 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
15273 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
15274 any IPv6 addresses. Instead, only reject a port over IPv6 if the
15275 exit policy rejects that port on more than an IPv6 /16 of
15276 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
15277 which rejected a relay's own IPv6 address by default. Fixes bug
15278 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
15280 o Major bugfixes (parsing, also in 0.3.0.4-rc):
15281 - Fix an integer underflow bug when comparing malformed Tor
15282 versions. This bug could crash Tor when built with
15283 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
15284 0.2.9.8, which were built with -ftrapv by default. In other cases
15285 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
15286 on 0.0.8pre1. Found by OSS-Fuzz.
15288 o Minor features (directory authorities, also in 0.3.0.4-rc):
15289 - Directory authorities now reject descriptors that claim to be
15290 malformed versions of Tor. Helps prevent exploitation of
15292 - Reject version numbers with components that exceed INT32_MAX.
15293 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
15294 Fixes bug 21450; bugfix on 0.0.8pre1.
15296 o Minor features (geoip):
15297 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
15300 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
15301 - Autoconf now checks to determine if OpenSSL structures are opaque,
15302 instead of explicitly checking for OpenSSL version numbers. Part
15304 - Support building with recent LibreSSL code that uses opaque
15305 structures. Closes ticket 21359.
15307 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
15308 - Repair a couple of (unreachable or harmless) cases of the risky
15309 comparison-by-subtraction pattern that caused bug 21278.
15311 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
15312 - The tor-resolve command line tool now rejects hostnames over 255
15313 characters in length. Previously, it would silently truncate them,
15314 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
15315 Patch by "junglefowl".
15318 Changes in version 0.3.0.3-alpha - 2017-02-03
15319 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
15320 0.3.0.x development series, including some that could cause
15321 authorities to behave badly. There is also a fix for a longstanding
15322 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
15323 includes some smaller features and bugfixes.
15325 The Tor 0.3.0.x release series is now in patch-freeze: no additional
15326 features will be considered for inclusion in 0.3.0.x. We suspect that
15327 some bugs will probably remain, however, and we encourage people to
15330 o Major bugfixes (directory authority):
15331 - During voting, when marking a relay as a probable sybil, do not
15332 clear its BadExit flag: sybils can still be bad in other ways
15333 too. (We still clear the other flags.) Fixes bug 21108; bugfix
15335 - When deciding whether we have just found a router to be reachable,
15336 do not penalize it for not having performed an Ed25519 link
15337 handshake if it does not claim to support an Ed25519 handshake.
15338 Previously, we would treat such relays as non-running. Fixes bug
15339 21107; bugfix on 0.3.0.1-alpha.
15341 o Major bugfixes (entry guards):
15342 - Stop trying to build circuits through entry guards for which we
15343 have no descriptor. Also, stop crashing in the case that we *do*
15344 accidentally try to build a circuit in such a state. Fixes bug
15345 21242; bugfix on 0.3.0.1-alpha.
15347 o Major bugfixes (IPv6 Exits):
15348 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
15349 any IPv6 addresses. Instead, only reject a port over IPv6 if the
15350 exit policy rejects that port on more than an IPv6 /16 of
15351 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
15352 which rejected a relay's own IPv6 address by default. Fixes bug
15353 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
15355 o Minor feature (client):
15356 - Enable IPv6 traffic on the SocksPort by default. To disable this,
15357 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
15359 o Minor feature (fallback scripts):
15360 - Add a check_existing mode to updateFallbackDirs.py, which checks
15361 if fallbacks in the hard-coded list are working. Closes ticket
15362 20174. Patch by haxxpop.
15364 o Minor features (ciphersuite selection):
15365 - Clients now advertise a list of ciphersuites closer to the ones
15366 preferred by Firefox. Closes part of ticket 15426.
15367 - Allow relays to accept a wider range of ciphersuites, including
15368 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
15370 o Minor features (controller, configuration):
15371 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
15372 and so on, now comes with a __*Port variant that will not be saved
15373 to the torrc file by the controller's SAVECONF command. This
15374 change allows TorBrowser to set up a single-use domain socket for
15375 each time it launches Tor. Closes ticket 20956.
15376 - The GETCONF command can now query options that may only be
15377 meaningful in context-sensitive lists. This allows the controller
15378 to query the mixed SocksPort/__SocksPort style options introduced
15379 in feature 20956. Implements ticket 21300.
15381 o Minor features (portability, compilation):
15382 - Autoconf now checks to determine if OpenSSL structures are opaque,
15383 instead of explicitly checking for OpenSSL version numbers. Part
15385 - Support building with recent LibreSSL code that uses opaque
15386 structures. Closes ticket 21359.
15388 o Minor features (relay):
15389 - We now allow separation of exit and relay traffic to different
15390 source IP addresses, using the OutboundBindAddressExit and
15391 OutboundBindAddressOR options respectively. Closes ticket 17975.
15392 Written by Michael Sonntag.
15394 o Minor bugfix (logging):
15395 - Don't recommend the use of Tor2web in non-anonymous mode.
15396 Recommending Tor2web is a bad idea because the client loses all
15397 anonymity. Tor2web should only be used in specific cases by users
15398 who *know* and understand the issues. Fixes bug 21294; bugfix
15401 o Minor bugfixes (client):
15402 - Always recover from failures in extend_info_from_node(), in an
15403 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
15404 bugfix on 0.2.3.1-alpha.
15406 o Minor bugfixes (client, entry guards):
15407 - Fix a bug warning (with backtrace) when we fail a channel that
15408 circuits to fallback directories on it. Fixes bug 21128; bugfix
15410 - Fix a spurious bug warning (with backtrace) when removing an
15411 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
15412 - Fix a bug of the new guard algorithm where tor could stall for up
15413 to 10 minutes before retrying a guard after a long period of no
15414 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
15415 - Do not try to build circuits until we have descriptors for our
15416 primary entry guards. Related to fix for bug 21242.
15418 o Minor bugfixes (configure, autoconf):
15419 - Rename the configure option --enable-expensive-hardening to
15420 --enable-fragile-hardening. Expensive hardening makes the tor
15421 daemon abort when some kinds of issues are detected. Thus, it
15422 makes tor more at risk of remote crashes but safer against RCE or
15423 heartbleed bug category. We now try to explain this issue in a
15424 message from the configure script. Fixes bug 21290; bugfix
15427 o Minor bugfixes (controller):
15428 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
15429 20824; bugfix on 0.3.0.1-alpha.
15431 o Minor bugfixes (hidden service):
15432 - Clean up the code for expiring intro points with no associated
15433 circuits. It was causing, rarely, a service with some expiring
15434 introduction points to not open enough additional introduction
15435 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
15436 - Stop setting the torrc option HiddenServiceStatistics to "0" just
15437 because we're not a bridge or relay. Instead, we preserve whatever
15438 value the user set (or didn't set). Fixes bug 21150; bugfix
15440 - Resolve two possible underflows which could lead to creating and
15441 closing a lot of introduction point circuits in a non-stop loop.
15442 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
15444 o Minor bugfixes (portability):
15445 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
15446 It is supported by OpenBSD itself, and also by most OpenBSD
15447 variants (such as Bitrig). Fixes bug 20980; bugfix
15449 - When mapping a file of length greater than SIZE_MAX, do not
15450 silently truncate its contents. This issue could occur on 32 bit
15451 systems with large file support and files which are larger than 4
15452 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
15454 o Minor bugfixes (tor-resolve):
15455 - The tor-resolve command line tool now rejects hostnames over 255
15456 characters in length. Previously, it would silently truncate them,
15457 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
15458 Patch by "junglefowl".
15460 o Minor bugfixes (Windows services):
15461 - Be sure to initialize the monotonic time subsystem before using
15462 it, even when running as an NT service. Fixes bug 21356; bugfix
15466 Changes in version 0.3.0.2-alpha - 2017-01-23
15467 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
15468 cause relays and clients to crash, even if they were not built with
15469 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
15470 versions, and also affects 0.3.0.1-alpha: all relays running an affected
15471 version should upgrade.
15473 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
15474 time-to-live values, makes directory authorities enforce the 1-to-1
15475 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
15476 client-side onion service reachability bug, does better at selecting
15477 the set of fallback directories, and more.
15479 o Major bugfixes (security, also in 0.2.9.9):
15480 - Downgrade the "-ftrapv" option from "always on" to "only on when
15481 --enable-expensive-hardening is provided." This hardening option, like
15482 others, can turn survivable bugs into crashes--and having it on by
15483 default made a (relatively harmless) integer overflow bug into a
15484 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
15487 o Major features (security):
15488 - Change the algorithm used to decide DNS TTLs on client and server
15489 side, to better resist DNS-based correlation attacks like the
15490 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
15491 Feamster. Now relays only return one of two possible DNS TTL
15492 values, and clients are willing to believe DNS TTL values up to 3
15493 hours long. Closes ticket 19769.
15495 o Major features (directory authority, security):
15496 - The default for AuthDirPinKeys is now 1: directory authorities
15497 will reject relays where the RSA identity key matches a previously
15498 seen value, but the Ed25519 key has changed. Closes ticket 18319.
15500 o Major bugfixes (client, guard, crash):
15501 - In circuit_get_global_origin_list(), return the actual list of
15502 origin circuits. The previous version of this code returned the
15503 list of all the circuits, and could have caused strange bugs,
15504 including possible crashes. Fixes bug 21118; bugfix
15507 o Major bugfixes (client, onion service, also in 0.2.9.9):
15508 - Fix a client-side onion service reachability bug, where multiple
15509 socks requests to an onion service (or a single slow request)
15510 could cause us to mistakenly mark some of the service's
15511 introduction points as failed, and we cache that failure so
15512 eventually we run out and can't reach the service. Also resolves a
15513 mysterious "Remote server sent bogus reason code 65021" log
15514 warning. The bug was introduced in ticket 17218, where we tried to
15515 remember the circuit end reason as a uint16_t, which mangled
15516 negative values. Partially fixes bug 21056 and fixes bug 20307;
15517 bugfix on 0.2.8.1-alpha.
15519 o Major bugfixes (DNS):
15520 - Fix a bug that prevented exit nodes from caching DNS records for
15521 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
15523 o Minor features (controller):
15524 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
15525 shared-random values to the controller. Closes ticket 19925.
15527 o Minor features (entry guards):
15528 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
15529 break regression tests.
15530 - Require UseEntryGuards when UseBridges is set, in order to make
15531 sure bridges aren't bypassed. Resolves ticket 20502.
15533 o Minor features (fallback directories):
15534 - Select 200 fallback directories for each release. Closes
15536 - Allow 3 fallback relays per operator, which is safe now that we
15537 are choosing 200 fallback relays. Closes ticket 20912.
15538 - Exclude relays affected by bug 20499 from the fallback list.
15539 Exclude relays from the fallback list if they are running versions
15540 known to be affected by bug 20499, or if in our tests they deliver
15541 a stale consensus (i.e. one that expired more than 24 hours ago).
15542 Closes ticket 20539.
15543 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
15545 - Require fallback directories to have the same address and port for
15546 7 days (now that we have enough relays with this stability).
15547 Relays whose OnionOO stability timer is reset on restart by bug
15548 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
15549 this issue. Closes ticket 20880; maintains short-term fix
15551 - Require fallbacks to have flags for 90% of the time (weighted
15552 decaying average), rather than 95%. This allows at least 73% of
15553 clients to bootstrap in the first 5 seconds without contacting an
15554 authority. Part of ticket 18828.
15555 - Annotate updateFallbackDirs.py with the bandwidth and consensus
15556 weight for each candidate fallback. Closes ticket 20878.
15557 - Make it easier to change the output sort order of fallbacks.
15558 Closes ticket 20822.
15559 - Display the relay fingerprint when downloading consensuses from
15560 fallbacks. Closes ticket 20908.
15562 o Minor features (geoip, also in 0.2.9.9):
15563 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
15566 o Minor features (next-gen onion service directories):
15567 - Remove the "EnableOnionServicesV3" consensus parameter that we
15568 introduced in 0.3.0.1-alpha: relays are now always willing to act
15569 as v3 onion service directories. Resolves ticket 19899.
15571 o Minor features (linting):
15572 - Enhance the changes file linter to warn on Tor versions that are
15573 prefixed with "tor-". Closes ticket 21096.
15575 o Minor features (logging):
15576 - In several places, describe unset ed25519 keys as "<unset>",
15577 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
15579 o Minor bugfix (control protocol):
15580 - The reply to a "GETINFO config/names" request via the control
15581 protocol now spells the type "Dependent" correctly. This is a
15582 breaking change in the control protocol. (The field seems to be
15583 ignored by the most common known controllers.) Fixes bug 18146;
15584 bugfix on 0.1.1.4-alpha.
15586 o Minor bugfixes (bug resilience):
15587 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
15588 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
15589 Hans Jerry Illikainen.
15591 o Minor bugfixes (build):
15592 - Replace obsolete Autoconf macros with their modern equivalent and
15593 prevent similar issues in the future. Fixes bug 20990; bugfix
15596 o Minor bugfixes (client, guards):
15597 - Fix bug where Tor would think that there are circuits waiting for
15598 better guards even though those circuits have been freed. Fixes
15599 bug 21142; bugfix on 0.3.0.1-alpha.
15601 o Minor bugfixes (config):
15602 - Don't assert on startup when trying to get the options list and
15603 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
15604 options so of course they aren't ready yet. Fixes bug 21062;
15605 bugfix on 0.2.9.3-alpha.
15607 o Minor bugfixes (controller):
15608 - Make the GETINFO interface for inquiring about entry guards
15609 support the new guards backend. Fixes bug 20823; bugfix
15612 o Minor bugfixes (dead code):
15613 - Remove a redundant check for PidFile changes at runtime in
15614 options_transition_allowed(): this check is already performed
15615 regardless of whether the sandbox is active. Fixes bug 21123;
15616 bugfix on 0.2.5.4-alpha.
15618 o Minor bugfixes (documentation):
15619 - Update the tor manual page to document every option that can not
15620 be changed while tor is running. Fixes bug 21122.
15622 o Minor bugfixes (fallback directories):
15623 - Stop failing when a relay has no uptime data in
15624 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
15625 - Avoid checking fallback candidates' DirPorts if they are down in
15626 OnionOO. When a relay operator has multiple relays, this
15627 prioritizes relays that are up over relays that are down. Fixes
15628 bug 20926; bugfix on 0.2.8.3-alpha.
15629 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
15630 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
15632 o Minor bugfixes (guards, bootstrapping):
15633 - When connecting to a directory guard during bootstrap, do not mark
15634 the guard as successful until we receive a good-looking directory
15635 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
15637 o Minor bugfixes (onion services):
15638 - Fix the config reload pruning of old vs new services so it
15639 actually works when both ephemeral and non-ephemeral services are
15640 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
15641 - Allow the number of introduction points to be as low as 0, rather
15642 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
15644 o Minor bugfixes (IPv6):
15645 - Make IPv6-using clients try harder to find an IPv6 directory
15646 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
15647 - When IPv6 addresses have not been downloaded yet (microdesc
15648 consensus documents don't list relay IPv6 addresses), use hard-
15649 coded addresses for authorities, fallbacks, and configured
15650 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
15651 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
15653 o Minor bugfixes (memory leaks):
15654 - Fix a memory leak when configuring hidden services. Fixes bug
15655 20987; bugfix on 0.3.0.1-alpha.
15657 o Minor bugfixes (portability, also in 0.2.9.9):
15658 - Avoid crashing when Tor is built using headers that contain
15659 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
15660 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
15662 - Fix Libevent detection on platforms without Libevent 1 headers
15663 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
15665 o Minor bugfixes (relay):
15666 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
15667 initializing the keys would reset the DataDirectory to 0700
15668 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
15669 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
15671 o Minor bugfixes (testing):
15672 - Remove undefined behavior from the backtrace generator by removing
15673 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
15675 o Minor bugfixes (unit tests):
15676 - Allow the unit tests to pass even when DNS lookups of bogus
15677 addresses do not fail as expected. Fixes bug 20862 and 20863;
15678 bugfix on unit tests introduced in 0.2.8.1-alpha
15679 through 0.2.9.4-alpha.
15681 o Code simplification and refactoring:
15682 - Refactor code to manipulate global_origin_circuit_list into
15683 separate functions. Closes ticket 20921.
15685 o Documentation (formatting):
15686 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
15687 blocks were incorrectly appearing. Closes ticket 20885.
15689 o Documentation (man page):
15690 - Clarify many options in tor.1 and add some min/max values for
15691 HiddenService options. Closes ticket 21058.
15694 Changes in version 0.2.9.9 - 2017-01-23
15695 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
15696 cause relays and clients to crash, even if they were not built with
15697 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
15698 versions, and also affects 0.3.0.1-alpha: all relays running an affected
15699 version should upgrade.
15701 This release also resolves a client-side onion service reachability
15702 bug, and resolves a pair of small portability issues.
15704 o Major bugfixes (security):
15705 - Downgrade the "-ftrapv" option from "always on" to "only on when
15706 --enable-expensive-hardening is provided." This hardening option,
15707 like others, can turn survivable bugs into crashes -- and having
15708 it on by default made a (relatively harmless) integer overflow bug
15709 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
15710 bugfix on 0.2.9.1-alpha.
15712 o Major bugfixes (client, onion service):
15713 - Fix a client-side onion service reachability bug, where multiple
15714 socks requests to an onion service (or a single slow request)
15715 could cause us to mistakenly mark some of the service's
15716 introduction points as failed, and we cache that failure so
15717 eventually we run out and can't reach the service. Also resolves a
15718 mysterious "Remote server sent bogus reason code 65021" log
15719 warning. The bug was introduced in ticket 17218, where we tried to
15720 remember the circuit end reason as a uint16_t, which mangled
15721 negative values. Partially fixes bug 21056 and fixes bug 20307;
15722 bugfix on 0.2.8.1-alpha.
15724 o Minor features (geoip):
15725 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
15728 o Minor bugfixes (portability):
15729 - Avoid crashing when Tor is built using headers that contain
15730 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
15731 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
15733 - Fix Libevent detection on platforms without Libevent 1 headers
15734 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
15737 Changes in version 0.3.0.1-alpha - 2016-12-19
15738 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
15739 series. It strengthens Tor's link and circuit handshakes by
15740 identifying relays by their Ed25519 keys, improves the algorithm that
15741 clients use to choose and maintain their list of guards, and includes
15742 additional backend support for the next-generation hidden service
15743 design. It also contains numerous other small features and
15744 improvements to security, correctness, and performance.
15746 Below are the changes since 0.2.9.8.
15748 o Major features (guard selection algorithm):
15749 - Tor's guard selection algorithm has been redesigned from the
15750 ground up, to better support unreliable networks and restrictive
15751 sets of entry nodes, and to better resist guard-capture attacks by
15752 hostile local networks. Implements proposal 271; closes
15755 o Major features (next-generation hidden services):
15756 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
15757 prop224 aka "Next Generation Hidden Services". Service and clients
15758 don't use this functionality yet. Closes ticket 19043. Based on
15759 initial code by Alec Heifetz.
15760 - Relays now support the HSDir version 3 protocol, so that they can
15761 can store and serve v3 descriptors. This is part of the next-
15762 generation onion service work detailed in proposal 224. Closes
15765 o Major features (protocol, ed25519 identity keys):
15766 - Relays now use Ed25519 to prove their Ed25519 identities and to
15767 one another, and to clients. This algorithm is faster and more
15768 secure than the RSA-based handshake we've been doing until now.
15769 Implements the second big part of proposal 220; Closes
15771 - Clients now support including Ed25519 identity keys in the EXTEND2
15772 cells they generate. By default, this is controlled by a consensus
15773 parameter, currently disabled. You can turn this feature on for
15774 testing by setting ExtendByEd25519ID in your configuration. This
15775 might make your traffic appear different than the traffic
15776 generated by other users, however. Implements part of ticket
15777 15056; part of proposal 220.
15778 - Relays now understand requests to extend to other relays by their
15779 Ed25519 identity keys. When an Ed25519 identity key is included in
15780 an EXTEND2 cell, the relay will only extend the circuit if the
15781 other relay can prove ownership of that identity. Implements part
15782 of ticket 15056; part of proposal 220.
15784 o Major bugfixes (scheduler):
15785 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
15786 caused the channel scheduler to behave more or less randomly,
15787 rather than preferring channels with higher-priority circuits.
15788 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
15790 o Minor features (controller):
15791 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
15792 rather than "unrecognized." Closes ticket 20389; patch from
15795 o Minor features (diagnostic, directory client):
15796 - Warn when we find an unexpected inconsistency in directory
15797 download status objects. Prevents some negative consequences of
15800 o Minor features (directory authority):
15801 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
15802 default) to control whether authorities should try to probe relays
15803 by their Ed25519 link keys. This option will go away in a few
15804 releases--unless we encounter major trouble in our ed25519 link
15805 protocol rollout, in which case it will serve as a safety option.
15807 o Minor features (directory cache):
15808 - Relays and bridges will now refuse to serve the consensus they
15809 have if they know it is too old for a client to use. Closes
15812 o Minor features (ed25519 link handshake):
15813 - Advertise support for the ed25519 link handshake using the
15814 subprotocol-versions mechanism, so that clients can tell which
15815 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
15817 o Minor features (fingerprinting resistance, authentication):
15818 - Extend the length of RSA keys used for TLS link authentication to
15819 2048 bits. (These weren't used for forward secrecy; for forward
15820 secrecy, we used P256.) Closes ticket 13752.
15822 o Minor features (infrastructure):
15823 - Implement smartlist_add_strdup() function. Replaces the use of
15824 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
15826 o Minor bugfixes (client):
15827 - When clients that use bridges start up with a cached consensus on
15828 disk, they were ignoring it and downloading a new one. Now they
15829 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
15831 o Minor bugfixes (configuration):
15832 - Accept non-space whitespace characters after the severity level in
15833 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
15834 - Support "TByte" and "TBytes" units in options given in bytes.
15835 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
15836 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
15838 o Minor bugfixes (consensus weight):
15839 - Add new consensus method that initializes bw weights to 1 instead
15840 of 0. This prevents a zero weight from making it all the way to
15841 the end (happens in small testing networks) and causing an error.
15842 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
15844 o Minor bugfixes (descriptors):
15845 - Correctly recognise downloaded full descriptors as valid, even
15846 when using microdescriptors as circuits. This affects clients with
15847 FetchUselessDescriptors set, and may affect directory authorities.
15848 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
15850 o Minor bugfixes (directory system):
15851 - Download all consensus flavors, descriptors, and authority
15852 certificates when FetchUselessDescriptors is set, regardless of
15853 whether tor is a directory cache or not. Fixes bug 20667; bugfix
15854 on all recent tor versions.
15855 - Bridges and relays now use microdescriptors (like clients do)
15856 rather than old-style router descriptors. Now bridges will blend
15857 in with clients in terms of the circuits they build. Fixes bug
15858 6769; bugfix on 0.2.3.2-alpha.
15860 o Minor bugfixes (ed25519 certificates):
15861 - Correctly interpret ed25519 certificates that would expire some
15862 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
15864 o Minor bugfixes (hidden services):
15865 - Stop ignoring misconfigured hidden services. Instead, refuse to
15866 start tor until the misconfigurations have been corrected. Fixes
15867 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
15870 o Minor bugfixes (memory leak at exit):
15871 - Fix a small harmless memory leak at exit of the previously unused
15872 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
15875 o Minor bugfixes (util):
15876 - When finishing writing a file to disk, if we were about to replace
15877 the file with the temporary file created before and we fail to
15878 replace it, remove the temporary file so it doesn't stay on disk.
15879 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
15881 o Minor bugfixes (Windows):
15882 - Check for getpagesize before using it to mmap files. This fixes
15883 compilation in some MinGW environments. Fixes bug 20530; bugfix on
15884 0.1.2.1-alpha. Reported by "ice".
15886 o Code simplification and refactoring:
15887 - Abolish all global guard context in entrynodes.c; replace with new
15888 guard_selection_t structure as preparation for proposal 271.
15889 Closes ticket 19858.
15890 - Introduce rend_service_is_ephemeral() that tells if given onion
15891 service is ephemeral. Replace unclear NULL-checkings for service
15892 directory with this function. Closes ticket 20526.
15893 - Extract magic numbers in circuituse.c into defined variables.
15894 - Refactor circuit_is_available_for_use to remove unnecessary check.
15895 - Refactor circuit_predict_and_launch_new for readability and
15896 testability. Closes ticket 18873.
15897 - Refactor large if statement in purpose_needs_anonymity to use
15898 switch statement instead. Closes part of ticket 20077.
15899 - Refactor the hashing API to return negative values for errors, as
15900 is done as throughout the codebase. Closes ticket 20717.
15901 - Remove data structures that were used to index or_connection
15902 objects by their RSA identity digests. These structures are fully
15903 redundant with the similar structures used in the
15904 channel abstraction.
15905 - Remove duplicate code in the channel_write_*cell() functions.
15906 Closes ticket 13827; patch from Pingl.
15907 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
15908 use only purpose_needs_anonymity. Closes part of ticket 20077.
15909 - The code to generate and parse EXTEND and EXTEND2 cells has been
15910 replaced with code automatically generated by the
15914 - Include the "TBits" unit in Tor's man page. Fixes part of bug
15915 20622; bugfix on 0.2.5.1-alpha.
15916 - Change '1' to 'weight_scale' in consensus bw weights calculation
15917 comments, as that is reality. Closes ticket 20273. Patch
15919 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
15920 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
15922 - Stop the man page from incorrectly stating that HiddenServiceDir
15923 must already exist. Fixes 20486.
15924 - Clarify that when ClientRejectInternalAddresses is enabled (which
15925 is the default), multicast DNS hostnames for machines on the local
15926 network (of the form *.local) are also rejected. Closes
15929 o Removed features:
15930 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
15931 limit for relays running on a single IP applies to authority IP
15932 addresses as well as to non-authority IP addresses. Closes
15934 - The UseDirectoryGuards torrc option no longer exists: all users
15935 that use entry guards will also use directory guards. Related to
15936 proposal 271; implements part of ticket 20831.
15939 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
15940 from "overcaffeinated".
15941 - Perform the coding style checks when running the tests and fail
15942 when coding style violations are found. Closes ticket 5500.
15943 - Add tests for networkstatus_compute_bw_weights_v10.
15944 - Add unit tests circuit_predict_and_launch_new.
15945 - Extract dummy_origin_circuit_new so it can be used by other
15949 Changes in version 0.2.8.12 - 2016-12-19
15950 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
15951 below) where Tor clients could crash when attempting to visit a
15952 hostile hidden service. Clients are recommended to upgrade as packages
15953 become available for their systems.
15955 It also includes an updated list of fallback directories, backported
15958 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
15959 backported to 0.2.8 in the future.
15961 o Major bugfixes (parsing, security, backported from 0.2.9.8):
15962 - Fix a bug in parsing that could cause clients to read a single
15963 byte past the end of an allocated region. This bug could be used
15964 to cause hardened clients (built with --enable-expensive-hardening)
15965 to crash if they tried to visit a hostile hidden service. Non-
15966 hardened clients are only affected depending on the details of
15967 their platform's memory allocator. Fixes bug 21018; bugfix on
15968 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
15969 2016-12-002 and as CVE-2016-1254.
15971 o Minor features (fallback directory list, backported from 0.2.9.8):
15972 - Replace the 81 remaining fallbacks of the 100 originally
15973 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
15974 fallbacks (123 new, 54 existing, 27 removed) generated in December
15975 2016. Resolves ticket 20170.
15977 o Minor features (geoip, backported from 0.2.9.7-rc):
15978 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
15982 Changes in version 0.2.9.8 - 2016-12-19
15983 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
15985 The Tor 0.2.9 series makes mandatory a number of security features
15986 that were formerly optional. It includes support for a new shared-
15987 randomness protocol that will form the basis for next generation
15988 hidden services, includes a single-hop hidden service mode for
15989 optimizing .onion services that don't actually want to be hidden,
15990 tries harder not to overload the directory authorities with excessive
15991 downloads, and supports a better protocol versioning scheme for
15992 improved compatibility with other implementations of the Tor protocol.
15994 And of course, there are numerous other bugfixes and improvements.
15996 This release also includes a fix for a medium-severity issue (bug
15997 21018 below) where Tor clients could crash when attempting to visit a
15998 hostile hidden service. Clients are recommended to upgrade as packages
15999 become available for their systems.
16001 Below are the changes since 0.2.9.7-rc. For a list of all changes
16002 since 0.2.8, see the ReleaseNotes file.
16004 o Major bugfixes (parsing, security):
16005 - Fix a bug in parsing that could cause clients to read a single
16006 byte past the end of an allocated region. This bug could be used
16007 to cause hardened clients (built with --enable-expensive-hardening)
16008 to crash if they tried to visit a hostile hidden service. Non-
16009 hardened clients are only affected depending on the details of
16010 their platform's memory allocator. Fixes bug 21018; bugfix on
16011 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
16012 2016-12-002 and as CVE-2016-1254.
16014 o Minor features (fallback directory list):
16015 - Replace the 81 remaining fallbacks of the 100 originally
16016 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
16017 fallbacks (123 new, 54 existing, 27 removed) generated in December
16018 2016. Resolves ticket 20170.
16021 Changes in version 0.2.9.7-rc - 2016-12-12
16022 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
16023 including a few that had prevented tests from passing on
16026 o Minor features (geoip):
16027 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
16030 o Minor bugfix (build):
16031 - The current Git revision when building from a local repository is
16032 now detected correctly when using git worktrees. Fixes bug 20492;
16033 bugfix on 0.2.3.9-alpha.
16035 o Minor bugfixes (directory authority):
16036 - When computing old Tor protocol line version in protover, we were
16037 looking at 0.2.7.5 twice instead of a specific case for
16038 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
16040 o Minor bugfixes (download scheduling):
16041 - Resolve a "bug" warning when considering a download schedule whose
16042 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
16044 o Minor bugfixes (logging):
16045 - Downgrade a harmless log message about the
16046 pending_entry_connections list from "warn" to "info". Mitigates
16049 o Minor bugfixes (memory leak):
16050 - Fix a small memory leak when receiving AF_UNIX connections on a
16051 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
16052 - When moving a signed descriptor object from a source to an
16053 existing destination, free the allocated memory inside that
16054 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
16056 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
16057 - Fix a memory leak and use-after-free error when removing entries
16058 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
16059 0.2.5.5-alpha. Patch from "cypherpunks".
16061 o Minor bugfixes (portability):
16062 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
16063 Fixes bug 20935; bugfix on 0.2.9.6-rc.
16065 o Minor bugfixes (unit tests):
16066 - Stop expecting NetBSD unit tests to report success for ipfw. Part
16067 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
16068 - Fix tolerances in unit tests for monotonic time comparisons
16069 between nanoseconds and microseconds. Previously, we accepted a 10
16070 us difference only, which is not realistic on every platform's
16071 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
16072 - Remove a double-free in the single onion service unit test. Stop
16073 ignoring a return value. Make future changes less error-prone.
16074 Fixes bug 20864; bugfix on 0.2.9.6-rc.
16077 Changes in version 0.2.8.11 - 2016-12-08
16078 Tor 0.2.8.11 backports fixes for additional portability issues that
16079 could prevent Tor from building correctly on OSX Sierra, or with
16080 OpenSSL 1.1. Affected users should upgrade; others can safely stay
16083 o Minor bugfixes (portability):
16084 - Avoid compilation errors when building on OSX Sierra. Sierra began
16085 to support the getentropy() and clock_gettime() APIs, but created
16086 a few problems in doing so. Tor 0.2.9 has a more thorough set of
16087 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
16088 monotonic time interfaces. Fixes bug 20865. Bugfix
16091 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
16092 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
16093 architectures. Closes ticket 20588.
16096 Changes in version 0.2.8.10 - 2016-12-02
16097 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
16098 unusable after they left standby mode. It also backports fixes for
16099 a few portability issues and a small but problematic memory leak.
16101 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
16102 - When Tor leaves standby because of a new application request, open
16103 circuits as needed to serve that request. Previously, we would
16104 potentially wait a very long time. Fixes part of bug 19969; bugfix
16107 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
16108 - Clients now respond to new application stream requests immediately
16109 when they arrive, rather than waiting up to one second before
16110 starting to handle them. Fixes part of bug 19969; bugfix
16113 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
16114 - Work around a bug in the OSX 10.12 SDK that would prevent us from
16115 successfully targeting earlier versions of OSX. Resolves
16118 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
16119 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
16120 20551; bugfix on 0.2.1.1-alpha.
16122 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
16123 - Work around a memory leak in OpenSSL 1.1 when encoding public
16124 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
16126 o Minor features (geoip):
16127 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
16130 Changes in version 0.2.9.6-rc - 2016-12-02
16131 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
16132 version. We hope that it will be ready to become stable soon, and we
16133 encourage everyone to test this release. If no showstopper bugs are
16134 found here, the next 0.2.9 release will be stable.
16136 o Major bugfixes (relay, resolver, logging):
16137 - For relays that don't know their own address, avoid attempting a
16138 local hostname resolve for each descriptor we download. This
16139 will cut down on the number of "Success: chose address 'x.x.x.x'"
16140 log lines, and also avoid confusing clock jumps if the resolver
16141 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
16143 o Minor bugfixes (client, fascistfirewall):
16144 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
16145 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
16147 o Minor bugfixes (hidden services):
16148 - Stop ignoring the anonymity status of saved keys for hidden
16149 services and single onion services when first starting tor.
16150 Instead, refuse to start tor if any hidden service key has been
16151 used in a different hidden service anonymity mode. Fixes bug
16152 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
16154 o Minor bugfixes (portability):
16155 - Work around a bug in the OSX 10.12 SDK that would prevent us from
16156 successfully targeting earlier versions of OSX. Resolves
16158 - Run correctly when built on Windows build environments that
16159 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
16161 o Minor bugfixes (single onion services, Tor2web):
16162 - Stop complaining about long-term one-hop circuits deliberately
16163 created by single onion services and Tor2web. These log messages
16164 are intended to diagnose issue 8387, which relates to circuits
16165 hanging around forever for no reason. Fixes bug 20613; bugfix on
16166 0.2.9.1-alpha. Reported by "pastly".
16168 o Minor bugfixes (unit tests):
16169 - Stop spurious failures in the local interface address discovery
16170 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
16174 - Correct the minimum bandwidth value in torrc.sample, and queue a
16175 corresponding change for torrc.minimal. Closes ticket 20085.
16178 Changes in version 0.2.9.5-alpha - 2016-11-08
16179 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
16180 version. We believe one or two probably remain, and we encourage
16181 everyone to test this release.
16183 o Major bugfixes (client performance):
16184 - Clients now respond to new application stream requests immediately
16185 when they arrive, rather than waiting up to one second before
16186 starting to handle them. Fixes part of bug 19969; bugfix
16189 o Major bugfixes (client reliability):
16190 - When Tor leaves standby because of a new application request, open
16191 circuits as needed to serve that request. Previously, we would
16192 potentially wait a very long time. Fixes part of bug 19969; bugfix
16195 o Major bugfixes (download scheduling):
16196 - When using an exponential backoff schedule, do not give up on
16197 downloading just because we have failed a bunch of times. Since
16198 each delay is longer than the last, retrying indefinitely won't
16199 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
16200 - If a consensus expires while we are waiting for certificates to
16201 download, stop waiting for certificates.
16202 - If we stop waiting for certificates less than a minute after we
16203 started downloading them, do not consider the certificate download
16204 failure a separate failure. Fixes bug 20533; bugfix
16206 - Remove the maximum delay on exponential-backoff scheduling. Since
16207 we now allow an infinite number of failures (see ticket 20536), we
16208 must now allow the time to grow longer on each failure. Fixes part
16209 of bug 20534; bugfix on 0.2.9.1-alpha.
16210 - Make our initial download delays closer to those from 0.2.8. Fixes
16211 another part of bug 20534; bugfix on 0.2.9.1-alpha.
16212 - When determining when to download a directory object, handle times
16213 after 2038 if the operating system supports them. (Someday this
16214 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
16215 - When using exponential backoff in test networks, use a lower
16216 exponent, so the delays do not vary as much. This helps test
16217 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
16219 o Minor features (geoip):
16220 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
16223 o Minor bugfixes (client directory scheduling):
16224 - Treat "relay too busy to answer request" as a failed request and a
16225 reason to back off on our retry frequency. This is safe now that
16226 exponential backoffs retry indefinitely, and avoids a bug where we
16227 would reset our download schedule erroneously. Fixes bug 20593;
16228 bugfix on 0.2.9.1-alpha.
16230 o Minor bugfixes (client, logging):
16231 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
16232 assume all nodes support EXTEND2. Use ntor whenever a key is
16233 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
16234 - On DNSPort, stop logging a BUG warning on a failed hostname
16235 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
16237 o Minor bugfixes (hidden services):
16238 - When configuring hidden services, check every hidden service
16239 directory's permissions. Previously, we only checked the last
16240 hidden service. Fixes bug 20529; bugfix the work to fix 13942
16243 o Minor bugfixes (portability):
16244 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
16245 architectures. Closes ticket 20588.
16246 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
16247 removed the ECDH ciphers which caused the tests to fail on
16248 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
16249 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
16250 20551; bugfix on 0.2.1.1-alpha.
16252 o Minor bugfixes (relay bootstrap):
16253 - Ensure relays don't make multiple connections during bootstrap.
16254 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
16256 o Minor bugfixes (relay):
16257 - Work around a memory leak in OpenSSL 1.1 when encoding public
16258 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
16259 - Avoid a small memory leak when informing worker threads about
16260 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
16261 - Do not try to parallelize workers more than 16x without the user
16262 explicitly configuring us to do so, even if we do detect more than
16263 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
16265 o Minor bugfixes (single onion services):
16266 - Start correctly when creating a single onion service in a
16267 directory that did not previously exist. Fixes bug 20484; bugfix
16270 o Minor bugfixes (testing):
16271 - Avoid a unit test failure on systems with over 16 detectable CPU
16272 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
16275 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
16276 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
16277 - Module-level documentation for several more modules. Closes
16278 tickets 19287 and 19290.
16281 Changes in version 0.2.8.9 - 2016-10-17
16282 Tor 0.2.8.9 backports a fix for a security hole in previous versions
16283 of Tor that would allow a remote attacker to crash a Tor client,
16284 hidden service, relay, or authority. All Tor users should upgrade to
16285 this version, or to 0.2.9.4-alpha. Patches will be released for older
16288 o Major features (security fixes, also in 0.2.9.4-alpha):
16289 - Prevent a class of security bugs caused by treating the contents
16290 of a buffer chunk as if they were a NUL-terminated string. At
16291 least one such bug seems to be present in all currently used
16292 versions of Tor, and would allow an attacker to remotely crash
16293 most Tor instances, especially those compiled with extra compiler
16294 hardening. With this defense in place, such bugs can't crash Tor,
16295 though we should still fix them as they occur. Closes ticket
16296 20384 (TROVE-2016-10-001).
16298 o Minor features (geoip):
16299 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
16303 Changes in version 0.2.9.4-alpha - 2016-10-17
16304 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
16305 that would allow a remote attacker to crash a Tor client, hidden
16306 service, relay, or authority. All Tor users should upgrade to this
16307 version, or to 0.2.8.9. Patches will be released for older versions
16310 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
16311 previous versions of Tor, including the implementation of a feature to
16312 future- proof the Tor ecosystem against protocol changes, some bug
16313 fixes necessary for Tor Browser to use unix domain sockets correctly,
16314 and several portability improvements. We anticipate that this will be
16315 the last alpha in the Tor 0.2.9 series, and that the next release will
16316 be a release candidate.
16318 o Major features (security fixes):
16319 - Prevent a class of security bugs caused by treating the contents
16320 of a buffer chunk as if they were a NUL-terminated string. At
16321 least one such bug seems to be present in all currently used
16322 versions of Tor, and would allow an attacker to remotely crash
16323 most Tor instances, especially those compiled with extra compiler
16324 hardening. With this defense in place, such bugs can't crash Tor,
16325 though we should still fix them as they occur. Closes ticket
16326 20384 (TROVE-2016-10-001).
16328 o Major features (subprotocol versions):
16329 - Tor directory authorities now vote on a set of recommended
16330 subprotocol versions, and on a set of required subprotocol
16331 versions. Clients and relays that lack support for a _required_
16332 subprotocol version will not start; those that lack support for a
16333 _recommended_ subprotocol version will warn the user to upgrade.
16334 Closes ticket 19958; implements part of proposal 264.
16335 - Tor now uses "subprotocol versions" to indicate compatibility.
16336 Previously, versions of Tor looked at the declared Tor version of
16337 a relay to tell whether they could use a given feature. Now, they
16338 should be able to rely on its declared subprotocol versions. This
16339 change allows compatible implementations of the Tor protocol(s) to
16340 exist without pretending to be 100% bug-compatible with particular
16341 releases of Tor itself. Closes ticket 19958; implements part of
16344 o Minor feature (fallback directories):
16345 - Remove broken fallbacks from the hard-coded fallback directory
16346 list. Closes ticket 20190; patch by teor.
16348 o Minor features (client, directory):
16349 - Since authorities now omit all routers that lack the Running and
16350 Valid flags, we assume that any relay listed in the consensus must
16351 have those flags. Closes ticket 20001; implements part of
16354 o Minor features (compilation, portability):
16355 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
16358 o Minor features (development tools, etags):
16359 - Teach the "make tags" Makefile target how to correctly find
16360 "MOCK_IMPL" function definitions. Patch from nherring; closes
16363 o Minor features (geoip):
16364 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
16367 o Minor features (unix domain sockets):
16368 - When configuring a unix domain socket for a SocksPort,
16369 ControlPort, or Hidden service, you can now wrap the address in
16370 quotes, using C-style escapes inside the quotes. This allows unix
16371 domain socket paths to contain spaces.
16373 o Minor features (virtual addresses):
16374 - Increase the maximum number of bits for the IPv6 virtual network
16375 prefix from 16 to 104. In this way, the condition for address
16376 allocation is less restrictive. Closes ticket 20151; feature
16379 o Minor bugfixes (address discovery):
16380 - Stop reordering IP addresses returned by the OS. This makes it
16381 more likely that Tor will guess the same relay IP address every
16382 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
16383 Reported by René Mayrhofer, patch by "cypherpunks".
16385 o Minor bugfixes (client, unix domain sockets):
16386 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
16387 the client address is meaningless. Fixes bug 20261; bugfix
16390 o Minor bugfixes (compilation, OpenBSD):
16391 - Detect Libevent2 functions correctly on systems that provide
16392 libevent2, but where libevent1 is linked with -levent. Fixes bug
16393 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
16395 o Minor bugfixes (configuration):
16396 - When parsing quoted configuration values from the torrc file,
16397 handle windows line endings correctly. Fixes bug 19167; bugfix on
16398 0.2.0.16-alpha. Patch from "Pingl".
16400 o Minor bugfixes (getpass):
16401 - Defensively fix a non-triggerable heap corruption at do_getpass()
16402 to protect ourselves from mistakes in the future. Fixes bug
16403 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
16406 o Minor bugfixes (hidden service):
16407 - Allow hidden services to run on IPv6 addresses even when the
16408 IPv6Exit option is not set. Fixes bug 18357; bugfix
16412 - Add module-level internal documentation for 36 C files that
16413 previously didn't have a high-level overview. Closes ticket #20385.
16415 o Required libraries:
16416 - When building with OpenSSL, Tor now requires version 1.0.1 or
16417 later. OpenSSL 1.0.0 and earlier are no longer supported by the
16418 OpenSSL team, and should not be used. Closes ticket 20303.
16421 Changes in version 0.2.9.3-alpha - 2016-09-23
16422 Tor 0.2.9.3-alpha adds improved support for entities that want to make
16423 high-performance services available through the Tor .onion mechanism
16424 without themselves receiving anonymity as they host those services. It
16425 also tries harder to ensure that all steps on a circuit are using the
16426 strongest crypto possible, strengthens some TLS properties, and
16427 resolves several bugs -- including a pair of crash bugs from the 0.2.8
16428 series. Anybody running an earlier version of 0.2.9.x should upgrade.
16430 o Major bugfixes (crash, also in 0.2.8.8):
16431 - Fix a complicated crash bug that could affect Tor clients
16432 configured to use bridges when replacing a networkstatus consensus
16433 in which one of their bridges was mentioned. OpenBSD users saw
16434 more crashes here, but all platforms were potentially affected.
16435 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
16437 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
16438 - Fix a timing-dependent assertion failure that could occur when we
16439 tried to flush from a circuit after having freed its cells because
16440 of an out-of-memory condition. Fixes bug 20203; bugfix on
16441 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
16444 o Major features (circuit building, security):
16445 - Authorities, relays and clients now require ntor keys in all
16446 descriptors, for all hops (except for rare hidden service protocol
16447 cases), for all circuits, and for all other roles. Part of
16449 - Tor authorities, relays, and clients only use ntor, except for
16450 rare cases in the hidden service protocol. Part of ticket 19163.
16452 o Major features (single-hop "hidden" services):
16453 - Add experimental HiddenServiceSingleHopMode and
16454 HiddenServiceNonAnonymousMode options. When both are set to 1,
16455 every hidden service on a Tor instance becomes a non-anonymous
16456 Single Onion Service. Single Onions make one-hop (direct)
16457 connections to their introduction and rendezvous points. One-hop
16458 circuits make Single Onion servers easily locatable, but clients
16459 remain location-anonymous. This is compatible with the existing
16460 hidden service implementation, and works on the current tor
16461 network without any changes to older relays or clients. Implements
16462 proposal 260, completes ticket 17178. Patch by teor and asn.
16464 o Major features (resource management):
16465 - Tor can now notice it is about to run out of sockets, and
16466 preemptively close connections of lower priority. (This feature is
16467 off by default for now, since the current prioritizing method is
16468 yet not mature enough. You can enable it by setting
16469 "DisableOOSCheck 0", but watch out: it might close some sockets
16470 you would rather have it keep.) Closes ticket 18640.
16472 o Major bugfixes (circuit building):
16473 - Hidden service client-to-intro-point and service-to-rendezvous-
16474 point circuits use the TAP key supplied by the protocol, to avoid
16475 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
16477 o Major bugfixes (compilation, OpenBSD):
16478 - Fix a Libevent-detection bug in our autoconf script that would
16479 prevent Tor from linking successfully on OpenBSD. Patch from
16480 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
16482 o Major bugfixes (hidden services):
16483 - Clients now require hidden services to include the TAP keys for
16484 their intro points in the hidden service descriptor. This prevents
16485 an inadvertent upgrade to ntor, which a malicious hidden service
16486 could use to distinguish clients by consensus version. Fixes bug
16487 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
16489 o Minor features (security, TLS):
16490 - Servers no longer support clients that without AES ciphersuites.
16491 (3DES is no longer considered an acceptable cipher.) We believe
16492 that no such Tor clients currently exist, since Tor has required
16493 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
16495 o Minor feature (fallback directories):
16496 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
16497 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
16498 2016. Closes ticket 20190; patch by teor.
16500 o Minor features (geoip, also in 0.2.8.8):
16501 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
16504 o Minor feature (port flags):
16505 - Add new flags to the *Port options to finer control over which
16506 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
16507 and the synthetic flag OnionTrafficOnly, which is equivalent to
16508 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
16509 18693; patch by "teor".
16511 o Minor features (directory authority):
16512 - After voting, if the authorities decide that a relay is not
16513 "Valid", they no longer include it in the consensus at all. Closes
16514 ticket 20002; implements part of proposal 272.
16516 o Minor features (testing):
16517 - Disable memory protections on OpenBSD when performing our unit
16518 tests for memwipe(). The test deliberately invokes undefined
16519 behavior, and the OpenBSD protections interfere with this. Patch
16520 from "rubiate". Closes ticket 20066.
16522 o Minor features (testing, ipv6):
16523 - Add the single-onion and single-onion-ipv6 chutney targets to
16524 "make test-network-all". This requires a recent chutney version
16525 with the single onion network flavours (git c72a652 or later).
16526 Closes ticket 20072; patch by teor.
16527 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
16528 tests. Remove bridges+hs, as it's somewhat redundant. This
16529 requires a recent chutney version that supports IPv6 clients,
16530 relays, and authorities. Closes ticket 20069; patch by teor.
16532 o Minor features (Tor2web):
16533 - Make Tor2web clients respect ReachableAddresses. This feature was
16534 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
16535 0.2.8.7. Implements feature 20034. Patch by teor.
16537 o Minor features (unit tests):
16538 - We've done significant work to make the unit tests run faster.
16539 - Our link-handshake unit tests now check that when invalid
16540 handshakes fail, they fail with the error messages we expected.
16541 - Our unit testing code that captures log messages no longer
16542 prevents them from being written out if the user asked for them
16543 (by passing --debug or --info or or --notice --warn to the "test"
16544 binary). This change prevents us from missing unexpected log
16545 messages simply because we were looking for others. Related to
16547 - The unit tests now log all warning messages with the "BUG" flag.
16548 Previously, they only logged errors by default. This change will
16549 help us make our testing code more correct, and make sure that we
16550 only hit this code when we mean to. In the meantime, however,
16551 there will be more warnings in the unit test logs than before.
16552 This is preparatory work for ticket 19999.
16553 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
16554 assertion as a test failure.
16556 o Minor bug fixes (circuits):
16557 - Use the CircuitBuildTimeout option whenever
16558 LearnCircuitBuildTimeout is disabled. Previously, we would respect
16559 the option when a user disabled it, but not when it was disabled
16560 because some other option was set. Fixes bug 20073; bugfix on
16561 0.2.4.12-alpha. Patch by teor.
16563 o Minor bugfixes (allocation):
16564 - Change how we allocate memory for large chunks on buffers, to
16565 avoid a (currently impossible) integer overflow, and to waste less
16566 space when allocating unusually large chunks. Fixes bug 20081;
16567 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
16568 - Always include orconfig.h before including any other C headers.
16569 Sometimes, it includes macros that affect the behavior of the
16570 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
16571 first version to use AC_USE_SYSTEM_EXTENSIONS).
16572 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
16573 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
16574 Patch from Gisle Vanem.
16575 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
16576 They apparently require a set of annotations that we aren't
16577 currently using, and they create false positives in our pthreads
16578 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
16580 o Minor bugfixes (directory authority):
16581 - Die with a more useful error when the operator forgets to place
16582 the authority_signing_key file into the keys directory. This
16583 avoids an uninformative assert & traceback about having an invalid
16584 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
16585 - When allowing private addresses, mark Exits that only exit to
16586 private locations as such. Fixes bug 20064; bugfix
16589 o Minor bugfixes (documentation):
16590 - Document the default PathsNeededToBuildCircuits value that's used
16591 by clients when the directory authorities don't set
16592 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
16593 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
16594 - Fix manual for the User option: it takes a username, not a UID.
16595 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
16598 o Minor bugfixes (hidden services):
16599 - Stop logging intro point details to the client log on certain
16600 error conditions. Fixed as part of bug 20012; bugfix on
16601 0.2.4.8-alpha. Patch by teor.
16603 o Minor bugfixes (IPv6, testing):
16604 - Check for IPv6 correctly on Linux when running test networks.
16605 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
16607 o Minor bugfixes (Linux seccomp2 sandbox):
16608 - Add permission to run the sched_yield() and sigaltstack() system
16609 calls, in order to support versions of Tor compiled with asan or
16610 ubsan code that use these calls. Now "sandbox 1" and
16611 "--enable-expensive-hardening" should be compatible on more
16612 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
16614 o Minor bugfixes (logging):
16615 - When logging a message from the BUG() macro, be explicit about
16616 what we were asserting. Previously we were confusing what we were
16617 asserting with what the bug was. Fixes bug 20093; bugfix
16619 - When we are unable to remove the bw_accounting file, do not warn
16620 if the reason we couldn't remove it was that it didn't exist.
16621 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
16623 o Minor bugfixes (option parsing):
16624 - Count unix sockets when counting client listeners (SOCKS, Trans,
16625 NATD, and DNS). This has no user-visible behaviour changes: these
16626 options are set once, and never read. Required for correct
16627 behaviour in ticket 17178. Fixes bug 19677; bugfix on
16628 0.2.6.3-alpha. Patch by teor.
16630 o Minor bugfixes (options):
16631 - Check the consistency of UseEntryGuards and EntryNodes more
16632 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
16634 - Stop changing the configured value of UseEntryGuards on
16635 authorities and Tor2web clients. Fixes bug 20074; bugfix on
16636 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
16639 o Minor bugfixes (Tor2web):
16640 - Prevent Tor2web clients running hidden services, these services
16641 are not anonymous due to the one-hop client paths. Fixes bug
16642 19678. Patch by teor.
16644 o Minor bugfixes (unit tests):
16645 - Fix a shared-random unit test that was failing on big endian
16646 architectures due to internal representation of a integer copied
16647 to a buffer. The test is changed to take a full 32 bytes of data
16648 and use the output of a python script that make the COMMIT and
16649 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
16651 - The tor_tls_server_info_callback unit test no longer crashes when
16652 debug-level logging is turned on. Fixes bug 20041; bugfix
16656 Changes in version 0.2.8.8 - 2016-09-23
16657 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
16658 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
16659 who select public relays as their bridges.
16661 o Major bugfixes (crash):
16662 - Fix a complicated crash bug that could affect Tor clients
16663 configured to use bridges when replacing a networkstatus consensus
16664 in which one of their bridges was mentioned. OpenBSD users saw
16665 more crashes here, but all platforms were potentially affected.
16666 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
16668 o Major bugfixes (relay, OOM handler):
16669 - Fix a timing-dependent assertion failure that could occur when we
16670 tried to flush from a circuit after having freed its cells because
16671 of an out-of-memory condition. Fixes bug 20203; bugfix on
16672 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
16675 o Minor feature (fallback directories):
16676 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
16677 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
16678 2016. Closes ticket 20190; patch by teor.
16680 o Minor features (geoip):
16681 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
16685 Changes in version 0.2.9.2-alpha - 2016-08-24
16686 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
16687 several new features and bugfixes. It also includes an important
16688 authority update and an important bugfix from 0.2.8.7. Everyone who
16689 sets the ReachableAddresses option, and all bridges, are strongly
16690 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
16692 o Directory authority changes (also in 0.2.8.7):
16693 - The "Tonga" bridge authority has been retired; the new bridge
16694 authority is "Bifroest". Closes tickets 19728 and 19690.
16696 o Major bugfixes (client, security, also in 0.2.8.7):
16697 - Only use the ReachableAddresses option to restrict the first hop
16698 in a path. In earlier versions of 0.2.8.x, it would apply to
16699 every hop in the path, with a possible degradation in anonymity
16700 for anyone using an uncommon ReachableAddress setting. Fixes bug
16701 19973; bugfix on 0.2.8.2-alpha.
16703 o Major features (user interface):
16704 - Tor now supports the ability to declare options deprecated, so
16705 that we can recommend that people stop using them. Previously,
16706 this was done in an ad-hoc way. Closes ticket 19820.
16708 o Major bugfixes (directory downloads):
16709 - Avoid resetting download status for consensuses hourly, since we
16710 already have another, smarter retry mechanism. Fixes bug 8625;
16711 bugfix on 0.2.0.9-alpha.
16713 o Minor features (config):
16714 - Warn users when descriptor and port addresses are inconsistent.
16715 Mitigates bug 13953; patch by teor.
16717 o Minor features (geoip):
16718 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
16721 o Minor features (user interface):
16722 - There is a new --list-deprecated-options command-line option to
16723 list all of the deprecated options. Implemented as part of
16726 o Minor bugfixes (code style):
16727 - Fix an integer signedness conversion issue in the case conversion
16728 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
16730 o Minor bugfixes (compilation):
16731 - Build correctly on versions of libevent2 without support for
16732 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
16734 - Fix a compilation warning on GCC versions before 4.6. Our
16735 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
16736 when it is also required as an argument to the compiler pragma.
16737 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
16739 o Minor bugfixes (compilation, also in 0.2.8.7):
16740 - Remove an inappropriate "inline" in tortls.c that was causing
16741 warnings on older versions of GCC. Fixes bug 19903; bugfix
16744 o Minor bugfixes (fallback directories, also in 0.2.8.7):
16745 - Avoid logging a NULL string pointer when loading fallback
16746 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
16747 and 0.2.8.1-alpha. Report and patch by "rubiate".
16749 o Minor bugfixes (logging):
16750 - Log a more accurate message when we fail to dump a microdescriptor.
16751 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
16753 o Minor bugfixes (memory leak):
16754 - Fix a series of slow memory leaks related to parsing torrc files
16755 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
16757 o Deprecated features:
16758 - A number of DNS-cache-related sub-options for client ports are now
16759 deprecated for security reasons, and may be removed in a future
16760 version of Tor. (We believe that client-side DNS caching is a bad
16761 idea for anonymity, and you should not turn it on.) The options
16762 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
16763 UseIPv4Cache, and UseIPv6Cache.
16764 - A number of options are deprecated for security reasons, and may
16765 be removed in a future version of Tor. The options are:
16766 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
16767 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
16768 CloseHSClientCircuitsImmediatelyOnTimeout,
16769 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
16770 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
16771 UseNTorHandshake, and WarnUnsafeSocks.
16772 - The *ListenAddress options are now deprecated as unnecessary: the
16773 corresponding *Port options should be used instead. These options
16774 may someday be removed. The affected options are:
16775 ControlListenAddress, DNSListenAddress, DirListenAddress,
16776 NATDListenAddress, ORListenAddress, SocksListenAddress,
16777 and TransListenAddress.
16780 - Correct the IPv6 syntax in our documentation for the
16781 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
16784 - We no longer include the (dead, deprecated) bufferevent code in
16785 Tor. Closes ticket 19450. Based on a patch from U+039b.
16788 Changes in version 0.2.8.7 - 2016-08-24
16789 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
16790 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
16791 who sets the ReachableAddresses option, and all bridges, are strongly
16792 encouraged to upgrade.
16794 o Directory authority changes:
16795 - The "Tonga" bridge authority has been retired; the new bridge
16796 authority is "Bifroest". Closes tickets 19728 and 19690.
16798 o Major bugfixes (client, security):
16799 - Only use the ReachableAddresses option to restrict the first hop
16800 in a path. In earlier versions of 0.2.8.x, it would apply to
16801 every hop in the path, with a possible degradation in anonymity
16802 for anyone using an uncommon ReachableAddress setting. Fixes bug
16803 19973; bugfix on 0.2.8.2-alpha.
16805 o Minor features (geoip):
16806 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
16809 o Minor bugfixes (compilation):
16810 - Remove an inappropriate "inline" in tortls.c that was causing
16811 warnings on older versions of GCC. Fixes bug 19903; bugfix
16814 o Minor bugfixes (fallback directories):
16815 - Avoid logging a NULL string pointer when loading fallback
16816 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
16817 and 0.2.8.1-alpha. Report and patch by "rubiate".
16820 Changes in version 0.2.9.1-alpha - 2016-08-08
16821 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
16822 series. It improves our support for hardened builds and compiler
16823 warnings, deploys some critical infrastructure for improvements to
16824 hidden services, includes a new timing backend that we hope to use for
16825 better support for traffic padding, makes it easier for programmers to
16826 log unexpected events, and contains other small improvements to
16827 security, correctness, and performance.
16829 Below are the changes since 0.2.8.6.
16831 o New system requirements:
16832 - Tor now requires Libevent version 2.0.10-stable or later. Older
16833 versions of Libevent have less efficient backends for several
16834 platforms, and lack the DNS code that we use for our server-side
16835 DNS support. This implements ticket 19554.
16836 - Tor now requires zlib version 1.2 or later, for security,
16837 efficiency, and (eventually) gzip support. (Back when we started,
16838 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
16839 released in 2003. We recommend the latest version.)
16841 o Major features (build, hardening):
16842 - Tor now builds with -ftrapv by default on compilers that support
16843 it. This option detects signed integer overflow (which C forbids),
16844 and turns it into a hard-failure. We do not apply this option to
16845 code that needs to run in constant time to avoid side-channels;
16846 instead, we use -fwrapv in that code. Closes ticket 17983.
16847 - When --enable-expensive-hardening is selected, stop applying the
16848 clang/gcc sanitizers to code that needs to run in constant time.
16849 Although we are aware of no introduced side-channels, we are not
16850 able to prove that there are none. Related to ticket 17983.
16852 o Major features (compilation):
16853 - Our big list of extra GCC warnings is now enabled by default when
16854 building with GCC (or with anything like Clang that claims to be
16855 GCC-compatible). To make all warnings into fatal compilation
16856 errors, pass --enable-fatal-warnings to configure. Closes
16858 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
16859 turn on C and POSIX extensions. (Previously, we attempted to do
16860 this on an ad hoc basis.) Closes ticket 19139.
16862 o Major features (directory authorities, hidden services):
16863 - Directory authorities can now perform the shared randomness
16864 protocol specified by proposal 250. Using this protocol, directory
16865 authorities generate a global fresh random value every day. In the
16866 future, this value will be used by hidden services to select
16867 HSDirs. This release implements the directory authority feature;
16868 the hidden service side will be implemented in the future as part
16869 of proposal 224. Resolves ticket 16943; implements proposal 250.
16871 o Major features (downloading, random exponential backoff):
16872 - When we fail to download an object from a directory service, wait
16873 for an (exponentially increasing) randomized amount of time before
16874 retrying, rather than a fixed interval as we did before. This
16875 prevents a group of Tor instances from becoming too synchronized,
16876 or a single Tor instance from becoming too predictable, in its
16877 download schedule. Closes ticket 15942.
16879 o Major bugfixes (exit policies):
16880 - Avoid disclosing exit outbound bind addresses, configured port
16881 bind addresses, and local interface addresses in relay descriptors
16882 by default under ExitPolicyRejectPrivate. Instead, only reject
16883 these (otherwise unlisted) addresses if
16884 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
16885 0.2.7.2-alpha. Patch by teor.
16887 o Major bugfixes (hidden service client):
16888 - Allow Tor clients with appropriate controllers to work with
16889 FetchHidServDescriptors set to 0. Previously, this option also
16890 disabled descriptor cache lookup, thus breaking hidden services
16891 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
16893 o Minor features (build, hardening):
16894 - Detect and work around a libclang_rt problem that would prevent
16895 clang from finding __mulodi4() on some 32-bit platforms, and thus
16896 keep -ftrapv from linking on those systems. Closes ticket 19079.
16897 - When building on a system without runtime support for the runtime
16898 hardening options, try to log a useful warning at configuration
16899 time, rather than an incomprehensible warning at link time. If
16900 expensive hardening was requested, this warning becomes an error.
16901 Closes ticket 18895.
16903 o Minor features (code safety):
16904 - In our integer-parsing functions, ensure that maxiumum value we
16905 give is no smaller than the minimum value. Closes ticket 19063;
16908 o Minor features (controller):
16909 - Implement new GETINFO queries for all downloads that use
16910 download_status_t to schedule retries. This allows controllers to
16911 examine the schedule for pending downloads. Closes ticket 19323.
16912 - Allow controllers to configure basic client authorization on
16913 hidden services when they create them with the ADD_ONION control
16914 command. Implements ticket 15588. Patch by "special".
16915 - Fire a STATUS_SERVER controller event whenever the hibernation
16916 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
16918 o Minor features (directory authority):
16919 - Directory authorities now only give the Guard flag to a relay if
16920 they are also giving it the Stable flag. This change allows us to
16921 simplify path selection for clients. It should have minimal effect
16922 in practice, since >99% of Guards already have the Stable flag.
16923 Implements ticket 18624.
16924 - Directory authorities now write their v3-status-votes file out to
16925 disk earlier in the consensus process, so we have a record of the
16926 votes even if we abort the consensus process. Resolves
16929 o Minor features (hidden service):
16930 - Stop being so strict about the payload length of "rendezvous1"
16931 cells. We used to be locked in to the "TAP" handshake length, and
16932 now we can handle better handshakes like "ntor". Resolves
16935 o Minor features (infrastructure, time):
16936 - Tor now uses the operating system's monotonic timers (where
16937 available) for internal fine-grained timing. Previously we would
16938 look at the system clock, and then attempt to compensate for the
16939 clock running backwards. Closes ticket 18908.
16940 - Tor now includes an improved timer backend, so that we can
16941 efficiently support tens or hundreds of thousands of concurrent
16942 timers, as will be needed for some of our planned anti-traffic-
16943 analysis work. This code is based on William Ahern's "timeout.c"
16944 project, which implements a "tickless hierarchical timing wheel".
16945 Closes ticket 18365.
16947 o Minor features (logging):
16948 - Provide a more useful warning message when configured with an
16949 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
16950 - When dumping unparseable router descriptors, optionally store them
16951 in separate files, named by digest, up to a configurable size
16952 limit. You can change the size limit by setting the
16953 MaxUnparseableDescSizeToLog option, and disable this feature by
16954 setting that option to 0. Closes ticket 18322.
16955 - Add a set of macros to check nonfatal assertions, for internal
16956 use. Migrating more of our checks to these should help us avoid
16957 needless crash bugs. Closes ticket 18613.
16959 o Minor features (performance):
16960 - Change the "optimistic data" extension from "off by default" to
16961 "on by default". The default was ordinarily overridden by a
16962 consensus option, but when clients were bootstrapping for the
16963 first time, they would not have a consensus to get the option
16964 from. Changing this default saves a round-trip during startup.
16965 Closes ticket 18815.
16967 o Minor features (relay, usability):
16968 - When the directory authorities refuse a bad relay's descriptor,
16969 encourage the relay operator to contact us. Many relay operators
16970 won't notice this line in their logs, but it's a win if even a few
16971 learn why we don't like what their relay was doing. Resolves
16974 o Minor features (testing):
16975 - Let backtrace tests work correctly under AddressSanitizer. Fixes
16976 part of bug 18934; bugfix on 0.2.5.2-alpha.
16977 - Move the test-network.sh script to chutney, and modify tor's test-
16978 network.sh to call the (newer) chutney version when available.
16979 Resolves ticket 19116. Patch by teor.
16980 - Use the lcov convention for marking lines as unreachable, so that
16981 we don't count them when we're generating test coverage data.
16982 Update our coverage tools to understand this convention. Closes
16985 o Minor bugfixes (bootstrap):
16986 - Remember the directory we fetched the consensus or previous
16987 certificates from, and use it to fetch future authority
16988 certificates. This change improves bootstrapping performance.
16989 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
16991 o Minor bugfixes (build):
16992 - The test-stem and test-network makefile targets now depend only on
16993 the tor binary that they are testing. Previously, they depended on
16994 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
16995 patch from "cypherpunks".
16997 o Minor bugfixes (circuits):
16998 - Make sure extend_info_from_router() is only called on servers.
16999 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
17001 o Minor bugfixes (compilation):
17002 - When building with Clang, use a full set of GCC warnings.
17003 (Previously, we included only a subset, because of the way we
17004 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
17006 o Minor bugfixes (directory authority):
17007 - Authorities now sort the "package" lines in their votes, for ease
17008 of debugging. (They are already sorted in consensus documents.)
17009 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
17010 - When parsing a detached signature, make sure we use the length of
17011 the digest algorithm instead of an hardcoded DIGEST256_LEN in
17012 order to avoid comparing bytes out-of-bounds with a smaller digest
17013 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
17015 o Minor bugfixes (documentation):
17016 - Document the --passphrase-fd option in the tor manpage. Fixes bug
17017 19504; bugfix on 0.2.7.3-rc.
17018 - Fix the description of the --passphrase-fd option in the
17019 tor-gencert manpage. The option is used to pass the number of a
17020 file descriptor to read the passphrase from, not to read the file
17021 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
17023 o Minor bugfixes (ephemeral hidden service):
17024 - When deleting an ephemeral hidden service, close its intro points
17025 even if they are not completely open. Fixes bug 18604; bugfix
17028 o Minor bugfixes (guard selection):
17029 - Use a single entry guard even if the NumEntryGuards consensus
17030 parameter is not provided. Fixes bug 17688; bugfix
17032 - Don't mark guards as unreachable if connection_connect() fails.
17033 That function fails for local reasons, so it shouldn't reveal
17034 anything about the status of the guard. Fixes bug 14334; bugfix
17037 o Minor bugfixes (hidden service client):
17038 - Increase the minimum number of internal circuits we preemptively
17039 build from 2 to 3, so a circuit is available when a client
17040 connects to another onion service. Fixes bug 13239; bugfix
17043 o Minor bugfixes (logging):
17044 - When logging a directory ownership mismatch, log the owning
17045 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
17047 o Minor bugfixes (memory leaks):
17048 - Fix a small, uncommon memory leak that could occur when reading a
17049 truncated ed25519 key file. Fixes bug 18956; bugfix
17052 o Minor bugfixes (testing):
17053 - Allow clients to retry HSDirs much faster in test networks. Fixes
17054 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
17055 - Disable ASAN's detection of segmentation faults while running
17056 test_bt.sh, so that we can make sure that our own backtrace
17057 generation code works. Fixes another aspect of bug 18934; bugfix
17058 on 0.2.5.2-alpha. Patch from "cypherpunks".
17059 - Fix the test-network-all target on out-of-tree builds by using the
17060 correct path to the test driver script. Fixes bug 19421; bugfix
17063 o Minor bugfixes (time):
17064 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
17065 bugfix on all released tor versions.
17066 - When computing the difference between two times in milliseconds,
17067 we now round to the nearest millisecond correctly. Previously, we
17068 could sometimes round in the wrong direction. Fixes bug 19428;
17069 bugfix on 0.2.2.2-alpha.
17071 o Minor bugfixes (user interface):
17072 - Display a more accurate number of suppressed messages in the log
17073 rate-limiter. Previously, there was a potential integer overflow
17074 in the counter. Now, if the number of messages hits a maximum, the
17075 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
17077 - Fix a typo in the passphrase prompt for the ed25519 identity key.
17078 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
17080 o Code simplification and refactoring:
17081 - Remove redundant declarations of the MIN macro. Closes
17083 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
17084 Closes ticket 18462; patch from "icanhasaccount".
17085 - Split the 600-line directory_handle_command_get function into
17086 separate functions for different URL types. Closes ticket 16698.
17089 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
17090 ticket 19153. Patch from "U+039b".
17092 o Removed features:
17093 - Remove support for "GET /tor/bytes.txt" DirPort request, and
17094 "GETINFO dir-usage" controller request, which were only available
17095 via a compile-time option in Tor anyway. Feature was added in
17096 0.2.2.1-alpha. Resolves ticket 19035.
17097 - There is no longer a compile-time option to disable support for
17098 TransPort. (If you don't want TransPort; just don't use it.) Patch
17099 from "U+039b". Closes ticket 19449.
17102 - Run more workqueue tests as part of "make check". These had
17103 previously been implemented, but you needed to know special
17104 command-line options to enable them.
17105 - We now have unit tests for our code to reject zlib "compression
17106 bombs". (Fortunately, the code works fine.)
17109 Changes in version 0.2.8.6 - 2016-08-02
17111 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
17113 The Tor 0.2.8 series improves client bootstrapping performance,
17114 completes the authority-side implementation of improved identity
17115 keys for relays, and includes numerous bugfixes and performance
17116 improvements throughout the program. This release continues to
17117 improve the coverage of Tor's test suite. For a full list of
17118 changes since Tor 0.2.7, see the ReleaseNotes file.
17120 Changes since 0.2.8.5-rc:
17122 o Minor features (geoip):
17123 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
17126 o Minor bugfixes (compilation):
17127 - Fix a compilation warning in the unit tests on systems where char
17128 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
17130 o Minor bugfixes (fallback directories):
17131 - Remove 1 fallback that was on the hardcoded list, then opted-out,
17132 leaving 89 of the 100 fallbacks originally introduced in Tor
17133 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
17135 o Minor bugfixes (Linux seccomp2 sandbox):
17136 - Allow more syscalls when running with "Sandbox 1" enabled:
17137 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
17138 some systems, these are required for Tor to start. Fixes bug
17139 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
17140 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
17141 so that get_interface_address6_via_udp_socket_hack() can work.
17142 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
17145 Changes in version 0.2.8.5-rc - 2016-07-07
17146 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
17147 series. If we find no new bugs or regressions here, the first stable
17148 0.2.8 release will be identical to it. It has a few small bugfixes
17149 against previous versions.
17151 o Directory authority changes:
17152 - Urras is no longer a directory authority. Closes ticket 19271.
17154 o Major bugfixes (heartbeat):
17155 - Fix a regression that would crash Tor when the periodic
17156 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
17157 0.2.8.1-alpha. Reported by "kubaku".
17159 o Minor features (build):
17160 - Tor now again builds with the recent OpenSSL 1.1 development
17161 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
17162 - When building manual pages, set the timezone to "UTC", so that the
17163 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
17164 Patch from intrigeri.
17166 o Minor bugfixes (fallback directory selection):
17167 - Avoid errors during fallback selection if there are no eligible
17168 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
17171 o Minor bugfixes (IPv6, microdescriptors):
17172 - Don't check node addresses when we only have a routerstatus. This
17173 allows IPv6-only clients to bootstrap by fetching microdescriptors
17174 from fallback directory mirrors. (The microdescriptor consensus
17175 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
17178 o Minor bugfixes (logging):
17179 - Reduce pointlessly verbose log messages when directory servers
17180 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
17181 0.2.8.1-alpha. Patch by teor.
17182 - When a fallback directory changes its fingerprint from the hard-
17183 coded fingerprint, log a less severe, more explanatory log
17184 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
17186 o Minor bugfixes (Linux seccomp2 sandboxing):
17187 - Allow statistics to be written to disk when "Sandbox 1" is
17188 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
17189 0.2.6.1-alpha respectively.
17191 o Minor bugfixes (user interface):
17192 - Remove a warning message "Service [scrubbed] not found after
17193 descriptor upload". This message appears when one uses HSPOST
17194 control command to upload a service descriptor. Since there is
17195 only a descriptor and no service, showing this message is
17196 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
17198 o Fallback directory list:
17199 - Add a comment to the generated fallback directory list that
17200 explains how to comment out unsuitable fallbacks in a way that's
17201 compatible with the stem fallback parser.
17202 - Update fallback whitelist and blacklist based on relay operator
17203 emails. Blacklist unsuitable (non-working, over-volatile)
17204 fallbacks. Resolves ticket 19071. Patch by teor.
17205 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
17206 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
17207 ticket 19071; patch by teor.
17210 Changes in version 0.2.8.4-rc - 2016-06-15
17211 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
17212 If we find no new bugs or regressions here, the first stable 0.2.8
17213 release will be identical to it. It has a few small bugfixes against
17216 o Major bugfixes (user interface):
17217 - Correctly give a warning in the cases where a relay is specified
17218 by nickname, and one such relay is found, but it is not officially
17219 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
17221 o Minor features (build):
17222 - Tor now builds once again with the recent OpenSSL 1.1 development
17223 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
17225 o Minor features (geoip):
17226 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
17229 o Minor bugfixes (compilation):
17230 - Cause the unit tests to compile correctly on mingw64 versions that
17231 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
17233 o Minor bugfixes (downloading):
17234 - Predict more correctly whether we'll be downloading over HTTP when
17235 we determine the maximum length of a URL. This should avoid a
17236 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
17240 Changes in version 0.2.8.3-alpha - 2016-05-26
17241 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
17242 the course of the 0.2.8 development cycle. It improves the behavior of
17243 directory clients, fixes several crash bugs, fixes a gap in compiler
17244 hardening, and allows the full integration test suite to run on
17247 o Major bugfixes (security, client, DNS proxy):
17248 - Stop a crash that could occur when a client running with DNSPort
17249 received a query with multiple address types, and the first
17250 address type was not supported. Found and fixed by Scott Dial.
17251 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
17253 o Major bugfixes (security, compilation):
17254 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
17255 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
17256 cause a compiler warning, thereby making other checks fail, and
17257 needlessly disabling compiler-hardening support. Fixes one case of
17258 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
17260 o Major bugfixes (security, directory authorities):
17261 - Fix a crash and out-of-bounds write during authority voting, when
17262 the list of relays includes duplicate ed25519 identity keys. Fixes
17263 bug 19032; bugfix on 0.2.8.2-alpha.
17265 o Major bugfixes (client, bootstrapping):
17266 - Check if bootstrap consensus downloads are still needed when the
17267 linked connection attaches. This prevents tor making unnecessary
17268 begindir-style connections, which are the only directory
17269 connections tor clients make since the fix for 18483 was merged.
17270 - Fix some edge cases where consensus download connections may not
17271 have been closed, even though they were not needed. Related to fix
17273 - Make relays retry consensus downloads the correct number of times,
17274 rather than the more aggressive client retry count. Fixes part of
17276 - Stop downloading consensuses when we have a consensus, even if we
17277 don't have all the certificates for it yet. Fixes bug 18809;
17278 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
17280 o Major bugfixes (directory mirrors):
17281 - Decide whether to advertise begindir support in the the same way
17282 we decide whether to advertise our DirPort. Allowing these
17283 decisions to become out-of-sync led to surprising behavior like
17284 advertising begindir support when hibernation made us not
17285 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
17288 o Major bugfixes (IPv6 bridges, client):
17289 - Actually use IPv6 addresses when selecting directory addresses for
17290 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
17293 o Major bugfixes (key management):
17294 - If OpenSSL fails to generate an RSA key, do not retain a dangling
17295 pointer to the previous (uninitialized) key value. The impact here
17296 should be limited to a difficult-to-trigger crash, if OpenSSL is
17297 running an engine that makes key generation failures possible, or
17298 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
17299 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
17302 o Major bugfixes (testing):
17303 - Fix a bug that would block 'make test-network-all' on systems where
17304 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
17305 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
17306 bugfix on 0.2.8.1-alpha.
17308 o Minor features (clients):
17309 - Make clients, onion services, and bridge relays always use an
17310 encrypted begindir connection for directory requests. Resolves
17311 ticket 18483. Patch by "teor".
17313 o Minor features (fallback directory mirrors):
17314 - Give each fallback the same weight for client selection; restrict
17315 fallbacks to one per operator; report fallback directory detail
17316 changes when rebuilding list; add new fallback directory mirrors
17317 to the whitelist; and many other minor simplifications and fixes.
17318 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
17319 0.2.8.1-alpha; patch by "teor".
17320 - Replace the 21 fallbacks generated in January 2016 and included in
17321 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
17322 2016. Closes task 17158; patch by "teor".
17324 o Minor features (geoip):
17325 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
17328 o Minor bugfixes (assert, portability):
17329 - Fix an assertion failure in memarea.c on systems where "long" is
17330 shorter than the size of a pointer. Fixes bug 18716; bugfix
17333 o Minor bugfixes (bootstrap):
17334 - Consistently use the consensus download schedule for authority
17335 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
17337 o Minor bugfixes (build):
17338 - Remove a pair of redundant AM_CONDITIONAL declarations from
17339 configure.ac. Fixes one final case of bug 17744; bugfix
17341 - Resolve warnings when building on systems that are concerned with
17342 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
17344 - When libscrypt.h is found, but no libscrypt library can be linked,
17345 treat libscrypt as absent. Fixes bug 19161; bugfix
17348 o Minor bugfixes (client):
17349 - Turn all TestingClientBootstrap* into non-testing torrc options.
17350 This changes simply renames them by removing "Testing" in front of
17351 them and they do not require TestingTorNetwork to be enabled
17352 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
17353 - Make directory node selection more reliable, mainly for IPv6-only
17354 clients and clients with few reachable addresses. Fixes bug 18929;
17355 bugfix on 0.2.8.1-alpha. Patch by "teor".
17357 o Minor bugfixes (controller, microdescriptors):
17358 - Make GETINFO dir/status-vote/current/consensus conform to the
17359 control specification by returning "551 Could not open cached
17360 consensus..." when not caching consensuses. Fixes bug 18920;
17361 bugfix on 0.2.2.6-alpha.
17363 o Minor bugfixes (crypto, portability):
17364 - The SHA3 and SHAKE routines now produce the correct output on Big
17365 Endian systems. No code calls either algorithm yet, so this is
17366 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
17367 - Tor now builds again with the recent OpenSSL 1.1 development
17368 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
17371 o Minor bugfixes (directories):
17372 - When fetching extrainfo documents, compare their SHA256 digests
17373 and Ed25519 signing key certificates with the routerinfo that led
17374 us to fetch them, rather than with the most recent routerinfo.
17375 Otherwise we generate many spurious warnings about mismatches.
17376 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
17378 o Minor bugfixes (logging):
17379 - When we can't generate a signing key because OfflineMasterKey is
17380 set, do not imply that we should have been able to load it. Fixes
17381 bug 18133; bugfix on 0.2.7.2-alpha.
17382 - Stop periodic_event_dispatch() from blasting twelve lines per
17383 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
17384 - When rejecting a misformed INTRODUCE2 cell, only log at
17385 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
17387 o Minor bugfixes (pluggable transports):
17388 - Avoid reporting a spurious error when we decide that we don't need
17389 to terminate a pluggable transport because it has already exited.
17390 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
17392 o Minor bugfixes (pointer arithmetic):
17393 - Fix a bug in memarea_alloc() that could have resulted in remote
17394 heap write access, if Tor had ever passed an unchecked size to
17395 memarea_alloc(). Fortunately, all the sizes we pass to
17396 memarea_alloc() are pre-checked to be less than 128 kilobytes.
17397 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
17400 o Minor bugfixes (relays):
17401 - Consider more config options when relays decide whether to
17402 regenerate their descriptor. Fixes more of bug 12538; bugfix
17404 - Resolve some edge cases where we might launch an ORPort
17405 reachability check even when DisableNetwork is set. Noticed while
17406 fixing bug 18616; bugfix on 0.2.3.9-alpha.
17408 o Minor bugfixes (statistics):
17409 - We now include consensus downloads via IPv6 in our directory-
17410 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
17412 o Minor bugfixes (testing):
17413 - Allow directories in small networks to bootstrap by skipping
17414 DirPort checks when the consensus has no exits. Fixes bug 19003;
17415 bugfix on 0.2.8.1-alpha. Patch by teor.
17416 - Fix a small memory leak that would occur when the
17417 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
17418 bugfix on 0.2.5.2-alpha.
17420 o Minor bugfixes (time handling):
17421 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
17422 field. Otherwise, our unit tests crash on Windows. Fixes bug
17423 18977; bugfix on 0.2.2.25-alpha.
17426 - Document the contents of the 'datadir/keys' subdirectory in the
17427 manual page. Closes ticket 17621.
17428 - Stop recommending use of nicknames to identify relays in our
17429 MapAddress documentation. Closes ticket 18312.
17432 Changes in version 0.2.8.2-alpha - 2016-03-28
17433 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
17434 bugs in earlier versions of Tor, including some that prevented
17435 authorities using Tor 0.2.7.x from running correctly. IPv6 and
17436 directory support should also be much improved.
17438 o New system requirements:
17439 - Tor no longer supports versions of OpenSSL with a broken
17440 implementation of counter mode. (This bug was present in OpenSSL
17441 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
17442 longer runs with, these versions.
17443 - Tor no longer attempts to support platforms where the "time_t"
17444 type is unsigned. (To the best of our knowledge, only OpenVMS does
17445 this, and Tor has never actually built on OpenVMS.) Closes
17447 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
17448 later (released in 2008 and 2009 respectively). If you are
17449 building Tor from the git repository instead of from the source
17450 distribution, and your tools are older than this, you will need to
17451 upgrade. Closes ticket 17732.
17453 o Major bugfixes (security, pointers):
17454 - Avoid a difficult-to-trigger heap corruption attack when extending
17455 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
17456 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
17457 Reported by Guido Vranken.
17459 o Major bugfixes (bridges, pluggable transports):
17460 - Modify the check for OR connections to private addresses. Allow
17461 bridges on private addresses, including pluggable transports that
17462 ignore the (potentially private) address in the bridge line. Fixes
17463 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
17465 o Major bugfixes (compilation):
17466 - Repair hardened builds under the clang compiler. Previously, our
17467 use of _FORTIFY_SOURCE would conflict with clang's address
17468 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
17470 o Major bugfixes (crash on shutdown):
17471 - Correctly handle detaching circuits from muxes when shutting down.
17472 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
17473 - Fix an assert-on-exit bug related to counting memory usage in
17474 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
17476 o Major bugfixes (crash on startup):
17477 - Fix a segfault during startup: If a Unix domain socket was
17478 configured as listener (such as a ControlSocket or a SocksPort
17479 "unix:" socket), and tor was started as root but not configured to
17480 switch to another user, tor would segfault while trying to string
17481 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
17484 o Major bugfixes (dns proxy mode, crash):
17485 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
17486 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
17488 o Major bugfixes (relays, bridge clients):
17489 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
17490 bridge clients use the address configured in the bridge line.
17491 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
17494 o Major bugfixes (voting):
17495 - Actually enable support for authorities to match routers by their
17496 Ed25519 identities. Previously, the code had been written, but
17497 some debugging code that had accidentally been left in the
17498 codebase made it stay turned off. Fixes bug 17702; bugfix
17500 - When collating votes by Ed25519 identities, authorities now
17501 include a "NoEdConsensus" flag if the ed25519 value (or lack
17502 thereof) for a server does not reflect the majority consensus.
17503 Related to bug 17668; bugfix on 0.2.7.2-alpha.
17504 - When generating a vote with keypinning disabled, never include two
17505 entries for the same ed25519 identity. This bug was causing
17506 authorities to generate votes that they could not parse when a
17507 router violated key pinning by changing its RSA identity but
17508 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
17509 18318. Bugfix on 0.2.7.2-alpha.
17511 o Minor features (security, win32):
17512 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
17513 attack. Fixes bug 18123; bugfix on all tor versions. Patch
17516 o Minor features (bug-resistance):
17517 - Make Tor survive errors involving connections without a
17518 corresponding event object. Previously we'd fail with an
17519 assertion; now we produce a log message. Related to bug 16248.
17521 o Minor features (build):
17522 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
17523 as having possible IPFW support. Closes ticket 18448. Patch from
17524 Steven Chamberlain.
17526 o Minor features (code hardening):
17527 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
17528 level code, to harden against accidental failures to NUL-
17529 terminate. Part of ticket 17852. Patch from jsturgix. Found
17532 o Minor features (crypto):
17533 - Validate the hard-coded Diffie-Hellman parameters and ensure that
17534 p is a safe prime, and g is a suitable generator. Closes
17537 o Minor features (geoip):
17538 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
17541 o Minor features (hidden service directory):
17542 - Streamline relay-side hsdir handling: when relays consider whether
17543 to accept an uploaded hidden service descriptor, they no longer
17544 check whether they are one of the relays in the network that is
17545 "supposed" to handle that descriptor. Implements ticket 18332.
17547 o Minor features (IPv6):
17548 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
17549 to 1, tor prefers IPv6 directory addresses.
17550 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
17551 avoids using IPv4 for client OR and directory connections.
17552 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
17553 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
17554 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
17556 o Minor features (linux seccomp2 sandbox):
17557 - Reject attempts to change our Address with "Sandbox 1" enabled.
17558 Changing Address with Sandbox turned on would never actually work,
17559 but previously it would fail in strange and confusing ways. Found
17560 while fixing 18548.
17562 o Minor features (robustness):
17563 - Exit immediately with an error message if the code attempts to use
17564 Libevent without having initialized it. This should resolve some
17565 frequently-made mistakes in our unit tests. Closes ticket 18241.
17567 o Minor features (unix domain sockets):
17568 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
17569 Unix domain sockets without checking the permissions on the parent
17570 directory. (Tor checks permissions by default because some
17571 operating systems only check permissions on the parent directory.
17572 However, some operating systems do look at permissions on the
17573 socket, and tor's default check is unneeded.) Closes ticket 18458.
17576 o Minor bugfixes (exit policies, security):
17577 - Refresh an exit relay's exit policy when interface addresses
17578 change. Previously, tor only refreshed the exit policy when the
17579 configured external address changed. Fixes bug 18208; bugfix on
17580 0.2.7.3-rc. Patch by teor.
17582 o Minor bugfixes (security, hidden services):
17583 - Prevent hidden services connecting to client-supplied rendezvous
17584 addresses that are reserved as internal or multicast. Fixes bug
17585 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
17587 o Minor bugfixes (build):
17588 - Do not link the unit tests against both the testing and non-
17589 testing versions of the static libraries. Fixes bug 18490; bugfix
17591 - Avoid spurious failures from configure files related to calling
17592 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
17593 0.2.0.1-alpha. Patch from "cypherpunks".
17594 - Silence spurious clang-scan warnings in the ed25519_donna code by
17595 explicitly initializing some objects. Fixes bug 18384; bugfix on
17596 0.2.7.2-alpha. Patch by teor.
17598 o Minor bugfixes (client, bootstrap):
17599 - Count receipt of new microdescriptors as progress towards
17600 bootstrapping. Previously, with EntryNodes set, Tor might not
17601 successfully repopulate the guard set on bootstrapping. Fixes bug
17602 16825; bugfix on 0.2.3.1-alpha.
17604 o Minor bugfixes (code correctness):
17605 - Update to the latest version of Trunnel, which tries harder to
17606 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
17607 by clang address sanitizer. Fixes bug 18373; bugfix
17610 o Minor bugfixes (configuration):
17611 - Fix a tiny memory leak when parsing a port configuration ending in
17612 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
17614 o Minor bugfixes (containers):
17615 - If we somehow attempt to construct a heap with more than
17616 1073741822 elements, avoid an integer overflow when maintaining
17617 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
17619 o Minor bugfixes (correctness):
17620 - Fix a bad memory handling bug that would occur if we had queued a
17621 cell on a channel's incoming queue. Fortunately, we can't actually
17622 queue a cell like that as our code is constructed today, but it's
17623 best to avoid this kind of error, even if there isn't any code
17624 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
17626 o Minor bugfixes (directory):
17627 - When generating a URL for a directory server on an IPv6 address,
17628 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
17629 on 0.2.3.9-alpha. Patch from Malek.
17631 o Minor bugfixes (fallback directory mirrors):
17632 - When requesting extrainfo descriptors from a trusted directory
17633 server, check whether it is an authority or a fallback directory
17634 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
17635 0.2.4.7-alpha. Reported by atagar, patch by teor.
17637 o Minor bugfixes (hidden service, client):
17638 - Handle the case where the user makes several fast consecutive
17639 requests to the same .onion address. Previously, the first six
17640 requests would each trigger a descriptor fetch, each picking a
17641 directory (there are 6 overall) and the seventh one would fail
17642 because no directories were left, thereby triggering a close on
17643 all current directory connections asking for the hidden service.
17644 The solution here is to not close the connections if we have
17645 pending directory fetches. Fixes bug 15937; bugfix
17648 o Minor bugfixes (hidden service, control port):
17649 - Add the onion address to the HS_DESC event for the UPLOADED action
17650 both on success or failure. It was previously hardcoded with
17651 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
17653 o Minor bugfixes (hidden service, directory):
17654 - Bridges now refuse "rendezvous2" (hidden service descriptor)
17655 publish attempts. Suggested by ticket 18332.
17657 o Minor bugfixes (linux seccomp2 sandbox):
17658 - Allow the setrlimit syscall, and the prlimit and prlimit64
17659 syscalls, which some libc implementations use under the hood.
17660 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
17661 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
17662 enabled and no DNS resolvers configured. This should help TAILS
17663 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
17664 - Fix the sandbox's interoperability with unix domain sockets under
17665 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
17667 o Minor bugfixes (logging):
17668 - When logging information about an unparsable networkstatus vote or
17669 consensus, do not say "vote" when we mean consensus. Fixes bug
17670 18368; bugfix on 0.2.0.8-alpha.
17671 - Scrub service name in "unrecognized service ID" log messages.
17672 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
17673 - Downgrade logs and backtraces about IP versions to info-level.
17674 Only log backtraces once each time tor runs. Assists in diagnosing
17675 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
17676 Christian, patch by teor.
17678 o Minor bugfixes (memory safety):
17679 - Avoid freeing an uninitialized pointer when opening a socket fails
17680 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
17681 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
17683 - Correctly duplicate addresses in get_interface_address6_list().
17684 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
17685 patch by "cypherpunks".
17686 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
17688 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
17689 18672; bugfix on 0.2.5.1-alpha.
17691 o Minor bugfixes (private directory):
17692 - Prevent a race condition when creating private directories. Fixes
17693 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
17694 Patch from jsturgix. Found with Flawfinder.
17696 o Minor bugfixes (test networks, IPv6):
17697 - Allow internal IPv6 addresses in descriptors in test networks.
17698 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
17701 o Minor bugfixes (testing):
17702 - We no longer disable assertions in the unit tests when coverage is
17703 enabled. Instead, we require you to say --disable-asserts-in-tests
17704 to the configure script if you need assertions disabled in the
17705 unit tests (for example, if you want to perform branch coverage).
17706 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
17708 o Minor bugfixes (time parsing):
17709 - Avoid overflow in tor_timegm when parsing dates in and after 2038
17710 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
17711 0.0.2pre14. Patch by teor.
17713 o Minor bugfixes (tor-gencert):
17714 - Correctly handle the case where an authority operator enters a
17715 passphrase but sends an EOF before sending a newline. Fixes bug
17716 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
17718 o Code simplification and refactoring:
17719 - Quote all the string interpolations in configure.ac -- even those
17720 which we are pretty sure can't contain spaces. Closes ticket
17721 17744. Patch from zerosion.
17722 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
17723 inplace, so there's no need to have a separate implementation for
17724 the non-inplace code. Closes ticket 18258. Patch from Malek.
17725 - Simplify return types for some crypto functions that can't
17726 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
17729 - Change build messages to refer to "Fedora" instead of "Fedora
17730 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
17731 Patches from "icanhasaccount" and "cypherpunks".
17733 o Removed features:
17734 - We no longer maintain an internal freelist in memarea.c.
17735 Allocators should be good enough to make this code unnecessary,
17736 and it's doubtful that it ever had any performance benefit.
17739 - Fix several warnings from clang's address sanitizer produced in
17741 - Treat backtrace test failures as expected on FreeBSD until we
17742 solve bug 17808. Closes ticket 18204.
17745 Changes in version 0.2.8.1-alpha - 2016-02-04
17746 Tor 0.2.8.1-alpha is the first alpha release in its series. It
17747 includes numerous small features and bugfixes against previous Tor
17748 versions, and numerous small infrastructure improvements. The most
17749 notable features are a set of improvements to the directory subsystem.
17751 o Major features (security, Linux):
17752 - When Tor starts as root on Linux and is told to switch user ID, it
17753 can now retain the capability to bind to low ports. By default,
17754 Tor will do this only when it's switching user ID and some low
17755 ports have been configured. You can change this behavior with the
17756 new option KeepBindCapabilities. Closes ticket 8195.
17758 o Major features (directory system):
17759 - When bootstrapping multiple consensus downloads at a time, use the
17760 first one that starts downloading, and close the rest. This
17761 reduces failures when authorities or fallback directories are slow
17762 or down. Together with the code for feature 15775, this feature
17763 should reduces failures due to fallback churn. Implements ticket
17764 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
17765 "mikeperry" and "teor".
17766 - Include a trial list of 21 default fallback directories, generated
17767 in January 2016, based on an opt-in survey of suitable relays.
17768 Doing this should make clients bootstrap more quickly and reliably,
17769 and reduce the load on the directory authorities. Closes ticket
17770 15775. Patch by "teor".
17771 Candidates identified using an OnionOO script by "weasel", "teor",
17772 "gsathya", and "karsten".
17773 - Previously only relays that explicitly opened a directory port
17774 (DirPort) accepted directory requests from clients. Now all
17775 relays, with and without a DirPort, accept and serve tunneled
17776 directory requests that they receive through their ORPort. You can
17777 disable this behavior using the new DirCache option. Closes
17780 o Major key updates:
17781 - Update the V3 identity key for the dannenberg directory authority:
17782 it was changed on 18 November 2015. Closes task 17906. Patch
17785 o Minor features (security, clock):
17786 - Warn when the system clock appears to move back in time (when the
17787 state file was last written in the future). Tor doesn't know that
17788 consensuses have expired if the clock is in the past. Patch by
17789 "teor". Implements ticket 17188.
17791 o Minor features (security, exit policies):
17792 - ExitPolicyRejectPrivate now rejects more private addresses by
17793 default. Specifically, it now rejects the relay's outbound bind
17794 addresses (if configured), and the relay's configured port
17795 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
17796 0.2.0.11-alpha. Patch by "teor".
17798 o Minor features (security, memory erasure):
17799 - Set the unused entries in a smartlist to NULL. This helped catch
17800 a (harmless) bug, and shouldn't affect performance too much.
17801 Implements ticket 17026.
17802 - Use SecureMemoryWipe() function to securely clean memory on
17803 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
17804 Implements feature 17986.
17805 - Use explicit_bzero or memset_s when present. Previously, we'd use
17806 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
17807 from <logan@hackers.mu> and <selven@hackers.mu>.
17808 - Make memwipe() do nothing when passed a NULL pointer or buffer of
17809 zero size. Check size argument to memwipe() for underflow. Fixes
17810 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
17813 o Minor features (security, RNG):
17814 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
17815 positively are not allowed to fail. Previously we depended on
17816 internal details of OpenSSL's behavior. Closes ticket 17686.
17817 - Never use the system entropy output directly for anything besides
17818 seeding the PRNG. When we want to generate important keys, instead
17819 of using system entropy directly, we now hash it with the PRNG
17820 stream. This may help resist certain attacks based on broken OS
17821 entropy implementations. Closes part of ticket 17694.
17822 - Use modern system calls (like getentropy() or getrandom()) to
17823 generate strong entropy on platforms that have them. Closes
17826 o Minor features (accounting):
17827 - Added two modes to the AccountingRule option: One for limiting
17828 only the number of bytes sent ("AccountingRule out"), and one for
17829 limiting only the number of bytes received ("AccountingRule in").
17830 Closes ticket 15989; patch from "unixninja92".
17832 o Minor features (build):
17833 - Since our build process now uses "make distcheck", we no longer
17834 force "make dist" to depend on "make check". Closes ticket 17893;
17835 patch from "cypherpunks."
17836 - Tor now builds successfully with the recent OpenSSL 1.1
17837 development branch, and with the latest LibreSSL. Closes tickets
17838 17549, 17921, and 17984.
17840 o Minor features (controller):
17841 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
17842 tickets 16774 and 17817. Patch by George Tankersley.
17843 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
17844 service descriptor from a service's local hidden service
17845 descriptor cache. Closes ticket 14846.
17846 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
17847 controllers can examine the the reject rules added by
17848 ExitPolicyRejectPrivate. This makes it easier for stem to display
17851 o Minor features (crypto):
17852 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
17854 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
17855 - When allocating a digest state object, allocate no more space than
17856 we actually need. Previously, we would allocate as much space as
17857 the state for the largest algorithm would need. This change saves
17858 up to 672 bytes per circuit. Closes ticket 17796.
17859 - Improve performance when hashing non-multiple of 8 sized buffers,
17860 based on Andrew Moon's public domain SipHash-2-4 implementation.
17861 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
17863 o Minor features (directory downloads):
17864 - Wait for busy authorities and fallback directories to become non-
17865 busy when bootstrapping. (A similar change was made in 6c443e987d
17866 for directory caches chosen from the consensus.) Closes ticket
17867 17864; patch by "teor".
17868 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
17869 directory mirrors. The default is 1; set it to 0 to disable
17870 fallbacks. Implements ticket 17576. Patch by "teor".
17872 o Minor features (geoip):
17873 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
17876 o Minor features (IPv6):
17877 - Add an argument 'ipv6=address:orport' to the DirAuthority and
17878 FallbackDir torrc options, to specify an IPv6 address for an
17879 authority or fallback directory. Add hard-coded ipv6 addresses for
17880 directory authorities that have them. Closes ticket 17327; patch
17881 from Nick Mathewson and "teor".
17882 - Add address policy assume_action support for IPv6 addresses.
17883 - Limit IPv6 mask bits to 128.
17884 - Warn when comparing against an AF_UNSPEC address in a policy, it's
17885 almost always a bug. Closes ticket 17863; patch by "teor".
17886 - Allow users to configure directory authorities and fallback
17887 directory servers with IPv6 addresses and ORPorts. Resolves
17889 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
17890 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
17891 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
17892 17638; bugfix on 0.0.2pre8. Patch by "teor".
17894 o Minor features (logging):
17895 - When logging to syslog, allow a tag to be added to the syslog
17896 identity (the string prepended to every log message). The tag can
17897 be configured with SyslogIdentityTag and defaults to none. Setting
17898 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
17901 o Minor features (portability):
17902 - Use timingsafe_memcmp() where available. Closes ticket 17944;
17903 patch from <logan@hackers.mu>.
17905 o Minor features (relay, address discovery):
17906 - Add a family argument to get_interface_addresses_raw() and
17907 subfunctions to make network interface address interogation more
17908 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
17909 types of interfaces from the operating system. Resolves
17911 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
17912 fails to enumerate interface addresses using the platform-specific
17913 API, have it rely on the UDP socket fallback technique to try and
17914 find out what IP addresses (both IPv4 and IPv6) our machine has.
17915 Resolves ticket 17951.
17917 o Minor features (replay cache):
17918 - The replay cache now uses SHA256 instead of SHA1. Implements
17919 feature 8961. Patch by "teor", issue reported by "rransom".
17921 o Minor features (unix file permissions):
17922 - Defer creation of Unix sockets until after setuid. This avoids
17923 needing CAP_CHOWN and CAP_FOWNER when using systemd's
17924 CapabilityBoundingSet, or chown and fowner when using SELinux.
17925 Implements part of ticket 17562. Patch from Jamie Nguyen.
17926 - If any directory created by Tor is marked as group readable, the
17927 filesystem group is allowed to be either the default GID or the
17928 root user. Allowing root to read the DataDirectory prevents the
17929 need for CAP_READ_SEARCH when using systemd's
17930 CapabilityBoundingSet, or dac_read_search when using SELinux.
17931 Implements part of ticket 17562. Patch from Jamie Nguyen.
17932 - Introduce a new DataDirectoryGroupReadable option. If it is set to
17933 1, the DataDirectory will be made readable by the default GID.
17934 Implements part of ticket 17562. Patch from Jamie Nguyen.
17936 o Minor bugfixes (accounting):
17937 - The max bandwidth when using 'AccountRule sum' is now correctly
17938 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
17939 from "unixninja92".
17941 o Minor bugfixes (code correctness):
17942 - When closing an entry connection, generate a warning if we should
17943 have sent an end cell for it but we haven't. Fixes bug 17876;
17944 bugfix on 0.2.3.2-alpha.
17945 - Assert that allocated memory held by the reputation code is freed
17946 according to its internal counters. Fixes bug 17753; bugfix
17948 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
17951 o Minor bugfixes (compilation):
17952 - Mark all object files that include micro-revision.i as depending
17953 on it, so as to make parallel builds more reliable. Fixes bug
17954 17826; bugfix on 0.2.5.1-alpha.
17955 - Don't try to use the pthread_condattr_setclock() function unless
17956 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
17957 17819; bugfix on 0.2.6.3-alpha.
17958 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
17960 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
17961 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
17962 - Fix search for libevent libraries on OpenBSD (and other systems
17963 that install libevent 1 and libevent 2 in parallel). Fixes bug
17964 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
17965 - Isolate environment variables meant for tests from the rest of the
17966 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
17967 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
17969 - Remove config.log only from make distclean, not from make clean.
17970 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
17972 o Minor bugfixes (crypto):
17973 - Check the return value of HMAC() and assert on failure. Fixes bug
17974 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
17976 o Minor bugfixes (fallback directories):
17977 - Mark fallbacks as "too busy" when they return a 503 response,
17978 rather than just marking authorities. Fixes bug 17572; bugfix on
17979 0.2.4.7-alpha. Patch by "teor".
17981 o Minor bugfixes (IPv6):
17982 - Update the limits in max_dl_per_request for IPv6 address length.
17983 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
17985 o Minor bugfixes (linux seccomp2 sandbox):
17986 - Fix a crash when using offline master ed25519 keys with the Linux
17987 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
17989 o Minor bugfixes (logging):
17990 - In log messages that include a function name, use __FUNCTION__
17991 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
17992 with clang __PRETTY_FUNCTION__ has extra information we don't
17993 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
17995 - Remove needless quotes from a log message about unparseable
17996 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
17998 o Minor bugfixes (portability):
17999 - Remove an #endif from configure.ac so that we correctly detect the
18000 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
18003 o Minor bugfixes (relays):
18004 - Check that both the ORPort and DirPort (if present) are reachable
18005 before publishing a relay descriptor. Otherwise, relays publish a
18006 descriptor with DirPort 0 when the DirPort reachability test takes
18007 longer than the ORPort reachability test. Fixes bug 18050; bugfix
18008 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
18010 o Minor bugfixes (relays, hidden services):
18011 - Refuse connection requests to private OR addresses unless
18012 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
18013 then refuse to send any cells to a private address. Fixes bugs
18014 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
18016 o Minor bugfixes (safe logging):
18017 - When logging a malformed hostname received through socks4, scrub
18018 it if SafeLogging says we should. Fixes bug 17419; bugfix
18021 o Minor bugfixes (statistics code):
18022 - Consistently check for overflow in round_*_to_next_multiple_of
18023 functions, and add unit tests with additional and maximal values.
18024 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
18025 - Handle edge cases in the laplace functions: avoid division by
18026 zero, avoid taking the log of zero, and silence clang type
18027 conversion warnings using round and trunc. Add unit tests for edge
18028 cases with maximal values. Fixes part of bug 13192; bugfix
18031 o Minor bugfixes (testing):
18032 - The test for log_heartbeat was incorrectly failing in timezones
18033 with non-integer offsets. Instead of comparing the end of the time
18034 string against a constant, compare it to the output of
18035 format_local_iso_time when given the correct input. Fixes bug
18036 18039; bugfix on 0.2.5.4-alpha.
18037 - Make unit tests pass on IPv6-only systems, and systems without
18038 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
18039 bugfix on 0.2.7.3-rc. Patch by "teor".
18040 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
18042 - Check the full results of SHA256 and SHA512 digests in the unit
18043 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
18045 o Code simplification and refactoring:
18046 - Move logging of redundant policy entries in
18047 policies_parse_exit_policy_internal into its own function. Closes
18048 ticket 17608; patch from "juce".
18049 - Extract the more complicated parts of circuit_mark_for_close()
18050 into a new function that we run periodically before circuits are
18051 freed. This change removes more than half of the functions
18052 currently in the "blob". Closes ticket 17218.
18053 - Clean up a little duplicated code in
18054 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
18056 - Decouple the list of streams waiting to be attached to circuits
18057 from the overall connection list. This change makes it possible to
18058 attach streams quickly while simplifying Tor's callgraph and
18059 avoiding O(N) scans of the entire connection list. Closes
18061 - When a direct directory request fails immediately on launch,
18062 instead of relaunching that request from inside the code that
18063 launches it, instead mark the connection for teardown. This change
18064 simplifies Tor's callback and prevents the directory-request
18065 launching code from invoking itself recursively. Closes
18067 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
18068 use them. Closes ticket 17926.
18071 - Add a description of the correct use of the '--keygen' command-
18072 line option. Closes ticket 17583; based on text by 's7r'.
18073 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
18074 - Explain actual minima for BandwidthRate. Closes ticket 16382.
18075 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
18076 - Mention torspec URL in the manpage and point the reader to it
18077 whenever we mention a document that belongs in torspce. Fixes
18080 o Removed features:
18081 - Remove client-side support for connecting to Tor relays running
18082 versions of Tor before 0.2.3.6-alpha. These relays didn't support
18083 the v3 TLS handshake protocol, and are no longer allowed on the
18084 Tor network. Implements the client side of ticket 11150. Based on
18085 patches by Tom van der Woerdt.
18088 - Add unit tests to check for common RNG failure modes, such as
18089 returning all zeroes, identical values, or incrementing values
18090 (OpenSSL's rand_predictable feature). Patch by "teor".
18091 - Log more information when the backtrace tests fail. Closes ticket
18092 17892. Patch from "cypherpunks."
18093 - Always test both ed25519 backends, so that we can be sure that our
18094 batch-open replacement code works. Part of ticket 16794.
18095 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
18096 portion of ticket 16831.
18097 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
18098 util_format.c, directory.c, and options_validate.c. Closes tickets
18099 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
18101 - Unit tests for directory_handle_command_get. Closes ticket 17004.
18102 Patch from Reinaldo de Souza Jr.
18105 Changes in version 0.2.7.6 - 2015-12-10
18106 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
18107 well as a minor bug in hidden service reliability.
18109 o Major bugfixes (guard selection):
18110 - Actually look at the Guard flag when selecting a new directory
18111 guard. When we implemented the directory guard design, we
18112 accidentally started treating all relays as if they have the Guard
18113 flag during guard selection, leading to weaker anonymity and worse
18114 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
18117 o Minor features (geoip):
18118 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
18121 o Minor bugfixes (compilation):
18122 - When checking for net/pfvar.h, include netinet/in.h if possible.
18123 This fixes transparent proxy detection on OpenBSD. Fixes bug
18124 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
18125 - Fix a compilation warning with Clang 3.6: Do not check the
18126 presence of an address which can never be NULL. Fixes bug 17781.
18128 o Minor bugfixes (correctness):
18129 - When displaying an IPv6 exit policy, include the mask bits
18130 correctly even when the number is greater than 31. Fixes bug
18131 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
18132 - The wrong list was used when looking up expired intro points in a
18133 rend service object, causing what we think could be reachability
18134 issues for hidden services, and triggering a BUG log. Fixes bug
18135 16702; bugfix on 0.2.7.2-alpha.
18136 - Fix undefined behavior in the tor_cert_checksig function. Fixes
18137 bug 17722; bugfix on 0.2.7.2-alpha.
18140 Changes in version 0.2.7.5 - 2015-11-20
18141 The Tor 0.2.7 release series is dedicated to the memory of Tor user
18142 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
18143 tirelessly to advocate human rights regardless of national borders,
18144 and oppose the encroachments of mass surveillance. He opposed national
18145 exceptionalism, he brought clarity to legal and policy debates, he
18146 understood and predicted the impact of mass surveillance on the world,
18147 and he laid the groundwork for resisting it. While serving on the Tor
18148 Project's board of directors, he brought us his uncompromising focus
18149 on technical excellence in the service of humankind. Caspar was an
18150 inimitable force for good and a wonderful friend. He was kind,
18151 humorous, generous, gallant, and believed we should protect one
18152 another without exception. We honor him here for his ideals, his
18153 efforts, and his accomplishments. Please honor his memory with works
18154 that would make him proud.
18156 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
18158 The 0.2.7 series adds a more secure identity key type for relays,
18159 improves cryptography performance, resolves several longstanding
18160 hidden-service performance issues, improves controller support for
18161 hidden services, and includes small bugfixes and performance
18162 improvements throughout the program. This release series also includes
18163 more tests than before, and significant simplifications to which parts
18164 of Tor invoke which others.
18166 (This release contains no code changes since 0.2.7.4-rc.)
18169 Changes in version 0.2.7.4-rc - 2015-10-21
18170 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
18171 fixes some important memory leaks, and a scary-looking (but mostly
18172 harmless in practice) invalid-read bug. It also has a few small
18173 bugfixes, notably fixes for compilation and portability on different
18174 platforms. If no further significant bounds are found, the next
18175 release will the the official stable release.
18177 o Major bugfixes (security, correctness):
18178 - Fix an error that could cause us to read 4 bytes before the
18179 beginning of an openssl string. This bug could be used to cause
18180 Tor to crash on systems with unusual malloc implementations, or
18181 systems with unusual hardening installed. Fixes bug 17404; bugfix
18184 o Major bugfixes (correctness):
18185 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
18186 bug 17401; bugfix on 0.2.7.3-rc.
18188 o Major bugfixes (memory leaks):
18189 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
18190 17398; bugfix on 0.2.6.1-alpha.
18191 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
18192 17402; bugfix on 0.2.7.3-rc.
18193 - Fix a memory leak when reading an expired signing key from disk.
18194 Fixes bug 17403; bugfix on 0.2.7.2-rc.
18196 o Minor features (geoIP):
18197 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
18200 o Minor bugfixes (compilation):
18201 - Repair compilation with the most recent (unreleased, alpha)
18202 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
18203 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
18204 17251; bugfix on 0.2.7.2-alpha.
18205 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
18206 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
18208 o Minor bugfixes (portability):
18209 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
18210 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
18213 o Minor bugfixes (sandbox):
18214 - Add the "hidserv-stats" filename to our sandbox filter for the
18215 HiddenServiceStatistics option to work properly. Fixes bug 17354;
18216 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
18218 o Minor bugfixes (testing):
18219 - Add unit tests for get_interface_address* failure cases. Fixes bug
18220 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
18221 - Fix breakage when running 'make check' with BSD make. Fixes bug
18222 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
18223 - Make the get_ifaddrs_* unit tests more tolerant of different
18224 network configurations. (Don't assume every test box has an IPv4
18225 address, and don't assume every test box has a non-localhost
18226 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
18227 - Skip backtrace tests when backtrace support is not compiled in.
18228 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
18232 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
18233 - Note that HiddenServicePorts can take a unix domain socket. Closes
18237 Changes in version 0.2.7.3-rc - 2015-09-25
18238 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
18239 contains numerous usability fixes for Ed25519 keys, safeguards against
18240 several misconfiguration problems, significant simplifications to
18241 Tor's callgraph, and numerous bugfixes and small features.
18243 This is the most tested release of Tor to date. The unit tests cover
18244 39.40% of the code, and the integration tests (accessible with "make
18245 test-full-online", requiring stem and chutney and a network
18246 connection) raise the coverage to 64.49%.
18248 o Major features (security, hidden services):
18249 - Hidden services, if using the EntryNodes option, are required to
18250 use more than one EntryNode, in order to avoid a guard discovery
18251 attack. (This would only affect people who had configured hidden
18252 services and manually specified the EntryNodes option with a
18253 single entry-node. The impact was that it would be easy to
18254 remotely identify the guard node used by such a hidden service.
18255 See ticket for more information.) Fixes ticket 14917.
18257 o Major features (Ed25519 keys, keypinning):
18258 - The key-pinning option on directory authorities is now advisory-
18259 only by default. In a future version, or when the AuthDirPinKeys
18260 option is set, pins are enforced again. Disabling key-pinning
18261 seemed like a good idea so that we can survive the fallout of any
18262 usability problems associated with Ed25519 keys. Closes
18265 o Major features (Ed25519 performance):
18266 - Improve the speed of Ed25519 operations and Curve25519 keypair
18267 generation when built targeting 32 bit x86 platforms with SSE2
18268 available. Implements ticket 16535.
18269 - Improve the runtime speed of Ed25519 signature verification by
18270 using Ed25519-donna's batch verification support. Implements
18273 o Major features (performance testing):
18274 - The test-network.sh script now supports performance testing.
18275 Requires corresponding chutney performance testing changes. Patch
18276 by "teor". Closes ticket 14175.
18278 o Major features (relay, Ed25519):
18279 - Significant usability improvements for Ed25519 key management. Log
18280 messages are better, and the code can recover from far more
18281 failure conditions. Thanks to "s7r" for reporting and diagnosing
18283 - Add a new OfflineMasterKey option to tell Tor never to try loading
18284 or generating a secret Ed25519 identity key. You can use this in
18285 combination with tor --keygen to manage offline and/or encrypted
18286 Ed25519 keys. Implements ticket 16944.
18287 - Add a --newpass option to allow changing or removing the
18288 passphrase of an encrypted key with tor --keygen. Implements part
18290 - On receiving a HUP signal, check to see whether the Ed25519
18291 signing key has changed, and reload it if so. Closes ticket 16790.
18293 o Major bugfixes (relay, Ed25519):
18294 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
18295 0.2.7.2-alpha. Reported by "s7r".
18296 - Improve handling of expired signing keys with offline master keys.
18297 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
18299 o Minor features (client-side privacy):
18300 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
18301 lifespan when IsolateSOCKSAuth and streams with SOCKS
18302 authentication are attached to the circuit. This allows
18303 applications like TorBrowser to manage circuit lifetime on their
18304 own. Implements feature 15482.
18305 - When logging malformed hostnames from SOCKS5 requests, respect
18306 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
18308 o Minor features (compilation):
18309 - Give a warning as early as possible when trying to build with an
18310 unsupported OpenSSL version. Closes ticket 16901.
18311 - Fail during configure if we're trying to build against an OpenSSL
18312 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
18313 which started requiring ECC.
18315 o Minor features (geoip):
18316 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
18319 o Minor features (hidden services):
18320 - Relays need to have the Fast flag to get the HSDir flag. As this
18321 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
18322 drop. This change should make some attacks against the hidden
18323 service directory system harder. Fixes ticket 15963.
18324 - Turn on hidden service statistics collection by setting the torrc
18325 option HiddenServiceStatistics to "1" by default. (This keeps
18326 track only of the fraction of traffic used by hidden services, and
18327 the total number of hidden services in existence.) Closes
18329 - Client now uses an introduction point failure cache to know when
18330 to fetch or keep a descriptor in their cache. Previously, failures
18331 were recorded implicitly, but not explicitly remembered. Closes
18334 o Minor features (testing, authorities, documentation):
18335 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
18336 explicitly manage consensus flags in testing networks. Patch by
18337 "robgjansen", modified by "teor". Implements part of ticket 14882.
18339 o Minor bugfixes (security, exit policies):
18340 - ExitPolicyRejectPrivate now also rejects the relay's published
18341 IPv6 address (if any), and any publicly routable IPv4 or IPv6
18342 addresses on any local interfaces. ticket 17027. Patch by "teor".
18343 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
18345 o Minor bug fixes (torrc exit policies):
18346 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
18347 produce IPv6 wildcard addresses. Previously they would produce
18348 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
18349 of bug 16069; bugfix on 0.2.4.7-alpha.
18350 - When parsing torrc ExitPolicies, we now warn for a number of cases
18351 where the user's intent is likely to differ from Tor's actual
18352 behavior. These include: using an IPv4 address with an accept6 or
18353 reject6 line; using "private" on an accept6 or reject6 line; and
18354 including any ExitPolicy lines after accept *:* or reject *:*.
18355 Related to ticket 16069.
18356 - When parsing torrc ExitPolicies, we now issue an info-level
18357 message when expanding an "accept/reject *" line to include both
18358 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
18359 - In each instance above, usage advice is provided to avoid the
18360 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
18361 16069; bugfix on 0.2.4.7-alpha.
18363 o Minor bugfixes (authority):
18364 - Don't assign "HSDir" to a router if it isn't Valid and Running.
18365 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
18366 - Downgrade log messages about Ed25519 key issues if they are in old
18367 cached router descriptors. Fixes part of bug 16286; bugfix
18369 - When we find an Ed25519 key issue in a cached descriptor, stop
18370 saying the descriptor was just "uploaded". Fixes another part of
18371 bug 16286; bugfix on 0.2.7.2-alpha.
18373 o Minor bugfixes (control port):
18374 - Repair a warning and a spurious result when getting the maximum
18375 number of file descriptors from the controller. Fixes bug 16697;
18376 bugfix on 0.2.7.2-alpha.
18378 o Minor bugfixes (correctness):
18379 - When calling channel_free_list(), avoid calling smartlist_remove()
18380 while inside a FOREACH loop. This partially reverts commit
18381 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
18382 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
18384 o Minor bugfixes (documentation):
18385 - Advise users on how to configure separate IPv4 and IPv6 exit
18386 policies in the manpage and sample torrcs. Related to ticket 16069.
18387 - Fix the usage message of tor-resolve(1) so that it no longer lists
18388 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
18389 - Fix an error in the manual page and comments for
18390 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
18391 required "ORPort connectivity". While this is true, it is in no
18392 way unique to the HSDir flag. Of all the flags, only HSDirs need a
18393 DirPort configured in order for the authorities to assign that
18394 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
18397 o Minor bugfixes (Ed25519):
18398 - Fix a memory leak when reading router descriptors with expired
18399 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
18401 o Minor bugfixes (linux seccomp2 sandbox):
18402 - Allow bridge authorities to run correctly under the seccomp2
18403 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
18404 - Allow routers with ed25519 keys to run correctly under the
18405 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
18407 o Minor bugfixes (open file limit):
18408 - Fix set_max_file_descriptors() to set by default the max open file
18409 limit to the current limit when setrlimit() fails. Fixes bug
18410 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
18412 o Minor bugfixes (portability):
18413 - Try harder to normalize the exit status of the Tor process to the
18414 standard-provided range. Fixes bug 16975; bugfix on every version
18416 - Check correctly for Windows socket errors in the workqueue
18417 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
18418 - Fix the behavior of crypto_rand_time_range() when told to consider
18419 times before 1970. (These times were possible when running in a
18420 simulated network environment where time()'s output starts at
18421 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
18422 - Restore correct operation of TLS client-cipher detection on
18423 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
18425 o Minor bugfixes (relay):
18426 - Ensure that worker threads actually exit when a fatal error or
18427 shutdown is indicated. This fix doesn't currently affect the
18428 behavior of Tor, because Tor workers never indicates fatal error
18429 or shutdown except in the unit tests. Fixes bug 16868; bugfix
18431 - Unblock threads before releasing the work queue mutex to ensure
18432 predictable scheduling behavior. Fixes bug 16644; bugfix
18435 o Code simplification and refactoring:
18436 - Change the function that's called when we need to retry all
18437 downloads so that it only reschedules the downloads to happen
18438 immediately, rather than launching them all at once itself. This
18439 further simplifies Tor's callgraph.
18440 - Move some format-parsing functions out of crypto.c and
18441 crypto_curve25519.c into crypto_format.c and/or util_format.c.
18442 - Move the client-only parts of init_keys() into a separate
18443 function. Closes ticket 16763.
18444 - Simplify the microdesc_free() implementation so that it no longer
18445 appears (to code analysis tools) to potentially invoke a huge
18446 suite of other microdesc functions.
18447 - Simply the control graph further by deferring the inner body of
18448 directory_all_unreachable() into a callback. Closes ticket 16762.
18449 - Treat the loss of an owning controller as equivalent to a SIGTERM
18450 signal. This removes a tiny amount of duplicated code, and
18451 simplifies our callgraph. Closes ticket 16788.
18452 - When generating an event to send to the controller, we no longer
18453 put the event over the network immediately. Instead, we queue
18454 these events, and use a Libevent callback to deliver them. This
18455 change simplifies Tor's callgraph by reducing the number of
18456 functions from which all other Tor functions are reachable. Closes
18458 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
18459 that try to scan or compile every file on Unix won't decide that
18461 - Remove the unused "nulterminate" argument from buf_pullup().
18464 - Recommend a 40 GB example AccountingMax in torrc.sample rather
18465 than a 4 GB max. Closes ticket 16742.
18466 - Include the TUNING document in our source tarball. It is referred
18467 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
18471 - The internal pure-C tor-fw-helper tool is now removed from the Tor
18472 distribution, in favor of the pure-Go clone available from
18473 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
18474 used by the C tor-fw-helper are not, in our opinion, very
18475 confidence- inspiring in their secure-programming techniques.
18476 Closes ticket 13338.
18477 - Remove the code that would try to aggressively flush controller
18478 connections while writing to them. This code was introduced in
18479 0.1.2.7-alpha, in order to keep output buffers from exceeding
18480 their limits. But there is no longer a maximum output buffer size,
18481 and flushing data in this way caused some undesirable recursions
18482 in our call graph. Closes ticket 16480.
18485 - Make "bridges+hs" the default test network. This tests almost all
18486 tor functionality during make test-network, while allowing tests
18487 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
18488 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
18489 (chutney). Patches by "teor".
18490 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
18491 by-side in the same parent directory. Closes ticket 16903. Patch
18493 - Use environment variables rather than autoconf substitutions to
18494 send variables from the build system to the test scripts. This
18495 change should be easier to maintain, and cause 'make distcheck' to
18496 work better than before. Fixes bug 17148.
18497 - Add a new set of callgraph analysis scripts that use clang to
18498 produce a list of which Tor functions are reachable from which
18499 other Tor functions. We're planning to use these to help simplify
18500 our code structure by identifying illogical dependencies.
18501 - Add new 'test-full' and 'test-full-online' targets to run all
18502 tests, including integration tests with stem and chutney.
18503 - Make the test-workqueue test work on Windows by initializing the
18504 network before we begin.
18505 - New make target (make test-network-all) to run multiple applicable
18506 chutney test cases. Patch from Teor; closes 16953.
18507 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
18508 functions in dns.c. Implements a portion of ticket 16831.
18509 - When building Tor with testing coverage enabled, run Chutney tests
18510 (if any) using the 'tor-cov' coverage binary.
18511 - When running test-network or test-stem, check for the absence of
18512 stem/chutney before doing any build operations.
18515 Changes in version 0.2.7.2-alpha - 2015-07-27
18516 This, the second alpha in the Tor 0.2.7 series, has a number of new
18517 features, including a way to manually pick the number of introduction
18518 points for hidden services, and the much stronger Ed25519 signing key
18519 algorithm for regular Tor relays (including support for encrypted
18520 offline identity keys in the new algorithm).
18522 Support for Ed25519 on relays is currently limited to signing router
18523 descriptors; later alphas in this series will extend Ed25519 key
18524 support to more parts of the Tor protocol.
18526 o Major features (Ed25519 identity keys, Proposal 220):
18527 - All relays now maintain a stronger identity key, using the Ed25519
18528 elliptic curve signature format. This master key is designed so
18529 that it can be kept offline. Relays also generate an online
18530 signing key, and a set of other Ed25519 keys and certificates.
18531 These are all automatically regenerated and rotated as needed.
18532 Implements part of ticket 12498.
18533 - Directory authorities now vote on Ed25519 identity keys along with
18534 RSA1024 keys. Implements part of ticket 12498.
18535 - Directory authorities track which Ed25519 identity keys have been
18536 used with which RSA1024 identity keys, and do not allow them to
18537 vary freely. Implements part of ticket 12498.
18538 - Microdescriptors now include Ed25519 identity keys. Implements
18539 part of ticket 12498.
18540 - Add support for offline encrypted Ed25519 master keys. To use this
18541 feature on your tor relay, run "tor --keygen" to make a new master
18542 key (or to make a new signing key if you already have a master
18543 key). Closes ticket 13642.
18545 o Major features (Hidden services):
18546 - Add the torrc option HiddenServiceNumIntroductionPoints, to
18547 specify a fixed number of introduction points. Its maximum value
18548 is 10 and default is 3. Using this option can increase a hidden
18549 service's reliability under load, at the cost of making it more
18550 visible that the hidden service is facing extra load. Closes
18552 - Remove the adaptive algorithm for choosing the number of
18553 introduction points, which used to change the number of
18554 introduction points (poorly) depending on the number of
18555 connections the HS sees. Closes ticket 4862.
18557 o Major features (onion key cross-certification):
18558 - Relay descriptors now include signatures of their own identity
18559 keys, made using the TAP and ntor onion keys. These signatures
18560 allow relays to prove ownership of their own onion keys. Because
18561 of this change, microdescriptors will no longer need to include
18562 RSA identity keys. Implements proposal 228; closes ticket 12499.
18564 o Major features (performance):
18565 - Improve the runtime speed of Ed25519 operations by using the
18566 public-domain Ed25519-donna by Andrew M. ("floodyberry").
18567 Implements ticket 16467.
18568 - Improve the runtime speed of the ntor handshake by using an
18569 optimized curve25519 basepoint scalarmult implementation from the
18570 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
18571 ideas by Adam Langley. Implements ticket 9663.
18573 o Major bugfixes (client-side privacy, also in 0.2.6.9):
18574 - Properly separate out each SOCKSPort when applying stream
18575 isolation. The error occurred because each port's session group
18576 was being overwritten by a default value when the listener
18577 connection was initialized. Fixes bug 16247; bugfix on
18578 0.2.6.3-alpha. Patch by "jojelino".
18580 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
18581 - Stop refusing to store updated hidden service descriptors on a
18582 client. This reverts commit 9407040c59218 (which indeed fixed bug
18583 14219, but introduced a major hidden service reachability
18584 regression detailed in bug 16381). This is a temporary fix since
18585 we can live with the minor issue in bug 14219 (it just results in
18586 some load on the network) but the regression of 16381 is too much
18587 of a setback. First-round fix for bug 16381; bugfix
18590 o Major bugfixes (hidden services):
18591 - When cannibalizing a circuit for an introduction point, always
18592 extend to the chosen exit node (creating a 4 hop circuit).
18593 Previously Tor would use the current circuit exit node, which
18594 changed the original choice of introduction point, and could cause
18595 the hidden service to skip excluded introduction points or
18596 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
18599 o Major bugfixes (open file limit):
18600 - The open file limit wasn't checked before calling
18601 tor_accept_socket_nonblocking(), which would make Tor exceed the
18602 limit. Now, before opening a new socket, Tor validates the open
18603 file limit just before, and if the max has been reached, return an
18604 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
18606 o Major bugfixes (stability, also in 0.2.6.10):
18607 - Stop crashing with an assertion failure when parsing certain kinds
18608 of malformed or truncated microdescriptors. Fixes bug 16400;
18609 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
18610 by "cypherpunks_backup".
18611 - Stop random client-side assertion failures that could occur when
18612 connecting to a busy hidden service, or connecting to a hidden
18613 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
18616 o Minor features (directory authorities, security, also in 0.2.6.9):
18617 - The HSDir flag given by authorities now requires the Stable flag.
18618 For the current network, this results in going from 2887 to 2806
18619 HSDirs. Also, it makes it harder for an attacker to launch a sybil
18620 attack by raising the effort for a relay to become Stable to
18621 require at the very least 7 days, while maintaining the 96 hours
18622 uptime requirement for HSDir. Implements ticket 8243.
18624 o Minor features (client):
18625 - Relax the validation of hostnames in SOCKS5 requests, allowing the
18626 character '_' to appear, in order to cope with domains observed in
18627 the wild that are serving non-RFC compliant records. Resolves
18629 - Relax the validation done to hostnames in SOCKS5 requests, and
18630 allow a single trailing '.' to cope with clients that pass FQDNs
18631 using that syntax to explicitly indicate that the domain name is
18632 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
18633 - Add GroupWritable and WorldWritable options to unix-socket based
18634 SocksPort and ControlPort options. These options apply to a single
18635 socket, and override {Control,Socks}SocketsGroupWritable. Closes
18638 o Minor features (control protocol):
18639 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
18640 the control protocol. Resolves ticket 15358.
18642 o Minor features (directory authorities):
18643 - Directory authorities no longer vote against the "Fast", "Stable",
18644 and "HSDir" flags just because they were going to vote against
18645 "Running": if the consensus turns out to be that the router was
18646 running, then the authority's vote should count. Patch from Peter
18647 Retzlaff; closes issue 8712.
18649 o Minor features (geoip, also in 0.2.6.10):
18650 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
18651 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
18653 o Minor features (hidden services):
18654 - Add the new options "HiddenServiceMaxStreams" and
18655 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
18656 limit the maximum number of simultaneous streams per circuit, and
18657 optionally tear down the circuit when the limit is exceeded. Part
18660 o Minor features (portability):
18661 - Use C99 variadic macros when the compiler is not GCC. This avoids
18662 failing compilations on MSVC, and fixes a log-file-based race
18663 condition in our old workarounds. Original patch from Gisle Vanem.
18665 o Minor bugfixes (compilation, also in 0.2.6.9):
18666 - Build with --enable-systemd correctly when libsystemd is
18667 installed, but systemd is not. Fixes bug 16164; bugfix on
18668 0.2.6.3-alpha. Patch from Peter Palfrader.
18670 o Minor bugfixes (controller):
18671 - Add the descriptor ID in each HS_DESC control event. It was
18672 missing, but specified in control-spec.txt. Fixes bug 15881;
18673 bugfix on 0.2.5.2-alpha.
18675 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
18676 - Check for failures from crypto_early_init, and refuse to continue.
18677 A previous typo meant that we could keep going with an
18678 uninitialized crypto library, and would have OpenSSL initialize
18679 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
18680 when implementing ticket 4900. Patch by "teor".
18682 o Minor bugfixes (hidden services):
18683 - Fix a crash when reloading configuration while at least one
18684 configured and one ephemeral hidden service exists. Fixes bug
18685 16060; bugfix on 0.2.7.1-alpha.
18686 - Avoid crashing with a double-free bug when we create an ephemeral
18687 hidden service but adding it fails for some reason. Fixes bug
18688 16228; bugfix on 0.2.7.1-alpha.
18690 o Minor bugfixes (Linux seccomp2 sandbox):
18691 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
18692 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
18694 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
18695 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
18696 these when eventfd2() support is missing. Fixes bug 16363; bugfix
18697 on 0.2.6.3-alpha. Patch from "teor".
18699 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
18700 - Fix sandboxing to work when running as a relay, by allowing the
18701 renaming of secret_id_key, and allowing the eventfd2 and futex
18702 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
18704 - Allow systemd connections to work with the Linux seccomp2 sandbox
18705 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
18708 o Minor bugfixes (relay):
18709 - Fix a rarely-encountered memory leak when failing to initialize
18710 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
18711 from "cypherpunks".
18713 o Minor bugfixes (systemd):
18714 - Fix an accidental formatting error that broke the systemd
18715 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
18716 - Tor's systemd unit file no longer contains extraneous spaces.
18717 These spaces would sometimes confuse tools like deb-systemd-
18718 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
18720 o Minor bugfixes (tests):
18721 - Use the configured Python executable when running test-stem-full.
18722 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
18724 o Minor bugfixes (tests, also in 0.2.6.9):
18725 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
18726 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
18728 o Minor bugfixes (threads, comments):
18729 - Always initialize return value in compute_desc_id in rendcommon.c
18730 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
18731 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
18732 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
18733 - Remove undefined directive-in-macro in test_util_writepid clang
18734 3.7 complains that using a preprocessor directive inside a macro
18735 invocation in test_util_writepid in test_util.c is undefined.
18736 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
18738 o Code simplification and refactoring:
18739 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
18740 to ensure they remain consistent and visible everywhere.
18741 - Remove some vestigial workarounds for the MSVC6 compiler. We
18742 haven't supported that in ages.
18743 - The link authentication code has been refactored for better
18744 testability and reliability. It now uses code generated with the
18745 "trunnel" binary encoding generator, to reduce the risk of bugs
18746 due to programmer error. Done as part of ticket 12498.
18749 - Include a specific and (hopefully) accurate documentation of the
18750 torrc file's meta-format in doc/torrc_format.txt. This is mainly
18751 of interest to people writing programs to parse or generate torrc
18752 files. This document is not a commitment to long-term
18753 compatibility; some aspects of the current format are a bit
18754 ridiculous. Closes ticket 2325.
18756 o Removed features:
18757 - Tor no longer supports copies of OpenSSL that are missing support
18758 for Elliptic Curve Cryptography. (We began using ECC when
18759 available in 0.2.4.8-alpha, for more safe and efficient key
18760 negotiation.) In particular, support for at least one of P256 or
18761 P224 is now required, with manual configuration needed if only
18762 P224 is available. Resolves ticket 16140.
18763 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
18764 on an operating system that has not upgraded to OpenSSL 1.0 or
18765 later, and you compile Tor from source, you will need to install a
18766 more recent OpenSSL to link Tor against.) These versions of
18767 OpenSSL are still supported by the OpenSSL, but the numerous
18768 cryptographic improvements in later OpenSSL releases makes them a
18769 clear choice. Resolves ticket 16034.
18770 - Remove the HidServDirectoryV2 option. Now all relays offer to
18771 store hidden service descriptors. Related to 16543.
18772 - Remove the VoteOnHidServDirectoriesV2 option, since all
18773 authorities have long set it to 1. Closes ticket 16543.
18776 - Document use of coverity, clang static analyzer, and clang dynamic
18777 undefined behavior and address sanitizers in doc/HACKING. Include
18778 detailed usage instructions in the blacklist. Patch by "teor".
18779 Closes ticket 15817.
18780 - The link authentication protocol code now has extensive tests.
18781 - The relay descriptor signature testing code now has
18783 - The test_workqueue program now runs faster, and is enabled by
18784 default as a part of "make check".
18785 - Now that OpenSSL has its own scrypt implementation, add an unit
18786 test that checks for interoperability between libscrypt_scrypt()
18787 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
18788 and rely on EVP_PBE_scrypt() whenever possible. Resolves
18792 Changes in version 0.2.6.10 - 2015-07-12
18793 Tor version 0.2.6.10 fixes some significant stability and hidden
18794 service client bugs, bulletproofs the cryptography init process, and
18795 fixes a bug when using the sandbox code with some older versions of
18796 Linux. Everyone running an older version, especially an older version
18797 of 0.2.6, should upgrade.
18799 o Major bugfixes (hidden service clients, stability):
18800 - Stop refusing to store updated hidden service descriptors on a
18801 client. This reverts commit 9407040c59218 (which indeed fixed bug
18802 14219, but introduced a major hidden service reachability
18803 regression detailed in bug 16381). This is a temporary fix since
18804 we can live with the minor issue in bug 14219 (it just results in
18805 some load on the network) but the regression of 16381 is too much
18806 of a setback. First-round fix for bug 16381; bugfix
18809 o Major bugfixes (stability):
18810 - Stop crashing with an assertion failure when parsing certain kinds
18811 of malformed or truncated microdescriptors. Fixes bug 16400;
18812 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
18813 by "cypherpunks_backup".
18814 - Stop random client-side assertion failures that could occur when
18815 connecting to a busy hidden service, or connecting to a hidden
18816 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
18819 o Minor features (geoip):
18820 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
18821 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
18823 o Minor bugfixes (crypto error-handling):
18824 - Check for failures from crypto_early_init, and refuse to continue.
18825 A previous typo meant that we could keep going with an
18826 uninitialized crypto library, and would have OpenSSL initialize
18827 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
18828 when implementing ticket 4900. Patch by "teor".
18830 o Minor bugfixes (Linux seccomp2 sandbox):
18831 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
18832 these when eventfd2() support is missing. Fixes bug 16363; bugfix
18833 on 0.2.6.3-alpha. Patch from "teor".
18836 Changes in version 0.2.6.9 - 2015-06-11
18837 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
18838 requirements for receiving an HSDir flag, and addresses some other small
18839 bugs in the systemd and sandbox code. Clients using circuit isolation
18840 should upgrade; all directory authorities should upgrade.
18842 o Major bugfixes (client-side privacy):
18843 - Properly separate out each SOCKSPort when applying stream
18844 isolation. The error occurred because each port's session group was
18845 being overwritten by a default value when the listener connection
18846 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
18849 o Minor feature (directory authorities, security):
18850 - The HSDir flag given by authorities now requires the Stable flag.
18851 For the current network, this results in going from 2887 to 2806
18852 HSDirs. Also, it makes it harder for an attacker to launch a sybil
18853 attack by raising the effort for a relay to become Stable which
18854 takes at the very least 7 days to do so and by keeping the 96
18855 hours uptime requirement for HSDir. Implements ticket 8243.
18857 o Minor bugfixes (compilation):
18858 - Build with --enable-systemd correctly when libsystemd is
18859 installed, but systemd is not. Fixes bug 16164; bugfix on
18860 0.2.6.3-alpha. Patch from Peter Palfrader.
18862 o Minor bugfixes (Linux seccomp2 sandbox):
18863 - Fix sandboxing to work when running as a relaymby renaming of
18864 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
18865 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
18866 - Allow systemd connections to work with the Linux seccomp2 sandbox
18867 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
18870 o Minor bugfixes (tests):
18871 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
18872 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
18875 Changes in version 0.2.6.8 - 2015-05-21
18876 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
18877 fixes an authority-side bug in assigning the HSDir flag. All directory
18878 authorities should upgrade.
18880 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
18881 - Revert commit that made directory authorities assign the HSDir
18882 flag to relays without a DirPort; this was bad because such relays
18883 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
18886 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
18887 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
18888 a client authorized hidden service. Fixes bug 15823; bugfix
18891 o Minor features (geoip):
18892 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
18893 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
18897 Changes in version 0.2.7.1-alpha - 2015-05-12
18898 Tor 0.2.7.1-alpha is the first alpha release in its series. It
18899 includes numerous small features and bugfixes against previous Tor
18900 versions, and numerous small infrastructure improvements. The most
18901 notable features are several new ways for controllers to interact with
18902 the hidden services subsystem.
18904 o New system requirements:
18905 - Tor no longer includes workarounds to support Libevent versions
18906 before 1.3e. Libevent 2.0 or later is recommended. Closes
18909 o Major features (controller):
18910 - Add the ADD_ONION and DEL_ONION commands that allow the creation
18911 and management of hidden services via the controller. Closes
18913 - New "GETINFO onions/current" and "GETINFO onions/detached"
18914 commands to get information about hidden services created via the
18915 controller. Part of ticket 6411.
18916 - New HSFETCH command to launch a request for a hidden service
18917 descriptor. Closes ticket 14847.
18918 - New HSPOST command to upload a hidden service descriptor. Closes
18919 ticket 3523. Patch by "DonnchaC".
18921 o Major bugfixes (hidden services):
18922 - Revert commit that made directory authorities assign the HSDir
18923 flag to relays without a DirPort; this was bad because such relays
18924 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
18927 o Minor features (clock-jump tolerance):
18928 - Recover better when our clock jumps back many hours, like might
18929 happen for Tails or Whonix users who start with a very wrong
18930 hardware clock, use Tor to discover a more accurate time, and then
18931 fix their clock. Resolves part of ticket 8766.
18933 o Minor features (command-line interface):
18934 - Make --hash-password imply --hush to prevent unnecessary noise.
18935 Closes ticket 15542. Patch from "cypherpunks".
18936 - Print a warning whenever we find a relative file path being used
18937 as torrc option. Resolves issue 14018.
18939 o Minor features (controller):
18940 - Add DirAuthority lines for default directory authorities to the
18941 output of the "GETINFO config/defaults" command if not already
18942 present. Implements ticket 14840.
18943 - Controllers can now use "GETINFO hs/client/desc/id/..." to
18944 retrieve items from the client's hidden service descriptor cache.
18945 Closes ticket 14845.
18946 - Implement a new controller command "GETINFO status/fresh-relay-
18947 descs" to fetch a descriptor/extrainfo pair that was generated on
18948 demand just for the controller's use. Implements ticket 14784.
18950 o Minor features (DoS-resistance):
18951 - Make it harder for attackers to overload hidden services with
18952 introductions, by blocking multiple introduction requests on the
18953 same circuit. Resolves ticket 15515.
18955 o Minor features (geoip):
18956 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
18957 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
18960 o Minor features (HS popularity countermeasure):
18961 - To avoid leaking HS popularity, don't cycle the introduction point
18962 when we've handled a fixed number of INTRODUCE2 cells but instead
18963 cycle it when a random number of introductions is reached, thus
18964 making it more difficult for an attacker to find out the amount of
18965 clients that have used the introduction point for a specific HS.
18966 Closes ticket 15745.
18968 o Minor features (logging):
18969 - Include the Tor version in all LD_BUG log messages, since people
18970 tend to cut and paste those into the bugtracker. Implements
18973 o Minor features (pluggable transports):
18974 - When launching managed pluggable transports on Linux systems,
18975 attempt to have the kernel deliver a SIGTERM on tor exit if the
18976 pluggable transport process is still running. Resolves
18978 - When launching managed pluggable transports, setup a valid open
18979 stdin in the child process that can be used to detect if tor has
18980 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
18981 can be used by implementations to detect this new behavior.
18982 Resolves ticket 15435.
18984 o Minor features (testing):
18985 - Add a test to verify that the compiler does not eliminate our
18986 memwipe() implementation. Closes ticket 15377.
18987 - Add make rule `check-changes` to verify the format of changes
18988 files. Closes ticket 15180.
18989 - Add unit tests for control_event_is_interesting(). Add a compile-
18990 time check that the number of events doesn't exceed the capacity
18991 of control_event_t.event_mask. Closes ticket 15431, checks for
18992 bugs similar to 13085. Patch by "teor".
18993 - Command-line argument tests moved to Stem. Resolves ticket 14806.
18994 - Integrate the ntor, backtrace, and zero-length keys tests into the
18995 automake test suite. Closes ticket 15344.
18996 - Remove assertions during builds to determine Tor's test coverage.
18997 We don't want to trigger these even in assertions, so including
18998 them artificially makes our branch coverage look worse than it is.
18999 This patch provides the new test-stem-full and coverage-html-full
19000 configure options. Implements ticket 15400.
19002 o Minor bugfixes (build):
19003 - Improve out-of-tree builds by making non-standard rules work and
19004 clean up additional files and directories. Fixes bug 15053; bugfix
19007 o Minor bugfixes (command-line interface):
19008 - When "--quiet" is provided along with "--validate-config", do not
19009 write anything to stdout on success. Fixes bug 14994; bugfix
19011 - When complaining about bad arguments to "--dump-config", use
19012 stderr, not stdout.
19014 o Minor bugfixes (configuration, unit tests):
19015 - Only add the default fallback directories when the DirAuthorities,
19016 AlternateDirAuthority, and FallbackDir directory config options
19017 are set to their defaults. The default fallback directory list is
19018 currently empty, this fix will only change tor's behavior when it
19019 has default fallback directories. Includes unit tests for
19020 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
19021 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
19023 o Minor bugfixes (correctness):
19024 - For correctness, avoid modifying a constant string in
19025 handle_control_postdescriptor. Fixes bug 15546; bugfix
19027 - Remove side-effects from tor_assert() calls. This was harmless,
19028 because we never disable assertions, but it is bad style and
19029 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
19032 o Minor bugfixes (hidden service):
19033 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
19034 a client authorized hidden service. Fixes bug 15823; bugfix
19036 - Remove an extraneous newline character from the end of hidden
19037 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
19039 o Minor bugfixes (interface):
19040 - Print usage information for --dump-config when it is used without
19041 an argument. Also, fix the error message to use different wording
19042 and add newline at the end. Fixes bug 15541; bugfix
19045 o Minor bugfixes (logs):
19046 - When building Tor under Clang, do not include an extra set of
19047 parentheses in log messages that include function names. Fixes bug
19048 15269; bugfix on every released version of Tor when compiled with
19049 recent enough Clang.
19051 o Minor bugfixes (network):
19052 - When attempting to use fallback technique for network interface
19053 lookup, disregard loopback and multicast addresses since they are
19054 unsuitable for public communications.
19056 o Minor bugfixes (statistics):
19057 - Disregard the ConnDirectionStatistics torrc options when Tor is
19058 not a relay since in that mode of operation no sensible data is
19059 being collected and because Tor might run into measurement hiccups
19060 when running as a client for some time, then becoming a relay.
19061 Fixes bug 15604; bugfix on 0.2.2.35.
19063 o Minor bugfixes (test networks):
19064 - When self-testing reachability, use ExtendAllowPrivateAddresses to
19065 determine if local/private addresses imply reachability. The
19066 previous fix used TestingTorNetwork, which implies
19067 ExtendAllowPrivateAddresses, but this excluded rare configurations
19068 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
19069 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
19070 issue discovered by CJ Ess.
19072 o Minor bugfixes (testing):
19073 - Check for matching value in server response in ntor_ref.py. Fixes
19074 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
19076 - Set the severity correctly when testing
19077 get_interface_addresses_ifaddrs() and
19078 get_interface_addresses_win32(), so that the tests fail gracefully
19079 instead of triggering an assertion. Fixes bug 15759; bugfix on
19080 0.2.6.3-alpha. Reported by Nicolas Derive.
19082 o Code simplification and refactoring:
19083 - Move the hacky fallback code out of get_interface_address6() into
19084 separate function and get it covered with unit-tests. Resolves
19086 - Refactor hidden service client-side cache lookup to intelligently
19087 report its various failure cases, and disentangle failure cases
19088 involving a lack of introduction points. Closes ticket 14391.
19089 - Use our own Base64 encoder instead of OpenSSL's, to allow more
19090 control over the output. Part of ticket 15652.
19093 - Improve the descriptions of statistics-related torrc options in
19094 the manpage to describe rationale and possible uses cases. Fixes
19096 - Improve the layout and formatting of ./configure --help messages.
19097 Closes ticket 15024. Patch from "cypherpunks".
19098 - Standardize on the term "server descriptor" in the manual page.
19099 Previously, we had used "router descriptor", "server descriptor",
19100 and "relay descriptor" interchangeably. Part of ticket 14987.
19103 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
19104 and always use the internal Base64 decoder. The internal decoder
19105 has been part of tor since 0.2.0.10-alpha, and no one should
19106 be using the OpenSSL one. Part of ticket 15652.
19107 - Remove the 'tor_strclear()' function; use memwipe() instead.
19108 Closes ticket 14922.
19110 o Removed features:
19111 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
19112 fingerprinting we now recommend pluggable transports; for forward-
19113 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
19114 - Remove the undocumented "--digests" command-line option. It
19115 complicated our build process, caused subtle build issues on
19116 multiple platforms, and is now redundant since we started
19117 including git version identifiers. Closes ticket 14742.
19118 - Tor no longer contains checks for ancient directory cache versions
19119 that didn't know about microdescriptors.
19120 - Tor no longer contains workarounds for stat files generated by
19121 super-old versions of Tor that didn't choose guards sensibly.
19124 Changes in version 0.2.4.27 - 2015-04-06
19125 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
19126 could be used by an attacker to crash hidden services, or crash clients
19127 visiting hidden services. Hidden services should upgrade as soon as
19128 possible; clients should upgrade whenever packages become available.
19130 This release also backports a simple improvement to make hidden
19131 services a bit less vulnerable to denial-of-service attacks.
19133 o Major bugfixes (security, hidden service):
19134 - Fix an issue that would allow a malicious client to trigger an
19135 assertion failure and halt a hidden service. Fixes bug 15600;
19136 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
19137 - Fix a bug that could cause a client to crash with an assertion
19138 failure when parsing a malformed hidden service descriptor. Fixes
19139 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
19141 o Minor features (DoS-resistance, hidden service):
19142 - Introduction points no longer allow multiple INTRODUCE1 cells to
19143 arrive on the same circuit. This should make it more expensive for
19144 attackers to overwhelm hidden services with introductions.
19145 Resolves ticket 15515.
19148 Changes in version 0.2.5.12 - 2015-04-06
19149 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
19150 could be used by an attacker to crash hidden services, or crash clients
19151 visiting hidden services. Hidden services should upgrade as soon as
19152 possible; clients should upgrade whenever packages become available.
19154 This release also backports a simple improvement to make hidden
19155 services a bit less vulnerable to denial-of-service attacks.
19157 o Major bugfixes (security, hidden service):
19158 - Fix an issue that would allow a malicious client to trigger an
19159 assertion failure and halt a hidden service. Fixes bug 15600;
19160 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
19161 - Fix a bug that could cause a client to crash with an assertion
19162 failure when parsing a malformed hidden service descriptor. Fixes
19163 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
19165 o Minor features (DoS-resistance, hidden service):
19166 - Introduction points no longer allow multiple INTRODUCE1 cells to
19167 arrive on the same circuit. This should make it more expensive for
19168 attackers to overwhelm hidden services with introductions.
19169 Resolves ticket 15515.
19172 Changes in version 0.2.6.7 - 2015-04-06
19173 Tor 0.2.6.7 fixes two security issues that could be used by an
19174 attacker to crash hidden services, or crash clients visiting hidden
19175 services. Hidden services should upgrade as soon as possible; clients
19176 should upgrade whenever packages become available.
19178 This release also contains two simple improvements to make hidden
19179 services a bit less vulnerable to denial-of-service attacks.
19181 o Major bugfixes (security, hidden service):
19182 - Fix an issue that would allow a malicious client to trigger an
19183 assertion failure and halt a hidden service. Fixes bug 15600;
19184 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
19185 - Fix a bug that could cause a client to crash with an assertion
19186 failure when parsing a malformed hidden service descriptor. Fixes
19187 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
19189 o Minor features (DoS-resistance, hidden service):
19190 - Introduction points no longer allow multiple INTRODUCE1 cells to
19191 arrive on the same circuit. This should make it more expensive for
19192 attackers to overwhelm hidden services with introductions.
19193 Resolves ticket 15515.
19194 - Decrease the amount of reattempts that a hidden service performs
19195 when its rendezvous circuits fail. This reduces the computational
19196 cost for running a hidden service under heavy load. Resolves
19200 Changes in version 0.2.6.6 - 2015-03-24
19201 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
19203 It adds numerous safety, security, correctness, and performance
19204 improvements. Client programs can be configured to use more kinds of
19205 sockets, AutomapHosts works better, the multithreading backend is
19206 improved, cell transmission is refactored, test coverage is much
19207 higher, more denial-of-service attacks are handled, guard selection is
19208 improved to handle long-term guards better, pluggable transports
19209 should work a bit better, and some annoying hidden service performance
19210 bugs should be addressed.
19212 o Minor bugfixes (portability):
19213 - Use the correct datatype in the SipHash-2-4 function to prevent
19214 compilers from assuming any sort of alignment. Fixes bug 15436;
19215 bugfix on 0.2.5.3-alpha.
19217 Changes in version 0.2.6.5-rc - 2015-03-18
19218 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
19219 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
19221 o Major bugfixes (client):
19222 - Avoid crashing when making certain configuration option changes on
19223 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
19226 o Major bugfixes (pluggable transports):
19227 - Initialize the extended OR Port authentication cookie before
19228 launching pluggable transports. This prevents a race condition
19229 that occurred when server-side pluggable transports would cache the
19230 authentication cookie before it has been (re)generated. Fixes bug
19231 15240; bugfix on 0.2.5.1-alpha.
19233 o Major bugfixes (portability):
19234 - Do not crash on startup when running on Solaris. Fixes a bug
19235 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
19238 o Minor features (heartbeat):
19239 - On relays, report how many connections we negotiated using each
19240 version of the Tor link protocols. This information will let us
19241 know if removing support for very old versions of the Tor
19242 protocols is harming the network. Closes ticket 15212.
19244 o Code simplification and refactoring:
19245 - Refactor main loop to extract the 'loop' part. This makes it
19246 easier to run Tor under Shadow. Closes ticket 15176.
19249 Changes in version 0.2.5.11 - 2015-03-17
19250 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
19252 It backports several bugfixes from the 0.2.6 branch, including a
19253 couple of medium-level security fixes for relays and exit nodes.
19254 It also updates the list of directory authorities.
19256 o Directory authority changes:
19257 - Remove turtles as a directory authority.
19258 - Add longclaw as a new (v3) directory authority. This implements
19259 ticket 13296. This keeps the directory authority count at 9.
19260 - The directory authority Faravahar has a new IP address. This
19261 closes ticket 14487.
19263 o Major bugfixes (crash, OSX, security):
19264 - Fix a remote denial-of-service opportunity caused by a bug in
19265 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
19268 o Major bugfixes (relay, stability, possible security):
19269 - Fix a bug that could lead to a relay crashing with an assertion
19270 failure if a buffer of exactly the wrong layout was passed to
19271 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
19272 0.2.0.10-alpha. Patch from 'cypherpunks'.
19273 - Do not assert if the 'data' pointer on a buffer is advanced to the
19274 very end of the buffer; log a BUG message instead. Only assert if
19275 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
19277 o Major bugfixes (exit node stability):
19278 - Fix an assertion failure that could occur under high DNS load.
19279 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
19280 diagnosed and fixed by "cypherpunks".
19282 o Major bugfixes (Linux seccomp2 sandbox):
19283 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
19284 crash during attempts to call wait4. Fixes bug 15088; bugfix on
19285 0.2.5.1-alpha. Patch from "sanic".
19287 o Minor features (controller):
19288 - New "GETINFO bw-event-cache" to get information about recent
19289 bandwidth events. Closes ticket 14128. Useful for controllers to
19290 get recent bandwidth history after the fix for ticket 13988.
19292 o Minor features (geoip):
19293 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
19294 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
19297 o Minor bugfixes (client, automapping):
19298 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
19299 no value follows the option. Fixes bug 14142; bugfix on
19300 0.2.4.7-alpha. Patch by "teor".
19301 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
19302 14195; bugfix on 0.1.0.1-rc.
19304 o Minor bugfixes (compilation):
19305 - Build without warnings with the stock OpenSSL srtp.h header, which
19306 has a duplicate declaration of SSL_get_selected_srtp_profile().
19307 Fixes bug 14220; this is OpenSSL's bug, not ours.
19309 o Minor bugfixes (directory authority):
19310 - Allow directory authorities to fetch more data from one another if
19311 they find themselves missing lots of votes. Previously, they had
19312 been bumping against the 10 MB queued data limit. Fixes bug 14261;
19313 bugfix on 0.1.2.5-alpha.
19314 - Enlarge the buffer to read bwauth generated files to avoid an
19315 issue when parsing the file in dirserv_read_measured_bandwidths().
19316 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
19318 o Minor bugfixes (statistics):
19319 - Increase period over which bandwidth observations are aggregated
19320 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
19322 o Minor bugfixes (preventative security, C safety):
19323 - When reading a hexadecimal, base-32, or base-64 encoded value from
19324 a string, always overwrite the whole output buffer. This prevents
19325 some bugs where we would look at (but fortunately, not reveal)
19326 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
19330 Changes in version 0.2.4.26 - 2015-03-17
19331 Tor 0.2.4.26 includes an updated list of directory authorities. It
19332 also backports a couple of stability and security bugfixes from 0.2.5
19335 o Directory authority changes:
19336 - Remove turtles as a directory authority.
19337 - Add longclaw as a new (v3) directory authority. This implements
19338 ticket 13296. This keeps the directory authority count at 9.
19339 - The directory authority Faravahar has a new IP address. This
19340 closes ticket 14487.
19342 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
19343 - Fix an assertion failure that could occur under high DNS load.
19344 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
19345 diagnosed and fixed by "cypherpunks".
19347 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
19348 - Fix a bug that could lead to a relay crashing with an assertion
19349 failure if a buffer of exactly the wrong layout was passed to
19350 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
19351 0.2.0.10-alpha. Patch from 'cypherpunks'.
19352 - Do not assert if the 'data' pointer on a buffer is advanced to the
19353 very end of the buffer; log a BUG message instead. Only assert if
19354 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
19356 o Minor features (geoip):
19357 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
19358 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
19361 Changes in version 0.2.6.4-rc - 2015-03-09
19362 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
19363 attacker might be able to use in order to crash certain Tor
19364 directories. It also resolves some minor issues left over from, or
19365 introduced in, Tor 0.2.6.3-alpha or earlier.
19367 o Major bugfixes (crash, OSX, security):
19368 - Fix a remote denial-of-service opportunity caused by a bug in
19369 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
19372 o Major bugfixes (relay, stability, possible security):
19373 - Fix a bug that could lead to a relay crashing with an assertion
19374 failure if a buffer of exactly the wrong layout is passed to
19375 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
19376 0.2.0.10-alpha. Patch from "cypherpunks".
19377 - Do not assert if the 'data' pointer on a buffer is advanced to the
19378 very end of the buffer; log a BUG message instead. Only assert if
19379 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
19381 o Major bugfixes (FreeBSD IPFW transparent proxy):
19382 - Fix address detection with FreeBSD transparent proxies, when
19383 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
19386 o Major bugfixes (Linux seccomp2 sandbox):
19387 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
19388 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
19390 - Allow AF_UNIX hidden services to be used with the seccomp2
19391 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
19392 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
19393 crash during attempts to call wait4. Fixes bug 15088; bugfix on
19394 0.2.5.1-alpha. Patch from "sanic".
19396 o Minor features (controller):
19397 - Messages about problems in the bootstrap process now include
19398 information about the server we were trying to connect to when we
19399 noticed the problem. Closes ticket 15006.
19401 o Minor features (geoip):
19402 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
19403 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
19406 o Minor features (logs):
19407 - Quiet some log messages in the heartbeat and at startup. Closes
19410 o Minor bugfixes (certificate handling):
19411 - If an authority operator accidentally makes a signing certificate
19412 with a future publication time, do not discard its real signing
19413 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
19414 - Remove any old authority certificates that have been superseded
19415 for at least two days. Previously, we would keep superseded
19416 certificates until they expired, if they were published close in
19417 time to the certificate that superseded them. Fixes bug 11454;
19418 bugfix on 0.2.1.8-alpha.
19420 o Minor bugfixes (compilation):
19421 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
19423 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
19426 o Minor bugfixes (testing):
19427 - Fix endianness issues in unit test for resolve_my_address() to
19428 have it pass on big endian systems. Fixes bug 14980; bugfix on
19430 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
19431 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
19432 - When running the new 'make test-stem' target, use the configured
19433 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
19434 from "cypherpunks".
19435 - When running the zero-length-keys tests, do not use the default
19436 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
19439 o Directory authority IP change:
19440 - The directory authority Faravahar has a new IP address. This
19441 closes ticket 14487.
19444 - Remove some lingering dead code that once supported mempools.
19445 Mempools were disabled by default in 0.2.5, and removed entirely
19446 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
19450 Changes in version 0.2.6.3-alpha - 2015-02-19
19451 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
19452 the 0.2.6.x series. It introduces support for more kinds of sockets,
19453 makes it harder to accidentally run an exit, improves our
19454 multithreading backend, incorporates several fixes for the
19455 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
19457 If no major regressions or security holes are found in this version,
19458 the next version will be a release candidate.
19460 o Deprecated versions:
19461 - Tor relays older than 0.2.4.18-rc are no longer allowed to
19462 advertise themselves on the network. Closes ticket 13555.
19464 o Major features (security, unix domain sockets):
19465 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
19466 applications can reach Tor without having to create AF_INET or
19467 AF_INET6 sockets, meaning they can completely disable their
19468 ability to make non-Tor network connections. To create a socket of
19469 this type, use "SocksPort unix:/path/to/socket". Implements
19471 - Support mapping hidden service virtual ports to AF_UNIX sockets.
19472 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
19473 Implements ticket 11485.
19475 o Major features (changed defaults):
19476 - Prevent relay operators from unintentionally running exits: When a
19477 relay is configured as an exit node, we now warn the user unless
19478 the "ExitRelay" option is set to 1. We warn even more loudly if
19479 the relay is configured with the default exit policy, since this
19480 can indicate accidental misconfiguration. Setting "ExitRelay 0"
19481 stops Tor from running as an exit relay. Closes ticket 10067.
19483 o Major features (directory system):
19484 - When downloading server- or microdescriptors from a directory
19485 server, we no longer launch multiple simultaneous requests to the
19486 same server. This reduces load on the directory servers,
19487 especially when directory guards are in use. Closes ticket 9969.
19488 - When downloading server- or microdescriptors over a tunneled
19489 connection, do not limit the length of our requests to what the
19490 Squid proxy is willing to handle. Part of ticket 9969.
19491 - Authorities can now vote on the correct digests and latest
19492 versions for different software packages. This allows packages
19493 that include Tor to use the Tor authority system as a way to get
19494 notified of updates and their correct digests. Implements proposal
19495 227. Closes ticket 10395.
19497 o Major features (guards):
19498 - Introduce the Guardfraction feature to improves load balancing on
19499 guard nodes. Specifically, it aims to reduce the traffic gap that
19500 guard nodes experience when they first get the Guard flag. This is
19501 a required step if we want to increase the guard lifetime to 9
19502 months or greater. Closes ticket 9321.
19504 o Major features (performance):
19505 - Make the CPU worker implementation more efficient by avoiding the
19506 kernel and lengthening pipelines. The original implementation used
19507 sockets to transfer data from the main thread to the workers, and
19508 didn't allow any thread to be assigned more than a single piece of
19509 work at once. The new implementation avoids communications
19510 overhead by making requests in shared memory, avoiding kernel IO
19511 where possible, and keeping more requests in flight at once.
19512 Implements ticket 9682.
19514 o Major features (relay):
19515 - Raise the minimum acceptable configured bandwidth rate for bridges
19516 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
19517 20 KiB/sec.) Closes ticket 13822.
19519 o Major bugfixes (exit node stability):
19520 - Fix an assertion failure that could occur under high DNS load.
19521 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
19522 diagnosed and fixed by "cypherpunks".
19524 o Major bugfixes (mixed relay-client operation):
19525 - When running as a relay and client at the same time (not
19526 recommended), if we decide not to use a new guard because we want
19527 to retry older guards, only close the locally-originating circuits
19528 passing through that guard. Previously we would close all the
19529 circuits through that guard. Fixes bug 9819; bugfix on
19530 0.2.1.1-alpha. Reported by "skruffy".
19532 o Minor features (build):
19533 - New --disable-system-torrc compile-time option to prevent Tor from
19534 looking for the system-wide torrc or torrc-defaults files.
19535 Resolves ticket 13037.
19537 o Minor features (controller):
19538 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
19539 events so controllers can observe circuit isolation inputs. Closes
19541 - ControlPort now supports the unix:/path/to/socket syntax as an
19542 alternative to the ControlSocket option, for consistency with
19543 SocksPort and HiddenServicePort. Closes ticket 14451.
19544 - New "GETINFO bw-event-cache" to get information about recent
19545 bandwidth events. Closes ticket 14128. Useful for controllers to
19546 get recent bandwidth history after the fix for ticket 13988.
19548 o Minor features (Denial of service resistance):
19549 - Count the total number of bytes used storing hidden service
19550 descriptors against the value of MaxMemInQueues. If we're low on
19551 memory, and more than 20% of our memory is used holding hidden
19552 service descriptors, free them until no more than 10% of our
19553 memory holds hidden service descriptors. Free the least recently
19554 fetched descriptors first. Resolves ticket 13806.
19555 - When we have recently been under memory pressure (over 3/4 of
19556 MaxMemInQueues is allocated), then allocate smaller zlib objects
19557 for small requests. Closes ticket 11791.
19559 o Minor features (geoip):
19560 - Update geoip and geoip6 files to the January 7 2015 Maxmind
19561 GeoLite2 Country database.
19563 o Minor features (guard nodes):
19564 - Reduce the time delay before saving guard status to disk from 10
19565 minutes to 30 seconds (or from one hour to 10 minutes if
19566 AvoidDiskWrites is set). Closes ticket 12485.
19568 o Minor features (hidden service):
19569 - Make Sybil attacks against hidden services harder by changing the
19570 minimum time required to get the HSDir flag from 25 hours up to 96
19571 hours. Addresses ticket 14149.
19572 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
19573 services to disable the anti-scanning feature introduced in
19574 0.2.6.2-alpha. With this option not set, a connection to an
19575 unlisted port closes the circuit. With this option set, only a
19576 RELAY_DONE cell is sent. Closes ticket 14084.
19578 o Minor features (interface):
19579 - Implement "-f -" command-line option to read torrc configuration
19580 from standard input, if you don't want to store the torrc file in
19581 the file system. Implements feature 13865.
19583 o Minor features (logging):
19584 - Add a count of unique clients to the bridge heartbeat message.
19585 Resolves ticket 6852.
19586 - Suppress "router info incompatible with extra info" message when
19587 reading extrainfo documents from cache. (This message got loud
19588 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
19590 - Elevate hidden service authorized-client message from DEBUG to
19591 INFO. Closes ticket 14015.
19593 o Minor features (stability):
19594 - Add assertions in our hash-table iteration code to check for
19595 corrupted values that could cause infinite loops. Closes
19598 o Minor features (systemd):
19599 - Various improvements and modernizations in systemd hardening
19600 support. Closes ticket 13805. Patch from Craig Andrews.
19602 o Minor features (testing networks):
19603 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
19604 and the default on a testing network to 2 minutes. Drop the
19605 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
19606 keep the default on a testing network at 30 seconds. This reduces
19607 HS bootstrap time to around 25 seconds. Also, change the default
19608 time in test-network.sh to match. Closes ticket 13401. Patch
19610 - Create TestingDirAuthVoteHSDir to correspond to
19611 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
19612 HSDir flag for the listed relays regardless of uptime or ORPort
19613 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
19614 Partial implementation for ticket 14067. Patch by "teor".
19616 o Minor features (tor2web mode):
19617 - Introduce the config option Tor2webRendezvousPoints, which allows
19618 clients in Tor2webMode to select a specific Rendezvous Point to be
19619 used in HS circuits. This might allow better performance for
19620 Tor2Web nodes. Implements ticket 12844.
19622 o Minor bugfixes (client DNS):
19623 - Report the correct cached DNS expiration times on SOCKS port or in
19624 DNS replies. Previously, we would report everything as "never
19625 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
19626 - Avoid a small memory leak when we find a cached answer for a
19627 reverse DNS lookup in a client-side DNS cache. (Remember, client-
19628 side DNS caching is off by default, and is not recommended.) Fixes
19629 bug 14259; bugfix on 0.2.0.1-alpha.
19631 o Minor bugfixes (client, automapping):
19632 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
19633 no value follows the option. Fixes bug 14142; bugfix on
19634 0.2.4.7-alpha. Patch by "teor".
19635 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
19636 14195; bugfix on 0.1.0.1-rc.
19637 - Prevent changes to other options from removing the wildcard value
19638 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
19640 - Allow MapAddress and AutomapHostsOnResolve to work together when
19641 an address is mapped into another address type (like .onion) that
19642 must be automapped at resolve time. Fixes bug 7555; bugfix
19645 o Minor bugfixes (client, bridges):
19646 - When we are using bridges and we had a network connectivity
19647 problem, only retry connecting to our currently configured
19648 bridges, not all bridges we know about and remember using. Fixes
19649 bug 14216; bugfix on 0.2.2.17-alpha.
19651 o Minor bugfixes (client, IPv6):
19652 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
19653 flag is not set; and not because the NoIPv4Traffic flag was set.
19654 Previously we'd looked at the NoIPv4Traffic flag for both types of
19655 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
19657 o Minor bugfixes (compilation):
19658 - The address of an array in the middle of a structure will always
19659 be non-NULL. clang recognises this and complains. Disable the
19660 tautologous and redundant check to silence this warning. Fixes bug
19661 14001; bugfix on 0.2.1.2-alpha.
19662 - Avoid warnings when building with systemd 209 or later. Fixes bug
19663 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
19664 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
19665 Addresses ticket 14188.
19666 - Build without warnings with the stock OpenSSL srtp.h header, which
19667 has a duplicate declaration of SSL_get_selected_srtp_profile().
19668 Fixes bug 14220; this is OpenSSL's bug, not ours.
19669 - Do not compile any code related to Tor2Web mode when Tor2Web mode
19670 is not enabled at compile time. Previously, this code was included
19671 in a disabled state. See discussion on ticket 12844.
19672 - Remove the --disable-threads configure option again. It was
19673 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
19674 14819; bugfix on 0.2.6.2-alpha.
19676 o Minor bugfixes (controller):
19677 - Report "down" in response to the "GETINFO entry-guards" command
19678 when relays are down with an unreachable_since value. Previously,
19679 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
19680 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
19681 14116; bugfix on 0.2.2.9-alpha.
19682 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
19683 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
19685 o Minor bugfixes (directory authority):
19686 - Allow directory authorities to fetch more data from one another if
19687 they find themselves missing lots of votes. Previously, they had
19688 been bumping against the 10 MB queued data limit. Fixes bug 14261;
19689 bugfix on 0.1.2.5-alpha.
19690 - Do not attempt to download extrainfo documents which we will be
19691 unable to validate with a matching server descriptor. Fixes bug
19692 13762; bugfix on 0.2.0.1-alpha.
19693 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
19694 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
19695 - Enlarge the buffer to read bwauth generated files to avoid an
19696 issue when parsing the file in dirserv_read_measured_bandwidths().
19697 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
19699 o Minor bugfixes (file handling):
19700 - Stop failing when key files are zero-length. Instead, generate new
19701 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
19702 on all versions of Tor. Patch by "teor".
19703 - Stop generating a fresh .old RSA onion key file when the .old file
19704 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
19705 - Avoid overwriting .old key files with empty key files.
19706 - Skip loading zero-length extrainfo store, router store, stats,
19707 state, and key files.
19708 - Avoid crashing when trying to reload a torrc specified as a
19709 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
19712 o Minor bugfixes (hidden services):
19713 - Close the introduction circuit when we have no more usable intro
19714 points, instead of waiting for it to time out. This also ensures
19715 that no follow-up HS descriptor fetch is triggered when the
19716 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
19717 - When fetching a hidden service descriptor for a down service that
19718 was recently up, do not keep refetching until we try the same
19719 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
19720 - Successfully launch Tor with a nonexistent hidden service
19721 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
19722 14106; bugfix on 0.2.6.2-alpha.
19724 o Minor bugfixes (logging):
19725 - Avoid crashing when there are more log domains than entries in
19726 domain_list. Bugfix on 0.2.3.1-alpha.
19727 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
19729 - Don't log messages to stdout twice when starting up. Fixes bug
19730 13993; bugfix on 0.2.6.1-alpha.
19732 o Minor bugfixes (parsing):
19733 - Stop accepting milliseconds (or other junk) at the end of
19734 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
19735 - Support two-number and three-number version numbers correctly, in
19736 case we change the Tor versioning system in the future. Fixes bug
19737 13661; bugfix on 0.0.8pre1.
19739 o Minor bugfixes (path counting):
19740 - When deciding whether the consensus lists any exit nodes, count
19741 the number listed in the consensus, not the number we have
19742 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
19743 - When deciding whether we have any exit nodes, only examine
19744 ExitNodes when the ExitNodes option is actually set. Fixes part of
19745 bug 14918; bugfix on 0.2.6.2-alpha.
19746 - Get rid of redundant and possibly scary warnings that we are
19747 missing directory information while we bootstrap. Fixes part of
19748 bug 14918; bugfix on 0.2.6.2-alpha.
19750 o Minor bugfixes (portability):
19751 - Fix the ioctl()-based network interface lookup code so that it
19752 will work on systems that have variable-length struct ifreq, for
19754 - Fix scheduler compilation on targets where char is unsigned. Fixes
19755 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
19757 o Minor bugfixes (sandbox):
19758 - Allow glibc fatal errors to be sent to stderr before Tor exits.
19759 Previously, glibc would try to write them to /dev/tty, and the
19760 sandbox would trap the call and make Tor exit prematurely. Fixes
19761 bug 14759; bugfix on 0.2.5.1-alpha.
19763 o Minor bugfixes (shutdown):
19764 - When shutting down, always call event_del() on lingering read or
19765 write events before freeing them. Otherwise, we risk double-frees
19766 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
19769 o Minor bugfixes (small memory leaks):
19770 - Avoid leaking memory when using IPv6 virtual address mappings.
19771 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
19774 o Minor bugfixes (statistics):
19775 - Increase period over which bandwidth observations are aggregated
19776 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
19778 o Minor bugfixes (systemd support):
19779 - Fix detection and operation of systemd watchdog. Fixes part of bug
19780 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
19781 - Run correctly under systemd with the RunAsDaemon option set. Fixes
19782 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
19783 - Inform the systemd supervisor about more changes in the Tor
19784 process status. Implements part of ticket 14141. Patch from
19786 - Cause the "--disable-systemd" option to actually disable systemd
19787 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
19790 o Minor bugfixes (TLS):
19791 - Check more thoroughly throughout the TLS code for possible
19792 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
19794 o Minor bugfixes (transparent proxy):
19795 - Use getsockname, not getsockopt, to retrieve the address for a
19796 TPROXY-redirected connection. Fixes bug 13796; bugfix
19799 o Code simplification and refactoring:
19800 - Move fields related to isolating and configuring client ports into
19801 a shared structure. Previously, they were duplicated across
19802 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
19803 to copy them correctly had been the cause of at least one bug in
19804 the past. Closes ticket 8546.
19805 - Refactor the get_interface_addresses_raw() doom-function into
19806 multiple smaller and simpler subfunctions. Cover the resulting
19807 subfunctions with unit-tests. Fixes a significant portion of
19809 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
19810 only for version <= 0.2.2.24 which is now deprecated. Closes
19812 - Remove a test for a long-defunct broken version-one
19816 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
19817 for writing the OpenBSD-specific tips. Resolves ticket 13702.
19818 - Make the tor-resolve documentation match its help string and its
19819 options. Resolves part of ticket 14325.
19820 - Log a more useful error message from tor-resolve when failing to
19821 look up a hidden service address. Resolves part of ticket 14325.
19823 o Downgraded warnings:
19824 - Don't warn when we've attempted to contact a relay using the wrong
19825 ntor onion key. Closes ticket 9635.
19827 o Removed features:
19828 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
19829 longer silently accepted as an alias for "ExitNodes".
19830 - The --enable-mempool and --enable-buf-freelists options, which
19831 were originally created to work around bad malloc implementations,
19832 no longer exist. They were off-by-default in 0.2.5. Closes
19836 - Make the checkdir/perms test complete successfully even if the
19837 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
19838 - Test that tor does not fail when key files are zero-length. Check
19839 that tor generates new keys, and overwrites the empty key files.
19840 - Test that tor generates new keys when keys are missing
19841 (existing behavior).
19842 - Test that tor does not overwrite key files that already contain
19843 data (existing behavior). Tests bug 13111. Patch by "teor".
19844 - New "make test-stem" target to run stem integration tests.
19845 Requires that the "STEM_SOURCE_DIR" environment variable be set.
19846 Closes ticket 14107.
19847 - Make the test_cmdline_args.py script work correctly on Windows.
19848 Patch from Gisle Vanem.
19849 - Move the slower unit tests into a new "./src/test/test-slow"
19850 binary that can be run independently of the other tests. Closes
19852 - Avoid undefined behavior when sampling huge values from the
19853 Laplace distribution. This made unittests fail on Raspberry Pi.
19854 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
19857 Changes in version 0.2.6.2-alpha - 2014-12-31
19858 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
19859 It introduces a major new backend for deciding when to send cells on
19860 channels, which should lead down the road to big performance
19861 increases. It contains security and statistics features for better
19862 work on hidden services, and numerous bugfixes.
19864 This release contains many new unit tests, along with major
19865 performance improvements for running testing networks using Chutney.
19866 Thanks to a series of patches contributed by "teor", testing networks
19867 should now bootstrap in seconds, rather than minutes.
19869 o Major features (relay, infrastructure):
19870 - Complete revision of the code that relays use to decide which cell
19871 to send next. Formerly, we selected the best circuit to write on
19872 each channel, but we didn't select among channels in any
19873 sophisticated way. Now, we choose the best circuits globally from
19874 among those whose channels are ready to deliver traffic.
19876 This patch implements a new inter-cmux comparison API, a global
19877 high/low watermark mechanism and a global scheduler loop for
19878 transmission prioritization across all channels as well as among
19879 circuits on one channel. This schedule is currently tuned to
19880 (tolerantly) avoid making changes in network performance, but it
19881 should form the basis for major circuit performance increases in
19882 the future. Code by Andrea; tuning by Rob Jansen; implements
19885 o Major features (hidden services):
19886 - Make HS port scanning more difficult by immediately closing the
19887 circuit when a user attempts to connect to a nonexistent port.
19888 Closes ticket 13667.
19889 - Add a HiddenServiceStatistics option that allows Tor relays to
19890 gather and publish statistics about the overall size and volume of
19891 hidden service usage. Specifically, when this option is turned on,
19892 an HSDir will publish an approximate number of hidden services
19893 that have published descriptors to it the past 24 hours. Also, if
19894 a relay has acted as a hidden service rendezvous point, it will
19895 publish the approximate amount of rendezvous cells it has relayed
19896 the past 24 hours. The statistics themselves are obfuscated so
19897 that the exact values cannot be derived. For more details see
19898 proposal 238, "Better hidden service stats from Tor relays". This
19899 feature is currently disabled by default. Implements feature 13192.
19901 o Major bugfixes (client, automap):
19902 - Repair automapping with IPv6 addresses. This automapping should
19903 have worked previously, but one piece of debugging code that we
19904 inserted to detect a regression actually caused the regression to
19905 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
19906 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
19909 o Major bugfixes (hidden services):
19910 - When closing an introduction circuit that was opened in parallel
19911 with others, don't mark the introduction point as unreachable.
19912 Previously, the first successful connection to an introduction
19913 point would make the other introduction points get marked as
19914 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
19916 o Directory authority changes:
19917 - Remove turtles as a directory authority.
19918 - Add longclaw as a new (v3) directory authority. This implements
19919 ticket 13296. This keeps the directory authority count at 9.
19921 o Major removed features:
19922 - Tor clients no longer support connecting to hidden services
19923 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
19924 option has been removed. (There shouldn't be any hidden services
19925 running these versions on the network.) Closes ticket 7803.
19927 o Minor features (client):
19928 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
19929 is enabled, reject requests with IP addresses as hostnames.
19930 Resolves ticket 13315.
19932 o Minor features (controller):
19933 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
19934 write an unscheduled heartbeat message to the log. Implements
19937 o Minor features (geoip):
19938 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
19941 o Minor features (hidden services):
19942 - When re-enabling the network, don't try to build introduction
19943 circuits until we have successfully built a circuit. This makes
19944 hidden services come up faster when the network is re-enabled.
19945 Patch from "akwizgran". Closes ticket 13447.
19946 - When we fail to retrieve a hidden service descriptor, send the
19947 controller an "HS_DESC FAILED" controller event. Implements
19949 - New HiddenServiceDirGroupReadable option to cause hidden service
19950 directories and hostname files to be created group-readable. Patch
19951 from "anon", David Stainton, and "meejah". Closes ticket 11291.
19953 o Minor features (systemd):
19954 - Where supported, when running with systemd, report successful
19955 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
19956 - When running with systemd, support systemd watchdog messages. Part
19957 of ticket 11016. Patch by Michael Scherer.
19959 o Minor features (transparent proxy):
19960 - Update the transparent proxy option checks to allow for both ipfw
19961 and pf on OS X. Closes ticket 14002.
19962 - Use the correct option when using IPv6 with transparent proxy
19963 support on Linux. Resolves 13808. Patch by Francisco Blas
19966 o Minor bugfixes (preventative security, C safety):
19967 - When reading a hexadecimal, base-32, or base-64 encoded value from
19968 a string, always overwrite the whole output buffer. This prevents
19969 some bugs where we would look at (but fortunately, not reveal)
19970 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
19972 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
19973 just the part that's used. This makes it harder for data leak bugs
19974 to occur in the event of other programming failures. Resolves
19977 o Minor bugfixes (client, microdescriptors):
19978 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
19979 computing which microdescriptors to download. This keeps us from
19980 erroneous download behavior if two microdescriptor digests ever
19981 have the same first 160 bits. Fixes part of bug 13399; bugfix
19983 - Reset a router's status if its microdescriptor digest changes,
19984 even if the first 160 bits remain the same. Fixes part of bug
19985 13399; bugfix on 0.2.3.1-alpha.
19987 o Minor bugfixes (compilation):
19988 - Silence clang warnings under --enable-expensive-hardening,
19989 including implicit truncation of 64 bit values to 32 bit, const
19990 char assignment to self, tautological compare, and additional
19991 parentheses around equality tests. Fixes bug 13577; bugfix
19993 - Fix a clang warning about checking whether an address in the
19994 middle of a structure is NULL. Fixes bug 14001; bugfix
19997 o Minor bugfixes (hidden services):
19998 - Correctly send a controller event when we find that a rendezvous
19999 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
20000 - Pre-check directory permissions for new hidden-services to avoid
20001 at least one case of "Bug: Acting on config options left us in a
20002 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
20003 - When adding a new hidden service (for example, via SETCONF), Tor
20004 no longer congratulates the user for running a relay. Fixes bug
20005 13941; bugfix on 0.2.6.1-alpha.
20006 - When fetching hidden service descriptors, we now check not only
20007 for whether we got the hidden service we had in mind, but also
20008 whether we got the particular descriptors we wanted. This prevents
20009 a class of inefficient but annoying DoS attacks by hidden service
20010 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
20013 o Minor bugfixes (Linux seccomp2 sandbox):
20014 - Make transparent proxy support work along with the seccomp2
20015 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
20016 by Francisco Blas Izquierdo Riera.
20017 - Fix a memory leak in tor-resolve when running with the sandbox
20018 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
20020 o Minor bugfixes (logging):
20021 - Downgrade warnings about RSA signature failures to info log level.
20022 Emit a warning when an extra info document is found incompatible
20023 with a corresponding router descriptor. Fixes bug 9812; bugfix
20025 - Make connection_ap_handshake_attach_circuit() log the circuit ID
20026 correctly. Fixes bug 13701; bugfix on 0.0.6.
20028 o Minor bugfixes (misc):
20029 - Stop allowing invalid address patterns like "*/24" that contain
20030 both a wildcard address and a bit prefix length. This affects all
20031 our address-range parsing code. Fixes bug 7484; bugfix
20034 o Minor bugfixes (testing networks, fast startup):
20035 - Allow Tor to build circuits using a consensus with no exits. If
20036 the consensus has no exits (typical of a bootstrapping test
20037 network), allow Tor to build circuits once enough descriptors have
20038 been downloaded. This assists in bootstrapping a testing Tor
20039 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
20041 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
20042 header to directory servers. This allows us to obtain consensuses
20043 promptly when the consensus interval is very short. This assists
20044 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
20045 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
20046 - Stop assuming that private addresses are local when checking
20047 reachability in a TestingTorNetwork. Instead, when testing, assume
20048 all OR connections are remote. (This is necessary due to many test
20049 scenarios running all relays on localhost.) This assists in
20050 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
20051 0.1.0.1-rc. Patch by "teor".
20052 - Avoid building exit circuits from a consensus with no exits. Now
20053 thanks to our fix for 13718, we accept a no-exit network as not
20054 wholly lost, but we need to remember not to try to build exit
20055 circuits on it. Closes ticket 13814; patch by "teor".
20056 - Stop requiring exits to have non-zero bandwithcapacity in a
20057 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
20058 ignore exit bandwidthcapacity. This assists in bootstrapping a
20059 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
20060 on 0.2.0.3-alpha. Patch by "teor".
20061 - Add "internal" to some bootstrap statuses when no exits are
20062 available. If the consensus does not contain Exits, Tor will only
20063 build internal circuits. In this case, relevant statuses will
20064 contain the word "internal" as indicated in the Tor control-
20065 spec.txt. When bootstrap completes, Tor will be ready to build
20066 internal circuits. If a future consensus contains Exits, exit
20067 circuits may become available. Fixes part of bug 13718; bugfix on
20068 0.2.4.10-alpha. Patch by "teor".
20069 - Decrease minimum consensus interval to 10 seconds when
20070 TestingTorNetwork is set, or 5 seconds for the first consensus.
20071 Fix assumptions throughout the code that assume larger intervals.
20072 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
20074 - Avoid excluding guards from path building in minimal test
20075 networks, when we're in a test network and excluding guards would
20076 exclude all relays. This typically occurs in incredibly small tor
20077 networks, and those using "TestingAuthVoteGuard *". Fixes part of
20078 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
20080 o Code simplification and refactoring:
20081 - Stop using can_complete_circuits as a global variable; access it
20082 with a function instead.
20083 - Avoid using operators directly as macro arguments: this lets us
20084 apply coccinelle transformations to our codebase more directly.
20085 Closes ticket 13172.
20086 - Combine the functions used to parse ClientTransportPlugin and
20087 ServerTransportPlugin into a single function. Closes ticket 6456.
20088 - Add inline functions and convenience macros for inspecting channel
20089 state. Refactor the code to use convenience macros instead of
20090 checking channel state directly. Fixes issue 7356.
20091 - Document all members of was_router_added_t and rename
20092 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
20093 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
20094 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
20095 constant instead of hardcoded value. Fixes issue 13840.
20096 - Refactor our generic strmap and digestmap types into a single
20097 implementation, so that we can add a new digest256map
20101 - Document the bridge-authority-only 'networkstatus-bridges' file.
20102 Closes ticket 13713; patch from "tom".
20103 - Fix typo in PredictedPortsRelevanceTime option description in
20104 manpage. Resolves issue 13707.
20105 - Stop suggesting that users specify relays by nickname: it isn't a
20106 good idea. Also, properly cross-reference how to specify relays in
20107 all parts of manual documenting options that take a list of
20108 relays. Closes ticket 13381.
20109 - Clarify the HiddenServiceDir option description in manpage to make
20110 it clear that relative paths are taken with respect to the current
20111 working directory. Also clarify that this behavior is not
20112 guaranteed to remain indefinitely. Fixes issue 13913.
20115 - New tests for many parts of channel, relay, and circuitmux
20116 functionality. Code by Andrea; part of 9262.
20117 - New tests for parse_transport_line(). Part of ticket 6456.
20118 - In the unit tests, use chgrp() to change the group of the unit
20119 test temporary directory to the current user, so that the sticky
20120 bit doesn't interfere with tests that check directory groups.
20122 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
20126 Changes in version 0.2.6.1-alpha - 2014-10-30
20127 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
20128 includes numerous code cleanups and new tests, and fixes a large
20129 number of annoying bugs. Out-of-memory conditions are handled better
20130 than in 0.2.5, pluggable transports have improved proxy support, and
20131 clients now use optimistic data for contacting hidden services. Also,
20132 we are now more robust to changes in what we consider a parseable
20133 directory object, so that tightening restrictions does not have a risk
20134 of introducing infinite download loops.
20136 This is the first alpha release in a new series, so expect there to be
20137 bugs. Users who would rather test out a more stable branch should stay
20138 with 0.2.5.x for now.
20140 o New compiler and system requirements:
20141 - Tor 0.2.6.x requires that your compiler support more of the C99
20142 language standard than before. The 'configure' script now detects
20143 whether your compiler supports C99 mid-block declarations and
20144 designated initializers. If it does not, Tor will not compile.
20146 We may revisit this requirement if it turns out that a significant
20147 number of people need to build Tor with compilers that don't
20148 bother implementing a 15-year-old standard. Closes ticket 13233.
20149 - Tor no longer supports systems without threading support. When we
20150 began working on Tor, there were several systems that didn't have
20151 threads, or where the thread support wasn't able to run the
20152 threads of a single process on multiple CPUs. That no longer
20153 holds: every system where Tor needs to run well now has threading
20154 support. Resolves ticket 12439.
20156 o Removed platform support:
20157 - We no longer include special code to build on Windows CE; as far
20158 as we know, nobody has used Tor on Windows CE in a very long time.
20159 Closes ticket 11446.
20161 o Major features (bridges):
20162 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
20163 transports if they are configured via the "TOR_PT_PROXY"
20164 environment variable. Implements proposal 232. Resolves
20167 o Major features (client performance, hidden services):
20168 - Allow clients to use optimistic data when connecting to a hidden
20169 service, which should remove a round-trip from hidden service
20170 initialization. See proposal 181 for details. Implements
20173 o Major features (directory system):
20174 - Upon receiving an unparseable directory object, if its digest
20175 matches what we expected, then don't try to download it again.
20176 Previously, when we got a descriptor we didn't like, we would keep
20177 trying to download it over and over. Closes ticket 11243.
20179 o Major features (sample torrc):
20180 - Add a new, infrequently-changed "torrc.minimal". This file is
20181 similar to torrc.sample, but it will change as infrequently as
20182 possible, for the benefit of users whose systems prompt them for
20183 intervention whenever a default configuration file is changed.
20184 Making this change allows us to update torrc.sample to be a more
20185 generally useful "sample torrc".
20187 o Major bugfixes (directory authorities):
20188 - Do not assign the HSDir flag to relays if they are not Valid, or
20189 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
20191 o Major bugfixes (directory bandwidth performance):
20192 - Don't flush the zlib buffer aggressively when compressing
20193 directory information for clients. This should save about 7% of
20194 the bandwidth currently used for compressed descriptors and
20195 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
20197 o Minor features (security, memory wiping):
20198 - Ensure we securely wipe keys from memory after
20199 crypto_digest_get_digest and init_curve25519_keypair_from_file
20200 have finished using them. Resolves ticket 13477.
20202 o Minor features (security, out-of-memory handling):
20203 - When handling an out-of-memory condition, allocate less memory for
20204 temporary data structures. Fixes issue 10115.
20205 - When handling an out-of-memory condition, consider more types of
20206 buffers, including those on directory connections, and zlib
20207 buffers. Resolves ticket 11792.
20210 - When identity keypair is generated for first time, log a
20211 congratulatory message that links to the new relay lifecycle
20212 document. Implements feature 10427.
20214 o Minor features (client):
20215 - Clients are now willing to send optimistic data (before they
20216 receive a 'connected' cell) to relays of any version. (Relays
20217 without support for optimistic data are no longer supported on the
20218 Tor network.) Resolves ticket 13153.
20220 o Minor features (directory authorities):
20221 - Don't list relays with a bandwidth estimate of 0 in the consensus.
20222 Implements a feature proposed during discussion of bug 13000.
20223 - In tor-gencert, report an error if the user provides the same
20224 argument more than once.
20225 - If a directory authority can't find a best consensus method in the
20226 votes that it holds, it now falls back to its favorite consensus
20227 method. Previously, it fell back to method 1. Neither of these is
20228 likely to get enough signatures, but "fall back to favorite"
20229 doesn't require us to maintain support an obsolete consensus
20230 method. Implements part of proposal 215.
20232 o Minor features (logging):
20233 - On Unix-like systems, you can now use named pipes as the target of
20234 the Log option, and other options that try to append to files.
20235 Closes ticket 12061. Patch from "carlo von lynX".
20236 - When opening a log file at startup, send it every log message that
20237 we generated between startup and opening it. Previously, log
20238 messages that were generated before opening the log file were only
20239 logged to stdout. Closes ticket 6938.
20240 - Add a TruncateLogFile option to overwrite logs instead of
20241 appending to them. Closes ticket 5583.
20243 o Minor features (portability, Solaris):
20244 - Threads are no longer disabled by default on Solaris; we believe
20245 that the versions of Solaris with broken threading support are all
20246 obsolete by now. Resolves ticket 9495.
20248 o Minor features (relay):
20249 - Re-check our address after we detect a changed IP address from
20250 getsockname(). This ensures that the controller command "GETINFO
20251 address" will report the correct value. Resolves ticket 11582.
20253 - A new AccountingRule option lets Relays set whether they'd like
20254 AccountingMax to be applied separately to inbound and outbound
20255 traffic, or applied to the sum of inbound and outbound traffic.
20256 Resolves ticket 961. Patch by "chobe".
20258 o Minor features (testing networks):
20259 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
20260 the "Exit" flag regardless of their uptime, bandwidth, or exit
20261 policy. TestingTorNetwork must be set for this option to have any
20262 effect. Previously, authorities would take up to 35 minutes to
20263 give nodes the Exit flag in a test network. Partially implements
20266 o Minor features (validation):
20267 - Check all date/time values passed to tor_timegm and
20268 parse_rfc1123_time for validity, taking leap years into account.
20269 Improves HTTP header validation. Implemented with bug 13476.
20270 - In correct_tm(), limit the range of values returned by system
20271 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
20272 This means we don't have to deal with negative or too large dates,
20273 even if a clock is wrong. Otherwise we might fail to read a file
20274 written by us which includes such a date. Fixes bug 13476.
20276 o Minor bugfixes (bridge clients):
20277 - When configured to use a bridge without an identity digest (not
20278 recommended), avoid launching an extra channel to it when
20279 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
20281 o Minor bugfixes (bridges):
20282 - When DisableNetwork is set, do not launch pluggable transport
20283 plugins, and if any are running, terminate them. Fixes bug 13213;
20284 bugfix on 0.2.3.6-alpha.
20286 o Minor bugfixes (C correctness):
20287 - Fix several instances of possible integer overflow/underflow/NaN.
20288 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
20290 - In circuit_build_times_calculate_timeout() in circuitstats.c,
20291 avoid dividing by zero in the pareto calculations. This traps
20292 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
20294 - Fix an integer overflow in format_time_interval(). Fixes bug
20295 13393; bugfix on 0.2.0.10-alpha.
20296 - Set the correct day of year value when the system's localtime(_r)
20297 or gmtime(_r) functions fail to set struct tm. Not externally
20298 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
20299 - Avoid unlikely signed integer overflow in tor_timegm on systems
20300 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
20302 o Minor bugfixes (client):
20303 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
20304 BadExit flag are not considered worthy candidates. Fixes bug
20305 13066; bugfix on 0.1.2.3-alpha.
20306 - Use the consensus schedule for downloading consensuses, and not
20307 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
20308 - Handle unsupported or malformed SOCKS5 requests properly by
20309 responding with the appropriate error message before closing the
20310 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
20312 o Minor bugfixes (client, torrc):
20313 - Stop modifying the value of our DirReqStatistics torrc option just
20314 because we're not a bridge or relay. This bug was causing Tor
20315 Browser users to write "DirReqStatistics 0" in their torrc files
20316 as if they had chosen to change the config. Fixes bug 4244; bugfix
20318 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
20319 that our options have changed every time we SIGHUP. Fixes bug
20320 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
20322 o Minor bugfixes (controller):
20323 - Return an error when the second or later arguments of the
20324 "setevents" controller command are invalid events. Previously we
20325 would return success while silently skipping invalid events. Fixes
20326 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
20328 o Minor bugfixes (directory system):
20329 - Always believe that v3 directory authorities serve extra-info
20330 documents, whether they advertise "caches-extra-info" or not.
20331 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
20332 - When running as a v3 directory authority, advertise that you serve
20333 extra-info documents so that clients who want them can find them
20334 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
20335 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
20336 Previously, directories offering BRIDGE_DIRINFO and some other
20337 flag (i.e. microdescriptors or extrainfo) would be ignored when
20338 looking for bridges. Partially fixes bug 13163; bugfix
20341 o Minor bugfixes (networking):
20342 - Check for orconns and use connection_or_close_for_error() rather
20343 than connection_mark_for_close() directly in the getsockopt()
20344 failure case of connection_handle_write_impl(). Fixes bug 11302;
20345 bugfix on 0.2.4.4-alpha.
20347 o Minor bugfixes (relay):
20348 - When generating our family list, remove spaces from around the
20349 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
20350 - If our previous bandwidth estimate was 0 bytes, allow publishing a
20351 new relay descriptor immediately. Fixes bug 13000; bugfix
20354 o Minor bugfixes (testing networks):
20355 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
20356 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
20357 - Stop using the default authorities in networks which provide both
20358 AlternateDirAuthority and AlternateBridgeAuthority. Partially
20359 fixes bug 13163; bugfix on 0.2.0.13-alpha.
20361 o Minor bugfixes (testing):
20362 - Stop spawn test failures due to a race condition between the
20363 SIGCHLD handler updating the process status, and the test reading
20364 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
20366 o Minor bugfixes (testing, Windows):
20367 - Avoid passing an extra backslash when creating a temporary
20368 directory for running the unit tests on Windows. Fixes bug 12392;
20369 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
20371 o Minor bugfixes (windows):
20372 - Remove code to special-case handling of NTE_BAD_KEYSET when
20373 acquiring windows CryptoAPI context. This error can't actually
20374 occur for the parameters we're providing. Fixes bug 10816; bugfix
20377 o Minor bugfixes (zlib):
20378 - Avoid truncating a zlib stream when trying to finalize it with an
20379 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
20382 - Allow our configure script to build correctly with autoconf 2.62
20383 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
20384 - Improve the error message from ./configure to make it clear that
20385 when asciidoc has not been found, the user will have to either add
20386 --disable-asciidoc argument or install asciidoc. Resolves
20389 o Code simplification and refactoring:
20390 - Change the entry_is_live() function to take named bitfield
20391 elements instead of an unnamed list of booleans. Closes
20393 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
20394 Resolves ticket 12205.
20395 - Use calloc and reallocarray functions instead of multiply-
20396 then-malloc. This makes it less likely for us to fall victim to an
20397 integer overflow attack when allocating. Resolves ticket 12855.
20398 - Use the standard macro name SIZE_MAX, instead of our
20400 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
20401 functions which take them as arguments. Replace 0 with NO_DIRINFO
20402 in a function call for clarity. Seeks to prevent future issues
20404 - Avoid 4 null pointer errors under clang static analysis by using
20405 tor_assert() to prove that the pointers aren't null. Fixes
20407 - Rework the API of policies_parse_exit_policy() to use a bitmask to
20408 represent parsing options, instead of a confusing mess of
20409 booleans. Resolves ticket 8197.
20410 - Introduce a helper function to parse ExitPolicy in
20411 or_options_t structure.
20414 - Add a doc/TUNING document with tips for handling large numbers of
20415 TCP connections when running busy Tor relay. Update the warning
20416 message to point to this file when running out of sockets
20417 operating system is allowing to use simultaneously. Resolves
20420 o Removed features:
20421 - We no longer remind the user about configuration options that have
20422 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
20423 - Remove our old, non-weighted bandwidth-based node selection code.
20424 Previously, we used it as a fallback when we couldn't perform
20425 weighted bandwidth-based node selection. But that would only
20426 happen in the cases where we had no consensus, or when we had a
20427 consensus generated by buggy or ancient directory authorities. In
20428 either case, it's better to use the more modern, better maintained
20429 algorithm, with reasonable defaults for the weights. Closes
20431 - Remove the --disable-curve25519 configure option. Relays and
20432 clients now are required to support curve25519 and the
20434 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
20435 used to be deprecated synonyms for "StrictNodes", are now marked
20436 obsolete. Resolves ticket 12226.
20437 - Clients don't understand the BadDirectory flag in the consensus
20438 anymore, and ignore it.
20441 - Refactor the function that chooses guard nodes so that it can more
20442 easily be tested; write some tests for it.
20443 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
20444 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
20445 - Create unit tests for format_time_interval(). With bug 13393.
20446 - Add unit tests for tor_timegm signed overflow, tor_timegm and
20447 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
20448 tests (visible) fixes in bug 13476.
20449 - Add a "coverage-html" make target to generate HTML-visualized
20450 coverage results when building with --enable-coverage. (Requires
20451 lcov.) Patch from Kevin Murray.
20452 - Enable the backtrace handler (where supported) when running the
20454 - Revise all unit tests that used the legacy test_* macros to
20455 instead use the recommended tt_* macros. This patch was generated
20456 with coccinelle, to avoid manual errors. Closes ticket 13119.
20458 o Distribution (systemd):
20459 - systemd unit file: only allow tor to write to /var/lib/tor and
20460 /var/log/tor. The rest of the filesystem is accessible for reading
20461 only. Patch by intrigeri; resolves ticket 12751.
20462 - systemd unit file: ensure that the process and all its children
20463 can never gain new privileges. Patch by intrigeri; resolves
20465 - systemd unit file: set up /var/run/tor as writable for the Tor
20466 service. Patch by intrigeri; resolves ticket 13196.
20468 o Removed features (directory authorities):
20469 - Remove code that prevented authorities from listing Tor relays
20470 affected by CVE-2011-2769 as guards. These relays are already
20471 rejected altogether due to the minimum version requirement of
20472 0.2.3.16-alpha. Closes ticket 13152.
20473 - The "AuthDirRejectUnlisted" option no longer has any effect, as
20474 the fingerprints file (approved-routers) has been deprecated.
20475 - Directory authorities do not support being Naming dirauths anymore.
20476 The "NamingAuthoritativeDir" config option is now obsolete.
20477 - Directory authorities do not support giving out the BadDirectory
20479 - Directory authorities no longer advertise or support consensus
20480 methods 1 through 12 inclusive. These consensus methods were
20481 obsolete and/or insecure: maintaining the ability to support them
20482 served no good purpose. Implements part of proposal 215; closes
20485 o Testing (test-network.sh):
20486 - Stop using "echo -n", as some shells' built-in echo doesn't
20487 support "-n". Instead, use "/bin/echo -n". Partially fixes
20489 - Stop an apparent test-network hang when used with make -j2. Fixes
20491 - Add a --delay option to test-network.sh, which configures the
20492 delay before the chutney network tests for data transmission.
20493 Partially implements ticket 13161.
20496 Changes in version 0.2.5.10 - 2014-10-24
20497 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
20499 It adds several new security features, including improved
20500 denial-of-service resistance for relays, new compiler hardening
20501 options, and a system-call sandbox for hardened installations on Linux
20502 (requires seccomp2). The controller protocol has several new features,
20503 resolving IPv6 addresses should work better than before, and relays
20504 should be a little more CPU-efficient. We've added support for more
20505 OpenBSD and FreeBSD transparent proxy types. We've improved the build
20506 system and testing infrastructure to allow unit testing of more parts
20507 of the Tor codebase. Finally, we've addressed several nagging pluggable
20508 transport usability issues, and included numerous other small bugfixes
20509 and features mentioned below.
20511 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
20512 have accumulated many known flaws; everyone should upgrade.
20514 o Deprecated versions:
20515 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
20516 attention for some while.
20519 Changes in version 0.2.5.9-rc - 2014-10-20
20520 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
20521 series. It disables SSL3 in response to the recent "POODLE" attack
20522 (even though POODLE does not affect Tor). It also works around a crash
20523 bug caused by some operating systems' response to the "POODLE" attack
20524 (which does affect Tor). It also contains a few miscellaneous fixes.
20526 o Major security fixes:
20527 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
20528 today support TLS 1.0 or later, so we can safely turn off support
20529 for this old (and insecure) protocol. Fixes bug 13426.
20531 o Major bugfixes (openssl bug workaround):
20532 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
20533 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
20534 13471. This is a workaround for an OpenSSL bug.
20537 - Disable the sandbox name resolver cache when running tor-resolve:
20538 tor-resolve doesn't use the sandbox code, and turning it on was
20539 breaking attempts to do tor-resolve on a non-default server on
20540 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
20542 o Compilation fixes:
20543 - Build and run correctly on systems like OpenBSD-current that have
20544 patched OpenSSL to remove get_cipher_by_char and/or its
20545 implementations. Fixes issue 13325.
20547 o Downgraded warnings:
20548 - Downgrade the severity of the 'unexpected sendme cell from client'
20549 from 'warn' to 'protocol warning'. Closes ticket 8093.
20552 Changes in version 0.2.4.25 - 2014-10-20
20553 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
20554 (even though POODLE does not affect Tor). It also works around a crash
20555 bug caused by some operating systems' response to the "POODLE" attack
20556 (which does affect Tor).
20558 o Major security fixes (also in 0.2.5.9-rc):
20559 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
20560 today support TLS 1.0 or later, so we can safely turn off support
20561 for this old (and insecure) protocol. Fixes bug 13426.
20563 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
20564 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
20565 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
20566 13471. This is a workaround for an OpenSSL bug.
20569 Changes in version 0.2.5.8-rc - 2014-09-22
20570 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
20571 series. It fixes a bug that affects consistency and speed when
20572 connecting to hidden services, and it updates the location of one of
20573 the directory authorities.
20576 - Clients now send the correct address for their chosen rendezvous
20577 point when trying to access a hidden service. They used to send
20578 the wrong address, which would still work some of the time because
20579 they also sent the identity digest of the rendezvous point, and if
20580 the hidden service happened to try connecting to the rendezvous
20581 point from a relay that already had a connection open to it,
20582 the relay would reuse that connection. Now connections to hidden
20583 services should be more robust and faster. Also, this bug meant
20584 that clients were leaking to the hidden service whether they were
20585 on a little-endian (common) or big-endian (rare) system, which for
20586 some users might have reduced their anonymity. Fixes bug 13151;
20587 bugfix on 0.2.1.5-alpha.
20589 o Directory authority changes:
20590 - Change IP address for gabelmoo (v3 directory authority).
20593 Changes in version 0.2.4.24 - 2014-09-22
20594 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
20595 connecting to hidden services, and it updates the location of one of
20596 the directory authorities.
20599 - Clients now send the correct address for their chosen rendezvous
20600 point when trying to access a hidden service. They used to send
20601 the wrong address, which would still work some of the time because
20602 they also sent the identity digest of the rendezvous point, and if
20603 the hidden service happened to try connecting to the rendezvous
20604 point from a relay that already had a connection open to it,
20605 the relay would reuse that connection. Now connections to hidden
20606 services should be more robust and faster. Also, this bug meant
20607 that clients were leaking to the hidden service whether they were
20608 on a little-endian (common) or big-endian (rare) system, which for
20609 some users might have reduced their anonymity. Fixes bug 13151;
20610 bugfix on 0.2.1.5-alpha.
20612 o Directory authority changes:
20613 - Change IP address for gabelmoo (v3 directory authority).
20615 o Minor features (geoip):
20616 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
20620 Changes in version 0.2.5.7-rc - 2014-09-11
20621 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
20622 release series, and some long-standing bugs related to ORPort reachability
20623 testing and failure to send CREATE cells. It is the first release
20624 candidate for the Tor 0.2.5.x series.
20626 o Major bugfixes (client, startup):
20627 - Start making circuits as soon as DisabledNetwork is turned off.
20628 When Tor started with DisabledNetwork set, it would correctly
20629 conclude that it shouldn't build circuits, but it would mistakenly
20630 cache this conclusion, and continue believing it even when
20631 DisableNetwork is set to 0. Fixes the bug introduced by the fix
20632 for bug 11200; bugfix on 0.2.5.4-alpha.
20633 - Resume expanding abbreviations for command-line options. The fix
20634 for bug 4647 accidentally removed our hack from bug 586 that
20635 rewrote HashedControlPassword to __HashedControlSessionPassword
20636 when it appears on the commandline (which allowed the user to set
20637 her own HashedControlPassword in the torrc file while the
20638 controller generates a fresh session password for each run). Fixes
20639 bug 12948; bugfix on 0.2.5.1-alpha.
20640 - Warn about attempts to run hidden services and relays in the same
20641 process: that's probably not a good idea. Closes ticket 12908.
20643 o Major bugfixes (relay):
20644 - Avoid queuing or sending destroy cells for circuit ID zero when we
20645 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
20646 Found and fixed by "cypherpunks".
20647 - Fix ORPort reachability detection on relays running behind a
20648 proxy, by correctly updating the "local" mark on the controlling
20649 channel when changing the address of an or_connection_t after the
20650 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
20652 o Minor features (bridge):
20653 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
20654 cookie file for the ExtORPort g+r by default.
20656 o Minor features (geoip):
20657 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
20660 o Minor bugfixes (logging):
20661 - Reduce the log severity of the "Pluggable transport proxy does not
20662 provide any needed transports and will not be launched." message,
20663 since Tor Browser includes several ClientTransportPlugin lines in
20664 its torrc-defaults file, leading every Tor Browser user who looks
20665 at her logs to see these notices and wonder if they're dangerous.
20666 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
20667 - Downgrade "Unexpected onionskin length after decryption" warning
20668 to a protocol-warn, since there's nothing relay operators can do
20669 about a client that sends them a malformed create cell. Resolves
20670 bug 12996; bugfix on 0.0.6rc1.
20671 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
20672 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
20673 - When logging information about an EXTEND2 or EXTENDED2 cell, log
20674 their names correctly. Fixes part of bug 12700; bugfix
20676 - When logging information about a relay cell whose command we don't
20677 recognize, log its command as an integer. Fixes part of bug 12700;
20678 bugfix on 0.2.1.10-alpha.
20679 - Escape all strings from the directory connection before logging
20680 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
20682 o Minor bugfixes (controller):
20683 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
20684 bug 12864; bugfix on 0.2.5.1-alpha.
20685 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
20686 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
20689 o Minor bugfixes (compilation):
20690 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
20691 bugfix on 0.2.5.5-alpha.
20692 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
20693 0.2.5.1-alpha. Patch from "NewEraCracker".
20694 - In routerlist_assert_ok(), don't take the address of a
20695 routerinfo's cache_info member unless that routerinfo is non-NULL.
20696 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
20697 - Fix a large number of false positive warnings from the clang
20698 analyzer static analysis tool. This should make real warnings
20699 easier for clang analyzer to find. Patch from "teor". Closes
20702 o Distribution (systemd):
20703 - Verify configuration file via ExecStartPre in the systemd unit
20704 file. Patch from intrigeri; resolves ticket 12730.
20705 - Explicitly disable RunAsDaemon in the systemd unit file. Our
20706 current systemd unit uses "Type = simple", so systemd does not
20707 expect tor to fork. If the user has "RunAsDaemon 1" in their
20708 torrc, then things won't work as expected. This is e.g. the case
20709 on Debian (and derivatives), since there we pass "--defaults-torrc
20710 /usr/share/tor/tor-service-defaults-torrc" (that contains
20711 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
20715 - Adjust the URLs in the README to refer to the new locations of
20716 several documents on the website. Fixes bug 12830. Patch from
20718 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
20722 Changes in version 0.2.5.6-alpha - 2014-07-28
20723 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
20724 risk from guard rotation, and fixes a variety of other issues to get
20725 us closer to a release candidate.
20727 o Major features (also in 0.2.4.23):
20728 - Make the number of entry guards configurable via a new
20729 NumEntryGuards consensus parameter, and the number of directory
20730 guards configurable via a new NumDirectoryGuards consensus
20731 parameter. Implements ticket 12688.
20733 o Major bugfixes (also in 0.2.4.23):
20734 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
20735 implementation that caused incorrect results on 32-bit
20736 implementations when certain malformed inputs were used along with
20737 a small class of private ntor keys. This bug does not currently
20738 appear to allow an attacker to learn private keys or impersonate a
20739 Tor server, but it could provide a means to distinguish 32-bit Tor
20740 implementations from 64-bit Tor implementations. Fixes bug 12694;
20741 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
20745 - Perform circuit cleanup operations even when circuit
20746 construction operations are disabled (because the network is
20747 disabled, or because there isn't enough directory information).
20748 Previously, when we were not building predictive circuits, we
20749 were not closing expired circuits either. Fixes bug 8387; bugfix on
20750 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
20751 became more strict about when we have "enough directory information
20752 to build circuits".
20755 - Authorities now assign the Guard flag to the fastest 25% of the
20756 network (it used to be the fastest 50%). Also raise the consensus
20757 weight that guarantees the Guard flag from 250 to 2000. For the
20758 current network, this results in about 1100 guards, down from 2500.
20759 This step paves the way for moving the number of entry guards
20760 down to 1 (proposal 236) while still providing reasonable expected
20761 performance for most users. Implements ticket 12690.
20762 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
20764 - Slightly enhance the diagnostic message for bug 12184.
20766 o Minor bugfixes (also in 0.2.4.23):
20767 - Warn and drop the circuit if we receive an inbound 'relay early'
20768 cell. Those used to be normal to receive on hidden service circuits
20769 due to bug 1038, but the buggy Tor versions are long gone from
20770 the network so we can afford to resume watching for them. Resolves
20771 the rest of bug 1038; bugfix on 0.2.1.19.
20772 - Correct a confusing error message when trying to extend a circuit
20773 via the control protocol but we don't know a descriptor or
20774 microdescriptor for one of the specified relays. Fixes bug 12718;
20775 bugfix on 0.2.3.1-alpha.
20778 - Fix compilation when building with bufferevents enabled. (This
20779 configuration is still not expected to work, however.)
20780 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
20781 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
20783 - Compile correctly with builds and forks of OpenSSL (such as
20784 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
20785 0.2.1.1-alpha. Patch from "dhill".
20788 Changes in version 0.2.4.23 - 2014-07-28
20789 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
20790 guard rotation, and also backports several important fixes from the
20791 Tor 0.2.5 alpha release series.
20794 - Clients now look at the "usecreatefast" consensus parameter to
20795 decide whether to use CREATE_FAST or CREATE cells for the first hop
20796 of their circuit. This approach can improve security on connections
20797 where Tor's circuit handshake is stronger than the available TLS
20798 connection security levels, but the tradeoff is more computational
20799 load on guard relays. Implements proposal 221. Resolves ticket 9386.
20800 - Make the number of entry guards configurable via a new
20801 NumEntryGuards consensus parameter, and the number of directory
20802 guards configurable via a new NumDirectoryGuards consensus
20803 parameter. Implements ticket 12688.
20806 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
20807 implementation that caused incorrect results on 32-bit
20808 implementations when certain malformed inputs were used along with
20809 a small class of private ntor keys. This bug does not currently
20810 appear to allow an attacker to learn private keys or impersonate a
20811 Tor server, but it could provide a means to distinguish 32-bit Tor
20812 implementations from 64-bit Tor implementations. Fixes bug 12694;
20813 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
20817 - Warn and drop the circuit if we receive an inbound 'relay early'
20818 cell. Those used to be normal to receive on hidden service circuits
20819 due to bug 1038, but the buggy Tor versions are long gone from
20820 the network so we can afford to resume watching for them. Resolves
20821 the rest of bug 1038; bugfix on 0.2.1.19.
20822 - Correct a confusing error message when trying to extend a circuit
20823 via the control protocol but we don't know a descriptor or
20824 microdescriptor for one of the specified relays. Fixes bug 12718;
20825 bugfix on 0.2.3.1-alpha.
20826 - Avoid an illegal read from stack when initializing the TLS
20827 module using a version of OpenSSL without all of the ciphers
20828 used by the v2 link handshake. Fixes bug 12227; bugfix on
20829 0.2.4.8-alpha. Found by "starlight".
20832 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
20836 Changes in version 0.2.5.5-alpha - 2014-06-18
20837 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
20838 0.2.5.x release series, including a couple of DoS issues, some
20839 performance regressions, a large number of bugs affecting the Linux
20840 seccomp2 sandbox code, and various other bugfixes. It also adds
20841 diagnostic bugfixes for a few tricky issues that we're trying to
20844 o Major features (security, traffic analysis resistance):
20845 - Several major improvements to the algorithm used to decide when to
20846 close TLS connections. Previous versions of Tor closed connections
20847 at a fixed interval after the last time a non-padding cell was
20848 sent over the connection, regardless of the target of the
20849 connection. Now, we randomize the intervals by adding up to 50% of
20850 their base value, we measure the length of time since connection
20851 last had at least one circuit, and we allow connections to known
20852 ORs to remain open a little longer (15 minutes instead of 3
20853 minutes minimum). These changes should improve Tor's resistance
20854 against some kinds of traffic analysis, and lower some overhead
20855 from needlessly closed connections. Fixes ticket 6799.
20856 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
20858 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
20859 - Fix a memory leak that could occur if a microdescriptor parse
20860 fails during the tokenizing step. This bug could enable a memory
20861 exhaustion attack by directory servers. Fixes bug 11649; bugfix
20864 o Major bugfixes (security, directory authorities):
20865 - Directory authorities now include a digest of each relay's
20866 identity key as a part of its microdescriptor.
20868 This is a workaround for bug 11743 (reported by "cypherpunks"),
20869 where Tor clients do not support receiving multiple
20870 microdescriptors with the same SHA256 digest in the same
20871 consensus. When clients receive a consensus like this, they only
20872 use one of the relays. Without this fix, a hostile relay could
20873 selectively disable some client use of target relays by
20874 constructing a router descriptor with a different identity and the
20875 same microdescriptor parameters and getting the authorities to
20876 list it in a microdescriptor consensus. This fix prevents an
20877 attacker from causing a microdescriptor collision, because the
20878 router's identity is not forgeable.
20880 o Major bugfixes (relay):
20881 - Use a direct dirport connection when uploading non-anonymous
20882 descriptors to the directory authorities. Previously, relays would
20883 incorrectly use tunnel connections under a fairly wide variety of
20884 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
20885 - When a circuit accidentally has the same circuit ID for its
20886 forward and reverse direction, correctly detect the direction of
20887 cells using that circuit. Previously, this bug made roughly one
20888 circuit in a million non-functional. Fixes bug 12195; this is a
20889 bugfix on every version of Tor.
20891 o Major bugfixes (client, pluggable transports):
20892 - When managing pluggable transports, use OS notification facilities
20893 to learn if they have crashed, and don't attempt to kill any
20894 process that has already exited. Fixes bug 8746; bugfix
20897 o Minor features (diagnostic):
20898 - When logging a warning because of bug 7164, additionally check the
20899 hash table for consistency (as proposed on ticket 11737). This may
20900 help diagnose bug 7164.
20901 - When we log a heartbeat, log how many one-hop circuits we have
20902 that are at least 30 minutes old, and log status information about
20903 a few of them. This is an attempt to track down bug 8387.
20904 - When encountering an unexpected CR while writing text to a file on
20905 Windows, log the name of the file. Should help diagnosing
20907 - Give more specific warnings when a client notices that an onion
20908 handshake has failed. Fixes ticket 9635.
20909 - Add significant new logging code to attempt to diagnose bug 12184,
20910 where relays seem to run out of available circuit IDs.
20911 - Improve the diagnostic log message for bug 8387 even further to
20912 try to improve our odds of figuring out why one-hop directory
20913 circuits sometimes do not get closed.
20915 o Minor features (security, memory management):
20916 - Memory allocation tricks (mempools and buffer freelists) are now
20917 disabled by default. You can turn them back on with
20918 --enable-mempools and --enable-buf-freelists respectively. We're
20919 disabling these features because malloc performance is good enough
20920 on most platforms, and a similar feature in OpenSSL exacerbated
20921 exploitation of the Heartbleed attack. Resolves ticket 11476.
20923 o Minor features (security):
20924 - Apply the secure SipHash-2-4 function to the hash table mapping
20925 circuit IDs and channels to circuits. We missed this one when we
20926 were converting all the other hash functions to use SipHash back
20927 in 0.2.5.3-alpha. Resolves ticket 11750.
20929 o Minor features (build):
20930 - The configure script has a --disable-seccomp option to turn off
20931 support for libseccomp on systems that have it, in case it (or
20932 Tor's use of it) is broken. Resolves ticket 11628.
20934 o Minor features (other):
20935 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
20938 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
20939 - When running a hidden service, do not allow TunneledDirConns 0;
20940 this will keep the hidden service from running, and also
20941 make it publish its descriptors directly over HTTP. Fixes bug 10849;
20942 bugfix on 0.2.1.1-alpha.
20944 o Minor bugfixes (performance):
20945 - Avoid a bug where every successful connection made us recompute
20946 the flag telling us whether we have sufficient information to
20947 build circuits. Previously, we would forget our cached value
20948 whenever we successfully opened a channel (or marked a router as
20949 running or not running for any other reason), regardless of
20950 whether we had previously believed the router to be running. This
20951 forced us to run an expensive update operation far too often.
20952 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
20953 - Avoid using tor_memeq() for checking relay cell integrity. This
20954 removes a possible performance bottleneck. Fixes part of bug
20955 12169; bugfix on 0.2.1.31.
20957 o Minor bugfixes (compilation):
20958 - Fix compilation of test_status.c when building with MVSC. Bugfix
20959 on 0.2.5.4-alpha. Patch from Gisle Vanem.
20960 - Resolve GCC complaints on OpenBSD about discarding constness in
20961 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
20962 on 0.1.1.23. Patch from Dana Koch.
20963 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
20964 treatment of long and time_t as comparable types. Fixes part of
20965 bug 11633. Patch from Dana Koch.
20966 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
20967 11623; bugfix on 0.2.5.3-alpha.
20968 - When deciding whether to build the 64-bit curve25519
20969 implementation, detect platforms where we can compile 128-bit
20970 arithmetic but cannot link it. Fixes bug 11729; bugfix on
20971 0.2.4.8-alpha. Patch from "conradev".
20972 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
20973 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
20974 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
20977 o Minor bugfixes (Directory server):
20978 - When sending a compressed set of descriptors or microdescriptors,
20979 make sure to finalize the zlib stream. Previously, we would write
20980 all the compressed data, but if the last descriptor we wanted to
20981 send was missing or too old, we would not mark the stream as
20982 finished. This caused problems for decompression tools. Fixes bug
20983 11648; bugfix on 0.1.1.23.
20985 o Minor bugfixes (Linux seccomp sandbox):
20986 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
20987 11622; bugfix on 0.2.5.1-alpha.
20988 - Avoid crashing when re-opening listener ports with the seccomp
20989 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
20990 - Avoid crashing with the seccomp sandbox enabled along with
20991 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
20992 - When we receive a SIGHUP with the sandbox enabled, correctly
20993 support rotating our log files. Fixes bug 12032; bugfix
20995 - Avoid crash when running with sandboxing enabled and
20996 DirReqStatistics not disabled. Fixes bug 12035; bugfix
20998 - Fix a "BUG" warning when trying to write bridge-stats files with
20999 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
21001 - Prevent the sandbox from crashing on startup when run with the
21002 --enable-expensive-hardening configuration option. Fixes bug
21003 11477; bugfix on 0.2.5.4-alpha.
21004 - When running with DirPortFrontPage and sandboxing both enabled,
21005 reload the DirPortFrontPage correctly when restarting. Fixes bug
21006 12028; bugfix on 0.2.5.1-alpha.
21007 - Don't try to enable the sandbox when using the Tor binary to check
21008 its configuration, hash a passphrase, or so on. Doing so was
21009 crashing on startup for some users. Fixes bug 11609; bugfix
21011 - Avoid warnings when running with sandboxing and node statistics
21012 enabled at the same time. Fixes part of 12064; bugfix on
21013 0.2.5.1-alpha. Patch from Michael Wolf.
21014 - Avoid warnings when running with sandboxing enabled at the same
21015 time as cookie authentication, hidden services, or directory
21016 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
21017 - Do not allow options that require calls to exec to be enabled
21018 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
21019 bug 12043; bugfix on 0.2.5.1-alpha.
21020 - Handle failures in getpwnam()/getpwuid() when running with the
21021 User option set and the Linux syscall sandbox enabled. Fixes bug
21022 11946; bugfix on 0.2.5.1-alpha.
21023 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
21024 to avoid calling getaddrinfo() after installing the sandbox
21025 filters. Previously, it preloaded a cache with the IPv4 address
21026 for our hostname, and nothing else. Now, it loads the cache with
21027 every address that it used to initialize the Tor process. Fixes
21028 bug 11970; bugfix on 0.2.5.1-alpha.
21030 o Minor bugfixes (pluggable transports):
21031 - Enable the ExtORPortCookieAuthFile option, to allow changing the
21032 default location of the authentication token for the extended OR
21033 Port as used by sever-side pluggable transports. We had
21034 implemented this option before, but the code to make it settable
21035 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
21036 - Avoid another 60-second delay when starting Tor in a pluggable-
21037 transport-using configuration when we already have cached
21038 descriptors for our bridges. Fixes bug 11965; bugfix
21041 o Minor bugfixes (client):
21042 - Avoid "Tried to open a socket with DisableNetwork set" warnings
21043 when starting a client with bridges configured and DisableNetwork
21044 set. (Tor launcher starts Tor with DisableNetwork set the first
21045 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
21047 o Minor bugfixes (testing):
21048 - The Python parts of the test scripts now work on Python 3 as well
21049 as Python 2, so systems where '/usr/bin/python' is Python 3 will
21050 no longer have the tests break. Fixes bug 11608; bugfix
21052 - When looking for versions of python that we could run the tests
21053 with, check for "python2.7" and "python3.3"; previously we were
21054 only looking for "python", "python2", and "python3". Patch from
21055 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
21056 - Fix all valgrind warnings produced by the unit tests. There were
21057 over a thousand memory leak warnings previously, mostly produced
21058 by forgetting to free things in the unit test code. Fixes bug
21059 11618, bugfixes on many versions of Tor.
21061 o Minor bugfixes (tor-fw-helper):
21062 - Give a correct log message when tor-fw-helper fails to launch.
21063 (Previously, we would say something like "tor-fw-helper sent us a
21064 string we could not parse".) Fixes bug 9781; bugfix
21067 o Minor bugfixes (relay, threading):
21068 - Check return code on spawn_func() in cpuworker code, so that we
21069 don't think we've spawned a nonworking cpuworker and write junk to
21070 it forever. Fix related to bug 4345; bugfix on all released Tor
21071 versions. Found by "skruffy".
21072 - Use a pthread_attr to make sure that spawn_func() cannot return an
21073 error while at the same time launching a thread. Fix related to
21074 bug 4345; bugfix on all released Tor versions. Reported
21077 o Minor bugfixes (relay, oom prevention):
21078 - Correctly detect the total available system memory. We tried to do
21079 this in 0.2.5.4-alpha, but the code was set up to always return an
21080 error value, even on success. Fixes bug 11805; bugfix
21083 o Minor bugfixes (relay, other):
21084 - We now drop CREATE cells for already-existent circuit IDs and for
21085 zero-valued circuit IDs, regardless of other factors that might
21086 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
21088 - Avoid an illegal read from stack when initializing the TLS module
21089 using a version of OpenSSL without all of the ciphers used by the
21090 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
21092 - When rejecting DATA cells for stream_id zero, still count them
21093 against the circuit's deliver window so that we don't fail to send
21094 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
21096 o Minor bugfixes (logging):
21097 - Fix a misformatted log message about delayed directory fetches.
21098 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
21099 - Squelch a spurious LD_BUG message "No origin circuit for
21100 successful SOCKS stream" in certain hidden service failure cases;
21104 - Include a tor.service file in contrib/dist for use with systemd.
21105 Some distributions will be able to use this file unmodified;
21106 others will need to tweak it, or write their own. Patch from Jamie
21107 Nguyen; resolves ticket 8368.
21110 - Clean up several option names in the manpage to match their real
21111 names, add the missing documentation for a couple of testing and
21112 directory authority options, remove the documentation for a
21113 V2-directory fetching option that no longer exists. Resolves
21115 - Correct the documentation so that it lists the correct directory
21116 for the stats files. (They are in a subdirectory called "stats",
21118 - In the manpage, move more authority-only options into the
21119 directory authority section so that operators of regular directory
21120 caches don't get confused.
21123 - The contrib directory has been sorted and tidied. Before, it was
21124 an unsorted dumping ground for useful and not-so-useful things.
21125 Now, it is divided based on functionality, and the items which
21126 seemed to be nonfunctional or useless have been removed. Resolves
21127 ticket 8966; based on patches from "rl1987".
21130 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
21131 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
21132 - The TunnelDirConns and PreferTunnelledDirConns options no longer
21133 exist; tunneled directory connections have been available since
21134 0.1.2.5-alpha, and turning them off is not a good idea. This is a
21135 brute-force fix for 10849, where "TunnelDirConns 0" would break
21139 Changes in version 0.2.4.22 - 2014-05-16
21140 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
21141 alpha release series. These include blocking all authority signing
21142 keys that may have been affected by the OpenSSL "heartbleed" bug,
21143 choosing a far more secure set of TLS ciphersuites by default, closing
21144 a couple of memory leaks that could be used to run a target relay out
21145 of RAM, and several others.
21147 o Major features (security, backport from 0.2.5.4-alpha):
21148 - Block authority signing keys that were used on authorities
21149 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
21150 don't have any evidence that these keys _were_ compromised; we're
21151 doing this to be prudent.) Resolves ticket 11464.
21153 o Major bugfixes (security, OOM):
21154 - Fix a memory leak that could occur if a microdescriptor parse
21155 fails during the tokenizing step. This bug could enable a memory
21156 exhaustion attack by directory servers. Fixes bug 11649; bugfix
21159 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
21160 - The relay ciphersuite list is now generated automatically based on
21161 uniform criteria, and includes all OpenSSL ciphersuites with
21162 acceptable strength and forward secrecy. Previously, we had left
21163 some perfectly fine ciphersuites unsupported due to omission or
21164 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
21165 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
21166 - Relays now trust themselves to have a better view than clients of
21167 which TLS ciphersuites are better than others. (Thanks to bug
21168 11513, the relay list is now well-considered, whereas the client
21169 list has been chosen mainly for anti-fingerprinting purposes.)
21170 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
21171 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
21172 AES128. Resolves ticket 11528.
21173 - Clients now try to advertise the same list of ciphersuites as
21174 Firefox 28. This change enables selection of (fast) GCM
21175 ciphersuites, disables some strange old ciphers, and stops
21176 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
21177 Resolves ticket 11438.
21179 o Minor bugfixes (configuration, security):
21180 - When running a hidden service, do not allow TunneledDirConns 0:
21181 trying to set that option together with a hidden service would
21182 otherwise prevent the hidden service from running, and also make
21183 it publish its descriptors directly over HTTP. Fixes bug 10849;
21184 bugfix on 0.2.1.1-alpha.
21186 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
21187 - Avoid sending a garbage value to the controller when a circuit is
21188 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
21190 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
21191 - Stop leaking memory when we successfully resolve a PTR record.
21192 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
21194 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
21195 - Avoid 60-second delays in the bootstrapping process when Tor is
21196 launching for a second time while using bridges. Fixes bug 9229;
21197 bugfix on 0.2.0.3-alpha.
21199 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
21200 - Give the correct URL in the warning message when trying to run a
21201 relay on an ancient version of Windows. Fixes bug 9393.
21203 o Minor bugfixes (compilation):
21204 - Fix a compilation error when compiling with --disable-curve25519.
21205 Fixes bug 9700; bugfix on 0.2.4.17-rc.
21208 - Downgrade the warning severity for the the "md was still
21209 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
21210 for trying to diagnose this bug, and the current warning in
21211 earlier versions of tor achieves nothing useful. Addresses warning
21214 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
21215 - When we run out of usable circuit IDs on a channel, log only one
21216 warning for the whole channel, and describe how many circuits
21217 there were on the channel. Fixes part of ticket 11553.
21219 o Minor features (security, backport from 0.2.5.4-alpha):
21220 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
21221 leave the default at 8GBytes), to better support Raspberry Pi
21222 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
21224 o Documentation (backport from 0.2.5.4-alpha):
21225 - Correctly document that we search for a system torrc file before
21226 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
21230 Changes in version 0.2.5.4-alpha - 2014-04-25
21231 Tor 0.2.5.4-alpha includes several security and performance
21232 improvements for clients and relays, including blacklisting authority
21233 signing keys that were used while susceptible to the OpenSSL
21234 "heartbleed" bug, fixing two expensive functions on busy relays,
21235 improved TLS ciphersuite preference lists, support for run-time
21236 hardening on compilers that support AddressSanitizer, and more work on
21237 the Linux sandbox code.
21239 There are also several usability fixes for clients (especially clients
21240 that use bridges), two new TransPort protocols supported (one on
21241 OpenBSD, one on FreeBSD), and various other bugfixes.
21243 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
21244 have accumulated many known flaws; everyone should upgrade.
21246 o Major features (security):
21247 - If you don't specify MaxMemInQueues yourself, Tor now tries to
21248 pick a good value based on your total system memory. Previously,
21249 the default was always 8 GB. You can still override the default by
21250 setting MaxMemInQueues yourself. Resolves ticket 11396.
21251 - Block authority signing keys that were used on authorities
21252 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
21253 don't have any evidence that these keys _were_ compromised; we're
21254 doing this to be prudent.) Resolves ticket 11464.
21256 o Major features (relay performance):
21257 - Speed up server-side lookups of rendezvous and introduction point
21258 circuits by using hashtables instead of linear searches. These
21259 functions previously accounted between 3 and 7% of CPU usage on
21260 some busy relays. Resolves ticket 9841.
21261 - Avoid wasting CPU when extending a circuit over a channel that is
21262 nearly out of circuit IDs. Previously, we would do a linear scan
21263 over possible circuit IDs before finding one or deciding that we
21264 had exhausted our possibilities. Now, we try at most 64 random
21265 circuit IDs before deciding that we probably won't succeed. Fixes
21266 a possible root cause of ticket 11553.
21268 o Major features (seccomp2 sandbox, Linux only):
21269 - The seccomp2 sandbox can now run a test network for multiple hours
21270 without crashing. The sandbox is still experimental, and more bugs
21271 will probably turn up. To try it, enable "Sandbox 1" on a Linux
21272 host. Resolves ticket 11351.
21273 - Strengthen sandbox code: the sandbox can now test the arguments
21274 for rename(), and blocks _sysctl() entirely. Resolves another part
21276 - When the sandbox blocks a system call, it now tries to log a stack
21277 trace before exiting. Resolves ticket 11465.
21279 o Major bugfixes (TLS cipher selection):
21280 - The relay ciphersuite list is now generated automatically based on
21281 uniform criteria, and includes all OpenSSL ciphersuites with
21282 acceptable strength and forward secrecy. Previously, we had left
21283 some perfectly fine ciphersuites unsupported due to omission or
21284 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
21285 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
21286 - Relays now trust themselves to have a better view than clients of
21287 which TLS ciphersuites are better than others. (Thanks to bug
21288 11513, the relay list is now well-considered, whereas the client
21289 list has been chosen mainly for anti-fingerprinting purposes.)
21290 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
21291 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
21292 AES128. Resolves ticket 11528.
21293 - Clients now try to advertise the same list of ciphersuites as
21294 Firefox 28. This change enables selection of (fast) GCM
21295 ciphersuites, disables some strange old ciphers, and stops
21296 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
21297 Resolves ticket 11438.
21299 o Major bugfixes (bridge client):
21300 - Avoid 60-second delays in the bootstrapping process when Tor is
21301 launching for a second time while using bridges. Fixes bug 9229;
21302 bugfix on 0.2.0.3-alpha.
21304 o Minor features (transparent proxy, *BSD):
21305 - Support FreeBSD's ipfw firewall interface for TransPort ports on
21306 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
21307 10267; patch from "yurivict".
21308 - Support OpenBSD's divert-to rules with the pf firewall for
21309 transparent proxy ports. To enable it, set "TransProxyType
21310 pf-divert". This allows Tor to run a TransPort transparent proxy
21311 port on OpenBSD 4.4 or later without root privileges. See the
21312 pf.conf(5) manual page for information on configuring pf to use
21313 divert-to rules. Closes ticket 10896; patch from Dana Koch.
21315 o Minor features (security):
21316 - New --enable-expensive-hardening option to enable security
21317 hardening options that consume nontrivial amounts of CPU and
21318 memory. Right now, this includes AddressSanitizer and UbSan, which
21319 are supported in newer versions of GCC and Clang. Closes ticket
21322 o Minor features (log verbosity):
21323 - Demote the message that we give when a flushing connection times
21324 out for too long from NOTICE to INFO. It was usually meaningless.
21325 Resolves ticket 5286.
21326 - Don't log so many notice-level bootstrapping messages at startup
21327 about downloading descriptors. Previously, we'd log a notice
21328 whenever we learned about more routers. Now, we only log a notice
21329 at every 5% of progress. Fixes bug 9963.
21330 - Warn less verbosely when receiving a malformed
21331 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
21332 - When we run out of usable circuit IDs on a channel, log only one
21333 warning for the whole channel, and describe how many circuits
21334 there were on the channel. Fixes part of ticket 11553.
21336 o Minor features (relay):
21337 - If a circuit timed out for at least 3 minutes, check if we have a
21338 new external IP address, and publish a new descriptor with the new
21339 IP address if it changed. Resolves ticket 2454.
21341 o Minor features (controller):
21342 - Make the entire exit policy available from the control port via
21343 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
21345 - Because of the fix for ticket 11396, the real limit for memory
21346 usage may no longer match the configured MaxMemInQueues value. The
21347 real limit is now exposed via GETINFO limits/max-mem-in-queues.
21349 o Minor features (bridge client):
21350 - Report a more useful failure message when we can't connect to a
21351 bridge because we don't have the right pluggable transport
21352 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
21354 o Minor features (diagnostic):
21355 - Add more log messages to diagnose bug 7164, which causes
21356 intermittent "microdesc_free() called but md was still referenced"
21357 warnings. We now include more information, to figure out why we
21358 might be cleaning a microdescriptor for being too old if it's
21359 still referenced by a live node_t object.
21361 o Minor bugfixes (client, DNSPort):
21362 - When using DNSPort, try to respond to AAAA requests with AAAA
21363 answers. Previously, we hadn't looked at the request type when
21364 deciding which answer type to prefer. Fixes bug 10468; bugfix on
21366 - When receiving a DNS query for an unsupported record type, reply
21367 with no answer rather than with a NOTIMPL error. This behavior
21368 isn't correct either, but it will break fewer client programs, we
21369 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
21372 o Minor bugfixes (exit relay):
21373 - Stop leaking memory when we successfully resolve a PTR record.
21374 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
21376 o Minor bugfixes (bridge client):
21377 - Stop accepting bridge lines containing hostnames. Doing so would
21378 cause clients to perform DNS requests on the hostnames, which was
21379 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
21380 - Avoid a 60-second delay in the bootstrapping process when a Tor
21381 client with pluggable transports re-reads its configuration at
21382 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
21384 o Minor bugfixes (client, logging during bootstrap):
21385 - Warn only once if we start logging in an unsafe way. Previously,
21386 we complain as many times as we had problems. Fixes bug 9870;
21387 bugfix on 0.2.5.1-alpha.
21388 - Only report the first fatal bootstrap error on a given OR
21389 connection. This stops us from telling the controller bogus error
21390 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
21391 - Be more helpful when trying to run sandboxed on Linux without
21392 libseccomp. Instead of saying "Sandbox is not implemented on this
21393 platform", we now explain that we need to be built with
21394 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
21395 - Avoid generating spurious warnings when starting with
21396 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
21399 o Minor bugfixes (closing OR connections):
21400 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
21401 check if it's an or_connection_t and correctly call
21402 connection_or_close_for_error() rather than
21403 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
21405 - When closing all connections on setting DisableNetwork to 1, use
21406 connection_or_close_normally() rather than closing OR connections
21407 out from under the channel layer. Fixes bug 11306; bugfix on
21410 o Minor bugfixes (controller):
21411 - Avoid sending a garbage value to the controller when a circuit is
21412 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
21414 o Minor bugfixes (tor-fw-helper):
21415 - Allow tor-fw-helper to build again by adding src/ext to its
21416 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
21418 o Minor bugfixes (bridges):
21419 - Avoid potential crashes or bad behavior when launching a
21420 server-side managed proxy with ORPort or ExtORPort temporarily
21421 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
21423 o Minor bugfixes (platform-specific):
21424 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
21425 bug 11426; bugfix on 0.2.5.3-alpha.
21426 - When dumping a malformed directory object to disk, save it in
21427 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
21429 - Don't report failures from make_socket_reuseable() on incoming
21430 sockets on OSX: this can happen when incoming connections close
21431 early. Fixes bug 10081.
21433 o Minor bugfixes (trivial memory leaks):
21434 - Fix a small memory leak when signing a directory object. Fixes bug
21435 11275; bugfix on 0.2.4.13-alpha.
21436 - Free placeholder entries in our circuit table at exit; fixes a
21437 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
21438 - Don't re-initialize a second set of OpenSSL mutexes when starting
21439 up. Previously, we'd make one set of mutexes, and then immediately
21440 replace them with another. Fixes bug 11726; bugfix on
21442 - Resolve some memory leaks found by coverity in the unit tests, on
21443 exit in tor-gencert, and on a failure to compute digests for our
21444 own keys when generating a v3 networkstatus vote. These leaks
21445 should never have affected anyone in practice.
21447 o Minor bugfixes (hidden service):
21448 - Only retry attempts to connect to a chosen rendezvous point 8
21449 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
21451 o Minor bugfixes (misc code correctness):
21452 - Fix various instances of undefined behavior in channeltls.c,
21453 tor_memmem(), and eventdns.c that would cause us to construct
21454 pointers to memory outside an allocated object. (These invalid
21455 pointers were not accessed, but C does not even allow them to
21456 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
21457 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
21458 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
21459 fix some miscellaneous errors in our tests and codebase. Fixes bug
21460 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
21461 - Always check return values for unlink, munmap, UnmapViewOfFile;
21462 check strftime return values more often. In some cases all we can
21463 do is report a warning, but this may help prevent deeper bugs from
21464 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
21466 - Fix numerous warnings from the clang "scan-build" static analyzer.
21467 Some of these are programming style issues; some of them are false
21468 positives that indicated awkward code; some are undefined behavior
21469 cases related to constructing (but not using) invalid pointers;
21470 some are assumptions about API behavior; some are (harmlessly)
21471 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
21472 correct; and one or two are genuine bugs that weren't reachable
21473 from the rest of the program. Fixes bug 8793; bugfixes on many,
21477 - Build the torify.1 manpage again. Previously, we were only trying
21478 to build it when also building tor-fw-helper. That's why we didn't
21479 notice that we'd broken the ability to build it. Fixes bug 11321;
21480 bugfix on 0.2.5.1-alpha.
21481 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
21482 11061; bugfix on 0.2.4.7-alpha.
21483 - Correctly document that we search for a system torrc file before
21484 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
21486 - Resolve warnings from Doxygen.
21488 o Code simplifications and refactoring:
21489 - Remove is_internal_IP() function. Resolves ticket 4645.
21490 - Remove unused function circuit_dump_by_chan from circuitlist.c.
21491 Closes issue 9107; patch from "marek".
21492 - Change our use of the ENUM_BF macro to avoid declarations that
21495 o Deprecated versions:
21496 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
21497 attention for some while. Directory authorities no longer accept
21498 descriptors from relays running any version of Tor prior to Tor
21499 0.2.3.16-alpha. Resolves ticket 11149.
21502 - New macros in test.h to simplify writing mock-functions for unit
21503 tests. Part of ticket 11507. Patch from Dana Koch.
21504 - Complete tests for the status.c module. Resolves ticket 11507.
21505 Patch from Dana Koch.
21508 - Remove all code for the long unused v1 directory protocol.
21509 Resolves ticket 11070.
21512 Changes in version 0.2.5.3-alpha - 2014-03-22
21513 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
21514 two new anti-DoS features for Tor relays, resolves a bug that kept
21515 SOCKS5 support for IPv6 from working, fixes several annoying usability
21516 issues for bridge users, and removes more old code for unused
21519 The Tor 0.2.5.x release series is now in patch-freeze: no feature
21520 patches not already written will be considered for inclusion in 0.2.5.x.
21522 o Major features (relay security, DoS-resistance):
21523 - When deciding whether we have run out of memory and we need to
21524 close circuits, also consider memory allocated in buffers for
21525 streams attached to each circuit.
21527 This change, which extends an anti-DoS feature introduced in
21528 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
21529 better resist more memory-based DoS attacks than before. Since the
21530 MaxMemInCellQueues option now applies to all queues, it is renamed
21531 to MaxMemInQueues. This feature fixes bug 10169.
21532 - Avoid hash-flooding denial-of-service attacks by using the secure
21533 SipHash-2-4 hash function for our hashtables. Without this
21534 feature, an attacker could degrade performance of a targeted
21535 client or server by flooding their data structures with a large
21536 number of entries to be stored at the same hash table position,
21537 thereby slowing down the Tor instance. With this feature, hash
21538 table positions are derived from a randomized cryptographic key,
21539 and an attacker cannot predict which entries will collide. Closes
21541 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
21542 the default at 8GBytes), to better support Raspberry Pi users. Fixes
21543 bug 9686; bugfix on 0.2.4.14-alpha.
21545 o Minor features (bridges, pluggable transports):
21546 - Bridges now write the SHA1 digest of their identity key
21547 fingerprint (that is, a hash of a hash of their public key) to
21548 notice-level logs, and to a new hashed-fingerprint file. This
21549 information will help bridge operators look up their bridge in
21550 Globe and similar tools. Resolves ticket 10884.
21551 - Improve the message that Tor displays when running as a bridge
21552 using pluggable transports without an Extended ORPort listener.
21553 Also, log the message in the log file too. Resolves ticket 11043.
21555 o Minor features (other):
21556 - Add a new option, PredictedPortsRelevanceTime, to control how long
21557 after having received a request to connect to a given port Tor
21558 will try to keep circuits ready in anticipation of future requests
21559 for that port. Patch from "unixninja92"; implements ticket 9176.
21560 - Generate a warning if any ports are listed in the SocksPolicy,
21561 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
21562 AuthDirBadExit options. (These options only support address
21563 ranges.) Fixes part of ticket 11108.
21564 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
21567 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
21568 - Build without warnings under clang 3.4. (We have some macros that
21569 define static functions only some of which will get used later in
21570 the module. Starting with clang 3.4, these give a warning unless the
21571 unused attribute is set on them.) Resolves ticket 10904.
21572 - Fix build warnings about missing "a2x" comment when building the
21573 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
21574 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
21576 o Minor bugfixes (client):
21577 - Improve the log message when we can't connect to a hidden service
21578 because all of the hidden service directory nodes hosting its
21579 descriptor are excluded. Improves on our fix for bug 10722, which
21580 was a bugfix on 0.2.0.10-alpha.
21581 - Raise a control port warning when we fail to connect to all of
21582 our bridges. Previously, we didn't inform the controller, and
21583 the bootstrap process would stall. Fixes bug 11069; bugfix on
21585 - Exit immediately when a process-owning controller exits.
21586 Previously, tor relays would wait for a little while after their
21587 controller exited, as if they had gotten an INT signal -- but this
21588 was problematic, since there was no feedback for the user. To do a
21589 clean shutdown, controllers should send an INT signal and give Tor
21590 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
21591 - Stop attempting to connect to bridges before our pluggable
21592 transports are configured (harmless but resulted in some erroneous
21593 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
21594 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
21595 generating incorrect SOCKS5 responses, and confusing client
21596 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
21598 o Minor bugfixes (relays and bridges):
21599 - Avoid crashing on a malformed resolv.conf file when running a
21600 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
21601 - Non-exit relays no longer launch mock DNS requests to check for
21602 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
21603 non-exit relays stopped servicing DNS requests. Fixes bug 965;
21604 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
21605 - Bridges now report complete directory request statistics. Related
21606 to bug 5824; bugfix on 0.2.2.1-alpha.
21607 - Bridges now never collect statistics that were designed for
21608 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
21609 - Stop giving annoying warning messages when we decide not to launch
21610 a pluggable transport proxy that we don't need (because there are
21611 no bridges configured to use it). Resolves ticket 5018; bugfix
21613 - Give the correct URL in the warning message when trying to run a
21614 relay on an ancient version of Windows. Fixes bug 9393.
21616 o Minor bugfixes (backtrace support):
21617 - Support automatic backtraces on more platforms by using the
21618 "-fasynchronous-unwind-tables" compiler option. This option is
21619 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
21620 is on by default and table generation is not. This doesn't yet
21621 add Windows support; only Linux, OSX, and some BSDs are affected.
21622 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
21623 - Avoid strange behavior if two threads hit failed assertions at the
21624 same time and both try to log backtraces at once. (Previously, if
21625 this had happened, both threads would have stored their intermediate
21626 results in the same buffer, and generated junk outputs.) Reported by
21627 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
21628 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
21629 0.2.5.2-alpha; patch from Nick Hopper.
21631 o Minor bugfixes (unit tests):
21632 - Fix a small bug in the unit tests that might have made the tests
21633 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
21634 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
21637 - Remove all remaining code related to version-0 hidden service
21638 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
21639 the rest of bug 10841.
21642 - Document in the manpage that "KBytes" may also be written as
21643 "kilobytes" or "KB", that "Kbits" may also be written as
21644 "kilobits", and so forth. Closes ticket 9222.
21645 - Document that the ClientOnly config option overrides ORPort.
21646 Our old explanation made ClientOnly sound as though it did
21647 nothing at all. Resolves bug 9059.
21648 - Explain that SocksPolicy, DirPolicy, and similar options don't
21649 take port arguments. Fixes the other part of ticket 11108.
21650 - Fix a comment about the rend_server_descriptor_t.protocols field
21651 to more accurately describe its range. Also, make that field
21652 unsigned, to more accurately reflect its usage. Fixes bug 9099;
21653 bugfix on 0.2.1.5-alpha.
21654 - Fix the manpage's description of HiddenServiceAuthorizeClient:
21655 the maximum client name length is 16, not 19. Fixes bug 11118;
21656 bugfix on 0.2.1.6-alpha.
21658 o Code simplifications and refactoring:
21659 - Get rid of router->address, since in all cases it was just the
21660 string representation of router->addr. Resolves ticket 5528.
21662 o Test infrastructure:
21663 - Update to the latest version of tinytest.
21664 - Improve the tinytest implementation of string operation tests so
21665 that comparisons with NULL strings no longer crash the tests; they
21666 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
21669 Changes in version 0.2.4.21 - 2014-02-28
21670 Tor 0.2.4.21 further improves security against potential adversaries who
21671 find breaking 1024-bit crypto doable, and backports several stability
21672 and robustness patches from the 0.2.5 branch.
21674 o Major features (client security):
21675 - When we choose a path for a 3-hop circuit, make sure it contains
21676 at least one relay that supports the NTor circuit extension
21677 handshake. Otherwise, there is a chance that we're building
21678 a circuit that's worth attacking by an adversary who finds
21679 breaking 1024-bit crypto doable, and that chance changes the game
21680 theory. Implements ticket 9777.
21683 - Do not treat streams that fail with reason
21684 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
21685 since it could also indicate an ENETUNREACH connection error. Fixes
21686 part of bug 10777; bugfix on 0.2.4.8-alpha.
21688 o Code simplification and refactoring:
21689 - Remove data structures which were introduced to implement the
21690 CellStatistics option: they are now redundant with the new timestamp
21691 field in the regular packed_cell_t data structure, which we did
21692 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
21695 - Always clear OpenSSL bignums before freeing them -- even bignums
21696 that don't contain secrets. Resolves ticket 10793. Patch by
21698 - Build without warnings under clang 3.4. (We have some macros that
21699 define static functions only some of which will get used later in
21700 the module. Starting with clang 3.4, these give a warning unless the
21701 unused attribute is set on them.) Resolves ticket 10904.
21702 - Update geoip and geoip6 files to the February 7 2014 Maxmind
21703 GeoLite2 Country database.
21706 - Set the listen() backlog limit to the largest actually supported
21707 on the system, not to the value in a header file. Fixes bug 9716;
21708 bugfix on every released Tor.
21709 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
21710 exit node as a NOROUTE error, not an INTERNAL error, since they
21711 can apparently happen when trying to connect to the wrong sort
21712 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
21713 - Fix build warnings about missing "a2x" comment when building the
21714 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
21715 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
21716 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
21717 not entirely remove it from the connection lists. Fixes bug 9602;
21718 bugfix on 0.2.4.4-alpha.
21719 - Fix a segmentation fault in our benchmark code when running with
21720 Fedora's OpenSSL package, or any other OpenSSL that provides
21721 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
21722 - Turn "circuit handshake stats since last time" log messages into a
21723 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
21725 o Documentation fixes:
21726 - Document that all but one DirPort entry must have the NoAdvertise
21727 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
21730 Changes in version 0.2.5.2-alpha - 2014-02-13
21731 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
21732 like the "poor random number generation" fix and the "building too many
21733 circuits" fix. It also further improves security against potential
21734 adversaries who find breaking 1024-bit crypto doable, and launches
21735 pluggable transports on demand (which gets us closer to integrating
21736 pluggable transport support by default -- not to be confused with Tor
21737 bundles enabling pluggable transports and bridges by default).
21739 o Major features (client security):
21740 - When we choose a path for a 3-hop circuit, make sure it contains
21741 at least one relay that supports the NTor circuit extension
21742 handshake. Otherwise, there is a chance that we're building
21743 a circuit that's worth attacking by an adversary who finds
21744 breaking 1024-bit crypto doable, and that chance changes the game
21745 theory. Implements ticket 9777.
21746 - Clients now look at the "usecreatefast" consensus parameter to
21747 decide whether to use CREATE_FAST or CREATE cells for the first hop
21748 of their circuit. This approach can improve security on connections
21749 where Tor's circuit handshake is stronger than the available TLS
21750 connection security levels, but the tradeoff is more computational
21751 load on guard relays. Implements proposal 221. Resolves ticket 9386.
21753 o Major features (bridges):
21754 - Don't launch pluggable transport proxies if we don't have any
21755 bridges configured that would use them. Now we can list many
21756 pluggable transports, and Tor will dynamically start one when it
21757 hears a bridge address that needs it. Resolves ticket 5018.
21758 - The bridge directory authority now assigns status flags (Stable,
21759 Guard, etc) to bridges based on thresholds calculated over all
21760 Running bridges. Now bridgedb can finally make use of its features
21761 to e.g. include at least one Stable bridge in its answers. Fixes
21764 o Major features (other):
21765 - Extend ORCONN controller event to include an "ID" parameter,
21766 and add four new controller event types CONN_BW, CIRC_BW,
21767 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
21768 The new events are emitted in private Tor networks only, with the
21769 goal of being able to better track performance and load during
21770 full-network simulations. Implements proposal 218 and ticket 7359.
21771 - On some platforms (currently: recent OSX versions, glibc-based
21772 platforms that support the ELF format, and a few other
21773 Unix-like operating systems), Tor can now dump stack traces
21774 when a crash occurs or an assertion fails. By default, traces
21775 are dumped to stderr (if possible) and to any logs that are
21776 reporting errors. Implements ticket 9299.
21779 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
21780 not entirely remove it from the connection lists. Fixes bug 9602;
21781 bugfix on 0.2.4.4-alpha.
21782 - Do not treat streams that fail with reason
21783 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
21784 since it could also indicate an ENETUNREACH connection error. Fixes
21785 part of bug 10777; bugfix on 0.2.4.8-alpha.
21787 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
21788 - Do not allow OpenSSL engines to replace the PRNG, even when
21789 HardwareAccel is set. The only default builtin PRNG engine uses
21790 the Intel RDRAND instruction to replace the entire PRNG, and
21791 ignores all attempts to seed it with more entropy. That's
21792 cryptographically stupid: the right response to a new alleged
21793 entropy source is never to discard all previously used entropy
21794 sources. Fixes bug 10402; works around behavior introduced in
21795 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
21797 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
21798 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
21799 - Avoid launching spurious extra circuits when a stream is pending.
21800 This fixes a bug where any circuit that _wasn't_ unusable for new
21801 streams would be treated as if it were, causing extra circuits to
21802 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
21804 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
21805 - No longer stop reading or writing on cpuworker connections when
21806 our rate limiting buckets go empty. Now we should handle circuit
21807 handshake requests more promptly. Resolves bug 9731.
21808 - Stop trying to bootstrap all our directory information from
21809 only our first guard. Discovered while fixing bug 9946; bugfix
21812 o Minor features (bridges, pluggable transports):
21813 - Add threshold cutoffs to the networkstatus document created by
21814 the Bridge Authority. Fixes bug 1117.
21815 - On Windows, spawn background processes using the CREATE_NO_WINDOW
21816 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
21817 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
21818 Vidalia set this option for us.) Implements ticket 10297.
21820 o Minor features (security):
21821 - Always clear OpenSSL bignums before freeing them -- even bignums
21822 that don't contain secrets. Resolves ticket 10793. Patch by
21825 o Minor features (config options and command line):
21826 - Add an --allow-missing-torrc commandline option that tells Tor to
21827 run even if the configuration file specified by -f is not available.
21828 Implements ticket 10060.
21829 - Add support for the TPROXY transparent proxying facility on Linux.
21830 See documentation for the new TransProxyType option for more
21831 details. Implementation by "thomo". Closes ticket 10582.
21833 o Minor features (controller):
21834 - Add a new "HS_DESC" controller event that reports activities
21835 related to hidden service descriptors. Resolves ticket 8510.
21836 - New "DROPGUARDS" controller command to forget all current entry
21837 guards. Not recommended for ordinary use, since replacing guards
21838 too frequently makes several attacks easier. Resolves ticket 9934;
21841 o Minor features (build):
21842 - Assume that a user using ./configure --host wants to cross-compile,
21843 and give an error if we cannot find a properly named
21844 tool-chain. Add a --disable-tool-name-check option to proceed
21845 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
21846 - If we run ./configure and the compiler recognizes -fstack-protector
21847 but the linker rejects it, warn the user about a potentially missing
21848 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
21850 o Minor features (testing):
21851 - If Python is installed, "make check" now runs extra tests beyond
21852 the unit test scripts.
21853 - When bootstrapping a test network, sometimes very few relays get
21854 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
21855 specify a set of relays which should be voted Guard regardless of
21856 their uptime or bandwidth. Addresses ticket 9206.
21858 o Minor features (log messages):
21859 - When ServerTransportPlugin is set on a bridge, Tor can write more
21860 useful statistics about bridge use in its extrainfo descriptors,
21861 but only if the Extended ORPort ("ExtORPort") is set too. Add a
21862 log message to inform the user in this case. Resolves ticket 9651.
21863 - When receiving a new controller connection, log the origin address.
21864 Resolves ticket 9698; patch from "sigpipe".
21865 - When logging OpenSSL engine status at startup, log the status of
21866 more engines. Fixes ticket 10043; patch from Joshua Datko.
21867 - Turn "circuit handshake stats since last time" log messages into a
21868 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
21870 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
21871 - Improve the circuit queue out-of-memory handler. Previously, when
21872 we ran low on memory, we'd close whichever circuits had the most
21873 queued cells. Now, we close those that have the *oldest* queued
21874 cells, on the theory that those are most responsible for us
21875 running low on memory. Based on analysis from a forthcoming paper
21876 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
21877 - Generate bootstrapping status update events correctly when fetching
21878 microdescriptors. Fixes bug 9927.
21879 - Update to the October 2 2013 Maxmind GeoLite Country database.
21881 o Minor bugfixes (clients):
21882 - When closing a channel that has already been open, do not close
21883 pending circuits that were waiting to connect to the same relay.
21884 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
21887 o Minor bugfixes (relays):
21888 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
21889 exit node as a NOROUTE error, not an INTERNAL error, since they
21890 can apparently happen when trying to connect to the wrong sort
21891 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
21893 o Minor bugfixes (bridges):
21894 - Fix a bug where the first connection works to a bridge that uses a
21895 pluggable transport with client-side parameters, but we don't send
21896 the client-side parameters on subsequent connections. (We don't
21897 use any pluggable transports with client-side parameters yet,
21898 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
21899 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
21901 o Minor bugfixes (node selection):
21902 - If ExcludeNodes is set, consider non-excluded hidden service
21903 directory servers before excluded ones. Do not consider excluded
21904 hidden service directory servers at all if StrictNodes is
21905 set. (Previously, we would sometimes decide to connect to those
21906 servers, and then realize before we initiated a connection that
21907 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
21908 Reported by "mr-4".
21909 - If we set the ExitNodes option but it doesn't include any nodes
21910 that have the Exit flag, we would choose not to bootstrap. Now we
21911 bootstrap so long as ExitNodes includes nodes which can exit to
21912 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
21914 o Minor bugfixes (controller and command-line):
21915 - If changing a config option via "setconf" fails in a recoverable
21916 way, we used to nonetheless write our new control ports to the
21917 file described by the "ControlPortWriteToFile" option. Now we only
21918 write out that file if we successfully switch to the new config
21919 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
21920 - When a command-line option such as --version or --help that
21921 ordinarily implies --hush appears on the command line along with
21922 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
21923 only if it appeared later on the command line. Fixes bug 9578;
21924 bugfix on 0.2.5.1-alpha.
21926 o Minor bugfixes (code correctness):
21927 - Previously we used two temporary files when writing descriptors to
21928 disk; now we only use one. Fixes bug 1376.
21929 - Remove an erroneous (but impossible and thus harmless) pointer
21930 comparison that would have allowed compilers to skip a bounds
21931 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
21932 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
21933 - Fix an always-true assertion in pluggable transports code so it
21934 actually checks what it was trying to check. Fixes bug 10046;
21935 bugfix on 0.2.3.9-alpha. Found by "dcb".
21937 o Minor bugfixes (protocol correctness):
21938 - When receiving a VERSIONS cell with an odd number of bytes, close
21939 the connection immediately since the cell is malformed. Fixes bug
21940 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
21943 o Minor bugfixes (build):
21944 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
21945 turned off (that is, without support for v2 link handshakes). Fixes
21946 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
21947 - Fix compilation warnings and startup issues when running with
21948 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
21950 - Fix compilation on Solaris 9, which didn't like us having an
21951 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
21953 o Minor bugfixes (testing):
21954 - Fix a segmentation fault in our benchmark code when running with
21955 Fedora's OpenSSL package, or any other OpenSSL that provides
21956 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
21958 o Minor bugfixes (log messages):
21959 - Fix a bug where clients using bridges would report themselves
21960 as 50% bootstrapped even without a live consensus document.
21961 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
21962 - Suppress a warning where, if there's only one directory authority
21963 in the network, we would complain that votes and signatures cannot
21964 be uploaded to other directory authorities. Fixes bug 10842;
21965 bugfix on 0.2.2.26-beta.
21966 - Report bootstrapping progress correctly when we're downloading
21967 microdescriptors. We had updated our "do we have enough microdescs
21968 to begin building circuits?" logic most recently in 0.2.4.10-alpha
21969 (see bug 5956), but we left the bootstrap status event logic at
21970 "how far through getting 1/4 of them are we?" Fixes bug 9958;
21971 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
21973 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
21974 - Avoid a crash bug when starting with a corrupted microdescriptor
21975 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
21976 - If we fail to dump a previously cached microdescriptor to disk, avoid
21977 freeing duplicate data later on. Fixes bug 10423; bugfix on
21978 0.2.4.13-alpha. Spotted by "bobnomnom".
21980 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
21981 - Correctly log long IPv6 exit policies, instead of truncating them
21982 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
21983 - Our default TLS ecdhe groups were backwards: we meant to be using
21984 P224 for relays (for performance win) and P256 for bridges (since
21985 it is more common in the wild). Instead we had it backwards. After
21986 reconsideration, we decided that the default should be P256 on all
21987 hosts, since its security is probably better, and since P224 is
21988 reportedly used quite little in the wild. Found by "skruffy" on
21989 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
21990 - Free directory authority certificate download statuses on exit
21991 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
21993 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
21994 - If the guard we choose first doesn't answer, we would try the
21995 second guard, but once we connected to the second guard we would
21996 abandon it and retry the first one, slowing down bootstrapping.
21997 The fix is to treat all our initially chosen guards as acceptable
21998 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
21999 - Fix an assertion failure that would occur when disabling the
22000 ORPort setting on a running Tor process while accounting was
22001 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
22002 - When examining the list of network interfaces to find our address,
22003 do not consider non-running or disabled network interfaces. Fixes
22004 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
22005 - Avoid an off-by-one error when checking buffer boundaries when
22006 formatting the exit status of a pluggable transport helper.
22007 This is probably not an exploitable bug, but better safe than
22008 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
22011 o Removed code and features:
22012 - Clients now reject any directory authority certificates lacking
22013 a dir-key-crosscert element. These have been included since
22014 0.2.1.9-alpha, so there's no real reason for them to be optional
22015 any longer. Completes proposal 157. Resolves ticket 10162.
22016 - Remove all code that existed to support the v2 directory system,
22017 since there are no longer any v2 directory authorities. Resolves
22019 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
22020 options, which were used for designating authorities as "Hidden
22021 service authorities". There has been no use of hidden service
22022 authorities since 0.2.2.1-alpha, when we stopped uploading or
22023 downloading v0 hidden service descriptors. Fixes bug 10881; also
22024 part of a fix for bug 10841.
22026 o Code simplification and refactoring:
22027 - Remove some old fallback code designed to keep Tor clients working
22028 in a network with only two working relays. Elsewhere in the code we
22029 have long since stopped supporting such networks, so there wasn't
22030 much point in keeping it around. Addresses ticket 9926.
22031 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
22032 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
22033 - Remove data structures which were introduced to implement the
22034 CellStatistics option: they are now redundant with the addition
22035 of a timestamp to the regular packed_cell_t data structure, which
22036 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
22039 o Documentation (man page) fixes:
22040 - Update manpage to describe some of the files you can expect to
22041 find in Tor's DataDirectory. Addresses ticket 9839.
22042 - Document that all but one DirPort entry must have the NoAdvertise
22043 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
22045 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
22046 - Clarify the usage and risks of setting the ContactInfo torrc line
22047 for your relay or bridge. Resolves ticket 9854.
22048 - Add anchors to the manpage so we can link to the html version of
22049 the documentation for specific options. Resolves ticket 9866.
22050 - Replace remaining references to DirServer in man page and
22051 log entries. Resolves ticket 10124.
22054 - Make the "tor-gencert" tool used by directory authority operators
22055 create 2048-bit signing keys by default (rather than 1024-bit, since
22056 1024-bit is uncomfortably small these days). Addresses ticket 10324.
22059 Changes in version 0.2.4.20 - 2013-12-22
22060 Tor 0.2.4.20 fixes potentially poor random number generation for users
22061 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
22062 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
22063 and 4) have no state file in their DataDirectory (as would happen on
22064 first start). Users who generated relay or hidden service identity
22065 keys in such a situation should discard them and generate new ones.
22067 This release also fixes a logic error that caused Tor clients to build
22068 many more preemptive circuits than they actually need.
22071 - Do not allow OpenSSL engines to replace the PRNG, even when
22072 HardwareAccel is set. The only default builtin PRNG engine uses
22073 the Intel RDRAND instruction to replace the entire PRNG, and
22074 ignores all attempts to seed it with more entropy. That's
22075 cryptographically stupid: the right response to a new alleged
22076 entropy source is never to discard all previously used entropy
22077 sources. Fixes bug 10402; works around behavior introduced in
22078 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
22080 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
22081 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
22082 - Avoid launching spurious extra circuits when a stream is pending.
22083 This fixes a bug where any circuit that _wasn't_ unusable for new
22084 streams would be treated as if it were, causing extra circuits to
22085 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
22088 - Avoid a crash bug when starting with a corrupted microdescriptor
22089 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
22090 - If we fail to dump a previously cached microdescriptor to disk, avoid
22091 freeing duplicate data later on. Fixes bug 10423; bugfix on
22092 0.2.4.13-alpha. Spotted by "bobnomnom".
22095 Changes in version 0.2.4.19 - 2013-12-11
22096 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
22097 (1986-2013). Aaron worked on diverse projects including helping to guide
22098 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
22099 transparency to the U.S government's PACER documents, and contributing
22100 design and development for Tor and Tor2Web. Aaron was one of the latest
22101 martyrs in our collective fight for civil liberties and human rights,
22102 and his death is all the more painful because he was one of us.
22104 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
22105 a new circuit handshake and link encryption that use ECC to provide
22106 better security and efficiency; makes relays better manage circuit
22107 creation requests; uses "directory guards" to reduce client enumeration
22108 risks; makes bridges collect and report statistics about the pluggable
22109 transports they support; cleans up and improves our geoip database;
22110 gets much closer to IPv6 support for clients, bridges, and relays; makes
22111 directory authorities use measured bandwidths rather than advertised
22112 ones when computing flags and thresholds; disables client-side DNS
22113 caching to reduce tracking risks; and fixes a big bug in bridge
22114 reachability testing. This release introduces two new design
22115 abstractions in the code: a new "channel" abstraction between circuits
22116 and or_connections to allow for implementing alternate relay-to-relay
22117 transports, and a new "circuitmux" abstraction storing the queue of
22118 circuits for a channel. The release also includes many stability,
22119 security, and privacy fixes.
22122 Changes in version 0.2.4.18-rc - 2013-11-16
22123 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
22124 series. It takes a variety of fixes from the 0.2.5.x branch to improve
22125 stability, performance, and better handling of edge cases.
22128 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
22129 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
22130 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
22131 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
22132 them to solve bug 6033.)
22135 - No longer stop reading or writing on cpuworker connections when
22136 our rate limiting buckets go empty. Now we should handle circuit
22137 handshake requests more promptly. Resolves bug 9731.
22138 - If we are unable to save a microdescriptor to the journal, do not
22139 drop it from memory and then reattempt downloading it. Fixes bug
22140 9645; bugfix on 0.2.2.6-alpha.
22141 - Stop trying to bootstrap all our directory information from
22142 only our first guard. Discovered while fixing bug 9946; bugfix
22144 - The new channel code sometimes lost track of in-progress circuits,
22145 causing long-running clients to stop building new circuits. The
22146 fix is to always call circuit_n_chan_done(chan, 0) from
22147 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
22149 o Minor bugfixes (on 0.2.4.x):
22150 - Correctly log long IPv6 exit policies, instead of truncating them
22151 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
22152 - Our default TLS ecdhe groups were backwards: we meant to be using
22153 P224 for relays (for performance win) and P256 for bridges (since
22154 it is more common in the wild). Instead we had it backwards. After
22155 reconsideration, we decided that the default should be P256 on all
22156 hosts, since its security is probably better, and since P224 is
22157 reportedly used quite little in the wild. Found by "skruffy" on
22158 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
22159 - Free directory authority certificate download statuses on exit
22160 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
22162 o Minor bugfixes (on 0.2.3.x and earlier):
22163 - If the guard we choose first doesn't answer, we would try the
22164 second guard, but once we connected to the second guard we would
22165 abandon it and retry the first one, slowing down bootstrapping.
22166 The fix is to treat all our initially chosen guards as acceptable
22167 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
22168 - Fix an assertion failure that would occur when disabling the
22169 ORPort setting on a running Tor process while accounting was
22170 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
22171 - When examining the list of network interfaces to find our address,
22172 do not consider non-running or disabled network interfaces. Fixes
22173 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
22174 - Avoid an off-by-one error when checking buffer boundaries when
22175 formatting the exit status of a pluggable transport helper.
22176 This is probably not an exploitable bug, but better safe than
22177 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
22180 o Minor features (protecting client timestamps):
22181 - Clients no longer send timestamps in their NETINFO cells. These were
22182 not used for anything, and they provided one small way for clients
22183 to be distinguished from each other as they moved from network to
22184 network or behind NAT. Implements part of proposal 222.
22185 - Clients now round timestamps in INTRODUCE cells down to the nearest
22186 10 minutes. If a new Support022HiddenServices option is set to 0, or
22187 if it's set to "auto" and the feature is disabled in the consensus,
22188 the timestamp is sent as 0 instead. Implements part of proposal 222.
22189 - Stop sending timestamps in AUTHENTICATE cells. This is not such
22190 a big deal from a security point of view, but it achieves no actual
22191 good purpose, and isn't needed. Implements part of proposal 222.
22192 - Reduce down accuracy of timestamps in hidden service descriptors.
22193 Implements part of proposal 222.
22195 o Minor features (other):
22196 - Improve the circuit queue out-of-memory handler. Previously, when
22197 we ran low on memory, we'd close whichever circuits had the most
22198 queued cells. Now, we close those that have the *oldest* queued
22199 cells, on the theory that those are most responsible for us
22200 running low on memory. Based on analysis from a forthcoming paper
22201 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
22202 - Generate bootstrapping status update events correctly when fetching
22203 microdescriptors. Fixes bug 9927.
22204 - Update to the October 2 2013 Maxmind GeoLite Country database.
22206 o Documentation fixes:
22207 - Clarify the usage and risks of setting the ContactInfo torrc line
22208 for your relay or bridge. Resolves ticket 9854.
22209 - Add anchors to the manpage so we can link to the html version of
22210 the documentation for specific options. Resolves ticket 9866.
22211 - Replace remaining references to DirServer in man page and
22212 log entries. Resolves ticket 10124.
22215 Changes in version 0.2.5.1-alpha - 2013-10-02
22216 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
22217 on Linux, allows bridges that offer pluggable transports to report usage
22218 statistics, fixes many issues to make testing easier, and provides
22219 a pile of minor features and bugfixes that have been waiting for a
22220 release of the new branch.
22222 This is the first alpha release in a new series, so expect there to
22223 be bugs. Users who would rather test out a more stable branch should
22224 stay with 0.2.4.x for now.
22226 o Major features (security):
22227 - Use the seccomp2 syscall filtering facility on Linux to limit
22228 which system calls Tor can invoke. This is an experimental,
22229 Linux-only feature to provide defense-in-depth against unknown
22230 attacks. To try turning it on, set "Sandbox 1" in your torrc
22231 file. Please be ready to report bugs. We hope to add support
22232 for better sandboxing in the future, including more fine-grained
22233 filters, better division of responsibility, and support for more
22234 platforms. This work has been done by Cristian-Matei Toader for
22235 Google Summer of Code.
22236 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
22237 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
22238 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
22239 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
22240 them to solve bug 6033.)
22242 o Major features (other):
22243 - Add support for passing arguments to managed pluggable transport
22244 proxies. Implements ticket 3594.
22245 - Bridges now track GeoIP information and the number of their users
22246 even when pluggable transports are in use, and report usage
22247 statistics in their extra-info descriptors. Resolves tickets 4773
22249 - Make testing Tor networks bootstrap better: lower directory fetch
22250 retry schedules and maximum interval without directory requests,
22251 and raise maximum download tries. Implements ticket 6752.
22252 - Add make target 'test-network' to run tests on a Chutney network.
22253 Implements ticket 8530.
22254 - The ntor handshake is now on-by-default, no matter what the
22255 directory authorities recommend. Implements ticket 8561.
22258 - Instead of writing destroy cells directly to outgoing connection
22259 buffers, queue them and intersperse them with other outgoing cells.
22260 This can prevent a set of resource starvation conditions where too
22261 many pending destroy cells prevent data cells from actually getting
22262 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
22263 bugfix on 0.2.0.1-alpha.
22264 - If we are unable to save a microdescriptor to the journal, do not
22265 drop it from memory and then reattempt downloading it. Fixes bug
22266 9645; bugfix on 0.2.2.6-alpha.
22267 - The new channel code sometimes lost track of in-progress circuits,
22268 causing long-running clients to stop building new circuits. The
22269 fix is to always call circuit_n_chan_done(chan, 0) from
22270 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
22273 - Tor now builds each source file in two modes: a mode that avoids
22274 exposing identifiers needlessly, and another mode that exposes
22275 more identifiers for testing. This lets the compiler do better at
22276 optimizing the production code, while enabling us to take more
22277 radical measures to let the unit tests test things.
22278 - The production builds no longer include functions used only in
22279 the unit tests; all functions exposed from a module only for
22280 unit-testing are now static in production builds.
22281 - Add an --enable-coverage configuration option to make the unit
22282 tests (and a new src/or/tor-cov target) to build with gcov test
22286 - We now have rudimentary function mocking support that our unit
22287 tests can use to test functions in isolation. Function mocking
22288 lets the tests temporarily replace a function's dependencies with
22289 stub functions, so that the tests can check the function without
22290 invoking the other functions it calls.
22291 - Add more unit tests for the <circid,channel>->circuit map, and
22292 the destroy-cell-tracking code to fix bug 7912.
22293 - Unit tests for failing cases of the TAP onion handshake.
22294 - More unit tests for address-manipulation functions.
22296 o Minor features (protecting client timestamps):
22297 - Clients no longer send timestamps in their NETINFO cells. These were
22298 not used for anything, and they provided one small way for clients
22299 to be distinguished from each other as they moved from network to
22300 network or behind NAT. Implements part of proposal 222.
22301 - Clients now round timestamps in INTRODUCE cells down to the nearest
22302 10 minutes. If a new Support022HiddenServices option is set to 0, or
22303 if it's set to "auto" and the feature is disabled in the consensus,
22304 the timestamp is sent as 0 instead. Implements part of proposal 222.
22305 - Stop sending timestamps in AUTHENTICATE cells. This is not such
22306 a big deal from a security point of view, but it achieves no actual
22307 good purpose, and isn't needed. Implements part of proposal 222.
22308 - Reduce down accuracy of timestamps in hidden service descriptors.
22309 Implements part of proposal 222.
22311 o Minor features (config options):
22312 - Config (torrc) lines now handle fingerprints which are missing
22313 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
22314 - Support a --dump-config option to print some or all of the
22315 configured options. Mainly useful for debugging the command-line
22316 option parsing code. Helps resolve ticket 4647.
22317 - Raise awareness of safer logging: notify user of potentially
22318 unsafe config options, like logging more verbosely than severity
22319 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
22320 - Add a new configuration option TestingV3AuthVotingStartOffset
22321 that bootstraps a network faster by changing the timing for
22322 consensus votes. Addresses ticket 8532.
22323 - Add a new torrc option "ServerTransportOptions" that allows
22324 bridge operators to pass configuration parameters to their
22325 pluggable transports. Resolves ticket 8929.
22326 - The config (torrc) file now accepts bandwidth and space limits in
22327 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
22328 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
22331 o Minor features (build):
22332 - Add support for `--library-versions` flag. Implements ticket 6384.
22333 - Return the "unexpected sendme" warnings to a warn severity, but make
22334 them rate limited, to help diagnose ticket 8093.
22335 - Detect a missing asciidoc, and warn the user about it, during
22336 configure rather than at build time. Fixes issue 6506. Patch from
22339 o Minor features (other):
22340 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
22341 sockets in a single system call. Implements ticket 5129.
22342 - Log current accounting state (bytes sent and received + remaining
22343 time for the current accounting period) in the relay's heartbeat
22344 message. Implements ticket 5526; patch from Peter Retzlaff.
22345 - Implement the TRANSPORT_LAUNCHED control port event that
22346 notifies controllers about new launched pluggable
22347 transports. Resolves ticket 5609.
22348 - If we're using the pure-C 32-bit curve25519_donna implementation
22349 of curve25519, build it with the -fomit-frame-pointer option to
22350 make it go faster on register-starved hosts. This improves our
22351 handshake performance by about 6% on i386 hosts without nacl.
22352 Closes ticket 8109.
22353 - Update to the September 4 2013 Maxmind GeoLite Country database.
22356 - Set the listen() backlog limit to the largest actually supported
22357 on the system, not to the value in a header file. Fixes bug 9716;
22358 bugfix on every released Tor.
22359 - No longer accept malformed http headers when parsing urls from
22360 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
22361 bugfix on 0.0.6pre1.
22362 - In munge_extrainfo_into_routerinfo(), check the return value of
22363 memchr(). This would have been a serious issue if we ever passed
22364 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
22366 - On the chance that somebody manages to build Tor on a
22367 platform where time_t is unsigned, correct the way that
22368 microdesc_add_to_cache() handles negative time arguments.
22369 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
22370 - Reject relative control socket paths and emit a warning. Previously,
22371 single-component control socket paths would be rejected, but Tor
22372 would not log why it could not validate the config. Fixes bug 9258;
22373 bugfix on 0.2.3.16-alpha.
22375 o Minor bugfixes (command line):
22376 - Use a single command-line parser for parsing torrc options on the
22377 command line and for finding special command-line options to avoid
22378 inconsistent behavior for torrc option arguments that have the same
22379 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
22381 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
22382 9573; bugfix on 0.0.9pre5.
22384 o Minor fixes (build, auxiliary programs):
22385 - Stop preprocessing the "torify" script with autoconf, since
22386 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
22388 - The tor-fw-helper program now follows the standard convention and
22389 exits with status code "0" on success. Fixes bug 9030; bugfix on
22390 0.2.3.1-alpha. Patch by Arlo Breault.
22391 - Corrected ./configure advice for what openssl dev package you should
22392 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
22394 o Minor code improvements:
22395 - Remove constants and tests for PKCS1 padding; it's insecure and
22396 shouldn't be used for anything new. Fixes bug 8792; patch
22398 - Remove instances of strcpy() from the unit tests. They weren't
22399 hurting anything, since they were only in the unit tests, but it's
22400 embarrassing to have strcpy() in the code at all, and some analysis
22401 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
22402 0.2.3.8-alpha. Patch from Arlo Breault.
22404 o Removed features:
22405 - Remove migration code from when we renamed the "cached-routers"
22406 file to "cached-descriptors" back in 0.2.0.8-alpha. This
22407 incidentally resolves ticket 6502 by cleaning up the related code
22408 a bit. Patch from Akshay Hebbar.
22410 o Code simplification and refactoring:
22411 - Extract the common duplicated code for creating a subdirectory
22412 of the data directory and writing to a file in it. Fixes ticket
22413 4282; patch from Peter Retzlaff.
22414 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
22415 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
22416 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
22417 - Add a set of accessor functions for the circuit timeout data
22418 structure. Fixes ticket 6153; patch from "piet".
22419 - Clean up exit paths from connection_listener_new(). Closes ticket
22420 8789. Patch from Arlo Breault.
22421 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
22422 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
22423 - Use a doubly-linked list to implement the global circuit list.
22424 Resolves ticket 9108. Patch from Marek Majkowski.
22425 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
22428 Changes in version 0.2.4.17-rc - 2013-09-05
22429 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
22430 series. It adds an emergency step to help us tolerate the massive
22431 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
22432 circuit-level handshakes now effectively jump the queue compared to
22433 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
22434 big bug hindering bridge reachability tests.
22437 - Relays now process the new "NTor" circuit-level handshake requests
22438 with higher priority than the old "TAP" circuit-level handshake
22439 requests. We still process some TAP requests to not totally starve
22440 0.2.3 clients when NTor becomes popular. A new consensus parameter
22441 "NumNTorsPerTAP" lets us tune the balance later if we need to.
22442 Implements ticket 9574.
22445 - If the circuit build timeout logic is disabled (via the consensus,
22446 or because we are an authority), then don't build testing circuits.
22447 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
22448 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
22449 previously they did not, which prevented them from receiving
22450 successful connections from relays for self-test or bandwidth
22451 testing. Also, when a relay is extending a circuit to a bridge,
22452 it needs to send a NETINFO cell, even when the bridge hasn't sent
22453 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
22454 - If the time to download the next old-style networkstatus is in
22455 the future, do not decline to consider whether to download the
22456 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
22460 - Avoid double-closing the listener socket in our socketpair()
22461 replacement (used on Windows) in the case where the addresses on
22462 our opened sockets don't match what we expected. Fixes bug 9400;
22463 bugfix on 0.0.2pre7. Found by Coverity.
22465 o Minor fixes (config options):
22466 - Avoid overflows when the user sets MaxCircuitDirtiness to a
22467 ridiculously high value, by imposing a (ridiculously high) 30-day
22468 maximum on MaxCircuitDirtiness.
22469 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
22470 message is logged at notice, not at info.
22471 - Warn and fail if a server is configured not to advertise any
22472 ORPorts at all. (We need *something* to put in our descriptor,
22473 or we just won't work.)
22476 - Track how many "TAP" and "NTor" circuit handshake requests we get,
22477 and how many we complete, and log it every hour to help relay
22478 operators follow trends in network load. Addresses ticket 9658.
22479 - Update to the August 7 2013 Maxmind GeoLite Country database.
22482 Changes in version 0.2.4.16-rc - 2013-08-10
22483 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
22484 series. It fixes several crash bugs in the 0.2.4 branch.
22487 - Fix a bug in the voting algorithm that could yield incorrect results
22488 when a non-naming authority declared too many flags. Fixes bug 9200;
22489 bugfix on 0.2.0.3-alpha.
22490 - Fix an uninitialized read that could in some cases lead to a remote
22491 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
22492 Anybody running a hidden service on the experimental 0.2.4.x
22493 branch should upgrade. (This is, so far as we know, unrelated to
22495 - Avoid an assertion failure when processing DNS replies without the
22496 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
22497 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
22498 0.2.4.15-rc. Found by stem integration tests.
22501 - Fix an invalid memory read that occurred when a pluggable
22502 transport proxy failed its configuration protocol.
22503 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
22504 - When evaluating whether to use a connection that we haven't
22505 decided is canonical using a recent link protocol version,
22506 decide that it's canonical only if it used address _does_
22507 match the desired address. Fixes bug 9309; bugfix on
22508 0.2.4.4-alpha. Reported by skruffy.
22509 - Make the default behavior of NumDirectoryGuards be to track
22510 NumEntryGuards. Now a user who changes only NumEntryGuards will get
22511 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
22512 - Fix a spurious compilation warning with some older versions of
22513 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
22516 - Update to the July 3 2013 Maxmind GeoLite Country database.
22519 Changes in version 0.2.4.15-rc - 2013-07-01
22520 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
22521 series. It fixes a few smaller bugs, but generally appears stable.
22522 Please test it and let us know whether it is!
22525 - When receiving a new configuration file via the control port's
22526 LOADCONF command, do not treat the defaults file as absent.
22527 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
22530 - Issue a warning when running with the bufferevents backend enabled.
22531 It's still not stable, and people should know that they're likely
22532 to hit unexpected problems. Closes ticket 9147.
22535 Changes in version 0.2.4.14-alpha - 2013-06-18
22536 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
22537 present in 0.2.4.13-alpha.
22540 - When we have too much memory queued in circuits (according to a new
22541 MaxMemInCellQueues option), close the circuits consuming the most
22542 memory. This prevents us from running out of memory as a relay if
22543 circuits fill up faster than they can be drained. Fixes bug 9063;
22544 bugfix on the 54th commit of Tor. This bug is a further fix beyond
22545 bug 6252, whose fix was merged into 0.2.3.21-rc.
22547 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
22548 where we tried to solve this issue simply by imposing an upper limit
22549 on the number of queued cells for a single circuit. That approach
22550 proved to be problematic, since there are ways to provoke clients to
22551 send a number of cells in excess of any such reasonable limit. Fixes
22552 bug 9072; bugfix on 0.2.4.13-alpha.
22554 - Limit hidden service descriptors to at most ten introduction
22555 points, to slow one kind of guard enumeration. Fixes bug 9002;
22556 bugfix on 0.1.1.11-alpha.
22559 Changes in version 0.2.4.13-alpha - 2013-06-14
22560 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
22561 vulnerabilities, makes socks5 username/password circuit isolation
22562 actually actually work (this time for sure!), and cleans up a bunch
22563 of other issues in preparation for a release candidate.
22565 o Major bugfixes (robustness):
22566 - Close any circuit that has too many cells queued on it. Fixes
22567 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
22568 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
22569 - Prevent the get_freelists() function from running off the end of
22570 the list of freelists if it somehow gets an unrecognized
22571 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
22573 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
22574 when an exit connection with optimistic data succeeds immediately
22575 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
22577 - Fix a directory authority crash bug when building a consensus
22578 using an older consensus as its basis. Fixes bug 8833. Bugfix
22582 - Avoid a memory leak where we would leak a consensus body when we
22583 find that a consensus which we couldn't previously verify due to
22584 missing certificates is now verifiable. Fixes bug 8719; bugfix
22586 - We used to always request authority certificates by identity digest,
22587 meaning we'd get the newest one even when we wanted one with a
22588 different signing key. Then we would complain about being given
22589 a certificate we already had, and never get the one we really
22590 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
22591 resource to request the one we want. Fixes bug 5595; bugfix on
22593 - Follow the socks5 protocol when offering username/password
22594 authentication. The fix for bug 8117 exposed this bug, and it
22595 turns out real-world applications like Pidgin do care. Bugfix on
22596 0.2.3.2-alpha; fixes bug 8879.
22597 - Prevent failures on Windows Vista and later when rebuilding the
22598 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
22599 bugfix on 0.2.4.12-alpha.
22602 - Fix an impossible buffer overrun in the AES unit tests. Fixes
22603 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
22604 - If for some reason we fail to write a microdescriptor while
22605 rebuilding the cache, do not let the annotations from that
22606 microdescriptor linger in the cache file, and do not let the
22607 microdescriptor stay recorded as present in its old location.
22608 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
22609 - Fix a memory leak that would occur whenever a configuration
22610 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
22611 - Paste the description for PathBias parameters from the man
22612 page into or.h, so the code documents them too. Fixes bug 7982;
22613 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
22614 - Relays now treat a changed IPv6 ORPort as sufficient reason to
22615 publish an updated descriptor. Fixes bug 6026; bugfix on
22617 - When launching a resolve request on behalf of an AF_UNIX control
22618 socket, omit the address field of the new entry connection, used in
22619 subsequent controller events, rather than letting tor_dup_addr()
22620 set it to "<unknown address type>". Fixes bug 8639; bugfix on
22623 o Minor bugfixes (log messages):
22624 - Fix a scaling issue in the path bias accounting code that
22625 resulted in "Bug:" log messages from either
22626 pathbias_scale_close_rates() or pathbias_count_build_success().
22627 This represents a bugfix on a previous bugfix: the original fix
22628 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
22630 - Give a less useless error message when the user asks for an IPv4
22631 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
22635 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
22636 to tolerate bug 8093 for now.
22637 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
22638 in directory authority votes to describe whether they have enough
22639 measured bandwidths to ignore advertised (relay descriptor)
22640 bandwidth claims. Resolves ticket 8711.
22641 - Update to the June 5 2013 Maxmind GeoLite Country database.
22643 o Removed documentation:
22644 - Remove some of the older contents of doc/ as obsolete; move others
22645 to torspec.git. Fixes bug 8965.
22647 o Code simplification and refactoring:
22648 - Avoid using character buffers when constructing most directory
22649 objects: this approach was unwieldy and error-prone. Instead,
22650 build smartlists of strings, and concatenate them when done.
22653 Changes in version 0.2.4.12-alpha - 2013-04-18
22654 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
22655 process for lengthening the guard rotation period, makes directory
22656 authority opinions in the consensus a bit less gameable, makes socks5
22657 username/password circuit isolation actually work, and fixes a wide
22658 variety of other issues.
22661 - Raise the default time that a client keeps an entry guard from
22662 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
22663 2012 paper. (We would make it even longer, but we need better client
22664 load balancing first.) Also, make the guard lifetime controllable
22665 via a new GuardLifetime torrc option and a GuardLifetime consensus
22666 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
22667 - Directory authorities now prefer using measured bandwidths to
22668 advertised ones when computing flags and thresholds. Resolves
22670 - Directory authorities that have more than a threshold number
22671 of relays with measured bandwidths now treat relays with unmeasured
22672 bandwidths as having bandwidth 0. Resolves ticket 8435.
22674 o Major bugfixes (assert / resource use):
22675 - Avoid a bug where our response to TLS renegotiation under certain
22676 network conditions could lead to a busy-loop, with 100% CPU
22677 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
22678 - Avoid an assertion when we discover that we'd like to write a cell
22679 onto a closing connection: just discard the cell. Fixes another
22680 case of bug 7350; bugfix on 0.2.4.4-alpha.
22682 o Major bugfixes (client-side privacy):
22683 - When we mark a circuit as unusable for new circuits, have it
22684 continue to be unusable for new circuits even if MaxCircuitDirtiness
22685 is increased too much at the wrong time, or the system clock jumps
22686 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
22687 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
22688 which have resolved to internal addresses") is set, apply that
22689 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
22690 - When an exit relay rejects a stream with reason "exit policy", but
22691 we only know an exit policy summary (e.g. from the microdesc
22692 consensus) for it, do not mark the relay as useless for all exiting.
22693 Instead, mark just the circuit as unsuitable for that particular
22694 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
22695 - Allow applications to get proper stream isolation with
22696 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
22697 username/password authentication also offer "no authentication". Tor
22698 had previously preferred "no authentication", so the applications
22699 never actually sent Tor their auth details. Now Tor selects
22700 username/password authentication if it's offered. You can disable
22701 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
22702 bug 8117; bugfix on 0.2.3.3-alpha.
22704 o Major bugfixes (other):
22705 - When unable to find any working directory nodes to use as a
22706 directory guard, give up rather than adding the same non-working
22707 nodes to the directory guard list over and over. Fixes bug 8231;
22708 bugfix on 0.2.4.8-alpha.
22711 - Reject as invalid most directory objects containing a NUL.
22712 Belt-and-suspender fix for bug 8037.
22713 - In our testsuite, create temporary directories with a bit more
22714 entropy in their name to make name collisions less likely. Fixes
22716 - Add CACHED keyword to ADDRMAP events in the control protocol
22717 to indicate whether a DNS result will be cached or not. Resolves
22719 - Update to the April 3 2013 Maxmind GeoLite Country database.
22721 o Minor features (build):
22722 - Detect and reject attempts to build Tor with threading support
22723 when OpenSSL has been compiled without threading support.
22725 - Clarify that when autoconf is checking for nacl, it is checking
22726 specifically for nacl with a fast curve25519 implementation.
22728 - Warn if building on a platform with an unsigned time_t: there
22729 are too many places where Tor currently assumes that time_t can
22730 hold negative values. We'd like to fix them all, but probably
22733 o Minor bugfixes (build):
22734 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
22735 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
22736 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
22737 - Add the old src/or/micro-revision.i filename to CLEANFILES.
22738 On the off chance that somebody has one, it will go away as soon
22739 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
22740 - Build Tor correctly on 32-bit platforms where the compiler can build
22741 but not run code using the "uint128_t" construction. Fixes bug 8587;
22742 bugfix on 0.2.4.8-alpha.
22743 - Fix compilation warning with some versions of clang that would
22744 prefer the -Wswitch-enum compiler flag to warn about switch
22745 statements with missing enum values, even if those switch
22746 statements have a "default:" statement. Fixes bug 8598; bugfix
22749 o Minor bugfixes (protocol):
22750 - Fix the handling of a TRUNCATE cell when it arrives while the
22751 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
22752 - Fix a misframing issue when reading the version numbers in a
22753 VERSIONS cell. Previously we would recognize [00 01 00 02] as
22754 'version 1, version 2, and version 0x100', when it should have
22755 only included versions 1 and 2. Fixes bug 8059; bugfix on
22756 0.2.0.10-alpha. Reported pseudonymously.
22757 - Make the format and order of STREAM events for DNS lookups
22758 consistent among the various ways to launch DNS lookups. Fixes
22759 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
22760 - Correct our check for which versions of Tor support the EXTEND2
22761 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
22762 later, when support was really added in version 0.2.4.8-alpha.
22763 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
22765 o Minor bugfixes (other):
22766 - Correctly store microdescriptors and extrainfo descriptors with
22767 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
22768 Bug reported by "cypherpunks".
22769 - Increase the width of the field used to remember a connection's
22770 link protocol version to two bytes. Harmless for now, since the
22771 only currently recognized versions are one byte long. Reported
22772 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
22773 - If the state file's path bias counts are invalid (presumably from a
22774 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
22775 additional checks and log messages to the scaling of Path Bias
22776 counts, in case there still are remaining issues with scaling.
22777 Should help resolve bug 8235.
22778 - Eliminate several instances where we use "Nickname=ID" to refer to
22779 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
22780 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
22781 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
22783 o Minor bugfixes (syscalls):
22784 - Always check the return values of functions fcntl() and
22785 setsockopt(). We don't believe these are ever actually failing in
22786 practice, but better safe than sorry. Also, checking these return
22787 values should please analysis tools like Coverity. Patch from
22788 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
22789 - Use direct writes rather than stdio when building microdescriptor
22790 caches, in an attempt to mitigate bug 8031, or at least make it
22793 o Minor bugfixes (config):
22794 - When rejecting a configuration because we were unable to parse a
22795 quoted string, log an actual error message. Fixes bug 7950; bugfix
22797 - Behave correctly when the user disables LearnCircuitBuildTimeout
22798 but doesn't tell us what they would like the timeout to be. Fixes
22799 bug 6304; bugfix on 0.2.2.14-alpha.
22800 - When autodetecting the number of CPUs, use the number of available
22801 CPUs in preference to the number of configured CPUs. Inform the
22802 user if this reduces the number of available CPUs. Fixes bug 8002;
22803 bugfix on 0.2.3.1-alpha.
22804 - Make it an error when you set EntryNodes but disable UseGuardNodes,
22805 since it will (surprisingly to some users) ignore EntryNodes. Fixes
22806 bug 8180; bugfix on 0.2.3.11-alpha.
22807 - Allow TestingTorNetworks to override the 4096-byte minimum for
22808 the Fast threshold. Otherwise they can't bootstrap until they've
22809 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
22810 - Fix some logic errors when the user manually overrides the
22811 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
22814 o Minor bugfixes (log messages to help diagnose bugs):
22815 - If we fail to free a microdescriptor because of bug 7164, log
22816 the filename and line number from which we tried to free it.
22817 - Add another diagnostic to the heartbeat message: track and log
22818 overhead that TLS is adding to the data we write. If this is
22819 high, we are sending too little data to SSL_write at a time.
22820 Diagnostic for bug 7707.
22821 - Add more detail to a log message about relaxed timeouts, to help
22823 - Warn more aggressively when flushing microdescriptors to a
22824 microdescriptor cache fails, in an attempt to mitigate bug 8031,
22825 or at least make it more diagnosable.
22826 - Improve debugging output to help track down bug 8185 ("Bug:
22827 outgoing relay cell has n_chan==NULL. Dropping.")
22828 - Log the purpose of a path-bias testing circuit correctly.
22829 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
22831 o Minor bugfixes (0.2.4.x log messages that were too noisy):
22832 - Don't attempt to relax the timeout of already opened 1-hop circuits.
22833 They might never timeout. This should eliminate some/all cases of
22834 the relaxed timeout log message.
22835 - Use circuit creation time for network liveness evaluation. This
22836 should eliminate warning log messages about liveness caused
22837 by changes in timeout evaluation. Fixes bug 6572; bugfix on
22839 - Reduce a path bias length check from notice to info. The message
22840 is triggered when creating controller circuits. Fixes bug 8196;
22841 bugfix on 0.2.4.8-alpha.
22842 - Fix a path state issue that triggered a notice during relay startup.
22843 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
22844 - Reduce occurrences of warns about circuit purpose in
22845 connection_ap_expire_building(). Fixes bug 8477; bugfix on
22848 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
22849 - If we encounter a write failure on a SOCKS connection before we
22850 finish our SOCKS handshake, don't warn that we closed the
22851 connection before we could send a SOCKS reply. Fixes bug 8427;
22852 bugfix on 0.1.0.1-rc.
22853 - Correctly recognize that [::1] is a loopback address. Fixes
22854 bug 8377; bugfix on 0.2.1.3-alpha.
22855 - Fix a directory authority warn caused when we have a large amount
22856 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
22857 - Don't log inappropriate heartbeat messages when hibernating: a
22858 hibernating node is _expected_ to drop out of the consensus,
22859 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
22860 bugfix on 0.2.3.1-alpha.
22861 - Don't complain about bootstrapping problems while hibernating.
22862 These complaints reflect a general code problem, but not one
22863 with any problematic effects (no connections are actually
22864 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
22866 o Documentation fixes:
22867 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
22868 names match. Fixes bug 7768.
22869 - Make the torify manpage no longer refer to tsocks; torify hasn't
22870 supported tsocks since 0.2.3.14-alpha.
22871 - Make the tor manpage no longer reference tsocks.
22872 - Fix the GeoIPExcludeUnknown documentation to refer to
22873 ExcludeExitNodes rather than the currently nonexistent
22874 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
22877 - The tor-tsocks.conf is no longer distributed or installed. We
22878 recommend that tsocks users use torsocks instead. Resolves
22882 Changes in version 0.2.4.11-alpha - 2013-03-11
22883 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
22884 more robust, makes hidden service authentication work again, and
22885 resolves a DPI fingerprint for Tor's SSL transport.
22887 o Major features (directory authorities):
22888 - Directory authorities now support a new consensus method (17)
22889 where they cap the published bandwidth of servers for which
22890 insufficient bandwidth measurements exist. Fixes part of bug 2286.
22891 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
22892 serve any v2 directory information. Now we can test disabling the
22893 old deprecated v2 directory format, and see whether doing so has
22894 any effect on network load. Begins to fix bug 6783.
22895 - Directory authorities now include inside each vote a statement of
22896 the performance thresholds they used when assigning flags.
22897 Implements ticket 8151.
22899 o Major bugfixes (directory authorities):
22900 - Stop marking every relay as having been down for one hour every
22901 time we restart a directory authority. These artificial downtimes
22902 were messing with our Stable and Guard flag calculations. Fixes
22903 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
22905 o Major bugfixes (hidden services):
22906 - Allow hidden service authentication to succeed again. When we
22907 refactored the hidden service introduction code back
22908 in 0.2.4.1-alpha, we didn't update the code that checks
22909 whether authentication information is present, causing all
22910 authentication checks to return "false". Fix for bug 8207; bugfix
22911 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
22913 o Minor features (relays, bridges):
22914 - Make bridge relays check once a minute for whether their IP
22915 address has changed, rather than only every 15 minutes. Resolves
22916 bugs 1913 and 1992.
22917 - Refactor resolve_my_address() so it returns the method by which we
22918 decided our public IP address (explicitly configured, resolved from
22919 explicit hostname, guessed from interfaces, learned by gethostname).
22920 Now we can provide more helpful log messages when a relay guesses
22921 its IP address incorrectly (e.g. due to unexpected lines in
22922 /etc/hosts). Resolves ticket 2267.
22923 - Teach bridge-using clients to avoid 0.2.2 bridges when making
22924 microdescriptor-related dir requests, and only fall back to normal
22925 descriptors if none of their bridges can handle microdescriptors
22926 (as opposed to the fix in ticket 4013, which caused them to fall
22927 back to normal descriptors if *any* of their bridges preferred
22928 them). Resolves ticket 4994.
22929 - Randomize the lifetime of our SSL link certificate, so censors can't
22930 use the static value for filtering Tor flows. Resolves ticket 8443;
22931 related to ticket 4014 which was included in 0.2.2.33.
22932 - Support a new version of the link protocol that allows 4-byte circuit
22933 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
22934 a possible resource exhaustion issue. Closes ticket 7351; implements
22937 o Minor features (portability):
22938 - Tweak the curve25519-donna*.c implementations to tolerate systems
22939 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
22940 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
22941 the signs of types during autoconf. This is better than our old
22942 approach, which didn't work when cross-compiling.
22943 - Detect the sign of enum values, rather than assuming that MSC is the
22944 only compiler where enum types are all signed. Fixes bug 7727;
22945 bugfix on 0.2.4.10-alpha.
22947 o Minor features (other):
22948 - Say "KBytes" rather than "KB" in the man page (for various values
22949 of K), to further reduce confusion about whether Tor counts in
22950 units of memory or fractions of units of memory. Resolves ticket 7054.
22951 - Clear the high bit on curve25519 public keys before passing them to
22952 our backend, in case we ever wind up using a backend that doesn't do
22953 so itself. If we used such a backend, and *didn't* clear the high bit,
22954 we could wind up in a situation where users with such backends would
22955 be distinguishable from users without. Fixes bug 8121; bugfix on
22957 - Update to the March 6 2013 Maxmind GeoLite Country database.
22959 o Minor bugfixes (clients):
22960 - When we receive a RELAY_END cell with the reason DONE, or with no
22961 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
22962 status as "connection refused". Previously we reported these cases
22963 as success but then immediately closed the connection. Fixes bug
22964 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
22965 - Downgrade an assertion in connection_ap_expire_beginning to an
22966 LD_BUG message. The fix for bug 8024 should prevent this message
22967 from displaying, but just in case, a warn that we can diagnose
22968 is better than more assert crashes. Fixes bug 8065; bugfix on
22970 - Lower path use bias thresholds to .80 for notice and .60 for warn.
22971 Also make the rate limiting flags for the path use bias log messages
22972 independent from the original path bias flags. Fixes bug 8161;
22973 bugfix on 0.2.4.10-alpha.
22975 o Minor bugfixes (relays):
22976 - Stop trying to resolve our hostname so often (e.g. every time we
22977 think about doing a directory fetch). Now we reuse the cached
22978 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
22979 and 2410 (bugfix on 0.1.2.2-alpha).
22980 - Stop sending a stray "(null)" in some cases for the server status
22981 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
22983 - When choosing which stream on a formerly stalled circuit to wake
22984 first, make better use of the platform's weak RNG. Previously,
22985 we had been using the % ("modulo") operator to try to generate a
22986 1/N chance of picking each stream, but this behaves badly with
22987 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
22989 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
22990 Irix's random() only return 15 bits; Solaris's random() returns more
22991 bits but its RAND_MAX says it only returns 15, and so on. Motivated
22992 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
22994 o Minor bugfixes (directory authorities):
22995 - Directory authorities now use less space when formatting identical
22996 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
22999 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
23000 - Avoid leaking memory if we fail to compute a consensus signature
23001 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
23002 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
23004 - Fix a memory leak during safe-cookie controller authentication.
23005 Bugfix on 0.2.3.13-alpha.
23006 - Avoid memory leak of IPv6 policy content if we fail to format it into
23007 a router descriptor. Bugfix on 0.2.4.7-alpha.
23009 o Minor bugfixes (other code correctness issues):
23010 - Avoid a crash if we fail to generate an extrainfo descriptor.
23011 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
23012 this is CID 718634.
23013 - When detecting the largest possible file descriptor (in order to
23014 close all file descriptors when launching a new program), actually
23015 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
23016 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
23018 - Fix a copy-and-paste error when adding a missing A1 to a routerset
23019 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
23020 Bugfix on 0.2.4.10-alpha.
23021 - Fix an impossible-to-trigger integer overflow when estimating how
23022 long our onionskin queue would take. (This overflow would require us
23023 to accept 4 million onionskins before processing 100 of them.) Fixes
23024 bug 8210; bugfix on 0.2.4.10-alpha.
23026 o Code simplification and refactoring:
23027 - Add a wrapper function for the common "log a message with a
23031 Changes in version 0.2.4.10-alpha - 2013-02-04
23032 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
23033 certain attacks that flood the network with relays; changes the queue
23034 for circuit create requests from a sized-based limit to a time-based
23035 limit; resumes building with MSVC on Windows; and fixes a wide variety
23038 o Major bugfixes (directory authority):
23039 - When computing directory thresholds, ignore any rejected-as-sybil
23040 nodes during the computation so that they can't influence Fast,
23041 Guard, etc. (We should have done this for proposal 109.) Fixes
23043 - When marking a node as a likely sybil, reset its uptime metrics
23044 to zero, so that it cannot time towards getting marked as Guard,
23045 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
23049 - When a TLS write is partially successful but incomplete, remember
23050 that the flushed part has been flushed, and notice that bytes were
23051 actually written. Reported and fixed pseudonymously. Fixes bug
23052 7708; bugfix on Tor 0.1.0.5-rc.
23053 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
23054 ID: these could be used to create unexpected streams and circuits
23055 which would count as "present" to some parts of Tor but "absent"
23056 to others, leading to zombie circuits and streams or to a bandwidth
23057 denial-of-service. Fixes bug 7889; bugfix on every released version
23058 of Tor. Reported by "oftc_must_be_destroyed".
23059 - Rename all macros in our local copy of queue.h to begin with "TOR_".
23060 This change seems the only good way to permanently prevent conflicts
23061 with queue.h on various operating systems. Fixes bug 8107; bugfix
23064 o Major features (relay):
23065 - Instead of limiting the number of queued onionskins (aka circuit
23066 create requests) to a fixed, hard-to-configure number, we limit
23067 the size of the queue based on how many we expect to be able to
23068 process in a given amount of time. We estimate the time it will
23069 take to process an onionskin based on average processing time
23070 of previous onionskins. Closes ticket 7291. You'll never have to
23071 configure MaxOnionsPending again.
23073 o Major features (portability):
23074 - Resume building correctly with MSVC and Makefile.nmake. This patch
23075 resolves numerous bugs and fixes reported by ultramage, including
23076 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
23077 - Make the ntor and curve25519 code build correctly with MSVC.
23078 Fix on 0.2.4.8-alpha.
23081 - When directory authorities are computing thresholds for flags,
23082 never let the threshold for the Fast flag fall below 4096
23083 bytes. Also, do not consider nodes with extremely low bandwidths
23084 when deciding thresholds for various directory flags. This change
23085 should raise our threshold for Fast relays, possibly in turn
23086 improving overall network performance; see ticket 1854. Resolves
23088 - The Tor client now ignores sub-domain components of a .onion
23089 address. This change makes HTTP "virtual" hosting
23090 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
23091 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
23092 hosted on the same hidden service. Implements proposal 204.
23093 - We compute the overhead from passing onionskins back and forth to
23094 cpuworkers, and report it when dumping statistics in response to
23095 SIGUSR1. Supports ticket 7291.
23097 o Minor features (path selection):
23098 - When deciding whether we have enough descriptors to build circuits,
23099 instead of looking at raw relay counts, look at which fraction
23100 of (bandwidth-weighted) paths we're able to build. This approach
23101 keeps clients from building circuits if their paths are likely to
23102 stand out statistically. The default fraction of paths needed is
23103 taken from the consensus directory; you can override it with the
23104 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
23105 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
23106 and we have GeoIP information, also exclude all nodes with unknown
23107 countries "??" and "A1". This behavior is controlled by the
23108 new GeoIPExcludeUnknown option: you can make such nodes always
23109 excluded with "GeoIPExcludeUnknown 1", and disable the feature
23110 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
23111 gets you the default behavior. Implements feature 7706.
23112 - Path Use Bias: Perform separate accounting for successful circuit
23113 use. Keep separate statistics on stream attempt rates versus stream
23114 success rates for each guard. Provide configurable thresholds to
23115 determine when to emit log messages or disable use of guards that
23116 fail too many stream attempts. Resolves ticket 7802.
23118 o Minor features (log messages):
23119 - When learning a fingerprint for a bridge, log its corresponding
23120 transport type. Implements ticket 7896.
23121 - Improve the log message when "Bug/attack: unexpected sendme cell
23122 from client" occurs, to help us track bug 8093.
23125 - Remove a couple of extraneous semicolons that were upsetting the
23126 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
23127 bugfix on 0.2.2.1-alpha.
23128 - Remove a source of rounding error during path bias count scaling;
23129 don't count cannibalized circuits as used for path bias until we
23130 actually try to use them; and fix a circuit_package_relay_cell()
23131 warning message about n_chan==NULL. Fixes bug 7802.
23132 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
23133 actually link against nacl when we're configured to use it. Fixes
23134 bug 7972; bugfix on 0.2.4.8-alpha.
23135 - Compile correctly with the --disable-curve25519 option. Fixes
23136 bug 8153; bugfix on 0.2.4.8-alpha.
23138 o Build improvements:
23139 - Do not report status verbosely from autogen.sh unless the -v flag
23140 is specified. Fixes issue 4664. Patch from Onizuka.
23141 - Replace all calls to snprintf() outside of src/ext with
23142 tor_snprintf(). Also remove the #define to replace snprintf with
23143 _snprintf on Windows; they have different semantics, and all of
23144 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
23145 - Try to detect if we are ever building on a platform where
23146 memset(...,0,...) does not set the value of a double to 0.0. Such
23147 platforms are permitted by the C standard, though in practice
23148 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
23149 currently support them, but it's better to detect them and fail
23150 than to perform erroneously.
23152 o Removed features:
23153 - Stop exporting estimates of v2 and v3 directory traffic shares
23154 in extrainfo documents. They were unneeded and sometimes inaccurate.
23155 Also stop exporting any v2 directory request statistics. Resolves
23157 - Drop support for detecting and warning about versions of Libevent
23158 before 1.3e. Nothing reasonable ships with them any longer;
23159 warning the user about them shouldn't be needed. Resolves ticket
23162 o Code simplifications and refactoring:
23163 - Rename "isin" functions to "contains", for grammar. Resolves
23165 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
23166 with the natural logarithm function from the system libm. Resolves
23170 Changes in version 0.2.4.9-alpha - 2013-01-15
23171 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
23172 work more robustly.
23175 - Fix backward compatibility logic when receiving an embedded ntor
23176 handshake tunneled in a CREATE cell. This clears up the "Bug:
23177 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
23181 Changes in version 0.2.4.8-alpha - 2013-01-14
23182 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
23183 risks, adds a new stronger and faster circuit handshake, and offers
23184 stronger and faster link encryption when both sides support it.
23187 - Preliminary support for directory guards (proposal 207): when
23188 possible, clients now use their entry guards for non-anonymous
23189 directory requests. This can help prevent client enumeration. Note
23190 that this behavior only works when we have a usable consensus
23191 directory, and when options about what to download are more or less
23192 standard. In the future we should re-bootstrap from our guards,
23193 rather than re-bootstrapping from the preconfigured list of
23194 directory sources that ships with Tor. Resolves ticket 6526.
23195 - Tor relays and clients now support a better CREATE/EXTEND cell
23196 format, allowing the sender to specify multiple address, identity,
23197 and handshake types. Implements Robert Ransom's proposal 200;
23198 closes ticket 7199.
23200 o Major features (new circuit handshake):
23201 - Tor now supports a new circuit extension handshake designed by Ian
23202 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
23203 circuit extension handshake, later called "TAP", was a bit slow
23204 (especially on the relay side), had a fragile security proof, and
23205 used weaker keys than we'd now prefer. The new circuit handshake
23206 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
23207 function, making it significantly more secure than the older
23208 handshake, and significantly faster. Tor can use one of two built-in
23209 pure-C curve25519-donna implementations by Adam Langley, or it
23210 can link against the "nacl" library for a tuned version if present.
23212 The built-in version is very fast for 64-bit systems when building
23213 with GCC. The built-in 32-bit version is still faster than the
23214 old TAP protocol, but using libnacl is better on most such hosts.
23216 Clients don't currently use this protocol by default, since
23217 comparatively few clients support it so far. To try it, set
23218 UseNTorHandshake to 1.
23220 Implements proposal 216; closes ticket 7202.
23222 o Major features (better link encryption):
23223 - Relays can now enable the ECDHE TLS ciphersuites when available
23224 and appropriate. These ciphersuites let us negotiate forward-secure
23225 TLS secret keys more safely and more efficiently than with our
23226 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
23227 public relays prefer the (faster) P224 group, and bridges prefer
23228 the (more common) P256 group; you can override this with the
23231 Enabling these ciphers was a little tricky, since for a long time,
23232 clients had been claiming to support them without actually doing
23233 so, in order to foil fingerprinting. But with the client-side
23234 implementation of proposal 198 in 0.2.3.17-beta, clients can now
23235 match the ciphers from recent Firefox versions *and* list the
23236 ciphers they actually mean, so relays can believe such clients
23237 when they advertise ECDHE support in their TLS ClientHello messages.
23239 This feature requires clients running 0.2.3.17-beta or later,
23240 and requires both sides to be running OpenSSL 1.0.0 or later
23241 with ECC support. OpenSSL 1.0.1, with the compile-time option
23242 "enable-ec_nistp_64_gcc_128", is highly recommended.
23244 Implements the relay side of proposal 198; closes ticket 7200.
23247 - Avoid crashing when, as a relay without IPv6-exit support, a
23248 client insists on getting an IPv6 address or nothing. Fixes bug
23249 7814; bugfix on 0.2.4.7-alpha.
23252 - Improve circuit build timeout handling for hidden services.
23253 In particular: adjust build timeouts more accurately depending
23254 upon the number of hop-RTTs that a particular circuit type
23255 undergoes. Additionally, launch intro circuits in parallel
23256 if they timeout, and take the first one to reply as valid.
23257 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
23258 separate error codes; or at least, don't break for that reason.
23259 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
23260 - Update to the January 2 2013 Maxmind GeoLite Country database.
23262 o Minor features (testing):
23263 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
23264 (P-256) Diffie-Hellman handshakes to src/or/bench.
23265 - Add benchmark functions to test onion handshake performance.
23267 o Minor features (path bias detection):
23268 - Alter the Path Bias log messages to be more descriptive in terms
23269 of reporting timeouts and other statistics.
23270 - Create three levels of Path Bias log messages, as opposed to just
23271 two. These are configurable via consensus as well as via the torrc
23272 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
23273 The default values are 0.70, 0.50, and 0.30 respectively.
23274 - Separate the log message levels from the decision to drop guards,
23275 which also is available via torrc option PathBiasDropGuards.
23276 PathBiasDropGuards still defaults to 0 (off).
23277 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
23278 in combination with PathBiasExtremeRate.
23279 - Increase the default values for PathBiasScaleThreshold and
23280 PathBiasCircThreshold from (200, 20) to (300, 150).
23281 - Add in circuit usage accounting to path bias. If we try to use a
23282 built circuit but fail for any reason, it counts as path bias.
23283 Certain classes of circuits where the adversary gets to pick your
23284 destination node are exempt from this accounting. Usage accounting
23285 can be specifically disabled via consensus parameter or torrc.
23286 - Convert all internal path bias state to double-precision floating
23287 point, to avoid roundoff error and other issues.
23288 - Only record path bias information for circuits that have completed
23289 *two* hops. Assuming end-to-end tagging is the attack vector, this
23290 makes us more resilient to ambient circuit failure without any
23291 detection capability loss.
23293 o Minor bugfixes (log messages):
23294 - Rate-limit the "No circuits are opened. Relaxed timeout for a
23295 circuit with channel state open..." message to once per hour to
23296 keep it from filling the notice logs. Mitigates bug 7799 but does
23297 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
23298 - Avoid spurious warnings when configuring multiple client ports of
23299 which only some are nonlocal. Previously, we had claimed that some
23300 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
23303 o Code simplifications and refactoring:
23304 - Get rid of a couple of harmless clang warnings, where we compared
23305 enums to ints. These warnings are newly introduced in clang 3.2.
23306 - Split the onion.c file into separate modules for the onion queue
23307 and the different handshakes it supports.
23308 - Remove the marshalling/unmarshalling code for sending requests to
23309 cpuworkers over a socket, and instead just send structs. The
23310 recipient will always be the same Tor binary as the sender, so
23311 any encoding is overkill.
23314 Changes in version 0.2.4.7-alpha - 2012-12-24
23315 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
23316 directory mirrors for more robust bootstrapping; fixes more issues where
23317 clients with changing network conditions refuse to make any circuits;
23318 adds initial support for exiting to IPv6 addresses; resumes being able
23319 to update our GeoIP database, and includes the geoip6 file this time;
23320 turns off the client-side DNS cache by default due to privacy risks;
23321 and fixes a variety of other issues.
23323 o Major features (client resilience):
23324 - Add a new "FallbackDir" torrc option to use when we can't use
23325 a directory mirror from the consensus (either because we lack a
23326 consensus, or because they're all down). Currently, all authorities
23327 are fallbacks by default, and there are no other default fallbacks,
23328 but that will change. This option will allow us to give clients a
23329 longer list of servers to try to get a consensus from when first
23330 connecting to the Tor network, and thereby reduce load on the
23331 directory authorities. Implements proposal 206, "Preconfigured
23332 directory sources for bootstrapping". We also removed the old
23333 "FallbackNetworkstatus" option, since we never got it working well
23334 enough to use it. Closes bug 572.
23335 - If we have no circuits open, use a relaxed timeout (the
23336 95-percentile cutoff) until a circuit succeeds. This heuristic
23337 should allow Tor to succeed at building circuits even when the
23338 network connection drastically changes. Should help with bug 3443.
23340 o Major features (IPv6):
23341 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
23342 connectivity, then set the IPv6Exit flag to 1. Also make sure your
23343 exit policy reads as you would like: the address * applies to all
23344 address families, whereas *4 is IPv4 address only, and *6 is IPv6
23345 addresses only. On the client side, you'll need to wait until the
23346 authorities have upgraded, wait for enough exits to support IPv6,
23347 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
23348 ticket 5547, implements proposal 117 as revised in proposal 208.
23350 We DO NOT recommend that clients with actual anonymity needs start
23351 using IPv6 over Tor yet, since not enough exits support it yet.
23353 o Major features (geoip database):
23354 - Maxmind began labelling Tor relays as being in country "A1",
23355 which breaks by-country node selection inside Tor. Now we use a
23356 script to replace "A1" ("Anonymous Proxy") entries in our geoip
23357 file with real country codes. This script fixes about 90% of "A1"
23358 entries automatically and uses manual country code assignments to
23359 fix the remaining 10%. See src/config/README.geoip for details.
23360 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
23361 Country database, as modified above.
23363 o Major bugfixes (client-side DNS):
23364 - Turn off the client-side DNS cache by default. Updating and using
23365 the DNS cache is now configurable on a per-client-port
23366 level. SOCKSPort, DNSPort, etc lines may now contain
23367 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
23368 cache these types of DNS answers when we receive them from an
23369 exit node in response to an application request on this port, and
23370 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
23371 cached DNS answers of these types, we shouldn't use them. It's
23372 potentially risky to use cached DNS answers at the client, since
23373 doing so can indicate to one exit what answers we've gotten
23374 for DNS lookups in the past. With IPv6, this becomes especially
23375 problematic. Using cached DNS answers for requests on the same
23376 circuit would present less linkability risk, since all traffic
23377 on a circuit is already linkable, but it would also provide
23378 little performance benefit: the exit node caches DNS replies
23379 too. Implements a simplified version of Proposal 205. Implements
23382 o Major bugfixes (other):
23383 - Alter circuit build timeout measurement to start at the point
23384 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
23385 initialization). This should make our timeout measurements more
23386 uniform. Previously, we were sometimes including ORconn setup time
23387 in our circuit build time measurements. Should resolve bug 3443.
23388 - Fix an assertion that could trigger in hibernate_go_dormant() when
23389 closing an or_connection_t: call channel_mark_for_close() rather
23390 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
23392 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
23393 7655; bugfix on 0.2.4.6-alpha.
23396 - Add a new torrc option "ServerTransportListenAddr" to let bridge
23397 operators select the address where their pluggable transports will
23398 listen for connections. Resolves ticket 7013.
23399 - Allow an optional $ before the node identity digest in the
23400 controller command GETINFO ns/id/<identity>, for consistency with
23401 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
23402 - Log packaged cell fullness as part of the heartbeat message.
23403 Diagnosis to try to determine the extent of bug 7743.
23405 o Minor features (IPv6):
23406 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
23407 prefer to hand out virtual IPv6 addresses, since there are more of
23408 them and we can't run out. To override this behavior and make IPv4
23409 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
23410 or DNSPort you're using for resolving. Implements ticket 7571.
23411 - AutomapHostsOnResolve responses are now randomized, to avoid
23412 annoying situations where Tor is restarted and applications
23413 connect to the wrong addresses.
23414 - Never try more than 1000 times to pick a new virtual address when
23415 AutomapHostsOnResolve is set. That's good enough so long as we
23416 aren't close to handing out our entire virtual address space;
23417 if you're getting there, it's best to switch to IPv6 virtual
23421 - The ADDRMAP command can no longer generate an ill-formed error
23422 code on a failed MAPADDRESS. It now says "internal" rather than
23423 an English sentence fragment with spaces in the middle. Bugfix on
23424 Tor 0.2.0.19-alpha.
23425 - Fix log messages and comments to avoid saying "GMT" when we mean
23426 "UTC". Fixes bug 6113.
23427 - Compile on win64 using mingw64. Fixes bug 7260; patches from
23429 - Fix a crash when debugging unit tests on Windows: deallocate a
23430 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
23431 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
23434 - The DirServer option is now DirAuthority, for consistency with
23435 current naming patterns. You can still use the old DirServer form.
23437 o Code simplification and refactoring:
23438 - Move the client-side address-map/virtual-address/DNS-cache code
23439 out of connection_edge.c into a new addressmap.c module.
23440 - Remove unused code for parsing v1 directories and "running routers"
23441 documents. Fixes bug 6887.
23444 Changes in version 0.2.3.25 - 2012-11-19
23445 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
23446 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
23447 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
23448 programmer, and friend. Unstinting in his dedication to the cause of
23449 freedom, he inspired and helped many of us as we began our work on
23450 anonymity, and inspires us still. Please honor his memory by writing
23451 software to protect people's freedoms, and by helping others to do so.
23453 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
23454 significantly reduced directory overhead (via microdescriptors),
23455 enormous crypto performance improvements for fast relays on new
23456 enough hardware, a new v3 TLS handshake protocol that can better
23457 resist fingerprinting, support for protocol obfuscation plugins (aka
23458 pluggable transports), better scalability for hidden services, IPv6
23459 support for bridges, performance improvements like allowing clients
23460 to skip the first round-trip on the circuit ("optimistic data") and
23461 refilling token buckets more often, a new "stream isolation" design
23462 to isolate different applications on different circuits, and many
23463 stability, security, and privacy fixes.
23466 - Tor tries to wipe potentially sensitive data after using it, so
23467 that if some subsequent security failure exposes Tor's memory,
23468 the damage will be limited. But we had a bug where the compiler
23469 was eliminating these wipe operations when it decided that the
23470 memory was no longer visible to a (correctly running) program,
23471 hence defeating our attempt at defense in depth. We fix that
23472 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
23473 is unlikely to optimize away. Future versions of Tor may use
23474 a less ridiculously heavy approach for this. Fixes bug 7352.
23475 Reported in an article by Andrey Karpov.
23478 - Fix a harmless bug when opting against publishing a relay descriptor
23479 because DisableNetwork is set. Fixes bug 7464; bugfix on
23483 Changes in version 0.2.4.6-alpha - 2012-11-13
23484 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
23485 makes our defense-in-depth memory wiping more reliable, and begins to
23486 count IPv6 addresses in bridge statistics,
23489 - Fix an assertion failure that could occur when closing a connection
23490 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
23492 - Tor tries to wipe potentially sensitive data after using it, so
23493 that if some subsequent security failure exposes Tor's memory,
23494 the damage will be limited. But we had a bug where the compiler
23495 was eliminating these wipe operations when it decided that the
23496 memory was no longer visible to a (correctly running) program,
23497 hence defeating our attempt at defense in depth. We fix that
23498 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
23499 is unlikely to optimize away. Future versions of Tor may use
23500 a less ridiculously heavy approach for this. Fixes bug 7352.
23501 Reported in an article by Andrey Karpov.
23504 - Add GeoIP database for IPv6 addresses. The new config option
23506 - Bridge statistics now count bridge clients connecting over IPv6:
23507 bridge statistics files now list "bridge-ip-versions" and
23508 extra-info documents list "geoip6-db-digest". The control protocol
23509 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
23510 implementation by "shkoo", addressing ticket 5055.
23513 - Warn when we are binding low ports when hibernation is enabled;
23514 previously we had warned when we were _advertising_ low ports with
23515 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
23516 - Fix a harmless bug when opting against publishing a relay descriptor
23517 because DisableNetwork is set. Fixes bug 7464; bugfix on
23519 - Add warning message when a managed proxy dies during configuration.
23520 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
23521 - Fix a linking error when building tor-fw-helper without miniupnp.
23522 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
23523 - Check for closing an or_connection_t without going through correct
23524 channel functions; emit a warning and then call
23525 connection_or_close_for_error() so we don't assert as in bugs 7212
23527 - Compile correctly on compilers without C99 designated initializer
23528 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
23529 - Avoid a possible assert that can occur when channel_send_destroy() is
23530 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
23531 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
23532 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
23533 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
23534 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
23536 o Code simplification and refactoring:
23537 - Start using OpenBSD's implementation of queue.h, so that we don't
23538 need to hand-roll our own pointer and list structures whenever we
23539 need them. (We can't rely on a sys/queue.h, since some operating
23540 systems don't have them, and the ones that do have them don't all
23541 present the same extensions.)
23544 Changes in version 0.2.4.5-alpha - 2012-10-25
23545 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
23546 two important security vulnerabilities that could lead to remotely
23547 triggerable relay crashes, fix a major bug that was preventing clients
23548 from choosing suitable exit nodes, and refactor some of our code.
23550 o Major bugfixes (security, also in 0.2.3.24-rc):
23551 - Fix a group of remotely triggerable assertion failures related to
23552 incorrect link protocol negotiation. Found, diagnosed, and fixed
23553 by "some guy from France". Fix for CVE-2012-2250; bugfix on
23555 - Fix a denial of service attack by which any directory authority
23556 could crash all the others, or by which a single v2 directory
23557 authority could crash everybody downloading v2 directory
23558 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
23560 o Major bugfixes (also in 0.2.3.24-rc):
23561 - When parsing exit policy summaries from microdescriptors, we had
23562 previously been ignoring the last character in each one, so that
23563 "accept 80,443,8080" would be treated by clients as indicating
23564 a node that allows access to ports 80, 443, and 808. That would
23565 lead to clients attempting connections that could never work,
23566 and ignoring exit nodes that would support their connections. Now
23567 clients parse these exit policy summaries correctly. Fixes bug 7192;
23568 bugfix on 0.2.3.1-alpha.
23570 o Minor bugfixes (also in 0.2.3.24-rc):
23571 - Clients now consider the ClientRejectInternalAddresses config option
23572 when using a microdescriptor consensus stanza to decide whether
23573 an exit relay would allow exiting to an internal address. Fixes
23574 bug 7190; bugfix on 0.2.3.1-alpha.
23577 - Only disable TLS session ticket support when running as a TLS
23578 server. Now clients will blend better with regular Firefox
23579 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
23581 o Code simplification and refactoring:
23582 - Start using OpenBSD's implementation of queue.h (originally by
23584 - Move the entry node code from circuitbuild.c to its own file.
23585 - Move the circuit build timeout tracking code from circuitbuild.c
23589 Changes in version 0.2.3.24-rc - 2012-10-25
23590 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
23591 could lead to remotely triggerable relay crashes, and fixes
23592 a major bug that was preventing clients from choosing suitable exit
23595 o Major bugfixes (security):
23596 - Fix a group of remotely triggerable assertion failures related to
23597 incorrect link protocol negotiation. Found, diagnosed, and fixed
23598 by "some guy from France". Fix for CVE-2012-2250; bugfix on
23600 - Fix a denial of service attack by which any directory authority
23601 could crash all the others, or by which a single v2 directory
23602 authority could crash everybody downloading v2 directory
23603 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
23606 - When parsing exit policy summaries from microdescriptors, we had
23607 previously been ignoring the last character in each one, so that
23608 "accept 80,443,8080" would be treated by clients as indicating
23609 a node that allows access to ports 80, 443, and 808. That would
23610 lead to clients attempting connections that could never work,
23611 and ignoring exit nodes that would support their connections. Now
23612 clients parse these exit policy summaries correctly. Fixes bug 7192;
23613 bugfix on 0.2.3.1-alpha.
23616 - Clients now consider the ClientRejectInternalAddresses config option
23617 when using a microdescriptor consensus stanza to decide whether
23618 an exit relay would allow exiting to an internal address. Fixes
23619 bug 7190; bugfix on 0.2.3.1-alpha.
23622 Changes in version 0.2.4.4-alpha - 2012-10-20
23623 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
23624 vulnerability introduced by a change in OpenSSL, fixes a remotely
23625 triggerable assert, and adds new channel_t and circuitmux_t abstractions
23626 that will make it easier to test new connection transport and cell
23627 scheduling algorithms.
23629 o New directory authorities (also in 0.2.3.23-rc):
23630 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
23631 authority. Closes ticket 5749.
23633 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
23634 - Disable TLS session tickets. OpenSSL's implementation was giving
23635 our TLS session keys the lifetime of our TLS context objects, when
23636 perfect forward secrecy would want us to discard anything that
23637 could decrypt a link connection as soon as the link connection
23638 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
23639 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
23640 - Discard extraneous renegotiation attempts once the V3 link
23641 protocol has been initiated. Failure to do so left us open to
23642 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
23643 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
23645 o Internal abstraction features:
23646 - Introduce new channel_t abstraction between circuits and
23647 or_connection_t to allow for implementing alternate OR-to-OR
23648 transports. A channel_t is an abstract object which can either be a
23649 cell-bearing channel, which is responsible for authenticating and
23650 handshaking with the remote OR and transmitting cells to and from
23651 it, or a listening channel, which spawns new cell-bearing channels
23652 at the request of remote ORs. Implements part of ticket 6465.
23653 - Also new is the channel_tls_t subclass of channel_t, adapting it
23654 to the existing or_connection_t code. The V2/V3 protocol handshaking
23655 code which formerly resided in command.c has been moved below the
23656 channel_t abstraction layer and may be found in channeltls.c now.
23657 Implements the rest of ticket 6465.
23658 - Introduce new circuitmux_t storing the queue of circuits for
23659 a channel; this encapsulates and abstracts the queue logic and
23660 circuit selection policy, and allows the latter to be overridden
23661 easily by switching out a policy object. The existing EWMA behavior
23662 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
23664 o Required libraries:
23665 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
23666 strongly recommended.
23669 - Warn users who run hidden services on a Tor client with
23670 UseEntryGuards disabled that their hidden services will be
23671 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
23672 attack which motivated Tor to support entry guards in the first
23673 place). Resolves ticket 6889.
23674 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
23675 dhill. Resolves ticket 6982.
23676 - Option OutboundBindAddress can be specified multiple times and
23677 accepts IPv6 addresses. Resolves ticket 6876.
23679 o Minor bugfixes (also in 0.2.3.23-rc):
23680 - Don't serve or accept v2 hidden service descriptors over a
23681 relay's DirPort. It's never correct to do so, and disabling it
23682 might make it more annoying to exploit any bugs that turn up in the
23683 descriptor-parsing code. Fixes bug 7149.
23684 - Fix two cases in src/or/transports.c where we were calling
23685 fmt_addr() twice in a parameter list. Bug found by David
23686 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
23687 - Fix memory leaks whenever we logged any message about the "path
23688 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
23689 - When relays refuse a "create" cell because their queue of pending
23690 create cells is too big (typically because their cpu can't keep up
23691 with the arrival rate), send back reason "resource limit" rather
23692 than reason "internal", so network measurement scripts can get a
23693 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
23696 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
23697 - Free some more still-in-use memory at exit, to make hunting for
23698 memory leaks easier. Resolves bug 7029.
23699 - When a Tor client gets a "truncated" relay cell, the first byte of
23700 its payload specifies why the circuit was truncated. We were
23701 ignoring this 'reason' byte when tearing down the circuit, resulting
23702 in the controller not being told why the circuit closed. Now we
23703 pass the reason from the truncated cell to the controller. Bugfix
23704 on 0.1.2.3-alpha; fixes bug 7039.
23705 - Downgrade "Failed to hand off onionskin" messages to "debug"
23706 severity, since they're typically redundant with the "Your computer
23707 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
23708 - Make clients running with IPv6 bridges connect over IPv6 again,
23709 even without setting new config options ClientUseIPv6 and
23710 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
23711 - Use square brackets around IPv6 addresses in numerous places
23712 that needed them, including log messages, HTTPS CONNECT proxy
23713 requests, TransportProxy statefile entries, and pluggable transport
23714 extra-info lines. Fixes bug 7011; patch by David Fifield.
23716 o Code refactoring and cleanup:
23717 - Source files taken from other packages now reside in src/ext;
23718 previously they were scattered around the rest of Tor.
23719 - Avoid use of reserved identifiers in our C code. The C standard
23720 doesn't like us declaring anything that starts with an
23721 underscore, so let's knock it off before we get in trouble. Fix
23722 for bug 1031; bugfix on the first Tor commit.
23725 Changes in version 0.2.3.23-rc - 2012-10-20
23726 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
23727 vulnerability introduced by a change in OpenSSL, and fixes a variety
23728 of smaller bugs in preparation for the release.
23730 o New directory authorities:
23731 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
23732 authority. Closes ticket 5749.
23734 o Major bugfixes (security/privacy):
23735 - Disable TLS session tickets. OpenSSL's implementation was giving
23736 our TLS session keys the lifetime of our TLS context objects, when
23737 perfect forward secrecy would want us to discard anything that
23738 could decrypt a link connection as soon as the link connection
23739 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
23740 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
23741 - Discard extraneous renegotiation attempts once the V3 link
23742 protocol has been initiated. Failure to do so left us open to
23743 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
23744 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
23747 - Fix a possible crash bug when checking for deactivated circuits
23748 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
23749 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
23751 o Minor bugfixes (on 0.2.3.x):
23752 - Fix two cases in src/or/transports.c where we were calling
23753 fmt_addr() twice in a parameter list. Bug found by David
23754 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
23755 - Convert an assert in the pathbias code to a log message. The assert
23756 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
23757 bugfix on 0.2.3.17-beta.
23758 - Fix memory leaks whenever we logged any message about the "path
23759 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
23761 o Minor bugfixes (on 0.2.2.x and earlier):
23762 - Don't serve or accept v2 hidden service descriptors over a relay's
23763 DirPort. It's never correct to do so, and disabling it might
23764 make it more annoying to exploit any bugs that turn up in the
23765 descriptor-parsing code. Fixes bug 7149.
23766 - When relays refuse a "create" cell because their queue of pending
23767 create cells is too big (typically because their cpu can't keep up
23768 with the arrival rate), send back reason "resource limit" rather
23769 than reason "internal", so network measurement scripts can get a
23770 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
23771 - Correct file sizes when reading binary files on Cygwin, to avoid
23772 a bug where Tor would fail to read its state file. Fixes bug 6844;
23773 bugfix on 0.1.2.7-alpha.
23774 - Avoid undefined behavior when parsing the list of supported
23775 rendezvous/introduction protocols in a hidden service descriptor.
23776 Previously, Tor would have confused (as-yet-unused) protocol version
23777 numbers greater than 32 with lower ones on many platforms. Fixes
23778 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
23780 o Documentation fixes:
23781 - Clarify that hidden services are TCP only. Fixes bug 6024.
23784 Changes in version 0.2.4.3-alpha - 2012-09-22
23785 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
23786 assertion, resumes letting relays test reachability of their DirPort,
23787 and cleans up a bunch of smaller bugs.
23790 - Fix an assertion failure in tor_timegm() that could be triggered
23791 by a badly formatted directory object. Bug found by fuzzing with
23792 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
23795 - Fix a possible crash bug when checking for deactivated circuits
23796 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
23797 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
23798 - Allow routers to detect that their own DirPorts are running. When
23799 we removed support for versions_supports_begindir, we also
23800 accidentally removed the mechanism we used to self-test our
23801 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
23802 bugfix on 0.2.4.2-alpha.
23804 o Security features:
23805 - Switch to a completely time-invariant approach for picking nodes
23806 weighted by bandwidth. Our old approach would run through the
23807 part of the loop after it had made its choice slightly slower
23808 than it ran through the part of the loop before it had made its
23809 choice. Addresses ticket 6538.
23810 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
23811 by tor2web clients allows hidden services to identify tor2web
23812 clients through their repeated selection of the same rendezvous
23813 and introduction point circuit endpoints (their guards). Resolves
23817 - Enable Tor to read configuration, state, and key information from
23818 a FIFO. Previously Tor would only read from files with a positive
23819 stat.st_size. Code from meejah; fixes bug 6044.
23822 - Correct file sizes when reading binary files on Cygwin, to avoid
23823 a bug where Tor would fail to read its state file. Fixes bug 6844;
23824 bugfix on 0.1.2.7-alpha.
23825 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
23826 bugfix on 0.2.0.3-alpha.
23827 - When complaining about a client port on a public address, log
23828 which address we're complaining about. Fixes bug 4020; bugfix on
23829 0.2.3.3-alpha. Patch by Tom Fitzhenry.
23830 - Convert an assert in the pathbias code to a log message. The assert
23831 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
23832 bugfix on 0.2.3.17-beta.
23833 - Our new buildsystem was overzealous about rebuilding manpages: it
23834 would rebuild them all whenever any one of them changed. Now our
23835 dependency checking should be correct. Fixes bug 6843; bugfix on
23837 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
23838 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
23839 - Correct log printout about which address family is preferred
23840 when connecting to a bridge with both an IPv4 and IPv6 OR port.
23841 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
23843 o Minor bugfixes (code cleanliness):
23844 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
23845 with large values. This situation was untriggered, but nevertheless
23846 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
23847 - Reject consensus votes with more than 64 known-flags. We aren't even
23848 close to that limit yet, and our code doesn't handle it correctly.
23849 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
23850 - Avoid undefined behavior when parsing the list of supported
23851 rendezvous/introduction protocols in a hidden service descriptor.
23852 Previously, Tor would have confused (as-yet-unused) protocol version
23853 numbers greater than 32 with lower ones on many platforms. Fixes
23854 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
23855 - Fix handling of rendezvous client authorization types over 8.
23856 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
23857 - Fix building with older versions of GCC (2.95, for one) that don't
23858 like preprocessor directives inside macro arguments. Found by
23859 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
23860 - Switch weighted node selection rule from using a list of doubles
23861 to using a list of int64_t. This change should make the process
23862 slightly easier to debug and maintain. Needed to finish ticket 6538.
23864 o Code simplification and refactoring:
23865 - Move the generic "config" code into a new file, and have "config.c"
23866 hold only torrc- and state-related code. Resolves ticket 6823.
23867 - Move the core of our "choose a weighted element at random" logic
23868 into its own function, and give it unit tests. Now the logic is
23869 testable, and a little less fragile too.
23870 - Removed the testing_since field of node_t, which hasn't been used
23871 for anything since 0.2.0.9-alpha.
23873 o Documentation fixes:
23874 - Clarify that hidden services are TCP only. Fixes bug 6024.
23875 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
23879 Changes in version 0.2.3.22-rc - 2012-09-11
23880 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
23884 - Fix an assertion failure in tor_timegm() that could be triggered
23885 by a badly formatted directory object. Bug found by fuzzing with
23886 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
23889 - Avoid segfault when starting up having run with an extremely old
23890 version of Tor and parsing its state file. Fixes bug 6801; bugfix
23894 Changes in version 0.2.2.39 - 2012-09-11
23895 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
23899 - Fix an assertion failure in tor_timegm() that could be triggered
23900 by a badly formatted directory object. Bug found by fuzzing with
23901 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
23902 - Do not crash when comparing an address with port value 0 to an
23903 address policy. This bug could have been used to cause a remote
23904 assertion failure by or against directory authorities, or to
23905 allow some applications to crash clients. Fixes bug 6690; bugfix
23909 Changes in version 0.2.4.2-alpha - 2012-09-10
23910 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
23911 raises the default rate limiting even more, and makes the bootstrapping
23912 log messages less noisy.
23915 - Automatically forward the TCP ports of pluggable transport
23916 proxies using tor-fw-helper if PortForwarding is enabled. Implements
23920 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
23921 to 1GB/1GB. The previous defaults were intended to be "basically
23922 infinite", but it turns out they're now limiting our 100mbit+
23923 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
23924 last time we raised it).
23927 - Detect when we're running with a version of OpenSSL other than the
23928 one we compiled with. This has occasionally given people hard-to-
23930 - Log fewer lines at level "notice" about our OpenSSL and Libevent
23931 versions and capabilities when everything is going right. Resolves
23932 part of ticket 6736.
23933 - Directory authorities no long accept descriptors for any version of
23934 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
23935 These versions are insecure, unsupported, or both. Implements
23939 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
23940 to start with a triple-underscore so the controller won't touch it.
23941 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
23942 - Avoid segfault when starting up having run with an extremely old
23943 version of Tor and parsing its state file. Fixes bug 6801; bugfix
23945 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
23946 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
23947 - Don't follow the NULL pointer if microdescriptor generation fails.
23948 (This does not appear to be triggerable, but it's best to be safe.)
23949 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
23950 - Fix mis-declared dependencies on src/common/crypto.c and
23951 src/or/tor_main.c that could break out-of-tree builds under some
23952 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
23953 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
23954 6778; bugfix on 0.2.4.1-alpha.
23955 - Fix a harmless (in this case) build warning for implicitly
23956 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
23958 o Removed features:
23959 - Now that all versions before 0.2.2.x are disallowed, we no longer
23960 need to work around their missing features. Thus we can remove a
23961 bunch of compatibility code.
23963 o Code refactoring:
23964 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
23965 TCP ports to forward. In the past it only accepted two ports:
23966 the ORPort and the DirPort.
23969 Changes in version 0.2.4.1-alpha - 2012-09-05
23970 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
23971 bridgedb; lets relays use IPv6 addresses and directory authorities
23972 advertise them; and switches to a cleaner build interface.
23974 This is the first alpha release in a new series, so expect there to
23975 be bugs. Users who would rather test out a more stable branch should
23976 stay with 0.2.3.x for now.
23978 o Major features (bridges):
23979 - Bridges now report the pluggable transports they support to the
23980 bridge authority, so it can pass the supported transports on to
23981 bridgedb and/or eventually do reachability testing. Implements
23984 o Major features (IPv6):
23985 - Bridge authorities now accept IPv6 bridge addresses and include
23986 them in network status documents. Implements ticket 5534.
23987 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
23988 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
23989 to happen. Implements ticket 5535.
23990 - All kind of relays, not just bridges, can now advertise an IPv6
23991 OR port. Implements ticket 6362.
23992 - Directory authorities vote on IPv6 OR ports using the new consensus
23993 method 14. Implements ticket 6363.
23995 o Major features (build):
23996 - Switch to a nonrecursive Makefile structure. Now instead of each
23997 Makefile.am invoking other Makefile.am's, there is a master
23998 Makefile.am that includes the others. This change makes our build
23999 process slightly more maintainable, and improves parallelism for
24000 building with make -j. Original patch by Stewart Smith; various
24001 fixes by Jim Meyering.
24002 - Where available, we now use automake's "silent" make rules by
24003 default, so that warnings are easier to spot. You can get the old
24004 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
24006 o Minor features (code security and spec conformance):
24007 - Clear keys and key-derived material left on the stack in
24008 rendservice.c and rendclient.c. Check return value of
24009 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
24010 These fixes should make us more forward-secure against cold-boot
24011 attacks and the like. Fixes bug 2385.
24012 - Reject EXTEND cells sent to nonexistent streams. According to the
24013 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
24014 we were only checking for stream IDs that were currently in use.
24015 Found while hunting for more instances of bug 6271. Bugfix on
24016 0.0.2pre8, which introduced incremental circuit construction.
24018 o Minor features (streamlining);
24019 - No longer include the "opt" prefix when generating routerinfos
24020 or v2 directories: it has been needless since Tor 0.1.2. Closes
24022 - Remove some now-needless code that tried to aggressively flush
24023 OR connections as data was added to them. Since 0.2.0.1-alpha, our
24024 cell queue logic has saved us from the failure mode that this code
24025 was supposed to prevent. Removing this code will limit the number
24026 of baroque control flow paths through Tor's network logic. Reported
24027 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
24029 o Minor features (controller):
24030 - Add a "GETINFO signal/names" control port command. Implements
24032 - Provide default values for all options via "GETINFO config/defaults".
24033 Implements ticket 4971.
24035 o Minor features (IPv6):
24036 - New config option "AuthDirHasIPv6Connectivity 1" that directory
24037 authorities should set if they have IPv6 connectivity and want to
24038 do reachability tests for IPv6 relays. Implements feature 5974.
24039 - A relay with an IPv6 OR port now sends that address in NETINFO
24040 cells (in addition to its other address). Implements ticket 6364.
24042 o Minor features (log messages):
24043 - Omit the first heartbeat log message, because it never has anything
24044 useful to say, and it clutters up the bootstrapping messages.
24045 Resolves ticket 6758.
24046 - Don't log about reloading the microdescriptor cache at startup. Our
24047 bootstrap warnings are supposed to tell the user when there's a
24048 problem, and our bootstrap notices say when there isn't. Resolves
24049 ticket 6759; bugfix on 0.2.2.6-alpha.
24050 - Don't log "I learned some more directory information" when we're
24051 reading cached directory information. Reserve it for when new
24052 directory information arrives in response to a fetch. Resolves
24054 - Prevent rounding error in path bias counts when scaling
24055 them down, and use the correct scale factor default. Also demote
24056 some path bias related log messages down a level and make others
24057 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
24058 - We no longer warn so much when generating manpages from their
24061 o Code simplifications and refactoring:
24062 - Enhance our internal sscanf replacement so that we can eliminate
24063 the last remaining uses of the system sscanf. (Though those uses
24064 of sscanf were safe, sscanf itself is generally error prone, so
24065 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
24067 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
24068 - Move last_reachable and testing_since from routerinfo_t to node_t.
24069 Implements ticket 5529.
24070 - Add replaycache_t structure, functions and unit tests, then refactor
24071 rend_service_introduce() to be more clear to read, improve, debug,
24072 and test. Resolves bug 6177.
24073 - Finally remove support for malloc_good_size and malloc_usable_size.
24074 We had hoped that these functions would let us eke a little more
24075 memory out of our malloc implementation. Unfortunately, the only
24076 implementations that provided these functions are also ones that
24077 are already efficient about not overallocation: they never got us
24078 more than 7 or so bytes per allocation. Removing them saves us a
24079 little code complexity and a nontrivial amount of build complexity.
24081 o New requirements:
24082 - Tor maintainers now require Automake version 1.9 or later to build
24083 Tor from the Git repository. (Automake is not required when building
24084 from a source distribution.)
24087 Changes in version 0.2.3.21-rc - 2012-09-05
24088 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
24089 series. It fixes a trio of potential security bugs, fixes a bug where
24090 we were leaving some of the fast relays out of the microdescriptor
24091 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
24092 and cleans up other smaller issues.
24094 o Major bugfixes (security):
24095 - Tear down the circuit if we get an unexpected SENDME cell. Clients
24096 could use this trick to make their circuits receive cells faster
24097 than our flow control would have allowed, or to gum up the network,
24098 or possibly to do targeted memory denial-of-service attacks on
24099 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
24100 from July 2002, before the release of Tor 0.0.0. We had committed
24101 this patch previously, but we had to revert it because of bug 6271.
24102 Now that 6271 is fixed, this patch appears to work.
24103 - Reject any attempt to extend to an internal address. Without
24104 this fix, a router could be used to probe addresses on an internal
24105 network to see whether they were accepting connections. Fixes bug
24106 6710; bugfix on 0.0.8pre1.
24107 - Do not crash when comparing an address with port value 0 to an
24108 address policy. This bug could have been used to cause a remote
24109 assertion failure by or against directory authorities, or to
24110 allow some applications to crash clients. Fixes bug 6690; bugfix
24114 - Remove the upper bound on microdescriptor length. We were hitting
24115 the limit for routers with complex exit policies or family
24116 declarations, causing clients to not use them. Fixes the first
24117 piece of bug 6404; fix on 0.2.2.6-alpha.
24118 - Detect "ORPort 0" as meaning, uniformly, that we're not running
24119 as a relay. Previously, some of our code would treat the presence
24120 of any ORPort line as meaning that we should act like a relay,
24121 even though our new listener code would correctly not open any
24122 ORPorts for ORPort 0. Similar bugs in other Port options are also
24123 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
24126 - Avoid a pair of double-free and use-after-mark bugs that can
24127 occur with certain timings in canceled and re-received DNS
24128 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
24129 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
24130 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
24131 - Allow one-hop directory fetching circuits the full "circuit build
24132 timeout" period, rather than just half of it, before failing them
24133 and marking the relay down. This fix should help reduce cases where
24134 clients declare relays (or worse, bridges) unreachable because
24135 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
24136 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
24138 - Authorities no longer include any router in their microdescriptor
24139 consensuses for which they couldn't generate or agree on a
24140 microdescriptor. Fixes the second piece of bug 6404; fix on
24142 - Detect and reject attempts to specify both "FooPort" and
24143 "FooPort 0" in the same configuration domain. (It's still okay
24144 to have a FooPort in your configuration file, and use "FooPort 0"
24145 on the command line to disable it.) Fixes the second half of bug
24146 6507; bugfix on 0.2.3.3-alpha.
24147 - Make wildcarded addresses (that is, ones beginning with "*.") work
24148 when provided via the controller's MapAddress command. Previously,
24149 they were accepted, but we never actually noticed that they were
24150 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
24151 - Avoid crashing on a malformed state file where EntryGuardPathBias
24152 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
24153 - Add a (probably redundant) memory clear between iterations of
24154 the router status voting loop, to prevent future coding errors
24155 where data might leak between iterations of the loop. Resolves
24158 o Minor bugfixes (log messages):
24159 - Downgrade "set buildtimeout to low value" messages to "info"
24160 severity; they were never an actual problem, there was never
24161 anything reasonable to do about them, and they tended to spam logs
24162 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
24163 - Downgrade path-bias warning messages to "info". We'll try to get
24164 them working better in 0.2.4. Add internal circuit construction
24165 state to protect against the noisy warn message "Unexpectedly high
24166 circuit_successes". Also add some additional rate-limited notice
24167 messages to help determine the root cause of the warn. Fixes bug
24168 6475. Bugfix against 0.2.3.17-beta.
24169 - Move log message when unable to find a microdesc in a routerstatus
24170 entry to parse time. Previously we'd spam this warning every time
24171 we tried to figure out which microdescriptors to download. Fixes
24172 the third piece of bug 6404; fix on 0.2.3.18-rc.
24175 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
24176 change when the authority is deciding whether to accept a newly
24177 uploaded descriptor. Implements ticket 6423.
24178 - Add missing documentation for consensus and microdesc files.
24179 Resolves ticket 6732.
24182 Changes in version 0.2.2.38 - 2012-08-12
24183 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
24184 attack that could in theory leak path information.
24187 - Avoid an uninitialized memory read when reading a vote or consensus
24188 document that has an unrecognized flavor name. This read could
24189 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
24190 - Try to leak less information about what relays a client is
24191 choosing to a side-channel attacker. Previously, a Tor client would
24192 stop iterating through the list of available relays as soon as it
24193 had chosen one, thus finishing a little earlier when it picked
24194 a router earlier in the list. If an attacker can recover this
24195 timing information (nontrivial but not proven to be impossible),
24196 they could learn some coarse-grained information about which relays
24197 a client was picking (middle nodes in particular are likelier to
24198 be affected than exits). The timing attack might be mitigated by
24199 other factors (see bug 6537 for some discussion), but it's best
24200 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
24203 Changes in version 0.2.3.20-rc - 2012-08-05
24204 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
24205 series. It fixes a pair of code security bugs and a potential anonymity
24206 issue, updates our RPM spec files, and cleans up other smaller issues.
24209 - Avoid read-from-freed-memory and double-free bugs that could occur
24210 when a DNS request fails while launching it. Fixes bug 6480;
24211 bugfix on 0.2.0.1-alpha.
24212 - Avoid an uninitialized memory read when reading a vote or consensus
24213 document that has an unrecognized flavor name. This read could
24214 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
24215 - Try to leak less information about what relays a client is
24216 choosing to a side-channel attacker. Previously, a Tor client would
24217 stop iterating through the list of available relays as soon as it
24218 had chosen one, thus finishing a little earlier when it picked
24219 a router earlier in the list. If an attacker can recover this
24220 timing information (nontrivial but not proven to be impossible),
24221 they could learn some coarse-grained information about which relays
24222 a client was picking (middle nodes in particular are likelier to
24223 be affected than exits). The timing attack might be mitigated by
24224 other factors (see bug 6537 for some discussion), but it's best
24225 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
24228 - Try to make the warning when giving an obsolete SOCKSListenAddress
24229 a little more useful.
24230 - Terminate active server managed proxies if Tor stops being a
24231 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
24232 - Provide a better error message about possible OSX Asciidoc failure
24233 reasons. Fixes bug 6436.
24234 - Warn when Tor is configured to use accounting in a way that can
24235 link a hidden service to some other hidden service or public
24236 address. Resolves ticket 6490.
24239 - Check return value of fputs() when writing authority certificate
24240 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
24241 - Ignore ServerTransportPlugin lines when Tor is not configured as
24242 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
24243 - When disabling guards for having too high a proportion of failed
24244 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
24248 - Update our default RPM spec files to work with mock and rpmbuild
24249 on RHEL/Fedora. They have an updated set of dependencies and
24250 conflicts, a fix for an ancient typo when creating the "_tor"
24251 user, and better instructions. Thanks to Ondrej Mikle for the
24252 patch series. Fixes bug 6043.
24255 - Make it possible to set the TestingTorNetwork configuration
24256 option using AlternateDirAuthority and AlternateBridgeAuthority
24257 as an alternative to setting DirServer. Addresses ticket 6377.
24260 - Clarify the documentation for the Alternate*Authority options.
24262 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
24264 o Code simplification and refactoring:
24265 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
24266 10 lines. Also, don't nest them. Doing so in the past has
24267 led to hard-to-debug code. The new style is to use the
24268 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
24271 Changes in version 0.2.3.19-rc - 2012-07-06
24272 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
24273 series. It fixes the compile on Windows, reverts to a GeoIP database
24274 that isn't as broken, and fixes a flow control bug that has been around
24275 since the beginning of Tor.
24278 - Fix a bug handling SENDME cells on nonexistent streams that could
24279 result in bizarre window values. Report and patch contributed
24280 pseudonymously. Fixes part of bug 6271. This bug was introduced
24281 before the first Tor release, in svn commit r152.
24282 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
24283 June 2012 database, Maxmind marked many Tor relays as country "A1",
24284 which will cause risky behavior for clients that set EntryNodes
24285 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
24286 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
24287 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
24290 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
24291 bugfix on 0.2.1.10-alpha.
24294 Changes in version 0.2.3.18-rc - 2012-06-28
24295 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
24296 series. It fixes a few smaller bugs, but generally appears stable.
24297 Please test it and let us know whether it is!
24300 - Allow wildcarded mapaddress targets to be specified on the
24301 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
24302 - Make our linker option detection code more robust against linkers
24303 such as on FreeBSD 8, where a bad combination of options completes
24304 successfully but makes an unrunnable binary. Fixes bug 6173;
24305 bugfix on 0.2.3.17-beta.
24307 o Minor bugfixes (on 0.2.2.x and earlier):
24308 - Avoid a false positive in the util/threads unit test by increasing
24309 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
24310 - Replace "Sending publish request" log messages with "Launching
24311 upload", so that they no longer confusingly imply that we're
24312 sending something to a directory we might not even be connected
24313 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
24314 - Make sure to set *socket_error in all error cases in
24315 connection_connect(), so it can't produce a warning about
24316 errno being zero from errno_to_orconn_end_reason(). Bugfix on
24317 0.2.1.1-alpha; resolves ticket 6028.
24318 - Downgrade "Got a certificate, but we already have it" log messages
24319 from warning to info, except when we're a dirauth. Fixes bug 5238;
24320 bugfix on 0.2.1.7-alpha.
24321 - When checking for requested signatures on the latest consensus
24322 before serving it to a client, make sure to check the right
24323 consensus flavor. Bugfix on 0.2.2.6-alpha.
24324 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
24325 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
24327 o Minor bugfixes (on 0.2.3.x):
24328 - Make format_helper_exit_status() avoid unnecessary space padding
24329 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
24331 - Downgrade a message about cleaning the microdescriptor cache to
24332 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
24333 - Log a BUG message at severity INFO if we have a networkstatus with
24334 a missing entry for some microdescriptor. Continues on a patch
24336 - Improve the log message when a managed proxy fails to launch. Fixes
24337 bug 5099; bugfix on 0.2.3.6-alpha.
24338 - Don't do DNS lookups when parsing corrupted managed proxy protocol
24339 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
24340 - When formatting wildcarded address mappings for the controller,
24341 be sure to include "*." as appropriate. Partially fixes bug 6244;
24342 bugfix on 0.2.3.9-alpha.
24343 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
24344 Bugfix on 0.2.3.13-alpha.
24345 - Stop logging messages about running with circuit timeout learning
24346 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
24347 - Disable a spurious warning about reading on a marked and flushing
24348 connection. We shouldn't be doing that, but apparently we
24349 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
24350 - Fix a bug that stopped AllowDotExit from working on addresses
24351 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
24354 o Code simplification, refactoring, unit tests:
24355 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
24356 Libevent's notion of cached time when possible.
24357 - Remove duplicate code for invoking getrlimit() from control.c.
24358 - Add a unit test for the environment_variable_names_equal function.
24361 - Document the --defaults-torrc option, and the new (in 0.2.3)
24362 semantics for overriding, extending, and clearing lists of
24363 options. Closes bug 4748.
24366 Changes in version 0.2.3.17-beta - 2012-06-15
24367 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
24368 gets our TLS handshake back on track for being able to blend in with
24369 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
24370 with Vidalia, and otherwise continues to get us closer to a release
24374 - Enable gcc and ld hardening by default. Resolves ticket 5210.
24375 - Update TLS cipher list to match Firefox 8 and later. Resolves
24377 - Implement the client side of proposal 198: remove support for
24378 clients falsely claiming to support standard ciphersuites that
24379 they can actually provide. As of modern OpenSSL versions, it's not
24380 necessary to fake any standard ciphersuite, and doing so prevents
24381 us from using better ciphersuites in the future, since servers
24382 can't know whether an advertised ciphersuite is really supported or
24383 not. Some hosts -- notably, ones with very old versions of OpenSSL
24384 or where OpenSSL has been built with ECC disabled -- will stand
24385 out because of this change; TBB users should not be affected.
24388 - Change the default value for DynamicDHGroups (introduced in
24389 0.2.3.9-alpha) to 0. This feature can make Tor relays less
24390 identifiable by their use of the mod_ssl DH group, but at
24391 the cost of some usability (#4721) and bridge tracing (#6087)
24392 regressions. Resolves ticket 5598.
24393 - Send a CRLF at the end of each STATUS_* control protocol event. This
24394 bug tickled a bug in Vidalia which would make it freeze. Fixes
24395 bug 6094; bugfix on 0.2.3.16-alpha.
24398 - Disable writing on marked-for-close connections when they are
24399 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
24400 bug 5263; bugfix on 0.0.2pre13, where we first added a special
24401 case for flushing marked connections.
24402 - Detect SSL handshake even when the initial attempt to write the
24403 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
24404 - Change the AllowDotExit rules so they should actually work.
24405 We now enforce AllowDotExit only immediately after receiving an
24406 address via SOCKS or DNSPort: other sources are free to provide
24407 .exit addresses after the resolution occurs. Fixes bug 3940;
24408 bugfix on 0.2.2.1-alpha.
24409 - Fix a (harmless) integer overflow in cell statistics reported by
24410 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
24411 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
24412 right places and never depends on the consensus parameters or
24413 computes adaptive timeouts when it is disabled. Fixes bug 5049;
24414 bugfix on 0.2.2.14-alpha.
24415 - When building Tor on Windows with -DUNICODE (not default), ensure
24416 that error messages, filenames, and DNS server names are always
24417 NUL-terminated when we convert them to a single-byte encoding.
24418 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
24419 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
24420 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
24421 - Fix an edge case where TestingTorNetwork is set but the authorities
24422 and relays all have an uptime of zero, where the private Tor network
24423 could briefly lack support for hidden services. Fixes bug 3886;
24424 bugfix on 0.2.2.18-alpha.
24425 - Correct the manpage's descriptions for the default values of
24426 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
24428 - Fix the documentation for the --hush and --quiet command line
24429 options, which changed their behavior back in 0.2.3.3-alpha.
24430 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
24434 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
24435 more information to it, so that we can track it down in case it
24436 returns again. Mitigates bug 5235.
24437 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
24438 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
24439 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
24440 - Warn the user when HTTPProxy, but no other proxy type, is
24441 configured. This can cause surprising behavior: it doesn't send
24442 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
24443 directory traffic only. Resolves ticket 4663.
24444 - Issue a notice if a guard completes less than 40% of your circuits.
24445 Threshold is configurable by torrc option PathBiasNoticeRate and
24446 consensus parameter pb_noticepct. There is additional, off-by-
24447 default code to disable guards which fail too many circuits.
24448 Addresses ticket 5458.
24449 - Update to the June 6 2012 Maxmind GeoLite Country database.
24451 o Code simplifications and refactoring:
24452 - Remove validate_pluggable_transports_config(): its warning
24453 message is now handled by connection_or_connect().
24456 Changes in version 0.2.2.37 - 2012-06-06
24457 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
24458 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
24462 - Work around a bug in OpenSSL that broke renegotiation with TLS
24463 1.1 and TLS 1.2. Without this workaround, all attempts to speak
24464 the v2 Tor connection protocol when both sides were using OpenSSL
24465 1.0.1 would fail. Resolves ticket 6033.
24466 - When waiting for a client to renegotiate, don't allow it to add
24467 any bytes to the input buffer. This fixes a potential DoS issue.
24468 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
24469 - Fix an edge case where if we fetch or publish a hidden service
24470 descriptor, we might build a 4-hop circuit and then use that circuit
24471 for exiting afterwards -- even if the new last hop doesn't obey our
24472 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
24475 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
24476 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
24479 - Tell GCC and Clang to check for any errors in format strings passed
24480 to the tor_v*(print|scan)f functions.
24483 Changes in version 0.2.3.16-alpha - 2012-06-05
24484 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
24485 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
24486 currently). It also fixes a variety of smaller bugs and other cleanups
24487 that get us closer to a release candidate.
24489 o Major bugfixes (general):
24490 - Work around a bug in OpenSSL that broke renegotiation with TLS
24491 1.1 and TLS 1.2. Without this workaround, all attempts to speak
24492 the v2 Tor connection protocol when both sides were using OpenSSL
24493 1.0.1 would fail. Resolves ticket 6033.
24494 - When waiting for a client to renegotiate, don't allow it to add
24495 any bytes to the input buffer. This fixes a potential DoS issue.
24496 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
24497 - Pass correct OR address to managed proxies (like obfsproxy),
24498 even when ORListenAddress is used. Fixes bug 4865; bugfix on
24500 - The advertised platform of a router now includes only its operating
24501 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
24502 service pack level (for Windows) or its CPU architecture (for Unix).
24503 We also no longer include the "git-XYZ" tag in the version. Resolves
24506 o Major bugfixes (clients):
24507 - If we are unable to find any exit that supports our predicted ports,
24508 stop calling them predicted, so that we don't loop and build
24509 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
24510 which introduced predicted ports.
24511 - Fix an edge case where if we fetch or publish a hidden service
24512 descriptor, we might build a 4-hop circuit and then use that circuit
24513 for exiting afterwards -- even if the new last hop doesn't obey our
24514 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
24515 - Check at each new consensus whether our entry guards were picked
24516 long enough ago that we should rotate them. Previously, we only
24517 did this check at startup, which could lead to us holding a guard
24518 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
24519 - When fetching a bridge descriptor from a bridge authority,
24520 always do so anonymously, whether we have been able to open
24521 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
24522 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
24523 but we'll need to wait for bug 6010 before it's actually usable.
24525 o Major bugfixes (directory authorities):
24526 - When computing weight parameters, behave more robustly in the
24527 presence of a bad bwweightscale value. Previously, the authorities
24528 would crash if they agreed on a sufficiently broken weight_scale
24529 value: now, they use a reasonable default and carry on. Partial
24530 fix for 5786; bugfix on 0.2.2.17-alpha.
24531 - Check more thoroughly to prevent a rogue authority from
24532 double-voting on any consensus directory parameter. Previously,
24533 authorities would crash in this case if the total number of
24534 votes for any parameter exceeded the number of active voters,
24535 but would let it pass otherwise. Partial fix for bug 5786; bugfix
24539 - Rate-limit log messages when asked to connect anonymously to
24540 a private address. When these hit, they tended to hit fast and
24541 often. Also, don't bother trying to connect to addresses that we
24542 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
24543 reply makes us think we have been lied to, even when the address the
24544 client tried to connect to was "localhost." Resolves ticket 2822.
24545 - Allow packagers to insert an extra string in server descriptor
24546 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
24547 Resolves the rest of ticket 2988.
24548 - Raise the threshold of server descriptors needed (75%) and exit
24549 server descriptors needed (50%) before we will declare ourselves
24550 bootstrapped. This will make clients start building circuits a
24551 little later, but makes the initially constructed circuits less
24552 skewed and less in conflict with further directory fetches. Fixes
24554 - Close any connection that sends unrecognized junk before the
24555 handshake. Solves an issue noted in bug 4369.
24556 - Improve log messages about managed transports. Resolves ticket 5070.
24557 - Tag a bridge's descriptor as "never to be sent unencrypted".
24558 This shouldn't matter, since bridges don't open non-anonymous
24559 connections to the bridge authority and don't allow unencrypted
24560 directory connections from clients, but we might as well make
24561 sure. Closes bug 5139.
24562 - Expose our view of whether we have gone dormant to the controller,
24563 via a new "GETINFO dormant" value. Torbutton and other controllers
24564 can use this to avoid doing periodic requests through Tor while
24565 it's dormant (bug 4718). Fixes bug 5954.
24566 - Tell GCC and Clang to check for any errors in format strings passed
24567 to the tor_v*(print|scan)f functions.
24568 - Update to the May 1 2012 Maxmind GeoLite Country database.
24570 o Minor bugfixes (already included in 0.2.2.36):
24571 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
24572 Fixes bug 5346; bugfix on 0.0.8pre3.
24573 - Correct parsing of certain date types in parse_http_time().
24574 Without this patch, If-Modified-Since would behave
24575 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
24576 Esteban Manchado Velázques.
24577 - Make our number-parsing functions always treat too-large values
24578 as an error, even when those values exceed the width of the
24579 underlying type. Previously, if the caller provided these
24580 functions with minima or maxima set to the extreme values of the
24581 underlying integer type, these functions would return those
24582 values on overflow rather than treating overflow as an error.
24583 Fixes part of bug 5786; bugfix on 0.0.9.
24584 - If we hit the error case where routerlist_insert() replaces an
24585 existing (old) server descriptor, make sure to remove that
24586 server descriptor from the old_routers list. Fix related to bug
24587 1776. Bugfix on 0.2.2.18-alpha.
24588 - Clarify the behavior of MaxCircuitDirtiness with hidden service
24589 circuits. Fixes issue 5259.
24591 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
24592 - Prevent a null-pointer dereference when receiving a data cell
24593 for a nonexistent stream when the circuit in question has an
24594 empty deliver window. We don't believe this is triggerable,
24595 since we don't currently allow deliver windows to become empty,
24596 but the logic is tricky enough that it's better to make the code
24597 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
24598 - Fix a memory leak when trying to launch a DNS request when the
24599 network is disabled or the nameservers are unconfigurable. Fixes
24600 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
24601 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
24602 - Don't hold a Windows file handle open for every file mapping;
24603 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
24605 - Avoid O(n^2) performance characteristics when parsing a large
24606 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
24607 - Format more doubles with %f, not %lf. Patch from grarpamp to make
24608 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
24610 - Make our replacement implementation of strtok_r() compatible with
24611 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
24612 bugfix on 0.2.2.1-alpha.
24613 - Fix a NULL-pointer dereference on a badly formed
24614 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
24615 bugfix on 0.2.2.9-alpha.
24616 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
24617 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
24618 - Defensively refactor rend_mid_rendezvous() so that protocol
24619 violations and length checks happen in the beginning. Fixes
24621 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
24622 that IPv6 stuff will compile on MSVC, and compilation issues
24623 will be easier to track down. Fixes bug 5861.
24625 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
24626 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
24627 resource exhaustion, so that clients can adjust their load to
24628 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
24629 started using END_STREAM_REASON_RESOURCELIMIT.
24630 - Don't check for whether the address we're using for outbound
24631 connections has changed until after the outbound connection has
24632 completed. On Windows, getsockname() doesn't succeed until the
24633 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
24634 - If the configuration tries to set MyFamily on a bridge, refuse to
24635 do so, and warn about the security implications. Fixes bug 4657;
24636 bugfix on 0.2.0.3-alpha.
24637 - If the client fails to set a reasonable set of ciphersuites
24638 during its v2 handshake renegotiation, allow the renegotiation to
24639 continue nevertheless (i.e. send all the required certificates).
24640 Fixes bug 4591; bugfix on 0.2.0.20-rc.
24641 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
24642 option is set to 0 (which Vidalia version 0.2.16 now does when
24643 a SAVECONF attempt fails), perform other actions that SIGHUP
24644 usually causes (like reopening the logs). Fixes bug 5095; bugfix
24646 - If we fail to write a microdescriptor to the disk cache, do not
24647 continue replacing the old microdescriptor file. Fixes bug 2954;
24648 bugfix on 0.2.2.6-alpha.
24649 - Exit nodes don't need to fetch certificates for authorities that
24650 they don't recognize; only directory authorities, bridges,
24651 and caches need to do that. Fixes part of bug 2297; bugfix on
24653 - Correctly handle checking the permissions on the parent
24654 directory of a control socket in the root directory. Bug found
24655 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
24657 - When told to add a bridge with the same digest as a preexisting
24658 bridge but a different addr:port, change the addr:port as
24659 requested. Previously we would not notice the change. Fixes half
24660 of bug 5603; fix on 0.2.2.26-beta.
24661 - End AUTHCHALLENGE error messages (in the control protocol) with
24662 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
24664 o Minor bugfixes (on 0.2.3.x):
24665 - Turn an assertion (that the number of handshakes received as a
24666 server is not < 1) into a warning. Fixes bug 4873; bugfix on
24668 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
24669 we had reversed them when the answer was cached.) Fixes bug
24670 5723; bugfix on 0.2.3.1-alpha.
24671 - Work correctly on Linux systems with accept4 support advertised in
24672 their headers, but without accept4 support in the kernel. Fix
24673 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
24674 - When told to add a bridge with the same addr:port as a preexisting
24675 bridge but a different transport, change the transport as
24676 requested. Previously we would not notice the change. Fixes half
24677 of bug 5603; fix on 0.2.3.2-alpha.
24678 - Avoid a "double-reply" warning when replying to a SOCKS request
24679 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
24680 bugfix on 0.2.3.4-alpha.
24681 - Fix a bug where a bridge authority crashes if it has seen no
24682 directory requests when it's time to write statistics to disk.
24683 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
24685 - Don't try to open non-control listeners when DisableNetwork is set.
24686 Previously, we'd open all listeners, then immediately close them.
24687 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
24688 - Don't abort the managed proxy protocol if the managed proxy
24689 sends us an unrecognized line; ignore it instead. Fixes bug
24690 5910; bugfix on 0.2.3.9-alpha.
24691 - Fix a compile warning in crypto.c when compiling with clang 3.1.
24692 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
24693 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
24694 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
24695 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
24696 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
24697 - Resolve numerous small warnings and build issues with MSVC. Resolves
24700 o Documentation fixes:
24701 - Improve the manual's documentation for the NT Service command-line
24702 options. Addresses ticket 3964.
24703 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
24704 - Document the changes to the ORPort and DirPort options, and the
24705 fact that {OR/Dir}ListenAddress is now unnecessary (and
24706 therefore deprecated). Resolves ticket 5597.
24709 - Remove the torrc.bridge file: we don't use it for anything, and
24710 it had become badly desynchronized from torrc.sample. Resolves
24714 Changes in version 0.2.2.36 - 2012-05-24
24715 Tor 0.2.2.36 updates the addresses for two of the eight directory
24716 authorities, fixes some potential anonymity and security issues,
24717 and fixes several crash bugs.
24719 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
24720 known flaws, and nobody should be using them. You should upgrade. If
24721 you're using a Linux or BSD and its packages are obsolete, stop using
24722 those packages and upgrade anyway.
24724 o Directory authority changes:
24725 - Change IP address for maatuska (v3 directory authority).
24726 - Change IP address for ides (v3 directory authority), and rename
24730 - When building or running with any version of OpenSSL earlier
24731 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
24732 versions have a bug (CVE-2011-4576) in which their block cipher
24733 padding includes uninitialized data, potentially leaking sensitive
24734 information to any peer with whom they make a SSLv3 connection. Tor
24735 does not use SSL v3 by default, but a hostile client or server
24736 could force an SSLv3 connection in order to gain information that
24737 they shouldn't have been able to get. The best solution here is to
24738 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
24739 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
24740 to make sure that the bug can't happen.
24741 - Never use a bridge or a controller-supplied node as an exit, even
24742 if its exit policy allows it. Found by wanoskarnet. Fixes bug
24743 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
24744 and 0.2.0.3-alpha (for bridge-purpose descriptors).
24745 - Only build circuits if we have a sufficient threshold of the total
24746 descriptors that are marked in the consensus with the "Exit"
24747 flag. This mitigates an attack proposed by wanoskarnet, in which
24748 all of a client's bridges collude to restrict the exit nodes that
24749 the client knows about. Fixes bug 5343.
24750 - Provide controllers with a safer way to implement the cookie
24751 authentication mechanism. With the old method, if another locally
24752 running program could convince a controller that it was the Tor
24753 process, then that program could trick the controller into telling
24754 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
24755 authentication method uses a challenge-response approach to prevent
24756 this attack. Fixes bug 5185; implements proposal 193.
24759 - Avoid logging uninitialized data when unable to decode a hidden
24760 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
24761 - Avoid a client-side assertion failure when receiving an INTRODUCE2
24762 cell on a general purpose circuit. Fixes bug 5644; bugfix on
24764 - Fix builds when the path to sed, openssl, or sha1sum contains
24765 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
24767 - Correct our replacements for the timeradd() and timersub() functions
24768 on platforms that lack them (for example, Windows). The timersub()
24769 function is used when expiring circuits, while timeradd() is
24770 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
24771 bugfix on 0.2.2.24-alpha.
24772 - Fix the SOCKET_OK test that we use to tell when socket
24773 creation fails so that it works on Win64. Fixes part of bug 4533;
24774 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
24777 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
24778 Fixes bug 5346; bugfix on 0.0.8pre3.
24779 - Make our number-parsing functions always treat too-large values
24780 as an error, even when those values exceed the width of the
24781 underlying type. Previously, if the caller provided these
24782 functions with minima or maxima set to the extreme values of the
24783 underlying integer type, these functions would return those
24784 values on overflow rather than treating overflow as an error.
24785 Fixes part of bug 5786; bugfix on 0.0.9.
24786 - Older Linux kernels erroneously respond to strange nmap behavior
24787 by having accept() return successfully with a zero-length
24788 socket. When this happens, just close the connection. Previously,
24789 we would try harder to learn the remote address: but there was
24790 no such remote address to learn, and our method for trying to
24791 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
24792 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
24793 - Correct parsing of certain date types in parse_http_time().
24794 Without this patch, If-Modified-Since would behave
24795 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
24796 Esteban Manchado Velázques.
24797 - Change the BridgePassword feature (part of the "bridge community"
24798 design, which is not yet implemented) to use a time-independent
24799 comparison. The old behavior might have allowed an adversary
24800 to use timing to guess the BridgePassword value. Fixes bug 5543;
24801 bugfix on 0.2.0.14-alpha.
24802 - Detect and reject certain misformed escape sequences in
24803 configuration values. Previously, these values would cause us
24804 to crash if received in a torrc file or over an authenticated
24805 control port. Bug found by Esteban Manchado Velázquez, and
24806 independently by Robert Connolly from Matta Consulting who further
24807 noted that it allows a post-authentication heap overflow. Patch
24808 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
24809 bugfix on 0.2.0.16-alpha.
24810 - Fix a compile warning when using the --enable-openbsd-malloc
24811 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
24812 - During configure, detect when we're building with clang version
24813 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
24814 CFLAGS. clang doesn't support them yet.
24815 - When sending an HTTP/1.1 proxy request, include a Host header.
24816 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
24817 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
24818 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
24819 - If we hit the error case where routerlist_insert() replaces an
24820 existing (old) server descriptor, make sure to remove that
24821 server descriptor from the old_routers list. Fix related to bug
24822 1776. Bugfix on 0.2.2.18-alpha.
24824 o Minor bugfixes (documentation and log messages):
24825 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
24826 Fixes bug 4856; bugfix on Tor 0.0.6.
24827 - Update "ClientOnly" man page entry to explain that there isn't
24828 really any point to messing with it. Resolves ticket 5005.
24829 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
24830 directory authority option (introduced in Tor 0.2.2.34).
24831 - Downgrade the "We're missing a certificate" message from notice
24832 to info: people kept mistaking it for a real problem, whereas it
24833 is seldom the problem even when we are failing to bootstrap. Fixes
24834 bug 5067; bugfix on 0.2.0.10-alpha.
24835 - Correctly spell "connect" in a log message on failure to create a
24836 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
24837 - Clarify the behavior of MaxCircuitDirtiness with hidden service
24838 circuits. Fixes issue 5259.
24841 - Directory authorities now reject versions of Tor older than
24842 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
24843 inclusive. These versions accounted for only a small fraction of
24844 the Tor network, and have numerous known security issues. Resolves
24846 - Update to the May 1 2012 Maxmind GeoLite Country database.
24849 - When sending or relaying a RELAY_EARLY cell, we used to convert
24850 it to a RELAY cell if the connection was using the v1 link
24851 protocol. This was a workaround for older versions of Tor, which
24852 didn't handle RELAY_EARLY cells properly. Now that all supported
24853 versions can handle RELAY_EARLY cells, and now that we're enforcing
24854 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
24855 remove this workaround. Addresses bug 4786.
24858 Changes in version 0.2.3.15-alpha - 2012-04-30
24859 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
24860 the development branch build on Windows again.
24862 o Minor bugfixes (on 0.2.2.x and earlier):
24863 - Make sure that there are no unhandled pending TLS errors before
24864 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
24865 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
24866 Bugfix on 0.1.0.5-rc; fixes bug 4528.
24867 - Fix an assert that directory authorities could trigger on sighup
24868 during some configuration state transitions. We now don't treat
24869 it as a fatal error when the new descriptor we just generated in
24870 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
24871 - After we pick a directory mirror, we would refuse to use it if
24872 it's in our ExcludeExitNodes list, resulting in mysterious failures
24873 to bootstrap for people who just wanted to avoid exiting from
24874 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
24875 - When building with --enable-static-tor on OpenBSD, do not
24876 erroneously attempt to link -lrt. Fixes bug 5103.
24878 o Minor bugfixes (on 0.2.3.x):
24879 - When Tor is built with kernel headers from a recent (last few
24880 years) Linux kernel, do not fail to run on older (pre-2.6.28
24881 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
24882 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
24883 and 0.2.3.12-alpha.
24884 - Fix compilation with miniupnpc version 1.6; patch from
24885 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
24886 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
24887 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
24888 - Fix compilation on platforms without unistd.h, or where environ
24889 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
24892 - Directory authorities are now a little more lenient at accepting
24893 older router descriptors, or newer router descriptors that don't
24894 make big changes. This should help ameliorate past and future
24895 issues where routers think they have uploaded valid descriptors,
24896 but the authorities don't think so. Fix for ticket 2479.
24897 - Make the code that clients use to detect an address change be
24898 IPv6-aware, so that it won't fill clients' logs with error
24899 messages when trying to get the IPv4 address of an IPv6
24900 connection. Implements ticket 5537.
24902 o Removed features:
24903 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
24904 authorities needed to use it for a while to keep the network working
24905 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
24906 that was six months ago. As of now, it should no longer be needed
24910 Changes in version 0.2.3.14-alpha - 2012-04-23
24911 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
24912 candidate. It also dramatically speeds up AES: fast relays should
24913 consider switching to the newer OpenSSL library.
24915 o Directory authority changes:
24916 - Change IP address for ides (v3 directory authority), and rename
24920 - Avoid logging uninitialized data when unable to decode a hidden
24921 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
24922 - Avoid a client-side assertion failure when receiving an INTRODUCE2
24923 cell on a general purpose circuit. Fixes bug 5644; bugfix on
24925 - If authorities are unable to get a v2 consensus document from other
24926 directory authorities, they no longer fall back to fetching
24927 them from regular directory caches. Fixes bug 5635; bugfix on
24928 0.2.2.26-beta, where routers stopped downloading v2 consensus
24929 documents entirely.
24930 - When we start a Tor client with a normal consensus already cached,
24931 be willing to download a microdescriptor consensus. Fixes bug 4011;
24932 fix on 0.2.3.1-alpha.
24934 o Major features (performance):
24935 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
24936 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
24937 vectorized AES implementations as appropriate. These can be much,
24938 much faster than other AES implementations.
24940 o Minor bugfixes (0.2.2.x and earlier):
24941 - Don't launch more than 10 service-side introduction-point circuits
24942 for a hidden service in five minutes. Previously, we would consider
24943 launching more introduction-point circuits if at least one second
24944 had passed without any introduction-point circuits failing. Fixes
24945 bug 4607; bugfix on 0.0.7pre1.
24946 - Change the BridgePassword feature (part of the "bridge community"
24947 design, which is not yet implemented) to use a time-independent
24948 comparison. The old behavior might have allowed an adversary
24949 to use timing to guess the BridgePassword value. Fixes bug 5543;
24950 bugfix on 0.2.0.14-alpha.
24951 - Enforce correct return behavior of tor_vsscanf() when the '%%'
24952 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
24953 - When sending an HTTP/1.1 proxy request, include a Host header.
24954 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
24955 - Don't log that we have "decided to publish new relay descriptor"
24956 unless we are actually publishing a descriptor. Fixes bug 3942;
24957 bugfix on 0.2.2.28-beta.
24959 o Minor bugfixes (0.2.3.x):
24960 - Fix a bug where a bridge authority crashes (on a failed assert)
24961 if it has seen no directory requests when it's time to write
24962 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
24963 - Fix bug stomping on ORPort option NoListen and ignoring option
24964 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
24965 - In the testsuite, provide a large enough buffer in the tor_sscanf
24966 unit test. Otherwise we'd overrun that buffer and crash during
24967 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
24969 - Make sure we create the keys directory if it doesn't exist and we're
24970 about to store the dynamic Diffie-Hellman parameters. Fixes bug
24971 5572; bugfix on 0.2.3.13-alpha.
24972 - Fix a small memory leak when trying to decode incorrect base16
24973 authenticator during SAFECOOKIE authentication. Found by
24974 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
24977 - Add more information to a log statement that might help track down
24978 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
24979 non-IP address" messages (or any Bug messages, for that matter!),
24980 please let us know about it.
24981 - Relays now understand an IPv6 address when they get one from a
24982 directory server. Resolves ticket 4875.
24983 - Resolve IPv6 addresses in bridge and entry statistics to country
24984 code "??" which means we at least count them. Resolves ticket 5053;
24985 improves on 0.2.3.9-alpha.
24986 - Update to the April 3 2012 Maxmind GeoLite Country database.
24987 - Begin a doc/state-contents.txt file to explain the contents of
24988 the Tor state file. Fixes bug 2987.
24990 o Default torrc changes:
24991 - Stop listing "socksport 9050" in torrc.sample. We open a socks
24992 port on 9050 by default anyway, so this should not change anything
24994 - Stop mentioning the deprecated *ListenAddress options in
24995 torrc.sample. Fixes bug 5438.
24996 - Document unit of bandwidth related options in sample torrc.
24999 o Removed features:
25000 - The "torify" script no longer supports the "tsocks" socksifier
25001 tool, since tsocks doesn't support DNS and UDP right for Tor.
25002 Everyone should be using torsocks instead. Fixes bugs 3530 and
25003 5180. Based on a patch by "ugh".
25005 o Code refactoring:
25006 - Change the symmetric cipher interface so that creating and
25007 initializing a stream cipher are no longer separate functions.
25008 - Remove all internal support for unpadded RSA. We never used it, and
25009 it would be a bad idea to start.
25012 Changes in version 0.2.3.13-alpha - 2012-03-26
25013 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
25014 in managed pluggable transports, as well as providing other cleanups
25015 that get us closer to a release candidate.
25017 o Directory authority changes:
25018 - Change IP address for maatuska (v3 directory authority).
25021 - Provide controllers with a safer way to implement the cookie
25022 authentication mechanism. With the old method, if another locally
25023 running program could convince a controller that it was the Tor
25024 process, then that program could trick the controller into telling
25025 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
25026 authentication method uses a challenge-response approach to prevent
25027 this attack. Fixes bug 5185, implements proposal 193.
25028 - Never use a bridge or a controller-supplied node as an exit, even
25029 if its exit policy allows it. Found by wanoskarnet. Fixes bug
25030 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
25031 and 0.2.0.3-alpha (for bridge-purpose descriptors).
25032 - Only build circuits if we have a sufficient threshold of the total
25033 descriptors that are marked in the consensus with the "Exit"
25034 flag. This mitigates an attack proposed by wanoskarnet, in which
25035 all of a client's bridges collude to restrict the exit nodes that
25036 the client knows about. Fixes bug 5343.
25038 o Major bugfixes (on Tor 0.2.3.x):
25039 - Avoid an assert when managed proxies like obfsproxy are configured,
25040 and we receive HUP signals or setconf attempts too rapidly. This
25041 situation happens most commonly when Vidalia tries to attach to
25042 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
25043 bugfix on 0.2.3.6-alpha.
25044 - Fix a relay-side pluggable transports bug where managed proxies were
25045 unreachable from the Internet, because Tor asked them to bind on
25046 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
25047 - Stop discarding command-line arguments when TestingTorNetwork
25048 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
25049 0.2.3.9-alpha, where task 4552 added support for two layers of
25051 - Resume allowing the unit tests to run in gdb. This was accidentally
25052 made impossible when the DisableDebuggerAttachment option was
25053 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
25054 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
25055 0.2.3.11-alpha. Reported by Anthony G. Basile.
25057 o Minor bugfixes (on 0.2.2.x and earlier):
25058 - Ensure we don't cannibalize circuits that are longer than three hops
25059 already, so we don't end up making circuits with 5 or more
25060 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
25061 0.1.0.1-rc which introduced cannibalization.
25062 - Detect and reject certain misformed escape sequences in
25063 configuration values. Previously, these values would cause us
25064 to crash if received in a torrc file or over an authenticated
25065 control port. Bug found by Esteban Manchado Velázquez, and
25066 independently by Robert Connolly from Matta Consulting who further
25067 noted that it allows a post-authentication heap overflow. Patch
25068 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
25069 bugfix on 0.2.0.16-alpha.
25070 - Fix a compile warning when using the --enable-openbsd-malloc
25071 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
25072 - Directory caches no longer refuse to clean out descriptors because
25073 of missing v2 networkstatus documents, unless they're configured
25074 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
25075 0.2.2.26-beta. Patch by Daniel Bryg.
25076 - Update to the latest version of the tinytest unit testing framework.
25077 This includes a couple of bugfixes that can be relevant for
25078 running forked unit tests on Windows, and removes all reserved
25081 o Minor bugfixes (on 0.2.3.x):
25082 - On a failed pipe() call, don't leak file descriptors. Fixes bug
25083 4296; bugfix on 0.2.3.1-alpha.
25084 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
25085 until after we have received a CERTS cell. Fixes bug 4361; bugfix
25086 on 0.2.3.6-alpha. Patch by "frosty".
25087 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
25088 option, so that the IP stack doesn't decide to use it for IPv4
25089 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
25090 - Ensure that variables set in Tor's environment cannot override
25091 environment variables that Tor passes to a managed
25092 pluggable-transport proxy. Previously, Tor would pass every
25093 variable in its environment to managed proxies along with the new
25094 ones, in such a way that on many operating systems, the inherited
25095 environment variables would override those which Tor tried to
25096 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
25097 bugfix on 0.2.3.9-alpha for Windows.
25100 - A wide variety of new unit tests by Esteban Manchado Velázquez.
25101 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
25102 - Update to the March 6 2012 Maxmind GeoLite Country database.
25105 Changes in version 0.2.3.12-alpha - 2012-02-13
25106 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
25107 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
25108 when Tor is configured to use a pluggable transport like obfsproxy.
25111 - Fix builds when the path to sed, openssl, or sha1sum contains
25112 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
25114 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
25115 connections. This change should allow busy exit relays to stop
25116 running out of available sockets as quickly. Fixes bug 4950;
25117 bugfix on 0.2.2.26-beta.
25118 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
25119 would ask the bridge for microdescriptors, which are only supported
25120 in 0.2.3.x, and then fail to bootstrap when it didn't get the
25121 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
25122 - Properly set up obfsproxy's environment when in managed mode. The
25123 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
25124 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
25125 5076 and 5082; bugfix on 0.2.3.6-alpha.
25128 - Use the dead_strip option when building Tor on OS X. This reduces
25129 binary size by almost 19% when linking openssl and libevent
25130 statically, which we do for Tor Browser Bundle.
25131 - Fix broken URLs in the sample torrc file, and tell readers about
25132 the OutboundBindAddress, ExitPolicyRejectPrivate, and
25133 PublishServerDescriptor options. Addresses bug 4652.
25134 - Update to the February 7 2012 Maxmind GeoLite Country database.
25137 - Downgrade the "We're missing a certificate" message from notice
25138 to info: people kept mistaking it for a real problem, whereas it
25139 is seldom the problem even when we are failing to bootstrap. Fixes
25140 bug 5067; bugfix on 0.2.0.10-alpha.
25141 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
25142 managed pluggable transport server proxy's environment.
25143 Previously, we would put it there, even though Tor doesn't
25144 implement an 'extended server port' yet, and even though Tor
25145 almost certainly isn't listening at that address. For now, we set
25146 it to an empty string to avoid crashing older obfsproxies. Bugfix
25148 - Log the heartbeat message every HeartbeatPeriod seconds, not every
25149 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
25150 0.2.3.1-alpha. Bug reported by Scott Bennett.
25151 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
25152 bugfix on 0.2.3.11-alpha.
25153 - Update "ClientOnly" man page entry to explain that there isn't
25154 really any point to messing with it. Resolves ticket 5005.
25155 - Use the correct CVE number for CVE-2011-4576 in our comments and
25156 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
25159 o Code simplifications and refactoring:
25160 - Use the _WIN32 macro throughout our code to detect Windows.
25161 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
25165 Changes in version 0.2.3.11-alpha - 2012-01-22
25166 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
25167 the last step of the plan to limit maximum circuit length, includes
25168 a wide variety of hidden service performance and correctness fixes,
25169 works around an OpenSSL security flaw if your distro is too stubborn
25170 to upgrade, and fixes a bunch of smaller issues.
25173 - Now that Tor 0.2.0.x is completely deprecated, enable the final
25174 part of "Proposal 110: Avoiding infinite length circuits" by
25175 refusing all circuit-extend requests that do not use a relay_early
25176 cell. This change helps Tor resist a class of denial-of-service
25177 attacks by limiting the maximum circuit length.
25178 - Adjust the number of introduction points that a hidden service
25179 will try to maintain based on how long its introduction points
25180 remain in use and how many introductions they handle. Fixes
25182 - Try to use system facilities for enumerating local interface
25183 addresses, before falling back to our old approach (which was
25184 binding a UDP socket, and calling getsockname() on it). That
25185 approach was scaring OS X users whose draconian firewall
25186 software warned about binding to UDP sockets, regardless of
25187 whether packets were sent. Now we try to use getifaddrs(),
25188 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
25189 system supports. Resolves ticket 1827.
25191 o Major security workaround:
25192 - When building or running with any version of OpenSSL earlier
25193 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
25194 versions have a bug (CVE-2011-4576) in which their block cipher
25195 padding includes uninitialized data, potentially leaking sensitive
25196 information to any peer with whom they make a SSLv3 connection. Tor
25197 does not use SSL v3 by default, but a hostile client or server
25198 could force an SSLv3 connection in order to gain information that
25199 they shouldn't have been able to get. The best solution here is to
25200 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
25201 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
25202 to make sure that the bug can't happen.
25205 - Fix the SOCKET_OK test that we use to tell when socket
25206 creation fails so that it works on Win64. Fixes part of bug 4533;
25207 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
25208 - Correct our replacements for the timeradd() and timersub() functions
25209 on platforms that lack them (for example, Windows). The timersub()
25210 function is used when expiring circuits, while timeradd() is
25211 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
25212 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
25213 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
25214 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
25215 bug at runtime, not compile time, because some distributions hack
25216 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
25217 on 0.2.3.9-alpha. Found by Pascal.
25219 o Minor features (controller):
25220 - Use absolute path names when reporting the torrc filename in the
25221 control protocol, so a controller can more easily find the torrc
25222 file. Resolves bug 1101.
25223 - Extend the control protocol to report flags that control a circuit's
25224 path selection in CIRC events and in replies to 'GETINFO
25225 circuit-status'. Implements part of ticket 2411.
25226 - Extend the control protocol to report the hidden service address
25227 and current state of a hidden-service-related circuit in CIRC
25228 events and in replies to 'GETINFO circuit-status'. Implements part
25230 - When reporting the path to the cookie file to the controller,
25231 give an absolute path. Resolves ticket 4881.
25232 - Allow controllers to request an event notification whenever a
25233 circuit is cannibalized or its purpose is changed. Implements
25234 part of ticket 3457.
25235 - Include the creation time of a circuit in CIRC and CIRC2
25236 control-port events and the list produced by the 'GETINFO
25237 circuit-status' control-port command.
25239 o Minor features (directory authorities):
25240 - Directory authorities now reject versions of Tor older than
25241 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
25242 inclusive. These versions accounted for only a small fraction of
25243 the Tor network, and have numerous known security issues. Resolves
25245 - Authority operators can now vote for all relays in a given
25246 set of countries to be BadDir/BadExit/Invalid/Rejected.
25247 - Provide two consensus parameters (FastFlagMinThreshold and
25248 FastFlagMaxThreshold) to control the range of allowable bandwidths
25249 for the Fast directory flag. These allow authorities to run
25250 experiments on appropriate requirements for being a "Fast" node.
25251 The AuthDirFastGuarantee config value still applies. Implements
25253 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
25254 directory authority option (introduced in Tor 0.2.2.34).
25256 o Minor features (other):
25257 - Don't disable the DirPort when we cannot exceed our AccountingMax
25258 limit during this interval because the effective bandwidthrate is
25259 low enough. This is useful in a situation where AccountMax is only
25260 used as an additional safeguard or to provide statistics.
25261 - Prepend an informative header to generated dynamic_dh_params files.
25262 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
25263 EntryNodes will have no effect. Resolves issue 2571.
25264 - Log more useful messages when we fail to disable debugger
25266 - Log which authority we're missing votes from when we go to fetch
25267 them from the other auths.
25268 - Log (at debug level) whenever a circuit's purpose is changed.
25269 - Add missing documentation for the MaxClientCircuitsPending,
25270 UseMicrodescriptors, UserspaceIOCPBuffers, and
25271 _UseFilteringSSLBufferevents options, all introduced during
25272 the 0.2.3.x series.
25273 - Update to the January 3 2012 Maxmind GeoLite Country database.
25275 o Minor bugfixes (hidden services):
25276 - Don't close hidden service client circuits which have almost
25277 finished connecting to their destination when they reach
25278 the normal circuit-build timeout. Previously, we would close
25279 introduction circuits which are waiting for an acknowledgement
25280 from the introduction point, and rendezvous circuits which have
25281 been specified in an INTRODUCE1 cell sent to a hidden service,
25282 after the normal CBT. Now, we mark them as 'timed out', and launch
25283 another rendezvous attempt in parallel. This behavior change can
25284 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
25285 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
25286 - Don't close hidden-service-side rendezvous circuits when they
25287 reach the normal circuit-build timeout. This behavior change can
25288 be disabled using the new
25289 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
25290 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
25291 - Make sure we never mark the wrong rendezvous circuit as having
25292 had its introduction cell acknowledged by the introduction-point
25293 relay. Previously, when we received an INTRODUCE_ACK cell on a
25294 client-side hidden-service introduction circuit, we might have
25295 marked a rendezvous circuit other than the one we specified in
25296 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
25297 a warning message and interfered with the hidden service
25298 connection-establishment process. Fixes bug 4759; bugfix on
25299 0.2.3.3-alpha, when we added the stream-isolation feature which
25300 might cause Tor to open multiple rendezvous circuits for the same
25302 - Don't trigger an assertion failure when we mark a new client-side
25303 hidden-service introduction circuit for close during the process
25304 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
25307 o Minor bugfixes (log messages):
25308 - Correctly spell "connect" in a log message on failure to create a
25309 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
25311 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
25312 Fixes bug 4856; bugfix on Tor 0.0.6.
25313 - Fix the log message describing how we work around discovering
25314 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
25315 4837; bugfix on 0.2.2.9-alpha.
25316 - When logging about a disallowed .exit name, do not also call it
25317 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
25319 o Minor bugfixes (build fixes):
25320 - During configure, detect when we're building with clang version
25321 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
25322 CFLAGS. clang doesn't support them yet.
25323 - During configure, search for library containing cos function as
25324 libm lives in libcore on some platforms (BeOS/Haiku). Linking
25325 against libm was hard-coded before. Fixes the first part of bug
25326 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
25328 - Detect attempts to build Tor on (as yet hypothetical) versions
25329 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
25330 fix for bug 4533. Bugfix on 0.2.2.28-beta.
25331 - Preprocessor directives should not be put inside the arguments
25332 of a macro. This would break compilation with GCC releases prior
25333 to version 3.3. We would never recommend such an old GCC version,
25334 but it is apparently required for binary compatibility on some
25335 platforms (namely, certain builds of Haiku). Fixes the other part
25336 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
25339 o Minor bugfixes (other):
25340 - Older Linux kernels erroneously respond to strange nmap behavior
25341 by having accept() return successfully with a zero-length
25342 socket. When this happens, just close the connection. Previously,
25343 we would try harder to learn the remote address: but there was
25344 no such remote address to learn, and our method for trying to
25345 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
25346 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
25347 - Fix null-pointer access that could occur if TLS allocation failed.
25348 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
25349 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
25350 accidentally been reverted.
25351 - Fix our implementation of crypto_random_hostname() so it can't
25352 overflow on ridiculously large inputs. (No Tor version has ever
25353 provided this kind of bad inputs, but let's be correct in depth.)
25354 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
25355 - Find more places in the code that should have been testing for
25356 invalid sockets using the SOCKET_OK macro. Required for a fix
25357 for bug 4533. Bugfix on 0.2.2.28-beta.
25358 - Fix an assertion failure when, while running with bufferevents, a
25359 connection finishes connecting after it is marked for close, but
25360 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
25361 - test_util_spawn_background_ok() hardcoded the expected value
25362 for ENOENT to 2. This isn't portable as error numbers are
25363 platform specific, and particularly the hurd has ENOENT at
25364 0x40000002. Construct expected string at runtime, using the correct
25365 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
25366 - Reject attempts to disable DisableDebuggerAttachment while Tor is
25367 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
25368 - Use an appropriate-width type for sockets in tor-fw-helper on
25369 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
25372 - When sending or relaying a RELAY_EARLY cell, we used to convert
25373 it to a RELAY cell if the connection was using the v1 link
25374 protocol. This was a workaround for older versions of Tor, which
25375 didn't handle RELAY_EARLY cells properly. Now that all supported
25376 versions can handle RELAY_EARLY cells, and now that we're enforcing
25377 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
25378 remove this workaround. Addresses bug 4786.
25380 o Code simplifications and refactoring:
25381 - Use OpenSSL's built-in SSL_state_string_long() instead of our
25382 own homebrewed ssl_state_to_string() replacement. Patch from
25383 Emile Snyder. Fixes bug 4653.
25384 - Use macros to indicate OpenSSL versions, so we don't need to worry
25385 about accidental hexadecimal bit shifts.
25386 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
25388 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
25389 - Use the smartlist_add_asprintf() alias more consistently.
25390 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
25391 invalid value, rather than just -1.
25392 - Rename a handful of old identifiers, mostly related to crypto
25393 structures and crypto functions. By convention, our "create an
25394 object" functions are called "type_new()", our "free an object"
25395 functions are called "type_free()", and our types indicate that
25396 they are types only with a final "_t". But a handful of older
25397 types and functions broke these rules, with function names like
25398 "type_create" or "subsystem_op_type", or with type names like
25402 Changes in version 0.2.3.10-alpha - 2011-12-16
25403 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
25404 Tor's buffers code. Absolutely everybody should upgrade.
25406 The bug relied on an incorrect calculation when making data continuous
25407 in one of our IO buffers, if the first chunk of the buffer was
25408 misaligned by just the wrong amount. The miscalculation would allow an
25409 attacker to overflow a piece of heap-allocated memory. To mount this
25410 attack, the attacker would need to either open a SOCKS connection to
25411 Tor's SocksPort (usually restricted to localhost), or target a Tor
25412 instance configured to make its connections through a SOCKS proxy
25413 (which Tor does not do by default).
25415 Good security practice requires that all heap-overflow bugs should be
25416 presumed to be exploitable until proven otherwise, so we are treating
25417 this as a potential code execution attack. Please upgrade immediately!
25418 This bug does not affect bufferevents-based builds of Tor. Special
25419 thanks to "Vektor" for reporting this issue to us!
25421 This release also contains a few minor bugfixes for issues discovered
25425 - Fix a heap overflow bug that could occur when trying to pull
25426 data into the first chunk of a buffer, when that chunk had
25427 already had some data drained from it. Fixes CVE-2011-2778;
25428 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
25431 - If we can't attach streams to a rendezvous circuit when we
25432 finish connecting to a hidden service, clear the rendezvous
25433 circuit's stream-isolation state and try to attach streams
25434 again. Previously, we cleared rendezvous circuits' isolation
25435 state either too early (if they were freshly built) or not at all
25436 (if they had been built earlier and were cannibalized). Bugfix on
25437 0.2.3.3-alpha; fixes bug 4655.
25438 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
25439 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
25440 - Fix an assertion failure when a relay with accounting enabled
25441 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
25444 - Update to the December 6 2011 Maxmind GeoLite Country database.
25447 Changes in version 0.2.2.35 - 2011-12-16
25448 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
25449 buffers code. Absolutely everybody should upgrade.
25451 The bug relied on an incorrect calculation when making data continuous
25452 in one of our IO buffers, if the first chunk of the buffer was
25453 misaligned by just the wrong amount. The miscalculation would allow an
25454 attacker to overflow a piece of heap-allocated memory. To mount this
25455 attack, the attacker would need to either open a SOCKS connection to
25456 Tor's SocksPort (usually restricted to localhost), or target a Tor
25457 instance configured to make its connections through a SOCKS proxy
25458 (which Tor does not do by default).
25460 Good security practice requires that all heap-overflow bugs should be
25461 presumed to be exploitable until proven otherwise, so we are treating
25462 this as a potential code execution attack. Please upgrade immediately!
25463 This bug does not affect bufferevents-based builds of Tor. Special
25464 thanks to "Vektor" for reporting this issue to us!
25466 Tor 0.2.2.35 also fixes several bugs in previous versions, including
25467 crash bugs for unusual configurations, and a long-term bug that
25468 would prevent Tor from starting on Windows machines with draconian
25471 With this release, we remind everyone that 0.2.0.x has reached its
25472 formal end-of-life. Those Tor versions have many known flaws, and
25473 nobody should be using them. You should upgrade -- ideally to the
25474 0.2.2.x series. If you're using a Linux or BSD and its packages are
25475 obsolete, stop using those packages and upgrade anyway.
25477 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
25478 longer receive support after some time in early 2012.
25481 - Fix a heap overflow bug that could occur when trying to pull
25482 data into the first chunk of a buffer, when that chunk had
25483 already had some data drained from it. Fixes CVE-2011-2778;
25484 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
25485 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
25486 that it doesn't attempt to allocate a socketpair. This could cause
25487 some problems on Windows systems with overzealous firewalls. Fix for
25488 bug 4457; workaround for Libevent versions 2.0.1-alpha through
25490 - If we mark an OR connection for close based on a cell we process,
25491 don't process any further cells on it. We already avoid further
25492 reads on marked-for-close connections, but now we also discard the
25493 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
25494 which was the first version where we might mark a connection for
25495 close based on processing a cell on it.
25496 - Correctly sanity-check that we don't underflow on a memory
25497 allocation (and then assert) for hidden service introduction
25498 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
25499 bugfix on 0.2.1.5-alpha.
25500 - Fix a memory leak when we check whether a hidden service
25501 descriptor has any usable introduction points left. Fixes bug
25502 4424. Bugfix on 0.2.2.25-alpha.
25503 - Don't crash when we're running as a relay and don't have a GeoIP
25504 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
25505 we've had in the 0.2.3.x branch already.
25506 - When running as a client, do not print a misleading (and plain
25507 wrong) log message that we're collecting "directory request"
25508 statistics: clients don't collect statistics. Also don't create a
25509 useless (because empty) stats file in the stats/ directory. Fixes
25510 bug 4353; bugfix on 0.2.2.34.
25513 - Detect failure to initialize Libevent. This fix provides better
25514 detection for future instances of bug 4457.
25515 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
25516 function. This was eating up hideously large amounts of time on some
25517 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
25518 - Resolve an integer overflow bug in smartlist_ensure_capacity().
25519 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
25521 - Don't warn about unused log_mutex in log.c when building with
25522 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
25523 0.1.0.6-rc which introduced --disable-threads.
25524 - When configuring, starting, or stopping an NT service, stop
25525 immediately after the service configuration attempt has succeeded
25526 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
25527 - When sending a NETINFO cell, include the original address
25528 received for the other side, not its canonical address. Found
25529 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
25530 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
25531 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
25532 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
25533 occurred when a client tried to fetch a descriptor for a bridge
25534 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
25535 - Backport fixes for a pair of compilation warnings on Windows.
25536 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
25537 - If we had ever tried to call tor_addr_to_str on an address of
25538 unknown type, we would have done a strdup on an uninitialized
25539 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
25540 Reported by "troll_un".
25541 - Correctly detect and handle transient lookup failures from
25542 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
25543 Reported by "troll_un".
25544 - Fix null-pointer access that could occur if TLS allocation failed.
25545 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
25546 - Use tor_socket_t type for listener argument to accept(). Fixes bug
25547 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
25550 - Add two new config options for directory authorities:
25551 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
25552 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
25553 that is always sufficient to satisfy the bandwidth requirement for
25554 the Guard flag. Now it will be easier for researchers to simulate
25555 Tor networks with different values. Resolves ticket 4484.
25556 - When Tor ignores a hidden service specified in its configuration,
25557 include the hidden service's directory in the warning message.
25558 Previously, we would only tell the user that some hidden service
25559 was ignored. Bugfix on 0.0.6; fixes bug 4426.
25560 - Update to the December 6 2011 Maxmind GeoLite Country database.
25562 o Packaging changes:
25563 - Make it easier to automate expert package builds on Windows,
25564 by removing an absolute path from makensis.exe command.
25567 Changes in version 0.2.1.32 - 2011-12-16
25568 Tor 0.2.1.32 backports important security and privacy fixes for
25569 oldstable. This release is intended only for package maintainers and
25570 others who cannot use the 0.2.2 stable series. All others should be
25571 using Tor 0.2.2.x or newer.
25573 The Tor 0.2.1.x series will reach formal end-of-life some time in
25574 early 2012; we will stop releasing patches for it then.
25576 o Major bugfixes (also included in 0.2.2.x):
25577 - Correctly sanity-check that we don't underflow on a memory
25578 allocation (and then assert) for hidden service introduction
25579 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
25580 bugfix on 0.2.1.5-alpha.
25581 - Fix a heap overflow bug that could occur when trying to pull
25582 data into the first chunk of a buffer, when that chunk had
25583 already had some data drained from it. Fixes CVE-2011-2778;
25584 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
25587 - Update to the December 6 2011 Maxmind GeoLite Country database.
25590 Changes in version 0.2.3.9-alpha - 2011-12-08
25591 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
25592 a "DisableNetwork" security feature that bundles can use to avoid
25593 touching the network until bridges are configured, moves forward on
25594 the pluggable transport design, fixes a flaw in the hidden service
25595 design that unnecessarily prevented clients with wrong clocks from
25596 reaching hidden services, and fixes a wide variety of other issues.
25599 - Clients can now connect to private bridges over IPv6. Bridges
25600 still need at least one IPv4 address in order to connect to
25601 other relays. Note that we don't yet handle the case where the
25602 user has two bridge lines for the same bridge (one IPv4, one
25603 IPv6). Implements parts of proposal 186.
25604 - New "DisableNetwork" config option to prevent Tor from launching any
25605 connections or accepting any connections except on a control port.
25606 Bundles and controllers can set this option before letting Tor talk
25607 to the rest of the network, for example to prevent any connections
25608 to a non-bridge address. Packages like Orbot can also use this
25609 option to instruct Tor to save power when the network is off.
25610 - Clients and bridges can now be configured to use a separate
25611 "transport" proxy. This approach makes the censorship arms race
25612 easier by allowing bridges to use protocol obfuscation plugins. It
25613 implements the "managed proxy" part of proposal 180 (ticket 3472).
25614 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
25615 implementation. It makes AES_CTR about 7% faster than our old one
25616 (which was about 10% faster than the one OpenSSL used to provide).
25617 Resolves ticket 4526.
25618 - Add a "tor2web mode" for clients that want to connect to hidden
25619 services non-anonymously (and possibly more quickly). As a safety
25620 measure to try to keep users from turning this on without knowing
25621 what they are doing, tor2web mode must be explicitly enabled at
25622 compile time, and a copy of Tor compiled to run in tor2web mode
25623 cannot be used as a normal Tor client. Implements feature 2553.
25624 - Add experimental support for running on Windows with IOCP and no
25625 kernel-space socket buffers. This feature is controlled by a new
25626 "UserspaceIOCPBuffers" config option (off by default), which has
25627 no effect unless Tor has been built with support for bufferevents,
25628 is running on Windows, and has enabled IOCP. This may, in the long
25629 run, help solve or mitigate bug 98.
25630 - Use a more secure consensus parameter voting algorithm. Now at
25631 least three directory authorities or a majority of them must
25632 vote on a given parameter before it will be included in the
25633 consensus. Implements proposal 178.
25636 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
25637 They used to check that the timestamp was within 30 minutes
25638 of their system clock, so they could cap the size of their
25639 replay-detection cache, but that approach unnecessarily refused
25640 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
25641 the v3 intro-point protocol (the first one which sent a timestamp
25642 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
25643 - Only use the EVP interface when AES acceleration is enabled,
25644 to avoid a 5-7% performance regression. Resolves issue 4525;
25645 bugfix on 0.2.3.8-alpha.
25647 o Privacy/anonymity features (bridge detection):
25648 - Make bridge SSL certificates a bit more stealthy by using random
25649 serial numbers, in the same fashion as OpenSSL when generating
25650 self-signed certificates. Implements ticket 4584.
25651 - Introduce a new config option "DynamicDHGroups", enabled by
25652 default, which provides each bridge with a unique prime DH modulus
25653 to be used during SSL handshakes. This option attempts to help
25654 against censors who might use the Apache DH modulus as a static
25655 identifier for bridges. Addresses ticket 4548.
25657 o Minor features (new/different config options):
25658 - New configuration option "DisableDebuggerAttachment" (on by default)
25659 to prevent basic debugging attachment attempts by other processes.
25660 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
25661 - Allow MapAddress directives to specify matches against super-domains,
25662 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
25663 Implements issue 933.
25664 - Slightly change behavior of "list" options (that is, config
25665 options that can appear more than once) when they appear both in
25666 torrc and on the command line. Previously, the command-line options
25667 would be appended to the ones from torrc. Now, the command-line
25668 options override the torrc options entirely. This new behavior
25669 allows the user to override list options (like exit policies and
25670 ports to listen on) from the command line, rather than simply
25671 appending to the list.
25672 - You can get the old (appending) command-line behavior for "list"
25673 options by prefixing the option name with a "+".
25674 - You can remove all the values for a "list" option from the command
25675 line without adding any new ones by prefixing the option name
25677 - Add experimental support for a "defaults" torrc file to be parsed
25678 before the regular torrc. Torrc options override the defaults file's
25679 options in the same way that the command line overrides the torrc.
25680 The SAVECONF controller command saves only those options which
25681 differ between the current configuration and the defaults file. HUP
25682 reloads both files. (Note: This is an experimental feature; its
25683 behavior will probably be refined in future 0.2.3.x-alpha versions
25684 to better meet packagers' needs.) Implements task 4552.
25687 - Try to make the introductory warning message that Tor prints on
25688 startup more useful for actually finding help and information.
25689 Resolves ticket 2474.
25690 - Running "make version" now displays the version of Tor that
25691 we're about to build. Idea from katmagic; resolves issue 4400.
25692 - Expire old or over-used hidden service introduction points.
25693 Required by fix for bug 3460.
25694 - Move the replay-detection cache for the RSA-encrypted parts of
25695 INTRODUCE2 cells to the introduction point data structures.
25696 Previously, we would use one replay-detection cache per hidden
25697 service. Required by fix for bug 3460.
25698 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
25699 public key replay-detection cache from 60 minutes to 5 minutes. This
25700 replay-detection cache is now used only to detect multiple
25701 INTRODUCE2 cells specifying the same rendezvous point, so we can
25702 avoid launching multiple simultaneous attempts to connect to it.
25704 o Minor bugfixes (on Tor 0.2.2.x and earlier):
25705 - Resolve an integer overflow bug in smartlist_ensure_capacity().
25706 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
25708 - Fix a minor formatting issue in one of tor-gencert's error messages.
25710 - Prevent a false positive from the check-spaces script, by disabling
25711 the "whitespace between function name and (" check for functions
25713 - Fix a log message suggesting that people contact a non-existent
25714 email address. Fixes bug 3448.
25715 - Fix null-pointer access that could occur if TLS allocation failed.
25716 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
25717 - Report a real bootstrap problem to the controller on router
25718 identity mismatch. Previously we just said "foo", which probably
25719 made a lot of sense at the time. Fixes bug 4169; bugfix on
25721 - If we had ever tried to call tor_addr_to_str() on an address of
25722 unknown type, we would have done a strdup() on an uninitialized
25723 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
25724 Reported by "troll_un".
25725 - Correctly detect and handle transient lookup failures from
25726 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
25727 Reported by "troll_un".
25728 - Use tor_socket_t type for listener argument to accept(). Fixes bug
25729 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
25730 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
25731 bug 4532; found by "troll_un".
25733 o Minor bugfixes (on Tor 0.2.3.x):
25734 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
25736 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
25737 circuit for use as a hidden service client's rendezvous point.
25738 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
25739 with help from wanoskarnet.
25740 - Restore behavior of overriding SocksPort, ORPort, and similar
25741 options from the command line. Bugfix on 0.2.3.3-alpha.
25744 - Properly handle the case where the build-tree is not the same
25745 as the source tree when generating src/common/common_sha1.i,
25746 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
25747 bugfix on 0.2.0.1-alpha.
25749 o Code simplifications, cleanups, and refactorings:
25750 - Remove the pure attribute from all functions that used it
25751 previously. In many cases we assigned it incorrectly, because the
25752 functions might assert or call impure functions, and we don't have
25753 evidence that keeping the pure attribute is worthwhile. Implements
25754 changes suggested in ticket 4421.
25755 - Remove some dead code spotted by coverity. Fixes cid 432.
25756 Bugfix on 0.2.3.1-alpha, closes bug 4637.
25759 Changes in version 0.2.3.8-alpha - 2011-11-22
25760 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
25761 socketpair-related bug that has been bothering Windows users. It adds
25762 support to serve microdescriptors to controllers, so Vidalia's network
25763 map can resume listing relays (once Vidalia implements its side),
25764 and adds better support for hardware AES acceleration. Finally, it
25765 starts the process of adjusting the bandwidth cutoff for getting the
25766 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
25767 that tiny relays harm performance more than they help network capacity.
25770 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
25771 that it doesn't attempt to allocate a socketpair. This could cause
25772 some problems on Windows systems with overzealous firewalls. Fix for
25773 bug 4457; workaround for Libevent versions 2.0.1-alpha through
25775 - Correctly sanity-check that we don't underflow on a memory
25776 allocation (and then assert) for hidden service introduction
25777 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
25778 bugfix on 0.2.1.5-alpha.
25779 - Remove the artificially low cutoff of 20KB to guarantee the Fast
25780 flag. In the past few years the average relay speed has picked
25781 up, and while the "top 7/8 of the network get the Fast flag" and
25782 "all relays with 20KB or more of capacity get the Fast flag" rules
25783 used to have the same result, now the top 7/8 of the network has
25784 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
25785 - Fix a rare assertion failure when checking whether a v0 hidden
25786 service descriptor has any usable introduction points left, and
25787 we don't have enough information to build a circuit to the first
25788 intro point named in the descriptor. The HS client code in
25789 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
25790 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
25791 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
25792 - Make bridge authorities not crash when they are asked for their own
25793 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
25794 - When running as a client, do not print a misleading (and plain
25795 wrong) log message that we're collecting "directory request"
25796 statistics: clients don't collect statistics. Also don't create a
25797 useless (because empty) stats file in the stats/ directory. Fixes
25798 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
25801 - Allow Tor controllers like Vidalia to obtain the microdescriptor
25802 for a relay by identity digest or nickname. Previously,
25803 microdescriptors were only available by their own digests, so a
25804 controller would have to ask for and parse the whole microdescriptor
25805 consensus in order to look up a single relay's microdesc. Fixes
25806 bug 3832; bugfix on 0.2.3.1-alpha.
25807 - Use OpenSSL's EVP interface for AES encryption, so that all AES
25808 operations can use hardware acceleration (if present). Resolves
25811 o Minor bugfixes (on 0.2.2.x and earlier):
25812 - Detect failure to initialize Libevent. This fix provides better
25813 detection for future instances of bug 4457.
25814 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
25815 function. This was eating up hideously large amounts of time on some
25816 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
25817 - Don't warn about unused log_mutex in log.c when building with
25818 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
25819 0.1.0.6-rc which introduced --disable-threads.
25820 - Allow manual 'authenticate' commands to the controller interface
25821 from netcat (nc) as well as telnet. We were rejecting them because
25822 they didn't come with the expected whitespace at the end of the
25823 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
25824 - Fix some (not actually triggerable) buffer size checks in usage of
25825 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
25827 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
25828 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
25829 - When configuring, starting, or stopping an NT service, stop
25830 immediately after the service configuration attempt has succeeded
25831 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
25832 - When sending a NETINFO cell, include the original address
25833 received for the other side, not its canonical address. Found
25834 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
25835 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
25836 can pick them up when the tests aren't disabled. Bugfix on
25837 0.2.2.4-alpha which introduced tinytest.
25838 - Fix a memory leak when we check whether a hidden service
25839 descriptor has any usable introduction points left. Fixes bug
25840 4424. Bugfix on 0.2.2.25-alpha.
25841 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
25842 occurred when a client tried to fetch a descriptor for a bridge
25843 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
25845 o Minor bugfixes (on 0.2.3.x):
25846 - Make util unit tests build correctly with MSVC. Bugfix on
25847 0.2.3.3-alpha. Patch by Gisle Vanem.
25848 - Successfully detect AUTH_CHALLENGE cells with no recognized
25849 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
25850 Found by frosty_un.
25851 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
25852 it should still send a NETINFO cell to allow the connection to
25853 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
25855 - Log less loudly when we get an invalid authentication certificate
25856 from a source other than a directory authority: it's not unusual
25857 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
25859 - Tolerate servers with more clock skew in their authentication
25860 certificates than previously. Fixes bug 4371; bugfix on
25862 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
25863 on 0.2.3.4-alpha and 0.2.3.6-alpha.
25866 - Add two new config options for directory authorities:
25867 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
25868 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
25869 that is always sufficient to satisfy the bandwidth requirement for
25870 the Guard flag. Now it will be easier for researchers to simulate
25871 Tor networks with different values. Resolves ticket 4484.
25872 - When Tor ignores a hidden service specified in its configuration,
25873 include the hidden service's directory in the warning message.
25874 Previously, we would only tell the user that some hidden service
25875 was ignored. Bugfix on 0.0.6; fixes bug 4426.
25876 - When we fail to initialize Libevent, retry with IOCP disabled so we
25877 don't need to turn on multi-threading support in Libevent, which in
25878 turn requires a working socketpair(). This is a workaround for bug
25879 4457, which affects Libevent versions from 2.0.1-alpha through
25881 - Detect when we try to build on a platform that doesn't define
25882 AF_UNSPEC to 0. We don't work there, so refuse to compile.
25883 - Update to the November 1 2011 Maxmind GeoLite Country database.
25885 o Packaging changes:
25886 - Make it easier to automate expert package builds on Windows,
25887 by removing an absolute path from makensis.exe command.
25889 o Code simplifications and refactoring:
25890 - Remove some redundant #include directives throughout the code.
25891 Patch from Andrea Gelmini.
25892 - Unconditionally use OpenSSL's AES implementation instead of our
25893 old built-in one. OpenSSL's AES has been better for a while, and
25894 relatively few servers should still be on any version of OpenSSL
25895 that doesn't have good optimized assembly AES.
25896 - Use the name "CERTS" consistently to refer to the new cell type;
25897 we were calling it CERT in some places and CERTS in others.
25900 - Numerous new unit tests for functions in util.c and address.c by
25902 - The long-disabled benchmark tests are now split into their own
25903 ./src/test/bench binary.
25904 - The benchmark tests can now use more accurate timers than
25905 gettimeofday() when such timers are available.
25908 Changes in version 0.2.3.7-alpha - 2011-10-30
25909 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
25910 the new v3 handshake. It also resolves yet another bridge address
25914 - If we mark an OR connection for close based on a cell we process,
25915 don't process any further cells on it. We already avoid further
25916 reads on marked-for-close connections, but now we also discard the
25917 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
25918 which was the first version where we might mark a connection for
25919 close based on processing a cell on it.
25920 - Fix a double-free bug that would occur when we received an invalid
25921 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
25922 bugfix on 0.2.3.6-alpha.
25923 - Bridges no longer include their address in NETINFO cells on outgoing
25924 OR connections, to allow them to blend in better with clients.
25925 Removes another avenue for enumerating bridges. Reported by
25926 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
25927 cells were introduced.
25930 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
25931 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
25934 Changes in version 0.2.3.6-alpha - 2011-10-26
25935 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
25936 anonymity vulnerability where an attacker can deanonymize Tor
25937 users. Everybody should upgrade.
25939 This release also features support for a new v3 connection handshake
25940 protocol, and fixes to make hidden service connections more robust.
25943 - Implement a new handshake protocol (v3) for authenticating Tors to
25944 each other over TLS. It should be more resistant to fingerprinting
25945 than previous protocols, and should require less TLS hacking for
25946 future Tor implementations. Implements proposal 176.
25947 - Allow variable-length padding cells to disguise the length of
25948 Tor's TLS records. Implements part of proposal 184.
25950 o Privacy/anonymity fixes (clients):
25951 - Clients and bridges no longer send TLS certificate chains on
25952 outgoing OR connections. Previously, each client or bridge would
25953 use the same cert chain for all outgoing OR connections until
25954 its IP address changes, which allowed any relay that the client
25955 or bridge contacted to determine which entry guards it is using.
25956 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
25957 - If a relay receives a CREATE_FAST cell on a TLS connection, it
25958 no longer considers that connection as suitable for satisfying a
25959 circuit EXTEND request. Now relays can protect clients from the
25960 CVE-2011-2768 issue even if the clients haven't upgraded yet.
25961 - Directory authorities no longer assign the Guard flag to relays
25962 that haven't upgraded to the above "refuse EXTEND requests
25963 to client connections" fix. Now directory authorities can
25964 protect clients from the CVE-2011-2768 issue even if neither
25965 the clients nor the relays have upgraded yet. There's a new
25966 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
25967 to let us transition smoothly, else tomorrow there would be no
25970 o Major bugfixes (hidden services):
25971 - Improve hidden service robustness: when an attempt to connect to
25972 a hidden service ends, be willing to refetch its hidden service
25973 descriptors from each of the HSDir relays responsible for them
25974 immediately. Previously, we would not consider refetching the
25975 service's descriptors from each HSDir for 15 minutes after the last
25976 fetch, which was inconvenient if the hidden service was not running
25977 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
25978 - When one of a hidden service's introduction points appears to be
25979 unreachable, stop trying it. Previously, we would keep trying
25980 to build circuits to the introduction point until we lost the
25981 descriptor, usually because the user gave up and restarted Tor.
25982 Partly fixes bug 3825.
25983 - Don't launch a useless circuit after failing to use one of a
25984 hidden service's introduction points. Previously, we would
25985 launch a new introduction circuit, but not set the hidden service
25986 which that circuit was intended to connect to, so it would never
25987 actually be used. A different piece of code would then create a
25988 new introduction circuit correctly. Bug reported by katmagic and
25989 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
25991 o Major bugfixes (other):
25992 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
25993 that they initiated. Relays could distinguish incoming bridge
25994 connections from client connections, creating another avenue for
25995 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
25996 Found by "frosty_un".
25997 - Don't update the AccountingSoftLimitHitAt state file entry whenever
25998 tor gets started. This prevents a wrong average bandwidth
25999 estimate, which would cause relays to always start a new accounting
26000 interval at the earliest possible moment. Fixes bug 2003; bugfix
26001 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
26002 immensely in tracking this bug down.
26003 - Fix a crash bug when changing node restrictions while a DNS lookup
26004 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
26007 o Minor bugfixes (on 0.2.2.x and earlier):
26008 - When a hidden service turns an extra service-side introduction
26009 circuit into a general-purpose circuit, free the rend_data and
26010 intro_key fields first, so we won't leak memory if the circuit
26011 is cannibalized for use as another service-side introduction
26012 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
26013 - Rephrase the log message emitted if the TestSocks check is
26014 successful. Patch from Fabian Keil; fixes bug 4094.
26015 - Bridges now skip DNS self-tests, to act a little more stealthily.
26016 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
26017 bridges. Patch by "warms0x".
26018 - Remove a confusing dollar sign from the example fingerprint in the
26019 man page, and also make the example fingerprint a valid one. Fixes
26020 bug 4309; bugfix on 0.2.1.3-alpha.
26021 - Fix internal bug-checking logic that was supposed to catch
26022 failures in digest generation so that it will fail more robustly
26023 if we ask for a nonexistent algorithm. Found by Coverity Scan.
26024 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
26025 - Report any failure in init_keys() calls launched because our
26026 IP address has changed. Spotted by Coverity Scan. Bugfix on
26027 0.1.1.4-alpha; fixes CID 484.
26029 o Minor bugfixes (on 0.2.3.x):
26030 - Fix a bug in configure.in that kept it from building a configure
26031 script with autoconf versions earlier than 2.61. Fixes bug 2430;
26032 bugfix on 0.2.3.1-alpha.
26033 - Don't warn users that they are exposing a client port to the
26034 Internet if they have specified an RFC1918 address. Previously,
26035 we would warn if the user had specified any non-loopback
26036 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
26037 - Fix memory leaks in the failing cases of the new SocksPort and
26038 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
26039 fixes coverity CIDs 485, 486, and 487.
26042 - When a hidden service's introduction point times out, consider
26043 trying it again during the next attempt to connect to the
26044 HS. Previously, we would not try it again unless a newly fetched
26045 descriptor contained it. Required by fixes for bugs 1297 and 3825.
26046 - The next version of Windows will be called Windows 8, and it has
26047 a major version of 6, minor version of 2. Correctly identify that
26048 version instead of calling it "Very recent version". Resolves
26049 ticket 4153; reported by funkstar.
26050 - The Bridge Authority now writes statistics on how many bridge
26051 descriptors it gave out in total, and how many unique descriptors
26052 it gave out. It also lists how often the most and least commonly
26053 fetched descriptors were given out, as well as the median and
26054 25th/75th percentile. Implements tickets 4200 and 4294.
26055 - Update to the October 4 2011 Maxmind GeoLite Country database.
26057 o Code simplifications and refactoring:
26058 - Remove some old code to remember statistics about which descriptors
26059 we've served as a directory mirror. The feature wasn't used and
26060 is outdated now that microdescriptors are around.
26061 - Rename Tor functions that turn strings into addresses, so that
26062 "parse" indicates that no hostname resolution occurs, and
26063 "lookup" indicates that hostname resolution may occur. This
26064 should help prevent mistakes in the future. Fixes bug 3512.
26067 Changes in version 0.2.2.34 - 2011-10-26
26068 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
26069 can deanonymize Tor users. Everybody should upgrade.
26071 The attack relies on four components: 1) Clients reuse their TLS cert
26072 when talking to different relays, so relays can recognize a user by
26073 the identity key in her cert. 2) An attacker who knows the client's
26074 identity key can probe each guard relay to see if that identity key
26075 is connected to that guard relay right now. 3) A variety of active
26076 attacks in the literature (starting from "Low-Cost Traffic Analysis
26077 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
26078 discover the guard relays that a Tor user visiting the website is using.
26079 4) Clients typically pick three guards at random, so the set of guards
26080 for a given user could well be a unique fingerprint for her. This
26081 release fixes components #1 and #2, which is enough to block the attack;
26082 the other two remain as open research problems. Special thanks to
26083 "frosty_un" for reporting the issue to us!
26085 Clients should upgrade so they are no longer recognizable by the TLS
26086 certs they present. Relays should upgrade so they no longer allow a
26087 remote attacker to probe them to test whether unpatched clients are
26088 currently connected to them.
26090 This release also fixes several vulnerabilities that allow an attacker
26091 to enumerate bridge relays. Some bridge enumeration attacks still
26092 remain; see for example proposal 188.
26094 o Privacy/anonymity fixes (clients):
26095 - Clients and bridges no longer send TLS certificate chains on
26096 outgoing OR connections. Previously, each client or bridge would
26097 use the same cert chain for all outgoing OR connections until
26098 its IP address changes, which allowed any relay that the client
26099 or bridge contacted to determine which entry guards it is using.
26100 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
26101 - If a relay receives a CREATE_FAST cell on a TLS connection, it
26102 no longer considers that connection as suitable for satisfying a
26103 circuit EXTEND request. Now relays can protect clients from the
26104 CVE-2011-2768 issue even if the clients haven't upgraded yet.
26105 - Directory authorities no longer assign the Guard flag to relays
26106 that haven't upgraded to the above "refuse EXTEND requests
26107 to client connections" fix. Now directory authorities can
26108 protect clients from the CVE-2011-2768 issue even if neither
26109 the clients nor the relays have upgraded yet. There's a new
26110 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
26111 to let us transition smoothly, else tomorrow there would be no
26114 o Privacy/anonymity fixes (bridge enumeration):
26115 - Bridge relays now do their directory fetches inside Tor TLS
26116 connections, like all the other clients do, rather than connecting
26117 directly to the DirPort like public relays do. Removes another
26118 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
26119 - Bridges relays now build circuits for themselves in a more similar
26120 way to how clients build them. Removes another avenue for
26121 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
26122 when bridges were introduced.
26123 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
26124 that they initiated. Relays could distinguish incoming bridge
26125 connections from client connections, creating another avenue for
26126 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
26127 Found by "frosty_un".
26130 - Fix a crash bug when changing node restrictions while a DNS lookup
26131 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
26133 - Don't launch a useless circuit after failing to use one of a
26134 hidden service's introduction points. Previously, we would
26135 launch a new introduction circuit, but not set the hidden service
26136 which that circuit was intended to connect to, so it would never
26137 actually be used. A different piece of code would then create a
26138 new introduction circuit correctly. Bug reported by katmagic and
26139 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
26142 - Change an integer overflow check in the OpenBSD_Malloc code so
26143 that GCC is less likely to eliminate it as impossible. Patch
26144 from Mansour Moufid. Fixes bug 4059.
26145 - When a hidden service turns an extra service-side introduction
26146 circuit into a general-purpose circuit, free the rend_data and
26147 intro_key fields first, so we won't leak memory if the circuit
26148 is cannibalized for use as another service-side introduction
26149 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
26150 - Bridges now skip DNS self-tests, to act a little more stealthily.
26151 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
26152 bridges. Patch by "warms0x".
26153 - Fix internal bug-checking logic that was supposed to catch
26154 failures in digest generation so that it will fail more robustly
26155 if we ask for a nonexistent algorithm. Found by Coverity Scan.
26156 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
26157 - Report any failure in init_keys() calls launched because our
26158 IP address has changed. Spotted by Coverity Scan. Bugfix on
26159 0.1.1.4-alpha; fixes CID 484.
26161 o Minor bugfixes (log messages and documentation):
26162 - Remove a confusing dollar sign from the example fingerprint in the
26163 man page, and also make the example fingerprint a valid one. Fixes
26164 bug 4309; bugfix on 0.2.1.3-alpha.
26165 - The next version of Windows will be called Windows 8, and it has
26166 a major version of 6, minor version of 2. Correctly identify that
26167 version instead of calling it "Very recent version". Resolves
26168 ticket 4153; reported by funkstar.
26169 - Downgrade log messages about circuit timeout calibration from
26170 "notice" to "info": they don't require or suggest any human
26171 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
26172 bugfix on 0.2.2.14-alpha.
26175 - Turn on directory request statistics by default and include them in
26176 extra-info descriptors. Don't break if we have no GeoIP database.
26177 Backported from 0.2.3.1-alpha; implements ticket 3951.
26178 - Update to the October 4 2011 Maxmind GeoLite Country database.
26181 Changes in version 0.2.1.31 - 2011-10-26
26182 Tor 0.2.1.31 backports important security and privacy fixes for
26183 oldstable. This release is intended only for package maintainers and
26184 others who cannot use the 0.2.2 stable series. All others should be
26185 using Tor 0.2.2.x or newer.
26187 o Security fixes (also included in 0.2.2.x):
26188 - Replace all potentially sensitive memory comparison operations
26189 with versions whose runtime does not depend on the data being
26190 compared. This will help resist a class of attacks where an
26191 adversary can use variations in timing information to learn
26192 sensitive data. Fix for one case of bug 3122. (Safe memcmp
26193 implementation by Robert Ransom based partially on code by DJB.)
26194 - Fix an assert in parsing router descriptors containing IPv6
26195 addresses. This one took down the directory authorities when
26196 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
26198 o Privacy/anonymity fixes (also included in 0.2.2.x):
26199 - Clients and bridges no longer send TLS certificate chains on
26200 outgoing OR connections. Previously, each client or bridge would
26201 use the same cert chain for all outgoing OR connections until
26202 its IP address changes, which allowed any relay that the client
26203 or bridge contacted to determine which entry guards it is using.
26204 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
26205 - If a relay receives a CREATE_FAST cell on a TLS connection, it
26206 no longer considers that connection as suitable for satisfying a
26207 circuit EXTEND request. Now relays can protect clients from the
26208 CVE-2011-2768 issue even if the clients haven't upgraded yet.
26209 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
26210 that they initiated. Relays could distinguish incoming bridge
26211 connections from client connections, creating another avenue for
26212 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
26213 Found by "frosty_un".
26214 - When receiving a hidden service descriptor, check that it is for
26215 the hidden service we wanted. Previously, Tor would store any
26216 hidden service descriptors that a directory gave it, whether it
26217 wanted them or not. This wouldn't have let an attacker impersonate
26218 a hidden service, but it did let directories pre-seed a client
26219 with descriptors that it didn't want. Bugfix on 0.0.6.
26220 - Avoid linkability based on cached hidden service descriptors: forget
26221 all hidden service descriptors cached as a client when processing a
26222 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
26223 - Make the bridge directory authority refuse to answer directory
26224 requests for "all" descriptors. It used to include bridge
26225 descriptors in its answer, which was a major information leak.
26226 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
26227 - Don't attach new streams to old rendezvous circuits after SIGNAL
26228 NEWNYM. Previously, we would keep using an existing rendezvous
26229 circuit if it remained open (i.e. if it were kept open by a
26230 long-lived stream, or if a new stream were attached to it before
26231 Tor could notice that it was old and no longer in use). Bugfix on
26232 0.1.1.15-rc; fixes bug 3375.
26234 o Minor bugfixes (also included in 0.2.2.x):
26235 - When we restart our relay, we might get a successful connection
26236 from the outside before we've started our reachability tests,
26237 triggering a warning: "ORPort found reachable, but I have no
26238 routerinfo yet. Failing to inform controller of success." This
26239 bug was harmless unless Tor is running under a controller
26240 like Vidalia, in which case the controller would never get a
26241 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
26243 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
26244 enabled. Fixes bug 1526.
26245 - Remove undocumented option "-F" from tor-resolve: it hasn't done
26246 anything since 0.2.1.16-rc.
26247 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
26248 None of the cases where we did this before were wrong, but by making
26249 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
26250 - Fix a rare crash bug that could occur when a client was configured
26251 with a large number of bridges. Fixes bug 2629; bugfix on
26252 0.2.1.2-alpha. Bugfix by trac user "shitlei".
26253 - Correct the warning displayed when a rendezvous descriptor exceeds
26254 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
26256 - Fix an uncommon assertion failure when running with DNSPort under
26257 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
26258 - When warning about missing zlib development packages during compile,
26259 give the correct package names. Bugfix on 0.2.0.1-alpha.
26260 - Require that introduction point keys and onion keys have public
26261 exponent 65537. Bugfix on 0.2.0.10-alpha.
26262 - Do not crash when our configuration file becomes unreadable, for
26263 example due to a permissions change, between when we start up
26264 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
26266 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
26268 - Always NUL-terminate the sun_path field of a sockaddr_un before
26269 passing it to the kernel. (Not a security issue: kernels are
26270 smart enough to reject bad sockaddr_uns.) Found by Coverity;
26271 CID #428. Bugfix on Tor 0.2.0.3-alpha.
26272 - Don't stack-allocate the list of supplementary GIDs when we're
26273 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
26274 could take up to 256K, which is way too much stack. Found by
26275 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
26277 o Minor bugfixes (only in 0.2.1.x):
26278 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
26279 rely on them. Bugfix on 0.2.1.30.
26280 - Use git revisions instead of svn revisions when generating our
26281 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
26283 o Minor features (also included in 0.2.2.x):
26284 - Adjust the expiration time on our SSL session certificates to
26285 better match SSL certs seen in the wild. Resolves ticket 4014.
26286 - Allow nameservers with IPv6 address. Resolves bug 2574.
26287 - Update to the October 4 2011 Maxmind GeoLite Country database.
26290 Changes in version 0.2.3.5-alpha - 2011-09-28
26291 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
26292 bridge relays; fixes an assertion error that many users started hitting
26293 today; and adds the ability to refill token buckets more often than
26294 once per second, allowing significant performance improvements.
26297 - Bridge relays now do their directory fetches inside Tor TLS
26298 connections, like all the other clients do, rather than connecting
26299 directly to the DirPort like public relays do. Removes another
26300 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
26301 - Bridges relays now build circuits for themselves in a more similar
26302 way to how clients build them. Removes another avenue for
26303 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
26304 when bridges were introduced.
26307 - Fix an "Assertion md->held_by_node == 1 failed" error that could
26308 occur when the same microdescriptor was referenced by two node_t
26309 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
26311 o Major features (networking):
26312 - Add a new TokenBucketRefillInterval option to refill token buckets
26313 more frequently than once per second. This should improve network
26314 performance, alleviate queueing problems, and make traffic less
26315 bursty. Implements proposal 183; closes ticket 3630. Design by
26316 Florian Tschorsch and Björn Scheuermann; implementation by
26320 - Change an integer overflow check in the OpenBSD_Malloc code so
26321 that GCC is less likely to eliminate it as impossible. Patch
26322 from Mansour Moufid. Fixes bug 4059.
26324 o Minor bugfixes (usability):
26325 - Downgrade log messages about circuit timeout calibration from
26326 "notice" to "info": they don't require or suggest any human
26327 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
26328 bugfix on 0.2.2.14-alpha.
26330 o Minor features (diagnostics):
26331 - When the system call to create a listener socket fails, log the
26332 error message explaining why. This may help diagnose bug 4027.
26335 Changes in version 0.2.3.4-alpha - 2011-09-13
26336 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
26337 tweak to Tor's TLS handshake that makes relays and bridges that run
26338 this new version reachable from Iran again. It also fixes a few new
26339 bugs in 0.2.3.x, and teaches relays to recognize when they're not
26340 listed in the network consensus and republish.
26342 o Major bugfixes (also part of 0.2.2.33):
26343 - Avoid an assertion failure when reloading a configuration with
26344 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
26345 3923; bugfix on 0.2.2.25-alpha.
26347 o Minor features (security, also part of 0.2.2.33):
26348 - Check for replays of the public-key encrypted portion of an
26349 INTRODUCE1 cell, in addition to the current check for replays of
26350 the g^x value. This prevents a possible class of active attacks
26351 by an attacker who controls both an introduction point and a
26352 rendezvous point, and who uses the malleability of AES-CTR to
26353 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
26354 that these attacks are infeasible (requiring the attacker to send
26355 on the order of zettabytes of altered cells in a short interval),
26356 but we'd rather block them off in case there are any classes of
26357 this attack that we missed. Reported by Willem Pinckaers.
26359 o Minor features (also part of 0.2.2.33):
26360 - Adjust the expiration time on our SSL session certificates to
26361 better match SSL certs seen in the wild. Resolves ticket 4014.
26362 - Change the default required uptime for a relay to be accepted as
26363 a HSDir (hidden service directory) from 24 hours to 25 hours.
26364 Improves on 0.2.0.10-alpha; resolves ticket 2649.
26365 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
26366 authorities to abstain from voting on assignment of the HSDir
26367 consensus flag. Related to bug 2649.
26368 - Update to the September 6 2011 Maxmind GeoLite Country database.
26370 o Minor bugfixes (also part of 0.2.2.33):
26371 - Demote the 'replay detected' log message emitted when a hidden
26372 service receives the same Diffie-Hellman public key in two different
26373 INTRODUCE2 cells to info level. A normal Tor client can cause that
26374 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
26375 fixes part of bug 2442.
26376 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
26377 level. There is nothing that a hidden service's operator can do
26378 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
26380 - Clarify a log message specifying the characters permitted in
26381 HiddenServiceAuthorizeClient client names. Previously, the log
26382 message said that "[A-Za-z0-9+-_]" were permitted; that could have
26383 given the impression that every ASCII character between "+" and "_"
26384 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
26386 o Build fixes (also part of 0.2.2.33):
26387 - Clean up some code issues that prevented Tor from building on older
26388 BSDs. Fixes bug 3894; reported by "grarpamp".
26389 - Search for a platform-specific version of "ar" when cross-compiling.
26390 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
26393 - Fix a bug where the SocksPort option (for example) would get
26394 ignored and replaced by the default if a SocksListenAddress
26395 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
26399 - Relays now try regenerating and uploading their descriptor more
26400 frequently if they are not listed in the consensus, or if the
26401 version of their descriptor listed in the consensus is too
26402 old. This fix should prevent situations where a server declines
26403 to re-publish itself because it has done so too recently, even
26404 though the authorities decided not to list its recent-enough
26405 descriptor. Fix for bug 3327.
26408 - Relays now include a reason for regenerating their descriptors
26409 in an HTTP header when uploading to the authorities. This will
26410 make it easier to debug descriptor-upload issues in the future.
26411 - When starting as root and then changing our UID via the User
26412 control option, and we have a ControlSocket configured, make sure
26413 that the ControlSocket is owned by the same account that Tor will
26414 run under. Implements ticket 3421; fix by Jérémy Bobbio.
26417 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
26418 utility function used in the control-port code). This shouldn't
26419 ever happen unless Tor is completely out of memory, but if it did
26420 happen and Tor somehow recovered from it, Tor could have sent a log
26421 message to a control port in the middle of a reply to a controller
26422 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
26423 - Make 'FetchUselessDescriptors' cause all descriptor types and
26424 all consensus types (including microdescriptors) to get fetched.
26425 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
26427 o Code refactoring:
26428 - Make a new "entry connection" struct as an internal subtype of "edge
26429 connection", to simplify the code and make exit connections smaller.
26432 Changes in version 0.2.2.33 - 2011-09-13
26433 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
26434 TLS handshake that makes relays and bridges that run this new version
26435 reachable from Iran again.
26438 - Avoid an assertion failure when reloading a configuration with
26439 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
26440 3923; bugfix on 0.2.2.25-alpha.
26442 o Minor features (security):
26443 - Check for replays of the public-key encrypted portion of an
26444 INTRODUCE1 cell, in addition to the current check for replays of
26445 the g^x value. This prevents a possible class of active attacks
26446 by an attacker who controls both an introduction point and a
26447 rendezvous point, and who uses the malleability of AES-CTR to
26448 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
26449 that these attacks are infeasible (requiring the attacker to send
26450 on the order of zettabytes of altered cells in a short interval),
26451 but we'd rather block them off in case there are any classes of
26452 this attack that we missed. Reported by Willem Pinckaers.
26455 - Adjust the expiration time on our SSL session certificates to
26456 better match SSL certs seen in the wild. Resolves ticket 4014.
26457 - Change the default required uptime for a relay to be accepted as
26458 a HSDir (hidden service directory) from 24 hours to 25 hours.
26459 Improves on 0.2.0.10-alpha; resolves ticket 2649.
26460 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
26461 authorities to abstain from voting on assignment of the HSDir
26462 consensus flag. Related to bug 2649.
26463 - Update to the September 6 2011 Maxmind GeoLite Country database.
26465 o Minor bugfixes (documentation and log messages):
26466 - Correct the man page to explain that HashedControlPassword and
26467 CookieAuthentication can both be set, in which case either method
26468 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
26469 when we decided to allow these config options to both be set. Issue
26470 raised by bug 3898.
26471 - Demote the 'replay detected' log message emitted when a hidden
26472 service receives the same Diffie-Hellman public key in two different
26473 INTRODUCE2 cells to info level. A normal Tor client can cause that
26474 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
26475 fixes part of bug 2442.
26476 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
26477 level. There is nothing that a hidden service's operator can do
26478 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
26480 - Clarify a log message specifying the characters permitted in
26481 HiddenServiceAuthorizeClient client names. Previously, the log
26482 message said that "[A-Za-z0-9+-_]" were permitted; that could have
26483 given the impression that every ASCII character between "+" and "_"
26484 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
26487 - Provide a substitute implementation of lround() for MSVC, which
26488 apparently lacks it. Patch from Gisle Vanem.
26489 - Clean up some code issues that prevented Tor from building on older
26490 BSDs. Fixes bug 3894; reported by "grarpamp".
26491 - Search for a platform-specific version of "ar" when cross-compiling.
26492 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
26495 Changes in version 0.2.3.3-alpha - 2011-09-01
26496 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
26497 security, and provides client-side support for the microdescriptor
26498 and optimistic data features introduced earlier in the 0.2.3.x
26499 series. It also includes numerous critical bugfixes in the (optional)
26500 bufferevent-based networking backend.
26502 o Major features (stream isolation):
26503 - You can now configure Tor so that streams from different
26504 applications are isolated on different circuits, to prevent an
26505 attacker who sees your streams as they leave an exit node from
26506 linking your sessions to one another. To do this, choose some way
26507 to distinguish the applications: have them connect to different
26508 SocksPorts, or have one of them use SOCKS4 while the other uses
26509 SOCKS5, or have them pass different authentication strings to the
26510 SOCKS proxy. Then, use the new SocksPort syntax to configure the
26511 degree of isolation you need. This implements Proposal 171.
26512 - There's a new syntax for specifying multiple client ports (such as
26513 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
26514 multiple *Port entries with full addr:port syntax on each.
26515 The old *ListenAddress format is still supported, but you can't
26516 mix it with the new *Port syntax.
26518 o Major features (other):
26519 - Enable microdescriptor fetching by default for clients. This allows
26520 clients to download a much smaller amount of directory information.
26521 To disable it (and go back to the old-style consensus and
26522 descriptors), set "UseMicrodescriptors 0" in your torrc file.
26523 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
26524 "PortForwarding" config option), now supports Windows.
26525 - When using an exit relay running 0.2.3.x, clients can now
26526 "optimistically" send data before the exit relay reports that
26527 the stream has opened. This saves a round trip when starting
26528 connections where the client speaks first (such as web browsing).
26529 This behavior is controlled by a consensus parameter (currently
26530 disabled). To turn it on or off manually, use the "OptimisticData"
26531 torrc option. Implements proposal 181; code by Ian Goldberg.
26533 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
26534 - When using IOCP on Windows, we need to enable Libevent windows
26536 - The IOCP backend now works even when the user has not specified
26537 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
26538 Fixes part of bug 3752.
26539 - Correctly record the bytes we've read and written when using
26540 bufferevents, so that we can include them in our bandwidth history
26541 and advertised bandwidth. Fixes bug 3803.
26542 - Apply rate-limiting only at the bottom of a chain of filtering
26543 bufferevents. This prevents us from filling up internal read
26544 buffers and violating rate-limits when filtering bufferevents
26545 are enabled. Fixes part of bug 3804.
26546 - Add high-watermarks to the output buffers for filtered
26547 bufferevents. This prevents us from filling up internal write
26548 buffers and wasting CPU cycles when filtering bufferevents are
26549 enabled. Fixes part of bug 3804.
26550 - Correctly notice when data has been written from a bufferevent
26551 without flushing it completely. Fixes bug 3805.
26552 - Fix a bug where server-side tunneled bufferevent-based directory
26553 streams would get closed prematurely. Fixes bug 3814.
26554 - Fix a use-after-free error with per-connection rate-limiting
26555 buckets. Fixes bug 3888.
26557 o Major bugfixes (also part of 0.2.2.31-rc):
26558 - If we're configured to write our ControlPorts to disk, only write
26559 them after switching UID and creating the data directory. This way,
26560 we don't fail when starting up with a nonexistent DataDirectory
26561 and a ControlPortWriteToFile setting based on that directory. Fixes
26562 bug 3747; bugfix on Tor 0.2.2.26-beta.
26565 - Added a new CONF_CHANGED event so that controllers can be notified
26566 of any configuration changes made by other controllers, or by the
26567 user. Implements ticket 1692.
26568 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
26569 leak when using bufferevents, and lets Libevent worry about how to
26570 best copy data out of a buffer.
26571 - Replace files in stats/ rather than appending to them. Now that we
26572 include statistics in extra-info descriptors, it makes no sense to
26573 keep old statistics forever. Implements ticket 2930.
26575 o Minor features (build compatibility):
26576 - Limited, experimental support for building with nmake and MSVC.
26577 - Provide a substitute implementation of lround() for MSVC, which
26578 apparently lacks it. Patch from Gisle Vanem.
26580 o Minor features (also part of 0.2.2.31-rc):
26581 - Update to the August 2 2011 Maxmind GeoLite Country database.
26583 o Minor bugfixes (on 0.2.3.x-alpha):
26584 - Fix a spurious warning when parsing SOCKS requests with
26585 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
26586 - Get rid of a harmless warning that could happen on relays running
26587 with bufferevents. The warning was caused by someone doing an http
26588 request to a relay's orport. Also don't warn for a few related
26589 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
26591 o Minor bugfixes (on 2.2.x and earlier):
26592 - Correct the man page to explain that HashedControlPassword and
26593 CookieAuthentication can both be set, in which case either method
26594 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
26595 when we decided to allow these config options to both be set. Issue
26596 raised by bug 3898.
26597 - The "--quiet" and "--hush" options now apply not only to Tor's
26598 behavior before logs are configured, but also to Tor's behavior in
26599 the absence of configured logs. Fixes bug 3550; bugfix on
26602 o Minor bugfixes (also part of 0.2.2.31-rc):
26603 - Write several files in text mode, on OSes that distinguish text
26604 mode from binary mode (namely, Windows). These files are:
26605 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
26606 that collect those statistics; 'client_keys' and 'hostname' for
26607 hidden services that use authentication; and (in the tor-gencert
26608 utility) newly generated identity and signing keys. Previously,
26609 we wouldn't specify text mode or binary mode, leading to an
26610 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
26611 the DirRecordUsageByCountry option which would have triggered
26612 the assertion failure was added), although this assertion failure
26613 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
26614 - Selectively disable deprecation warnings on OS X because Lion
26615 started deprecating the shipped copy of openssl. Fixes bug 3643.
26616 - Remove an extra pair of quotation marks around the error
26617 message in control-port STATUS_GENERAL BUG events. Bugfix on
26618 0.1.2.6-alpha; fixes bug 3732.
26619 - When unable to format an address as a string, report its value
26620 as "???" rather than reusing the last formatted address. Bugfix
26623 o Code simplifications and refactoring:
26624 - Rewrite the listener-selection logic so that parsing which ports
26625 we want to listen on is now separate from binding to the ports
26629 - Building Tor with bufferevent support now requires Libevent
26630 2.0.13-stable or later. Previous versions of Libevent had bugs in
26631 SSL-related bufferevents and related issues that would make Tor
26632 work badly with bufferevents. Requiring 2.0.13-stable also allows
26633 Tor with bufferevents to take advantage of Libevent APIs
26634 introduced after 2.0.8-rc.
26637 Changes in version 0.2.2.32 - 2011-08-27
26638 The Tor 0.2.2 release series is dedicated to the memory of Andreas
26639 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
26640 a founder of the PETS community, a leader in our field, a mentor,
26641 and a friend. He left us with these words: "I had the possibility
26642 to contribute to this world that is not as it should be. I hope I
26643 could help in some areas to make the world a better place, and that
26644 I could also encourage other people to be engaged in improving the
26645 world. Please, stay engaged. This world needs you, your love, your
26646 initiative -- now I cannot be part of that anymore."
26648 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
26649 ready. More than two years in the making, this release features improved
26650 client performance and hidden service reliability, better compatibility
26651 for Android, correct behavior for bridges that listen on more than
26652 one address, more extensible and flexible directory object handling,
26653 better reporting of network statistics, improved code security, and
26654 many many other features and bugfixes.
26657 Changes in version 0.2.2.31-rc - 2011-08-17
26658 Tor 0.2.2.31-rc is the second and hopefully final release candidate
26659 for the Tor 0.2.2.x series.
26662 - Remove an extra pair of quotation marks around the error
26663 message in control-port STATUS_GENERAL BUG events. Bugfix on
26664 0.1.2.6-alpha; fixes bug 3732.
26665 - If we're configured to write our ControlPorts to disk, only write
26666 them after switching UID and creating the data directory. This way,
26667 we don't fail when starting up with a nonexistent DataDirectory
26668 and a ControlPortWriteToFile setting based on that directory. Fixes
26669 bug 3747; bugfix on Tor 0.2.2.26-beta.
26672 - Update to the August 2 2011 Maxmind GeoLite Country database.
26675 - Allow GETINFO fingerprint to return a fingerprint even when
26676 we have not yet built a router descriptor. Fixes bug 3577;
26677 bugfix on 0.2.0.1-alpha.
26678 - Write several files in text mode, on OSes that distinguish text
26679 mode from binary mode (namely, Windows). These files are:
26680 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
26681 that collect those statistics; 'client_keys' and 'hostname' for
26682 hidden services that use authentication; and (in the tor-gencert
26683 utility) newly generated identity and signing keys. Previously,
26684 we wouldn't specify text mode or binary mode, leading to an
26685 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
26686 the DirRecordUsageByCountry option which would have triggered
26687 the assertion failure was added), although this assertion failure
26688 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
26689 - Selectively disable deprecation warnings on OS X because Lion
26690 started deprecating the shipped copy of openssl. Fixes bug 3643.
26691 - When unable to format an address as a string, report its value
26692 as "???" rather than reusing the last formatted address. Bugfix
26696 Changes in version 0.2.3.2-alpha - 2011-07-18
26697 Tor 0.2.3.2-alpha introduces two new experimental features:
26698 microdescriptors and pluggable transports. It also continues cleaning
26699 up a variety of recently introduced features.
26702 - Clients can now use microdescriptors instead of regular descriptors
26703 to build circuits. Microdescriptors are authority-generated
26704 summaries of regular descriptors' contents, designed to change
26705 very rarely (see proposal 158 for details). This feature is
26706 designed to save bandwidth, especially for clients on slow internet
26707 connections. It's off by default for now, since nearly no caches
26708 support it, but it will be on-by-default for clients in a future
26709 version. You can use the UseMicrodescriptors option to turn it on.
26710 - Tor clients using bridges can now be configured to use a separate
26711 'transport' proxy for each bridge. This approach helps to resist
26712 censorship by allowing bridges to use protocol obfuscation
26713 plugins. It implements part of proposal 180. Implements ticket 2841.
26714 - While we're trying to bootstrap, record how many TLS connections
26715 fail in each state, and report which states saw the most failures
26716 in response to any bootstrap failures. This feature may speed up
26717 diagnosis of censorship events. Implements ticket 3116.
26719 o Major bugfixes (on 0.2.3.1-alpha):
26720 - When configuring a large set of nodes in EntryNodes (as with
26721 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
26722 random subset to be guards, and choose them in random
26723 order. Fixes bug 2798.
26724 - Tor could crash when remembering a consensus in a non-used consensus
26725 flavor without having a current consensus set. Fixes bug 3361.
26726 - Comparing an unknown address to a microdescriptor's shortened exit
26727 policy would always give a "rejected" result. Fixes bug 3599.
26728 - Using microdescriptors as a client no longer prevents Tor from
26729 uploading and downloading hidden service descriptors. Fixes
26733 - Allow nameservers with IPv6 address. Resolves bug 2574.
26734 - Accept attempts to include a password authenticator in the
26735 handshake, as supported by SOCKS5. This handles SOCKS clients that
26736 don't know how to omit a password when authenticating. Resolves
26738 - When configuring a large set of nodes in EntryNodes, and there are
26739 enough of them listed as Guard so that we don't need to consider
26740 the non-guard entries, prefer the ones listed with the Guard flag.
26741 - Check for and recover from inconsistency in the microdescriptor
26742 cache. This will make it harder for us to accidentally free a
26743 microdescriptor without removing it from the appropriate data
26744 structures. Fixes issue 3135; issue noted by "wanoskarnet".
26745 - Log SSL state transitions at log level DEBUG, log domain
26746 HANDSHAKE. This can be useful for debugging censorship events.
26747 Implements ticket 3264.
26748 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
26749 implements ticket 3439.
26751 o Minor bugfixes (on 0.2.3.1-alpha):
26752 - Do not free all general-purpose regular descriptors just
26753 because microdescriptor use is enabled. Fixes bug 3113.
26754 - Correctly link libevent_openssl when --enable-static-libevent
26755 is passed to configure. Fixes bug 3118.
26756 - Bridges should not complain during their heartbeat log messages that
26757 they are unlisted in the consensus: that's more or less the point
26758 of being a bridge. Fixes bug 3183.
26759 - Report a SIGNAL event to controllers when acting on a delayed
26760 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
26761 event to the controller if we acted on a SIGNAL NEWNYM command
26762 immediately, and otherwise not report a SIGNAL event for the
26763 command at all. Fixes bug 3349.
26764 - Fix a crash when handling the SIGNAL controller command or
26765 reporting ERR-level status events with bufferevents enabled. Found
26766 by Robert Ransom. Fixes bug 3367.
26767 - Always ship the tor-fw-helper manpage in our release tarballs.
26768 Fixes bug 3389. Reported by Stephen Walker.
26769 - Fix a class of double-mark-for-close bugs when bufferevents
26770 are enabled. Fixes bug 3403.
26771 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
26772 - Add SIGNAL to the list returned by the 'GETINFO events/names'
26773 control-port command. Fixes part of bug 3465.
26774 - Prevent using negative indices during unit test runs when read_all()
26775 fails. Spotted by coverity.
26776 - Fix a rare memory leak when checking the nodelist without it being
26777 present. Found by coverity.
26778 - Only try to download a microdescriptor-flavored consensus from
26779 a directory cache that provides them.
26781 o Minor bugfixes (on 0.2.2.x and earlier):
26782 - Assert that hidden-service-related operations are not performed
26783 using single-hop circuits. Previously, Tor would assert that
26784 client-side streams are not attached to single-hop circuits,
26785 but not that other sensitive operations on the client and service
26786 side are not performed using single-hop circuits. Fixes bug 3332;
26788 - Don't publish a new relay descriptor when we reload our onion key,
26789 unless the onion key has actually changed. Fixes bug 3263 and
26790 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
26791 - Allow GETINFO fingerprint to return a fingerprint even when
26792 we have not yet built a router descriptor. Fixes bug 3577;
26793 bugfix on 0.2.0.1-alpha.
26794 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
26795 on 0.2.2.4-alpha; fixes bug 3427.
26797 o Code simplification and refactoring:
26798 - Use tor_sscanf() in place of scanf() in more places through the
26799 code. This makes us a little more locale-independent, and
26800 should help shut up code-analysis tools that can't tell
26801 a safe sscanf string from a dangerous one.
26802 - Use tt_assert(), not tor_assert(), for checking for test failures.
26803 This makes the unit tests more able to go on in the event that
26805 - Split connection_about_to_close() into separate functions for each
26809 - On Windows, we now define the _WIN32_WINNT macros only if they
26810 are not already defined. This lets the person building Tor decide,
26811 if they want, to require a later version of Windows.
26814 Changes in version 0.2.2.30-rc - 2011-07-07
26815 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
26816 series. It fixes a few smaller bugs, but generally appears stable.
26817 Please test it and let us know whether it is!
26820 - Send a SUCCEEDED stream event to the controller when a reverse
26821 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
26822 discovered by katmagic.
26823 - Always NUL-terminate the sun_path field of a sockaddr_un before
26824 passing it to the kernel. (Not a security issue: kernels are
26825 smart enough to reject bad sockaddr_uns.) Found by Coverity;
26826 CID #428. Bugfix on Tor 0.2.0.3-alpha.
26827 - Don't stack-allocate the list of supplementary GIDs when we're
26828 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
26829 could take up to 256K, which is way too much stack. Found by
26830 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
26831 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
26832 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
26833 fixes part of bug 3465.
26834 - Fix a memory leak when receiving a descriptor for a hidden
26835 service we didn't ask for. Found by Coverity; CID #30. Bugfix
26839 - Update to the July 1 2011 Maxmind GeoLite Country database.
26842 Changes in version 0.2.2.29-beta - 2011-06-20
26843 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
26844 have bridge lines in their torrc but don't want to use them; gets
26845 us closer to having the control socket feature working on Debian;
26846 and fixes a variety of smaller bugs.
26849 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
26850 When we changed the default behavior to "use bridges if any
26851 are listed in the torrc", we surprised users who had bridges
26852 in their torrc files but who didn't actually want to use them.
26853 Partial resolution for bug 3354.
26856 - Don't attach new streams to old rendezvous circuits after SIGNAL
26857 NEWNYM. Previously, we would keep using an existing rendezvous
26858 circuit if it remained open (i.e. if it were kept open by a
26859 long-lived stream, or if a new stream were attached to it before
26860 Tor could notice that it was old and no longer in use). Bugfix on
26861 0.1.1.15-rc; fixes bug 3375.
26864 - Fix a bug when using ControlSocketsGroupWritable with User. The
26865 directory's group would be checked against the current group, not
26866 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
26867 bugfix on 0.2.2.26-beta.
26868 - Make connection_printf_to_buf()'s behavior sane. Its callers
26869 expect it to emit a CRLF iff the format string ends with CRLF;
26870 it actually emitted a CRLF iff (a) the format string ended with
26871 CRLF or (b) the resulting string was over 1023 characters long or
26872 (c) the format string did not end with CRLF *and* the resulting
26873 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
26874 fixes part of bug 3407.
26875 - Make send_control_event_impl()'s behavior sane. Its callers
26876 expect it to always emit a CRLF at the end of the string; it
26877 might have emitted extra control characters as well. Bugfix on
26878 0.1.1.9-alpha; fixes another part of bug 3407.
26879 - Make crypto_rand_int() check the value of its input correctly.
26880 Previously, it accepted values up to UINT_MAX, but could return a
26881 negative number if given a value above INT_MAX+1. Found by George
26882 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
26883 - Avoid a segfault when reading a malformed circuit build state
26884 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
26886 - When asked about a DNS record type we don't support via a
26887 client DNSPort, reply with NOTIMPL rather than an empty
26888 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
26889 - Fix a rare memory leak during stats writing. Found by coverity.
26892 - Update to the June 1 2011 Maxmind GeoLite Country database.
26894 o Code simplifications and refactoring:
26895 - Remove some dead code as indicated by coverity.
26896 - Remove a few dead assignments during router parsing. Found by
26898 - Add some forgotten return value checks during unit tests. Found
26900 - Don't use 1-bit wide signed bit fields. Found by coverity.
26903 Changes in version 0.2.2.28-beta - 2011-06-04
26904 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
26905 fixed a big bug in whether relays stay in the consensus consistently,
26906 we moved closer to handling bridges and hidden services correctly,
26907 and we started the process of better handling the dreaded "my Vidalia
26908 died, and now my Tor demands a password when I try to reconnect to it"
26912 - Don't decide to make a new descriptor when receiving a HUP signal.
26913 This bug has caused a lot of 0.2.2.x relays to disappear from the
26914 consensus periodically. Fixes the most common case of triggering
26915 bug 1810; bugfix on 0.2.2.7-alpha.
26916 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
26917 - Don't try to build descriptors if "ORPort auto" is set and we
26918 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
26920 - Resolve a crash that occurred when setting BridgeRelay to 1 with
26921 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
26922 - Apply circuit timeouts to opened hidden-service-related circuits
26923 based on the correct start time. Previously, we would apply the
26924 circuit build timeout based on time since the circuit's creation;
26925 it was supposed to be applied based on time since the circuit
26926 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
26927 - Use the same circuit timeout for client-side introduction
26928 circuits as for other four-hop circuits, rather than the timeout
26929 for single-hop directory-fetch circuits; the shorter timeout may
26930 have been appropriate with the static circuit build timeout in
26931 0.2.1.x and earlier, but caused many hidden service access attempts
26932 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
26933 on 0.2.2.2-alpha; fixes another part of bug 1297.
26934 - In ticket 2511 we fixed a case where you could use an unconfigured
26935 bridge if you had configured it as a bridge the last time you ran
26936 Tor. Now fix another edge case: if you had configured it as a bridge
26937 but then switched to a different bridge via the controller, you
26938 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
26942 - Add an __OwningControllerProcess configuration option and a
26943 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
26944 that when it exits, Tor will shut down. Implements feature 3049.
26945 - If "UseBridges 1" is set and no bridges are configured, Tor will
26946 now refuse to build any circuits until some bridges are set.
26947 If "UseBridges auto" is set, Tor will use bridges if they are
26948 configured and we are not running as a server, but otherwise will
26949 make circuits as usual. The new default is "auto". Patch by anonym,
26950 so the Tails LiveCD can stop automatically revealing you as a Tor
26954 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
26955 - Remove a trailing asterisk from "exit-policy/default" in the
26956 output of the control port command "GETINFO info/names". Bugfix
26958 - Use a wide type to hold sockets when built for 64-bit Windows builds.
26960 - Warn when the user configures two HiddenServiceDir lines that point
26961 to the same directory. Bugfix on 0.0.6 (the version introducing
26962 HiddenServiceDir); fixes bug 3289.
26963 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
26964 part of bug 2748; bugfix on 0.2.0.10-alpha.
26965 - Log malformed requests for rendezvous descriptors as protocol
26966 warnings, not warnings. Also, use a more informative log message
26967 in case someone sees it at log level warning without prior
26968 info-level messages. Fixes the other part of bug 2748; bugfix
26970 - Clear the table recording the time of the last request for each
26971 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
26972 Previously, we would clear our HS descriptor cache on SIGNAL
26973 NEWNYM, but if we had previously retrieved a descriptor (or tried
26974 to) from every directory responsible for it, we would refuse to
26975 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
26977 - Fix a log message that said "bits" while displaying a value in
26978 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
26980 - When checking for 1024-bit keys, check for 1024 bits, not 128
26981 bytes. This allows Tor to correctly discard keys of length 1017
26982 through 1023. Bugfix on 0.0.9pre5.
26985 - Relays now log the reason for publishing a new relay descriptor,
26986 so we have a better chance of hunting down instances of bug 1810.
26987 Resolves ticket 3252.
26988 - Revise most log messages that refer to nodes by nickname to
26989 instead use the "$key=nickname at address" format. This should be
26990 more useful, especially since nicknames are less and less likely
26991 to be unique. Resolves ticket 3045.
26992 - Log (at info level) when purging pieces of hidden-service-client
26993 state because of SIGNAL NEWNYM.
26996 - Remove undocumented option "-F" from tor-resolve: it hasn't done
26997 anything since 0.2.1.16-rc.
27000 Changes in version 0.2.2.27-beta - 2011-05-18
27001 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
27002 release, and also adds a few more general bugfixes.
27005 - Fix a crash bug when changing bridges in a running Tor process.
27006 Fixes bug 3213; bugfix on 0.2.2.26-beta.
27007 - When the controller configures a new bridge, don't wait 10 to 60
27008 seconds before trying to fetch its descriptor. Bugfix on
27009 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
27012 - Require that onion keys have exponent 65537 in microdescriptors too.
27013 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
27014 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
27015 Changed the limit to 512 characters by removing base64 newlines.
27016 Fixes bug 2752. Fix by Michael Yakubovich.
27017 - When a client starts or stops using bridges, never use a circuit
27018 that was built before the configuration change. This behavior could
27019 put at risk a user who uses bridges to ensure that her traffic
27020 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
27024 Changes in version 0.2.2.26-beta - 2011-05-17
27025 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
27026 also introduces a new "socksport auto" approach that should make it
27027 easier to run multiple Tors on the same system, and does a lot of
27028 cleanup to get us closer to a release candidate.
27030 o Security/privacy fixes:
27031 - Replace all potentially sensitive memory comparison operations
27032 with versions whose runtime does not depend on the data being
27033 compared. This will help resist a class of attacks where an
27034 adversary can use variations in timing information to learn
27035 sensitive data. Fix for one case of bug 3122. (Safe memcmp
27036 implementation by Robert Ransom based partially on code by DJB.)
27037 - When receiving a hidden service descriptor, check that it is for
27038 the hidden service we wanted. Previously, Tor would store any
27039 hidden service descriptors that a directory gave it, whether it
27040 wanted them or not. This wouldn't have let an attacker impersonate
27041 a hidden service, but it did let directories pre-seed a client
27042 with descriptors that it didn't want. Bugfix on 0.0.6.
27043 - On SIGHUP, do not clear out all TrackHostExits mappings, client
27044 DNS cache entries, and virtual address mappings: that's what
27045 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
27048 - The options SocksPort, ControlPort, and so on now all accept a
27049 value "auto" that opens a socket on an OS-selected port. A
27050 new ControlPortWriteToFile option tells Tor to write its
27051 actual control port or ports to a chosen file. If the option
27052 ControlPortFileGroupReadable is set, the file is created as
27053 group-readable. Now users can run two Tor clients on the same
27054 system without needing to manually mess with parameters. Resolves
27055 part of ticket 3076.
27056 - Set SO_REUSEADDR on all sockets, not just listeners. This should
27057 help busy exit nodes avoid running out of useable ports just
27058 because all the ports have been used in the near past. Resolves
27062 - New "GETINFO net/listeners/(type)" controller command to return
27063 a list of addresses and ports that are bound for listeners for a
27064 given connection type. This is useful when the user has configured
27065 "SocksPort auto" and the controller needs to know which port got
27066 chosen. Resolves another part of ticket 3076.
27067 - Add a new ControlSocketsGroupWritable configuration option: when
27068 it is turned on, ControlSockets are group-writeable by the default
27069 group of the current user. Patch by Jérémy Bobbio; implements
27071 - Tor now refuses to create a ControlSocket in a directory that is
27072 world-readable (or group-readable if ControlSocketsGroupWritable
27073 is 0). This is necessary because some operating systems do not
27074 enforce permissions on an AF_UNIX sockets. Permissions on the
27075 directory holding the socket, however, seems to work everywhere.
27076 - Rate-limit a warning about failures to download v2 networkstatus
27077 documents. Resolves part of bug 1352.
27078 - Backport code from 0.2.3.x that allows directory authorities to
27079 clean their microdescriptor caches. Needed to resolve bug 2230.
27080 - When an HTTPS proxy reports "403 Forbidden", we now explain
27081 what it means rather than calling it an unexpected status code.
27082 Closes bug 2503. Patch from Michael Yakubovich.
27083 - Update to the May 1 2011 Maxmind GeoLite Country database.
27086 - Authorities now clean their microdesc cache periodically and when
27087 reading from disk initially, not only when adding new descriptors.
27088 This prevents a bug where we could lose microdescriptors. Bugfix
27089 on 0.2.2.6-alpha. Fixes bug 2230.
27090 - Do not crash when our configuration file becomes unreadable, for
27091 example due to a permissions change, between when we start up
27092 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
27094 - Avoid a bug that would keep us from replacing a microdescriptor
27095 cache on Windows. (We would try to replace the file while still
27096 holding it open. That's fine on Unix, but Windows doesn't let us
27097 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
27098 - Add missing explanations for the authority-related torrc options
27099 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
27100 man page. Resolves issue 2379.
27101 - As an authority, do not upload our own vote or signature set to
27102 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
27103 it would get flagged as a duplicate. Resolves bug 3026.
27104 - Accept hidden service descriptors if we think we might be a hidden
27105 service directory, regardless of what our consensus says. This
27106 helps robustness, since clients and hidden services can sometimes
27107 have a more up-to-date view of the network consensus than we do,
27108 and if they think that the directory authorities list us a HSDir,
27109 we might actually be one. Related to bug 2732; bugfix on
27111 - When a controller changes TrackHostExits, remove mappings for
27112 hosts that should no longer have their exits tracked. Bugfix on
27114 - When a controller changes VirtualAddrNetwork, remove any mappings
27115 for hosts that were automapped to the old network. Bugfix on
27117 - When a controller changes one of the AutomapHosts* options, remove
27118 any mappings for hosts that should no longer be automapped. Bugfix
27120 - Do not reset the bridge descriptor download status every time we
27121 re-parse our configuration or get a configuration change. Fixes
27122 bug 3019; bugfix on 0.2.0.3-alpha.
27124 o Minor bugfixes (code cleanup):
27125 - When loading the microdesc journal, remember its current size.
27126 In 0.2.2, this helps prevent the microdesc journal from growing
27127 without limit on authorities (who are the only ones to use it in
27128 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
27129 Fix posted by "cypherpunks."
27130 - The microdesc journal is supposed to get rebuilt only if it is
27131 at least _half_ the length of the store, not _twice_ the length
27132 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
27133 - Fix a potential null-pointer dereference while computing a
27134 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
27136 - Avoid a possible null-pointer dereference when rebuilding the mdesc
27137 cache without actually having any descriptors to cache. Bugfix on
27138 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
27139 - If we fail to compute the identity digest of a v3 legacy keypair,
27140 warn, and don't use a buffer-full of junk instead. Bugfix on
27141 0.2.1.1-alpha; fixes bug 3106.
27142 - Resolve an untriggerable issue in smartlist_string_num_isin(),
27143 where if the function had ever in the future been used to check
27144 for the presence of a too-large number, it would have given an
27145 incorrect result. (Fortunately, we only used it for 16-bit
27146 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
27147 - Require that introduction point keys and onion handshake keys
27148 have a public exponent of 65537. Starts to fix bug 3207; bugfix
27151 o Removed features:
27152 - Caches no longer download and serve v2 networkstatus documents
27153 unless FetchV2Networkstatus flag is set: these documents haven't
27154 haven't been used by clients or relays since 0.2.0.x. Resolves
27158 Changes in version 0.2.3.1-alpha - 2011-05-05
27159 Tor 0.2.3.1-alpha adds some new experimental features, including support
27160 for an improved network IO backend, IOCP networking on Windows,
27161 microdescriptor caching, "fast-start" support for streams, and automatic
27162 home router configuration. There are also numerous internal improvements
27163 to try to make the code easier for developers to work with.
27165 This is the first alpha release in a new series, so expect there to be
27166 bugs. Users who would rather test out a more stable branch should
27167 stay with 0.2.2.x for now.
27170 - Tor can now optionally build with the "bufferevents" buffered IO
27171 backend provided by Libevent 2. To use this feature, make sure you
27172 have the latest possible version of Libevent, and pass the
27173 --enable-bufferevents flag to configure when building Tor from
27174 source. This feature will make our networking code more flexible,
27175 let us stack layers on each other, and let us use more efficient
27176 zero-copy transports where available.
27177 - As an experimental feature, Tor can use IOCP for networking on Windows.
27178 Once this code is tuned and optimized, it promises much better
27179 performance than the select-based backend we've used in the past. To
27180 try this feature, you must build Tor with Libevent 2, configure Tor
27181 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
27182 your torrc. There are known bugs here: only try this if you can help
27183 debug it as it breaks.
27184 - The EntryNodes option can now include country codes like {de} or IP
27185 addresses or network masks. Previously we had disallowed these options
27186 because we didn't have an efficient way to keep the list up to
27187 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
27188 - Exit nodes now accept and queue data on not-yet-connected streams.
27189 Previously, the client wasn't allowed to send data until the stream was
27190 connected, which slowed down all connections. This change will enable
27191 clients to perform a "fast-start" on streams and send data without
27192 having to wait for a confirmation that the stream has opened. (Patch
27193 from Ian Goldberg; implements the server side of Proposal 174.)
27194 - Tor now has initial support for automatic port mapping on the many
27195 home routers that support NAT-PMP or UPnP. (Not yet supported on
27196 Windows). To build the support code, you'll need to have libnatpnp
27197 library and/or the libminiupnpc library, and you'll need to enable the
27198 feature specifically by passing "--enable-upnp" and/or
27199 "--enable-natpnp" to configure. To turn it on, use the new
27200 PortForwarding option.
27201 - Caches now download, cache, and serve multiple "flavors" of the
27202 consensus, including a flavor that describes microdescriptors.
27203 - Caches now download, cache, and serve microdescriptors -- small
27204 summaries of router descriptors that are authenticated by all of the
27205 directory authorities. Once enough caches are running this code,
27206 clients will be able to save significant amounts of directory bandwidth
27207 by downloading microdescriptors instead of router descriptors.
27210 - Make logging resolution configurable with a new LogTimeGranularity
27211 option, and change the default from 1 millisecond to 1 second.
27212 Implements enhancement 1668.
27213 - We log which torrc file we're using on startup. Implements ticket
27215 - Ordinarily, Tor does not count traffic from private addresses (like
27216 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
27217 There is now a new option, CountPrivateBandwidth, to disable this
27218 behavior. Patch from Daniel Cagara.
27219 - New --enable-static-tor configure option for building Tor as
27220 statically as possible. Idea, general hackery and thoughts from
27221 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
27223 - If you set the NumCPUs option to 0, Tor will now try to detect how
27224 many CPUs you have. This is the new default behavior.
27225 - Turn on directory request statistics by default and include them in
27226 extra-info descriptors. Don't break if we have no GeoIP database.
27227 - Relays that set "ConnDirectionStatistics 1" write statistics on the
27228 bidirectional use of connections to disk every 24 hours.
27229 - Add a GeoIP file digest to the extra-info descriptor. Implements
27231 - The NodeFamily option -- which let you declare that you want to
27232 consider nodes to be part of a family whether they list themselves
27233 that way or not -- now allows IP address ranges and country codes.
27234 - Add a new 'Heartbeat' log message type to periodically log a message
27235 describing Tor's status at level Notice. This feature is meant for
27236 operators who log at notice, and want to make sure that their Tor
27237 server is still working. Implementation by George Kadianakis.
27239 o Minor bugfixes (on 0.2.2.25-alpha):
27240 - When loading the microdesc journal, remember its current size.
27241 In 0.2.2, this helps prevent the microdesc journal from growing
27242 without limit on authorities (who are the only ones to use it in
27243 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
27244 Fix posted by "cypherpunks."
27245 - The microdesc journal is supposed to get rebuilt only if it is
27246 at least _half_ the length of the store, not _twice_ the length
27247 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
27248 - If as an authority we fail to compute the identity digest of a v3
27249 legacy keypair, warn, and don't use a buffer-full of junk instead.
27250 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
27251 - Authorities now clean their microdesc cache periodically and when
27252 reading from disk initially, not only when adding new descriptors.
27253 This prevents a bug where we could lose microdescriptors. Bugfix
27256 o Minor features (controller):
27257 - Add a new SIGNAL event to the controller interface so that
27258 controllers can be notified when Tor handles a signal. Resolves
27259 issue 1955. Patch by John Brooks.
27260 - Add a new GETINFO option to get total bytes read and written. Patch
27261 from pipe, revised by atagar. Resolves ticket 2345.
27262 - Implement some GETINFO controller fields to provide information about
27263 the Tor process's pid, euid, username, and resource limits.
27266 - Our build system requires automake 1.6 or later to create the
27267 Makefile.in files. Previously, you could have used 1.4.
27268 This only affects developers and people building Tor from git;
27269 people who build Tor from the source distribution without changing
27270 the Makefile.am files should be fine.
27271 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
27272 so on. This is more robust against some of the failure modes
27273 associated with running the autotools pieces on their own.
27275 o Minor packaging issues:
27276 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
27277 already created. Patch from Andreas Stieger. Fixes bug 2573.
27279 o Code simplifications and refactoring:
27280 - A major revision to our internal node-selecting and listing logic.
27281 Tor already had at least two major ways to look at the question of
27282 "which Tor servers do we know about": a list of router descriptors,
27283 and a list of entries in the current consensus. With
27284 microdescriptors, we're adding a third. Having so many systems
27285 without an abstraction layer over them was hurting the codebase.
27286 Now, we have a new "node_t" abstraction that presents a consistent
27287 interface to a client's view of a Tor node, and holds (nearly) all
27288 of the mutable state formerly in routerinfo_t and routerstatus_t.
27289 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
27290 no longer link against Libevent: they never used it, but
27291 our library structure used to force them to link it.
27293 o Removed features:
27294 - Remove some old code to work around even older versions of Tor that
27295 used forked processes to handle DNS requests. Such versions of Tor
27296 are no longer in use as servers.
27298 o Documentation fixes:
27299 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
27300 - Add missing documentation for the authority-related torrc options
27301 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
27305 Changes in version 0.2.2.25-alpha - 2011-04-29
27306 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
27307 robust, routers no longer overreport their bandwidth, Win7 should crash
27308 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
27309 now prevents hidden service-related activity from being linkable. It
27310 provides more information to Vidalia so you can see if your bridge is
27311 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
27312 StrictNodes configuration options to make them more reliable, more
27313 understandable, and more regularly applied. If you use those options,
27314 please see the revised documentation for them in the manual page.
27317 - Relays were publishing grossly inflated bandwidth values because
27318 they were writing their state files wrong--now they write the
27319 correct value. Also, resume reading bandwidth history from the
27320 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
27321 - Improve hidden service robustness: When we find that we have
27322 extended a hidden service's introduction circuit to a relay not
27323 listed as an introduction point in the HS descriptor we currently
27324 have, retry with an introduction point from the current
27325 descriptor. Previously we would just give up. Fixes bugs 1024 and
27326 1930; bugfix on 0.2.0.10-alpha.
27327 - Clients now stop trying to use an exit node associated with a given
27328 destination by TrackHostExits if they fail to reach that exit node.
27329 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
27330 - Fix crash bug on platforms where gmtime and localtime can return
27331 NULL. Windows 7 users were running into this one. Fixes part of bug
27332 2077. Bugfix on all versions of Tor. Found by boboper.
27334 o Security and stability fixes:
27335 - Don't double-free a parsable, but invalid, microdescriptor, even if
27336 it is followed in the blob we're parsing by an unparsable
27337 microdescriptor. Fixes an issue reported in a comment on bug 2954.
27338 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
27339 - If the Nickname configuration option isn't given, Tor would pick a
27340 nickname based on the local hostname as the nickname for a relay.
27341 Because nicknames are not very important in today's Tor and the
27342 "Unnamed" nickname has been implemented, this is now problematic
27343 behavior: It leaks information about the hostname without being
27344 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
27345 introduced the Unnamed nickname. Reported by tagnaq.
27346 - Fix an uncommon assertion failure when running with DNSPort under
27347 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
27348 - Avoid linkability based on cached hidden service descriptors: forget
27349 all hidden service descriptors cached as a client when processing a
27350 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
27353 - Export GeoIP information on bridge usage to controllers even if we
27354 have not yet been running for 24 hours. Now Vidalia bridge operators
27355 can get more accurate and immediate feedback about their
27356 contributions to the network.
27358 o Major features and bugfixes (node selection):
27359 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
27360 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
27361 options. Previously, we had been ambiguous in describing what
27362 counted as an "exit" node, and what operations exactly "StrictNodes
27363 0" would permit. This created confusion when people saw nodes built
27364 through unexpected circuits, and made it hard to tell real bugs from
27365 surprises. Now the intended behavior is:
27366 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
27367 a node that delivers user traffic outside the Tor network.
27368 . "Entry", in the context of EntryNodes, means a node used as the
27369 first hop of a multihop circuit. It doesn't include direct
27370 connections to directory servers.
27371 . "ExcludeNodes" applies to all nodes.
27372 . "StrictNodes" changes the behavior of ExcludeNodes only. When
27373 StrictNodes is set, Tor should avoid all nodes listed in
27374 ExcludeNodes, even when it will make user requests fail. When
27375 StrictNodes is *not* set, then Tor should follow ExcludeNodes
27376 whenever it can, except when it must use an excluded node to
27377 perform self-tests, connect to a hidden service, provide a
27378 hidden service, fulfill a .exit request, upload directory
27379 information, or fetch directory information.
27380 Collectively, the changes to implement the behavior fix bug 1090.
27381 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
27382 a node is listed in both, it's treated as excluded.
27383 - ExcludeNodes now applies to directory nodes -- as a preference if
27384 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
27385 Don't exclude all the directory authorities and set StrictNodes to 1
27386 unless you really want your Tor to break.
27387 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
27388 - ExcludeExitNodes now overrides .exit requests.
27389 - We don't use bridges listed in ExcludeNodes.
27390 - When StrictNodes is 1:
27391 . We now apply ExcludeNodes to hidden service introduction points
27392 and to rendezvous points selected by hidden service users. This
27393 can make your hidden service less reliable: use it with caution!
27394 . If we have used ExcludeNodes on ourself, do not try relay
27395 reachability self-tests.
27396 . If we have excluded all the directory authorities, we will not
27397 even try to upload our descriptor if we're a relay.
27398 . Do not honor .exit requests to an excluded node.
27399 - Remove a misfeature that caused us to ignore the Fast/Stable flags
27400 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
27401 - When the set of permitted nodes changes, we now remove any mappings
27402 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
27404 - We never cannibalize a circuit that had excluded nodes on it, even
27405 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
27406 - Revert a change where we would be laxer about attaching streams to
27407 circuits than when building the circuits. This was meant to prevent
27408 a set of bugs where streams were never attachable, but our improved
27409 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
27410 - Keep track of how many times we launch a new circuit to handle a
27411 given stream. Too many launches could indicate an inconsistency
27412 between our "launch a circuit to handle this stream" logic and our
27413 "attach this stream to one of the available circuits" logic.
27414 - Improve log messages related to excluded nodes.
27417 - Fix a spurious warning when moving from a short month to a long
27418 month on relays with month-based BandwidthAccounting. Bugfix on
27419 0.2.2.17-alpha; fixes bug 3020.
27420 - When a client finds that an origin circuit has run out of 16-bit
27421 stream IDs, we now mark it as unusable for new streams. Previously,
27422 we would try to close the entire circuit. Bugfix on 0.0.6.
27423 - Add a forgotten cast that caused a compile warning on OS X 10.6.
27424 Bugfix on 0.2.2.24-alpha.
27425 - Be more careful about reporting the correct error from a failed
27426 connect() system call. Under some circumstances, it was possible to
27427 look at an incorrect value for errno when sending the end reason.
27428 Bugfix on 0.1.0.1-rc.
27429 - Correctly handle an "impossible" overflow cases in connection byte
27430 counting, where we write or read more than 4GB on an edge connection
27431 in a single second. Bugfix on 0.1.2.8-beta.
27432 - Correct the warning displayed when a rendezvous descriptor exceeds
27433 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
27435 - Clients and hidden services now use HSDir-flagged relays for hidden
27436 service descriptor downloads and uploads even if the relays have no
27437 DirPort set and the client has disabled TunnelDirConns. This will
27438 eventually allow us to give the HSDir flag to relays with no
27439 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
27440 - Downgrade "no current certificates known for authority" message from
27441 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
27442 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
27443 2917. Bugfix on 0.1.1.1-alpha.
27444 - Only limit the lengths of single HS descriptors, even when multiple
27445 HS descriptors are published to an HSDir relay in a single POST
27446 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
27447 - Write the current time into the LastWritten line in our state file,
27448 rather than the time from the previous write attempt. Also, stop
27449 trying to use a time of -1 in our log statements. Fixes bug 3039;
27450 bugfix on 0.2.2.14-alpha.
27451 - Be more consistent in our treatment of file system paths. "~" should
27452 get expanded to the user's home directory in the Log config option.
27453 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
27454 feature for the -f and --DataDirectory options.
27457 - Make sure every relay writes a state file at least every 12 hours.
27458 Previously, a relay could go for weeks without writing its state
27459 file, and on a crash could lose its bandwidth history, capacity
27460 estimates, client country statistics, and so on. Addresses bug 3012.
27461 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
27462 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
27463 clients are already deprecated because of security bugs.
27464 - Don't allow v0 hidden service authorities to act as clients.
27465 Required by fix for bug 3000.
27466 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
27467 by fix for bug 3000.
27468 - Ensure that no empty [dirreq-](read|write)-history lines are added
27469 to an extrainfo document. Implements ticket 2497.
27471 o Code simplification and refactoring:
27472 - Remove workaround code to handle directory responses from servers
27473 that had bug 539 (they would send HTTP status 503 responses _and_
27474 send a body too). Since only server versions before
27475 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
27476 keep the workaround in place.
27477 - Remove the old 'fuzzy time' logic. It was supposed to be used for
27478 handling calculations where we have a known amount of clock skew and
27479 an allowed amount of unknown skew. But we only used it in three
27480 places, and we never adjusted the known/unknown skew values. This is
27481 still something we might want to do someday, but if we do, we'll
27482 want to do it differently.
27483 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
27484 None of the cases where we did this before were wrong, but by making
27485 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
27486 - Use GetTempDir to find the proper temporary directory location on
27487 Windows when generating temporary files for the unit tests. Patch by
27491 Changes in version 0.2.2.24-alpha - 2011-04-08
27492 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
27493 prevented Tor clients from effectively using "multihomed" bridges,
27494 that is, bridges that listen on multiple ports or IP addresses so users
27495 can continue to use some of their addresses even if others get blocked.
27498 - Fix a bug where bridge users who configure the non-canonical
27499 address of a bridge automatically switch to its canonical
27500 address. If a bridge listens at more than one address, it should be
27501 able to advertise those addresses independently and any non-blocked
27502 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
27504 - If you configured Tor to use bridge A, and then quit and
27505 configured Tor to use bridge B instead, it would happily continue
27506 to use bridge A if it's still reachable. While this behavior is
27507 a feature if your goal is connectivity, in some scenarios it's a
27508 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
27509 - Directory authorities now use data collected from their own
27510 uptime observations when choosing whether to assign the HSDir flag
27511 to relays, instead of trusting the uptime value the relay reports in
27512 its descriptor. This change helps prevent an attack where a small
27513 set of nodes with frequently-changing identity keys can blackhole
27514 a hidden service. (Only authorities need upgrade; others will be
27515 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
27518 - When we restart our relay, we might get a successful connection
27519 from the outside before we've started our reachability tests,
27520 triggering a warning: "ORPort found reachable, but I have no
27521 routerinfo yet. Failing to inform controller of success." This
27522 bug was harmless unless Tor is running under a controller
27523 like Vidalia, in which case the controller would never get a
27524 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
27526 - Make directory authorities more accurate at recording when
27527 relays that have failed several reachability tests became
27528 unreachable, so we can provide more accuracy at assigning Stable,
27529 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
27530 - Fix an issue that prevented static linking of libevent on
27531 some platforms (notably Linux). Fixes bug 2698; bugfix on
27532 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
27533 the --with-static-libevent configure option).
27534 - We now ask the other side of a stream (the client or the exit)
27535 for more data on that stream when the amount of queued data on
27536 that stream dips low enough. Previously, we wouldn't ask the
27537 other side for more data until either it sent us more data (which
27538 it wasn't supposed to do if it had exhausted its window!) or we
27539 had completely flushed all our queued data. This flow control fix
27540 should improve throughput. Fixes bug 2756; bugfix on the earliest
27541 released versions of Tor (svn commit r152).
27542 - Avoid a double-mark-for-free warning when failing to attach a
27543 transparent proxy connection. (We thought we had fixed this in
27544 0.2.2.23-alpha, but it turns out our fix was checking the wrong
27545 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
27546 bug) and 0.2.2.23-alpha (the incorrect fix).
27547 - When warning about missing zlib development packages during compile,
27548 give the correct package names. Bugfix on 0.2.0.1-alpha.
27551 - Directory authorities now log the source of a rejected POSTed v3
27552 networkstatus vote.
27553 - Make compilation with clang possible when using
27554 --enable-gcc-warnings by removing two warning options that clang
27555 hasn't implemented yet and by fixing a few warnings. Implements
27557 - When expiring circuits, use microsecond timers rather than
27558 one-second timers. This can avoid an unpleasant situation where a
27559 circuit is launched near the end of one second and expired right
27560 near the beginning of the next, and prevent fluctuations in circuit
27562 - Use computed circuit-build timeouts to decide when to launch
27563 parallel introduction circuits for hidden services. (Previously,
27564 we would retry after 15 seconds.)
27565 - Update to the April 1 2011 Maxmind GeoLite Country database.
27568 - Create the /var/run/tor directory on startup on OpenSUSE if it is
27569 not already created. Patch from Andreas Stieger. Fixes bug 2573.
27571 o Documentation changes:
27572 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
27573 - Resolve all doxygen warnings except those for missing documentation.
27575 - Add doxygen documentation for more functions, fields, and types.
27578 Changes in version 0.2.2.23-alpha - 2011-03-08
27579 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
27580 they restart they don't lose their bandwidth capacity estimate. This
27581 release also fixes a diverse set of user-facing bugs, ranging from
27582 relays overrunning their rate limiting to clients falsely warning about
27583 clock skew to bridge descriptor leaks by our bridge directory authority.
27586 - Stop sending a CLOCK_SKEW controller status event whenever
27587 we fetch directory information from a relay that has a wrong clock.
27588 Instead, only inform the controller when it's a trusted authority
27589 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
27590 the rest of bug 1074.
27591 - Fix an assert in parsing router descriptors containing IPv6
27592 addresses. This one took down the directory authorities when
27593 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
27594 - Make the bridge directory authority refuse to answer directory
27595 requests for "all" descriptors. It used to include bridge
27596 descriptors in its answer, which was a major information leak.
27597 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
27598 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
27599 Tor would ignore their RelayBandwidthBurst setting,
27600 potentially using more bandwidth than expected. Bugfix on
27601 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
27602 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
27603 hidserv" in her torrc. The 'hidserv' argument never controlled
27604 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
27607 - Relays now save observed peak bandwidth throughput rates to their
27608 state file (along with total usage, which was already saved)
27609 so that they can determine their correct estimated bandwidth on
27610 restart. Resolves bug 1863, where Tor relays would reset their
27611 estimated bandwidth to 0 after restarting.
27612 - Directory authorities now take changes in router IP address and
27613 ORPort into account when determining router stability. Previously,
27614 if a router changed its IP or ORPort, the authorities would not
27615 treat it as having any downtime for the purposes of stability
27616 calculation, whereas clients would experience downtime since the
27617 change could take a while to propagate to them. Resolves issue 1035.
27618 - Enable Address Space Layout Randomization (ASLR) and Data Execution
27619 Prevention (DEP) by default on Windows to make it harder for
27620 attackers to exploit vulnerabilities. Patch from John Brooks.
27622 o Minor bugfixes (on 0.2.1.x and earlier):
27623 - Fix a rare crash bug that could occur when a client was configured
27624 with a large number of bridges. Fixes bug 2629; bugfix on
27625 0.2.1.2-alpha. Bugfix by trac user "shitlei".
27626 - Avoid a double mark-for-free warning when failing to attach a
27627 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
27629 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
27630 found by "cypherpunks". This bug was introduced before the first
27631 Tor release, in svn commit r110.
27632 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
27633 don't mention them in the manpage. Fixes bug 2450; issue
27634 spotted by keb and G-Lo.
27635 - Fix a bug in bandwidth history state parsing that could have been
27636 triggered if a future version of Tor ever changed the timing
27637 granularity at which bandwidth history is measured. Bugfix on
27638 Tor 0.1.1.11-alpha.
27639 - When a relay decides that its DNS is too broken for it to serve
27640 as an exit server, it advertised itself as a non-exit, but
27641 continued to act as an exit. This could create accidental
27642 partitioning opportunities for users. Instead, if a relay is
27643 going to advertise reject *:* as its exit policy, it should
27644 really act with exit policy "reject *:*". Fixes bug 2366.
27645 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
27646 - In the special case where you configure a public exit relay as your
27647 bridge, Tor would be willing to use that exit relay as the last
27648 hop in your circuit as well. Now we fail that circuit instead.
27649 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
27650 - Fix a bug with our locking implementation on Windows that couldn't
27651 correctly detect when a file was already locked. Fixes bug 2504,
27652 bugfix on 0.2.1.6-alpha.
27653 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
27654 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
27656 - Set target port in get_interface_address6() correctly. Bugfix
27657 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
27658 - Directory authorities are now more robust to hops back in time
27659 when calculating router stability. Previously, if a run of uptime
27660 or downtime appeared to be negative, the calculation could give
27661 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
27663 - Fix an assert that got triggered when using the TestingTorNetwork
27664 configuration option and then issuing a GETINFO config-text control
27665 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
27667 o Minor bugfixes (on 0.2.2.x):
27668 - Clients should not weight BadExit nodes as Exits in their node
27669 selection. Similarly, directory authorities should not count BadExit
27670 bandwidth as Exit bandwidth when computing bandwidth-weights.
27671 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
27672 - Correctly clear our dir_read/dir_write history when there is an
27673 error parsing any bw history value from the state file. Bugfix on
27674 Tor 0.2.2.15-alpha.
27675 - Resolve a bug in verifying signatures of directory objects
27676 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
27677 Fixes bug 2409. Found by "piebeer".
27678 - Bridge authorities no longer crash on SIGHUP when they try to
27679 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
27683 - Log less aggressively about circuit timeout changes, and improve
27684 some other circuit timeout messages. Resolves bug 2004.
27685 - Log a little more clearly about the times at which we're no longer
27686 accepting new connections. Resolves bug 2181.
27687 - Reject attempts at the client side to open connections to private
27688 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
27689 a randomly chosen exit node. Attempts to do so are always
27690 ill-defined, generally prevented by exit policies, and usually
27691 in error. This will also help to detect loops in transparent
27692 proxy configurations. You can disable this feature by setting
27693 "ClientRejectInternalAddresses 0" in your torrc.
27694 - Always treat failure to allocate an RSA key as an unrecoverable
27696 - Update to the March 1 2011 Maxmind GeoLite Country database.
27698 o Minor features (log subsystem):
27699 - Add documentation for configuring logging at different severities in
27700 different log domains. We've had this feature since 0.2.1.1-alpha,
27701 but for some reason it never made it into the manpage. Fixes
27703 - Make it simpler to specify "All log domains except for A and B".
27704 Previously you needed to say "[*,~A,~B]". Now you can just say
27706 - Add a "LogMessageDomains 1" option to include the domains of log
27707 messages along with the messages. Without this, there's no way
27708 to use log domains without reading the source or doing a lot
27711 o Packaging changes:
27712 - Stop shipping the Tor specs files and development proposal documents
27713 in the tarball. They are now in a separate git repository at
27714 git://git.torproject.org/torspec.git
27717 Changes in version 0.2.1.30 - 2011-02-23
27718 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
27719 change is a slight tweak to Tor's TLS handshake that makes relays
27720 and bridges that run this new version reachable from Iran again.
27721 We don't expect this tweak will win the arms race long-term, but it
27722 buys us time until we roll out a better solution.
27725 - Stop sending a CLOCK_SKEW controller status event whenever
27726 we fetch directory information from a relay that has a wrong clock.
27727 Instead, only inform the controller when it's a trusted authority
27728 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
27729 the rest of bug 1074.
27730 - Fix a bounds-checking error that could allow an attacker to
27731 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
27732 Found by "piebeer".
27733 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
27734 Tor would ignore their RelayBandwidthBurst setting,
27735 potentially using more bandwidth than expected. Bugfix on
27736 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
27737 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
27738 hidserv" in her torrc. The 'hidserv' argument never controlled
27739 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
27742 - Adjust our TLS Diffie-Hellman parameters to match those used by
27744 - Update to the February 1 2011 Maxmind GeoLite Country database.
27747 - Check for and reject overly long directory certificates and
27748 directory tokens before they have a chance to hit any assertions.
27749 Bugfix on 0.2.1.28. Found by "doorss".
27750 - Bring the logic that gathers routerinfos and assesses the
27751 acceptability of circuits into line. This prevents a Tor OP from
27752 getting locked in a cycle of choosing its local OR as an exit for a
27753 path (due to a .exit request) and then rejecting the circuit because
27754 its OR is not listed yet. It also prevents Tor clients from using an
27755 OR running in the same instance as an exit (due to a .exit request)
27756 if the OR does not meet the same requirements expected of an OR
27757 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
27759 o Packaging changes:
27760 - Stop shipping the Tor specs files and development proposal documents
27761 in the tarball. They are now in a separate git repository at
27762 git://git.torproject.org/torspec.git
27763 - Do not include Git version tags as though they are SVN tags when
27764 generating a tarball from inside a repository that has switched
27765 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
27768 Changes in version 0.2.2.22-alpha - 2011-01-25
27769 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
27770 main other change is a slight tweak to Tor's TLS handshake that makes
27771 relays and bridges that run this new version reachable from Iran again.
27772 We don't expect this tweak will win the arms race long-term, but it
27773 will buy us a bit more time until we roll out a better solution.
27776 - Fix a bounds-checking error that could allow an attacker to
27777 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
27778 Found by "piebeer".
27779 - Don't assert when changing from bridge to relay or vice versa
27780 via the controller. The assert happened because we didn't properly
27781 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
27782 bug 2433. Reported by bastik.
27785 - Adjust our TLS Diffie-Hellman parameters to match those used by
27787 - Provide a log message stating which geoip file we're parsing
27788 instead of just stating that we're parsing the geoip file.
27789 Implements ticket 2432.
27792 - Check for and reject overly long directory certificates and
27793 directory tokens before they have a chance to hit any assertions.
27794 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
27797 Changes in version 0.2.2.21-alpha - 2011-01-15
27798 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
27799 continues our recent code security audit work. The main fix resolves
27800 a remote heap overflow vulnerability that can allow remote code
27801 execution (CVE-2011-0427). Other fixes address a variety of assert
27802 and crash bugs, most of which we think are hard to exploit remotely.
27804 o Major bugfixes (security), also included in 0.2.1.29:
27805 - Fix a heap overflow bug where an adversary could cause heap
27806 corruption. This bug probably allows remote code execution
27807 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
27809 - Prevent a denial-of-service attack by disallowing any
27810 zlib-compressed data whose compression factor is implausibly
27811 high. Fixes part of bug 2324; reported by "doorss".
27812 - Zero out a few more keys in memory before freeing them. Fixes
27813 bug 2384 and part of bug 2385. These key instances found by
27814 "cypherpunks", based on Andrew Case's report about being able
27815 to find sensitive data in Tor's memory space if you have enough
27816 permissions. Bugfix on 0.0.2pre9.
27818 o Major bugfixes (crashes), also included in 0.2.1.29:
27819 - Prevent calls to Libevent from inside Libevent log handlers.
27820 This had potential to cause a nasty set of crashes, especially
27821 if running Libevent with debug logging enabled, and running
27822 Tor with a controller watching for low-severity log messages.
27823 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
27824 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
27825 underflow errors there too. Fixes the other part of bug 2324.
27826 - Fix a bug where we would assert if we ever had a
27827 cached-descriptors.new file (or another file read directly into
27828 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
27829 on 0.2.1.25. Found by doorss.
27830 - Fix some potential asserts and parsing issues with grossly
27831 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
27834 o Minor bugfixes (other), also included in 0.2.1.29:
27835 - Fix a bug with handling misformed replies to reverse DNS lookup
27836 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
27837 bug reported by doorss.
27838 - Fix compilation on mingw when a pthreads compatibility library
27839 has been installed. (We don't want to use it, so we shouldn't
27840 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
27841 - Fix a bug where we would declare that we had run out of virtual
27842 addresses when the address space was only half-exhausted. Bugfix
27844 - Correctly handle the case where AutomapHostsOnResolve is set but
27845 no virtual addresses are available. Fixes bug 2328; bugfix on
27846 0.1.2.1-alpha. Bug found by doorss.
27847 - Correctly handle wrapping around when we run out of virtual
27848 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
27850 o Minor features, also included in 0.2.1.29:
27851 - Update to the January 1 2011 Maxmind GeoLite Country database.
27852 - Introduce output size checks on all of our decryption functions.
27854 o Build changes, also included in 0.2.1.29:
27855 - Tor does not build packages correctly with Automake 1.6 and earlier;
27856 added a check to Makefile.am to make sure that we're building with
27857 Automake 1.7 or later.
27858 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
27859 because we built it with a too-old version of automake. Thus that
27860 release broke ./configure --enable-openbsd-malloc, which is popular
27861 among really fast exit relays on Linux.
27863 o Major bugfixes, new in 0.2.2.21-alpha:
27864 - Prevent crash/heap corruption when the cbtnummodes consensus
27865 parameter is set to 0 or large values. Fixes bug 2317; bugfix
27868 o Major features, new in 0.2.2.21-alpha:
27869 - Introduce minimum/maximum values that clients will believe
27870 from the consensus. Now we'll have a better chance to avoid crashes
27871 or worse when a consensus param has a weird value.
27873 o Minor features, new in 0.2.2.21-alpha:
27874 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
27875 used on bridges, and it makes bridge scanning somewhat easier.
27876 - If writing the state file to disk fails, wait up to an hour before
27877 retrying again, rather than trying again each second. Fixes bug
27878 2346; bugfix on Tor 0.1.1.3-alpha.
27879 - Make Libevent log messages get delivered to controllers later,
27880 and not from inside the Libevent log handler. This prevents unsafe
27881 reentrant Libevent calls while still letting the log messages
27883 - Detect platforms that brokenly use a signed size_t, and refuse to
27884 build there. Found and analyzed by doorss and rransom.
27885 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
27888 o Minor bugfixes, new in 0.2.2.21-alpha:
27889 - Handle SOCKS messages longer than 128 bytes long correctly, rather
27890 than waiting forever for them to finish. Fixes bug 2330; bugfix
27891 on 0.2.0.16-alpha. Found by doorss.
27892 - Add assertions to check for overflow in arguments to
27893 base32_encode() and base32_decode(); fix a signed-unsigned
27894 comparison there too. These bugs are not actually reachable in Tor,
27895 but it's good to prevent future errors too. Found by doorss.
27896 - Correctly detect failures to create DNS requests when using Libevent
27897 versions before v2. (Before Libevent 2, we used our own evdns
27898 implementation. Its return values for Libevent's evdns_resolve_*()
27899 functions are not consistent with those from Libevent.) Fixes bug
27900 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
27902 o Documentation, new in 0.2.2.21-alpha:
27903 - Document the default socks host and port (127.0.0.1:9050) for
27907 Changes in version 0.2.1.29 - 2011-01-15
27908 Tor 0.2.1.29 continues our recent code security audit work. The main
27909 fix resolves a remote heap overflow vulnerability that can allow remote
27910 code execution. Other fixes address a variety of assert and crash bugs,
27911 most of which we think are hard to exploit remotely.
27913 o Major bugfixes (security):
27914 - Fix a heap overflow bug where an adversary could cause heap
27915 corruption. This bug probably allows remote code execution
27916 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
27918 - Prevent a denial-of-service attack by disallowing any
27919 zlib-compressed data whose compression factor is implausibly
27920 high. Fixes part of bug 2324; reported by "doorss".
27921 - Zero out a few more keys in memory before freeing them. Fixes
27922 bug 2384 and part of bug 2385. These key instances found by
27923 "cypherpunks", based on Andrew Case's report about being able
27924 to find sensitive data in Tor's memory space if you have enough
27925 permissions. Bugfix on 0.0.2pre9.
27927 o Major bugfixes (crashes):
27928 - Prevent calls to Libevent from inside Libevent log handlers.
27929 This had potential to cause a nasty set of crashes, especially
27930 if running Libevent with debug logging enabled, and running
27931 Tor with a controller watching for low-severity log messages.
27932 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
27933 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
27934 underflow errors there too. Fixes the other part of bug 2324.
27935 - Fix a bug where we would assert if we ever had a
27936 cached-descriptors.new file (or another file read directly into
27937 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
27938 on 0.2.1.25. Found by doorss.
27939 - Fix some potential asserts and parsing issues with grossly
27940 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
27943 o Minor bugfixes (other):
27944 - Fix a bug with handling misformed replies to reverse DNS lookup
27945 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
27946 bug reported by doorss.
27947 - Fix compilation on mingw when a pthreads compatibility library
27948 has been installed. (We don't want to use it, so we shouldn't
27949 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
27950 - Fix a bug where we would declare that we had run out of virtual
27951 addresses when the address space was only half-exhausted. Bugfix
27953 - Correctly handle the case where AutomapHostsOnResolve is set but
27954 no virtual addresses are available. Fixes bug 2328; bugfix on
27955 0.1.2.1-alpha. Bug found by doorss.
27956 - Correctly handle wrapping around to when we run out of virtual
27957 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
27958 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
27959 because we built it with a too-old version of automake. Thus that
27960 release broke ./configure --enable-openbsd-malloc, which is popular
27961 among really fast exit relays on Linux.
27964 - Update to the January 1 2011 Maxmind GeoLite Country database.
27965 - Introduce output size checks on all of our decryption functions.
27968 - Tor does not build packages correctly with Automake 1.6 and earlier;
27969 added a check to Makefile.am to make sure that we're building with
27970 Automake 1.7 or later.
27973 Changes in version 0.2.2.20-alpha - 2010-12-17
27974 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
27975 exploitable bugs. We also fix a variety of other significant bugs,
27976 change the IP address for one of our directory authorities, and update
27977 the minimum version that Tor relays must run to join the network.
27980 - Fix a remotely exploitable bug that could be used to crash instances
27981 of Tor remotely by overflowing on the heap. Remote-code execution
27982 hasn't been confirmed, but can't be ruled out. Everyone should
27983 upgrade. Bugfix on the 0.1.1 series and later.
27984 - Fix a bug that could break accounting on 64-bit systems with large
27985 time_t values, making them hibernate for impossibly long intervals.
27986 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
27987 - Fix a logic error in directory_fetches_from_authorities() that
27988 would cause all _non_-exits refusing single-hop-like circuits
27989 to fetch from authorities, when we wanted to have _exits_ fetch
27990 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
27992 - Fix a stream fairness bug that would cause newer streams on a given
27993 circuit to get preference when reading bytes from the origin or
27994 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
27995 introduced before the first Tor release, in svn revision r152.
27997 o Directory authority changes:
27998 - Change IP address and ports for gabelmoo (v3 directory authority).
28001 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
28002 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
28003 - Fix an off-by-one error in calculating some controller command
28004 argument lengths. Fortunately, this mistake is harmless since
28005 the controller code does redundant NUL termination too. Found by
28006 boboper. Bugfix on 0.1.1.1-alpha.
28007 - Do not dereference NULL if a bridge fails to build its
28008 extra-info descriptor. Found by an anonymous commenter on
28009 Trac. Bugfix on 0.2.2.19-alpha.
28012 - Update to the December 1 2010 Maxmind GeoLite Country database.
28013 - Directory authorities now reject relays running any versions of
28014 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
28015 known bugs that keep RELAY_EARLY cells from working on rendezvous
28016 circuits. Followup to fix for bug 2081.
28017 - Directory authorities now reject relays running any version of Tor
28018 older than 0.2.0.26-rc. That version is the earliest that fetches
28019 current directory information correctly. Fixes bug 2156.
28020 - Report only the top 10 ports in exit-port stats in order not to
28021 exceed the maximum extra-info descriptor length of 50 KB. Implements
28025 Changes in version 0.2.1.28 - 2010-12-17
28026 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
28027 exploitable bugs. We also took this opportunity to change the IP address
28028 for one of our directory authorities, and to update the geoip database
28032 - Fix a remotely exploitable bug that could be used to crash instances
28033 of Tor remotely by overflowing on the heap. Remote-code execution
28034 hasn't been confirmed, but can't be ruled out. Everyone should
28035 upgrade. Bugfix on the 0.1.1 series and later.
28037 o Directory authority changes:
28038 - Change IP address and ports for gabelmoo (v3 directory authority).
28041 - Update to the December 1 2010 Maxmind GeoLite Country database.
28044 Changes in version 0.2.1.27 - 2010-11-23
28045 Yet another OpenSSL security patch broke its compatibility with Tor:
28046 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
28047 also took this opportunity to fix several crash bugs, integrate a new
28048 directory authority, and update the bundled GeoIP database.
28051 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
28052 No longer set the tlsext_host_name extension on server SSL objects;
28053 but continue to set it on client SSL objects. Our goal in setting
28054 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
28055 bugfix on 0.2.1.1-alpha.
28056 - Do not log messages to the controller while shrinking buffer
28057 freelists. Doing so would sometimes make the controller connection
28058 try to allocate a buffer chunk, which would mess up the internals
28059 of the freelist and cause an assertion failure. Fixes bug 1125;
28060 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
28061 - Learn our external IP address when we're a relay or bridge, even if
28062 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
28063 where we introduced bridge relays that don't need to publish to
28064 be useful. Fixes bug 2050.
28065 - Do even more to reject (and not just ignore) annotations on
28066 router descriptors received anywhere but from the cache. Previously
28067 we would ignore such annotations at first, but cache them to disk
28068 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
28069 - When you're using bridges and your network goes away and your
28070 bridges get marked as down, recover when you attempt a new socks
28071 connection (if the network is back), rather than waiting up to an
28072 hour to try fetching new descriptors for your bridges. Bugfix on
28073 0.2.0.3-alpha; fixes bug 1981.
28076 - Move to the November 2010 Maxmind GeoLite country db (rather
28077 than the June 2009 ip-to-country GeoIP db) for our statistics that
28078 count how many users relays are seeing from each country. Now we'll
28079 have more accurate data, especially for many African countries.
28081 o New directory authorities:
28082 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
28086 - Fix an assertion failure that could occur in directory caches or
28087 bridge users when using a very short voting interval on a testing
28088 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
28090 - Enforce multiplicity rules when parsing annotations. Bugfix on
28091 0.2.0.8-alpha. Found by piebeer.
28092 - Allow handshaking OR connections to take a full KeepalivePeriod
28093 seconds to handshake. Previously, we would close them after
28094 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
28095 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
28097 - When building with --enable-gcc-warnings on OpenBSD, disable
28098 warnings in system headers. This makes --enable-gcc-warnings
28099 pass on OpenBSD 4.8.
28102 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
28103 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
28104 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
28105 Servers can start sending this code when enough clients recognize
28106 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
28107 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
28108 Patch from mingw-san.
28111 - Remove the old debian/ directory from the main Tor distribution.
28112 The official Tor-for-debian git repository lives at the URL
28113 https://git.torproject.org/debian/tor.git
28114 - Stop shipping the old doc/website/ directory in the tarball. We
28115 changed the website format in late 2010, and what we shipped in
28116 0.2.1.26 really wasn't that useful anyway.
28119 Changes in version 0.2.2.19-alpha - 2010-11-22
28120 Yet another OpenSSL security patch broke its compatibility with Tor:
28121 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
28124 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
28125 No longer set the tlsext_host_name extension on server SSL objects;
28126 but continue to set it on client SSL objects. Our goal in setting
28127 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
28128 bugfix on 0.2.1.1-alpha.
28131 - Try harder not to exceed the maximum length of 50 KB when writing
28132 statistics to extra-info descriptors. This bug was triggered by very
28133 fast relays reporting exit-port, entry, and dirreq statistics.
28134 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
28135 - Publish a router descriptor even if generating an extra-info
28136 descriptor fails. Previously we would not publish a router
28137 descriptor without an extra-info descriptor; this can cause fast
28138 exit relays collecting exit-port statistics to drop from the
28139 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
28142 Changes in version 0.2.2.18-alpha - 2010-11-16
28143 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
28144 us lately, makes unpublished bridge relays able to detect their IP
28145 address, and fixes a wide variety of other bugs to get us much closer
28146 to a stable release.
28149 - Do even more to reject (and not just ignore) annotations on
28150 router descriptors received anywhere but from the cache. Previously
28151 we would ignore such annotations at first, but cache them to disk
28152 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
28153 - Do not log messages to the controller while shrinking buffer
28154 freelists. Doing so would sometimes make the controller connection
28155 try to allocate a buffer chunk, which would mess up the internals
28156 of the freelist and cause an assertion failure. Fixes bug 1125;
28157 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
28158 - Learn our external IP address when we're a relay or bridge, even if
28159 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
28160 where we introduced bridge relays that don't need to publish to
28161 be useful. Fixes bug 2050.
28162 - Maintain separate TLS contexts and certificates for incoming and
28163 outgoing connections in bridge relays. Previously we would use the
28164 same TLS contexts and certs for incoming and outgoing connections.
28165 Bugfix on 0.2.0.3-alpha; addresses bug 988.
28166 - Maintain separate identity keys for incoming and outgoing TLS
28167 contexts in bridge relays. Previously we would use the same
28168 identity keys for incoming and outgoing TLS contexts. Bugfix on
28169 0.2.0.3-alpha; addresses the other half of bug 988.
28170 - Avoid an assertion failure when we as an authority receive a
28171 duplicate upload of a router descriptor that we already have,
28172 but which we previously considered an obsolete descriptor.
28173 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
28174 - Avoid a crash bug triggered by looking at a dangling pointer while
28175 setting the network status consensus. Found by Robert Ransom.
28176 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
28177 - Fix a logic error where servers that _didn't_ act as exits would
28178 try to keep their server lists more aggressively up to date than
28179 exits, when it was supposed to be the other way around. Bugfix
28182 o Minor bugfixes (on Tor 0.2.1.x and earlier):
28183 - When we're trying to guess whether we know our IP address as
28184 a relay, we would log various ways that we failed to guess
28185 our address, but never log that we ended up guessing it
28186 successfully. Now add a log line to help confused and anxious
28187 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
28188 - Bring the logic that gathers routerinfos and assesses the
28189 acceptability of circuits into line. This prevents a Tor OP from
28190 getting locked in a cycle of choosing its local OR as an exit for a
28191 path (due to a .exit request) and then rejecting the circuit because
28192 its OR is not listed yet. It also prevents Tor clients from using an
28193 OR running in the same instance as an exit (due to a .exit request)
28194 if the OR does not meet the same requirements expected of an OR
28195 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
28196 - Correctly describe errors that occur when generating a TLS object.
28197 Previously we would attribute them to a failure while generating a
28198 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
28200 - Enforce multiplicity rules when parsing annotations. Bugfix on
28201 0.2.0.8-alpha. Found by piebeer.
28202 - Fix warnings that newer versions of autoconf produced during
28203 ./autogen.sh. These warnings appear to be harmless in our case,
28204 but they were extremely verbose. Fixes bug 2020.
28206 o Minor bugfixes (on Tor 0.2.2.x):
28207 - Enable protection of small arrays whenever we build with gcc
28208 hardening features, not only when also building with warnings
28209 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
28212 - Make hidden services work better in private Tor networks by not
28213 requiring any uptime to join the hidden service descriptor
28214 DHT. Implements ticket 2088.
28215 - Rate-limit the "your application is giving Tor only an IP address"
28216 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
28217 - When AllowSingleHopExits is set, print a warning to explain to the
28218 relay operator why most clients are avoiding her relay.
28219 - Update to the November 1 2010 Maxmind GeoLite Country database.
28221 o Code simplifications and refactoring:
28222 - When we fixed bug 1038 we had to put in a restriction not to send
28223 RELAY_EARLY cells on rend circuits. This was necessary as long
28224 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
28225 active. Now remove this obsolete check. Resolves bug 2081.
28226 - Some options used different conventions for uppercasing of acronyms
28227 when comparing manpage and source. Fix those in favor of the
28228 manpage, as it makes sense to capitalize acronyms.
28229 - Remove the torrc.complete file. It hasn't been kept up to date
28230 and users will have better luck checking out the manpage.
28231 - Remove the obsolete "NoPublish" option; it has been flagged
28232 as obsolete and has produced a warning since 0.1.1.18-rc.
28233 - Remove everything related to building the expert bundle for OS X.
28234 It has confused many users, doesn't work right on OS X 10.6,
28235 and is hard to get rid of once installed. Resolves bug 1274.
28238 Changes in version 0.2.2.17-alpha - 2010-09-30
28239 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
28240 to use one-hop circuits (which can put the exit relays at higher risk,
28241 plus unbalance the network); fixes a big bug in bandwidth accounting
28242 for relays that want to limit their monthly bandwidth use; fixes a
28243 big pile of bugs in how clients tolerate temporary network failure;
28244 and makes our adaptive circuit build timeout feature (which improves
28245 client performance if your network is fast while not breaking things
28246 if your network is slow) better handle bad networks.
28249 - Exit relays now try harder to block exit attempts from unknown
28250 relays, to make it harder for people to use them as one-hop proxies
28251 a la tortunnel. Controlled by the refuseunknownexits consensus
28252 parameter (currently enabled), or you can override it on your
28253 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
28255 o Major bugfixes (0.2.1.x and earlier):
28256 - Fix a bug in bandwidth accounting that could make us use twice
28257 the intended bandwidth when our interval start changes due to
28258 daylight saving time. Now we tolerate skew in stored vs computed
28259 interval starts: if the start of the period changes by no more than
28260 50% of the period's duration, we remember bytes that we transferred
28261 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
28262 - Always search the Windows system directory for system DLLs, and
28263 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
28264 - When you're using bridges and your network goes away and your
28265 bridges get marked as down, recover when you attempt a new socks
28266 connection (if the network is back), rather than waiting up to an
28267 hour to try fetching new descriptors for your bridges. Bugfix on
28268 0.2.0.3-alpha; fixes bug 1981.
28270 o Major bugfixes (on 0.2.2.x):
28271 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
28273 - Fix a segfault that could happen when operating a bridge relay with
28274 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
28275 - The consensus bandwidth-weights (used by clients to choose fast
28276 relays) entered an unexpected edge case in September where
28277 Exits were much scarcer than Guards, resulting in bad weight
28278 recommendations. Now we compute them using new constraints that
28279 should succeed in all cases. Also alter directory authorities to
28280 not include the bandwidth-weights line if they fail to produce
28281 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
28282 - When weighting bridges during path selection, we used to trust
28283 the bandwidths they provided in their descriptor, only capping them
28284 at 10MB/s. This turned out to be problematic for two reasons:
28285 Bridges could claim to handle a lot more traffic then they
28286 actually would, thus making more clients pick them and have a
28287 pretty effective DoS attack. The other issue is that new bridges
28288 that might not have a good estimate for their bw capacity yet
28289 would not get used at all unless no other bridges are available
28290 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
28292 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
28293 - Ignore cannibalized circuits when recording circuit build times.
28294 This should provide for a minor performance improvement for hidden
28295 service users using 0.2.2.14-alpha, and should remove two spurious
28296 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
28297 - Simplify the logic that causes us to decide if the network is
28298 unavailable for purposes of recording circuit build times. If we
28299 receive no cells whatsoever for the entire duration of a circuit's
28300 full measured lifetime, the network is probably down. Also ignore
28301 one-hop directory fetching circuit timeouts when calculating our
28302 circuit build times. These changes should hopefully reduce the
28303 cases where we see ridiculous circuit build timeouts for people
28304 with spotty wireless connections. Fixes part of bug 1772; bugfix
28306 - Prevent the circuit build timeout from becoming larger than
28307 the maximum build time we have ever seen. Also, prevent the time
28308 period for measurement circuits from becoming larger than twice that
28309 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
28312 - When we run out of directory information such that we can't build
28313 circuits, but then get enough that we can build circuits, log when
28314 we actually construct a circuit, so the user has a better chance of
28315 knowing what's going on. Fixes bug 1362.
28316 - Be more generous with how much bandwidth we'd use up (with
28317 accounting enabled) before entering "soft hibernation". Previously,
28318 we'd refuse new connections and circuits once we'd used up 95% of
28319 our allotment. Now, we use up 95% of our allotment, AND make sure
28320 that we have no more than 500MB (or 3 hours of expected traffic,
28321 whichever is lower) remaining before we enter soft hibernation.
28322 - If we've configured EntryNodes and our network goes away and/or all
28323 our entrynodes get marked down, optimistically retry them all when
28324 a new socks application request appears. Fixes bug 1882.
28325 - Add some more defensive programming for architectures that can't
28326 handle unaligned integer accesses. We don't know of any actual bugs
28327 right now, but that's the best time to fix them. Fixes bug 1943.
28328 - Support line continuations in the torrc config file. If a line
28329 ends with a single backslash character, the newline is ignored, and
28330 the configuration value is treated as continuing on the next line.
28333 o Minor bugfixes (on 0.2.1.x and earlier):
28334 - For bandwidth accounting, calculate our expected bandwidth rate
28335 based on the time during which we were active and not in
28336 soft-hibernation during the last interval. Previously, we were
28337 also considering the time spent in soft-hibernation. If this
28338 was a long time, we would wind up underestimating our bandwidth
28339 by a lot, and skewing our wakeup time towards the start of the
28340 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
28342 o Minor bugfixes (on 0.2.2.x):
28343 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
28344 which were disabled by the circuit build timeout changes in
28345 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
28346 - Make sure we don't warn about missing bandwidth weights when
28347 choosing bridges or other relays not in the consensus. Bugfix on
28348 0.2.2.10-alpha; fixes bug 1805.
28349 - In our logs, do not double-report signatures from unrecognized
28350 authorities both as "from unknown authority" and "not
28351 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
28354 Changes in version 0.2.2.16-alpha - 2010-09-17
28355 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
28356 evident at exit relays), and also continues to resolve all the little
28357 bugs that have been filling up trac lately.
28359 o Major bugfixes (stream-level fairness):
28360 - When receiving a circuit-level SENDME for a blocked circuit, try
28361 to package cells fairly from all the streams that had previously
28362 been blocked on that circuit. Previously, we had started with the
28363 oldest stream, and allowed each stream to potentially exhaust
28364 the circuit's package window. This gave older streams on any
28365 given circuit priority over newer ones. Fixes bug 1937. Detected
28366 originally by Camilo Viecco. This bug was introduced before the
28367 first Tor release, in svn commit r152: it is the new winner of
28368 the longest-lived bug prize.
28369 - When the exit relay got a circuit-level sendme cell, it started
28370 reading on the exit streams, even if had 500 cells queued in the
28371 circuit queue already, so the circuit queue just grew and grew in
28372 some cases. We fix this by not re-enabling reading on receipt of a
28373 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
28374 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
28376 - Newly created streams were allowed to read cells onto circuits,
28377 even if the circuit's cell queue was blocked and waiting to drain.
28378 This created potential unfairness, as older streams would be
28379 blocked, but newer streams would gladly fill the queue completely.
28380 We add code to detect this situation and prevent any stream from
28381 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
28385 - Update to the September 1 2010 Maxmind GeoLite Country database.
28386 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
28387 not. This would lead to a cookie that is still not group readable.
28388 Closes bug 1843. Suggested by katmagic.
28389 - When logging a rate-limited warning, we now mention how many messages
28390 got suppressed since the last warning.
28391 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
28392 do individual connection-level rate limiting of clients. The torrc
28393 config options with the same names trump the consensus params, if
28394 both are present. Replaces the old "bwconnrate" and "bwconnburst"
28395 consensus params which were broken from 0.2.2.7-alpha through
28396 0.2.2.14-alpha. Closes bug 1947.
28397 - When a router changes IP address or port, authorities now launch
28398 a new reachability test for it. Implements ticket 1899.
28399 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
28400 2 no signature, 4 required" messages about consensus signatures
28401 easier to read, and make sure they get logged at the same severity
28402 as the messages explaining which keys are which. Fixes bug 1290.
28403 - Don't warn when we have a consensus that we can't verify because
28404 of missing certificates, unless those certificates are ones
28405 that we have been trying and failing to download. Fixes bug 1145.
28406 - If you configure your bridge with a known identity fingerprint,
28407 and the bridge authority is unreachable (as it is in at least
28408 one country now), fall back to directly requesting the descriptor
28409 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
28411 - When building with --enable-gcc-warnings on OpenBSD, disable
28412 warnings in system headers. This makes --enable-gcc-warnings
28413 pass on OpenBSD 4.8.
28415 o Minor bugfixes (on 0.2.1.x and earlier):
28416 - Authorities will now attempt to download consensuses if their
28417 own efforts to make a live consensus have failed. This change
28418 means authorities that restart will fetch a valid consensus, and
28419 it means authorities that didn't agree with the current consensus
28420 will still fetch and serve it if it has enough signatures. Bugfix
28421 on 0.2.0.9-alpha; fixes bug 1300.
28422 - Ensure DNS requests launched by "RESOLVE" commands from the
28423 controller respect the __LeaveStreamsUnattached setconf options. The
28424 same goes for requests launched via DNSPort or transparent
28425 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
28426 - Allow handshaking OR connections to take a full KeepalivePeriod
28427 seconds to handshake. Previously, we would close them after
28428 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
28429 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
28431 - Rate-limit "Failed to hand off onionskin" warnings.
28432 - Never relay a cell for a circuit we have already destroyed.
28433 Between marking a circuit as closeable and finally closing it,
28434 it may have been possible for a few queued cells to get relayed,
28435 even though they would have been immediately dropped by the next
28436 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
28437 - Never queue a cell for a circuit that's already been marked
28439 - Never vote for a server as "Running" if we have a descriptor for
28440 it claiming to be hibernating, and that descriptor was published
28441 more recently than our last contact with the server. Bugfix on
28442 0.2.0.3-alpha; fixes bug 911.
28443 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
28446 o Minor bugfixes (on 0.2.2.x):
28447 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
28448 down if a directory fetch fails and you've configured either
28449 bridges or EntryNodes. The intent was to mark the relay as down
28450 _unless_ you're using bridges or EntryNodes, since if you are
28451 then you could quickly run out of entry points.
28452 - Fix the Windows directory-listing code. A bug introduced in
28453 0.2.2.14-alpha could make Windows directory servers forget to load
28454 some of their cached v2 networkstatus files.
28455 - Really allow clients to use relays as bridges. Fixes bug 1776;
28456 bugfix on 0.2.2.15-alpha.
28457 - Demote a warn to info that happens when the CellStatistics option
28458 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
28459 Reported by Moritz Bartl.
28460 - On Windows, build correctly either with or without Unicode support.
28461 This is necessary so that Tor can support fringe platforms like
28462 Windows 98 (which has no Unicode), or Windows CE (which has no
28463 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
28466 - Add a unit test for cross-platform directory-listing code.
28469 Changes in version 0.2.2.15-alpha - 2010-08-18
28470 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
28471 fixes a variety of other bugs that were preventing performance
28472 experiments from moving forward, fixes several bothersome memory leaks,
28473 and generally closes a lot of smaller bugs that have been filling up
28477 - Stop assigning the HSDir flag to relays that disable their
28478 DirPort (and thus will refuse to answer directory requests). This
28479 fix should dramatically improve the reachability of hidden services:
28480 hidden services and hidden service clients pick six HSDir relays
28481 to store and retrieve the hidden service descriptor, and currently
28482 about half of the HSDir relays will refuse to work. Bugfix on
28483 0.2.0.10-alpha; fixes part of bug 1693.
28484 - The PerConnBWRate and Burst config options, along with the
28485 bwconnrate and bwconnburst consensus params, initialized each conn's
28486 token bucket values only when the connection is established. Now we
28487 update them if the config options change, and update them every time
28488 we get a new consensus. Otherwise we can encounter an ugly edge
28489 case where we initialize an OR conn to client-level bandwidth,
28490 but then later the relay joins the consensus and we leave it
28491 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
28492 - Fix a regression that caused Tor to rebind its ports if it receives
28493 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
28496 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
28497 should give us approximately 40-50% more Guard-flagged nodes,
28498 improving the anonymity the Tor network can provide and also
28499 decreasing the dropoff in throughput that relays experience when
28500 they first get the Guard flag.
28501 - Allow enabling or disabling the *Statistics config options while
28505 - Update to the August 1 2010 Maxmind GeoLite Country database.
28506 - Have the controller interface give a more useful message than
28507 "Internal Error" in response to failed GETINFO requests.
28508 - Warn when the same option is provided more than once in a torrc
28509 file, on the command line, or in a single SETCONF statement, and
28510 the option is one that only accepts a single line. Closes bug 1384.
28511 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
28512 Patch from mingw-san.
28513 - Add support for the country code "{??}" in torrc options like
28514 ExcludeNodes, to indicate all routers of unknown country. Closes
28516 - Relays report the number of bytes spent on answering directory
28517 requests in extra-info descriptors similar to {read,write}-history.
28518 Implements enhancement 1790.
28520 o Minor bugfixes (on 0.2.1.x and earlier):
28521 - Complain if PublishServerDescriptor is given multiple arguments that
28522 include 0 or 1. This configuration will be rejected in the future.
28523 Bugfix on 0.2.0.1-alpha; closes bug 1107.
28524 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
28525 Bugfix on 0.2.0.13-alpha; closes bug 928.
28526 - Change "Application request when we're believed to be offline."
28527 notice to "Application request when we haven't used client
28528 functionality lately.", to clarify that it's not an error. Bugfix
28529 on 0.0.9.3; fixes bug 1222.
28530 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
28531 would return "551 Internal error" rather than "552 Unrecognized key
28532 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
28533 - Users can't configure a regular relay to be their bridge. It didn't
28534 work because when Tor fetched the bridge descriptor, it found
28535 that it already had it, and didn't realize that the purpose of the
28536 descriptor had changed. Now we replace routers with a purpose other
28537 than bridge with bridge descriptors when fetching them. Bugfix on
28538 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
28539 refetch the descriptor with router purpose 'general', disabling
28541 - Fix a rare bug in rend_fn unit tests: we would fail a test when
28542 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
28543 on 0.2.0.10-alpha; fixes bug 1808.
28544 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
28545 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
28546 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
28547 Servers can start sending this code when enough clients recognize
28548 it. Also update the spec to reflect this new reason. Bugfix on
28549 0.1.0.1-rc; fixes part of bug 1793.
28550 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
28551 when we switch from being a public relay to a bridge. Otherwise
28552 there will still be clients that see the relay in their consensus,
28553 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
28555 - Instead of giving an assertion failure on an internal mismatch
28556 on estimated freelist size, just log a BUG warning and try later.
28557 Mitigates but does not fix bug 1125.
28558 - Fix an assertion failure that could occur in caches or bridge users
28559 when using a very short voting interval on a testing network.
28560 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
28562 o Minor bugfixes (on 0.2.2.x):
28563 - Alter directory authorities to always consider Exit-flagged nodes
28564 as potential Guard nodes in their votes. The actual decision to
28565 use Exits as Guards is done in the consensus bandwidth weights.
28566 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
28567 - When the controller is reporting the purpose of circuits that
28568 didn't finish building before the circuit build timeout, it was
28569 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
28570 - Our libevent version parsing code couldn't handle versions like
28571 1.4.14b-stable and incorrectly warned the user about using an
28572 old and broken version of libevent. Treat 1.4.14b-stable like
28573 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
28575 - Don't use substitution references like $(VAR:MOD) when
28576 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
28577 '$(:x)' to 'x' rather than the empty string. This bites us in
28578 doc/ when configured with --disable-asciidoc. Bugfix on
28579 0.2.2.9-alpha; fixes bug 1773.
28580 - Remove a spurious hidden service server-side log notice about
28581 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
28583 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
28585 - Correctly report written bytes on linked connections. Found while
28586 implementing 1790. Bugfix on 0.2.2.4-alpha.
28587 - Fix three memory leaks: one in circuit_build_times_parse_state(),
28588 one in dirvote_add_signatures_to_pending_consensus(), and one every
28589 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
28590 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
28592 o Code simplifications and refactoring:
28593 - Take a first step towards making or.h smaller by splitting out
28594 function definitions for all source files in src/or/. Leave
28595 structures and defines in or.h for now.
28596 - Remove a bunch of unused function declarations as well as a block of
28597 #if 0'd code from the unit tests. Closes bug 1824.
28598 - New unit tests for exit-port history statistics; refactored exit
28599 statistics code to be more easily tested.
28600 - Remove the old debian/ directory from the main Tor distribution.
28601 The official Tor-for-debian git repository lives at the URL
28602 https://git.torproject.org/debian/tor.git
28605 Changes in version 0.2.2.14-alpha - 2010-07-12
28606 Tor 0.2.2.14-alpha greatly improves client-side handling of
28607 circuit build timeouts, which are used to estimate speed and improve
28608 performance. We also move to a much better GeoIP database, port Tor to
28609 Windows CE, introduce new compile flags that improve code security,
28610 add an eighth v3 directory authority, and address a lot of more
28614 - Tor directory authorities no longer crash when started with a
28615 cached-microdesc-consensus file in their data directory. Bugfix
28616 on 0.2.2.6-alpha; fixes bug 1532.
28617 - Treat an unset $HOME like an empty $HOME rather than triggering an
28618 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
28619 - Ignore negative and large circuit build timeout values that can
28620 happen during a suspend or hibernate. These values caused various
28621 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
28622 - Alter calculation of Pareto distribution parameter 'Xm' for
28623 Circuit Build Timeout learning to use the weighted average of the
28624 top N=3 modes (because we have three entry guards). Considering
28625 multiple modes should improve the timeout calculation in some cases,
28626 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
28628 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
28629 right censored distribution model. This approach improves over the
28630 synthetic timeout generation approach that was producing insanely
28631 high timeout values. Now we calculate build timeouts using truncated
28632 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
28633 - Do not close circuits that are under construction when they reach
28634 the circuit build timeout. Instead, leave them building (but do not
28635 use them) for up until the time corresponding to the 95th percentile
28636 on the Pareto CDF or 60 seconds, whichever is greater. This is done
28637 to provide better data for the new Pareto model. This percentile
28638 can be controlled by the consensus.
28641 - Move to the June 2010 Maxmind GeoLite country db (rather than the
28642 June 2009 ip-to-country GeoIP db) for our statistics that count
28643 how many users relays are seeing from each country. Now we have
28644 more accurate data for many African countries.
28645 - Port Tor to build and run correctly on Windows CE systems, using
28646 the wcecompat library. Contributed by Valerio Lupi.
28647 - New "--enable-gcc-hardening" ./configure flag (off by default)
28648 to turn on gcc compile time hardening options. It ensures
28649 that signed ints have defined behavior (-fwrapv), enables
28650 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
28651 with canaries (-fstack-protector-all), turns on ASLR protection if
28652 supported by the kernel (-fPIE, -pie), and adds additional security
28653 related warnings. Verified to work on Mac OS X and Debian Lenny.
28654 - New "--enable-linker-hardening" ./configure flag (off by default)
28655 to turn on ELF specific hardening features (relro, now). This does
28656 not work with Mac OS X or any other non-ELF binary format.
28658 o New directory authorities:
28659 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
28663 - New config option "WarnUnsafeSocks 0" disables the warning that
28664 occurs whenever Tor receives a socks handshake using a version of
28665 the socks protocol that can only provide an IP address (rather
28666 than a hostname). Setups that do DNS locally over Tor are fine,
28667 and we shouldn't spam the logs in that case.
28668 - Convert the HACKING file to asciidoc, and add a few new sections
28669 to it, explaining how we use Git, how we make changelogs, and
28670 what should go in a patch.
28671 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
28672 event, to give information on the current rate of circuit timeouts
28673 over our stored history.
28674 - Add ability to disable circuit build time learning via consensus
28675 parameter and via a LearnCircuitBuildTimeout config option. Also
28676 automatically disable circuit build time calculation if we are
28677 either a AuthoritativeDirectory, or if we fail to write our state
28678 file. Fixes bug 1296.
28679 - More gracefully handle corrupt state files, removing asserts
28680 in favor of saving a backup and resetting state.
28681 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
28685 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
28687 - When a2x fails, mention that the user could disable manpages instead
28688 of trying to fix their asciidoc installation.
28689 - Where available, use Libevent 2.0's periodic timers so that our
28690 once-per-second cleanup code gets called even more closely to
28691 once per second than it would otherwise. Fixes bug 943.
28692 - If you run a bridge that listens on multiple IP addresses, and
28693 some user configures a bridge address that uses a different IP
28694 address than your bridge writes in its router descriptor, and the
28695 user doesn't specify an identity key, their Tor would discard the
28696 descriptor because "it isn't one of our configured bridges", and
28697 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
28698 Bugfix on 0.2.0.3-alpha.
28699 - If OpenSSL fails to make a duplicate of a private or public key, log
28700 an error message and try to exit cleanly. May help with debugging
28701 if bug 1209 ever remanifests.
28702 - Save a couple bytes in memory allocation every time we escape
28703 certain characters in a string. Patch from Florian Zumbiehl.
28704 - Make it explicit that we don't cannibalize one-hop circuits. This
28705 happens in the wild, but doesn't turn out to be a problem because
28706 we fortunately don't use those circuits. Many thanks to outofwords
28707 for the initial analysis and to swissknife who confirmed that
28708 two-hop circuits are actually created.
28709 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
28710 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
28711 - Eliminate a case where a circuit build time warning was displayed
28712 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
28715 Changes in version 0.2.1.26 - 2010-05-02
28716 Tor 0.2.1.26 addresses the recent connection and memory overload
28717 problems we've been seeing on relays, especially relays with their
28718 DirPort open. If your relay has been crashing, or you turned it off
28719 because it used too many resources, give this release a try.
28721 This release also fixes yet another instance of broken OpenSSL libraries
28722 that was causing some relays to drop out of the consensus.
28725 - Teach relays to defend themselves from connection overload. Relays
28726 now close idle circuits early if it looks like they were intended
28727 for directory fetches. Relays are also more aggressive about closing
28728 TLS connections that have no circuits on them. Such circuits are
28729 unlikely to be re-used, and tens of thousands of them were piling
28730 up at the fast relays, causing the relays to run out of sockets
28731 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
28732 their directory fetches over TLS).
28733 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
28734 that claim to be earlier than 0.9.8m, but which have in reality
28735 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
28736 behavior. Possible fix for some cases of bug 1346.
28737 - Directory mirrors were fetching relay descriptors only from v2
28738 directory authorities, rather than v3 authorities like they should.
28739 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
28740 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
28743 - Finally get rid of the deprecated and now harmful notion of "clique
28744 mode", where directory authorities maintain TLS connections to
28748 - In the util/threads test, no longer free the test_mutex before all
28749 worker threads have finished. Bugfix on 0.2.1.6-alpha.
28750 - The master thread could starve the worker threads quite badly on
28751 certain systems, causing them to run only partially in the allowed
28752 window. This resulted in test failures. Now the master thread sleeps
28753 occasionally for a few microseconds while the two worker-threads
28754 compete for the mutex. Bugfix on 0.2.0.1-alpha.
28757 Changes in version 0.2.2.13-alpha - 2010-04-24
28758 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
28759 problems we've been seeing on relays, especially relays with their
28760 DirPort open. If your relay has been crashing, or you turned it off
28761 because it used too many resources, give this release a try.
28764 - Teach relays to defend themselves from connection overload. Relays
28765 now close idle circuits early if it looks like they were intended
28766 for directory fetches. Relays are also more aggressive about closing
28767 TLS connections that have no circuits on them. Such circuits are
28768 unlikely to be re-used, and tens of thousands of them were piling
28769 up at the fast relays, causing the relays to run out of sockets
28770 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
28771 their directory fetches over TLS).
28774 - Finally get rid of the deprecated and now harmful notion of "clique
28775 mode", where directory authorities maintain TLS connections to
28777 - Directory authorities now do an immediate reachability check as soon
28778 as they hear about a new relay. This change should slightly reduce
28779 the time between setting up a relay and getting listed as running
28780 in the consensus. It should also improve the time between setting
28781 up a bridge and seeing use by bridge users.
28782 - Directory authorities no longer launch a TLS connection to every
28783 relay as they startup. Now that we have 2k+ descriptors cached,
28784 the resulting network hiccup is becoming a burden. Besides,
28785 authorities already avoid voting about Running for the first half
28786 hour of their uptime.
28789 Changes in version 0.2.2.12-alpha - 2010-04-20
28790 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
28791 handle and vote on descriptors. It was causing relays to drop out of
28795 - Many relays have been falling out of the consensus lately because
28796 not enough authorities know about their descriptor for them to get
28797 a majority of votes. When we deprecated the v2 directory protocol,
28798 we got rid of the only way that v3 authorities can hear from each
28799 other about other descriptors. Now authorities examine every v3
28800 vote for new descriptors, and fetch them from that authority. Bugfix
28802 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
28803 and a warning in or.h related to bandwidth_weight_rule_t that
28804 prevented clean compile on OS X. Fixes bug 1363; bugfix on
28806 - Fix a segfault on relays when DirReqStatistics is enabled
28807 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
28811 - Demote a confusing TLS warning that relay operators might get when
28812 someone tries to talk to their OrPort. It is neither the operator's
28813 fault nor can they do anything about it. Fixes bug 1364; bugfix
28817 Changes in version 0.2.2.11-alpha - 2010-04-15
28818 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
28819 libraries that was causing some relays to drop out of the consensus.
28822 - Directory mirrors were fetching relay descriptors only from v2
28823 directory authorities, rather than v3 authorities like they should.
28824 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
28825 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
28826 - Fix a parsing error that made every possible value of
28827 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
28828 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
28829 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
28830 about the option without breaking older ones.
28831 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
28832 that claim to be earlier than 0.9.8m, but which have in reality
28833 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
28834 behavior. Possible fix for some cases of bug 1346.
28837 - Experiment with a more aggressive approach to preventing clients
28838 from making one-hop exit streams. Exit relays who want to try it
28839 out can set "RefuseUnknownExits 1" in their torrc, and then look
28840 for "Attempt by %s to open a stream" log messages. Let us know
28842 - Add support for statically linking zlib by specifying
28843 --enable-static-zlib, to go with our support for statically linking
28844 openssl and libevent. Resolves bug 1358.
28847 - Fix a segfault that happens whenever a Tor client that is using
28848 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
28850 - When we cleaned up the contrib/tor-exit-notice.html file, we left
28851 out the first line. Fixes bug 1295.
28852 - When building the manpage from a tarball, we required asciidoc, but
28853 the asciidoc -> roff/html conversion was already done for the
28854 tarball. Make 'make' complain only when we need asciidoc (either
28855 because we're compiling directly from git, or because we altered
28856 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
28857 - When none of the directory authorities vote on any params, Tor
28858 segfaulted when trying to make the consensus from the votes. We
28859 didn't trigger the bug in practice, because authorities do include
28860 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
28863 - In the util/threads test, no longer free the test_mutex before all
28864 worker threads have finished. Bugfix on 0.2.1.6-alpha.
28865 - The master thread could starve the worker threads quite badly on
28866 certain systems, causing them to run only partially in the allowed
28867 window. This resulted in test failures. Now the master thread sleeps
28868 occasionally for a few microseconds while the two worker-threads
28869 compete for the mutex. Bugfix on 0.2.0.1-alpha.
28872 Changes in version 0.2.2.10-alpha - 2010-03-07
28873 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
28874 could prevent relays from guessing their IP address correctly. It also
28875 starts the groundwork for another client-side performance boost, since
28876 currently we're not making efficient use of relays that have both the
28877 Guard flag and the Exit flag.
28880 - Fix a regression from our patch for bug 1244 that caused relays
28881 to guess their IP address incorrectly if they didn't set Address
28882 in their torrc and/or their address fails to resolve. Bugfix on
28883 0.2.2.9-alpha; fixes bug 1269.
28885 o Major features (performance):
28886 - Directory authorities now compute consensus weightings that instruct
28887 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
28888 and no flag. Clients that use these weightings will distribute
28889 network load more evenly across these different relay types. The
28890 weightings are in the consensus so we can change them globally in
28891 the future. Extra thanks to "outofwords" for finding some nasty
28892 security bugs in the first implementation of this feature.
28894 o Minor features (performance):
28895 - Always perform router selections using weighted relay bandwidth,
28896 even if we don't need a high capacity circuit at the time. Non-fast
28897 circuits now only differ from fast ones in that they can use relays
28898 not marked with the Fast flag. This "feature" could turn out to
28899 be a horrible bug; we should investigate more before it goes into
28903 - Allow disabling building of the manpages. Skipping the manpage
28904 speeds up the build considerably.
28906 o Minor bugfixes (on 0.2.2.x):
28907 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
28908 Bugfix on 0.2.2.9-alpha.
28909 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
28910 config option. Bugfix on 0.2.2.7-alpha.
28911 - Ship the asciidoc-helper file in the tarball, so that people can
28912 build from source if they want to, and touching the .1.txt files
28913 doesn't break the build. Bugfix on 0.2.2.9-alpha.
28915 o Minor bugfixes (on 0.2.1.x or earlier):
28916 - Fix a dereference-then-NULL-check sequence when publishing
28917 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
28919 - Fix another dereference-then-NULL-check sequence. Bugfix on
28920 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
28921 - Make sure we treat potentially not NUL-terminated strings correctly.
28922 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
28924 o Code simplifications and refactoring:
28925 - Fix some urls in the exit notice file and make it XHTML1.1 strict
28926 compliant. Based on a patch from Christian Kujau.
28927 - Don't use sed in asciidoc-helper anymore.
28928 - Make the build process fail if asciidoc cannot be found and
28929 building with asciidoc isn't disabled.
28932 Changes in version 0.2.2.9-alpha - 2010-02-22
28933 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
28934 location of a directory authority, and cleans up a bunch of small bugs.
28936 o Directory authority changes:
28937 - Change IP address for dannenberg (v3 directory authority), and
28938 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
28939 service directory authority) from the list.
28942 - Make Tor work again on the latest OS X: when deciding whether to
28943 use strange flags to turn TLS renegotiation on, detect the OpenSSL
28944 version at run-time, not compile time. We need to do this because
28945 Apple doesn't update its dev-tools headers when it updates its
28946 libraries in a security patch.
28947 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
28948 that could happen on 32-bit platforms with 64-bit time_t. Also fix
28949 a memory leak when requesting a hidden service descriptor we've
28950 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
28952 - Authorities could be tricked into giving out the Exit flag to relays
28953 that didn't allow exiting to any ports. This bug could screw
28954 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
28955 1238. Bug discovered by Martin Kowalczyk.
28956 - When freeing a session key, zero it out completely. We only zeroed
28957 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
28958 patched by ekir. Fixes bug 1254.
28961 - Fix static compilation by listing the openssl libraries in the right
28962 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
28963 - Resume handling .exit hostnames in a special way: originally we
28964 stripped the .exit part and used the requested exit relay. In
28965 0.2.2.1-alpha we stopped treating them in any special way, meaning
28966 if you use a .exit address then Tor will pass it on to the exit
28967 relay. Now we reject the .exit stream outright, since that behavior
28968 might be more expected by the user. Found and diagnosed by Scott
28969 Bennett and Downie on or-talk.
28970 - Don't spam the controller with events when we have no file
28971 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
28972 for log messages was already solved from bug 748.)
28973 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
28975 - Make the DNSPort option work with libevent 2.x. Don't alter the
28976 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
28977 - Emit a GUARD DROPPED controller event for a case we missed.
28978 - Make more fields in the controller protocol case-insensitive, since
28979 control-spec.txt said they were.
28980 - Refactor resolve_my_address() to not use gethostbyname() anymore.
28981 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
28982 - Fix a spec conformance issue: the network-status-version token
28983 must be the first token in a v3 consensus or vote. Discovered by
28984 parakeep. Bugfix on 0.2.0.3-alpha.
28986 o Code simplifications and refactoring:
28987 - Generate our manpage and HTML documentation using Asciidoc. This
28988 change should make it easier to maintain the documentation, and
28989 produce nicer HTML.
28990 - Remove the --enable-iphone option. According to reports from Marco
28991 Bonetti, Tor builds fine without any special tweaking on recent
28992 iPhone SDK versions.
28993 - Removed some unnecessary files from the source distribution. The
28994 AUTHORS file has now been merged into the people page on the
28995 website. The roadmaps and design doc can now be found in the
28996 projects directory in svn.
28997 - Enabled various circuit build timeout constants to be controlled
28998 by consensus parameters. Also set better defaults for these
28999 parameters based on experimentation on broadband and simulated
29000 high latency links.
29003 - The 'EXTENDCIRCUIT' control port command can now be used with
29004 a circ id of 0 and no path. This feature will cause Tor to build
29005 a new 'fast' general purpose circuit using its own path selection
29007 - Added a BUILDTIMEOUT_SET controller event to describe changes
29008 to the circuit build timeout.
29009 - Future-proof the controller protocol a bit by ignoring keyword
29010 arguments we do not recognize.
29011 - Expand homedirs passed to tor-checkkey. This should silence a
29012 coverity complaint about passing a user-supplied string into
29013 open() without checking it.
29016 Changes in version 0.2.1.25 - 2010-03-16
29017 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
29018 prevent relays from guessing their IP address correctly. It also fixes
29019 several minor potential security bugs.
29022 - Fix a regression from our patch for bug 1244 that caused relays
29023 to guess their IP address incorrectly if they didn't set Address
29024 in their torrc and/or their address fails to resolve. Bugfix on
29025 0.2.1.23; fixes bug 1269.
29026 - When freeing a session key, zero it out completely. We only zeroed
29027 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
29028 patched by ekir. Fixes bug 1254.
29031 - Fix a dereference-then-NULL-check sequence when publishing
29032 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
29034 - Fix another dereference-then-NULL-check sequence. Bugfix on
29035 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
29036 - Make sure we treat potentially not NUL-terminated strings correctly.
29037 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
29041 Changes in version 0.2.1.24 - 2010-02-21
29042 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
29046 - Work correctly out-of-the-box with even more vendor-patched versions
29047 of OpenSSL. In particular, make it so Debian and OS X don't need
29048 customized patches to run/build.
29051 Changes in version 0.2.1.23 - 2010-02-13
29052 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
29053 again on the latest OS X, and updates the location of a directory
29056 o Major bugfixes (performance):
29057 - We were selecting our guards uniformly at random, and then weighting
29058 which of our guards we'd use uniformly at random. This imbalance
29059 meant that Tor clients were severely limited on throughput (and
29060 probably latency too) by the first hop in their circuit. Now we
29061 select guards weighted by currently advertised bandwidth. We also
29062 automatically discard guards picked using the old algorithm. Fixes
29063 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
29066 - Make Tor work again on the latest OS X: when deciding whether to
29067 use strange flags to turn TLS renegotiation on, detect the OpenSSL
29068 version at run-time, not compile time. We need to do this because
29069 Apple doesn't update its dev-tools headers when it updates its
29070 libraries in a security patch.
29071 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
29072 that could happen on 32-bit platforms with 64-bit time_t. Also fix
29073 a memory leak when requesting a hidden service descriptor we've
29074 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
29077 o Directory authority changes:
29078 - Change IP address for dannenberg (v3 directory authority), and
29079 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
29080 service directory authority) from the list.
29083 - Refactor resolve_my_address() to not use gethostbyname() anymore.
29084 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
29087 - Avoid a mad rush at the beginning of each month when each client
29088 rotates half of its guards. Instead we spread the rotation out
29089 throughout the month, but we still avoid leaving a precise timestamp
29090 in the state file about when we first picked the guard. Improves
29091 over the behavior introduced in 0.1.2.17.
29094 Changes in version 0.2.2.8-alpha - 2010-01-26
29095 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
29096 causing bridge relays to disappear. If you're running a bridge,
29100 - Fix a memory corruption bug on bridges that occurred during the
29101 inclusion of stats data in extra-info descriptors. Also fix the
29102 interface for geoip_get_bridge_stats* to prevent similar bugs in
29103 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
29104 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
29107 - Ignore OutboundBindAddress when connecting to localhost.
29108 Connections to localhost need to come _from_ localhost, or else
29109 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
29113 Changes in version 0.2.2.7-alpha - 2010-01-19
29114 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
29115 as laying the groundwork for further relay-side performance fixes. It
29116 also starts cleaning up client behavior with respect to the EntryNodes,
29117 ExitNodes, and StrictNodes config options.
29119 This release also rotates two directory authority keys, due to a
29120 security breach of some of the Torproject servers.
29122 o Directory authority changes:
29123 - Rotate keys (both v3 identity and relay identity) for moria1
29126 o Major features (performance):
29127 - We were selecting our guards uniformly at random, and then weighting
29128 which of our guards we'd use uniformly at random. This imbalance
29129 meant that Tor clients were severely limited on throughput (and
29130 probably latency too) by the first hop in their circuit. Now we
29131 select guards weighted by currently advertised bandwidth. We also
29132 automatically discard guards picked using the old algorithm. Fixes
29133 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
29134 - When choosing which cells to relay first, relays can now favor
29135 circuits that have been quiet recently, to provide lower latency
29136 for low-volume circuits. By default, relays enable or disable this
29137 feature based on a setting in the consensus. You can override
29138 this default by using the new "CircuitPriorityHalflife" config
29139 option. Design and code by Ian Goldberg, Can Tang, and Chris
29141 - Add separate per-conn write limiting to go with the per-conn read
29142 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
29143 but never per-conn write limits.
29144 - New consensus params "bwconnrate" and "bwconnburst" to let us
29145 rate-limit client connections as they enter the network. It's
29146 controlled in the consensus so we can turn it on and off for
29147 experiments. It's starting out off. Based on proposal 163.
29149 o Major features (relay selection options):
29150 - Switch to a StrictNodes config option, rather than the previous
29151 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
29152 "StrictExcludeNodes" option.
29153 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
29154 change during a config reload, mark and discard all our origin
29155 circuits. This fix should address edge cases where we change the
29156 config options and but then choose a circuit that we created before
29158 - If EntryNodes or ExitNodes are set, be more willing to use an
29159 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
29161 - Make EntryNodes config option much more aggressive even when
29162 StrictNodes is not set. Before it would prepend your requested
29163 entrynodes to your list of guard nodes, but feel free to use others
29164 after that. Now it chooses only from your EntryNodes if any of
29165 those are available, and only falls back to others if a) they're
29166 all down and b) StrictNodes is not set.
29167 - Now we refresh your entry guards from EntryNodes at each consensus
29168 fetch -- rather than just at startup and then they slowly rot as
29169 the network changes.
29172 - Stop bridge directory authorities from answering dbg-stability.txt
29173 directory queries, which would let people fetch a list of all
29174 bridge identities they track. Bugfix on 0.2.1.6-alpha.
29177 - Log a notice when we get a new control connection. Now it's easier
29178 for security-conscious users to recognize when a local application
29179 is knocking on their controller door. Suggested by bug 1196.
29180 - New config option "CircuitStreamTimeout" to override our internal
29181 timeout schedule for how many seconds until we detach a stream from
29182 a circuit and try a new circuit. If your network is particularly
29183 slow, you might want to set this to a number like 60.
29184 - New controller command "getinfo config-text". It returns the
29185 contents that Tor would write if you send it a SAVECONF command,
29186 so the controller can write the file to disk itself.
29187 - New options for SafeLogging to allow scrubbing only log messages
29188 generated while acting as a relay.
29189 - Ship the bridges spec file in the tarball too.
29190 - Avoid a mad rush at the beginning of each month when each client
29191 rotates half of its guards. Instead we spread the rotation out
29192 throughout the month, but we still avoid leaving a precise timestamp
29193 in the state file about when we first picked the guard. Improves
29194 over the behavior introduced in 0.1.2.17.
29196 o Minor bugfixes (compiling):
29197 - Fix compilation on OS X 10.3, which has a stub mlockall() but
29198 hides it. Bugfix on 0.2.2.6-alpha.
29199 - Fix compilation on Solaris by removing support for the
29200 DisableAllSwap config option. Solaris doesn't have an rlimit for
29201 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
29204 o Minor bugfixes (crashes):
29205 - Do not segfault when writing buffer stats when we haven't observed
29206 a single circuit to report about. Found by Fabian Lanze. Bugfix on
29208 - If we're in the pathological case where there's no exit bandwidth
29209 but there is non-exit bandwidth, or no guard bandwidth but there
29210 is non-guard bandwidth, don't crash during path selection. Bugfix
29212 - Fix an impossible-to-actually-trigger buffer overflow in relay
29213 descriptor generation. Bugfix on 0.1.0.15.
29215 o Minor bugfixes (privacy):
29216 - Fix an instance where a Tor directory mirror might accidentally
29217 log the IP address of a misbehaving Tor client. Bugfix on
29219 - Don't list Windows capabilities in relay descriptors. We never made
29220 use of them, and maybe it's a bad idea to publish them. Bugfix
29223 o Minor bugfixes (other):
29224 - Resolve an edge case in path weighting that could make us misweight
29225 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
29226 - Fix statistics on client numbers by country as seen by bridges that
29227 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
29228 intervals instead of variable 12-to-48-hour intervals.
29229 - After we free an internal connection structure, overwrite it
29230 with a different memory value than we use for overwriting a freed
29231 internal circuit structure. Should help with debugging. Suggested
29233 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
29236 o Removed features:
29237 - Remove the HSAuthorityRecordStats option that version 0 hidden
29238 service authorities could have used to track statistics of overall
29239 hidden service usage.
29242 Changes in version 0.2.1.22 - 2010-01-19
29243 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
29244 authorities -- it would tell you its whole history of bridge descriptors
29245 if you make the right directory request. This stable update also
29246 rotates two of the seven v3 directory authority keys and locations.
29248 o Directory authority changes:
29249 - Rotate keys (both v3 identity and relay identity) for moria1
29253 - Stop bridge directory authorities from answering dbg-stability.txt
29254 directory queries, which would let people fetch a list of all
29255 bridge identities they track. Bugfix on 0.2.1.6-alpha.
29258 Changes in version 0.2.1.21 - 2009-12-21
29259 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
29260 library. If you use Tor on Linux / Unix and you're getting SSL
29261 renegotiation errors, upgrading should help. We also recommend an
29262 upgrade if you're an exit relay.
29265 - Work around a security feature in OpenSSL 0.9.8l that prevents our
29266 handshake from working unless we explicitly tell OpenSSL that we
29267 are using SSL renegotiation safely. We are, of course, but OpenSSL
29268 0.9.8l won't work unless we say we are.
29269 - Avoid crashing if the client is trying to upload many bytes and the
29270 circuit gets torn down at the same time, or if the flip side
29271 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
29274 - Do not refuse to learn about authority certs and v2 networkstatus
29275 documents that are older than the latest consensus. This bug might
29276 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
29277 Spotted and fixed by xmux.
29278 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
29279 trigger platform-specific option misparsing case found by Coverity
29281 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
29282 trigger assert. Fixes bug 1173.
29285 Changes in version 0.2.2.6-alpha - 2009-11-19
29286 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
29287 support for the new lower-footprint "microdescriptor" directory design,
29288 future-proofing our consensus format against new hash functions or
29289 other changes, and an Android port. It also makes Tor compatible with
29290 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
29293 - Directory authorities can now create, vote on, and serve multiple
29294 parallel formats of directory data as part of their voting process.
29295 Partially implements Proposal 162: "Publish the consensus in
29297 - Directory authorities can now agree on and publish small summaries
29298 of router information that clients can use in place of regular
29299 server descriptors. This transition will eventually allow clients
29300 to use far less bandwidth for downloading information about the
29301 network. Begins the implementation of Proposal 158: "Clients
29302 download consensus + microdescriptors".
29303 - The directory voting system is now extensible to use multiple hash
29304 algorithms for signatures and resource selection. Newer formats
29305 are signed with SHA256, with a possibility for moving to a better
29306 hash algorithm in the future.
29307 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
29308 current and future memory pages via mlockall(). On supported
29309 platforms (modern Linux and probably BSD but not Windows or OS X),
29310 this should effectively disable any and all attempts to page out
29311 memory. This option requires that you start your Tor as root --
29312 if you use DisableAllSwap, please consider using the User option
29313 to properly reduce the privileges of your Tor.
29314 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
29315 to help Tor build correctly for Android phones.
29318 - Work around a security feature in OpenSSL 0.9.8l that prevents our
29319 handshake from working unless we explicitly tell OpenSSL that we
29320 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
29321 won't work unless we say we are.
29324 - Fix a crash bug when trying to initialize the evdns module in
29325 Libevent 2. Bugfix on 0.2.1.16-rc.
29326 - Stop logging at severity 'warn' when some other Tor client tries
29327 to establish a circuit with us using weak DH keys. It's a protocol
29328 violation, but that doesn't mean ordinary users need to hear about
29329 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
29330 - Do not refuse to learn about authority certs and v2 networkstatus
29331 documents that are older than the latest consensus. This bug might
29332 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
29333 Spotted and fixed by xmux.
29334 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
29335 - If all authorities restart at once right before a consensus vote,
29336 nobody will vote about "Running", and clients will get a consensus
29337 with no usable relays. Instead, authorities refuse to build a
29338 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
29339 - If your relay can't keep up with the number of incoming create
29340 cells, it would log one warning per failure into your logs. Limit
29341 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
29342 - Bridges now use "reject *:*" as their default exit policy. Bugfix
29343 on 0.2.0.3-alpha; fixes bug 1113.
29344 - Fix a memory leak on directory authorities during voting that was
29345 introduced in 0.2.2.1-alpha. Found via valgrind.
29348 Changes in version 0.2.1.20 - 2009-10-15
29349 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
29350 services at once, prepares for more performance improvements, and
29351 fixes a bunch of smaller bugs.
29353 The Windows and OS X bundles also include a more recent Vidalia,
29354 and switch from Privoxy to Polipo.
29356 The OS X installers are now drag and drop. It's best to un-install
29357 Tor/Vidalia and then install this new bundle, rather than upgrade. If
29358 you want to upgrade, you'll need to update the paths for Tor and Polipo
29359 in the Vidalia Settings window.
29362 - Send circuit or stream sendme cells when our window has decreased
29363 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
29364 by Karsten when testing the "reduce circuit window" performance
29365 patch. Bugfix on the 54th commit on Tor -- from July 2002,
29366 before the release of Tor 0.0.0. This is the new winner of the
29368 - Fix a remotely triggerable memory leak when a consensus document
29369 contains more than one signature from the same voter. Bugfix on
29371 - Avoid segfault in rare cases when finishing an introduction circuit
29372 as a client and finding out that we don't have an introduction key
29373 for it. Fixes bug 1073. Reported by Aaron Swartz.
29376 - Tor now reads the "circwindow" parameter out of the consensus,
29377 and uses that value for its circuit package window rather than the
29378 default of 1000 cells. Begins the implementation of proposal 168.
29380 o New directory authorities:
29381 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
29383 - Move moria1 and tonga to alternate IP addresses.
29386 - Fix a signed/unsigned compile warning in 0.2.1.19.
29387 - Fix possible segmentation fault on directory authorities. Bugfix on
29389 - Fix an extremely rare infinite recursion bug that could occur if
29390 we tried to log a message after shutting down the log subsystem.
29391 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
29392 - Fix an obscure bug where hidden services on 64-bit big-endian
29393 systems might mis-read the timestamp in v3 introduce cells, and
29394 refuse to connect back to the client. Discovered by "rotor".
29395 Bugfix on 0.2.1.6-alpha.
29396 - We were triggering a CLOCK_SKEW controller status event whenever
29397 we connect via the v2 connection protocol to any relay that has
29398 a wrong clock. Instead, we should only inform the controller when
29399 it's a trusted authority that claims our clock is wrong. Bugfix
29400 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
29401 - We were telling the controller about CHECKING_REACHABILITY and
29402 REACHABILITY_FAILED status events whenever we launch a testing
29403 circuit or notice that one has failed. Instead, only tell the
29404 controller when we want to inform the user of overall success or
29405 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
29407 - Don't warn when we're using a circuit that ends with a node
29408 excluded in ExcludeExitNodes, but the circuit is not used to access
29409 the outside world. This should help fix bug 1090. Bugfix on
29411 - Work around a small memory leak in some versions of OpenSSL that
29412 stopped the memory used by the hostname TLS extension from being
29416 - Add a "getinfo status/accepted-server-descriptor" controller
29417 command, which is the recommended way for controllers to learn
29418 whether our server descriptor has been successfully received by at
29419 least on directory authority. Un-recommend good-server-descriptor
29420 getinfo and status events until we have a better design for them.
29423 Changes in version 0.2.2.5-alpha - 2009-10-11
29424 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
29427 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
29429 o Directory authorities:
29430 - Temporarily (just for this release) move dizum to an alternate
29434 Changes in version 0.2.2.4-alpha - 2009-10-10
29435 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
29436 introduces a new unit test framework, shifts directry authority
29437 addresses around to reduce the impact from recent blocking events,
29438 and fixes a few smaller bugs.
29441 - Fix several more asserts in the circuit_build_times code, for
29442 example one that causes Tor to fail to start once we have
29443 accumulated 5000 build times in the state file. Bugfixes on
29444 0.2.2.2-alpha; fixes bug 1108.
29446 o New directory authorities:
29447 - Move moria1 and Tonga to alternate IP addresses.
29450 - Log SSL state transitions at debug level during handshake, and
29451 include SSL states in error messages. This may help debug future
29452 SSL handshake issues.
29453 - Add a new "Handshake" log domain for activities that happen
29454 during the TLS handshake.
29455 - Revert to the "June 3 2009" ip-to-country file. The September one
29456 seems to have removed most US IP addresses.
29457 - Directory authorities now reject Tor relays with versions less than
29458 0.1.2.14. This step cuts out four relays from the current network,
29459 none of which are very big.
29462 - Fix a couple of smaller issues with gathering statistics. Bugfixes
29464 - Fix two memory leaks in the error case of
29465 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
29466 - Don't count one-hop circuits when we're estimating how long it
29467 takes circuits to build on average. Otherwise we'll set our circuit
29468 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
29469 - Directory authorities no longer change their opinion of, or vote on,
29470 whether a router is Running, unless they have themselves been
29471 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
29474 o Code simplifications and refactoring:
29475 - Revise our unit tests to use the "tinytest" framework, so we
29476 can run tests in their own processes, have smarter setup/teardown
29477 code, and so on. The unit test code has moved to its own
29478 subdirectory, and has been split into multiple modules.
29481 Changes in version 0.2.2.3-alpha - 2009-09-23
29482 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
29485 - Fix an overzealous assert in our new circuit build timeout code.
29486 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
29489 - If the networkstatus consensus tells us that we should use a
29490 negative circuit package window, ignore it. Otherwise we'll
29491 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
29494 Changes in version 0.2.2.2-alpha - 2009-09-21
29495 Tor 0.2.2.2-alpha introduces our latest performance improvement for
29496 clients: Tor tracks the average time it takes to build a circuit, and
29497 avoids using circuits that take too long to build. For fast connections,
29498 this feature can cut your expected latency in half. For slow or flaky
29499 connections, it could ruin your Tor experience. Let us know if it does!
29502 - Tor now tracks how long it takes to build client-side circuits
29503 over time, and adapts its timeout to local network performance.
29504 Since a circuit that takes a long time to build will also provide
29505 bad performance, we get significant latency improvements by
29506 discarding the slowest 20% of circuits. Specifically, Tor creates
29507 circuits more aggressively than usual until it has enough data
29508 points for a good timeout estimate. Implements proposal 151.
29509 We are especially looking for reports (good and bad) from users with
29510 both EDGE and broadband connections that can move from broadband
29511 to EDGE and find out if the build-time data in the .tor/state gets
29512 reset without loss of Tor usability. You should also see a notice
29513 log message telling you that Tor has reset its timeout.
29514 - Directory authorities can now vote on arbitrary integer values as
29515 part of the consensus process. This is designed to help set
29516 network-wide parameters. Implements proposal 167.
29517 - Tor now reads the "circwindow" parameter out of the consensus,
29518 and uses that value for its circuit package window rather than the
29519 default of 1000 cells. Begins the implementation of proposal 168.
29522 - Fix a remotely triggerable memory leak when a consensus document
29523 contains more than one signature from the same voter. Bugfix on
29527 - Fix an extremely rare infinite recursion bug that could occur if
29528 we tried to log a message after shutting down the log subsystem.
29529 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
29530 - Fix parsing for memory or time units given without a space between
29531 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
29532 - A networkstatus vote must contain exactly one signature. Spec
29533 conformance issue. Bugfix on 0.2.0.3-alpha.
29534 - Fix an obscure bug where hidden services on 64-bit big-endian
29535 systems might mis-read the timestamp in v3 introduce cells, and
29536 refuse to connect back to the client. Discovered by "rotor".
29537 Bugfix on 0.2.1.6-alpha.
29538 - We were triggering a CLOCK_SKEW controller status event whenever
29539 we connect via the v2 connection protocol to any relay that has
29540 a wrong clock. Instead, we should only inform the controller when
29541 it's a trusted authority that claims our clock is wrong. Bugfix
29542 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
29543 - We were telling the controller about CHECKING_REACHABILITY and
29544 REACHABILITY_FAILED status events whenever we launch a testing
29545 circuit or notice that one has failed. Instead, only tell the
29546 controller when we want to inform the user of overall success or
29547 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
29549 - Don't warn when we're using a circuit that ends with a node
29550 excluded in ExcludeExitNodes, but the circuit is not used to access
29551 the outside world. This should help fix bug 1090, but more problems
29552 remain. Bugfix on 0.2.1.6-alpha.
29553 - Work around a small memory leak in some versions of OpenSSL that
29554 stopped the memory used by the hostname TLS extension from being
29556 - Make our 'torify' script more portable; if we have only one of
29557 'torsocks' or 'tsocks' installed, don't complain to the user;
29558 and explain our warning about tsocks better.
29561 - Add a "getinfo status/accepted-server-descriptor" controller
29562 command, which is the recommended way for controllers to learn
29563 whether our server descriptor has been successfully received by at
29564 least on directory authority. Un-recommend good-server-descriptor
29565 getinfo and status events until we have a better design for them.
29566 - Update to the "September 4 2009" ip-to-country file.
29569 Changes in version 0.2.2.1-alpha - 2009-08-26
29570 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
29571 Tor clients to bootstrap on networks where only port 80 is reachable,
29572 makes it more straightforward to support hardware crypto accelerators,
29573 and starts the groundwork for gathering stats safely at relays.
29576 - Start the process of disabling ".exit" address notation, since it
29577 can be used for a variety of esoteric application-level attacks
29578 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
29581 o New directory authorities:
29582 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
29586 - New AccelName and AccelDir options add support for dynamic OpenSSL
29587 hardware crypto acceleration engines.
29588 - Tor now supports tunneling all of its outgoing connections over
29589 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
29590 configuration options. Code by Christopher Davis.
29593 - Send circuit or stream sendme cells when our window has decreased
29594 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
29595 by Karsten when testing the "reduce circuit window" performance
29596 patch. Bugfix on the 54th commit on Tor -- from July 2002,
29597 before the release of Tor 0.0.0. This is the new winner of the
29600 o New options for gathering stats safely:
29601 - Directory mirrors that set "DirReqStatistics 1" write statistics
29602 about directory requests to disk every 24 hours. As compared to the
29603 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
29604 1) stats are written to disk exactly every 24 hours; 2) estimated
29605 shares of v2 and v3 requests are determined as mean values, not at
29606 the end of a measurement period; 3) unresolved requests are listed
29607 with country code '??'; 4) directories also measure download times.
29608 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
29609 number of exit streams and transferred bytes per port to disk every
29611 - Relays that set "CellStatistics 1" write statistics on how long
29612 cells spend in their circuit queues to disk every 24 hours.
29613 - Entry nodes that set "EntryStatistics 1" write statistics on the
29614 rough number and origins of connecting clients to disk every 24
29616 - Relays that write any of the above statistics to disk and set
29617 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
29618 their extra-info documents.
29621 - New --digests command-line switch to output the digests of the
29622 source files Tor was built with.
29623 - The "torify" script now uses torsocks where available.
29624 - The memarea code now uses a sentinel value at the end of each area
29625 to make sure nothing writes beyond the end of an area. This might
29626 help debug some conceivable causes of bug 930.
29627 - Time and memory units in the configuration file can now be set to
29628 fractional units. For example, "2.5 GB" is now a valid value for
29630 - Certain Tor clients (such as those behind check.torproject.org) may
29631 want to fetch the consensus in an extra early manner. To enable this
29632 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
29633 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
29634 as only certain clients who must have this information sooner should
29636 - Instead of adding the svn revision to the Tor version string, report
29637 the git commit (when we're building from a git checkout).
29640 - If any of the v3 certs we download are unparseable, we should
29641 actually notice the failure so we don't retry indefinitely. Bugfix
29642 on 0.2.0.x; reported by "rotator".
29643 - If the cached cert file is unparseable, warn but don't exit.
29644 - Fix possible segmentation fault on directory authorities. Bugfix on
29646 - When Tor fails to parse a descriptor of any kind, dump it to disk.
29647 Might help diagnosing bug 1051.
29649 o Deprecated and removed features:
29650 - The controller no longer accepts the old obsolete "addr-mappings/"
29651 or "unregistered-servers-" GETINFO values.
29652 - Hidden services no longer publish version 0 descriptors, and clients
29653 do not request or use version 0 descriptors. However, the old hidden
29654 service authorities still accept and serve version 0 descriptors
29655 when contacted by older hidden services/clients.
29656 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
29657 always on; using them is necessary for correct forward-compatible
29659 - Remove support for .noconnect style addresses. Nobody was using
29660 them, and they provided another avenue for detecting Tor users
29661 via application-level web tricks.
29663 o Packaging changes:
29664 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
29665 installer bundles. See
29666 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
29667 for details of what's new in Vidalia 0.2.3.
29668 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
29669 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
29670 configuration file, rather than the old Privoxy.
29671 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
29672 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
29673 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
29674 better compatibility with OS X 10.6, aka Snow Leopard.
29675 - OS X Vidalia Bundle: The multi-package installer is now replaced
29676 by a simple drag and drop to the /Applications folder. This change
29677 occurred with the upgrade to Vidalia 0.2.3.
29680 Changes in version 0.2.1.19 - 2009-07-28
29681 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
29682 services on Tor 0.2.1.3-alpha through 0.2.1.18.
29685 - Make accessing hidden services on 0.2.1.x work right again.
29686 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
29687 part of patch provided by "optimist".
29690 - When a relay/bridge is writing out its identity key fingerprint to
29691 the "fingerprint" file and to its logs, write it without spaces. Now
29692 it will look like the fingerprints in our bridges documentation,
29693 and confuse fewer users.
29696 - Relays no longer publish a new server descriptor if they change
29697 their MaxAdvertisedBandwidth config option but it doesn't end up
29698 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
29699 fixes bug 1026. Patch from Sebastian.
29700 - Avoid leaking memory every time we get a create cell but we have
29701 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
29702 fixes bug 1034. Reported by BarkerJr.
29705 Changes in version 0.2.1.18 - 2009-07-24
29706 Tor 0.2.1.18 lays the foundations for performance improvements,
29707 adds status events to help users diagnose bootstrap problems, adds
29708 optional authentication/authorization for hidden services, fixes a
29709 variety of potential anonymity problems, and includes a huge pile of
29710 other features and bug fixes.
29713 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
29716 Changes in version 0.2.1.17-rc - 2009-07-07
29717 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
29718 candidate for the 0.2.1.x series. It lays the groundwork for further
29719 client performance improvements, and also fixes a big bug with directory
29720 authorities that were causing them to assign Guard and Stable flags
29723 The Windows bundles also finally include the geoip database that we
29724 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
29725 should actually install Torbutton rather than giving you a cryptic
29726 failure message (oops).
29729 - Clients now use the bandwidth values in the consensus, rather than
29730 the bandwidth values in each relay descriptor. This approach opens
29731 the door to more accurate bandwidth estimates once the directory
29732 authorities start doing active measurements. Implements more of
29736 - When Tor clients restart after 1-5 days, they discard all their
29737 cached descriptors as too old, but they still use the cached
29738 consensus document. This approach is good for robustness, but
29739 bad for performance: since they don't know any bandwidths, they
29740 end up choosing at random rather than weighting their choice by
29741 speed. Fixed by the above feature of putting bandwidths in the
29742 consensus. Bugfix on 0.2.0.x.
29743 - Directory authorities were neglecting to mark relays down in their
29744 internal histories if the relays fall off the routerlist without
29745 ever being found unreachable. So there were relays in the histories
29746 that haven't been seen for eight months, and are listed as being
29747 up for eight months. This wreaked havoc on the "median wfu"
29748 and "median mtbf" calculations, in turn making Guard and Stable
29749 flags very wrong, hurting network performance. Fixes bugs 696 and
29750 969. Bugfix on 0.2.0.6-alpha.
29753 - Serve the DirPortFrontPage page even when we have been approaching
29754 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
29755 - The control port would close the connection before flushing long
29756 replies, such as the network consensus, if a QUIT command was issued
29757 before the reply had completed. Now, the control port flushes all
29758 pending replies before closing the connection. Also fixed a spurious
29759 warning when a QUIT command is issued after a malformed or rejected
29760 AUTHENTICATE command, but before the connection was closed. Patch
29761 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
29762 - When we can't find an intro key for a v2 hidden service descriptor,
29763 fall back to the v0 hidden service descriptor and log a bug message.
29764 Workaround for bug 1024.
29765 - Fix a log message that did not respect the SafeLogging option.
29769 - If we're a relay and we change our IP address, be more verbose
29770 about the reason that made us change. Should help track down
29771 further bugs for relays on dynamic IP addresses.
29774 Changes in version 0.2.0.35 - 2009-06-24
29776 - Avoid crashing in the presence of certain malformed descriptors.
29777 Found by lark, and by automated fuzzing.
29778 - Fix an edge case where a malicious exit relay could convince a
29779 controller that the client's DNS question resolves to an internal IP
29780 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
29783 - Finally fix the bug where dynamic-IP relays disappear when their
29784 IP address changes: directory mirrors were mistakenly telling
29785 them their old address if they asked via begin_dir, so they
29786 never got an accurate answer about their new address, so they
29787 just vanished after a day. For belt-and-suspenders, relays that
29788 don't set Address in their config now avoid using begin_dir for
29789 all direct connections. Should fix bugs 827, 883, and 900.
29790 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
29791 that would occur on some exit nodes when DNS failures and timeouts
29792 occurred in certain patterns. Fix for bug 957.
29795 - When starting with a cache over a few days old, do not leak
29796 memory for the obsolete router descriptors in it. Bugfix on
29797 0.2.0.33; fixes bug 672.
29798 - Hidden service clients didn't use a cached service descriptor that
29799 was older than 15 minutes, but wouldn't fetch a new one either,
29800 because there was already one in the cache. Now, fetch a v2
29801 descriptor unless the same descriptor was added to the cache within
29802 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
29805 Changes in version 0.2.1.16-rc - 2009-06-20
29806 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
29807 a bunch of minor bugs.
29810 - Fix an edge case where a malicious exit relay could convince a
29811 controller that the client's DNS question resolves to an internal IP
29812 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
29814 o Major performance improvements (on 0.2.0.x):
29815 - Disable and refactor some debugging checks that forced a linear scan
29816 over the whole server-side DNS cache. These accounted for over 50%
29817 of CPU time on a relatively busy exit node's gprof profile. Found
29819 - Disable some debugging checks that appeared in exit node profile
29823 - Update to the "June 3 2009" ip-to-country file.
29824 - Do not have tor-resolve automatically refuse all .onion addresses;
29825 if AutomapHostsOnResolve is set in your torrc, this will work fine.
29827 o Minor bugfixes (on 0.2.0.x):
29828 - Log correct error messages for DNS-related network errors on
29830 - Fix a race condition that could cause crashes or memory corruption
29831 when running as a server with a controller listening for log
29833 - Avoid crashing when we have a policy specified in a DirPolicy or
29834 SocksPolicy or ReachableAddresses option with ports set on it,
29835 and we re-load the policy. May fix bug 996.
29836 - Hidden service clients didn't use a cached service descriptor that
29837 was older than 15 minutes, but wouldn't fetch a new one either,
29838 because there was already one in the cache. Now, fetch a v2
29839 descriptor unless the same descriptor was added to the cache within
29840 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
29842 o Minor bugfixes (on 0.2.1.x):
29843 - Don't warn users about low port and hibernation mix when they
29844 provide a *ListenAddress directive to fix that. Bugfix on
29846 - When switching back and forth between bridge mode, do not start
29847 gathering GeoIP data until two hours have passed.
29848 - Do not complain that the user has requested an excluded node as
29849 an exit when the node is not really an exit. This could happen
29850 because the circuit was for testing, or an introduction point.
29854 Changes in version 0.2.1.15-rc - 2009-05-25
29855 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
29856 series. It fixes a major bug on fast exit relays, as well as a variety
29857 of more minor bugs.
29859 o Major bugfixes (on 0.2.0.x):
29860 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
29861 that would occur on some exit nodes when DNS failures and timeouts
29862 occurred in certain patterns. Fix for bug 957.
29864 o Minor bugfixes (on 0.2.0.x):
29865 - Actually return -1 in the error case for read_bandwidth_usage().
29866 Harmless bug, since we currently don't care about the return value
29867 anywhere. Bugfix on 0.2.0.9-alpha.
29868 - Provide a more useful log message if bug 977 (related to buffer
29869 freelists) ever reappears, and do not crash right away.
29870 - Fix an assertion failure on 64-bit platforms when we allocated
29871 memory right up to the end of a memarea, then realigned the memory
29872 one step beyond the end. Fixes a possible cause of bug 930.
29873 - Protect the count of open sockets with a mutex, so we can't
29874 corrupt it when two threads are closing or opening sockets at once.
29875 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
29876 - Don't allow a bridge to publish its router descriptor to a
29877 non-bridge directory authority. Fixes part of bug 932.
29878 - When we change to or from being a bridge, reset our counts of
29879 client usage by country. Fixes bug 932.
29880 - Fix a bug that made stream bandwidth get misreported to the
29882 - Stop using malloc_usable_size() to use more area than we had
29883 actually allocated: it was safe, but made valgrind really unhappy.
29884 - Fix a memory leak when v3 directory authorities load their keys
29885 and cert from disk. Bugfix on 0.2.0.1-alpha.
29887 o Minor bugfixes (on 0.2.1.x):
29888 - Fix use of freed memory when deciding to mark a non-addable
29889 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
29892 Changes in version 0.2.1.14-rc - 2009-04-12
29893 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
29894 series. It begins fixing some major performance problems, and also
29895 finally addresses the bug that was causing relays on dynamic IP
29896 addresses to fall out of the directory.
29899 - Clients replace entry guards that were chosen more than a few months
29900 ago. This change should significantly improve client performance,
29901 especially once more people upgrade, since relays that have been
29902 a guard for a long time are currently overloaded.
29904 o Major bugfixes (on 0.2.0):
29905 - Finally fix the bug where dynamic-IP relays disappear when their
29906 IP address changes: directory mirrors were mistakenly telling
29907 them their old address if they asked via begin_dir, so they
29908 never got an accurate answer about their new address, so they
29909 just vanished after a day. For belt-and-suspenders, relays that
29910 don't set Address in their config now avoid using begin_dir for
29911 all direct connections. Should fix bugs 827, 883, and 900.
29912 - Relays were falling out of the networkstatus consensus for
29913 part of a day if they changed their local config but the
29914 authorities discarded their new descriptor as "not sufficiently
29915 different". Now directory authorities accept a descriptor as changed
29916 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
29917 patch by Sebastian.
29918 - Avoid crashing in the presence of certain malformed descriptors.
29919 Found by lark, and by automated fuzzing.
29922 - When generating circuit events with verbose nicknames for
29923 controllers, try harder to look up nicknames for routers on a
29924 circuit. (Previously, we would look in the router descriptors we had
29925 for nicknames, but not in the consensus.) Partial fix for bug 941.
29926 - If the bridge config line doesn't specify a port, assume 443.
29927 This makes bridge lines a bit smaller and easier for users to
29929 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
29930 bytes (aka 20KB/s), to match our documentation. Also update
29931 directory authorities so they always assign the Fast flag to relays
29932 with 20KB/s of capacity. Now people running relays won't suddenly
29933 find themselves not seeing any use, if the network gets faster
29935 - Update to the "April 3 2009" ip-to-country file.
29938 - Avoid trying to print raw memory to the logs when we decide to
29939 give up on downloading a given relay descriptor. Bugfix on
29941 - In tor-resolve, when the Tor client to use is specified by
29942 <hostname>:<port>, actually use the specified port rather than
29943 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
29944 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
29945 - When starting with a cache over a few days old, do not leak
29946 memory for the obsolete router descriptors in it. Bugfix on
29948 - Avoid double-free on list of successfully uploaded hidden
29949 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
29950 - Change memarea_strndup() implementation to work even when
29951 duplicating a string at the end of a page. This bug was
29952 harmless for now, but could have meant crashes later. Fix by
29953 lark. Bugfix on 0.2.1.1-alpha.
29954 - Limit uploaded directory documents to be 16M rather than 500K.
29955 The directory authorities were refusing v3 consensus votes from
29956 other authorities, since the votes are now 504K. Fixes bug 959;
29957 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
29958 - Directory authorities should never send a 503 "busy" response to
29959 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
29963 Changes in version 0.2.1.13-alpha - 2009-03-09
29964 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
29965 cleanups. We're finally getting close to a release candidate.
29968 - Correctly update the list of which countries we exclude as
29969 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
29970 lark. Bugfix on 0.2.1.6-alpha.
29972 o Minor bugfixes (on 0.2.0.x and earlier):
29973 - Automatically detect MacOSX versions earlier than 10.4.0, and
29974 disable kqueue from inside Tor when running with these versions.
29975 We previously did this from the startup script, but that was no
29976 help to people who didn't use the startup script. Resolves bug 863.
29977 - When we had picked an exit node for a connection, but marked it as
29978 "optional", and it turned out we had no onion key for the exit,
29979 stop wanting that exit and try again. This situation may not
29980 be possible now, but will probably become feasible with proposal
29981 158. Spotted by rovv. Fixes another case of bug 752.
29982 - Clients no longer cache certificates for authorities they do not
29983 recognize. Bugfix on 0.2.0.9-alpha.
29984 - When we can't transmit a DNS request due to a network error, retry
29985 it after a while, and eventually transmit a failing response to
29986 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
29987 - If the controller claimed responsibility for a stream, but that
29988 stream never finished making its connection, it would live
29989 forever in circuit_wait state. Now we close it after SocksTimeout
29990 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
29991 - Drop begin cells to a hidden service if they come from the middle
29992 of a circuit. Patch from lark.
29993 - When we erroneously receive two EXTEND cells for the same circuit
29994 ID on the same connection, drop the second. Patch from lark.
29995 - Fix a crash that occurs on exit nodes when a nameserver request
29996 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
29997 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
29999 - Do not assume that a stack-allocated character array will be
30000 64-bit aligned on platforms that demand that uint64_t access is
30001 aligned. Possible fix for bug 604.
30002 - Parse dates and IPv4 addresses in a locale- and libc-independent
30003 manner, to avoid platform-dependent behavior on malformed input.
30004 - Build correctly when configured to build outside the main source
30005 path. Patch from Michael Gold.
30006 - We were already rejecting relay begin cells with destination port
30007 of 0. Now also reject extend cells with destination port or address
30008 of 0. Suggested by lark.
30010 o Minor bugfixes (on 0.2.1.x):
30011 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
30012 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
30013 - If we're an exit node, scrub the IP address to which we are exiting
30014 in the logs. Bugfix on 0.2.1.8-alpha.
30017 - On Linux, use the prctl call to re-enable core dumps when the user
30019 - New controller event NEWCONSENSUS that lists the networkstatus
30020 lines for every recommended relay. Now controllers like Torflow
30021 can keep up-to-date on which relays they should be using.
30022 - Update to the "February 26 2009" ip-to-country file.
30025 Changes in version 0.2.0.34 - 2009-02-08
30026 Tor 0.2.0.34 features several more security-related fixes. You should
30027 upgrade, especially if you run an exit relay (remote crash) or a
30028 directory authority (remote infinite loop), or you're on an older
30029 (pre-XP) or not-recently-patched Windows (remote exploit).
30031 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
30032 have many known flaws, and nobody should be using them. You should
30033 upgrade. If you're using a Linux or BSD and its packages are obsolete,
30034 stop using those packages and upgrade anyway.
30037 - Fix an infinite-loop bug on handling corrupt votes under certain
30038 circumstances. Bugfix on 0.2.0.8-alpha.
30039 - Fix a temporary DoS vulnerability that could be performed by
30040 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
30041 - Avoid a potential crash on exit nodes when processing malformed
30042 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
30043 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
30044 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
30047 - Fix compilation on systems where time_t is a 64-bit integer.
30048 Patch from Matthias Drochner.
30049 - Don't consider expiring already-closed client connections. Fixes
30050 bug 893. Bugfix on 0.0.2pre20.
30053 Changes in version 0.2.1.12-alpha - 2009-02-08
30054 Tor 0.2.1.12-alpha features several more security-related fixes. You
30055 should upgrade, especially if you run an exit relay (remote crash) or
30056 a directory authority (remote infinite loop), or you're on an older
30057 (pre-XP) or not-recently-patched Windows (remote exploit). It also
30058 includes a big pile of minor bugfixes and cleanups.
30061 - Fix an infinite-loop bug on handling corrupt votes under certain
30062 circumstances. Bugfix on 0.2.0.8-alpha.
30063 - Fix a temporary DoS vulnerability that could be performed by
30064 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
30065 - Avoid a potential crash on exit nodes when processing malformed
30066 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
30069 - Let controllers actually ask for the "clients_seen" event for
30070 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
30071 reported by Matt Edman.
30072 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
30074 - Fix a bug in address parsing that was preventing bridges or hidden
30075 service targets from being at IPv6 addresses.
30076 - Solve a bug that kept hardware crypto acceleration from getting
30077 enabled when accounting was turned on. Fixes bug 907. Bugfix on
30079 - Remove a bash-ism from configure.in to build properly on non-Linux
30080 platforms. Bugfix on 0.2.1.1-alpha.
30081 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
30082 headers. Bugfix on 0.2.0.10-alpha.
30083 - Don't consider expiring already-closed client connections. Fixes
30084 bug 893. Bugfix on 0.0.2pre20.
30085 - Fix another interesting corner-case of bug 891 spotted by rovv:
30086 Previously, if two hosts had different amounts of clock drift, and
30087 one of them created a new connection with just the wrong timing,
30088 the other might decide to deprecate the new connection erroneously.
30089 Bugfix on 0.1.1.13-alpha.
30090 - Resolve a very rare crash bug that could occur when the user forced
30091 a nameserver reconfiguration during the middle of a nameserver
30092 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
30093 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
30094 Bugfix on 0.2.1.7-alpha.
30095 - If we're using bridges and our network goes away, be more willing
30096 to forgive our bridges and try again when we get an application
30097 request. Bugfix on 0.2.0.x.
30100 - Support platforms where time_t is 64 bits long. (Congratulations,
30101 NetBSD!) Patch from Matthias Drochner.
30102 - Add a 'getinfo status/clients-seen' controller command, in case
30103 controllers want to hear clients_seen events but connect late.
30106 - Disable GCC's strict alias optimization by default, to avoid the
30107 likelihood of its introducing subtle bugs whenever our code violates
30108 the letter of C99's alias rules.
30111 Changes in version 0.2.0.33 - 2009-01-21
30112 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
30113 useful to users. It also finally fixes a bug where a relay or client
30114 that's been off for many days would take a long time to bootstrap.
30116 This update also fixes an important security-related bug reported by
30117 Ilja van Sprundel. You should upgrade. (We'll send out more details
30118 about the bug once people have had some time to upgrade.)
30121 - Fix a heap-corruption bug that may be remotely triggerable on
30122 some platforms. Reported by Ilja van Sprundel.
30125 - When a stream at an exit relay is in state "resolving" or
30126 "connecting" and it receives an "end" relay cell, the exit relay
30127 would silently ignore the end cell and not close the stream. If
30128 the client never closes the circuit, then the exit relay never
30129 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
30130 reported by "wood".
30131 - When sending CREATED cells back for a given circuit, use a 64-bit
30132 connection ID to find the right connection, rather than an addr:port
30133 combination. Now that we can have multiple OR connections between
30134 the same ORs, it is no longer possible to use addr:port to uniquely
30135 identify a connection.
30136 - Bridge relays that had DirPort set to 0 would stop fetching
30137 descriptors shortly after startup, and then briefly resume
30138 after a new bandwidth test and/or after publishing a new bridge
30139 descriptor. Bridge users that try to bootstrap from them would
30140 get a recent networkstatus but would get descriptors from up to
30141 18 hours earlier, meaning most of the descriptors were obsolete
30142 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
30143 - Prevent bridge relays from serving their 'extrainfo' document
30144 to anybody who asks, now that extrainfo docs include potentially
30145 sensitive aggregated client geoip summaries. Bugfix on
30147 - If the cached networkstatus consensus is more than five days old,
30148 discard it rather than trying to use it. In theory it could be
30149 useful because it lists alternate directory mirrors, but in practice
30150 it just means we spend many minutes trying directory mirrors that
30151 are long gone from the network. Also discard router descriptors as
30152 we load them if they are more than five days old, since the onion
30153 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
30156 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
30157 could make gcc generate non-functional binary search code. Bugfix
30159 - Build correctly on platforms without socklen_t.
30160 - Compile without warnings on solaris.
30161 - Avoid potential crash on internal error during signature collection.
30162 Fixes bug 864. Patch from rovv.
30163 - Correct handling of possible malformed authority signing key
30164 certificates with internal signature types. Fixes bug 880.
30165 Bugfix on 0.2.0.3-alpha.
30166 - Fix a hard-to-trigger resource leak when logging credential status.
30168 - When we can't initialize DNS because the network is down, do not
30169 automatically stop Tor from starting. Instead, we retry failed
30170 dns_init() every 10 minutes, and change the exit policy to reject
30171 *:* until one succeeds. Fixes bug 691.
30172 - Use 64 bits instead of 32 bits for connection identifiers used with
30173 the controller protocol, to greatly reduce risk of identifier reuse.
30174 - When we're choosing an exit node for a circuit, and we have
30175 no pending streams, choose a good general exit rather than one that
30176 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
30177 - Fix another case of assuming, when a specific exit is requested,
30178 that we know more than the user about what hosts it allows.
30179 Fixes one case of bug 752. Patch from rovv.
30180 - Clip the MaxCircuitDirtiness config option to a minimum of 10
30181 seconds. Warn the user if lower values are given in the
30182 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
30183 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
30184 user if lower values are given in the configuration. Bugfix on
30185 0.1.1.17-rc. Patch by Sebastian.
30186 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
30187 the cache because we already had a v0 descriptor with the same ID.
30188 Bugfix on 0.2.0.18-alpha.
30189 - Fix a race condition when freeing keys shared between main thread
30190 and CPU workers that could result in a memory leak. Bugfix on
30191 0.1.0.1-rc. Fixes bug 889.
30192 - Send a valid END cell back when a client tries to connect to a
30193 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
30194 840. Patch from rovv.
30195 - Check which hops rendezvous stream cells are associated with to
30196 prevent possible guess-the-streamid injection attacks from
30197 intermediate hops. Fixes another case of bug 446. Based on patch
30199 - If a broken client asks a non-exit router to connect somewhere,
30200 do not even do the DNS lookup before rejecting the connection.
30201 Fixes another case of bug 619. Patch from rovv.
30202 - When a relay gets a create cell it can't decrypt (e.g. because it's
30203 using the wrong onion key), we were dropping it and letting the
30204 client time out. Now actually answer with a destroy cell. Fixes
30205 bug 904. Bugfix on 0.0.2pre8.
30207 o Minor bugfixes (hidden services):
30208 - Do not throw away existing introduction points on SIGHUP. Bugfix on
30209 0.0.6pre1. Patch by Karsten. Fixes bug 874.
30212 - Report the case where all signatures in a detached set are rejected
30213 differently than the case where there is an error handling the
30215 - When we realize that another process has modified our cached
30216 descriptors, print out a more useful error message rather than
30217 triggering an assertion. Fixes bug 885. Patch from Karsten.
30218 - Implement the 0x20 hack to better resist DNS poisoning: set the
30219 case on outgoing DNS requests randomly, and reject responses that do
30220 not match the case correctly. This logic can be disabled with the
30221 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
30222 of servers that do not reliably preserve case in replies. See
30223 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
30225 - Check DNS replies for more matching fields to better resist DNS
30227 - Never use OpenSSL compression: it wastes RAM and CPU trying to
30228 compress cells, which are basically all encrypted, compressed, or
30232 Changes in version 0.2.1.11-alpha - 2009-01-20
30233 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
30234 week it will take a long time to bootstrap again" bug. It also fixes
30235 an important security-related bug reported by Ilja van Sprundel. You
30236 should upgrade. (We'll send out more details about the bug once people
30237 have had some time to upgrade.)
30240 - Fix a heap-corruption bug that may be remotely triggerable on
30241 some platforms. Reported by Ilja van Sprundel.
30244 - Discard router descriptors as we load them if they are more than
30245 five days old. Otherwise if Tor is off for a long time and then
30246 starts with cached descriptors, it will try to use the onion
30247 keys in those obsolete descriptors when building circuits. Bugfix
30248 on 0.2.0.x. Fixes bug 887.
30251 - Try to make sure that the version of Libevent we're running with
30252 is binary-compatible with the one we built with. May address bug
30254 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
30255 for bug 905. Bugfix on 0.2.1.7-alpha.
30256 - Add a new --enable-local-appdata configuration switch to change
30257 the default location of the datadir on win32 from APPDATA to
30258 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
30259 entirely. Patch from coderman.
30262 - Make outbound DNS packets respect the OutboundBindAddress setting.
30263 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
30264 - When our circuit fails at the first hop (e.g. we get a destroy
30265 cell back), avoid using that OR connection anymore, and also
30266 tell all the one-hop directory requests waiting for it that they
30267 should fail. Bugfix on 0.2.1.3-alpha.
30268 - In the torify(1) manpage, mention that tsocks will leak your
30272 Changes in version 0.2.1.10-alpha - 2009-01-06
30273 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
30274 would make the bridge relay not so useful if it had DirPort set to 0,
30275 and one that could let an attacker learn a little bit of information
30276 about the bridge's users), and a bug that would cause your Tor relay
30277 to ignore a circuit create request it can't decrypt (rather than reply
30278 with an error). It also fixes a wide variety of other bugs.
30281 - If the cached networkstatus consensus is more than five days old,
30282 discard it rather than trying to use it. In theory it could
30283 be useful because it lists alternate directory mirrors, but in
30284 practice it just means we spend many minutes trying directory
30285 mirrors that are long gone from the network. Helps bug 887 a bit;
30287 - Bridge relays that had DirPort set to 0 would stop fetching
30288 descriptors shortly after startup, and then briefly resume
30289 after a new bandwidth test and/or after publishing a new bridge
30290 descriptor. Bridge users that try to bootstrap from them would
30291 get a recent networkstatus but would get descriptors from up to
30292 18 hours earlier, meaning most of the descriptors were obsolete
30293 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
30294 - Prevent bridge relays from serving their 'extrainfo' document
30295 to anybody who asks, now that extrainfo docs include potentially
30296 sensitive aggregated client geoip summaries. Bugfix on
30300 - New controller event "clients_seen" to report a geoip-based summary
30301 of which countries we've seen clients from recently. Now controllers
30302 like Vidalia can show bridge operators that they're actually making
30304 - Build correctly against versions of OpenSSL 0.9.8 or later built
30305 without support for deprecated functions.
30306 - Update to the "December 19 2008" ip-to-country file.
30308 o Minor bugfixes (on 0.2.0.x):
30309 - Authorities now vote for the Stable flag for any router whose
30310 weighted MTBF is at least 5 days, regardless of the mean MTBF.
30311 - Do not remove routers as too old if we do not have any consensus
30312 document. Bugfix on 0.2.0.7-alpha.
30313 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
30314 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
30315 - When an exit relay resolves a stream address to a local IP address,
30316 do not just keep retrying that same exit relay over and
30317 over. Instead, just close the stream. Addresses bug 872. Bugfix
30318 on 0.2.0.32. Patch from rovv.
30319 - If a hidden service sends us an END cell, do not consider
30320 retrying the connection; just close it. Patch from rovv.
30321 - When we made bridge authorities stop serving bridge descriptors over
30322 unencrypted links, we also broke DirPort reachability testing for
30323 bridges. So bridges with a non-zero DirPort were printing spurious
30324 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
30325 - When a relay gets a create cell it can't decrypt (e.g. because it's
30326 using the wrong onion key), we were dropping it and letting the
30327 client time out. Now actually answer with a destroy cell. Fixes
30328 bug 904. Bugfix on 0.0.2pre8.
30329 - Squeeze 2-5% out of client performance (according to oprofile) by
30330 improving the implementation of some policy-manipulation functions.
30332 o Minor bugfixes (on 0.2.1.x):
30333 - Make get_interface_address() function work properly again; stop
30334 guessing the wrong parts of our address as our address.
30335 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
30336 send on that circuit. Otherwise we might violate the proposal-110
30337 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
30339 - When we're sending non-EXTEND cells to the first hop in a circuit,
30340 for example to use an encrypted directory connection, we don't need
30341 to use RELAY_EARLY cells: the first hop knows what kind of cell
30342 it is, and nobody else can even see the cell type. Conserving
30343 RELAY_EARLY cells makes it easier to cannibalize circuits like
30345 - Stop logging nameserver addresses in reverse order.
30346 - If we are retrying a directory download slowly over and over, do
30347 not automatically give up after the 254th failure. Bugfix on
30349 - Resume reporting accurate "stream end" reasons to the local control
30350 port. They were lost in the changes for Proposal 148. Bugfix on
30353 o Deprecated and removed features:
30354 - The old "tor --version --version" command, which would print out
30355 the subversion "Id" of most of the source files, is now removed. It
30356 turned out to be less useful than we'd expected, and harder to
30359 o Code simplifications and refactoring:
30360 - Change our header file guard macros to be less likely to conflict
30361 with system headers. Adam Langley noticed that we were conflicting
30362 with log.h on Android.
30363 - Tool-assisted documentation cleanup. Nearly every function or
30364 static variable in Tor should have its own documentation now.
30367 Changes in version 0.2.1.9-alpha - 2008-12-25
30368 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
30370 o New directory authorities:
30371 - gabelmoo (the authority run by Karsten Loesing) now has a new
30375 - Never use a connection with a mismatched address to extend a
30376 circuit, unless that connection is canonical. A canonical
30377 connection is one whose address is authenticated by the router's
30378 identity key, either in a NETINFO cell or in a router descriptor.
30379 - Avoid a possible memory corruption bug when receiving hidden service
30380 descriptors. Bugfix on 0.2.1.6-alpha.
30383 - Fix a logic error that would automatically reject all but the first
30384 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
30385 part of bug 813/868. Bug spotted by coderman.
30386 - When a stream at an exit relay is in state "resolving" or
30387 "connecting" and it receives an "end" relay cell, the exit relay
30388 would silently ignore the end cell and not close the stream. If
30389 the client never closes the circuit, then the exit relay never
30390 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
30391 reported by "wood".
30392 - When we can't initialize DNS because the network is down, do not
30393 automatically stop Tor from starting. Instead, retry failed
30394 dns_init() every 10 minutes, and change the exit policy to reject
30395 *:* until one succeeds. Fixes bug 691.
30398 - Give a better error message when an overzealous init script says
30399 "sudo -u username tor --user username". Makes Bug 882 easier for
30401 - When a directory authority gives us a new guess for our IP address,
30402 log which authority we used. Hopefully this will help us debug
30403 the recent complaints about bad IP address guesses.
30404 - Detect svn revision properly when we're using git-svn.
30405 - Try not to open more than one descriptor-downloading connection
30406 to an authority at once. This should reduce load on directory
30407 authorities. Fixes bug 366.
30408 - Add cross-certification to newly generated certificates, so that
30409 a signing key is enough information to look up a certificate.
30410 Partial implementation of proposal 157.
30411 - Start serving certificates by <identity digest, signing key digest>
30412 pairs. Partial implementation of proposal 157.
30413 - Clients now never report any stream end reason except 'MISC'.
30414 Implements proposal 148.
30415 - On platforms with a maximum syslog string length, truncate syslog
30416 messages to that length ourselves, rather than relying on the
30417 system to do it for us.
30418 - Optimize out calls to time(NULL) that occur for every IO operation,
30419 or for every cell. On systems where time() is a slow syscall,
30420 this fix will be slightly helpful.
30421 - Exit servers can now answer resolve requests for ip6.arpa addresses.
30422 - When we download a descriptor that we then immediately (as
30423 a directory authority) reject, do not retry downloading it right
30424 away. Should save some bandwidth on authorities. Fix for bug
30425 888. Patch by Sebastian Hahn.
30426 - When a download gets us zero good descriptors, do not notify
30427 Tor that new directory information has arrived.
30428 - Avoid some nasty corner cases in the logic for marking connections
30429 as too old or obsolete or noncanonical for circuits. Partial
30432 o Minor features (controller):
30433 - New CONSENSUS_ARRIVED event to note when a new consensus has
30434 been fetched and validated.
30435 - When we realize that another process has modified our cached
30436 descriptors file, print out a more useful error message rather
30437 than triggering an assertion. Fixes bug 885. Patch from Karsten.
30438 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
30439 controllers to prevent SIGHUP from reloading the
30440 configuration. Fixes bug 856.
30443 - Resume using the correct "REASON=" stream when telling the
30444 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
30445 - When a canonical connection appears later in our internal list
30446 than a noncanonical one for a given OR ID, always use the
30447 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
30449 - Clip the MaxCircuitDirtiness config option to a minimum of 10
30450 seconds. Warn the user if lower values are given in the
30451 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
30452 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
30453 user if lower values are given in the configuration. Bugfix on
30454 0.1.1.17-rc. Patch by Sebastian.
30455 - Fix a race condition when freeing keys shared between main thread
30456 and CPU workers that could result in a memory leak. Bugfix on
30457 0.1.0.1-rc. Fixes bug 889.
30459 o Minor bugfixes (hidden services):
30460 - Do not throw away existing introduction points on SIGHUP (bugfix on
30461 0.0.6pre1); also, do not stall hidden services because we're
30462 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
30463 by John Brooks. Patch by Karsten. Fixes bug 874.
30464 - Fix a memory leak when we decline to add a v2 rendezvous
30465 descriptor to the cache because we already had a v0 descriptor
30466 with the same ID. Bugfix on 0.2.0.18-alpha.
30468 o Deprecated and removed features:
30469 - RedirectExits has been removed. It was deprecated since
30471 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
30472 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
30473 - Cell pools are now always enabled; --disable-cell-pools is ignored.
30475 o Code simplifications and refactoring:
30476 - Rename the confusing or_is_obsolete field to the more appropriate
30477 is_bad_for_new_circs, and move it to or_connection_t where it
30479 - Move edge-only flags from connection_t to edge_connection_t: not
30480 only is this better coding, but on machines of plausible alignment,
30481 it should save 4-8 bytes per connection_t. "Every little bit helps."
30482 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
30483 for consistency; keep old option working for backward compatibility.
30484 - Simplify the code for finding connections to use for a circuit.
30487 Changes in version 0.2.1.8-alpha - 2008-12-08
30488 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
30489 builds better on unusual platforms like Solaris and old OS X, and
30490 fixes a variety of other issues.
30493 - New DirPortFrontPage option that takes an html file and publishes
30494 it as "/" on the DirPort. Now relay operators can provide a
30495 disclaimer without needing to set up a separate webserver. There's
30496 a sample disclaimer in contrib/tor-exit-notice.html.
30499 - When the client is choosing entry guards, now it selects at most
30500 one guard from a given relay family. Otherwise we could end up with
30501 all of our entry points into the network run by the same operator.
30502 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
30505 - Fix a DOS opportunity during the voting signature collection process
30506 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
30507 - Fix a possible segfault when establishing an exit connection. Bugfix
30511 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
30513 - Made Tor a little less aggressive about deleting expired
30514 certificates. Partial fix for bug 854.
30515 - Stop doing unaligned memory access that generated bus errors on
30516 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
30517 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
30518 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
30519 - Make USR2 log-level switch take effect immediately. Bugfix on
30521 - If one win32 nameserver fails to get added, continue adding the
30522 rest, and don't automatically fail.
30523 - Use fcntl() for locking when flock() is not available. Should fix
30524 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
30525 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
30526 could make gcc generate non-functional binary search code. Bugfix
30528 - Build correctly on platforms without socklen_t.
30529 - Avoid potential crash on internal error during signature collection.
30530 Fixes bug 864. Patch from rovv.
30531 - Do not use C's stdio library for writing to log files. This will
30532 improve logging performance by a minute amount, and will stop
30533 leaking fds when our disk is full. Fixes bug 861.
30534 - Stop erroneous use of O_APPEND in cases where we did not in fact
30535 want to re-seek to the end of a file before every last write().
30536 - Correct handling of possible malformed authority signing key
30537 certificates with internal signature types. Fixes bug 880. Bugfix
30539 - Fix a hard-to-trigger resource leak when logging credential status.
30543 - Directory mirrors no longer fetch the v1 directory or
30544 running-routers files. They are obsolete, and nobody asks for them
30545 anymore. This is the first step to making v1 authorities obsolete.
30547 o Minor features (controller):
30548 - Return circuit purposes in response to GETINFO circuit-status. Fixes
30552 Changes in version 0.2.0.32 - 2008-11-20
30553 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
30554 packages (and maybe other packages) noticed by Theo de Raadt, fixes
30555 a smaller security flaw that might allow an attacker to access local
30556 services, further improves hidden service performance, and fixes a
30557 variety of other issues.
30560 - The "User" and "Group" config options did not clear the
30561 supplementary group entries for the Tor process. The "User" option
30562 is now more robust, and we now set the groups to the specified
30563 user's primary group. The "Group" option is now ignored. For more
30564 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
30565 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
30566 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
30567 - The "ClientDNSRejectInternalAddresses" config option wasn't being
30568 consistently obeyed: if an exit relay refuses a stream because its
30569 exit policy doesn't allow it, we would remember what IP address
30570 the relay said the destination address resolves to, even if it's
30571 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
30574 - Fix a DOS opportunity during the voting signature collection process
30575 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
30577 o Major bugfixes (hidden services):
30578 - When fetching v0 and v2 rendezvous service descriptors in parallel,
30579 we were failing the whole hidden service request when the v0
30580 descriptor fetch fails, even if the v2 fetch is still pending and
30581 might succeed. Similarly, if the last v2 fetch fails, we were
30582 failing the whole hidden service request even if a v0 fetch is
30583 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
30584 - When extending a circuit to a hidden service directory to upload a
30585 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
30586 requests failed, because the router descriptor has not been
30587 downloaded yet. In these cases, do not attempt to upload the
30588 rendezvous descriptor, but wait until the router descriptor is
30589 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
30590 descriptor from a hidden service directory for which the router
30591 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
30595 - Fix several infrequent memory leaks spotted by Coverity.
30596 - When testing for libevent functions, set the LDFLAGS variable
30597 correctly. Found by Riastradh.
30598 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
30599 bootstrapping with tunneled directory connections. Bugfix on
30600 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
30601 - When asked to connect to A.B.exit:80, if we don't know the IP for A
30602 and we know that server B rejects most-but-not all connections to
30603 port 80, we would previously reject the connection. Now, we assume
30604 the user knows what they were asking for. Fixes bug 752. Bugfix
30605 on 0.0.9rc5. Diagnosed by BarkerJr.
30606 - If we overrun our per-second write limits a little, count this as
30607 having used up our write allocation for the second, and choke
30608 outgoing directory writes. Previously, we had only counted this when
30609 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
30610 Bugfix on 0.2.0.x (??).
30611 - Remove the old v2 directory authority 'lefkada' from the default
30612 list. It has been gone for many months.
30613 - Stop doing unaligned memory access that generated bus errors on
30614 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
30615 - Make USR2 log-level switch take effect immediately. Bugfix on
30618 o Minor bugfixes (controller):
30619 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
30620 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
30623 Changes in version 0.2.1.7-alpha - 2008-11-08
30624 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
30625 packages (and maybe other packages) noticed by Theo de Raadt, fixes
30626 a smaller security flaw that might allow an attacker to access local
30627 services, adds better defense against DNS poisoning attacks on exit
30628 relays, further improves hidden service performance, and fixes a
30629 variety of other issues.
30632 - The "ClientDNSRejectInternalAddresses" config option wasn't being
30633 consistently obeyed: if an exit relay refuses a stream because its
30634 exit policy doesn't allow it, we would remember what IP address
30635 the relay said the destination address resolves to, even if it's
30636 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
30637 - The "User" and "Group" config options did not clear the
30638 supplementary group entries for the Tor process. The "User" option
30639 is now more robust, and we now set the groups to the specified
30640 user's primary group. The "Group" option is now ignored. For more
30641 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
30642 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
30643 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
30644 - Do not use or believe expired v3 authority certificates. Patch
30645 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
30648 - Now NodeFamily and MyFamily config options allow spaces in
30649 identity fingerprints, so it's easier to paste them in.
30650 Suggested by Lucky Green.
30651 - Implement the 0x20 hack to better resist DNS poisoning: set the
30652 case on outgoing DNS requests randomly, and reject responses that do
30653 not match the case correctly. This logic can be disabled with the
30654 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
30655 of servers that do not reliably preserve case in replies. See
30656 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
30658 - Preserve case in replies to DNSPort requests in order to support
30659 the 0x20 hack for resisting DNS poisoning attacks.
30661 o Hidden service performance improvements:
30662 - When the client launches an introduction circuit, retry with a
30663 new circuit after 30 seconds rather than 60 seconds.
30664 - Launch a second client-side introduction circuit in parallel
30665 after a delay of 15 seconds (based on work by Christian Wilms).
30666 - Hidden services start out building five intro circuits rather
30667 than three, and when the first three finish they publish a service
30668 descriptor using those. Now we publish our service descriptor much
30669 faster after restart.
30672 - Minor fix in the warning messages when you're having problems
30673 bootstrapping; also, be more forgiving of bootstrap problems when
30674 we're still making incremental progress on a given bootstrap phase.
30675 - When we're choosing an exit node for a circuit, and we have
30676 no pending streams, choose a good general exit rather than one that
30677 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
30678 - Send a valid END cell back when a client tries to connect to a
30679 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
30680 840. Patch from rovv.
30681 - If a broken client asks a non-exit router to connect somewhere,
30682 do not even do the DNS lookup before rejecting the connection.
30683 Fixes another case of bug 619. Patch from rovv.
30684 - Fix another case of assuming, when a specific exit is requested,
30685 that we know more than the user about what hosts it allows.
30686 Fixes another case of bug 752. Patch from rovv.
30687 - Check which hops rendezvous stream cells are associated with to
30688 prevent possible guess-the-streamid injection attacks from
30689 intermediate hops. Fixes another case of bug 446. Based on patch
30691 - Avoid using a negative right-shift when comparing 32-bit
30692 addresses. Possible fix for bug 845 and bug 811.
30693 - Make the assert_circuit_ok() function work correctly on circuits that
30694 have already been marked for close.
30695 - Fix read-off-the-end-of-string error in unit tests when decoding
30696 introduction points.
30697 - Fix uninitialized size field for memory area allocation: may improve
30698 memory performance during directory parsing.
30699 - Treat duplicate certificate fetches as failures, so that we do
30700 not try to re-fetch an expired certificate over and over and over.
30701 - Do not say we're fetching a certificate when we'll in fact skip it
30702 because of a pending download.
30705 Changes in version 0.2.1.6-alpha - 2008-09-30
30706 Tor 0.2.1.6-alpha further improves performance and robustness of
30707 hidden services, starts work on supporting per-country relay selection,
30708 and fixes a variety of smaller issues.
30711 - Implement proposal 121: make it possible to build hidden services
30712 that only certain clients are allowed to connect to. This is
30713 enforced at several points, so that unauthorized clients are unable
30714 to send INTRODUCE cells to the service, or even (depending on the
30715 type of authentication) to learn introduction points. This feature
30716 raises the bar for certain kinds of active attacks against hidden
30717 services. Code by Karsten Loesing.
30718 - Relays now store and serve v2 hidden service descriptors by default,
30719 i.e., the new default value for HidServDirectoryV2 is 1. This is
30720 the last step in proposal 114, which aims to make hidden service
30721 lookups more reliable.
30722 - Start work to allow node restrictions to include country codes. The
30723 syntax to exclude nodes in a country with country code XX is
30724 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
30725 refinement to decide what config options should take priority if
30726 you ask to both use a particular node and exclude it.
30727 - Allow ExitNodes list to include IP ranges and country codes, just
30728 like the Exclude*Nodes lists. Patch from Robert Hogan.
30731 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
30732 Tor to fail to start if you had it configured to use a bridge
30733 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
30734 - When extending a circuit to a hidden service directory to upload a
30735 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
30736 requests failed, because the router descriptor had not been
30737 downloaded yet. In these cases, we now wait until the router
30738 descriptor is downloaded, and then retry. Likewise, clients
30739 now skip over a hidden service directory if they don't yet have
30740 its router descriptor, rather than futilely requesting it and
30741 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
30743 - When fetching v0 and v2 rendezvous service descriptors in parallel,
30744 we were failing the whole hidden service request when the v0
30745 descriptor fetch fails, even if the v2 fetch is still pending and
30746 might succeed. Similarly, if the last v2 fetch fails, we were
30747 failing the whole hidden service request even if a v0 fetch is
30748 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
30749 - DNS replies need to have names matching their requests, but
30750 these names should be in the questions section, not necessarily
30751 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
30754 - Update to the "September 1 2008" ip-to-country file.
30755 - Allow ports 465 and 587 in the default exit policy again. We had
30756 rejected them in 0.1.0.15, because back in 2005 they were commonly
30757 misconfigured and ended up as spam targets. We hear they are better
30758 locked down these days.
30759 - Use a lockfile to make sure that two Tor processes are not
30760 simultaneously running with the same datadir.
30761 - Serve the latest v3 networkstatus consensus via the control
30762 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
30763 - Better logging about stability/reliability calculations on directory
30765 - Drop the requirement to have an open dir port for storing and
30766 serving v2 hidden service descriptors.
30767 - Directory authorities now serve a /tor/dbg-stability.txt URL to
30768 help debug WFU and MTBF calculations.
30769 - Implement most of Proposal 152: allow specialized servers to permit
30770 single-hop circuits, and clients to use those servers to build
30771 single-hop circuits when using a specialized controller. Patch
30772 from Josh Albrecht. Resolves feature request 768.
30773 - Add a -p option to tor-resolve for specifying the SOCKS port: some
30774 people find host:port too confusing.
30775 - Make TrackHostExit mappings expire a while after their last use, not
30776 after their creation. Patch from Robert Hogan.
30777 - Provide circuit purposes along with circuit events to the controller.
30780 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
30782 - Fixed some memory leaks -- some quite frequent, some almost
30783 impossible to trigger -- based on results from Coverity.
30784 - When testing for libevent functions, set the LDFLAGS variable
30785 correctly. Found by Riastradh.
30786 - Fix an assertion bug in parsing policy-related options; possible fix
30788 - Catch and report a few more bootstrapping failure cases when Tor
30789 fails to establish a TCP connection. Cleanup on 0.2.1.x.
30790 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
30791 bootstrapping with tunneled directory connections. Bugfix on
30792 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
30793 - When asked to connect to A.B.exit:80, if we don't know the IP for A
30794 and we know that server B rejects most-but-not all connections to
30795 port 80, we would previously reject the connection. Now, we assume
30796 the user knows what they were asking for. Fixes bug 752. Bugfix
30797 on 0.0.9rc5. Diagnosed by BarkerJr.
30798 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
30799 service directories if they have no advertised dir port. Bugfix
30801 - If we overrun our per-second write limits a little, count this as
30802 having used up our write allocation for the second, and choke
30803 outgoing directory writes. Previously, we had only counted this when
30804 we had met our limits precisely. Fixes bug 824. Patch by rovv.
30805 Bugfix on 0.2.0.x (??).
30806 - Avoid a "0 divided by 0" calculation when calculating router uptime
30807 at directory authorities. Bugfix on 0.2.0.8-alpha.
30808 - Make DNS resolved controller events into "CLOSED", not
30809 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
30811 - Fix a bug where an unreachable relay would establish enough
30812 reachability testing circuits to do a bandwidth test -- if
30813 we already have a connection to the middle hop of the testing
30814 circuit, then it could establish the last hop by using the existing
30815 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
30816 circuits no longer use entry guards in 0.2.1.3-alpha.
30817 - If we have correct permissions on $datadir, we complain to stdout
30818 and fail to start. But dangerous permissions on
30819 $datadir/cached-status/ would cause us to open a log and complain
30820 there. Now complain to stdout and fail to start in both cases. Fixes
30821 bug 820, reported by seeess.
30822 - Remove the old v2 directory authority 'lefkada' from the default
30823 list. It has been gone for many months.
30825 o Code simplifications and refactoring:
30826 - Revise the connection_new functions so that a more typesafe variant
30827 exists. This will work better with Coverity, and let us find any
30828 actual mistakes we're making here.
30829 - Refactor unit testing logic so that dmalloc can be used sensibly
30830 with unit tests to check for memory leaks.
30831 - Move all hidden-service related fields from connection and circuit
30832 structure to substructures: this way they won't eat so much memory.
30835 Changes in version 0.2.0.31 - 2008-09-03
30836 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
30837 a big bug we're seeing where in rare cases traffic from one Tor stream
30838 gets mixed into another stream, and fixes a variety of smaller issues.
30841 - Make sure that two circuits can never exist on the same connection
30842 with the same circuit ID, even if one is marked for close. This
30843 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
30844 - Relays now reject risky extend cells: if the extend cell includes
30845 a digest of all zeroes, or asks to extend back to the relay that
30846 sent the extend cell, tear down the circuit. Ideas suggested
30848 - If not enough of our entry guards are available so we add a new
30849 one, we might use the new one even if it overlapped with the
30850 current circuit's exit relay (or its family). Anonymity bugfix
30851 pointed out by rovv.
30854 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
30855 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
30856 - Correctly detect the presence of the linux/netfilter_ipv4.h header
30857 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
30858 - Pick size of default geoip filename string correctly on windows.
30859 Fixes bug 806. Bugfix on 0.2.0.30.
30860 - Make the autoconf script accept the obsolete --with-ssl-dir
30861 option as an alias for the actually-working --with-openssl-dir
30862 option. Fix the help documentation to recommend --with-openssl-dir.
30863 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
30864 - When using the TransPort option on OpenBSD, and using the User
30865 option to change UID and drop privileges, make sure to open
30866 /dev/pf before dropping privileges. Fixes bug 782. Patch from
30867 Christopher Davis. Bugfix on 0.1.2.1-alpha.
30868 - Try to attach connections immediately upon receiving a RENDEZVOUS2
30869 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
30870 on the client side when connecting to a hidden service. Bugfix
30871 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
30872 - When closing an application-side connection because its circuit is
30873 getting torn down, generate the stream event correctly. Bugfix on
30874 0.1.2.x. Anonymous patch.
30877 Changes in version 0.2.1.5-alpha - 2008-08-31
30878 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
30879 in a lot of the infrastructure for adding authorization to hidden
30880 services, lays the groundwork for having clients read their load
30881 balancing information out of the networkstatus consensus rather than
30882 the individual router descriptors, addresses two potential anonymity
30883 issues, and fixes a variety of smaller issues.
30886 - Convert many internal address representations to optionally hold
30888 - Generate and accept IPv6 addresses in many protocol elements.
30889 - Make resolver code handle nameservers located at ipv6 addresses.
30890 - Begin implementation of proposal 121 ("Client authorization for
30891 hidden services"): configure hidden services with client
30892 authorization, publish descriptors for them, and configure
30893 authorization data for hidden services at clients. The next
30894 step is to actually access hidden services that perform client
30896 - More progress toward proposal 141: Network status consensus
30897 documents and votes now contain bandwidth information for each
30898 router and a summary of that router's exit policy. Eventually this
30899 will be used by clients so that they do not have to download every
30900 known descriptor before building circuits.
30902 o Major bugfixes (on 0.2.0.x and before):
30903 - When sending CREATED cells back for a given circuit, use a 64-bit
30904 connection ID to find the right connection, rather than an addr:port
30905 combination. Now that we can have multiple OR connections between
30906 the same ORs, it is no longer possible to use addr:port to uniquely
30907 identify a connection.
30908 - Relays now reject risky extend cells: if the extend cell includes
30909 a digest of all zeroes, or asks to extend back to the relay that
30910 sent the extend cell, tear down the circuit. Ideas suggested
30912 - If not enough of our entry guards are available so we add a new
30913 one, we might use the new one even if it overlapped with the
30914 current circuit's exit relay (or its family). Anonymity bugfix
30915 pointed out by rovv.
30918 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
30919 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
30920 - When using the TransPort option on OpenBSD, and using the User
30921 option to change UID and drop privileges, make sure to open /dev/pf
30922 before dropping privileges. Fixes bug 782. Patch from Christopher
30923 Davis. Bugfix on 0.1.2.1-alpha.
30924 - Correctly detect the presence of the linux/netfilter_ipv4.h header
30925 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
30926 - Add a missing safe_str() call for a debug log message.
30927 - Use 64 bits instead of 32 bits for connection identifiers used with
30928 the controller protocol, to greatly reduce risk of identifier reuse.
30929 - Make the autoconf script accept the obsolete --with-ssl-dir
30930 option as an alias for the actually-working --with-openssl-dir
30931 option. Fix the help documentation to recommend --with-openssl-dir.
30932 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
30935 - Rate-limit too-many-sockets messages: when they happen, they happen
30936 a lot. Resolves bug 748.
30937 - Resist DNS poisoning a little better by making sure that names in
30938 answer sections match.
30939 - Print the SOCKS5 error message string as well as the error code
30940 when a tor-resolve request fails. Patch from Jacob.
30943 Changes in version 0.2.1.4-alpha - 2008-08-04
30944 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
30947 - The address part of exit policies was not correctly written
30948 to router descriptors. This generated router descriptors that failed
30949 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
30951 - Tor triggered a false assert when extending a circuit to a relay
30952 but we already have a connection open to that relay. Noticed by
30953 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
30956 - Fix a hidden service logging bug: in some edge cases, the router
30957 descriptor of a previously picked introduction point becomes
30958 obsolete and we need to give up on it rather than continually
30959 complaining that it has become obsolete. Observed by xiando. Bugfix
30962 o Removed features:
30963 - Take out the TestVia config option, since it was a workaround for
30964 a bug that was fixed in Tor 0.1.1.21.
30967 Changes in version 0.2.1.3-alpha - 2008-08-03
30968 Tor 0.2.1.3-alpha implements most of the pieces to prevent
30969 infinite-length circuit attacks (see proposal 110); fixes a bug that
30970 might cause exit relays to corrupt streams they send back; allows
30971 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
30972 ExcludeExitNodes config options; and fixes a big pile of bugs.
30974 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
30975 - Send a bootstrap problem "warn" event on the first problem if the
30976 reason is NO_ROUTE (that is, our network is down).
30979 - Implement most of proposal 110: The first K cells to be sent
30980 along a circuit are marked as special "early" cells; only K "early"
30981 cells will be allowed. Once this code is universal, we can block
30982 certain kinds of DOS attack by requiring that EXTEND commands must
30983 be sent using an "early" cell.
30986 - Try to attach connections immediately upon receiving a RENDEZVOUS2
30987 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
30988 on the client side when connecting to a hidden service. Bugfix
30989 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
30990 - Ensure that two circuits can never exist on the same connection
30991 with the same circuit ID, even if one is marked for close. This
30992 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
30995 - When relays do their initial bandwidth measurement, don't limit
30996 to just our entry guards for the test circuits. Otherwise we tend
30997 to have multiple test circuits going through a single entry guard,
30998 which makes our bandwidth test less accurate. Fixes part of bug 654;
30999 patch contributed by Josh Albrecht.
31000 - Add an ExcludeExitNodes option so users can list a set of nodes
31001 that should be be excluded from the exit node position, but
31002 allowed elsewhere. Implements proposal 151.
31003 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
31004 ExcludeNodes and ExcludeExitNodes lists.
31005 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
31006 be more efficient. Formerly it was quadratic in the number of
31007 servers; now it should be linear. Fixes bug 509.
31008 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
31009 and n_conn_id_digest fields into a separate structure that's
31010 only needed when the circuit has not yet attached to an n_conn.
31013 - Change the contrib/tor.logrotate script so it makes the new
31014 logs as "_tor:_tor" rather than the default, which is generally
31015 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
31016 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
31017 warnings (occasionally), but it can also cause the compiler to
31018 eliminate error-checking code. Suggested by Peter Gutmann.
31019 - When a hidden service is giving up on an introduction point candidate
31020 that was not included in the last published rendezvous descriptor,
31021 don't reschedule publication of the next descriptor. Fixes bug 763.
31023 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
31024 HiddenServiceExcludeNodes as obsolete: they never worked properly,
31025 and nobody claims to be using them. Fixes bug 754. Bugfix on
31026 0.1.0.1-rc. Patch from Christian Wilms.
31027 - Fix a small alignment and memory-wasting bug on buffer chunks.
31030 o Minor bugfixes (controller):
31031 - When closing an application-side connection because its circuit
31032 is getting torn down, generate the stream event correctly.
31033 Bugfix on 0.1.2.x. Anonymous patch.
31035 o Removed features:
31036 - Remove all backward-compatibility code to support relays running
31037 versions of Tor so old that they no longer work at all on the
31041 Changes in version 0.2.0.30 - 2008-07-15
31043 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
31044 warnings (occasionally), but it can also cause the compiler to
31045 eliminate error-checking code. Suggested by Peter Gutmann.
31048 Changes in version 0.2.0.29-rc - 2008-07-08
31049 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
31050 hidden-service performance bugs, and fixes a bunch of smaller bugs.
31053 - If you have more than one bridge but don't know their keys,
31054 you would only launch a request for the descriptor of the first one
31055 on your list. (Tor considered launching requests for the others, but
31056 found that it already had a connection on the way for $0000...0000
31057 so it didn't open another.) Bugfix on 0.2.0.x.
31058 - If you have more than one bridge but don't know their keys, and the
31059 connection to one of the bridges failed, you would cancel all
31060 pending bridge connections. (After all, they all have the same
31061 digest.) Bugfix on 0.2.0.x.
31062 - When a hidden service was trying to establish an introduction point,
31063 and Tor had built circuits preemptively for such purposes, we
31064 were ignoring all the preemptive circuits and launching a new one
31065 instead. Bugfix on 0.2.0.14-alpha.
31066 - When a hidden service was trying to establish an introduction point,
31067 and Tor *did* manage to reuse one of the preemptively built
31068 circuits, it didn't correctly remember which one it used,
31069 so it asked for another one soon after, until there were no
31070 more preemptive circuits, at which point it launched one from
31071 scratch. Bugfix on 0.0.9.x.
31072 - Make directory servers include the X-Your-Address-Is: http header in
31073 their responses even for begin_dir conns. Now clients who only
31074 ever use begin_dir connections still have a way to learn their IP
31075 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
31078 - Fix a macro/CPP interaction that was confusing some compilers:
31079 some GCCs don't like #if/#endif pairs inside macro arguments.
31081 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
31082 Fixes bug 704; fix from Steven Murdoch.
31083 - When opening /dev/null in finish_daemonize(), do not pass the
31084 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
31085 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
31086 - Correctly detect transparent proxy support on Linux hosts that
31087 require in.h to be included before netfilter_ipv4.h. Patch
31089 - Disallow session resumption attempts during the renegotiation
31090 stage of the v2 handshake protocol. Clients should never be trying
31091 session resumption at this point, but apparently some did, in
31092 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
31093 found by Geoff Goodell.
31096 Changes in version 0.2.1.2-alpha - 2008-06-20
31097 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
31098 make it easier to set up your own private Tor network; fixes several
31099 big bugs with using more than one bridge relay; fixes a big bug with
31100 offering hidden services quickly after Tor starts; and uses a better
31101 API for reporting potential bootstrapping problems to the controller.
31104 - New TestingTorNetwork config option to allow adjustment of
31105 previously constant values that, while reasonable, could slow
31106 bootstrapping. Implements proposal 135. Patch from Karsten.
31109 - If you have more than one bridge but don't know their digests,
31110 you would only learn a request for the descriptor of the first one
31111 on your list. (Tor considered launching requests for the others, but
31112 found that it already had a connection on the way for $0000...0000
31113 so it didn't open another.) Bugfix on 0.2.0.x.
31114 - If you have more than one bridge but don't know their digests,
31115 and the connection to one of the bridges failed, you would cancel
31116 all pending bridge connections. (After all, they all have the
31117 same digest.) Bugfix on 0.2.0.x.
31118 - When establishing a hidden service, introduction points that
31119 originate from cannibalized circuits are completely ignored and not
31120 included in rendezvous service descriptors. This might be another
31121 reason for delay in making a hidden service available. Bugfix
31122 from long ago (0.0.9.x?)
31125 - Allow OpenSSL to use dynamic locks if it wants.
31126 - When building a consensus, do not include routers that are down.
31127 This will cut down 30% to 40% on consensus size. Implements
31129 - In directory authorities' approved-routers files, allow
31130 fingerprints with or without space.
31131 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
31132 controller can query our current bootstrap state in case it attaches
31133 partway through and wants to catch up.
31134 - Send an initial "Starting" bootstrap status event, so we have a
31135 state to start out in.
31138 - Asking for a conditional consensus at .../consensus/<fingerprints>
31139 would crash a dirserver if it did not already have a
31140 consensus. Bugfix on 0.2.1.1-alpha.
31141 - Clean up some macro/CPP interactions: some GCC versions don't like
31142 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
31145 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
31146 - Directory authorities shouldn't complain about bootstrapping
31147 problems just because they do a lot of reachability testing and
31148 some of the connection attempts fail.
31149 - Start sending "count" and "recommendation" key/value pairs in
31150 bootstrap problem status events, so the controller can hear about
31151 problems even before Tor decides they're worth reporting for sure.
31152 - If you're using bridges, generate "bootstrap problem" warnings
31153 as soon as you run out of working bridges, rather than waiting
31154 for ten failures -- which will never happen if you have less than
31156 - If we close our OR connection because there's been a circuit
31157 pending on it for too long, we were telling our bootstrap status
31158 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
31161 Changes in version 0.2.1.1-alpha - 2008-06-13
31162 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
31163 were making the Tor process bloat especially on Linux; makes our TLS
31164 handshake blend in better; sends "bootstrap phase" status events to
31165 the controller, so it can keep the user informed of progress (and
31166 problems) fetching directory information and establishing circuits;
31167 and adds a variety of smaller features.
31170 - More work on making our TLS handshake blend in: modify the list
31171 of ciphers advertised by OpenSSL in client mode to even more
31172 closely resemble a common web browser. We cheat a little so that
31173 we can advertise ciphers that the locally installed OpenSSL doesn't
31175 - Start sending "bootstrap phase" status events to the controller,
31176 so it can keep the user informed of progress fetching directory
31177 information and establishing circuits. Also inform the controller
31178 if we think we're stuck at a particular bootstrap phase. Implements
31180 - Resume using OpenSSL's RAND_poll() for better (and more portable)
31181 cross-platform entropy collection again. We used to use it, then
31182 stopped using it because of a bug that could crash systems that
31183 called RAND_poll when they had a lot of fds open. It looks like the
31184 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
31185 at startup, and to call RAND_poll() when we reseed later only if
31186 we have a non-buggy OpenSSL version.
31189 - When we choose to abandon a new entry guard because we think our
31190 older ones might be better, close any circuits pending on that
31191 new entry guard connection. This fix should make us recover much
31192 faster when our network is down and then comes back. Bugfix on
31193 0.1.2.8-beta; found by lodger.
31195 o Memory fixes and improvements:
31196 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
31197 to avoid unused RAM in buffer chunks and memory pools.
31198 - Speed up parsing and cut down on memory fragmentation by using
31199 stack-style allocations for parsing directory objects. Previously,
31200 this accounted for over 40% of allocations from within Tor's code
31201 on a typical directory cache.
31202 - Use a Bloom filter rather than a digest-based set to track which
31203 descriptors we need to keep around when we're cleaning out old
31204 router descriptors. This speeds up the computation significantly,
31205 and may reduce fragmentation.
31206 - Reduce the default smartlist size from 32 to 16; it turns out that
31207 most smartlists hold around 8-12 elements tops.
31208 - Make dumpstats() log the fullness and size of openssl-internal
31210 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
31211 patch to their OpenSSL, turn it on to save memory on servers. This
31212 patch will (with any luck) get included in a mainline distribution
31214 - Never use OpenSSL compression: it wastes RAM and CPU trying to
31215 compress cells, which are basically all encrypted, compressed,
31219 - Stop reloading the router list from disk for no reason when we
31220 run out of reachable directory mirrors. Once upon a time reloading
31221 it would set the 'is_running' flag back to 1 for them. It hasn't
31222 done that for a long time.
31223 - In very rare situations new hidden service descriptors were
31224 published earlier than 30 seconds after the last change to the
31225 service. (We currently think that a hidden service descriptor
31226 that's been stable for 30 seconds is worth publishing.)
31229 - Allow separate log levels to be configured for different logging
31230 domains. For example, this allows one to log all notices, warnings,
31231 or errors, plus all memory management messages of level debug or
31232 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
31233 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
31234 and stop using a warning that had become unfixably verbose under
31236 - New --hush command-line option similar to --quiet. While --quiet
31237 disables all logging to the console on startup, --hush limits the
31238 output to messages of warning and error severity.
31239 - Servers support a new URL scheme for consensus downloads that
31240 allows the client to specify which authorities are trusted.
31241 The server then only sends the consensus if the client will trust
31242 it. Otherwise a 404 error is sent back. Clients use this
31243 new scheme when the server supports it (meaning it's running
31244 0.2.1.1-alpha or later). Implements proposal 134.
31245 - New configure/torrc options (--enable-geoip-stats,
31246 DirRecordUsageByCountry) to record how many IPs we've served
31247 directory info to in each country code, how many status documents
31248 total we've sent to each country code, and what share of the total
31249 directory requests we should expect to see.
31250 - Use the TLS1 hostname extension to more closely resemble browser
31252 - Lots of new unit tests.
31253 - Add a macro to implement the common pattern of iterating through
31254 two parallel lists in lockstep.
31257 Changes in version 0.2.0.28-rc - 2008-06-13
31258 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
31259 performance bug, and fixes a bunch of smaller bugs.
31262 - Fix a bug where, when we were choosing the 'end stream reason' to
31263 put in our relay end cell that we send to the exit relay, Tor
31264 clients on Windows were sometimes sending the wrong 'reason'. The
31265 anonymity problem is that exit relays may be able to guess whether
31266 the client is running Windows, thus helping partition the anonymity
31267 set. Down the road we should stop sending reasons to exit relays,
31268 or otherwise prevent future versions of this bug.
31271 - While setting up a hidden service, some valid introduction circuits
31272 were overlooked and abandoned. This might be the reason for
31273 the long delay in making a hidden service available. Bugfix on
31277 - Update to the "June 9 2008" ip-to-country file.
31278 - Run 'make test' as part of 'make dist', so we stop releasing so
31279 many development snapshots that fail their unit tests.
31282 - When we're checking if we have enough dir info for each relay
31283 to begin establishing circuits, make sure that we actually have
31284 the descriptor listed in the consensus, not just any descriptor.
31286 - Bridge relays no longer print "xx=0" in their extrainfo document
31287 for every single country code in the geoip db. Bugfix on
31289 - Only warn when we fail to load the geoip file if we were planning to
31290 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
31291 - If we change our MaxAdvertisedBandwidth and then reload torrc,
31292 Tor won't realize it should publish a new relay descriptor. Fixes
31293 bug 688, reported by mfr. Bugfix on 0.1.2.x.
31294 - When we haven't had any application requests lately, don't bother
31295 logging that we have expired a bunch of descriptors. Bugfix
31297 - Make relay cells written on a connection count as non-padding when
31298 tracking how long a connection has been in use. Bugfix on
31299 0.2.0.1-alpha. Spotted by lodger.
31300 - Fix unit tests in 0.2.0.27-rc.
31301 - Fix compile on Windows.
31304 Changes in version 0.2.0.27-rc - 2008-06-03
31305 Tor 0.2.0.27-rc adds a few features we left out of the earlier
31306 release candidates. In particular, we now include an IP-to-country
31307 GeoIP database, so controllers can easily look up what country a
31308 given relay is in, and so bridge relays can give us some sanitized
31309 summaries about which countries are making use of bridges. (See proposal
31310 126-geoip-fetching.txt for details.)
31313 - Include an IP-to-country GeoIP file in the tarball, so bridge
31314 relays can report sanitized summaries of the usage they're seeing.
31317 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
31318 Robert Hogan. Fixes the first part of bug 681.
31319 - Make bridge authorities never serve extrainfo docs.
31320 - Add support to detect Libevent versions in the 1.4.x series
31322 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
31323 - Include a new contrib/tor-exit-notice.html file that exit relay
31324 operators can put on their website to help reduce abuse queries.
31327 - When tunneling an encrypted directory connection, and its first
31328 circuit fails, do not leave it unattached and ask the controller
31329 to deal. Fixes the second part of bug 681.
31330 - Make bridge authorities correctly expire old extrainfo documents
31334 Changes in version 0.2.0.26-rc - 2008-05-13
31335 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
31336 in Debian's OpenSSL packages. All users running any 0.2.0.x version
31337 should upgrade, whether they're running Debian or not.
31339 o Major security fixes:
31340 - Use new V3 directory authority keys on the tor26, gabelmoo, and
31341 moria1 V3 directory authorities. The old keys were generated with
31342 a vulnerable version of Debian's OpenSSL package, and must be
31343 considered compromised. Other authorities' keys were not generated
31344 with an affected version of OpenSSL.
31347 - List authority signatures as "unrecognized" based on DirServer
31348 lines, not on cert cache. Bugfix on 0.2.0.x.
31351 - Add a new V3AuthUseLegacyKey option to make it easier for
31352 authorities to change their identity keys if they have to.
31355 Changes in version 0.2.0.25-rc - 2008-04-23
31356 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
31359 - Remember to initialize threading before initializing logging.
31360 Otherwise, many BSD-family implementations will crash hard on
31361 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
31364 - Authorities correctly free policies on bad servers on
31365 exit. Fixes bug 672. Bugfix on 0.2.0.x.
31368 Changes in version 0.2.0.24-rc - 2008-04-22
31369 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
31370 v3 directory authority, makes relays with dynamic IP addresses and no
31371 DirPort notice more quickly when their IP address changes, fixes a few
31372 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
31374 o New directory authorities:
31375 - Take lefkada out of the list of v3 directory authorities, since
31376 it has been down for months.
31377 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
31381 - Detect address changes more quickly on non-directory mirror
31382 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
31384 o Minor features (security):
31385 - Reject requests for reverse-dns lookup of names that are in
31386 a private address space. Patch from lodger.
31387 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
31390 o Minor bugfixes (crashes):
31391 - Avoid a rare assert that can trigger when Tor doesn't have much
31392 directory information yet and it tries to fetch a v2 hidden
31393 service descriptor. Fixes bug 651, reported by nwf.
31394 - Initialize log mutex before initializing dmalloc. Otherwise,
31395 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
31396 - Use recursive pthread mutexes in order to avoid deadlock when
31397 logging debug-level messages to a controller. Bug spotted by nwf,
31398 bugfix on 0.2.0.16-alpha.
31400 o Minor bugfixes (resource management):
31401 - Keep address policies from leaking memory: start their refcount
31402 at 1, not 2. Bugfix on 0.2.0.16-alpha.
31403 - Free authority certificates on exit, so they don't look like memory
31404 leaks. Bugfix on 0.2.0.19-alpha.
31405 - Free static hashtables for policy maps and for TLS connections on
31406 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
31407 - Avoid allocating extra space when computing consensuses on 64-bit
31408 platforms. Bug spotted by aakova.
31410 o Minor bugfixes (misc):
31411 - Do not read the configuration file when we've only been told to
31412 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
31413 based on patch from Sebastian Hahn.
31414 - Exit relays that are used as a client can now reach themselves
31415 using the .exit notation, rather than just launching an infinite
31416 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
31417 - When attempting to open a logfile fails, tell us why.
31418 - Fix a dumb bug that was preventing us from knowing that we should
31419 preemptively build circuits to handle expected directory requests.
31420 Fixes bug 660. Bugfix on 0.1.2.x.
31421 - Warn less verbosely about clock skew from netinfo cells from
31422 untrusted sources. Fixes bug 663.
31423 - Make controller stream events for DNS requests more consistent,
31424 by adding "new stream" events for DNS requests, and removing
31425 spurious "stream closed" events" for cached reverse resolves.
31426 Patch from mwenge. Fixes bug 646.
31427 - Correctly notify one-hop connections when a circuit build has
31428 failed. Possible fix for bug 669. Found by lodger.
31431 Changes in version 0.2.0.23-rc - 2008-03-24
31432 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
31433 makes bootstrapping faster if the first directory mirror you contact
31434 is down. The bundles also include the new Vidalia 0.1.2 release.
31437 - When a tunneled directory request is made to a directory server
31438 that's down, notice after 30 seconds rather than 120 seconds. Also,
31439 fail any begindir streams that are pending on it, so they can
31440 retry elsewhere. This was causing multi-minute delays on bootstrap.
31443 Changes in version 0.2.0.22-rc - 2008-03-18
31444 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
31445 enables encrypted directory connections by default for non-relays, fixes
31446 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
31447 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
31450 - Enable encrypted directory connections by default for non-relays,
31451 so censor tools that block Tor directory connections based on their
31452 plaintext patterns will no longer work. This means Tor works in
31453 certain censored countries by default again.
31456 - Make sure servers always request certificates from clients during
31457 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
31458 - Do not enter a CPU-eating loop when a connection is closed in
31459 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
31460 diagnosed by lodger; bugfix on 0.2.0.20-rc.
31461 - Fix assertion failure that could occur when a blocked circuit
31462 became unblocked, and it had pending client DNS requests. Bugfix
31463 on 0.2.0.1-alpha. Fixes bug 632.
31465 o Minor bugfixes (on 0.1.2.x):
31466 - Generate "STATUS_SERVER" events rather than misspelled
31467 "STATUS_SEVER" events. Caught by mwenge.
31468 - When counting the number of bytes written on a TLS connection,
31469 look at the BIO actually used for writing to the network, not
31470 at the BIO used (sometimes) to buffer data for the network.
31471 Looking at different BIOs could result in write counts on the
31472 order of ULONG_MAX. Fixes bug 614.
31473 - On Windows, correctly detect errors when listing the contents of
31474 a directory. Fix from lodger.
31476 o Minor bugfixes (on 0.2.0.x):
31477 - Downgrade "sslv3 alert handshake failure" message to INFO.
31478 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
31479 left BandwidthRate and BandwidthBurst at the default, we would be
31480 silently limited by those defaults. Now raise them to match the
31481 RelayBandwidth* values.
31482 - Fix the SVK version detection logic to work correctly on a branch.
31483 - Make --enable-openbsd-malloc work correctly on Linux with alpha
31484 CPUs. Fixes bug 625.
31485 - Logging functions now check that the passed severity is sane.
31486 - Use proper log levels in the testsuite call of
31487 get_interface_address6().
31488 - When using a nonstandard malloc, do not use the platform values for
31489 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
31490 - Make the openbsd malloc code use 8k pages on alpha CPUs and
31492 - Detect mismatched page sizes when using --enable-openbsd-malloc.
31493 - Avoid double-marked-for-close warning when certain kinds of invalid
31494 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
31495 for bug 617. Bugfix on 0.2.0.1-alpha.
31496 - Make sure that the "NULL-means-reject *:*" convention is followed by
31497 all the policy manipulation functions, avoiding some possible crash
31498 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
31499 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
31500 actually works, and doesn't warn about every single reverse lookup.
31501 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
31504 - Only log guard node status when guard node status has changed.
31505 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
31506 make "INFO" 75% less verbose.
31509 Changes in version 0.2.0.21-rc - 2008-03-02
31510 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
31511 makes Tor work well with Vidalia again, fixes a rare assert bug,
31512 and fixes a pair of more minor bugs. The bundles also include Vidalia
31513 0.1.0 and Torbutton 1.1.16.
31516 - The control port should declare that it requires password auth
31517 when HashedControlSessionPassword is set too. Patch from Matt Edman;
31518 bugfix on 0.2.0.20-rc. Fixes bug 615.
31519 - Downgrade assert in connection_buckets_decrement() to a log message.
31520 This may help us solve bug 614, and in any case will make its
31521 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
31522 - We were sometimes miscounting the number of bytes read from the
31523 network, causing our rate limiting to not be followed exactly.
31524 Bugfix on 0.2.0.16-alpha. Reported by lodger.
31527 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
31528 OpenSSL versions should have been working fine. Diagnosis and patch
31529 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
31530 Bugfix on 0.2.0.20-rc.
31533 Changes in version 0.2.0.20-rc - 2008-02-24
31534 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
31535 makes more progress towards normalizing Tor's TLS handshake, makes
31536 hidden services work better again, helps relays bootstrap if they don't
31537 know their IP address, adds optional support for linking in openbsd's
31538 allocator or tcmalloc, allows really fast relays to scale past 15000
31539 sockets, and fixes a bunch of minor bugs reported by Veracode.
31542 - Enable the revised TLS handshake based on the one designed by
31543 Steven Murdoch in proposal 124, as revised in proposal 130. It
31544 includes version negotiation for OR connections as described in
31545 proposal 105. The new handshake is meant to be harder for censors
31546 to fingerprint, and it adds the ability to detect certain kinds of
31547 man-in-the-middle traffic analysis attacks. The version negotiation
31548 feature will allow us to improve Tor's link protocol more safely
31550 - Choose which bridge to use proportional to its advertised bandwidth,
31551 rather than uniformly at random. This should speed up Tor for
31552 bridge users. Also do this for people who set StrictEntryNodes.
31553 - When a TrackHostExits-chosen exit fails too many times in a row,
31554 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
31557 - Resolved problems with (re-)fetching hidden service descriptors.
31558 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
31559 and 0.2.0.19-alpha.
31560 - If we only ever used Tor for hidden service lookups or posts, we
31561 would stop building circuits and start refusing connections after
31562 24 hours, since we falsely believed that Tor was dormant. Reported
31563 by nwf; bugfix on 0.1.2.x.
31564 - Servers that don't know their own IP address should go to the
31565 authorities for their first directory fetch, even if their DirPort
31566 is off or if they don't know they're reachable yet. This will help
31567 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
31568 - When counting the number of open sockets, count not only the number
31569 of sockets we have received from the socket() call, but also
31570 the number we've gotten from accept() and socketpair(). This bug
31571 made us fail to count all sockets that we were using for incoming
31572 connections. Bugfix on 0.2.0.x.
31573 - Fix code used to find strings within buffers, when those strings
31574 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
31575 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
31576 - Add a new __HashedControlSessionPassword option for controllers
31577 to use for one-off session password hashes that shouldn't get
31578 saved to disk by SAVECONF --- Vidalia users were accumulating a
31579 pile of HashedControlPassword lines in their torrc files, one for
31580 each time they had restarted Tor and then clicked Save. Make Tor
31581 automatically convert "HashedControlPassword" to this new option but
31582 only when it's given on the command line. Partial fix for bug 586.
31584 o Minor features (performance):
31585 - Tune parameters for cell pool allocation to minimize amount of
31587 - Add OpenBSD malloc code from phk as an optional malloc
31588 replacement on Linux: some glibc libraries do very poorly
31589 with Tor's memory allocation patterns. Pass
31590 --enable-openbsd-malloc to get the replacement malloc code.
31591 - Add a --with-tcmalloc option to the configure script to link
31592 against tcmalloc (if present). Does not yet search for
31593 non-system include paths.
31594 - Stop imposing an arbitrary maximum on the number of file descriptors
31595 used for busy servers. Bug reported by Olaf Selke; patch from
31598 o Minor features (other):
31599 - When SafeLogging is disabled, log addresses along with all TLS
31601 - When building with --enable-gcc-warnings, check for whether Apple's
31602 warning "-Wshorten-64-to-32" is available.
31603 - Add a --passphrase-fd argument to the tor-gencert command for
31606 o Minor bugfixes (memory leaks and code problems):
31607 - We were leaking a file descriptor if Tor started with a zero-length
31608 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
31609 - Detect size overflow in zlib code. Reported by Justin Ferguson and
31611 - We were comparing the raw BridgePassword entry with a base64'ed
31612 version of it, when handling a "/tor/networkstatus-bridges"
31613 directory request. Now compare correctly. Noticed by Veracode.
31614 - Recover from bad tracked-since value in MTBF-history file.
31615 Should fix bug 537.
31616 - Alter the code that tries to recover from unhandled write
31617 errors, to not try to flush onto a socket that's given us
31618 unhandled errors. Bugfix on 0.1.2.x.
31619 - Make Unix controlsockets work correctly on OpenBSD. Patch from
31620 tup. Bugfix on 0.2.0.3-alpha.
31622 o Minor bugfixes (other):
31623 - If we have an extra-info document for our server, always make
31624 it available on the control port, even if we haven't gotten
31625 a copy of it from an authority yet. Patch from mwenge.
31626 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
31627 - Directory mirrors no longer include a guess at the client's IP
31628 address if the connection appears to be coming from the same /24
31629 network; it was producing too many wrong guesses.
31630 - Make the new hidden service code respect the SafeLogging setting.
31631 Bugfix on 0.2.0.x. Patch from Karsten.
31632 - When starting as an authority, do not overwrite all certificates
31633 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
31634 - If we're trying to flush the last bytes on a connection (for
31635 example, when answering a directory request), reset the
31636 time-to-give-up timeout every time we manage to write something
31637 on the socket. Bugfix on 0.1.2.x.
31638 - Change the behavior of "getinfo status/good-server-descriptor"
31639 so it doesn't return failure when any authority disappears.
31640 - Even though the man page said that "TrackHostExits ." should
31641 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
31642 - Report TLS "zero return" case as a "clean close" and "IO error"
31643 as a "close". Stop calling closes "unexpected closes": existing
31644 Tors don't use SSL_close(), so having a connection close without
31645 the TLS shutdown handshake is hardly unexpected.
31646 - Send NAMESERVER_STATUS messages for a single failed nameserver
31649 o Code simplifications and refactoring:
31650 - Remove the tor_strpartition function: its logic was confused,
31651 and it was only used for one thing that could be implemented far
31655 Changes in version 0.2.0.19-alpha - 2008-02-09
31656 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
31657 handshake, makes path selection for relays more secure and IP address
31658 guessing more robust, and generally fixes a lot of bugs in preparation
31659 for calling the 0.2.0 branch stable.
31662 - Do not include recognizeable strings in the commonname part of
31663 Tor's x509 certificates.
31666 - If we're a relay, avoid picking ourselves as an introduction point,
31667 a rendezvous point, or as the final hop for internal circuits. Bug
31668 reported by taranis and lodger. Bugfix on 0.1.2.x.
31669 - Patch from "Andrew S. Lists" to catch when we contact a directory
31670 mirror at IP address X and he says we look like we're coming from
31671 IP address X. Bugfix on 0.1.2.x.
31673 o Minor features (security):
31674 - Be more paranoid about overwriting sensitive memory on free(),
31675 as a defensive programming tactic to ensure forward secrecy.
31677 o Minor features (directory authority):
31678 - Actually validate the options passed to AuthDirReject,
31679 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
31680 - Reject router descriptors with out-of-range bandwidthcapacity or
31681 bandwidthburst values.
31683 o Minor features (controller):
31684 - Reject controller commands over 1MB in length. This keeps rogue
31685 processes from running us out of memory.
31687 o Minor features (misc):
31688 - Give more descriptive well-formedness errors for out-of-range
31689 hidden service descriptor/protocol versions.
31690 - Make memory debugging information describe more about history
31691 of cell allocation, so we can help reduce our memory use.
31693 o Deprecated features (controller):
31694 - The status/version/num-versioning and status/version/num-concurring
31695 GETINFO options are no longer useful in the v3 directory protocol:
31696 treat them as deprecated, and warn when they're used.
31699 - When our consensus networkstatus has been expired for a while, stop
31700 being willing to build circuits using it. Fixes bug 401. Bugfix
31702 - Directory caches now fetch certificates from all authorities
31703 listed in a networkstatus consensus, even when they do not
31704 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
31705 - When connecting to a bridge without specifying its key, insert
31706 the connection into the identity-to-connection map as soon as
31707 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
31708 - Detect versions of OS X where malloc_good_size() is present in the
31709 library but never actually declared. Resolves bug 587. Bugfix
31711 - Stop incorrectly truncating zlib responses to directory authority
31712 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
31713 - Stop recommending that every server operator send mail to tor-ops.
31714 Resolves bug 597. Bugfix on 0.1.2.x.
31715 - Don't trigger an assert if we start a directory authority with a
31716 private IP address (like 127.0.0.1).
31717 - Avoid possible failures when generating a directory with routers
31718 with over-long versions strings, or too many flags set. Bugfix
31720 - If an attempt to launch a DNS resolve request over the control
31721 port fails because we have overrun the limit on the number of
31722 connections, tell the controller that the request has failed.
31723 - Avoid using too little bandwidth when our clock skips a few
31724 seconds. Bugfix on 0.1.2.x.
31725 - Fix shell error when warning about missing packages in configure
31726 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
31727 - Do not become confused when receiving a spurious VERSIONS-like
31728 cell from a confused v1 client. Bugfix on 0.2.0.x.
31729 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
31730 introduction points for a hidden service have failed. Patch from
31731 Karsten Loesing. Bugfix on 0.2.0.x.
31733 o Code simplifications and refactoring:
31734 - Remove some needless generality from cpuworker code, for improved
31736 - Stop overloading the circuit_t.onionskin field for both "onionskin
31737 from a CREATE cell that we are waiting for a cpuworker to be
31738 assigned" and "onionskin from an EXTEND cell that we are going to
31739 send to an OR as soon as we are connected". Might help with bug 600.
31740 - Add an in-place version of aes_crypt() so that we can avoid doing a
31741 needless memcpy() call on each cell payload.
31744 Changes in version 0.2.0.18-alpha - 2008-01-25
31745 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
31746 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
31747 that can warn or reject connections to ports generally associated with
31748 vulnerable-plaintext protocols.
31750 o New directory authorities:
31751 - Set up dannenberg (run by CCC) as the sixth v3 directory
31755 - Fix a major memory leak when attempting to use the v2 TLS
31756 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
31757 - We accidentally enabled the under-development v2 TLS handshake
31758 code, which was causing log entries like "TLS error while
31759 renegotiating handshake". Disable it again. Resolves bug 590.
31760 - We were computing the wrong Content-Length: header for directory
31761 responses that need to be compressed on the fly, causing clients
31762 asking for those items to always fail. Bugfix on 0.2.0.x; partially
31766 - Avoid going directly to the directory authorities even if you're a
31767 relay, if you haven't found yourself reachable yet or if you've
31768 decided not to advertise your dirport yet. Addresses bug 556.
31769 - If we've gone 12 hours since our last bandwidth check, and we
31770 estimate we have less than 50KB bandwidth capacity but we could
31771 handle more, do another bandwidth test.
31772 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
31773 Tor can warn and/or refuse connections to ports commonly used with
31774 vulnerable-plaintext protocols. Currently we warn on ports 23,
31775 109, 110, and 143, but we don't reject any.
31778 - When we setconf ClientOnly to 1, close any current OR and Dir
31779 listeners. Reported by mwenge.
31780 - When we get a consensus that's been signed by more people than
31781 we expect, don't log about it; it's not a big deal. Reported
31785 - Don't answer "/tor/networkstatus-bridges" directory requests if
31786 the request isn't encrypted.
31787 - Make "ClientOnly 1" config option disable directory ports too.
31788 - Patches from Karsten Loesing to make v2 hidden services more
31789 robust: work even when there aren't enough HSDir relays available;
31790 retry when a v2 rend desc fetch fails; but don't retry if we
31791 already have a usable v0 rend desc.
31794 Changes in version 0.2.0.17-alpha - 2008-01-17
31795 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
31798 - Make the tor-gencert man page get included correctly in the tarball.
31801 Changes in version 0.2.0.16-alpha - 2008-01-17
31802 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
31803 Loesing, and generally cleans up a lot of features and minor bugs.
31805 o New directory authorities:
31806 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
31809 o Major performance improvements:
31810 - Switch our old ring buffer implementation for one more like that
31811 used by free Unix kernels. The wasted space in a buffer with 1mb
31812 of data will now be more like 8k than 1mb. The new implementation
31813 also avoids realloc();realloc(); patterns that can contribute to
31814 memory fragmentation.
31817 - Configuration files now accept C-style strings as values. This
31818 helps encode characters not allowed in the current configuration
31819 file format, such as newline or #. Addresses bug 557.
31820 - Although we fixed bug 539 (where servers would send HTTP status 503
31821 responses _and_ send a body too), there are still servers out
31822 there that haven't upgraded. Therefore, make clients parse such
31823 bodies when they receive them.
31824 - When we're not serving v2 directory information, there is no reason
31825 to actually keep any around. Remove the obsolete files and directory
31826 on startup if they are very old and we aren't going to serve them.
31828 o Minor performance improvements:
31829 - Reference-count and share copies of address policy entries; only 5%
31830 of them were actually distinct.
31831 - Never walk through the list of logs if we know that no log is
31832 interested in a given message.
31835 - When an authority has not signed a consensus, do not try to
31836 download a nonexistent "certificate with key 00000000". Bugfix
31837 on 0.2.0.x. Fixes bug 569.
31838 - Fix a rare assert error when we're closing one of our threads:
31839 use a mutex to protect the list of logs, so we never write to the
31840 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
31841 bug 575, which is kind of the revenge of bug 222.
31842 - Patch from Karsten Loesing to complain less at both the client
31843 and the relay when a relay used to have the HSDir flag but doesn't
31844 anymore, and we try to upload a hidden service descriptor.
31845 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
31847 - Do not try to download missing certificates until we have tried
31848 to check our fallback consensus. Fixes bug 583.
31849 - Make bridges round reported GeoIP stats info up to the nearest
31850 estimate, not down. Now we can distinguish between "0 people from
31851 this country" and "1 person from this country".
31852 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
31853 - Avoid possible segfault if key generation fails in
31854 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
31855 - Avoid segfault in the case where a badly behaved v2 versioning
31856 directory sends a signed networkstatus with missing client-versions.
31858 - Avoid segfaults on certain complex invocations of
31859 router_get_by_hexdigest(). Bugfix on 0.1.2.
31860 - Correct bad index on array access in parse_http_time(). Bugfix
31862 - Fix possible bug in vote generation when server versions are present
31863 but client versions are not.
31864 - Fix rare bug on REDIRECTSTREAM control command when called with no
31865 port set: it could erroneously report an error when none had
31867 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
31868 compressing large objects and find ourselves with more than 4k
31869 left over. Bugfix on 0.2.0.
31870 - Fix a small memory leak when setting up a hidden service.
31871 - Fix a few memory leaks that could in theory happen under bizarre
31873 - Fix an assert if we post a general-purpose descriptor via the
31874 control port but that descriptor isn't mentioned in our current
31875 network consensus. Bug reported by Jon McLachlan; bugfix on
31878 o Minor features (controller):
31879 - Get NS events working again. Patch from tup.
31880 - The GETCONF command now escapes and quotes configuration values
31881 that don't otherwise fit into the torrc file.
31882 - The SETCONF command now handles quoted values correctly.
31884 o Minor features (directory authorities):
31885 - New configuration options to override default maximum number of
31886 servers allowed on a single IP address. This is important for
31887 running a test network on a single host.
31888 - Actually implement the -s option to tor-gencert.
31889 - Add a manual page for tor-gencert.
31891 o Minor features (bridges):
31892 - Bridge authorities no longer serve bridge descriptors over
31893 unencrypted connections.
31895 o Minor features (other):
31896 - Add hidden services and DNSPorts to the list of things that make
31897 Tor accept that it has running ports. Change starting Tor with no
31898 ports from a fatal error to a warning; we might change it back if
31899 this turns out to confuse anybody. Fixes bug 579.
31902 Changes in version 0.1.2.19 - 2008-01-17
31903 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
31904 exit policy a little bit more conservative so it's safer to run an
31905 exit relay on a home system, and fixes a variety of smaller issues.
31908 - Exit policies now reject connections that are addressed to a
31909 relay's public (external) IP address too, unless
31910 ExitPolicyRejectPrivate is turned off. We do this because too
31911 many relays are running nearby to services that trust them based
31912 on network address.
31915 - When the clock jumps forward a lot, do not allow the bandwidth
31916 buckets to become negative. Fixes bug 544.
31917 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
31918 on every successful resolve. Reported by Mike Perry.
31919 - Purge old entries from the "rephist" database and the hidden
31920 service descriptor database even when DirPort is zero.
31921 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
31922 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
31923 crashing or mis-answering these requests.
31924 - When we decide to send a 503 response to a request for servers, do
31925 not then also send the server descriptors: this defeats the whole
31926 purpose. Fixes bug 539.
31929 - Changing the ExitPolicyRejectPrivate setting should cause us to
31930 rebuild our server descriptor.
31931 - Fix handling of hex nicknames when answering controller requests for
31932 networkstatus by name, or when deciding whether to warn about
31933 unknown routers in a config option. (Patch from mwenge.)
31934 - Fix a couple of hard-to-trigger autoconf problems that could result
31935 in really weird results on platforms whose sys/types.h files define
31936 nonstandard integer types.
31937 - Don't try to create the datadir when running --verify-config or
31938 --hash-password. Resolves bug 540.
31939 - If we were having problems getting a particular descriptor from the
31940 directory caches, and then we learned about a new descriptor for
31941 that router, we weren't resetting our failure count. Reported
31943 - Although we fixed bug 539 (where servers would send HTTP status 503
31944 responses _and_ send a body too), there are still servers out there
31945 that haven't upgraded. Therefore, make clients parse such bodies
31946 when they receive them.
31947 - Run correctly on systems where rlim_t is larger than unsigned long.
31948 This includes some 64-bit systems.
31949 - Run correctly on platforms (like some versions of OS X 10.5) where
31950 the real limit for number of open files is OPEN_FILES, not rlim_max
31951 from getrlimit(RLIMIT_NOFILES).
31952 - Avoid a spurious free on base64 failure.
31953 - Avoid segfaults on certain complex invocations of
31954 router_get_by_hexdigest().
31955 - Fix rare bug on REDIRECTSTREAM control command when called with no
31956 port set: it could erroneously report an error when none had
31960 Changes in version 0.2.0.15-alpha - 2007-12-25
31961 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
31962 features added in 0.2.0.13-alpha.
31965 - Fix several remotely triggerable asserts based on DirPort requests
31966 for a v2 or v3 networkstatus object before we were prepared. This
31967 was particularly bad for 0.2.0.13 and later bridge relays, who
31968 would never have a v2 networkstatus and would thus always crash
31969 when used. Bugfixes on 0.2.0.x.
31970 - Estimate the v3 networkstatus size more accurately, rather than
31971 estimating it at zero bytes and giving it artificially high priority
31972 compared to other directory requests. Bugfix on 0.2.0.x.
31975 - Fix configure.in logic for cross-compilation.
31976 - When we load a bridge descriptor from the cache, and it was
31977 previously unreachable, mark it as retriable so we won't just
31978 ignore it. Also, try fetching a new copy immediately. Bugfixes
31980 - The bridge GeoIP stats were counting other relays, for example
31981 self-reachability and authority-reachability tests.
31984 - Support compilation to target iPhone; patch from cjacker huang.
31985 To build for iPhone, pass the --enable-iphone option to configure.
31988 Changes in version 0.2.0.14-alpha - 2007-12-23
31990 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
31991 without a datadirectory from a previous Tor install. Reported
31993 - Fix a crash when we fetch a descriptor that turns out to be
31994 unexpected (it used to be in our networkstatus when we started
31995 fetching it, but it isn't in our current networkstatus), and we
31996 aren't using bridges. Bugfix on 0.2.0.x.
31997 - Fix a crash when accessing hidden services: it would work the first
31998 time you use a given introduction point for your service, but
31999 on subsequent requests we'd be using garbage memory. Fixed by
32000 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
32001 - Fix a crash when we load a bridge descriptor from disk but we don't
32002 currently have a Bridge line for it in our torrc. Bugfix on
32006 - If bridge authorities set BridgePassword, they will serve a
32007 snapshot of known bridge routerstatuses from their DirPort to
32008 anybody who knows that password. Unset by default.
32011 - Make the unit tests build again.
32012 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
32013 - Make PublishServerDescriptor default to 1, so the default doesn't
32014 have to change as we invent new directory protocol versions.
32015 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
32016 be included unless sys/time.h is already included. Fixes
32017 bug 553. Bugfix on 0.2.0.x.
32018 - If we receive a general-purpose descriptor and then receive an
32019 identical bridge-purpose descriptor soon after, don't discard
32020 the next one as a duplicate.
32023 - If BridgeRelay is set to 1, then the default for
32024 PublishServerDescriptor is now "bridge" rather than "v2,v3".
32025 - If the user sets RelayBandwidthRate but doesn't set
32026 RelayBandwidthBurst, then make them equal rather than erroring out.
32029 Changes in version 0.2.0.13-alpha - 2007-12-21
32030 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
32031 Goodell, fixes many more bugs, and adds a lot of infrastructure for
32034 o New directory authorities:
32035 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
32039 - Only update guard status (usable / not usable) once we have
32040 enough directory information. This was causing us to always pick
32041 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
32042 causing us to discard all our guards on startup if we hadn't been
32043 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
32044 - Purge old entries from the "rephist" database and the hidden
32045 service descriptor databases even when DirPort is zero. Bugfix
32047 - We were ignoring our RelayBandwidthRate for the first 30 seconds
32048 after opening a circuit -- even a relayed circuit. Bugfix on
32050 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
32051 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
32052 crashing or mis-answering these types of requests.
32053 - Relays were publishing their server descriptor to v1 and v2
32054 directory authorities, but they didn't try publishing to v3-only
32055 authorities. Fix this; and also stop publishing to v1 authorities.
32057 - When we were reading router descriptors from cache, we were ignoring
32058 the annotations -- so for example we were reading in bridge-purpose
32059 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
32060 - When we decided to send a 503 response to a request for servers, we
32061 were then also sending the server descriptors: this defeats the
32062 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
32065 - Bridge relays now behave like clients with respect to time
32066 intervals for downloading new consensus documents -- otherwise they
32067 stand out. Bridge users now wait until the end of the interval,
32068 so their bridge relay will be sure to have a new consensus document.
32069 - Three new config options (AlternateDirAuthority,
32070 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
32071 user selectively replace the default directory authorities by type,
32072 rather than the all-or-nothing replacement that DirServer offers.
32073 - Tor can now be configured to read a GeoIP file from disk in one
32074 of two formats. This can be used by controllers to map IP addresses
32075 to countries. Eventually, it may support exit-by-country.
32076 - When possible, bridge relays remember which countries users
32077 are coming from, and report aggregate information in their
32078 extra-info documents, so that the bridge authorities can learn
32079 where Tor is blocked.
32080 - Bridge directory authorities now do reachability testing on the
32081 bridges they know. They provide router status summaries to the
32082 controller via "getinfo ns/purpose/bridge", and also dump summaries
32083 to a file periodically.
32084 - Stop fetching directory info so aggressively if your DirPort is
32085 on but your ORPort is off; stop fetching v2 dir info entirely.
32086 You can override these choices with the new FetchDirInfoEarly
32090 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
32091 consensus documents when there are too many relays at a single
32092 IP address. Now clear it in v2 network status documents too, and
32093 also clear it in routerinfo_t when the relay is no longer listed
32094 in the relevant networkstatus document.
32095 - Don't crash if we get an unexpected value for the
32096 PublishServerDescriptor config option. Reported by Matt Edman;
32097 bugfix on 0.2.0.9-alpha.
32098 - Our new v2 hidden service descriptor format allows descriptors
32099 that have no introduction points. But Tor crashed when we tried
32100 to build a descriptor with no intro points (and it would have
32101 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
32102 by Karsten Loesing.
32103 - Fix building with dmalloc 5.5.2 with glibc.
32104 - Reject uploaded descriptors and extrainfo documents if they're
32105 huge. Otherwise we'll cache them all over the network and it'll
32106 clog everything up. Reported by Aljosha Judmayer.
32107 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
32108 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
32109 - When the DANGEROUS_VERSION controller status event told us we're
32110 running an obsolete version, it used the string "OLD" to describe
32111 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
32112 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
32113 - If we can't expand our list of entry guards (e.g. because we're
32114 using bridges or we have StrictEntryNodes set), don't mark relays
32115 down when they fail a directory request. Otherwise we're too quick
32116 to mark all our entry points down. Bugfix on 0.1.2.x.
32117 - Fix handling of hex nicknames when answering controller requests for
32118 networkstatus by name, or when deciding whether to warn about unknown
32119 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
32120 - Fix a couple of hard-to-trigger autoconf problems that could result
32121 in really weird results on platforms whose sys/types.h files define
32122 nonstandard integer types. Bugfix on 0.1.2.x.
32123 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
32124 - Don't crash on name lookup when we have no current consensus. Fixes
32125 bug 538; bugfix on 0.2.0.x.
32126 - Only Tors that want to mirror the v2 directory info should
32127 create the "cached-status" directory in their datadir. (All Tors
32128 used to create it.) Bugfix on 0.2.0.9-alpha.
32129 - Directory authorities should only automatically download Extra Info
32130 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
32133 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
32134 consumers. (We already do this on HUP.)
32135 - Authorities and caches fetch the v2 networkstatus documents
32136 less often, now that v3 is encouraged.
32137 - Add a new config option BridgeRelay that specifies you want to
32138 be a bridge relay. Right now the only difference is that it makes
32139 you answer begin_dir requests, and it makes you cache dir info,
32140 even if your DirPort isn't on.
32141 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
32142 ask about source, timestamp of arrival, purpose, etc. We need
32143 something like this to help Vidalia not do GeoIP lookups on bridge
32145 - Allow multiple HashedControlPassword config lines, to support
32146 multiple controller passwords.
32147 - Authorities now decide whether they're authoritative for a given
32148 router based on the router's purpose.
32149 - New config options AuthDirBadDir and AuthDirListBadDirs for
32150 authorities to mark certain relays as "bad directories" in the
32151 networkstatus documents. Also supports the "!baddir" directive in
32152 the approved-routers file.
32155 Changes in version 0.2.0.12-alpha - 2007-11-16
32156 This twelfth development snapshot fixes some more build problems as
32157 well as a few minor bugs.
32160 - Make it build on OpenBSD again. Patch from tup.
32161 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
32162 package-building for Red Hat, OS X, etc.
32164 o Minor bugfixes (on 0.1.2.x):
32165 - Changing the ExitPolicyRejectPrivate setting should cause us to
32166 rebuild our server descriptor.
32168 o Minor bugfixes (on 0.2.0.x):
32169 - When we're lacking a consensus, don't try to perform rendezvous
32170 operations. Reported by Karsten Loesing.
32171 - Fix a small memory leak whenever we decide against using a
32172 newly picked entry guard. Reported by Mike Perry.
32173 - When authorities detected more than two relays running on the same
32174 IP address, they were clearing all the status flags but forgetting
32175 to clear the "hsdir" flag. So clients were being told that a
32176 given relay was the right choice for a v2 hsdir lookup, yet they
32177 never had its descriptor because it was marked as 'not running'
32179 - If we're trying to fetch a bridge descriptor and there's no way
32180 the bridge authority could help us (for example, we don't know
32181 a digest, or there is no bridge authority), don't be so eager to
32182 fall back to asking the bridge authority.
32183 - If we're using bridges or have strictentrynodes set, and our
32184 chosen exit is in the same family as all our bridges/entry guards,
32185 then be flexible about families.
32188 - When we negotiate a v2 link-layer connection (not yet implemented),
32189 accept RELAY_EARLY cells and turn them into RELAY cells if we've
32190 negotiated a v1 connection for their next step. Initial code for
32194 Changes in version 0.2.0.11-alpha - 2007-11-12
32195 This eleventh development snapshot fixes some build problems with
32196 the previous snapshot. It also includes a more secure-by-default exit
32197 policy for relays, fixes an enormous memory leak for exit relays, and
32198 fixes another bug where servers were falling out of the directory list.
32201 - Exit policies now reject connections that are addressed to a
32202 relay's public (external) IP address too, unless
32203 ExitPolicyRejectPrivate is turned off. We do this because too
32204 many relays are running nearby to services that trust them based
32205 on network address. Bugfix on 0.1.2.x.
32208 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
32209 on every successful resolve. Reported by Mike Perry; bugfix
32211 - On authorities, never downgrade to old router descriptors simply
32212 because they're listed in the consensus. This created a catch-22
32213 where we wouldn't list a new descriptor because there was an
32214 old one in the consensus, and we couldn't get the new one in the
32215 consensus because we wouldn't list it. Possible fix for bug 548.
32216 Also, this might cause bug 543 to appear on authorities; if so,
32217 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
32219 o Packaging fixes on 0.2.0.10-alpha:
32220 - We were including instructions about what to do with the
32221 src/config/fallback-consensus file, but we weren't actually
32222 including it in the tarball. Disable all of that for now.
32225 - Allow people to say PreferTunnelledDirConns rather than
32226 PreferTunneledDirConns, for those alternate-spellers out there.
32229 - Don't reevaluate all the information from our consensus document
32230 just because we've downloaded a v2 networkstatus that we intend
32231 to cache. Fixes bug 545; bugfix on 0.2.0.x.
32234 Changes in version 0.2.0.10-alpha - 2007-11-10
32235 This tenth development snapshot adds a third v3 directory authority
32236 run by Mike Perry, adds most of Karsten Loesing's new hidden service
32237 descriptor format, fixes a bad crash bug and new bridge bugs introduced
32238 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
32239 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
32240 addresses many more minor issues.
32242 o New directory authorities:
32243 - Set up ides (run by Mike Perry) as the third v3 directory authority.
32246 - Allow tunnelled directory connections to ask for an encrypted
32247 "begin_dir" connection or an anonymized "uses a full Tor circuit"
32248 connection independently. Now we can make anonymized begin_dir
32249 connections for (e.g.) more secure hidden service posting and
32251 - More progress on proposal 114: code from Karsten Loesing to
32252 implement new hidden service descriptor format.
32253 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
32254 accommodate the growing number of servers that use the default
32255 and are reaching it.
32256 - Directory authorities use a new formula for selecting which nodes
32257 to advertise as Guards: they must be in the top 7/8 in terms of
32258 how long we have known about them, and above the median of those
32259 nodes in terms of weighted fractional uptime.
32260 - Make "not enough dir info yet" warnings describe *why* Tor feels
32261 it doesn't have enough directory info yet.
32264 - Stop servers from crashing if they set a Family option (or
32265 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
32267 - Make bridge users work again -- the move to v3 directories in
32268 0.2.0.9-alpha had introduced a number of bugs that made bridges
32269 no longer work for clients.
32270 - When the clock jumps forward a lot, do not allow the bandwidth
32271 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
32273 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
32274 - When the consensus lists a router descriptor that we previously were
32275 mirroring, but that we considered non-canonical, reload the
32276 descriptor as canonical. This fixes bug 543 where Tor servers
32277 would start complaining after a few days that they don't have
32278 enough directory information to build a circuit.
32279 - Consider replacing the current consensus when certificates arrive
32280 that make the pending consensus valid. Previously, we were only
32281 considering replacement when the new certs _didn't_ help.
32282 - Fix an assert error on startup if we didn't already have the
32283 consensus and certs cached in our datadirectory: we were caching
32284 the consensus in consensus_waiting_for_certs but then free'ing it
32286 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
32287 Request) if we need more v3 certs but we've already got pending
32288 requests for all of them.
32289 - Correctly back off from failing certificate downloads. Fixes
32291 - Authorities don't vote on the Running flag if they have been running
32292 for less than 30 minutes themselves. Fixes bug 547, where a newly
32293 started authority would vote that everyone was down.
32295 o New requirements:
32296 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
32297 it, it had no AES, and it hasn't seen any security patches since
32301 - Clients now hold circuitless TLS connections open for 1.5 times
32302 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
32303 rebuild a new circuit over them within that timeframe. Previously,
32304 they held them open only for KeepalivePeriod (5 minutes).
32305 - Use "If-Modified-Since" to avoid retrieving consensus
32306 networkstatuses that we already have.
32307 - When we have no consensus, check FallbackNetworkstatusFile (defaults
32308 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
32309 we start knowing some directory caches.
32310 - When we receive a consensus from the future, warn about skew.
32311 - Improve skew reporting: try to give the user a better log message
32312 about how skewed they are, and how much this matters.
32313 - When we have a certificate for an authority, believe that
32314 certificate's claims about the authority's IP address.
32315 - New --quiet command-line option to suppress the default console log.
32316 Good in combination with --hash-password.
32317 - Authorities send back an X-Descriptor-Not-New header in response to
32318 an accepted-but-discarded descriptor upload. Partially implements
32320 - Make the log message for "tls error. breaking." more useful.
32321 - Better log messages about certificate downloads, to attempt to
32322 track down the second incarnation of bug 546.
32324 o Minor features (bridges):
32325 - If bridge users set UpdateBridgesFromAuthority, but the digest
32326 they ask for is a 404 from the bridge authority, they now fall
32327 back to trying the bridge directly.
32328 - Bridges now use begin_dir to publish their server descriptor to
32329 the bridge authority, even when they haven't set TunnelDirConns.
32331 o Minor features (controller):
32332 - When reporting clock skew, and we know that the clock is _at least
32333 as skewed_ as some value, but we don't know the actual value,
32334 report the value as a "minimum skew."
32337 - Update linux-tor-prio.sh script to allow QoS based on the uid of
32338 the Tor process. Patch from Marco Bonetti with tweaks from Mike
32342 - Refuse to start if both ORPort and UseBridges are set. Bugfix
32343 on 0.2.0.x, suggested by Matt Edman.
32344 - Don't stop fetching descriptors when FetchUselessDescriptors is
32345 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
32346 reported by tup and ioerror.
32347 - Better log message on vote from unknown authority.
32348 - Don't log "Launching 0 request for 0 router" message.
32350 o Minor bugfixes (memory leaks):
32351 - Stop leaking memory every time we parse a v3 certificate. Bugfix
32353 - Stop leaking memory every time we load a v3 certificate. Bugfix
32354 on 0.2.0.1-alpha. Fixes bug 536.
32355 - Stop leaking a cached networkstatus on exit. Bugfix on
32357 - Stop leaking voter information every time we free a consensus.
32358 Bugfix on 0.2.0.3-alpha.
32359 - Stop leaking signed data every time we check a voter signature.
32360 Bugfix on 0.2.0.3-alpha.
32361 - Stop leaking a signature every time we fail to parse a consensus or
32362 a vote. Bugfix on 0.2.0.3-alpha.
32363 - Stop leaking v2_download_status_map on shutdown. Bugfix on
32365 - Stop leaking conn->nickname every time we make a connection to a
32366 Tor relay without knowing its expected identity digest (e.g. when
32367 using bridges). Bugfix on 0.2.0.3-alpha.
32369 - Minor bugfixes (portability):
32370 - Run correctly on platforms where rlim_t is larger than unsigned
32371 long, and/or where the real limit for number of open files is
32372 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
32373 particular, these may be needed for OS X 10.5.
32376 Changes in version 0.1.2.18 - 2007-10-28
32377 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
32378 hidden service introduction that were causing huge delays, and a big
32379 bug that was causing some servers to disappear from the network status
32380 lists for a few hours each day.
32382 o Major bugfixes (crashes):
32383 - If a connection is shut down abruptly because of something that
32384 happened inside connection_flushed_some(), do not call
32385 connection_finished_flushing(). Should fix bug 451:
32386 "connection_stop_writing: Assertion conn->write_event failed"
32387 Bugfix on 0.1.2.7-alpha.
32388 - Fix possible segfaults in functions called from
32389 rend_process_relay_cell().
32391 o Major bugfixes (hidden services):
32392 - Hidden services were choosing introduction points uniquely by
32393 hexdigest, but when constructing the hidden service descriptor
32394 they merely wrote the (potentially ambiguous) nickname.
32395 - Clients now use the v2 intro format for hidden service
32396 connections: they specify their chosen rendezvous point by identity
32397 digest rather than by (potentially ambiguous) nickname. These
32398 changes could speed up hidden service connections dramatically.
32400 o Major bugfixes (other):
32401 - Stop publishing a new server descriptor just because we get a
32402 HUP signal. This led (in a roundabout way) to some servers getting
32403 dropped from the networkstatus lists for a few hours each day.
32404 - When looking for a circuit to cannibalize, consider family as well
32405 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
32406 circuit cannibalization).
32407 - When a router wasn't listed in a new networkstatus, we were leaving
32408 the flags for that router alone -- meaning it remained Named,
32409 Running, etc -- even though absence from the networkstatus means
32410 that it shouldn't be considered to exist at all anymore. Now we
32411 clear all the flags for routers that fall out of the networkstatus
32412 consensus. Fixes bug 529.
32415 - Don't try to access (or alter) the state file when running
32416 --list-fingerprint or --verify-config or --hash-password. Resolves
32418 - When generating information telling us how to extend to a given
32419 router, do not try to include the nickname if it is
32420 absent. Resolves bug 467.
32421 - Fix a user-triggerable segfault in expand_filename(). (There isn't
32422 a way to trigger this remotely.)
32423 - When sending a status event to the controller telling it that an
32424 OR address is reachable, set the port correctly. (Previously we
32425 were reporting the dir port.)
32426 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
32427 command. Bugfix on 0.1.2.17.
32428 - When loading bandwidth history, do not believe any information in
32429 the future. Fixes bug 434.
32430 - When loading entry guard information, do not believe any information
32432 - When we have our clock set far in the future and generate an
32433 onion key, then re-set our clock to be correct, we should not stop
32434 the onion key from getting rotated.
32435 - On some platforms, accept() can return a broken address. Detect
32436 this more quietly, and deal accordingly. Fixes bug 483.
32437 - It's not actually an error to find a non-pending entry in the DNS
32438 cache when canceling a pending resolve. Don't log unless stuff
32439 is fishy. Resolves bug 463.
32440 - Don't reset trusted dir server list when we set a configuration
32441 option. Patch from Robert Hogan.
32442 - Don't try to create the datadir when running --verify-config or
32443 --hash-password. Resolves bug 540.
32446 Changes in version 0.2.0.9-alpha - 2007-10-24
32447 This ninth development snapshot switches clients to the new v3 directory
32448 system; allows servers to be listed in the network status even when they
32449 have the same nickname as a registered server; and fixes many other
32450 bugs including a big one that was causing some servers to disappear
32451 from the network status lists for a few hours each day.
32453 o Major features (directory system):
32454 - Clients now download v3 consensus networkstatus documents instead
32455 of v2 networkstatus documents. Clients and caches now base their
32456 opinions about routers on these consensus documents. Clients only
32457 download router descriptors listed in the consensus.
32458 - Authorities now list servers who have the same nickname as
32459 a different named server, but list them with a new flag,
32460 "Unnamed". Now we can list servers that happen to pick the same
32461 nickname as a server that registered two years ago and then
32462 disappeared. Partially implements proposal 122.
32463 - If the consensus lists a router as "Unnamed", the name is assigned
32464 to a different router: do not identify the router by that name.
32465 Partially implements proposal 122.
32466 - Authorities can now come to a consensus on which method to use to
32467 compute the consensus. This gives us forward compatibility.
32470 - Stop publishing a new server descriptor just because we HUP or
32471 when we find our DirPort to be reachable but won't actually publish
32472 it. New descriptors without any real changes are dropped by the
32473 authorities, and can screw up our "publish every 18 hours" schedule.
32475 - When a router wasn't listed in a new networkstatus, we were leaving
32476 the flags for that router alone -- meaning it remained Named,
32477 Running, etc -- even though absence from the networkstatus means
32478 that it shouldn't be considered to exist at all anymore. Now we
32479 clear all the flags for routers that fall out of the networkstatus
32480 consensus. Fixes bug 529; bugfix on 0.1.2.x.
32481 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
32482 extrainfo documents and then discard them immediately for not
32483 matching the latest router. Bugfix on 0.2.0.1-alpha.
32485 o Minor features (v3 directory protocol):
32486 - Allow tor-gencert to generate a new certificate without replacing
32488 - Allow certificates to include an address.
32489 - When we change our directory-cache settings, reschedule all voting
32490 and download operations.
32491 - Reattempt certificate downloads immediately on failure, as long as
32492 we haven't failed a threshold number of times yet.
32493 - Delay retrying consensus downloads while we're downloading
32494 certificates to verify the one we just got. Also, count getting a
32495 consensus that we already have (or one that isn't valid) as a failure,
32496 and count failing to get the certificates after 20 minutes as a
32498 - Build circuits and download descriptors even if our consensus is a
32499 little expired. (This feature will go away once authorities are
32502 o Minor features (router descriptor cache):
32503 - If we find a cached-routers file that's been sitting around for more
32504 than 28 days unmodified, then most likely it's a leftover from
32505 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
32507 - When we (as a cache) download a descriptor because it was listed
32508 in a consensus, remember when the consensus was supposed to expire,
32509 and don't expire the descriptor until then.
32511 o Minor features (performance):
32512 - Call routerlist_remove_old_routers() much less often. This should
32513 speed startup, especially on directory caches.
32514 - Don't try to launch new descriptor downloads quite so often when we
32515 already have enough directory information to build circuits.
32516 - Base64 decoding was actually showing up on our profile when parsing
32517 the initial descriptor file; switch to an in-process all-at-once
32518 implementation that's about 3.5x times faster than calling out to
32521 o Minor features (compilation):
32522 - Detect non-ASCII platforms (if any still exist) and refuse to
32523 build there: some of our code assumes that 'A' is 65 and so on.
32525 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
32526 - Make the "next period" votes into "current period" votes immediately
32527 after publishing the consensus; avoid a heisenbug that made them
32528 stick around indefinitely.
32529 - When we discard a vote as a duplicate, do not report this as
32531 - Treat missing v3 keys or certificates as an error when running as a
32532 v3 directory authority.
32533 - When we're configured to be a v3 authority, but we're only listed
32534 as a non-v3 authority in our DirServer line for ourself, correct
32536 - If an authority doesn't have a qualified hostname, just put
32537 its address in the vote. This fixes the problem where we referred to
32538 "moria on moria:9031."
32539 - Distinguish between detached signatures for the wrong period, and
32540 detached signatures for a divergent vote.
32541 - Fix a small memory leak when computing a consensus.
32542 - When there's no consensus, we were forming a vote every 30
32543 minutes, but writing the "valid-after" line in our vote based
32544 on our configured V3AuthVotingInterval: so unless the intervals
32545 matched up, we immediately rejected our own vote because it didn't
32546 start at the voting interval that caused us to construct a vote.
32548 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
32549 - Delete unverified-consensus when the real consensus is set.
32550 - Consider retrying a consensus networkstatus fetch immediately
32551 after one fails: don't wait 60 seconds to notice.
32552 - When fetching a consensus as a cache, wait until a newer consensus
32553 should exist before trying to replace the current one.
32554 - Use a more forgiving schedule for retrying failed consensus
32555 downloads than for other types.
32557 o Minor bugfixes (other directory issues):
32558 - Correct the implementation of "download votes by digest." Bugfix on
32560 - Authorities no longer send back "400 you're unreachable please fix
32561 it" errors to Tor servers that aren't online all the time. We're
32562 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
32564 o Minor bugfixes (controller):
32565 - Don't reset trusted dir server list when we set a configuration
32566 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
32567 - Respond to INT and TERM SIGNAL commands before we execute the
32568 signal, in case the signal shuts us down. We had a patch in
32569 0.1.2.1-alpha that tried to do this by queueing the response on
32570 the connection's buffer before shutting down, but that really
32571 isn't the same thing at all. Bug located by Matt Edman.
32573 o Minor bugfixes (misc):
32574 - Correctly check for bad options to the "PublishServerDescriptor"
32575 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
32576 - Stop leaking memory on failing case of base32_decode, and make
32577 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
32578 - Don't try to download extrainfo documents when we're trying to
32579 fetch enough directory info to build a circuit: having enough
32580 info should get priority. Bugfix on 0.2.0.x.
32581 - Don't complain that "your server has not managed to confirm that its
32582 ports are reachable" if we haven't been able to build any circuits
32583 yet. Bug found by spending four hours without a v3 consensus. Bugfix
32585 - Detect the reason for failing to mmap a descriptor file we just
32586 wrote, and give a more useful log message. Fixes bug 533. Bugfix
32589 o Code simplifications and refactoring:
32590 - Remove support for the old bw_accounting file: we've been storing
32591 bandwidth accounting information in the state file since
32592 0.1.2.5-alpha. This may result in bandwidth accounting errors
32593 if you try to upgrade from 0.1.1.x or earlier, or if you try to
32594 downgrade to 0.1.1.x or earlier.
32595 - New convenience code to locate a file within the DataDirectory.
32596 - Move non-authority functionality out of dirvote.c.
32597 - Refactor the arguments for router_pick_{directory_|trusteddir}server
32598 so that they all take the same named flags.
32601 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
32602 Unix users an easy way to script their Tor process (e.g. by
32603 adjusting bandwidth based on the time of the day).
32606 Changes in version 0.2.0.8-alpha - 2007-10-12
32607 This eighth development snapshot fixes a crash bug that's been bothering
32608 us since February 2007, lets bridge authorities store a list of bridge
32609 descriptors they've seen, gets v3 directory voting closer to working,
32610 starts caching v3 directory consensus documents on directory mirrors,
32611 and fixes a variety of smaller issues including some minor memory leaks.
32613 o Major features (router descriptor cache):
32614 - Store routers in a file called cached-descriptors instead of in
32615 cached-routers. Initialize cached-descriptors from cached-routers
32616 if the old format is around. The new format allows us to store
32617 annotations along with descriptors.
32618 - Use annotations to record the time we received each descriptor, its
32619 source, and its purpose.
32620 - Disable the SETROUTERPURPOSE controller command: it is now
32622 - Controllers should now specify cache=no or cache=yes when using
32623 the +POSTDESCRIPTOR command.
32624 - Bridge authorities now write bridge descriptors to disk, meaning
32625 we can export them to other programs and begin distributing them
32628 o Major features (directory authorities):
32629 - When a v3 authority is missing votes or signatures, it now tries
32631 - Directory authorities track weighted fractional uptime as well as
32632 weighted mean-time-between failures. WFU is suitable for deciding
32633 whether a node is "usually up", while MTBF is suitable for deciding
32634 whether a node is "likely to stay up." We need both, because
32635 "usually up" is a good requirement for guards, while "likely to
32636 stay up" is a good requirement for long-lived connections.
32638 o Major features (v3 directory system):
32639 - Caches now download v3 network status documents as needed,
32640 and download the descriptors listed in them.
32641 - All hosts now attempt to download and keep fresh v3 authority
32642 certificates, and re-attempt after failures.
32643 - More internal-consistency checks for vote parsing.
32645 o Major bugfixes (crashes):
32646 - If a connection is shut down abruptly because of something that
32647 happened inside connection_flushed_some(), do not call
32648 connection_finished_flushing(). Should fix bug 451. Bugfix on
32651 o Major bugfixes (performance):
32652 - Fix really bad O(n^2) performance when parsing a long list of
32653 routers: Instead of searching the entire list for an "extra-info "
32654 string which usually wasn't there, once for every routerinfo
32655 we read, just scan lines forward until we find one we like.
32657 - When we add data to a write buffer in response to the data on that
32658 write buffer getting low because of a flush, do not consider the
32659 newly added data as a candidate for immediate flushing, but rather
32660 make it wait until the next round of writing. Otherwise, we flush
32661 and refill recursively, and a single greedy TLS connection can
32662 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
32664 o Minor features (v3 authority system):
32665 - Add more ways for tools to download the votes that lead to the
32667 - Send a 503 when low on bandwidth and a vote, consensus, or
32668 certificate is requested.
32669 - If-modified-since is now implemented properly for all kinds of
32670 certificate requests.
32672 o Minor bugfixes (network statuses):
32673 - Tweak the implementation of proposal 109 slightly: allow at most
32674 two Tor servers on the same IP address, except if it's the location
32675 of a directory authority, in which case allow five. Bugfix on
32678 o Minor bugfixes (controller):
32679 - When sending a status event to the controller telling it that an
32680 OR address is reachable, set the port correctly. (Previously we
32681 were reporting the dir port.) Bugfix on 0.1.2.x.
32683 o Minor bugfixes (v3 directory system):
32684 - Fix logic to look up a cert by its signing key digest. Bugfix on
32686 - Only change the reply to a vote to "OK" if it's not already
32687 set. This gets rid of annoying "400 OK" log messages, which may
32688 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
32689 - When we get a valid consensus, recompute the voting schedule.
32690 - Base the valid-after time of a vote on the consensus voting
32691 schedule, not on our preferred schedule.
32692 - Make the return values and messages from signature uploads and
32693 downloads more sensible.
32694 - Fix a memory leak when serving votes and consensus documents, and
32695 another when serving certificates.
32697 o Minor bugfixes (performance):
32698 - Use a slightly simpler string hashing algorithm (copying Python's
32699 instead of Java's) and optimize our digest hashing algorithm to take
32700 advantage of 64-bit platforms and to remove some possibly-costly
32702 - Fix a minor memory leak whenever we parse guards from our state
32703 file. Bugfix on 0.2.0.7-alpha.
32704 - Fix a minor memory leak whenever we write out a file. Bugfix on
32706 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
32707 command. Bugfix on 0.2.0.5-alpha.
32709 o Minor bugfixes (portability):
32710 - On some platforms, accept() can return a broken address. Detect
32711 this more quietly, and deal accordingly. Fixes bug 483.
32712 - Stop calling tor_strlower() on uninitialized memory in some cases.
32713 Bugfix in 0.2.0.7-alpha.
32715 o Minor bugfixes (usability):
32716 - Treat some 403 responses from directory servers as INFO rather than
32717 WARN-severity events.
32718 - It's not actually an error to find a non-pending entry in the DNS
32719 cache when canceling a pending resolve. Don't log unless stuff is
32720 fishy. Resolves bug 463.
32722 o Minor bugfixes (anonymity):
32723 - Never report that we've used more bandwidth than we're willing to
32724 relay: it leaks how much non-relay traffic we're using. Resolves
32726 - When looking for a circuit to cannibalize, consider family as well
32727 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
32728 circuit cannibalization).
32730 o Code simplifications and refactoring:
32731 - Make a bunch of functions static. Remove some dead code.
32732 - Pull out about a third of the really big routerlist.c; put it in a
32733 new module, networkstatus.c.
32734 - Merge the extra fields in local_routerstatus_t back into
32735 routerstatus_t: we used to need one routerstatus_t for each
32736 authority's opinion, plus a local_routerstatus_t for the locally
32737 computed consensus opinion. To save space, we put the locally
32738 modified fields into local_routerstatus_t, and only the common
32739 stuff into routerstatus_t. But once v3 directories are in use,
32740 clients and caches will no longer need to hold authority opinions;
32741 thus, the rationale for keeping the types separate is now gone.
32742 - Make the code used to reschedule and reattempt downloads more
32744 - Turn all 'Are we a directory server/mirror?' logic into a call to
32746 - Remove the code to generate the oldest (v1) directory format.
32747 The code has been disabled since 0.2.0.5-alpha.
32750 Changes in version 0.2.0.7-alpha - 2007-09-21
32751 This seventh development snapshot makes bridges work again, makes bridge
32752 authorities work for the first time, fixes two huge performance flaws
32753 in hidden services, and fixes a variety of minor issues.
32755 o New directory authorities:
32756 - Set up moria1 and tor26 as the first v3 directory authorities. See
32757 doc/spec/dir-spec.txt for details on the new directory design.
32759 o Major bugfixes (crashes):
32760 - Fix possible segfaults in functions called from
32761 rend_process_relay_cell(). Bugfix on 0.1.2.x.
32763 o Major bugfixes (bridges):
32764 - Fix a bug that made servers send a "404 Not found" in response to
32765 attempts to fetch their server descriptor. This caused Tor servers
32766 to take many minutes to establish reachability for their DirPort,
32767 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
32768 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
32769 users configure that and specify a bridge with an identity
32770 fingerprint, now they will lookup the bridge descriptor at the
32771 default bridge authority via a one-hop tunnel, but once circuits
32772 are established they will switch to a three-hop tunnel for later
32773 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
32775 o Major bugfixes (hidden services):
32776 - Hidden services were choosing introduction points uniquely by
32777 hexdigest, but when constructing the hidden service descriptor
32778 they merely wrote the (potentially ambiguous) nickname.
32779 - Clients now use the v2 intro format for hidden service
32780 connections: they specify their chosen rendezvous point by identity
32781 digest rather than by (potentially ambiguous) nickname. Both
32782 are bugfixes on 0.1.2.x, and they could speed up hidden service
32783 connections dramatically. Thanks to Karsten Loesing.
32785 o Minor features (security):
32786 - As a client, do not believe any server that tells us that an
32787 address maps to an internal address space.
32788 - Make it possible to enable HashedControlPassword and
32789 CookieAuthentication at the same time.
32791 o Minor features (guard nodes):
32792 - Tag every guard node in our state file with the version that
32793 we believe added it, or with our own version if we add it. This way,
32794 if a user temporarily runs an old version of Tor and then switches
32795 back to a new one, she doesn't automatically lose her guards.
32797 o Minor features (speed):
32798 - When implementing AES counter mode, update only the portions of the
32799 counter buffer that need to change, and don't keep separate
32800 network-order and host-order counters when they are the same (i.e.,
32801 on big-endian hosts.)
32803 o Minor features (controller):
32804 - Accept LF instead of CRLF on controller, since some software has a
32805 hard time generating real Internet newlines.
32806 - Add GETINFO values for the server status events
32807 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
32810 o Removed features:
32811 - Routers no longer include bandwidth-history lines in their
32812 descriptors; this information is already available in extra-info
32813 documents, and including it in router descriptors took up 60%
32814 (!) of compressed router descriptor downloads. Completes
32815 implementation of proposal 104.
32816 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
32817 and TorControl.py, as they use the old v0 controller protocol,
32818 and are obsoleted by TorFlow anyway.
32819 - Drop support for v1 rendezvous descriptors, since we never used
32820 them anyway, and the code has probably rotted by now. Based on
32821 patch from Karsten Loesing.
32822 - On OSX, stop warning the user that kqueue support in libevent is
32823 "experimental", since it seems to have worked fine for ages.
32826 - When generating information telling us how to extend to a given
32827 router, do not try to include the nickname if it is absent. Fixes
32828 bug 467. Bugfix on 0.2.0.3-alpha.
32829 - Fix a user-triggerable (but not remotely-triggerable) segfault
32830 in expand_filename(). Bugfix on 0.1.2.x.
32831 - Fix a memory leak when freeing incomplete requests from DNSPort.
32832 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
32833 - Don't try to access (or alter) the state file when running
32834 --list-fingerprint or --verify-config or --hash-password. (Resolves
32835 bug 499.) Bugfix on 0.1.2.x.
32836 - Servers used to decline to publish their DirPort if their
32837 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
32838 were below a threshold. Now they only look at BandwidthRate and
32839 RelayBandwidthRate. Bugfix on 0.1.2.x.
32840 - Remove an optimization in the AES counter-mode code that assumed
32841 that the counter never exceeded 2^68. When the counter can be set
32842 arbitrarily as an IV (as it is by Karsten's new hidden services
32843 code), this assumption no longer holds. Bugfix on 0.1.2.x.
32844 - Resume listing "AUTHORITY" flag for authorities in network status.
32845 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
32847 o Code simplifications and refactoring:
32848 - Revamp file-writing logic so we don't need to have the entire
32849 contents of a file in memory at once before we write to disk. Tor,
32851 - Turn "descriptor store" into a full-fledged type.
32852 - Move all NT services code into a separate source file.
32853 - Unify all code that computes medians, percentile elements, etc.
32854 - Get rid of a needless malloc when parsing address policies.
32857 Changes in version 0.1.2.17 - 2007-08-30
32858 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
32859 X bundles. Vidalia 0.0.14 makes authentication required for the
32860 ControlPort in the default configuration, which addresses important
32861 security risks. Everybody who uses Vidalia (or another controller)
32864 In addition, this Tor update fixes major load balancing problems with
32865 path selection, which should speed things up a lot once many people
32868 o Major bugfixes (security):
32869 - We removed support for the old (v0) control protocol. It has been
32870 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
32871 become more of a headache than it's worth.
32873 o Major bugfixes (load balancing):
32874 - When choosing nodes for non-guard positions, weight guards
32875 proportionally less, since they already have enough load. Patch
32877 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
32878 will allow fast Tor servers to get more attention.
32879 - When we're upgrading from an old Tor version, forget our current
32880 guards and pick new ones according to the new weightings. These
32881 three load balancing patches could raise effective network capacity
32882 by a factor of four. Thanks to Mike Perry for measurements.
32884 o Major bugfixes (stream expiration):
32885 - Expire not-yet-successful application streams in all cases if
32886 they've been around longer than SocksTimeout. Right now there are
32887 some cases where the stream will live forever, demanding a new
32888 circuit every 15 seconds. Fixes bug 454; reported by lodger.
32890 o Minor features (controller):
32891 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
32892 is valid before any authentication has been received. It tells
32893 a controller what kind of authentication is expected, and what
32894 protocol is spoken. Implements proposal 119.
32896 o Minor bugfixes (performance):
32897 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
32898 greatly speeding up loading cached-routers from disk on startup.
32899 - Disable sentinel-based debugging for buffer code: we squashed all
32900 the bugs that this was supposed to detect a long time ago, and now
32901 its only effect is to change our buffer sizes from nice powers of
32902 two (which platform mallocs tend to like) to values slightly over
32903 powers of two (which make some platform mallocs sad).
32905 o Minor bugfixes (misc):
32906 - If exit bandwidth ever exceeds one third of total bandwidth, then
32907 use the correct formula to weight exit nodes when choosing paths.
32908 Based on patch from Mike Perry.
32909 - Choose perfectly fairly among routers when choosing by bandwidth and
32910 weighting by fraction of bandwidth provided by exits. Previously, we
32911 would choose with only approximate fairness, and correct ourselves
32912 if we ran off the end of the list.
32913 - If we require CookieAuthentication but we fail to write the
32914 cookie file, we would warn but not exit, and end up in a state
32915 where no controller could authenticate. Now we exit.
32916 - If we require CookieAuthentication, stop generating a new cookie
32917 every time we change any piece of our config.
32918 - Refuse to start with certain directory authority keys, and
32919 encourage people using them to stop.
32920 - Terminate multi-line control events properly. Original patch
32922 - Fix a minor memory leak when we fail to find enough suitable
32923 servers to choose a circuit.
32924 - Stop leaking part of the descriptor when we run into a particularly
32925 unparseable piece of it.
32928 Changes in version 0.2.0.6-alpha - 2007-08-26
32929 This sixth development snapshot features a new Vidalia version in the
32930 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
32931 the ControlPort in the default configuration, which addresses important
32934 In addition, this snapshot fixes major load balancing problems
32935 with path selection, which should speed things up a lot once many
32936 people have upgraded. The directory authorities also use a new
32937 mean-time-between-failure approach to tracking which servers are stable,
32938 rather than just looking at the most recent uptime.
32940 o New directory authorities:
32941 - Set up Tonga as the default bridge directory authority.
32944 - Directory authorities now track servers by weighted
32945 mean-times-between-failures. When we have 4 or more days of data,
32946 use measured MTBF rather than declared uptime to decide whether
32947 to call a router Stable. Implements proposal 108.
32949 o Major bugfixes (load balancing):
32950 - When choosing nodes for non-guard positions, weight guards
32951 proportionally less, since they already have enough load. Patch
32953 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
32954 will allow fast Tor servers to get more attention.
32955 - When we're upgrading from an old Tor version, forget our current
32956 guards and pick new ones according to the new weightings. These
32957 three load balancing patches could raise effective network capacity
32958 by a factor of four. Thanks to Mike Perry for measurements.
32960 o Major bugfixes (descriptor parsing):
32961 - Handle unexpected whitespace better in malformed descriptors. Bug
32962 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
32965 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
32966 GETINFO for Torstat to use until it can switch to using extrainfos.
32967 - Optionally (if built with -DEXPORTMALLINFO) export the output
32968 of mallinfo via http, as tor/mallinfo.txt. Only accessible
32972 - Do not intermix bridge routers with controller-added
32973 routers. (Bugfix on 0.2.0.x)
32974 - Do not fail with an assert when accept() returns an unexpected
32975 address family. Addresses but does not wholly fix bug 483. (Bugfix
32977 - Let directory authorities startup even when they can't generate
32978 a descriptor immediately, e.g. because they don't know their
32980 - Stop putting the authentication cookie in a file called "0"
32981 in your working directory if you don't specify anything for the
32982 new CookieAuthFile option. Reported by Matt Edman.
32983 - Make it possible to read the PROTOCOLINFO response in a way that
32984 conforms to our control-spec. Reported by Matt Edman.
32985 - Fix a minor memory leak when we fail to find enough suitable
32986 servers to choose a circuit. Bugfix on 0.1.2.x.
32987 - Stop leaking part of the descriptor when we run into a particularly
32988 unparseable piece of it. Bugfix on 0.1.2.x.
32989 - Unmap the extrainfo cache file on exit.
32992 Changes in version 0.2.0.5-alpha - 2007-08-19
32993 This fifth development snapshot fixes compilation on Windows again;
32994 fixes an obnoxious client-side bug that slowed things down and put
32995 extra load on the network; gets us closer to using the v3 directory
32996 voting scheme; makes it easier for Tor controllers to use cookie-based
32997 authentication; and fixes a variety of other bugs.
32999 o Removed features:
33000 - Version 1 directories are no longer generated in full. Instead,
33001 authorities generate and serve "stub" v1 directories that list
33002 no servers. This will stop Tor versions 0.1.0.x and earlier from
33003 working, but (for security reasons) nobody should be running those
33006 o Major bugfixes (compilation, 0.2.0.x):
33007 - Try to fix Win32 compilation again: improve checking for IPv6 types.
33008 - Try to fix MSVC compilation: build correctly on platforms that do
33009 not define s6_addr16 or s6_addr32.
33010 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
33013 o Major bugfixes (stream expiration):
33014 - Expire not-yet-successful application streams in all cases if
33015 they've been around longer than SocksTimeout. Right now there are
33016 some cases where the stream will live forever, demanding a new
33017 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
33018 reported by lodger.
33020 o Minor features (directory servers):
33021 - When somebody requests a list of statuses or servers, and we have
33022 none of those, return a 404 rather than an empty 200.
33024 o Minor features (directory voting):
33025 - Store v3 consensus status consensuses on disk, and reload them
33028 o Minor features (security):
33029 - Warn about unsafe ControlPort configurations.
33030 - Refuse to start with certain directory authority keys, and
33031 encourage people using them to stop.
33033 o Minor features (controller):
33034 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
33035 is valid before any authentication has been received. It tells
33036 a controller what kind of authentication is expected, and what
33037 protocol is spoken. Implements proposal 119.
33038 - New config option CookieAuthFile to choose a new location for the
33039 cookie authentication file, and config option
33040 CookieAuthFileGroupReadable to make it group-readable.
33042 o Minor features (unit testing):
33043 - Add command-line arguments to unit-test executable so that we can
33044 invoke any chosen test from the command line rather than having
33045 to run the whole test suite at once; and so that we can turn on
33046 logging for the unit tests.
33048 o Minor bugfixes (on 0.1.2.x):
33049 - If we require CookieAuthentication but we fail to write the
33050 cookie file, we would warn but not exit, and end up in a state
33051 where no controller could authenticate. Now we exit.
33052 - If we require CookieAuthentication, stop generating a new cookie
33053 every time we change any piece of our config.
33054 - When loading bandwidth history, do not believe any information in
33055 the future. Fixes bug 434.
33056 - When loading entry guard information, do not believe any information
33058 - When we have our clock set far in the future and generate an
33059 onion key, then re-set our clock to be correct, we should not stop
33060 the onion key from getting rotated.
33061 - Clean up torrc sample config file.
33062 - Do not automatically run configure from autogen.sh. This
33063 non-standard behavior tended to annoy people who have built other
33066 o Minor bugfixes (on 0.2.0.x):
33067 - Fix a bug with AutomapHostsOnResolve that would always cause
33068 the second request to fail. Bug reported by Kate. Bugfix on
33070 - Fix a bug in ADDRMAP controller replies that would sometimes
33071 try to print a NULL. Patch from tup.
33072 - Read v3 directory authority keys from the right location.
33073 - Numerous bugfixes to directory voting code.
33076 Changes in version 0.1.2.16 - 2007-08-01
33077 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
33078 remote attacker in certain situations to rewrite the user's torrc
33079 configuration file. This can completely compromise anonymity of users
33080 in most configurations, including those running the Vidalia bundles,
33081 TorK, etc. Or worse.
33083 o Major security fixes:
33084 - Close immediately after missing authentication on control port;
33085 do not allow multiple authentication attempts.
33088 Changes in version 0.2.0.4-alpha - 2007-08-01
33089 This fourth development snapshot fixes a critical security vulnerability
33090 for most users, specifically those running Vidalia, TorK, etc. Everybody
33091 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
33093 o Major security fixes:
33094 - Close immediately after missing authentication on control port;
33095 do not allow multiple authentication attempts.
33097 o Major bugfixes (compilation):
33098 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
33101 o Minor features (performance):
33102 - Be even more aggressive about releasing RAM from small
33103 empty buffers. Thanks to our free-list code, this shouldn't be too
33104 performance-intensive.
33105 - Disable sentinel-based debugging for buffer code: we squashed all
33106 the bugs that this was supposed to detect a long time ago, and
33107 now its only effect is to change our buffer sizes from nice
33108 powers of two (which platform mallocs tend to like) to values
33109 slightly over powers of two (which make some platform mallocs sad).
33110 - Log malloc statistics from mallinfo() on platforms where it
33114 Changes in version 0.2.0.3-alpha - 2007-07-29
33115 This third development snapshot introduces new experimental
33116 blocking-resistance features and a preliminary version of the v3
33117 directory voting design, and includes many other smaller features
33121 - The first pieces of our "bridge" design for blocking-resistance
33122 are implemented. People can run bridge directory authorities;
33123 people can run bridges; and people can configure their Tor clients
33124 with a set of bridges to use as the first hop into the Tor network.
33125 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
33127 - Create listener connections before we setuid to the configured
33128 User and Group. Now non-Windows users can choose port values
33129 under 1024, start Tor as root, and have Tor bind those ports
33130 before it changes to another UID. (Windows users could already
33132 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
33133 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
33134 on "vserver" accounts. (Patch from coderman.)
33135 - Be even more aggressive about separating local traffic from relayed
33136 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
33138 o Major features (experimental):
33139 - First cut of code for "v3 dir voting": directory authorities will
33140 vote on a common network status document rather than each publishing
33141 their own opinion. This code needs more testing and more corner-case
33142 handling before it's ready for use.
33145 - Directory authorities now call routers Fast if their bandwidth is
33146 at least 100KB/s, and consider their bandwidth adequate to be a
33147 Guard if it is at least 250KB/s, no matter the medians. This fix
33148 complements proposal 107. [Bugfix on 0.1.2.x]
33149 - Directory authorities now never mark more than 3 servers per IP as
33150 Valid and Running. (Implements proposal 109, by Kevin Bauer and
33152 - Minor change to organizationName and commonName generation
33153 procedures in TLS certificates during Tor handshakes, to invalidate
33154 some earlier censorware approaches. This is not a long-term
33155 solution, but applying it will give us a bit of time to look into
33156 the epidemiology of countermeasures as they spread.
33158 o Major bugfixes (directory):
33159 - Rewrite directory tokenization code to never run off the end of
33160 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
33162 o Minor features (controller):
33163 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
33164 match requests to applications. (Patch from Robert Hogan.)
33165 - Report address and port correctly on connections to DNSPort. (Patch
33166 from Robert Hogan.)
33167 - Add a RESOLVE command to launch hostname lookups. (Original patch
33168 from Robert Hogan.)
33169 - Add GETINFO status/enough-dir-info to let controllers tell whether
33170 Tor has downloaded sufficient directory information. (Patch
33172 - You can now use the ControlSocket option to tell Tor to listen for
33173 controller connections on Unix domain sockets on systems that
33174 support them. (Patch from Peter Palfrader.)
33175 - STREAM NEW events are generated for DNSPort requests and for
33176 tunneled directory connections. (Patch from Robert Hogan.)
33177 - New "GETINFO address-mappings/*" command to get address mappings
33178 with expiry information. "addr-mappings/*" is now deprecated.
33181 o Minor features (misc):
33182 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
33184 - The tor-gencert tool for v3 directory authorities now creates all
33185 files as readable to the file creator only, and write-protects
33186 the authority identity key.
33187 - When dumping memory usage, list bytes used in buffer memory
33189 - When running with dmalloc, dump more stats on hup and on exit.
33190 - Directory authorities now fail quickly and (relatively) harmlessly
33191 if they generate a network status document that is somehow
33194 o Traffic load balancing improvements:
33195 - If exit bandwidth ever exceeds one third of total bandwidth, then
33196 use the correct formula to weight exit nodes when choosing paths.
33197 (Based on patch from Mike Perry.)
33198 - Choose perfectly fairly among routers when choosing by bandwidth and
33199 weighting by fraction of bandwidth provided by exits. Previously, we
33200 would choose with only approximate fairness, and correct ourselves
33201 if we ran off the end of the list. [Bugfix on 0.1.2.x]
33203 o Performance improvements:
33204 - Be more aggressive with freeing buffer RAM or putting it on the
33206 - Use Critical Sections rather than Mutexes for synchronizing threads
33207 on win32; Mutexes are heavier-weight, and designed for synchronizing
33210 o Deprecated and removed features:
33211 - RedirectExits is now deprecated.
33212 - Stop allowing address masks that do not correspond to bit prefixes.
33213 We have warned about these for a really long time; now it's time
33214 to reject them. (Patch from croup.)
33216 o Minor bugfixes (directory):
33217 - Fix another crash bug related to extra-info caching. (Bug found by
33218 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
33219 - Directories no longer return a "304 not modified" when they don't
33220 have the networkstatus the client asked for. Also fix a memory
33221 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
33222 - We had accidentally labelled 0.1.2.x directory servers as not
33223 suitable for begin_dir requests, and had labelled no directory
33224 servers as suitable for uploading extra-info documents. [Bugfix
33227 o Minor bugfixes (dns):
33228 - Fix a crash when DNSPort is set more than once. (Patch from Robert
33229 Hogan.) [Bugfix on 0.2.0.2-alpha]
33230 - Add DNSPort connections to the global connection list, so that we
33231 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
33233 - Fix a dangling reference that could lead to a crash when DNSPort is
33234 changed or closed (Patch from Robert Hogan.) [Bugfix on
33237 o Minor bugfixes (controller):
33238 - Provide DNS expiry times in GMT, not in local time. For backward
33239 compatibility, ADDRMAP events only provide GMT expiry in an extended
33240 field. "GETINFO address-mappings" always does the right thing.
33241 - Use CRLF line endings properly in NS events.
33242 - Terminate multi-line control events properly. (Original patch
33243 from tup.) [Bugfix on 0.1.2.x-alpha]
33244 - Do not include spaces in SOURCE_ADDR fields in STREAM
33245 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
33248 Changes in version 0.1.2.15 - 2007-07-17
33249 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
33250 problems, fixes compilation on BSD, and fixes a variety of other
33251 bugs. Everybody should upgrade.
33253 o Major bugfixes (compilation):
33254 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
33256 o Major bugfixes (crashes):
33257 - Try even harder not to dereference the first character after
33258 an mmap(). Reported by lodger.
33259 - Fix a crash bug in directory authorities when we re-number the
33260 routerlist while inserting a new router.
33261 - When the cached-routers file is an even multiple of the page size,
33262 don't run off the end and crash. (Fixes bug 455; based on idea
33264 - Fix eventdns.c behavior on Solaris: It is critical to include
33265 orconfig.h _before_ sys/types.h, so that we can get the expected
33266 definition of _FILE_OFFSET_BITS.
33268 o Major bugfixes (security):
33269 - Fix a possible buffer overrun when using BSD natd support. Bug
33271 - When sending destroy cells from a circuit's origin, don't include
33272 the reason for tearing down the circuit. The spec says we didn't,
33273 and now we actually don't. Reported by lodger.
33274 - Keep streamids from different exits on a circuit separate. This
33275 bug may have allowed other routers on a given circuit to inject
33276 cells into streams. Reported by lodger; fixes bug 446.
33277 - If there's a never-before-connected-to guard node in our list,
33278 never choose any guards past it. This way we don't expand our
33279 guard list unless we need to.
33281 o Minor bugfixes (guard nodes):
33282 - Weight guard selection by bandwidth, so that low-bandwidth nodes
33283 don't get overused as guards.
33285 o Minor bugfixes (directory):
33286 - Correctly count the number of authorities that recommend each
33287 version. Previously, we were under-counting by 1.
33288 - Fix a potential crash bug when we load many server descriptors at
33289 once and some of them make others of them obsolete. Fixes bug 458.
33291 o Minor bugfixes (hidden services):
33292 - Stop tearing down the whole circuit when the user asks for a
33293 connection to a port that the hidden service didn't configure.
33296 o Minor bugfixes (misc):
33297 - On Windows, we were preventing other processes from reading
33298 cached-routers while Tor was running. Reported by janbar.
33299 - Fix a possible (but very unlikely) bug in picking routers by
33300 bandwidth. Add a log message to confirm that it is in fact
33301 unlikely. Patch from lodger.
33302 - Backport a couple of memory leak fixes.
33303 - Backport miscellaneous cosmetic bugfixes.
33306 Changes in version 0.2.0.2-alpha - 2007-06-02
33307 o Major bugfixes on 0.2.0.1-alpha:
33308 - Fix an assertion failure related to servers without extra-info digests.
33309 Resolves bugs 441 and 442.
33311 o Minor features (directory):
33312 - Support "If-Modified-Since" when answering HTTP requests for
33313 directories, running-routers documents, and network-status documents.
33314 (There's no need to support it for router descriptors, since those
33315 are downloaded by descriptor digest.)
33317 o Minor build issues:
33318 - Clear up some MIPSPro compiler warnings.
33319 - When building from a tarball on a machine that happens to have SVK
33320 installed, report the micro-revision as whatever version existed
33321 in the tarball, not as "x".
33324 Changes in version 0.2.0.1-alpha - 2007-06-01
33325 This early development snapshot provides new features for people running
33326 Tor as both a client and a server (check out the new RelayBandwidth
33327 config options); lets Tor run as a DNS proxy; and generally moves us
33328 forward on a lot of fronts.
33330 o Major features, server usability:
33331 - New config options RelayBandwidthRate and RelayBandwidthBurst:
33332 a separate set of token buckets for relayed traffic. Right now
33333 relayed traffic is defined as answers to directory requests, and
33334 OR connections that don't have any local circuits on them.
33336 o Major features, client usability:
33337 - A client-side DNS proxy feature to replace the need for
33338 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
33339 for DNS requests on port 9999, use the Tor network to resolve them
33340 anonymously, and send the reply back like a regular DNS server.
33341 The code still only implements a subset of DNS.
33342 - Make PreferTunneledDirConns and TunnelDirConns work even when
33343 we have no cached directory info. This means Tor clients can now
33344 do all of their connections protected by TLS.
33346 o Major features, performance and efficiency:
33347 - Directory authorities accept and serve "extra info" documents for
33348 routers. These documents contain fields from router descriptors
33349 that aren't usually needed, and that use a lot of excess
33350 bandwidth. Once these fields are removed from router descriptors,
33351 the bandwidth savings should be about 60%. [Partially implements
33353 - Servers upload extra-info documents to any authority that accepts
33354 them. Authorities (and caches that have been configured to download
33355 extra-info documents) download them as needed. [Partially implements
33357 - Change the way that Tor buffers data that it is waiting to write.
33358 Instead of queueing data cells in an enormous ring buffer for each
33359 client->OR or OR->OR connection, we now queue cells on a separate
33360 queue for each circuit. This lets us use less slack memory, and
33361 will eventually let us be smarter about prioritizing different kinds
33363 - Use memory pools to allocate cells with better speed and memory
33364 efficiency, especially on platforms where malloc() is inefficient.
33365 - Stop reading on edge connections when their corresponding circuit
33366 buffers are full; start again as the circuits empty out.
33368 o Major features, other:
33369 - Add an HSAuthorityRecordStats option that hidden service authorities
33370 can use to track statistics of overall hidden service usage without
33371 logging information that would be very useful to an attacker.
33372 - Start work implementing multi-level keys for directory authorities:
33373 Add a standalone tool to generate key certificates. (Proposal 103.)
33376 - Directory authorities now call routers Stable if they have an
33377 uptime of at least 30 days, even if that's not the median uptime
33378 in the network. Implements proposal 107, suggested by Kevin Bauer
33381 o Minor fixes (resource management):
33382 - Count the number of open sockets separately from the number
33383 of active connection_t objects. This will let us avoid underusing
33384 our allocated connection limit.
33385 - We no longer use socket pairs to link an edge connection to an
33386 anonymous directory connection or a DirPort test connection.
33387 Instead, we track the link internally and transfer the data
33388 in-process. This saves two sockets per "linked" connection (at the
33389 client and at the server), and avoids the nasty Windows socketpair()
33391 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
33392 for every single inactive connection_t. Free items from the
33393 4k/16k-buffer free lists when they haven't been used for a while.
33395 o Minor features (build):
33396 - Make autoconf search for libevent, openssl, and zlib consistently.
33397 - Update deprecated macros in configure.in.
33398 - When warning about missing headers, tell the user to let us
33399 know if the compile succeeds anyway, so we can downgrade the
33401 - Include the current subversion revision as part of the version
33402 string: either fetch it directly if we're in an SVN checkout, do
33403 some magic to guess it if we're in an SVK checkout, or use
33404 the last-detected version if we're building from a .tar.gz.
33405 Use this version consistently in log messages.
33407 o Minor features (logging):
33408 - Always prepend "Bug: " to any log message about a bug.
33409 - Put a platform string (e.g. "Linux i686") in the startup log
33410 message, so when people paste just their logs, we know if it's
33411 OpenBSD or Windows or what.
33412 - When logging memory usage, break down memory used in buffers by
33415 o Minor features (directory system):
33416 - New config option V2AuthoritativeDirectory that all directory
33417 authorities should set. This will let future authorities choose
33418 not to serve V2 directory information.
33419 - Directory authorities allow multiple router descriptors and/or extra
33420 info documents to be uploaded in a single go. This will make
33421 implementing proposal 104 simpler.
33423 o Minor features (controller):
33424 - Add a new config option __DisablePredictedCircuits designed for
33425 use by the controller, when we don't want Tor to build any circuits
33427 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
33428 so we can exit from the middle of the circuit.
33429 - Implement "getinfo status/circuit-established".
33430 - Implement "getinfo status/version/..." so a controller can tell
33431 whether the current version is recommended, and whether any versions
33432 are good, and how many authorities agree. (Patch from shibz.)
33434 o Minor features (hidden services):
33435 - Allow multiple HiddenServicePort directives with the same virtual
33436 port; when they occur, the user is sent round-robin to one
33437 of the target ports chosen at random. Partially fixes bug 393 by
33438 adding limited ad-hoc round-robining.
33440 o Minor features (other):
33442 - Add a new AutomapHostsOnResolve option: when it is enabled, any
33443 resolve request for hosts matching a given pattern causes Tor to
33444 generate an internal virtual address mapping for that host. This
33445 allows DNSPort to work sensibly with hidden service users. By
33446 default, .exit and .onion addresses are remapped; the list of
33447 patterns can be reconfigured with AutomapHostsSuffixes.
33448 - Add an "-F" option to tor-resolve to force a resolve for a .onion
33449 address. Thanks to the AutomapHostsOnResolve option, this is no
33450 longer a completely silly thing to do.
33451 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
33452 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
33453 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
33454 minus 1 byte: the actual maximum declared bandwidth.
33456 o Removed features:
33457 - Removed support for the old binary "version 0" controller protocol.
33458 This has been deprecated since 0.1.1, and warnings have been issued
33459 since 0.1.2. When we encounter a v0 control message, we now send
33460 back an error and close the connection.
33461 - Remove the old "dns worker" server DNS code: it hasn't been default
33462 since 0.1.2.2-alpha, and all the servers seem to be using the new
33465 o Minor bugfixes (portability):
33466 - Even though Windows is equally happy with / and \ as path separators,
33467 try to use \ consistently on Windows and / consistently on Unix: it
33468 makes the log messages nicer.
33469 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
33470 - Read resolv.conf files correctly on platforms where read() returns
33471 partial results on small file reads.
33473 o Minor bugfixes (directory):
33474 - Correctly enforce that elements of directory objects do not appear
33475 more often than they are allowed to appear.
33476 - When we are reporting the DirServer line we just parsed, we were
33477 logging the second stanza of the key fingerprint, not the first.
33479 o Minor bugfixes (logging):
33480 - When we hit an EOF on a log (probably because we're shutting down),
33481 don't try to remove the log from the list: just mark it as
33482 unusable. (Bulletproofs against bug 222.)
33484 o Minor bugfixes (other):
33485 - In the exitlist script, only consider the most recently published
33486 server descriptor for each server. Also, when the user requests
33487 a list of servers that _reject_ connections to a given address,
33488 explicitly exclude the IPs that also have servers that accept
33489 connections to that address. (Resolves bug 405.)
33490 - Stop allowing hibernating servers to be "stable" or "fast".
33491 - On Windows, we were preventing other processes from reading
33492 cached-routers while Tor was running. (Reported by janbar)
33493 - Make the NodeFamilies config option work. (Reported by
33494 lodger -- it has never actually worked, even though we added it
33496 - Check return values from pthread_mutex functions.
33497 - Don't save non-general-purpose router descriptors to the disk cache,
33498 because we have no way of remembering what their purpose was when
33500 - Add even more asserts to hunt down bug 417.
33501 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
33502 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
33503 Add a log message to confirm that it is in fact unlikely.
33505 o Minor bugfixes (controller):
33506 - Make 'getinfo fingerprint' return a 551 error if we're not a
33507 server, so we match what the control spec claims we do. Reported
33509 - Fix a typo in an error message when extendcircuit fails that
33510 caused us to not follow the \r\n-based delimiter protocol. Reported
33513 o Code simplifications and refactoring:
33514 - Stop passing around circuit_t and crypt_path_t pointers that are
33515 implicit in other procedure arguments.
33516 - Drop the old code to choke directory connections when the
33517 corresponding OR connections got full: thanks to the cell queue
33518 feature, OR conns don't get full any more.
33519 - Make dns_resolve() handle attaching connections to circuits
33520 properly, so the caller doesn't have to.
33521 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
33522 - Keep the connection array as a dynamic smartlist_t, rather than as
33523 a fixed-sized array. This is important, as the number of connections
33524 is becoming increasingly decoupled from the number of sockets.
33527 Changes in version 0.1.2.14 - 2007-05-25
33528 Tor 0.1.2.14 changes the addresses of two directory authorities (this
33529 change especially affects those who serve or use hidden services),
33530 and fixes several other crash- and security-related bugs.
33532 o Directory authority changes:
33533 - Two directory authorities (moria1 and moria2) just moved to new
33534 IP addresses. This change will particularly affect those who serve
33535 or use hidden services.
33537 o Major bugfixes (crashes):
33538 - If a directory server runs out of space in the connection table
33539 as it's processing a begin_dir request, it will free the exit stream
33540 but leave it attached to the circuit, leading to unpredictable
33541 behavior. (Reported by seeess, fixes bug 425.)
33542 - Fix a bug in dirserv_remove_invalid() that would cause authorities
33543 to corrupt memory under some really unlikely scenarios.
33544 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
33545 - Avoid segfaults when reading from mmaped descriptor file. (Reported
33548 o Major bugfixes (security):
33549 - When choosing an entry guard for a circuit, avoid using guards
33550 that are in the same family as the chosen exit -- not just guards
33551 that are exactly the chosen exit. (Reported by lodger.)
33553 o Major bugfixes (resource management):
33554 - If a directory authority is down, skip it when deciding where to get
33555 networkstatus objects or descriptors. Otherwise we keep asking
33556 every 10 seconds forever. Fixes bug 384.
33557 - Count it as a failure if we fetch a valid network-status but we
33558 don't want to keep it. Otherwise we'll keep fetching it and keep
33559 not wanting to keep it. Fixes part of bug 422.
33560 - If all of our dirservers have given us bad or no networkstatuses
33561 lately, then stop hammering them once per minute even when we
33562 think they're failed. Fixes another part of bug 422.
33565 - Actually set the purpose correctly for descriptors inserted with
33566 purpose=controller.
33567 - When we have k non-v2 authorities in our DirServer config,
33568 we ignored the last k authorities in the list when updating our
33570 - Correctly back-off from requesting router descriptors that we are
33571 having a hard time downloading.
33572 - Read resolv.conf files correctly on platforms where read() returns
33573 partial results on small file reads.
33574 - Don't rebuild the entire router store every time we get 32K of
33575 routers: rebuild it when the journal gets very large, or when
33576 the gaps in the store get very large.
33579 - When routers publish SVN revisions in their router descriptors,
33580 authorities now include those versions correctly in networkstatus
33582 - Warn when using a version of libevent before 1.3b to run a server on
33583 OSX or BSD: these versions interact badly with userspace threads.
33586 Changes in version 0.1.2.13 - 2007-04-24
33587 This release features some major anonymity fixes, such as safer path
33588 selection; better client performance; faster bootstrapping, better
33589 address detection, and better DNS support for servers; write limiting as
33590 well as read limiting to make servers easier to run; and a huge pile of
33591 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
33593 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
33594 of the Freenode IRC network, remembering his patience and vision for
33595 free speech on the Internet.
33598 - Fix a memory leak when we ask for "all" networkstatuses and we
33599 get one we don't recognize.
33600 - Add more asserts to hunt down bug 417.
33601 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
33604 Changes in version 0.1.2.12-rc - 2007-03-16
33606 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
33607 directory information requested inside Tor connections (i.e. via
33608 begin_dir cells). It only triggered when the same connection was
33609 serving other data at the same time. Reported by seeess.
33612 - When creating a circuit via the controller, send a 'launched'
33613 event when we're done, so we follow the spec better.
33616 Changes in version 0.1.2.11-rc - 2007-03-15
33617 o Minor bugfixes (controller), reported by daejees:
33618 - Correct the control spec to match how the code actually responds
33619 to 'getinfo addr-mappings/*'.
33620 - The control spec described a GUARDS event, but the code
33621 implemented a GUARD event. Standardize on GUARD, but let people
33622 ask for GUARDS too.
33625 Changes in version 0.1.2.10-rc - 2007-03-07
33626 o Major bugfixes (Windows):
33627 - Do not load the NT services library functions (which may not exist)
33628 just to detect if we're a service trying to shut down. Now we run
33629 on Win98 and friends again.
33631 o Minor bugfixes (other):
33632 - Clarify a couple of log messages.
33633 - Fix a misleading socks5 error number.
33636 Changes in version 0.1.2.9-rc - 2007-03-02
33637 o Major bugfixes (Windows):
33638 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
33639 of the usual GCC "%llu". This prevents a bug when saving 64-bit
33640 int configuration values: the high-order 32 bits would get
33641 truncated. In particular, we were being bitten by the default
33642 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
33643 and maybe also bug 397.)
33645 o Minor bugfixes (performance):
33646 - Use OpenSSL's AES implementation on platforms where it's faster.
33647 This could save us as much as 10% CPU usage.
33649 o Minor bugfixes (server):
33650 - Do not rotate onion key immediately after setting it for the first
33653 o Minor bugfixes (directory authorities):
33654 - Stop calling servers that have been hibernating for a long time
33655 "stable". Also, stop letting hibernating or obsolete servers affect
33656 uptime and bandwidth cutoffs.
33657 - Stop listing hibernating servers in the v1 directory.
33659 o Minor bugfixes (hidden services):
33660 - Upload hidden service descriptors slightly less often, to reduce
33661 load on authorities.
33663 o Minor bugfixes (other):
33664 - Fix an assert that could trigger if a controller quickly set then
33665 cleared EntryNodes. Bug found by Udo van den Heuvel.
33666 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
33668 - Fix a potential race condition in the rpm installer. Found by
33670 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
33671 of 2 as indicating that the server is completely bad; it sometimes
33672 means that the server is just bad for the request in question. (may fix
33673 the last of bug 326.)
33674 - Disable encrypted directory connections when we don't have a server
33675 descriptor for the destination. We'll get this working again in
33679 Changes in version 0.1.2.8-beta - 2007-02-26
33680 o Major bugfixes (crashes):
33681 - Stop crashing when the controller asks us to resetconf more than
33682 one config option at once. (Vidalia 0.0.11 does this.)
33683 - Fix a crash that happened on Win98 when we're given command-line
33684 arguments: don't try to load NT service functions from advapi32.dll
33685 except when we need them. (Bug introduced in 0.1.2.7-alpha;
33687 - Fix a longstanding obscure crash bug that could occur when
33688 we run out of DNS worker processes. (Resolves bug 390.)
33690 o Major bugfixes (hidden services):
33691 - Correctly detect whether hidden service descriptor downloads are
33692 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
33694 o Major bugfixes (accounting):
33695 - When we start during an accounting interval before it's time to wake
33696 up, remember to wake up at the correct time. (May fix bug 342.)
33698 o Minor bugfixes (controller):
33699 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
33700 clear the corresponding on_circuit variable, and remember later
33701 that we don't need to send a redundant CLOSED event. Resolves part
33703 - Report events where a resolve succeeded or where we got a socks
33704 protocol error correctly, rather than calling both of them
33706 - Change reported stream target addresses to IP consistently when
33707 we finally get the IP from an exit node.
33708 - Send log messages to the controller even if they happen to be very
33711 o Minor bugfixes (other):
33712 - Display correct results when reporting which versions are
33713 recommended, and how recommended they are. (Resolves bug 383.)
33714 - Improve our estimates for directory bandwidth to be less random:
33715 guess that an unrecognized directory will have the average bandwidth
33716 from all known directories, not that it will have the average
33717 bandwidth from those directories earlier than it on the list.
33718 - If we start a server with ClientOnly 1, then set ClientOnly to 0
33719 and hup, stop triggering an assert based on an empty onion_key.
33720 - On platforms with no working mmap() equivalent, don't warn the
33721 user when cached-routers doesn't exist.
33722 - Warn the user when mmap() [or its equivalent] fails for some reason
33723 other than file-not-found.
33724 - Don't warn the user when cached-routers.new doesn't exist: that's
33725 perfectly fine when starting up for the first time.
33726 - When EntryNodes are configured, rebuild the guard list to contain,
33727 in order: the EntryNodes that were guards before; the rest of the
33728 EntryNodes; the nodes that were guards before.
33729 - Mask out all signals in sub-threads; only the libevent signal
33730 handler should be processing them. This should prevent some crashes
33731 on some machines using pthreads. (Patch from coderman.)
33732 - Fix switched arguments on memset in the implementation of
33733 tor_munmap() for systems with no mmap() call.
33734 - When Tor receives a router descriptor that it asked for, but
33735 no longer wants (because it has received fresh networkstatuses
33736 in the meantime), do not warn the user. Cache the descriptor if
33737 we're a cache; drop it if we aren't.
33738 - Make earlier entry guards _really_ get retried when the network
33740 - On a malformed DNS reply, always give an error to the corresponding
33742 - Build with recent libevents on platforms that do not define the
33743 nonstandard types "u_int8_t" and friends.
33745 o Minor features (controller):
33746 - Warn the user when an application uses the obsolete binary v0
33747 control protocol. We're planning to remove support for it during
33748 the next development series, so it's good to give people some
33750 - Add STREAM_BW events to report per-entry-stream bandwidth
33751 use. (Patch from Robert Hogan.)
33752 - Rate-limit SIGNEWNYM signals in response to controllers that
33753 impolitely generate them for every single stream. (Patch from
33754 mwenge; closes bug 394.)
33755 - Make REMAP stream events have a SOURCE (cache or exit), and
33756 make them generated in every case where we get a successful
33757 connected or resolved cell.
33759 o Minor bugfixes (performance):
33760 - Call router_have_min_dir_info half as often. (This is showing up in
33761 some profiles, but not others.)
33762 - When using GCC, make log_debug never get called at all, and its
33763 arguments never get evaluated, when no debug logs are configured.
33764 (This is showing up in some profiles, but not others.)
33767 - Remove some never-implemented options. Mark PathlenCoinWeight as
33769 - Implement proposal 106: Stop requiring clients to have well-formed
33770 certificates; stop checking nicknames in certificates. (Clients
33771 have certificates so that they can look like Tor servers, but in
33772 the future we might want to allow them to look like regular TLS
33773 clients instead. Nicknames in certificates serve no purpose other
33774 than making our protocol easier to recognize on the wire.)
33775 - Revise messages on handshake failure again to be even more clear about
33776 which are incoming connections and which are outgoing.
33777 - Discard any v1 directory info that's over 1 month old (for
33778 directories) or over 1 week old (for running-routers lists).
33779 - Do not warn when individual nodes in the configuration's EntryNodes,
33780 ExitNodes, etc are down: warn only when all possible nodes
33781 are down. (Fixes bug 348.)
33782 - Always remove expired routers and networkstatus docs before checking
33783 whether we have enough information to build circuits. (Fixes
33785 - Put a lower-bound on MaxAdvertisedBandwidth.
33788 Changes in version 0.1.2.7-alpha - 2007-02-06
33789 o Major bugfixes (rate limiting):
33790 - Servers decline directory requests much more aggressively when
33791 they're low on bandwidth. Otherwise they end up queueing more and
33792 more directory responses, which can't be good for latency.
33793 - But never refuse directory requests from local addresses.
33794 - Fix a memory leak when sending a 503 response for a networkstatus
33796 - Be willing to read or write on local connections (e.g. controller
33797 connections) even when the global rate limiting buckets are empty.
33798 - If our system clock jumps back in time, don't publish a negative
33799 uptime in the descriptor. Also, don't let the global rate limiting
33800 buckets go absurdly negative.
33801 - Flush local controller connection buffers periodically as we're
33802 writing to them, so we avoid queueing 4+ megabytes of data before
33805 o Major bugfixes (NT services):
33806 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
33807 command-line flag so that admins can override the default by saying
33808 "tor --service install --user "SomeUser"". This will not affect
33809 existing installed services. Also, warn the user that the service
33810 will look for its configuration file in the service user's
33811 %appdata% directory. (We can't do the 'hardwire the user's appdata
33812 directory' trick any more, since we may not have read access to that
33815 o Major bugfixes (other):
33816 - Previously, we would cache up to 16 old networkstatus documents
33817 indefinitely, if they came from nontrusted authorities. Now we
33818 discard them if they are more than 10 days old.
33819 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
33821 - Detect and reject malformed DNS responses containing circular
33823 - If exits are rare enough that we're not marking exits as guards,
33824 ignore exit bandwidth when we're deciding the required bandwidth
33826 - When we're handling a directory connection tunneled over Tor,
33827 don't fill up internal memory buffers with all the data we want
33828 to tunnel; instead, only add it if the OR connection that will
33829 eventually receive it has some room for it. (This can lead to
33830 slowdowns in tunneled dir connections; a better solution will have
33831 to wait for 0.2.0.)
33833 o Minor bugfixes (dns):
33834 - Add some defensive programming to eventdns.c in an attempt to catch
33835 possible memory-stomping bugs.
33836 - Detect and reject DNS replies containing IPv4 or IPv6 records with
33837 an incorrect number of bytes. (Previously, we would ignore the
33839 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
33840 in the correct order, and doesn't crash.
33841 - Free memory held in recently-completed DNS lookup attempts on exit.
33842 This was not a memory leak, but may have been hiding memory leaks.
33843 - Handle TTL values correctly on reverse DNS lookups.
33844 - Treat failure to parse resolv.conf as an error.
33846 o Minor bugfixes (other):
33847 - Fix crash with "tor --list-fingerprint" (reported by seeess).
33848 - When computing clock skew from directory HTTP headers, consider what
33849 time it was when we finished asking for the directory, not what
33851 - Expire socks connections if they spend too long waiting for the
33852 handshake to finish. Previously we would let them sit around for
33853 days, if the connecting application didn't close them either.
33854 - And if the socks handshake hasn't started, don't send a
33855 "DNS resolve socks failed" handshake reply; just close it.
33856 - Stop using C functions that OpenBSD's linker doesn't like.
33857 - Don't launch requests for descriptors unless we have networkstatuses
33858 from at least half of the authorities. This delays the first
33859 download slightly under pathological circumstances, but can prevent
33860 us from downloading a bunch of descriptors we don't need.
33861 - Do not log IPs with TLS failures for incoming TLS
33862 connections. (Fixes bug 382.)
33863 - If the user asks to use invalid exit nodes, be willing to use
33865 - Stop using the reserved ac_cv namespace in our configure script.
33866 - Call stat() slightly less often; use fstat() when possible.
33867 - Refactor the way we handle pending circuits when an OR connection
33868 completes or fails, in an attempt to fix a rare crash bug.
33869 - Only rewrite a conn's address based on X-Forwarded-For: headers
33870 if it's a parseable public IP address; and stop adding extra quotes
33871 to the resulting address.
33874 - Weight directory requests by advertised bandwidth. Now we can
33875 let servers enable write limiting but still allow most clients to
33876 succeed at their directory requests. (We still ignore weights when
33877 choosing a directory authority; I hope this is a feature.)
33880 - Create a new file ReleaseNotes which was the old ChangeLog. The
33881 new ChangeLog file now includes the summaries for all development
33883 - Check for addresses with invalid characters at the exit as well
33884 as at the client, and warn less verbosely when they fail. You can
33885 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
33886 - Adapt a patch from goodell to let the contrib/exitlist script
33887 take arguments rather than require direct editing.
33888 - Inform the server operator when we decide not to advertise a
33889 DirPort due to AccountingMax enabled or a low BandwidthRate. It
33890 was confusing Zax, so now we're hopefully more helpful.
33891 - Bring us one step closer to being able to establish an encrypted
33892 directory tunnel without knowing a descriptor first. Still not
33893 ready yet. As part of the change, now assume we can use a
33894 create_fast cell if we don't know anything about a router.
33895 - Allow exit nodes to use nameservers running on ports other than 53.
33896 - Servers now cache reverse DNS replies.
33897 - Add an --ignore-missing-torrc command-line option so that we can
33898 get the "use sensible defaults if the configuration file doesn't
33899 exist" behavior even when specifying a torrc location on the command
33902 o Minor features (controller):
33903 - Track reasons for OR connection failure; make these reasons
33904 available via the controller interface. (Patch from Mike Perry.)
33905 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
33906 can learn when clients are sending malformed hostnames to Tor.
33907 - Clean up documentation for controller status events.
33908 - Add a REMAP status to stream events to note that a stream's
33909 address has changed because of a cached address or a MapAddress
33913 Changes in version 0.1.2.6-alpha - 2007-01-09
33915 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
33916 connection handles more than 4 gigs in either direction, we crash.
33917 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
33918 advertised exit node, somebody might try to exit from us when
33919 we're bootstrapping and before we've built our descriptor yet.
33920 Refuse the connection rather than crashing.
33923 - Warn if we (as a server) find that we've resolved an address that we
33924 weren't planning to resolve.
33925 - Warn that using select() on any libevent version before 1.1 will be
33926 unnecessarily slow (even for select()).
33927 - Flush ERR-level controller status events just like we currently
33928 flush ERR-level log events, so that a Tor shutdown doesn't prevent
33929 the controller from learning about current events.
33931 o Minor features (more controller status events):
33932 - Implement EXTERNAL_ADDRESS server status event so controllers can
33933 learn when our address changes.
33934 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
33935 can learn when directories reject our descriptor.
33936 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
33937 can learn when a client application is speaking a non-socks protocol
33939 - Implement DANGEROUS_SOCKS client status event so controllers
33940 can learn when a client application is leaking DNS addresses.
33941 - Implement BUG general status event so controllers can learn when
33942 Tor is unhappy about its internal invariants.
33943 - Implement CLOCK_SKEW general status event so controllers can learn
33944 when Tor thinks the system clock is set incorrectly.
33945 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
33946 server status events so controllers can learn when their descriptors
33947 are accepted by a directory.
33948 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
33949 server status events so controllers can learn about Tor's progress in
33950 deciding whether it's reachable from the outside.
33951 - Implement BAD_LIBEVENT general status event so controllers can learn
33952 when we have a version/method combination in libevent that needs to
33954 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
33955 and DNS_USELESS server status events so controllers can learn
33956 about changes to DNS server status.
33958 o Minor features (directory):
33959 - Authorities no longer recommend exits as guards if this would shift
33960 too much load to the exit nodes.
33963 Changes in version 0.1.2.5-alpha - 2007-01-06
33965 - Enable write limiting as well as read limiting. Now we sacrifice
33966 capacity if we're pushing out lots of directory traffic, rather
33967 than overrunning the user's intended bandwidth limits.
33968 - Include TLS overhead when counting bandwidth usage; previously, we
33969 would count only the bytes sent over TLS, but not the bytes used
33971 - Support running the Tor service with a torrc not in the same
33972 directory as tor.exe and default to using the torrc located in
33973 the %appdata%\Tor\ of the user who installed the service. Patch
33975 - Servers now check for the case when common DNS requests are going to
33976 wildcarded addresses (i.e. all getting the same answer), and change
33977 their exit policy to reject *:* if it's happening.
33978 - Implement BEGIN_DIR cells, so we can connect to the directory
33979 server via TLS to do encrypted directory requests rather than
33980 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
33981 config options if you like.
33983 o Minor features (config and docs):
33984 - Start using the state file to store bandwidth accounting data:
33985 the bw_accounting file is now obsolete. We'll keep generating it
33986 for a while for people who are still using 0.1.2.4-alpha.
33987 - Try to batch changes to the state file so that we do as few
33988 disk writes as possible while still storing important things in
33990 - The state file and the bw_accounting file get saved less often when
33991 the AvoidDiskWrites config option is set.
33992 - Make PIDFile work on Windows (untested).
33993 - Add internal descriptions for a bunch of configuration options:
33994 accessible via controller interface and in comments in saved
33996 - Reject *:563 (NNTPS) in the default exit policy. We already reject
33997 NNTP by default, so this seems like a sensible addition.
33998 - Clients now reject hostnames with invalid characters. This should
33999 avoid some inadvertent info leaks. Add an option
34000 AllowNonRFC953Hostnames to disable this behavior, in case somebody
34001 is running a private network with hosts called @, !, and #.
34002 - Add a maintainer script to tell us which options are missing
34003 documentation: "make check-docs".
34004 - Add a new address-spec.txt document to describe our special-case
34005 addresses: .exit, .onion, and .noconnnect.
34007 o Minor features (DNS):
34008 - Ongoing work on eventdns infrastructure: now it has dns server
34009 and ipv6 support. One day Tor will make use of it.
34010 - Add client-side caching for reverse DNS lookups.
34011 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
34012 - When we change nameservers or IP addresses, reset and re-launch
34013 our tests for DNS hijacking.
34015 o Minor features (directory):
34016 - Authorities now specify server versions in networkstatus. This adds
34017 about 2% to the size of compressed networkstatus docs, and allows
34018 clients to tell which servers support BEGIN_DIR and which don't.
34019 The implementation is forward-compatible with a proposed future
34020 protocol version scheme not tied to Tor versions.
34021 - DirServer configuration lines now have an orport= option so
34022 clients can open encrypted tunnels to the authorities without
34023 having downloaded their descriptors yet. Enabled for moria1,
34024 moria2, tor26, and lefkada now in the default configuration.
34025 - Directory servers are more willing to send a 503 "busy" if they
34026 are near their write limit, especially for v1 directory requests.
34027 Now they can use their limited bandwidth for actual Tor traffic.
34028 - Clients track responses with status 503 from dirservers. After a
34029 dirserver has given us a 503, we try not to use it until an hour has
34030 gone by, or until we have no dirservers that haven't given us a 503.
34031 - When we get a 503 from a directory, and we're not a server, we don't
34032 count the failure against the total number of failures allowed
34033 for the thing we're trying to download.
34034 - Report X-Your-Address-Is correctly from tunneled directory
34035 connections; don't report X-Your-Address-Is when it's an internal
34036 address; and never believe reported remote addresses when they're
34038 - Protect against an unlikely DoS attack on directory servers.
34039 - Add a BadDirectory flag to network status docs so that authorities
34040 can (eventually) tell clients about caches they believe to be
34043 o Minor features (controller):
34044 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
34045 - Reimplement GETINFO so that info/names stays in sync with the
34047 - Implement "GETINFO fingerprint".
34048 - Implement "SETEVENTS GUARD" so controllers can get updates on
34049 entry guard status as it changes.
34051 o Minor features (clean up obsolete pieces):
34052 - Remove some options that have been deprecated since at least
34053 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
34054 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
34055 to set log options.
34056 - We no longer look for identity and onion keys in "identity.key" and
34057 "onion.key" -- these were replaced by secret_id_key and
34058 secret_onion_key in 0.0.8pre1.
34059 - We no longer require unrecognized directory entries to be
34062 o Major bugfixes (security):
34063 - Stop sending the HttpProxyAuthenticator string to directory
34064 servers when directory connections are tunnelled through Tor.
34065 - Clients no longer store bandwidth history in the state file.
34066 - Do not log introduction points for hidden services if SafeLogging
34068 - When generating bandwidth history, round down to the nearest
34069 1k. When storing accounting data, round up to the nearest 1k.
34070 - When we're running as a server, remember when we last rotated onion
34071 keys, so that we will rotate keys once they're a week old even if
34072 we never stay up for a week ourselves.
34074 o Major bugfixes (other):
34075 - Fix a longstanding bug in eventdns that prevented the count of
34076 timed-out resolves from ever being reset. This bug caused us to
34077 give up on a nameserver the third time it timed out, and try it
34078 10 seconds later... and to give up on it every time it timed out
34080 - Take out the '5 second' timeout from the connection retry
34081 schedule. Now the first connect attempt will wait a full 10
34082 seconds before switching to a new circuit. Perhaps this will help
34083 a lot. Based on observations from Mike Perry.
34084 - Fix a bug on the Windows implementation of tor_mmap_file() that
34085 would prevent the cached-routers file from ever loading. Reported
34089 - Fix an assert failure when a directory authority sets
34090 AuthDirRejectUnlisted and then receives a descriptor from an
34091 unlisted router. Reported by seeess.
34092 - Avoid a double-free when parsing malformed DirServer lines.
34093 - Fix a bug when a BSD-style PF socket is first used. Patch from
34095 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
34096 to resolve an address at a given exit node even when they ask for
34098 - Servers no longer ever list themselves in their "family" line,
34099 even if configured to do so. This makes it easier to configure
34100 family lists conveniently.
34101 - When running as a server, don't fall back to 127.0.0.1 when no
34102 nameservers are configured in /etc/resolv.conf; instead, make the
34103 user fix resolv.conf or specify nameservers explicitly. (Resolves
34105 - Stop accepting certain malformed ports in configured exit policies.
34106 - Don't re-write the fingerprint file every restart, unless it has
34108 - Stop warning when a single nameserver fails: only warn when _all_ of
34109 our nameservers have failed. Also, when we only have one nameserver,
34110 raise the threshold for deciding that the nameserver is dead.
34111 - Directory authorities now only decide that routers are reachable
34112 if their identity keys are as expected.
34113 - When the user uses bad syntax in the Log config line, stop
34114 suggesting other bad syntax as a replacement.
34115 - Correctly detect ipv6 DNS capability on OpenBSD.
34117 o Minor bugfixes (controller):
34118 - Report the circuit number correctly in STREAM CLOSED events. Bug
34119 reported by Mike Perry.
34120 - Do not report bizarre values for results of accounting GETINFOs
34121 when the last second's write or read exceeds the allotted bandwidth.
34122 - Report "unrecognized key" rather than an empty string when the
34123 controller tries to fetch a networkstatus that doesn't exist.
34126 Changes in version 0.1.1.26 - 2006-12-14
34127 o Security bugfixes:
34128 - Stop sending the HttpProxyAuthenticator string to directory
34129 servers when directory connections are tunnelled through Tor.
34130 - Clients no longer store bandwidth history in the state file.
34131 - Do not log introduction points for hidden services if SafeLogging
34135 - Fix an assert failure when a directory authority sets
34136 AuthDirRejectUnlisted and then receives a descriptor from an
34137 unlisted router (reported by seeess).
34140 Changes in version 0.1.2.4-alpha - 2006-12-03
34142 - Add support for using natd; this allows FreeBSDs earlier than
34143 5.1.2 to have ipfw send connections through Tor without using
34144 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
34147 - Make all connections to addresses of the form ".noconnect"
34148 immediately get closed. This lets application/controller combos
34149 successfully test whether they're talking to the same Tor by
34150 watching for STREAM events.
34151 - Make cross.sh cross-compilation script work even when autogen.sh
34152 hasn't been run. (Patch from Michael Mohr.)
34153 - Statistics dumped by -USR2 now include a breakdown of public key
34154 operations, for profiling.
34157 - Fix a major leak when directory authorities parse their
34158 approved-routers list, a minor memory leak when we fail to pick
34159 an exit node, and a few rare leaks on errors.
34160 - Handle TransPort connections even when the server sends data before
34161 the client sends data. Previously, the connection would just hang
34162 until the client sent data. (Patch from tup based on patch from
34164 - Avoid assert failure when our cached-routers file is empty on
34168 - Don't log spurious warnings when we see a circuit close reason we
34169 don't recognize; it's probably just from a newer version of Tor.
34170 - Have directory authorities allow larger amounts of drift in uptime
34171 without replacing the server descriptor: previously, a server that
34172 restarted every 30 minutes could have 48 "interesting" descriptors
34174 - Start linking to the Tor specification and Tor reference manual
34175 correctly in the Windows installer.
34176 - Add Vidalia to the OS X uninstaller script, so when we uninstall
34177 Tor/Privoxy we also uninstall Vidalia.
34178 - Resume building on Irix64, and fix a lot of warnings from its
34179 MIPSpro C compiler.
34180 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
34181 when we're running as a client.
34184 Changes in version 0.1.1.25 - 2006-11-04
34186 - When a client asks us to resolve (rather than connect to)
34187 an address, and we have a cached answer, give them the cached
34188 answer. Previously, we would give them no answer at all.
34189 - We were building exactly the wrong circuits when we predict
34190 hidden service requirements, meaning Tor would have to build all
34191 its circuits on demand.
34192 - If none of our live entry guards have a high uptime, but we
34193 require a guard with a high uptime, try adding a new guard before
34194 we give up on the requirement. This patch should make long-lived
34195 connections more stable on average.
34196 - When testing reachability of our DirPort, don't launch new
34197 tests when there's already one in progress -- unreachable
34198 servers were stacking up dozens of testing streams.
34200 o Security bugfixes:
34201 - When the user sends a NEWNYM signal, clear the client-side DNS
34202 cache too. Otherwise we continue to act on previous information.
34205 - Avoid a memory corruption bug when creating a hash table for
34207 - Avoid possibility of controller-triggered crash when misusing
34208 certain commands from a v0 controller on platforms that do not
34209 handle printf("%s",NULL) gracefully.
34210 - Avoid infinite loop on unexpected controller input.
34211 - Don't log spurious warnings when we see a circuit close reason we
34212 don't recognize; it's probably just from a newer version of Tor.
34213 - Add Vidalia to the OS X uninstaller script, so when we uninstall
34214 Tor/Privoxy we also uninstall Vidalia.
34217 Changes in version 0.1.2.3-alpha - 2006-10-29
34219 - Prepare for servers to publish descriptors less often: never
34220 discard a descriptor simply for being too old until either it is
34221 recommended by no authorities, or until we get a better one for
34222 the same router. Make caches consider retaining old recommended
34223 routers for even longer.
34224 - If most authorities set a BadExit flag for a server, clients
34225 don't think of it as a general-purpose exit. Clients only consider
34226 authorities that advertise themselves as listing bad exits.
34227 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
34228 headers for content, so that we can work better in the presence of
34229 caching HTTP proxies.
34230 - Allow authorities to list nodes as bad exits by fingerprint or by
34233 o Minor features, controller:
34234 - Add a REASON field to CIRC events; for backward compatibility, this
34235 field is sent only to controllers that have enabled the extended
34236 event format. Also, add additional reason codes to explain why
34237 a given circuit has been destroyed or truncated. (Patches from
34239 - Add a REMOTE_REASON field to extended CIRC events to tell the
34240 controller about why a remote OR told us to close a circuit.
34241 - Stream events also now have REASON and REMOTE_REASON fields,
34242 working much like those for circuit events.
34243 - There's now a GETINFO ns/... field so that controllers can ask Tor
34244 about the current status of a router.
34245 - A new event type "NS" to inform a controller when our opinion of
34246 a router's status has changed.
34247 - Add a GETINFO events/names and GETINFO features/names so controllers
34248 can tell which events and features are supported.
34249 - A new CLEARDNSCACHE signal to allow controllers to clear the
34250 client-side DNS cache without expiring circuits.
34252 o Security bugfixes:
34253 - When the user sends a NEWNYM signal, clear the client-side DNS
34254 cache too. Otherwise we continue to act on previous information.
34257 - Avoid sending junk to controllers or segfaulting when a controller
34258 uses EVENT_NEW_DESC with verbose nicknames.
34259 - Stop triggering asserts if the controller tries to extend hidden
34260 service circuits (reported by mwenge).
34261 - Avoid infinite loop on unexpected controller input.
34262 - When the controller does a "GETINFO network-status", tell it
34263 about even those routers whose descriptors are very old, and use
34264 long nicknames where appropriate.
34265 - Change NT service functions to be loaded on demand. This lets us
34266 build with MinGW without breaking Tor for Windows 98 users.
34267 - Do DirPort reachability tests less often, since a single test
34268 chews through many circuits before giving up.
34269 - In the hidden service example in torrc.sample, stop recommending
34270 esoteric and discouraged hidden service options.
34271 - When stopping an NT service, wait up to 10 sec for it to actually
34272 stop. Patch from Matt Edman; resolves bug 295.
34273 - Fix handling of verbose nicknames with ORCONN controller events:
34274 make them show up exactly when requested, rather than exactly when
34276 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
34277 printing a duplicate "$" in the keys we send (reported by mwenge).
34278 - Correctly set maximum connection limit on Cygwin. (This time
34280 - Try to detect Windows correctly when cross-compiling.
34281 - Detect the size of the routers file correctly even if it is
34282 corrupted (on systems without mmap) or not page-aligned (on systems
34283 with mmap). This bug was harmless.
34284 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
34285 to open a stream fails; now we do in more cases. This should
34286 make clients able to find a good exit faster in some cases, since
34287 unhandleable requests will now get an error rather than timing out.
34288 - Resolve two memory leaks when rebuilding the on-disk router cache
34289 (reported by fookoowa).
34290 - Clean up minor code warnings suggested by the MIPSpro C compiler,
34291 and reported by some Centos users.
34292 - Controller signals now work on non-Unix platforms that don't define
34293 SIGUSR1 and SIGUSR2 the way we expect.
34294 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
34295 values before failing, and always enables eventdns.
34296 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
34297 Try to fix this in configure.in by checking for most functions
34298 before we check for libevent.
34301 Changes in version 0.1.2.2-alpha - 2006-10-07
34303 - Make our async eventdns library on-by-default for Tor servers,
34304 and plan to deprecate the separate dnsworker threads.
34305 - Add server-side support for "reverse" DNS lookups (using PTR
34306 records so clients can determine the canonical hostname for a given
34307 IPv4 address). Only supported by servers using eventdns; servers
34308 now announce in their descriptors whether they support eventdns.
34309 - Specify and implement client-side SOCKS5 interface for reverse DNS
34310 lookups (see doc/socks-extensions.txt).
34311 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
34312 connect to directory servers through Tor. Previously, clients needed
34313 to find Tor exits to make private connections to directory servers.
34314 - Avoid choosing Exit nodes for entry or middle hops when the
34315 total bandwidth available from non-Exit nodes is much higher than
34316 the total bandwidth available from Exit nodes.
34317 - Workaround for name servers (like Earthlink's) that hijack failing
34318 DNS requests and replace the no-such-server answer with a "helpful"
34319 redirect to an advertising-driven search portal. Also work around
34320 DNS hijackers who "helpfully" decline to hijack known-invalid
34321 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
34322 lets you turn it off.
34323 - Send out a burst of long-range padding cells once we've established
34324 that we're reachable. Spread them over 4 circuits, so hopefully
34325 a few will be fast. This exercises our bandwidth and bootstraps
34326 us into the directory more quickly.
34328 o New/improved config options:
34329 - Add new config option "ResolvConf" to let the server operator
34330 choose an alternate resolve.conf file when using eventdns.
34331 - Add an "EnforceDistinctSubnets" option to control our "exclude
34332 servers on the same /16" behavior. It's still on by default; this
34333 is mostly for people who want to operate private test networks with
34334 all the machines on the same subnet.
34335 - If one of our entry guards is on the ExcludeNodes list, or the
34336 directory authorities don't think it's a good guard, treat it as
34337 if it were unlisted: stop using it as a guard, and throw it off
34338 the guards list if it stays that way for a long time.
34339 - Allow directory authorities to be marked separately as authorities
34340 for the v1 directory protocol, the v2 directory protocol, and
34341 as hidden service directories, to make it easier to retire old
34342 authorities. V1 authorities should set "HSAuthoritativeDir 1"
34343 to continue being hidden service authorities too.
34344 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
34346 o Minor features, controller:
34347 - Fix CIRC controller events so that controllers can learn the
34348 identity digests of non-Named servers used in circuit paths.
34349 - Let controllers ask for more useful identifiers for servers. Instead
34350 of learning identity digests for un-Named servers and nicknames
34351 for Named servers, the new identifiers include digest, nickname,
34352 and indication of Named status. Off by default; see control-spec.txt
34353 for more information.
34354 - Add a "getinfo address" controller command so it can display Tor's
34355 best guess to the user.
34356 - New controller event to alert the controller when our server
34357 descriptor has changed.
34358 - Give more meaningful errors on controller authentication failure.
34360 o Minor features, other:
34361 - When asked to resolve a hostname, don't use non-exit servers unless
34362 requested to do so. This allows servers with broken DNS to be
34363 useful to the network.
34364 - Divide eventdns log messages into warn and info messages.
34365 - Reserve the nickname "Unnamed" for routers that can't pick
34366 a hostname: any router can call itself Unnamed; directory
34367 authorities will never allocate Unnamed to any particular router;
34368 clients won't believe that any router is the canonical Unnamed.
34369 - Only include function names in log messages for info/debug messages.
34370 For notice/warn/err, the content of the message should be clear on
34371 its own, and printing the function name only confuses users.
34372 - Avoid some false positives during reachability testing: don't try
34373 to test via a server that's on the same /24 as us.
34374 - If we fail to build a circuit to an intended enclave, and it's
34375 not mandatory that we use that enclave, stop wanting it.
34376 - When eventdns is enabled, allow multithreaded builds on NetBSD and
34377 OpenBSD. (We had previously disabled threads on these platforms
34378 because they didn't have working thread-safe resolver functions.)
34380 o Major bugfixes, anonymity/security:
34381 - If a client asked for a server by name, and there's a named server
34382 in our network-status but we don't have its descriptor yet, we
34383 could return an unnamed server instead.
34384 - Fix NetBSD bug that could allow someone to force uninitialized RAM
34385 to be sent to a server's DNS resolver. This only affects NetBSD
34386 and other platforms that do not bounds-check tolower().
34387 - Reject (most) attempts to use Tor circuits with length one. (If
34388 many people start using Tor as a one-hop proxy, exit nodes become
34389 a more attractive target for compromise.)
34390 - Just because your DirPort is open doesn't mean people should be
34391 able to remotely teach you about hidden service descriptors. Now
34392 only accept rendezvous posts if you've got HSAuthoritativeDir set.
34394 o Major bugfixes, other:
34395 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
34396 - When a client asks the server to resolve (not connect to)
34397 an address, and it has a cached answer, give them the cached answer.
34398 Previously, the server would give them no answer at all.
34399 - Allow really slow clients to not hang up five minutes into their
34400 directory downloads (suggested by Adam J. Richter).
34401 - We were building exactly the wrong circuits when we anticipated
34402 hidden service requirements, meaning Tor would have to build all
34403 its circuits on demand.
34404 - Avoid crashing when we mmap a router cache file of size 0.
34405 - When testing reachability of our DirPort, don't launch new
34406 tests when there's already one in progress -- unreachable
34407 servers were stacking up dozens of testing streams.
34409 o Minor bugfixes, correctness:
34410 - If we're a directory mirror and we ask for "all" network status
34411 documents, we would discard status documents from authorities
34412 we don't recognize.
34413 - Avoid a memory corruption bug when creating a hash table for
34415 - Avoid controller-triggered crash when misusing certain commands
34416 from a v0 controller on platforms that do not handle
34417 printf("%s",NULL) gracefully.
34418 - Don't crash when a controller sends a third argument to an
34419 "extendcircuit" request.
34420 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
34421 response; fix error code when "getinfo dir/status/" fails.
34422 - Avoid crash when telling controller stream-status and a stream
34424 - Patch from Adam Langley to fix assert() in eventdns.c.
34425 - Fix a debug log message in eventdns to say "X resolved to Y"
34426 instead of "X resolved to X".
34427 - Make eventdns give strings for DNS errors, not just error numbers.
34428 - Track unreachable entry guards correctly: don't conflate
34429 'unreachable by us right now' with 'listed as down by the directory
34430 authorities'. With the old code, if a guard was unreachable by
34431 us but listed as running, it would clog our guard list forever.
34432 - Behave correctly in case we ever have a network with more than
34433 2GB/s total advertised capacity.
34434 - Make TrackExitHosts case-insensitive, and fix the behavior of
34435 ".suffix" TrackExitHosts items to avoid matching in the middle of
34437 - Finally fix the openssl warnings from newer gccs that believe that
34438 ignoring a return value is okay, but casting a return value and
34439 then ignoring it is a sign of madness.
34440 - Prevent the contrib/exitlist script from printing the same
34441 result more than once.
34442 - Patch from Steve Hildrey: Generate network status correctly on
34443 non-versioning dirservers.
34444 - Don't listen to the X-Your-Address-Is hint if you did the lookup
34445 via Tor; otherwise you'll think you're the exit node's IP address.
34447 o Minor bugfixes, performance:
34448 - Two small performance improvements on parsing descriptors.
34449 - Major performance improvement on inserting descriptors: change
34450 algorithm from O(n^2) to O(n).
34451 - Make the common memory allocation path faster on machines where
34452 malloc(0) returns a pointer.
34453 - Start remembering X-Your-Address-Is directory hints even if you're
34454 a client, so you can become a server more smoothly.
34455 - Avoid duplicate entries on MyFamily line in server descriptor.
34457 o Packaging, features:
34458 - Remove architecture from OS X builds. The official builds are
34459 now universal binaries.
34460 - The Debian package now uses --verify-config when (re)starting,
34461 to distinguish configuration errors from other errors.
34462 - Update RPMs to require libevent 1.1b.
34464 o Packaging, bugfixes:
34465 - Patches so Tor builds with MinGW on Windows.
34466 - Patches so Tor might run on Cygwin again.
34467 - Resume building on non-gcc compilers and ancient gcc. Resume
34468 building with the -O0 compile flag. Resume building cleanly on
34470 - Run correctly on OS X platforms with case-sensitive filesystems.
34471 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
34472 - Add autoconf checks so Tor can build on Solaris x86 again.
34475 - Documented (and renamed) ServerDNSSearchDomains and
34476 ServerDNSResolvConfFile options.
34477 - Be clearer that the *ListenAddress directives can be repeated
34481 Changes in version 0.1.1.24 - 2006-09-29
34483 - Allow really slow clients to not hang up five minutes into their
34484 directory downloads (suggested by Adam J. Richter).
34485 - Fix major performance regression from 0.1.0.x: instead of checking
34486 whether we have enough directory information every time we want to
34487 do something, only check when the directory information has changed.
34488 This should improve client CPU usage by 25-50%.
34489 - Don't crash if, after a server has been running for a while,
34490 it can't resolve its hostname.
34493 - Allow Tor to start when RunAsDaemon is set but no logs are set.
34494 - Don't crash when the controller receives a third argument to an
34495 "extendcircuit" request.
34496 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
34497 response; fix error code when "getinfo dir/status/" fails.
34498 - Fix configure.in to not produce broken configure files with
34499 more recent versions of autoconf. Thanks to Clint for his auto*
34501 - Fix security bug on NetBSD that could allow someone to force
34502 uninitialized RAM to be sent to a server's DNS resolver. This
34503 only affects NetBSD and other platforms that do not bounds-check
34505 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
34506 methods: these are known to be buggy.
34507 - If we're a directory mirror and we ask for "all" network status
34508 documents, we would discard status documents from authorities
34509 we don't recognize.
34512 Changes in version 0.1.2.1-alpha - 2006-08-27
34514 - Add "eventdns" async dns library from Adam Langley, tweaked to
34515 build on OSX and Windows. Only enabled if you pass the
34516 --enable-eventdns argument to configure.
34517 - Allow servers with no hostname or IP address to learn their
34518 IP address by asking the directory authorities. This code only
34519 kicks in when you would normally have exited with a "no address"
34520 error. Nothing's authenticated, so use with care.
34521 - Rather than waiting a fixed amount of time between retrying
34522 application connections, we wait only 5 seconds for the first,
34523 10 seconds for the second, and 15 seconds for each retry after
34524 that. Hopefully this will improve the expected user experience.
34525 - Patch from Tup to add support for transparent AP connections:
34526 this basically bundles the functionality of trans-proxy-tor
34527 into the Tor mainline. Now hosts with compliant pf/netfilter
34528 implementations can redirect TCP connections straight to Tor
34529 without diverting through SOCKS. Needs docs.
34530 - Busy directory servers save lots of memory by spooling server
34531 descriptors, v1 directories, and v2 networkstatus docs to buffers
34532 as needed rather than en masse. Also mmap the cached-routers
34533 files, so we don't need to keep the whole thing in memory too.
34534 - Automatically avoid picking more than one node from the same
34535 /16 network when constructing a circuit.
34536 - Revise and clean up the torrc.sample that we ship with; add
34537 a section for BandwidthRate and BandwidthBurst.
34540 - Split circuit_t into origin_circuit_t and or_circuit_t, and
34541 split connection_t into edge, or, dir, control, and base structs.
34542 These will save quite a bit of memory on busy servers, and they'll
34543 also help us track down bugs in the code and bugs in the spec.
34544 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
34545 or later. Log when we are doing this, so we can diagnose it when
34546 it fails. (Also, recommend libevent 1.1b for kqueue and
34547 win32 methods; deprecate libevent 1.0b harder; make libevent
34548 recommendation system saner.)
34549 - Start being able to build universal binaries on OS X (thanks
34551 - Export the default exit policy via the control port, so controllers
34552 don't need to guess what it is / will be later.
34553 - Add a man page entry for ProtocolWarnings.
34554 - Add TestVia config option to the man page.
34555 - Remove even more protocol-related warnings from Tor server logs,
34556 such as bad TLS handshakes and malformed begin cells.
34557 - Stop fetching descriptors if you're not a dir mirror and you
34558 haven't tried to establish any circuits lately. [This currently
34559 causes some dangerous behavior, because when you start up again
34560 you'll use your ancient server descriptors.]
34561 - New DirPort behavior: if you have your dirport set, you download
34562 descriptors aggressively like a directory mirror, whether or not
34563 your ORPort is set.
34564 - Get rid of the router_retry_connections notion. Now routers
34565 no longer try to rebuild long-term connections to directory
34566 authorities, and directory authorities no longer try to rebuild
34567 long-term connections to all servers. We still don't hang up
34568 connections in these two cases though -- we need to look at it
34569 more carefully to avoid flapping, and we likely need to wait til
34570 0.1.1.x is obsolete.
34571 - Drop compatibility with obsolete Tors that permit create cells
34572 to have the wrong circ_id_type.
34573 - Re-enable per-connection rate limiting. Get rid of the "OP
34574 bandwidth" concept. Lay groundwork for "bandwidth classes" --
34575 separate global buckets that apply depending on what sort of conn
34577 - Start publishing one minute or so after we find our ORPort
34578 to be reachable. This will help reduce the number of descriptors
34579 we have for ourselves floating around, since it's quite likely
34580 other things (e.g. DirPort) will change during that minute too.
34581 - Fork the v1 directory protocol into its own spec document,
34582 and mark dir-spec.txt as the currently correct (v2) spec.
34585 - When we find our DirPort to be reachable, publish a new descriptor
34586 so we'll tell the world (reported by pnx).
34587 - Publish a new descriptor after we hup/reload. This is important
34588 if our config has changed such that we'll want to start advertising
34589 our DirPort now, etc.
34590 - Allow Tor to start when RunAsDaemon is set but no logs are set.
34591 - When we have a state file we cannot parse, tell the user and
34592 move it aside. Now we avoid situations where the user starts
34593 Tor in 1904, Tor writes a state file with that timestamp in it,
34594 the user fixes her clock, and Tor refuses to start.
34595 - Fix configure.in to not produce broken configure files with
34596 more recent versions of autoconf. Thanks to Clint for his auto*
34598 - "tor --verify-config" now exits with -1(255) or 0 depending on
34599 whether the config options are bad or good.
34600 - Resolve bug 321 when using dnsworkers: append a period to every
34601 address we resolve at the exit node, so that we do not accidentally
34602 pick up local addresses, and so that failing searches are retried
34603 in the resolver search domains. (This is already solved for
34604 eventdns.) (This breaks Blossom servers for now.)
34605 - If we are using an exit enclave and we can't connect, e.g. because
34606 its webserver is misconfigured to not listen on localhost, then
34607 back off and try connecting from somewhere else before we fail.
34610 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
34611 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
34612 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
34613 when the IP address is mapped through MapAddress to a hostname.
34614 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
34615 useless IPv6 DNS resolves.
34616 - Patch suggested by Karsten Loesing: respond to SIGNAL command
34617 before we execute the signal, in case the signal shuts us down.
34618 - Clean up AllowInvalidNodes man page entry.
34619 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
34620 - Add more asserts to track down an assert error on a windows Tor
34621 server with connection_add being called with socket == -1.
34622 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
34623 - Fix misleading log messages: an entry guard that is "unlisted",
34624 as well as not known to be "down" (because we've never heard
34625 of it), is not therefore "up".
34626 - Remove code to special-case "-cvs" ending, since it has not
34627 actually mattered since 0.0.9.
34628 - Make our socks5 handling more robust to broken socks clients:
34629 throw out everything waiting on the buffer in between socks
34630 handshake phases, since they can't possibly (so the theory
34631 goes) have predicted what we plan to respond to them.
34634 Changes in version 0.1.1.23 - 2006-07-30
34636 - Fast Tor servers, especially exit nodes, were triggering asserts
34637 due to a bug in handling the list of pending DNS resolves. Some
34638 bugs still remain here; we're hunting them.
34639 - Entry guards could crash clients by sending unexpected input.
34640 - More fixes on reachability testing: if you find yourself reachable,
34641 then don't ever make any client requests (so you stop predicting
34642 circuits), then hup or have your clock jump, then later your IP
34643 changes, you won't think circuits are working, so you won't try to
34644 test reachability, so you won't publish.
34647 - Avoid a crash if the controller does a resetconf firewallports
34648 and then a setconf fascistfirewall=1.
34649 - Avoid an integer underflow when the dir authority decides whether
34650 a router is stable: we might wrongly label it stable, and compute
34651 a slightly wrong median stability, when a descriptor is published
34653 - Fix a place where we might trigger an assert if we can't build our
34654 own server descriptor yet.
34657 Changes in version 0.1.1.22 - 2006-07-05
34659 - Fix a big bug that was causing servers to not find themselves
34660 reachable if they changed IP addresses. Since only 0.1.1.22+
34661 servers can do reachability testing correctly, now we automatically
34662 make sure to test via one of these.
34663 - Fix to allow clients and mirrors to learn directory info from
34664 descriptor downloads that get cut off partway through.
34665 - Directory authorities had a bug in deciding if a newly published
34666 descriptor was novel enough to make everybody want a copy -- a few
34667 servers seem to be publishing new descriptors many times a minute.
34669 - Fix a rare bug that was causing some servers to complain about
34670 "closing wedged cpuworkers" and skip some circuit create requests.
34671 - Make the Exit flag in directory status documents actually work.
34674 Changes in version 0.1.1.21 - 2006-06-10
34675 o Crash and assert fixes from 0.1.1.20:
34676 - Fix a rare crash on Tor servers that have enabled hibernation.
34677 - Fix a seg fault on startup for Tor networks that use only one
34678 directory authority.
34679 - Fix an assert from a race condition that occurs on Tor servers
34680 while exiting, where various threads are trying to log that they're
34681 exiting, and delete the logs, at the same time.
34682 - Make our unit tests pass again on certain obscure platforms.
34685 - Add support for building SUSE RPM packages.
34686 - Speed up initial bootstrapping for clients: if we are making our
34687 first ever connection to any entry guard, then don't mark it down
34689 - When only one Tor server in the network is labelled as a guard,
34690 and we've already picked him, we would cycle endlessly picking him
34691 again, being unhappy about it, etc. Now we specifically exclude
34692 current guards when picking a new guard.
34693 - Servers send create cells more reliably after the TLS connection
34694 is established: we were sometimes forgetting to send half of them
34695 when we had more than one pending.
34696 - If we get a create cell that asks us to extend somewhere, but the
34697 Tor server there doesn't match the expected digest, we now send
34698 a destroy cell back, rather than silently doing nothing.
34699 - Make options->RedirectExit work again.
34700 - Make cookie authentication for the controller work again.
34701 - Stop being picky about unusual characters in the arguments to
34702 mapaddress. It's none of our business.
34703 - Add a new config option "TestVia" that lets you specify preferred
34704 middle hops to use for test circuits. Perhaps this will let me
34705 debug the reachability problems better.
34707 o Log / documentation fixes:
34708 - If we're a server and some peer has a broken TLS certificate, don't
34709 log about it unless ProtocolWarnings is set, i.e., we want to hear
34710 about protocol violations by others.
34711 - Fix spelling of VirtualAddrNetwork in man page.
34712 - Add a better explanation at the top of the autogenerated torrc file
34713 about what happened to our old torrc.
34716 Changes in version 0.1.1.20 - 2006-05-23
34718 - Downgrade a log severity where servers complain that they're
34720 - Avoid a compile warning on FreeBSD.
34721 - Remove string size limit on NEWDESC messages; solve bug 291.
34722 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
34723 more thoroughly when we're running on windows.
34726 Changes in version 0.1.1.19-rc - 2006-05-03
34728 - Regenerate our local descriptor if it's dirty and we try to use
34729 it locally (e.g. if it changes during reachability detection).
34730 - If we setconf our ORPort to 0, we continued to listen on the
34731 old ORPort and receive connections.
34732 - Avoid a second warning about machine/limits.h on Debian
34734 - Be willing to add our own routerinfo into the routerlist.
34735 Now authorities will include themselves in their directories
34736 and network-statuses.
34737 - Stop trying to upload rendezvous descriptors to every
34738 directory authority: only try the v1 authorities.
34739 - Servers no longer complain when they think they're not
34740 registered with the directory authorities. There were too many
34742 - Backport dist-rpm changes so rpms can be built without errors.
34745 - Implement an option, VirtualAddrMask, to set which addresses
34746 get handed out in response to mapaddress requests. This works
34747 around a bug in tsocks where 127.0.0.0/8 is never socksified.
34750 Changes in version 0.1.1.18-rc - 2006-04-10
34752 - Work harder to download live network-statuses from all the
34753 directory authorities we know about. Improve the threshold
34754 decision logic so we're more robust to edge cases.
34755 - When fetching rendezvous descriptors, we were willing to ask
34756 v2 authorities too, which would always return 404.
34759 - Stop listing down or invalid nodes in the v1 directory. This will
34760 reduce its bulk by about 1/3, and reduce load on directory
34762 - When deciding whether a router is Fast or Guard-worthy, consider
34763 his advertised BandwidthRate and not just the BandwidthCapacity.
34764 - No longer ship INSTALL and README files -- they are useless now.
34765 - Force rpmbuild to behave and honor target_cpu.
34766 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
34767 - Start to include translated versions of the tor-doc-*.html
34768 files, along with the screenshots. Still needs more work.
34769 - Start sending back 512 and 451 errors if mapaddress fails,
34770 rather than not sending anything back at all.
34771 - When we fail to bind or listen on an incoming or outgoing
34772 socket, we should close it before failing. otherwise we just
34773 leak it. (thanks to weasel for finding.)
34774 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
34775 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
34776 - Make NoPublish (even though deprecated) work again.
34777 - Fix a minor security flaw where a versioning auth dirserver
34778 could list a recommended version many times in a row to make
34779 clients more convinced that it's recommended.
34780 - Fix crash bug if there are two unregistered servers running
34781 with the same nickname, one of them is down, and you ask for
34782 them by nickname in your EntryNodes or ExitNodes. Also, try
34783 to pick the one that's running rather than an arbitrary one.
34784 - Fix an infinite loop we could hit if we go offline for too long.
34785 - Complain when we hit WSAENOBUFS on recv() or write() too.
34786 Perhaps this will help us hunt the bug.
34787 - If you're not a versioning dirserver, don't put the string
34788 "client-versions \nserver-versions \n" in your network-status.
34789 - Lower the minimum required number of file descriptors to 1000,
34790 so we can have some overhead for Valgrind on Linux, where the
34791 default ulimit -n is 1024.
34794 - Add tor.dizum.com as the fifth authoritative directory server.
34795 - Add a new config option FetchUselessDescriptors, off by default,
34796 for when you plan to run "exitlist" on your client and you want
34797 to know about even the non-running descriptors.
34800 Changes in version 0.1.1.17-rc - 2006-03-28
34802 - Clients and servers since 0.1.1.10-alpha have been expiring
34803 connections whenever they are idle for 5 minutes and they *do*
34804 have circuits on them. Oops. With this new version, clients will
34805 discard their previous entry guard choices and avoid choosing
34806 entry guards running these flawed versions.
34807 - Fix memory leak when uncompressing concatenated zlib streams. This
34808 was causing substantial leaks over time on Tor servers.
34809 - The v1 directory was including servers as much as 48 hours old,
34810 because that's how the new routerlist->routers works. Now only
34811 include them if they're 20 hours old or less.
34814 - Resume building on irix64, netbsd 2.0, etc.
34815 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
34817 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
34818 and it is confusing some users.
34819 - Mirrors stop caching the v1 directory so often.
34820 - Make the max number of old descriptors that a cache will hold
34821 rise with the number of directory authorities, so we can scale.
34822 - Change our win32 uname() hack to be more forgiving about what
34823 win32 versions it thinks it's found.
34826 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
34828 - When the controller's *setconf commands fail, collect an error
34829 message in a string and hand it back to the controller.
34830 - Make the v2 dir's "Fast" flag based on relative capacity, just
34831 like "Stable" is based on median uptime. Name everything in the
34832 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
34833 - Log server fingerprint on startup, so new server operators don't
34834 have to go hunting around their filesystem for it.
34835 - Return a robots.txt on our dirport to discourage google indexing.
34836 - Let the controller ask for GETINFO dir/status/foo so it can ask
34837 directly rather than connecting to the dir port. Only works when
34838 dirport is set for now.
34840 o New config options rather than constants in the code:
34841 - SocksTimeout: How long do we let a socks connection wait
34842 unattached before we fail it?
34843 - CircuitBuildTimeout: Cull non-open circuits that were born
34844 at least this many seconds ago.
34845 - CircuitIdleTimeout: Cull open clean circuits that were born
34846 at least this many seconds ago.
34849 Changes in version 0.1.1.16-rc - 2006-03-18
34850 o Bugfixes on 0.1.1.15-rc:
34851 - Fix assert when the controller asks to attachstream a connect-wait
34852 or resolve-wait stream.
34853 - Now do address rewriting when the controller asks us to attach
34854 to a particular circuit too. This will let Blossom specify
34855 "moria2.exit" without having to learn what moria2's IP address is.
34856 - Make the "tor --verify-config" command-line work again, so people
34857 can automatically check if their torrc will parse.
34858 - Authoritative dirservers no longer require an open connection from
34859 a server to consider him "reachable". We need this change because
34860 when we add new auth dirservers, old servers won't know not to
34862 - Let Tor build on Sun CC again.
34863 - Fix an off-by-one buffer size in dirserv.c that magically never
34864 hit our three authorities but broke sjmurdoch's own tor network.
34865 - If we as a directory mirror don't know of any v1 directory
34866 authorities, then don't try to cache any v1 directories.
34867 - Stop warning about unknown servers in our family when they are
34868 given as hex digests.
34869 - Stop complaining as quickly to the server operator that he
34870 hasn't registered his nickname/key binding.
34871 - Various cleanups so we can add new V2 Auth Dirservers.
34872 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
34873 reflect the updated flags in our v2 dir protocol.
34874 - Resume allowing non-printable characters for exit streams (both
34875 for connecting and for resolving). Now we tolerate applications
34876 that don't follow the RFCs. But continue to block malformed names
34879 o Bugfixes on 0.1.0.x:
34880 - Fix assert bug in close_logs(): when we close and delete logs,
34881 remove them all from the global "logfiles" list.
34882 - Fix minor integer overflow in calculating when we expect to use up
34883 our bandwidth allocation before hibernating.
34884 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
34885 there are multiple SSLs installed with different versions.
34886 - When we try to be a server and Address is not explicitly set and
34887 our hostname resolves to a private IP address, try to use an
34888 interface address if it has a public address. Now Windows machines
34889 that think of themselves as localhost can work by default.
34892 - Let the controller ask for GETINFO dir/server/foo so it can ask
34893 directly rather than connecting to the dir port.
34894 - Let the controller tell us about certain router descriptors
34895 that it doesn't want Tor to use in circuits. Implement
34896 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
34897 - New config option SafeSocks to reject all application connections
34898 using unsafe socks protocols. Defaults to off.
34901 Changes in version 0.1.1.15-rc - 2006-03-11
34902 o Bugfixes and cleanups:
34903 - When we're printing strings from the network, don't try to print
34904 non-printable characters. This protects us against shell escape
34905 sequence exploits, and also against attacks to fool humans into
34906 misreading their logs.
34907 - Fix a bug where Tor would fail to establish any connections if you
34908 left it off for 24 hours and then started it: we were happy with
34909 the obsolete network statuses, but they all referred to router
34910 descriptors that were too old to fetch, so we ended up with no
34911 valid router descriptors.
34912 - Fix a seg fault in the controller's "getinfo orconn-status"
34913 command while listing status on incoming handshaking connections.
34914 Introduce a status name "NEW" for these connections.
34915 - If we get a linelist or linelist_s config option from the torrc
34916 (e.g. ExitPolicy) and it has no value, warn and skip rather than
34917 silently resetting it to its default.
34918 - Don't abandon entry guards until they've been down or gone for
34920 - Cleaner and quieter log messages.
34923 - New controller signal NEWNYM that makes new application requests
34924 use clean circuits.
34925 - Add a new circuit purpose 'controller' to let the controller ask
34926 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
34927 controller command to let you specify the purpose if you're
34928 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
34929 command to let you change a circuit's purpose after it's been
34931 - Accept "private:*" in routerdesc exit policies; not generated yet
34932 because older Tors do not understand it.
34933 - Add BSD-style contributed startup script "rc.subr" from Peter
34937 Changes in version 0.1.1.14-alpha - 2006-02-20
34938 o Bugfixes on 0.1.1.x:
34939 - Don't die if we ask for a stdout or stderr log (even implicitly)
34940 and we're set to RunAsDaemon -- just warn.
34941 - We still had a few bugs in the OR connection rotation code that
34942 caused directory servers to slowly aggregate connections to other
34943 fast Tor servers. This time for sure!
34944 - Make log entries on Win32 include the name of the function again.
34945 - We were treating a pair of exit policies if they were equal even
34946 if one said accept and the other said reject -- causing us to
34947 not always publish a new descriptor since we thought nothing
34949 - Retry pending server downloads as well as pending networkstatus
34950 downloads when we unexpectedly get a socks request.
34951 - We were ignoring the IS_FAST flag in the directory status,
34952 meaning we were willing to pick trivial-bandwidth nodes for "fast"
34954 - If the controller's SAVECONF command fails (e.g. due to file
34955 permissions), let the controller know that it failed.
34958 - If we're trying to be a Tor server and running Windows 95/98/ME
34959 as a server, explain that we'll likely crash.
34960 - When we're a server, a client asks for an old-style directory,
34961 and our write bucket is empty, don't give it to him. This way
34962 small servers can continue to serve the directory *sometimes*,
34963 without getting overloaded.
34964 - Compress exit policies even more -- look for duplicate lines
34966 - Clients now honor the "guard" flag in the router status when
34967 picking entry guards, rather than looking at is_fast or is_stable.
34968 - Retain unrecognized lines in $DATADIR/state file, so that we can
34969 be forward-compatible.
34970 - Generate 18.0.0.0/8 address policy format in descs when we can;
34971 warn when the mask is not reducible to a bit-prefix.
34972 - Let the user set ControlListenAddress in the torrc. This can be
34973 dangerous, but there are some cases (like a secured LAN) where it
34975 - Split ReachableAddresses into ReachableDirAddresses and
34976 ReachableORAddresses, so we can restrict Dir conns to port 80
34977 and OR conns to port 443.
34978 - Now we can target arch and OS in rpm builds (contributed by
34979 Phobos). Also make the resulting dist-rpm filename match the
34981 - New config options to help controllers: FetchServerDescriptors
34982 and FetchHidServDescriptors for whether to fetch server
34983 info and hidserv info or let the controller do it, and
34984 PublishServerDescriptor and PublishHidServDescriptors.
34985 - Also let the controller set the __AllDirActionsPrivate config
34986 option if you want all directory fetches/publishes to happen via
34987 Tor (it assumes your controller bootstraps your circuits).
34990 Changes in version 0.1.0.17 - 2006-02-17
34991 o Crash bugfixes on 0.1.0.x:
34992 - When servers with a non-zero DirPort came out of hibernation,
34993 sometimes they would trigger an assert.
34995 o Other important bugfixes:
34996 - On platforms that don't have getrlimit (like Windows), we were
34997 artificially constraining ourselves to a max of 1024
34998 connections. Now just assume that we can handle as many as 15000
34999 connections. Hopefully this won't cause other problems.
35001 o Backported features:
35002 - When we're a server, a client asks for an old-style directory,
35003 and our write bucket is empty, don't give it to him. This way
35004 small servers can continue to serve the directory *sometimes*,
35005 without getting overloaded.
35006 - Whenever you get a 503 in response to a directory fetch, try
35007 once more. This will become important once servers start sending
35008 503's whenever they feel busy.
35009 - Fetch a new directory every 120 minutes, not every 40 minutes.
35010 Now that we have hundreds of thousands of users running the old
35011 directory algorithm, it's starting to hurt a lot.
35012 - Bump up the period for forcing a hidden service descriptor upload
35013 from 20 minutes to 1 hour.
35016 Changes in version 0.1.1.13-alpha - 2006-02-09
35017 o Crashes in 0.1.1.x:
35018 - When you tried to setconf ORPort via the controller, Tor would
35019 crash. So people using TorCP to become a server were sad.
35020 - Solve (I hope) the stack-smashing bug that we were seeing on fast
35021 servers. The problem appears to be something do with OpenSSL's
35022 random number generation, or how we call it, or something. Let me
35023 know if the crashes continue.
35024 - Turn crypto hardware acceleration off by default, until we find
35025 somebody smart who can test it for us. (It appears to produce
35026 seg faults in at least some cases.)
35027 - Fix a rare assert error when we've tried all intro points for
35028 a hidden service and we try fetching the service descriptor again:
35029 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
35032 - Fix a major load balance bug: we were round-robining in 16 KB
35033 chunks, and servers with bandwidthrate of 20 KB, while downloading
35034 a 600 KB directory, would starve their other connections. Now we
35035 try to be a bit more fair.
35036 - Dir authorities and mirrors were never expiring the newest
35037 descriptor for each server, causing memory and directory bloat.
35038 - Fix memory-bloating and connection-bloating bug on servers: We
35039 were never closing any connection that had ever had a circuit on
35040 it, because we were checking conn->n_circuits == 0, yet we had a
35041 bug that let it go negative.
35042 - Make Tor work using squid as your http proxy again -- squid
35043 returns an error if you ask for a URL that's too long, and it uses
35044 a really generic error message. Plus, many people are behind a
35045 transparent squid so they don't even realize it.
35046 - On platforms that don't have getrlimit (like Windows), we were
35047 artificially constraining ourselves to a max of 1024
35048 connections. Now just assume that we can handle as many as 15000
35049 connections. Hopefully this won't cause other problems.
35050 - Add a new config option ExitPolicyRejectPrivate which defaults to
35051 1. This means all exit policies will begin with rejecting private
35052 addresses, unless the server operator explicitly turns it off.
35055 - Clients no longer download descriptors for non-running
35057 - Before we add new directory authorities, we should make it
35058 clear that only v1 authorities should receive/publish hidden
35059 service descriptors.
35062 - As soon as we've fetched some more directory info, immediately
35063 try to download more server descriptors. This way we don't have
35064 a 10 second pause during initial bootstrapping.
35065 - Remove even more loud log messages that the server operator can't
35067 - When we're running an obsolete or un-recommended version, make
35068 the log message more clear about what the problem is and what
35069 versions *are* still recommended.
35070 - Provide a more useful warn message when our onion queue gets full:
35071 the CPU is too slow or the exit policy is too liberal.
35072 - Don't warn when we receive a 503 from a dirserver/cache -- this
35073 will pave the way for them being able to refuse if they're busy.
35074 - When we fail to bind a listener, try to provide a more useful
35075 log message: e.g., "Is Tor already running?"
35076 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
35077 Goldberg can prove things about our handshake protocol more
35079 - MaxConn has been obsolete for a while now. Document the ConnLimit
35080 config option, which is a *minimum* number of file descriptors
35081 that must be available else Tor refuses to start.
35082 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
35083 if you log to syslog and want something other than LOG_DAEMON.
35084 - Make dirservers generate a separate "guard" flag to mean,
35085 "would make a good entry guard". Make clients parse it and vote
35086 on it. Not used by clients yet.
35087 - Implement --with-libevent-dir option to ./configure. Also, improve
35088 search techniques to find libevent, and use those for openssl too.
35089 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
35090 - Only start testing reachability once we've established a
35091 circuit. This will make startup on dirservers less noisy.
35092 - Don't try to upload hidden service descriptors until we have
35093 established a circuit.
35094 - Fix the controller's "attachstream 0" command to treat conn like
35095 it just connected, doing address remapping, handling .exit and
35096 .onion idioms, and so on. Now we're more uniform in making sure
35097 that the controller hears about new and closing connections.
35100 Changes in version 0.1.1.12-alpha - 2006-01-11
35101 o Bugfixes on 0.1.1.x:
35102 - The fix to close duplicate server connections was closing all
35103 Tor client connections if they didn't establish a circuit
35104 quickly enough. Oops.
35105 - Fix minor memory issue (double-free) that happened on exit.
35107 o Bugfixes on 0.1.0.x:
35108 - Tor didn't warn when it failed to open a log file.
35111 Changes in version 0.1.1.11-alpha - 2006-01-10
35112 o Crashes in 0.1.1.x:
35113 - Include all the assert/crash fixes from 0.1.0.16.
35114 - If you start Tor and then quit very quickly, there were some
35115 races that tried to free things that weren't allocated yet.
35116 - Fix a rare memory stomp if you're running hidden services.
35117 - Fix segfault when specifying DirServer in config without nickname.
35118 - Fix a seg fault when you finish connecting to a server but at
35119 that moment you dump his server descriptor.
35120 - Extendcircuit and Attachstream controller commands would
35121 assert/crash if you don't give them enough arguments.
35122 - Fix an assert error when we're out of space in the connection_list
35123 and we try to post a hidden service descriptor (reported by weasel).
35124 - If you specify a relative torrc path and you set RunAsDaemon in
35125 your torrc, then it chdir()'s to the new directory. If you HUP,
35126 it tries to load the new torrc location, fails, and exits.
35127 The fix: no longer allow a relative path to torrc using -f.
35130 - Implement "entry guards": automatically choose a handful of entry
35131 nodes and stick with them for all circuits. Only pick new guards
35132 when the ones you have are unsuitable, and if the old guards
35133 become suitable again, switch back. This will increase security
35134 dramatically against certain end-point attacks. The EntryNodes
35135 config option now provides some hints about which entry guards you
35136 want to use most; and StrictEntryNodes means to only use those.
35137 - New directory logic: download by descriptor digest, not by
35138 fingerprint. Caches try to download all listed digests from
35139 authorities; clients try to download "best" digests from caches.
35140 This avoids partitioning and isolating attacks better.
35141 - Make the "stable" router flag in network-status be the median of
35142 the uptimes of running valid servers, and make clients pay
35143 attention to the network-status flags. Thus the cutoff adapts
35144 to the stability of the network as a whole, making IRC, IM, etc
35145 connections more reliable.
35148 - Tor servers with dynamic IP addresses were needing to wait 18
35149 hours before they could start doing reachability testing using
35150 the new IP address and ports. This is because they were using
35151 the internal descriptor to learn what to test, yet they were only
35152 rebuilding the descriptor once they decided they were reachable.
35153 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
35154 to download certain server descriptors, throw them away, and then
35155 fetch them again after 30 minutes. Now mirrors throw away these
35156 server descriptors so clients can't get them.
35157 - We were leaving duplicate connections to other ORs open for a week,
35158 rather than closing them once we detect a duplicate. This only
35159 really affected authdirservers, but it affected them a lot.
35160 - Spread the authdirservers' reachability testing over the entire
35161 testing interval, so we don't try to do 500 TLS's at once every
35165 - If the network is down, and we try to connect to a conn because
35166 we have a circuit in mind, and we timeout (30 seconds) because the
35167 network never answers, we were expiring the circuit, but we weren't
35168 obsoleting the connection or telling the entry_guards functions.
35169 - Some Tor servers process billions of cells per day. These statistics
35170 need to be uint64_t's.
35171 - Check for integer overflows in more places, when adding elements
35172 to smartlists. This could possibly prevent a buffer overflow
35173 on malicious huge inputs. I don't see any, but I haven't looked
35175 - ReachableAddresses kept growing new "reject *:*" lines on every
35177 - When you "setconf log" via the controller, it should remove all
35178 logs. We were automatically adding back in a "log notice stdout".
35179 - Newly bootstrapped Tor networks couldn't establish hidden service
35180 circuits until they had nodes with high uptime. Be more tolerant.
35181 - We were marking servers down when they could not answer every piece
35182 of the directory request we sent them. This was far too harsh.
35183 - Fix the torify (tsocks) config file to not use Tor for localhost
35185 - Directory authorities now go to the proper authority when asking for
35186 a networkstatus, even when they want a compressed one.
35187 - Fix a harmless bug that was causing Tor servers to log
35188 "Got an end because of misc error, but we're not an AP. Closing."
35189 - Authorities were treating their own descriptor changes as cosmetic,
35190 meaning the descriptor available in the network-status and the
35191 descriptor that clients downloaded were different.
35192 - The OS X installer was adding a symlink for tor_resolve but
35193 the binary was called tor-resolve (reported by Thomas Hardly).
35194 - Workaround a problem with some http proxies where they refuse GET
35195 requests that specify "Content-Length: 0" (reported by Adrian).
35196 - Fix wrong log message when you add a "HiddenServiceNodes" config
35197 line without any HiddenServiceDir line (reported by Chris Thomas).
35200 - Write the TorVersion into the state file so we have a prayer of
35201 keeping forward and backward compatibility.
35202 - Revive the FascistFirewall config option rather than eliminating it:
35203 now it's a synonym for ReachableAddresses *:80,*:443.
35204 - Clients choose directory servers from the network status lists,
35205 not from their internal list of router descriptors. Now they can
35206 go to caches directly rather than needing to go to authorities
35208 - Directory authorities ignore router descriptors that have only
35209 cosmetic differences: do this for 0.1.0.x servers now too.
35210 - Add a new flag to network-status indicating whether the server
35211 can answer v2 directory requests too.
35212 - Authdirs now stop whining so loudly about bad descriptors that
35213 they fetch from other dirservers. So when there's a log complaint,
35214 it's for sure from a freshly uploaded descriptor.
35215 - Reduce memory requirements in our structs by changing the order
35217 - There used to be two ways to specify your listening ports in a
35218 server descriptor: on the "router" line and with a separate "ports"
35219 line. Remove support for the "ports" line.
35220 - New config option "AuthDirRejectUnlisted" for auth dirservers as
35221 a panic button: if we get flooded with unusable servers we can
35222 revert to only listing servers in the approved-routers file.
35223 - Auth dir servers can now mark a fingerprint as "!reject" or
35224 "!invalid" in the approved-routers file (as its nickname), to
35225 refuse descriptors outright or include them but marked as invalid.
35226 - Servers store bandwidth history across restarts/crashes.
35227 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
35228 get a better idea of why their circuits failed. Not used yet.
35229 - Directory mirrors now cache up to 16 unrecognized network-status
35230 docs. Now we can add new authdirservers and they'll be cached too.
35231 - When picking a random directory, prefer non-authorities if any
35233 - New controller option "getinfo desc/all-recent" to fetch the
35234 latest server descriptor for every router that Tor knows about.
35237 Changes in version 0.1.0.16 - 2006-01-02
35238 o Crash bugfixes on 0.1.0.x:
35239 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
35240 corrupting the heap, losing FDs, or crashing when we need to resize
35241 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
35242 - It turns out sparc64 platforms crash on unaligned memory access
35243 too -- so detect and avoid this.
35244 - Handle truncated compressed data correctly (by detecting it and
35246 - Fix possible-but-unlikely free(NULL) in control.c.
35247 - When we were closing connections, there was a rare case that
35248 stomped on memory, triggering seg faults and asserts.
35249 - Avoid potential infinite recursion when building a descriptor. (We
35250 don't know that it ever happened, but better to fix it anyway.)
35251 - We were neglecting to unlink marked circuits from soon-to-close OR
35252 connections, which caused some rare scribbling on freed memory.
35253 - Fix a memory stomping race bug when closing the joining point of two
35254 rendezvous circuits.
35255 - Fix an assert in time parsing found by Steven Murdoch.
35257 o Other bugfixes on 0.1.0.x:
35258 - When we're doing reachability testing, provide more useful log
35259 messages so the operator knows what to expect.
35260 - Do not check whether DirPort is reachable when we are suppressing
35261 advertising it because of hibernation.
35262 - When building with -static or on Solaris, we sometimes needed -ldl.
35263 - When we're deciding whether a stream has enough circuits around
35264 that can handle it, count the freshly dirty ones and not the ones
35265 that are so dirty they won't be able to handle it.
35266 - When we're expiring old circuits, we had a logic error that caused
35267 us to close new rendezvous circuits rather than old ones.
35268 - Give a more helpful log message when you try to change ORPort via
35269 the controller: you should upgrade Tor if you want that to work.
35270 - We were failing to parse Tor versions that start with "Tor ".
35271 - Tolerate faulty streams better: when a stream fails for reason
35272 exitpolicy, stop assuming that the router is lying about his exit
35273 policy. When a stream fails for reason misc, allow it to retry just
35274 as if it was resolvefailed. When a stream has failed three times,
35275 reset its failure count so we can try again and get all three tries.
35278 Changes in version 0.1.1.10-alpha - 2005-12-11
35279 o Correctness bugfixes on 0.1.0.x:
35280 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
35281 corrupting the heap, losing FDs, or crashing when we need to resize
35282 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
35283 - Stop doing the complex voodoo overkill checking for insecure
35284 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
35285 - When we were closing connections, there was a rare case that
35286 stomped on memory, triggering seg faults and asserts.
35287 - We were neglecting to unlink marked circuits from soon-to-close OR
35288 connections, which caused some rare scribbling on freed memory.
35289 - When we're deciding whether a stream has enough circuits around
35290 that can handle it, count the freshly dirty ones and not the ones
35291 that are so dirty they won't be able to handle it.
35292 - Recover better from TCP connections to Tor servers that are
35293 broken but don't tell you (it happens!); and rotate TLS
35294 connections once a week.
35295 - When we're expiring old circuits, we had a logic error that caused
35296 us to close new rendezvous circuits rather than old ones.
35297 - Fix a scary-looking but apparently harmless bug where circuits
35298 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
35299 servers, and never switch to state CIRCUIT_STATE_OPEN.
35300 - When building with -static or on Solaris, we sometimes needed to
35302 - Give a useful message when people run Tor as the wrong user,
35303 rather than telling them to start chowning random directories.
35304 - We were failing to inform the controller about new .onion streams.
35306 o Security bugfixes on 0.1.0.x:
35307 - Refuse server descriptors if the fingerprint line doesn't match
35308 the included identity key. Tor doesn't care, but other apps (and
35309 humans) might actually be trusting the fingerprint line.
35310 - We used to kill the circuit when we receive a relay command we
35311 don't recognize. Now we just drop it.
35312 - Start obeying our firewall options more rigorously:
35313 . If we can't get to a dirserver directly, try going via Tor.
35314 . Don't ever try to connect (as a client) to a place our
35315 firewall options forbid.
35316 . If we specify a proxy and also firewall options, obey the
35317 firewall options even when we're using the proxy: some proxies
35318 can only proxy to certain destinations.
35319 - Fix a bug found by Lasse Overlier: when we were making internal
35320 circuits (intended to be cannibalized later for rendezvous and
35321 introduction circuits), we were picking them so that they had
35322 useful exit nodes. There was no need for this, and it actually
35323 aids some statistical attacks.
35324 - Start treating internal circuits and exit circuits separately.
35325 It's important to keep them separate because internal circuits
35326 have their last hops picked like middle hops, rather than like
35327 exit hops. So exiting on them will break the user's expectations.
35329 o Bugfixes on 0.1.1.x:
35330 - Take out the mis-feature where we tried to detect IP address
35331 flapping for people with DynDNS, and chose not to upload a new
35332 server descriptor sometimes.
35333 - Try to be compatible with OpenSSL 0.9.6 again.
35334 - Log fix: when the controller is logging about .onion addresses,
35335 sometimes it didn't include the ".onion" part of the address.
35336 - Don't try to modify options->DirServers internally -- if the
35337 user didn't specify any, just add the default ones directly to
35338 the trusted dirserver list. This fixes a bug where people running
35339 controllers would use SETCONF on some totally unrelated config
35340 option, and Tor would start yelling at them about changing their
35342 - Let the controller's redirectstream command specify a port, in
35343 case the controller wants to change that too.
35344 - When we requested a pile of server descriptors, we sometimes
35345 accidentally launched a duplicate request for the first one.
35346 - Bugfix for trackhostexits: write down the fingerprint of the
35347 chosen exit, not its nickname, because the chosen exit might not
35349 - When parsing foo.exit, if foo is unknown, and we are leaving
35350 circuits unattached, set the chosen_exit field and leave the
35351 address empty. This matters because controllers got confused
35353 - Directory authorities no longer try to download server
35354 descriptors that they know they will reject.
35356 o Features and updates:
35357 - Replace balanced trees with hash tables: this should make stuff
35358 significantly faster.
35359 - Resume using the AES counter-mode implementation that we ship,
35360 rather than OpenSSL's. Ours is significantly faster.
35361 - Many other CPU and memory improvements.
35362 - Add a new config option FastFirstHopPK (on by default) so clients
35363 do a trivial crypto handshake for their first hop, since TLS has
35364 already taken care of confidentiality and authentication.
35365 - Add a new config option TestSocks so people can see if their
35366 applications are using socks4, socks4a, socks5-with-ip, or
35367 socks5-with-hostname. This way they don't have to keep mucking
35368 with tcpdump and wondering if something got cached somewhere.
35369 - Warn when listening on a public address for socks. I suspect a
35370 lot of people are setting themselves up as open socks proxies,
35371 and they have no idea that jerks on the Internet are using them,
35372 since they simply proxy the traffic into the Tor network.
35373 - Add "private:*" as an alias in configuration for policies. Now
35374 you can simplify your exit policy rather than needing to list
35375 every single internal or nonroutable network space.
35376 - Add a new controller event type that allows controllers to get
35377 all server descriptors that were uploaded to a router in its role
35378 as authoritative dirserver.
35379 - Start shipping socks-extensions.txt, tor-doc-unix.html,
35380 tor-doc-server.html, and stylesheet.css in the tarball.
35381 - Stop shipping tor-doc.html in the tarball.
35384 Changes in version 0.1.1.9-alpha - 2005-11-15
35385 o Usability improvements:
35386 - Start calling it FooListenAddress rather than FooBindAddress,
35387 since few of our users know what it means to bind an address
35389 - Reduce clutter in server logs. We're going to try to make
35390 them actually usable now. New config option ProtocolWarnings that
35391 lets you hear about how _other Tors_ are breaking the protocol. Off
35393 - Divide log messages into logging domains. Once we put some sort
35394 of interface on this, it will let people looking at more verbose
35395 log levels specify the topics they want to hear more about.
35396 - Make directory servers return better http 404 error messages
35397 instead of a generic "Servers unavailable".
35398 - Check for even more Windows version flags when writing the platform
35399 string in server descriptors, and note any we don't recognize.
35400 - Clean up more of the OpenSSL memory when exiting, so we can detect
35401 memory leaks better.
35402 - Make directory authorities be non-versioning, non-naming by
35403 default. Now we can add new directory servers without requiring
35404 their operators to pay close attention.
35405 - When logging via syslog, include the pid whenever we provide
35406 a log entry. Suggested by Todd Fries.
35408 o Performance improvements:
35409 - Directory servers now silently throw away new descriptors that
35410 haven't changed much if the timestamps are similar. We do this to
35411 tolerate older Tor servers that upload a new descriptor every 15
35412 minutes. (It seemed like a good idea at the time.)
35413 - Inline bottleneck smartlist functions; use fast versions by default.
35414 - Add a "Map from digest to void*" abstraction digestmap_t so we
35415 can do less hex encoding/decoding. Use it in router_get_by_digest()
35416 to resolve a performance bottleneck.
35417 - Allow tor_gzip_uncompress to extract as much as possible from
35418 truncated compressed data. Try to extract as many
35419 descriptors as possible from truncated http responses (when
35420 DIR_PURPOSE_FETCH_ROUTERDESC).
35421 - Make circ->onionskin a pointer, not a static array. moria2 was using
35422 125000 circuit_t's after it had been up for a few weeks, which
35423 translates to 20+ megs of wasted space.
35424 - The private half of our EDH handshake keys are now chosen out
35425 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
35427 o Security improvements:
35428 - Start making directory caches retain old routerinfos, so soon
35429 clients can start asking by digest of descriptor rather than by
35430 fingerprint of server.
35431 - Add half our entropy from RAND_poll in OpenSSL. This knows how
35432 to use egd (if present), openbsd weirdness (if present), vms/os2
35433 weirdness (if we ever port there), and more in the future.
35435 o Bugfixes on 0.1.0.x:
35436 - Do round-robin writes of at most 16 kB per write. This might be
35437 more fair on loaded Tor servers, and it might resolve our Windows
35438 crash bug. It might also slow things down.
35439 - Our TLS handshakes were generating a single public/private
35440 keypair for the TLS context, rather than making a new one for
35441 each new connections. Oops. (But we were still rotating them
35442 periodically, so it's not so bad.)
35443 - When we were cannibalizing a circuit with a particular exit
35444 node in mind, we weren't checking to see if that exit node was
35445 already present earlier in the circuit. Oops.
35446 - When a Tor server's IP changes (e.g. from a dyndns address),
35447 upload a new descriptor so clients will learn too.
35448 - Really busy servers were keeping enough circuits open on stable
35449 connections that they were wrapping around the circuit_id
35450 space. (It's only two bytes.) This exposed a bug where we would
35451 feel free to reuse a circuit_id even if it still exists but has
35452 been marked for close. Try to fix this bug. Some bug remains.
35453 - If we would close a stream early (e.g. it asks for a .exit that
35454 we know would refuse it) but the LeaveStreamsUnattached config
35455 option is set by the controller, then don't close it.
35457 o Bugfixes on 0.1.1.8-alpha:
35458 - Fix a big pile of memory leaks, some of them serious.
35459 - Do not try to download a routerdesc if we would immediately reject
35461 - Resume inserting a newline between all router descriptors when
35462 generating (old style) signed directories, since our spec says
35464 - When providing content-type application/octet-stream for
35465 server descriptors using .z, we were leaving out the
35466 content-encoding header. Oops. (Everything tolerated this just
35467 fine, but that doesn't mean we need to be part of the problem.)
35468 - Fix a potential seg fault in getconf and getinfo using version 1
35469 of the controller protocol.
35470 - Avoid crash: do not check whether DirPort is reachable when we
35471 are suppressing it because of hibernation.
35472 - Make --hash-password not crash on exit.
35475 Changes in version 0.1.1.8-alpha - 2005-10-07
35476 o New features (major):
35477 - Clients don't download or use the directory anymore. Now they
35478 download and use network-statuses from the trusted dirservers,
35479 and fetch individual server descriptors as needed from mirrors.
35480 See dir-spec.txt for all the gory details.
35481 - Be more conservative about whether to advertise our DirPort.
35482 The main change is to not advertise if we're running at capacity
35483 and either a) we could hibernate or b) our capacity is low and
35484 we're using a default DirPort.
35485 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
35487 o New features (minor):
35488 - Try to be smart about when to retry network-status and
35489 server-descriptor fetches. Still needs some tuning.
35490 - Stop parsing, storing, or using running-routers output (but
35491 mirrors still cache and serve it).
35492 - Consider a threshold of versioning dirservers (dirservers who have
35493 an opinion about which Tor versions are still recommended) before
35494 deciding whether to warn the user that he's obsolete.
35495 - Dirservers can now reject/invalidate by key and IP, with the
35496 config options "AuthDirInvalid" and "AuthDirReject". This is
35497 useful since currently we automatically list servers as running
35498 and usable even if we know they're jerks.
35499 - Provide dire warnings to any users who set DirServer; move it out
35500 of torrc.sample and into torrc.complete.
35501 - Add MyFamily to torrc.sample in the server section.
35502 - Add nicknames to the DirServer line, so we can refer to them
35503 without requiring all our users to memorize their IP addresses.
35504 - When we get an EOF or a timeout on a directory connection, note
35505 how many bytes of serverdesc we are dropping. This will help
35506 us determine whether it is smart to parse incomplete serverdesc
35508 - Add a new function to "change pseudonyms" -- that is, to stop
35509 using any currently-dirty circuits for new streams, so we don't
35510 link new actions to old actions. Currently it's only called on
35511 HUP (or SIGNAL RELOAD).
35512 - On sighup, if UseHelperNodes changed to 1, use new circuits.
35513 - Start using RAND_bytes rather than RAND_pseudo_bytes from
35514 OpenSSL. Also, reseed our entropy every hour, not just at
35515 startup. And entropy in 512-bit chunks, not 160-bit chunks.
35517 o Fixes on 0.1.1.7-alpha:
35518 - Nobody ever implemented EVENT_ADDRMAP for control protocol
35519 version 0, so don't let version 0 controllers ask for it.
35520 - If you requested something with too many newlines via the
35521 v1 controller protocol, you could crash tor.
35522 - Fix a number of memory leaks, including some pretty serious ones.
35523 - Re-enable DirPort testing again, so Tor servers will be willing
35524 to advertise their DirPort if it's reachable.
35525 - On TLS handshake, only check the other router's nickname against
35526 its expected nickname if is_named is set.
35528 o Fixes forward-ported from 0.1.0.15:
35529 - Don't crash when we don't have any spare file descriptors and we
35530 try to spawn a dns or cpu worker.
35531 - Make the numbers in read-history and write-history into uint64s,
35532 so they don't overflow and publish negatives in the descriptor.
35534 o Fixes on 0.1.0.x:
35535 - For the OS X package's modified privoxy config file, comment
35536 out the "logfile" line so we don't log everything passed
35538 - We were whining about using socks4 or socks5-with-local-lookup
35539 even when it's an IP in the "virtual" range we designed exactly
35541 - We were leaking some memory every time the client changes IPs.
35542 - Never call free() on tor_malloc()d memory. This will help us
35543 use dmalloc to detect memory leaks.
35544 - Check for named servers when looking them up by nickname;
35545 warn when we'recalling a non-named server by its nickname;
35546 don't warn twice about the same name.
35547 - Try to list MyFamily elements by key, not by nickname, and warn
35548 if we've not heard of the server.
35549 - Make windows platform detection (uname equivalent) smarter.
35550 - It turns out sparc64 doesn't like unaligned access either.
35553 Changes in version 0.1.0.15 - 2005-09-23
35554 o Bugfixes on 0.1.0.x:
35555 - Reject ports 465 and 587 (spam targets) in default exit policy.
35556 - Don't crash when we don't have any spare file descriptors and we
35557 try to spawn a dns or cpu worker.
35558 - Get rid of IgnoreVersion undocumented config option, and make us
35559 only warn, never exit, when we're running an obsolete version.
35560 - Don't try to print a null string when your server finds itself to
35561 be unreachable and the Address config option is empty.
35562 - Make the numbers in read-history and write-history into uint64s,
35563 so they don't overflow and publish negatives in the descriptor.
35564 - Fix a minor memory leak in smartlist_string_remove().
35565 - We were only allowing ourselves to upload a server descriptor at
35566 most every 20 minutes, even if it changed earlier than that.
35567 - Clean up log entries that pointed to old URLs.
35570 Changes in version 0.1.1.7-alpha - 2005-09-14
35571 o Fixes on 0.1.1.6-alpha:
35572 - Exit servers were crashing when people asked them to make a
35573 connection to an address not in their exit policy.
35574 - Looking up a non-existent stream for a v1 control connection would
35576 - Fix a seg fault if we ask a dirserver for a descriptor by
35577 fingerprint but he doesn't know about him.
35578 - SETCONF was appending items to linelists, not clearing them.
35579 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
35580 out and refuse the setconf if it would fail.
35581 - Downgrade the dirserver log messages when whining about
35585 - Add Peter Palfrader's check-tor script to tor/contrib/
35586 It lets you easily check whether a given server (referenced by
35587 nickname) is reachable by you.
35588 - Numerous changes to move towards client-side v2 directories. Not
35591 o Fixes on 0.1.0.x:
35592 - If the user gave tor an odd number of command-line arguments,
35593 we were silently ignoring the last one. Now we complain and fail.
35594 [This wins the oldest-bug prize -- this bug has been present since
35595 November 2002, as released in Tor 0.0.0.]
35596 - Do not use unaligned memory access on alpha, mips, or mipsel.
35597 It *works*, but is very slow, so we treat them as if it doesn't.
35598 - Retry directory requests if we fail to get an answer we like
35599 from a given dirserver (we were retrying before, but only if
35600 we fail to connect).
35601 - When writing the RecommendedVersions line, sort them first.
35602 - When the client asked for a rendezvous port that the hidden
35603 service didn't want to provide, we were sending an IP address
35604 back along with the end cell. Fortunately, it was zero. But stop
35606 - Correct "your server is reachable" log entries to indicate that
35607 it was self-testing that told us so.
35610 Changes in version 0.1.1.6-alpha - 2005-09-09
35611 o Fixes on 0.1.1.5-alpha:
35612 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
35613 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
35614 - Fix bug with tor_memmem finding a match at the end of the string.
35615 - Make unit tests run without segfaulting.
35616 - Resolve some solaris x86 compile warnings.
35617 - Handle duplicate lines in approved-routers files without warning.
35618 - Fix bug where as soon as a server refused any requests due to his
35619 exit policy (e.g. when we ask for localhost and he tells us that's
35620 127.0.0.1 and he won't do it), we decided he wasn't obeying his
35621 exit policy using him for any exits.
35622 - Only do openssl hardware accelerator stuff if openssl version is
35625 o New controller features/fixes:
35626 - Add a "RESETCONF" command so you can set config options like
35627 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
35628 a config option in the torrc with no value, then it clears it
35629 entirely (rather than setting it to its default).
35630 - Add a "GETINFO config-file" to tell us where torrc is.
35631 - Avoid sending blank lines when GETINFO replies should be empty.
35632 - Add a QUIT command for the controller (for using it manually).
35633 - Fix a bug in SAVECONF that was adding default dirservers and
35634 other redundant entries to the torrc file.
35636 o Start on the new directory design:
35637 - Generate, publish, cache, serve new network-status format.
35638 - Publish individual descriptors (by fingerprint, by "all", and by
35640 - Publish client and server recommended versions separately.
35641 - Allow tor_gzip_uncompress() to handle multiple concatenated
35642 compressed strings. Serve compressed groups of router
35643 descriptors. The compression logic here could be more
35645 - Distinguish v1 authorities (all currently trusted directories)
35646 from v2 authorities (all trusted directories).
35647 - Change DirServers config line to note which dirs are v1 authorities.
35648 - Add configuration option "V1AuthoritativeDirectory 1" which
35649 moria1, moria2, and tor26 should set.
35650 - Remove option when getting directory cache to see whether they
35651 support running-routers; they all do now. Replace it with one
35652 to see whether caches support v2 stuff.
35655 - Dirservers now do their own external reachability testing of each
35656 Tor server, and only list them as running if they've been found to
35657 be reachable. We also send back warnings to the server's logs if
35658 it uploads a descriptor that we already believe is unreachable.
35659 - Implement exit enclaves: if we know an IP address for the
35660 destination, and there's a running Tor server at that address
35661 which allows exit to the destination, then extend the circuit to
35662 that exit first. This provides end-to-end encryption and end-to-end
35663 authentication. Also, if the user wants a .exit address or enclave,
35664 use 4 hops rather than 3, and cannibalize a general circ for it
35666 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
35667 controller. Also, rotate dns and cpu workers if the controller
35668 changes options that will affect them; and initialize the dns
35669 worker cache tree whether or not we start out as a server.
35670 - Only upload a new server descriptor when options change, 18
35671 hours have passed, uptime is reset, or bandwidth changes a lot.
35672 - Check [X-]Forwarded-For headers in HTTP requests when generating
35673 log messages. This lets people run dirservers (and caches) behind
35674 Apache but still know which IP addresses are causing warnings.
35676 o Config option changes:
35677 - Replace (Fascist)Firewall* config options with a new
35678 ReachableAddresses option that understands address policies.
35679 For example, "ReachableAddresses *:80,*:443"
35680 - Get rid of IgnoreVersion undocumented config option, and make us
35681 only warn, never exit, when we're running an obsolete version.
35682 - Make MonthlyAccountingStart config option truly obsolete now.
35684 o Fixes on 0.1.0.x:
35685 - Reject ports 465 and 587 in the default exit policy, since
35686 people have started using them for spam too.
35687 - It turns out we couldn't bootstrap a network since we added
35688 reachability detection in 0.1.0.1-rc. Good thing the Tor network
35689 has never gone down. Add an AssumeReachable config option to let
35690 servers and dirservers bootstrap. When we're trying to build a
35691 high-uptime or high-bandwidth circuit but there aren't enough
35692 suitable servers, try being less picky rather than simply failing.
35693 - Our logic to decide if the OR we connected to was the right guy
35694 was brittle and maybe open to a mitm for unverified routers.
35695 - We weren't cannibalizing circuits correctly for
35696 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
35697 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
35698 build those from scratch. This should make hidden services faster.
35699 - Predict required circuits better, with an eye toward making hidden
35700 services faster on the service end.
35701 - Retry streams if the exit node sends back a 'misc' failure. This
35702 should result in fewer random failures. Also, after failing
35703 from resolve failed or misc, reset the num failures, so we give
35704 it a fair shake next time we try.
35705 - Clean up the rendezvous warn log msgs, and downgrade some to info.
35706 - Reduce severity on logs about dns worker spawning and culling.
35707 - When we're shutting down and we do something like try to post a
35708 server descriptor or rendezvous descriptor, don't complain that
35709 we seem to be unreachable. Of course we are, we're shutting down.
35710 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
35711 We don't use them yet, but maybe one day our DNS resolver will be
35712 able to discover them.
35713 - Make ContactInfo mandatory for authoritative directory servers.
35714 - Require server descriptors to list IPv4 addresses -- hostnames
35715 are no longer allowed. This also fixes some potential security
35716 problems with people providing hostnames as their address and then
35717 preferentially resolving them to partition users.
35718 - Change log line for unreachability to explicitly suggest /etc/hosts
35719 as the culprit. Also make it clearer what IP address and ports we're
35720 testing for reachability.
35721 - Put quotes around user-supplied strings when logging so users are
35722 more likely to realize if they add bad characters (like quotes)
35724 - Let auth dir servers start without specifying an Address config
35726 - Make unit tests (and other invocations that aren't the real Tor)
35727 run without launching listeners, creating subdirectories, and so on.
35730 Changes in version 0.1.1.5-alpha - 2005-08-08
35731 o Bugfixes included in 0.1.0.14.
35733 o Bugfixes on 0.1.0.x:
35734 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
35735 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
35736 it would silently using ignore the 6668.
35739 Changes in version 0.1.0.14 - 2005-08-08
35740 o Bugfixes on 0.1.0.x:
35741 - Fix the other half of the bug with crypto handshakes
35743 - Fix an assert trigger if you send a 'signal term' via the
35744 controller when it's listening for 'event info' messages.
35747 Changes in version 0.1.1.4-alpha - 2005-08-04
35748 o Bugfixes included in 0.1.0.13.
35751 - Improve tor_gettimeofday() granularity on windows.
35752 - Make clients regenerate their keys when their IP address changes.
35753 - Implement some more GETINFO goodness: expose helper nodes, config
35754 options, getinfo keys.
35757 Changes in version 0.1.0.13 - 2005-08-04
35758 o Bugfixes on 0.1.0.x:
35759 - Fix a critical bug in the security of our crypto handshakes.
35760 - Fix a size_t underflow in smartlist_join_strings2() that made
35761 it do bad things when you hand it an empty smartlist.
35762 - Fix Windows installer to ship Tor license (thanks to Aphex for
35763 pointing out this oversight) and put a link to the doc directory
35765 - Explicitly set no-unaligned-access for sparc: it turns out the
35766 new gcc's let you compile broken code, but that doesn't make it
35770 Changes in version 0.1.1.3-alpha - 2005-07-23
35771 o Bugfixes on 0.1.1.2-alpha:
35772 - Fix a bug in handling the controller's "post descriptor"
35774 - Fix several bugs in handling the controller's "extend circuit"
35776 - Fix a bug in handling the controller's "stream status" event.
35777 - Fix an assert failure if we have a controller listening for
35778 circuit events and we go offline.
35779 - Re-allow hidden service descriptors to publish 0 intro points.
35780 - Fix a crash when generating your hidden service descriptor if
35781 you don't have enough intro points already.
35783 o New features on 0.1.1.2-alpha:
35784 - New controller function "getinfo accounting", to ask how
35785 many bytes we've used in this time period.
35786 - Experimental support for helper nodes: a lot of the risk from
35787 a small static adversary comes because users pick new random
35788 nodes every time they rebuild a circuit. Now users will try to
35789 stick to the same small set of entry nodes if they can. Not
35790 enabled by default yet.
35792 o Bugfixes on 0.1.0.12:
35793 - If you're an auth dir server, always publish your dirport,
35794 even if you haven't yet found yourself to be reachable.
35795 - Fix a size_t underflow in smartlist_join_strings2() that made
35796 it do bad things when you hand it an empty smartlist.
35799 Changes in version 0.1.0.12 - 2005-07-18
35800 o New directory servers:
35801 - tor26 has changed IP address.
35803 o Bugfixes on 0.1.0.x:
35804 - Fix a possible double-free in tor_gzip_uncompress().
35805 - When --disable-threads is set, do not search for or link against
35806 pthreads libraries.
35807 - Don't trigger an assert if an authoritative directory server
35808 claims its dirport is 0.
35809 - Fix bug with removing Tor as an NT service: some people were
35810 getting "The service did not return an error." Thanks to Matt
35814 Changes in version 0.1.1.2-alpha - 2005-07-15
35815 o New directory servers:
35816 - tor26 has changed IP address.
35818 o Bugfixes on 0.1.0.x, crashes/leaks:
35819 - Port the servers-not-obeying-their-exit-policies fix from
35821 - Fix an fd leak in start_daemon().
35822 - On Windows, you can't always reopen a port right after you've
35823 closed it. So change retry_listeners() to only close and re-open
35824 ports that have changed.
35825 - Fix a possible double-free in tor_gzip_uncompress().
35827 o Bugfixes on 0.1.0.x, usability:
35828 - When tor_socketpair() fails in Windows, give a reasonable
35829 Windows-style errno back.
35830 - Let people type "tor --install" as well as "tor -install" when
35832 want to make it an NT service.
35833 - NT service patch from Matt Edman to improve error messages.
35834 - When the controller asks for a config option with an abbreviated
35835 name, give the full name in our response.
35836 - Correct the man page entry on TrackHostExitsExpire.
35837 - Looks like we were never delivering deflated (i.e. compressed)
35838 running-routers lists, even when asked. Oops.
35839 - When --disable-threads is set, do not search for or link against
35840 pthreads libraries.
35842 o Bugfixes on 0.1.1.x:
35843 - Fix a seg fault with autodetecting which controller version is
35847 - New hidden service descriptor format: put a version in it, and
35848 let people specify introduction/rendezvous points that aren't
35849 in "the directory" (which is subjective anyway).
35850 - Allow the DEBUG controller event to work again. Mark certain log
35851 entries as "don't tell this to controllers", so we avoid cycles.
35854 Changes in version 0.1.0.11 - 2005-06-30
35855 o Bugfixes on 0.1.0.x:
35856 - Fix major security bug: servers were disregarding their
35857 exit policies if clients behaved unexpectedly.
35858 - Make OS X init script check for missing argument, so we don't
35859 confuse users who invoke it incorrectly.
35860 - Fix a seg fault in "tor --hash-password foo".
35861 - The MAPADDRESS control command was broken.
35864 Changes in version 0.1.1.1-alpha - 2005-06-29
35866 - Make OS X init script check for missing argument, so we don't
35867 confuse users who invoke it incorrectly.
35868 - Fix a seg fault in "tor --hash-password foo".
35869 - Fix a possible way to DoS dirservers.
35870 - When we complain that your exit policy implicitly allows local or
35871 private address spaces, name them explicitly so operators can
35873 - Make the log message less scary when all the dirservers are
35874 temporarily unreachable.
35875 - We were printing the number of idle dns workers incorrectly when
35879 - Revised controller protocol (version 1) that uses ascii rather
35880 than binary. Add supporting libraries in python and java so you
35881 can use the controller from your applications without caring how
35882 our protocol works.
35883 - Spiffy new support for crypto hardware accelerators. Can somebody
35887 Changes in version 0.0.9.10 - 2005-06-16
35888 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
35889 - Refuse relay cells that claim to have a length larger than the
35890 maximum allowed. This prevents a potential attack that could read
35891 arbitrary memory (e.g. keys) from an exit server's process
35895 Changes in version 0.1.0.10 - 2005-06-14
35896 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
35897 libevent before 1.1a.
35900 Changes in version 0.1.0.9-rc - 2005-06-09
35902 - Reset buf->highwater every time buf_shrink() is called, not just on
35903 a successful shrink. This was causing significant memory bloat.
35904 - Fix buffer overflow when checking hashed passwords.
35905 - Security fix: if seeding the RNG on Win32 fails, quit.
35906 - Allow seeding the RNG on Win32 even when you're not running as
35908 - Disable threading on Solaris too. Something is wonky with it,
35909 cpuworkers, and reentrant libs.
35910 - Reenable the part of the code that tries to flush as soon as an
35911 OR outbuf has a full TLS record available. Perhaps this will make
35912 OR outbufs not grow as huge except in rare cases, thus saving lots
35913 of CPU time plus memory.
35914 - Reject malformed .onion addresses rather then passing them on as
35915 normal web requests.
35916 - Adapt patch from Adam Langley: fix possible memory leak in
35917 tor_lookup_hostname().
35918 - Initialize libevent later in the startup process, so the logs are
35919 already established by the time we start logging libevent warns.
35920 - Use correct errno on win32 if libevent fails.
35921 - Check and warn about known-bad/slow libevent versions.
35922 - Pay more attention to the ClientOnly config option.
35923 - Have torctl.in/tor.sh.in check for location of su binary (needed
35925 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
35926 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
35927 HttpProxyAuthenticator
35928 - Stop warning about sigpipes in the logs. We're going to
35929 pretend that getting these occasionally is normal and fine.
35930 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
35932 installer screens; and don't put stuff into StartupItems unless
35933 the user asks you to.
35934 - Require servers that use the default dirservers to have public IP
35935 addresses. We have too many servers that are configured with private
35936 IPs and their admins never notice the log entries complaining that
35937 their descriptors are being rejected.
35938 - Add OSX uninstall instructions. An actual uninstall script will
35942 Changes in version 0.1.0.8-rc - 2005-05-23
35944 - It turns out that kqueue on OS X 10.3.9 was causing kernel
35945 panics. Disable kqueue on all OS X Tors.
35946 - Fix RPM: remove duplicate line accidentally added to the rpm
35948 - Disable threads on openbsd too, since its gethostaddr is not
35950 - Tolerate libevent 0.8 since it still works, even though it's
35952 - Enable building on Red Hat 9.0 again.
35953 - Allow the middle hop of the testing circuit to be running any
35954 version, now that most of them have the bugfix to let them connect
35955 to unknown servers. This will allow reachability testing to work
35956 even when 0.0.9.7-0.0.9.9 become obsolete.
35957 - Handle relay cells with rh.length too large. This prevents
35958 a potential attack that could read arbitrary memory (maybe even
35959 keys) from the exit server's process.
35960 - We screwed up the dirport reachability testing when we don't yet
35961 have a cached version of the directory. Hopefully now fixed.
35962 - Clean up router_load_single_router() (used by the controller),
35963 so it doesn't seg fault on error.
35964 - Fix a minor memory leak when somebody establishes an introduction
35965 point at your Tor server.
35966 - If a socks connection ends because read fails, don't warn that
35967 you're not sending a socks reply back.
35970 - Add HttpProxyAuthenticator config option too, that works like
35971 the HttpsProxyAuthenticator config option.
35972 - Encode hashed controller passwords in hex instead of base64,
35973 to make it easier to write controllers.
35976 Changes in version 0.1.0.7-rc - 2005-05-17
35978 - Fix a bug in the OS X package installer that prevented it from
35979 installing on Tiger.
35980 - Fix a script bug in the OS X package installer that made it
35981 complain during installation.
35982 - Find libevent even if it's hiding in /usr/local/ and your
35983 CFLAGS and LDFLAGS don't tell you to look there.
35984 - Be able to link with libevent as a shared library (the default
35985 after 1.0d), even if it's hiding in /usr/local/lib and even
35986 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
35987 assuming you're running gcc. Otherwise fail and give a useful
35989 - Fix a bug in the RPM packager: set home directory for _tor to
35990 something more reasonable when first installing.
35991 - Free a minor amount of memory that is still reachable on exit.
35994 Changes in version 0.1.0.6-rc - 2005-05-14
35996 - Implement --disable-threads configure option. Disable threads on
35997 netbsd by default, because it appears to have no reentrant resolver
35999 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
36000 release (1.1) detects and disables kqueue if it's broken.
36001 - Append default exit policy before checking for implicit internal
36002 addresses. Now we don't log a bunch of complaints on startup
36003 when using the default exit policy.
36004 - Some people were putting "Address " in their torrc, and they had
36005 a buggy resolver that resolved " " to 0.0.0.0. Oops.
36006 - If DataDir is ~/.tor, and that expands to /.tor, then default to
36007 LOCALSTATEDIR/tor instead.
36008 - Fix fragmented-message bug in TorControl.py.
36009 - Resolve a minor bug which would prevent unreachable dirports
36010 from getting suppressed in the published descriptor.
36011 - When the controller gave us a new descriptor, we weren't resolving
36012 it immediately, so Tor would think its address was 0.0.0.0 until
36013 we fetched a new directory.
36014 - Fix an uppercase/lowercase case error in suppressing a bogus
36015 libevent warning on some Linuxes.
36018 - Begin scrubbing sensitive strings from logs by default. Turn off
36019 the config option SafeLogging if you need to do debugging.
36020 - Switch to a new buffer management algorithm, which tries to avoid
36021 reallocing and copying quite as much. In first tests it looks like
36022 it uses *more* memory on average, but less cpu.
36023 - First cut at support for "create-fast" cells. Clients can use
36024 these when extending to their first hop, since the TLS already
36025 provides forward secrecy and authentication. Not enabled on
36027 - When dirservers refuse a router descriptor, we now log its
36028 contactinfo, platform, and the poster's IP address.
36029 - Call tor_free_all instead of connections_free_all after forking, to
36030 save memory on systems that need to fork.
36031 - Whine at you if you're a server and you don't set your contactinfo.
36032 - Implement --verify-config command-line option to check if your torrc
36033 is valid without actually launching Tor.
36034 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
36035 rather than just rejecting it.
36038 Changes in version 0.1.0.5-rc - 2005-04-27
36040 - Stop trying to print a null pointer if an OR conn fails because
36041 we didn't like its cert.
36043 - Switch our internal buffers implementation to use a ring buffer,
36044 to hopefully improve performance for fast servers a lot.
36045 - Add HttpsProxyAuthenticator support (basic auth only), based
36046 on patch from Adam Langley.
36047 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
36048 the fast servers that have been joining lately.
36049 - Give hidden service accesses extra time on the first attempt,
36050 since 60 seconds is often only barely enough. This might improve
36052 - Improve performance for dirservers: stop re-parsing the whole
36053 directory every time you regenerate it.
36054 - Add more debugging info to help us find the weird dns freebsd
36055 pthreads bug; cleaner debug messages to help track future issues.
36058 Changes in version 0.0.9.9 - 2005-04-23
36059 o Bugfixes on 0.0.9.x:
36060 - If unofficial Tor clients connect and send weird TLS certs, our
36061 Tor server triggers an assert. This release contains a minimal
36062 backport from the broader fix that we put into 0.1.0.4-rc.
36065 Changes in version 0.1.0.4-rc - 2005-04-23
36067 - If unofficial Tor clients connect and send weird TLS certs, our
36068 Tor server triggers an assert. Stop asserting, and start handling
36069 TLS errors better in other situations too.
36070 - When the controller asks us to tell it about all the debug-level
36071 logs, it turns out we were generating debug-level logs while
36072 telling it about them, which turns into a bad loop. Now keep
36073 track of whether you're sending a debug log to the controller,
36074 and don't log when you are.
36075 - Fix the "postdescriptor" feature of the controller interface: on
36076 non-complete success, only say "done" once.
36078 - Clients are now willing to load balance over up to 2mB, not 1mB,
36079 of advertised bandwidth capacity.
36080 - Add a NoPublish config option, so you can be a server (e.g. for
36081 testing running Tor servers in other Tor networks) without
36082 publishing your descriptor to the primary dirservers.
36085 Changes in version 0.1.0.3-rc - 2005-04-08
36086 o Improvements on 0.1.0.2-rc:
36087 - Client now retries when streams end early for 'hibernating' or
36088 'resource limit' reasons, rather than failing them.
36089 - More automated handling for dirserver operators:
36090 - Automatically approve nodes running 0.1.0.2-rc or later,
36091 now that the the reachability detection stuff is working.
36092 - Now we allow two unverified servers with the same nickname
36093 but different keys. But if a nickname is verified, only that
36094 nickname+key are allowed.
36095 - If you're an authdirserver connecting to an address:port,
36096 and it's not the OR you were expecting, forget about that
36097 descriptor. If he *was* the one you were expecting, then forget
36098 about all other descriptors for that address:port.
36099 - Allow servers to publish descriptors from 12 hours in the future.
36100 Corollary: only whine about clock skew from the dirserver if
36101 he's a trusted dirserver (since now even verified servers could
36102 have quite wrong clocks).
36103 - Adjust maximum skew and age for rendezvous descriptors: let skew
36104 be 48 hours rather than 90 minutes.
36105 - Efficiency improvements:
36106 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
36107 it much faster to look up a circuit for each relay cell.
36108 - Remove most calls to assert_all_pending_dns_resolves_ok(),
36109 since they're eating our cpu on exit nodes.
36110 - Stop wasting time doing a case insensitive comparison for every
36111 dns name every time we do any lookup. Canonicalize the names to
36112 lowercase and be done with it.
36113 - Start sending 'truncated' cells back rather than destroy cells,
36114 if the circuit closes in front of you. This means we won't have
36115 to abandon partially built circuits.
36116 - Only warn once per nickname from add_nickname_list_to_smartlist
36117 per failure, so an entrynode or exitnode choice that's down won't
36119 - Put a note in the torrc about abuse potential with the default
36121 - Revise control spec and implementation to allow all log messages to
36122 be sent to controller with their severities intact (suggested by
36123 Matt Edman). Update TorControl to handle new log event types.
36124 - Provide better explanation messages when controller's POSTDESCRIPTOR
36126 - Stop putting nodename in the Platform string in server descriptors.
36127 It doesn't actually help, and it is confusing/upsetting some people.
36129 o Bugfixes on 0.1.0.2-rc:
36130 - We were printing the host mask wrong in exit policies in server
36131 descriptors. This isn't a critical bug though, since we were still
36132 obeying the exit policy internally.
36133 - Fix Tor when compiled with libevent but without pthreads: move
36134 connection_unregister() from _connection_free() to
36136 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
36137 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
36138 when we look through the connection array, we'll find any of the
36139 cpu/dnsworkers. This is no good.
36141 o Bugfixes on 0.0.9.8:
36142 - Fix possible bug on threading platforms (e.g. win32) which was
36143 leaking a file descriptor whenever a cpuworker or dnsworker died.
36144 - When using preferred entry or exit nodes, ignore whether the
36145 circuit wants uptime or capacity. They asked for the nodes, they
36147 - chdir() to your datadirectory at the *end* of the daemonize process,
36148 not the beginning. This was a problem because the first time you
36149 run tor, if your datadir isn't there, and you have runasdaemon set
36150 to 1, it will try to chdir to it before it tries to create it. Oops.
36151 - Handle changed router status correctly when dirserver reloads
36152 fingerprint file. We used to be dropping all unverified descriptors
36153 right then. The bug was hidden because we would immediately
36154 fetch a directory from another dirserver, which would include the
36155 descriptors we just dropped.
36156 - When we're connecting to an OR and he's got a different nickname/key
36157 than we were expecting, only complain loudly if we're an OP or a
36158 dirserver. Complaining loudly to the OR admins just confuses them.
36159 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
36160 artificially capped at 500kB.
36163 Changes in version 0.0.9.8 - 2005-04-07
36164 o Bugfixes on 0.0.9.x:
36165 - We have a bug that I haven't found yet. Sometimes, very rarely,
36166 cpuworkers get stuck in the 'busy' state, even though the cpuworker
36167 thinks of itself as idle. This meant that no new circuits ever got
36168 established. Here's a workaround to kill any cpuworker that's been
36169 busy for more than 100 seconds.
36172 Changes in version 0.1.0.2-rc - 2005-04-01
36173 o Bugfixes on 0.1.0.1-rc:
36174 - Fixes on reachability detection:
36175 - Don't check for reachability while hibernating.
36176 - If ORPort is reachable but DirPort isn't, still publish the
36177 descriptor, but zero out DirPort until it's found reachable.
36178 - When building testing circs for ORPort testing, use only
36179 high-bandwidth nodes, so fewer circuits fail.
36180 - Complain about unreachable ORPort separately from unreachable
36181 DirPort, so the user knows what's going on.
36182 - Make sure we only conclude ORPort reachability if we didn't
36183 initiate the conn. Otherwise we could falsely conclude that
36184 we're reachable just because we connected to the guy earlier
36185 and he used that same pipe to extend to us.
36186 - Authdirservers shouldn't do ORPort reachability detection,
36187 since they're in clique mode, so it will be rare to find a
36188 server not already connected to them.
36189 - When building testing circuits, always pick middle hops running
36190 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
36191 bug. (This is a kludge; it will go away when 0.0.9.x becomes
36193 - When we decide we're reachable, actually publish our descriptor
36195 - Fix bug in redirectstream in the controller.
36196 - Fix the state descriptor strings so logs don't claim edge streams
36197 are in a different state than they actually are.
36198 - Use recent libevent features when possible (this only really affects
36199 win32 and osx right now, because the new libevent with these
36200 features hasn't been released yet). Add code to suppress spurious
36202 - Prevent possible segfault in connection_close_unattached_ap().
36203 - Fix newlines on torrc in win32.
36204 - Improve error msgs when tor-resolve fails.
36206 o Improvements on 0.0.9.x:
36207 - New experimental script tor/contrib/ExerciseServer.py (needs more
36208 work) that uses the controller interface to build circuits and
36209 fetch pages over them. This will help us bootstrap servers that
36210 have lots of capacity but haven't noticed it yet.
36211 - New experimental script tor/contrib/PathDemo.py (needs more work)
36212 that uses the controller interface to let you choose whole paths
36214 "<hostname>.<path,separated by dots>.<length of path>.path"
36215 - When we've connected to an OR and handshaked but didn't like
36216 the result, we were closing the conn without sending destroy
36217 cells back for pending circuits. Now send those destroys.
36220 Changes in version 0.0.9.7 - 2005-04-01
36221 o Bugfixes on 0.0.9.x:
36222 - Fix another race crash bug (thanks to Glenn Fink for reporting).
36223 - Compare identity to identity, not to nickname, when extending to
36224 a router not already in the directory. This was preventing us from
36225 extending to unknown routers. Oops.
36226 - Make sure to create OS X Tor user in <500 range, so we aren't
36227 creating actual system users.
36228 - Note where connection-that-hasn't-sent-end was marked, and fix
36229 a few really loud instances of this harmless bug (it's fixed more
36233 Changes in version 0.1.0.1-rc - 2005-03-28
36235 - Add reachability testing. Your Tor server will automatically try
36236 to see if its ORPort and DirPort are reachable from the outside,
36237 and it won't upload its descriptor until it decides they are.
36238 - Handle unavailable hidden services better. Handle slow or busy
36239 hidden services better.
36240 - Add support for CONNECTing through https proxies, with "HttpsProxy"
36242 - New exit policy: accept most low-numbered ports, rather than
36243 rejecting most low-numbered ports.
36244 - More Tor controller support (still experimental). See
36245 http://tor.eff.org/doc/control-spec.txt for all the new features,
36246 including signals to emulate unix signals from any platform;
36247 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
36248 closestream; closecircuit; etc.
36249 - Make nt services work and start on startup on win32 (based on
36250 patch by Matt Edman).
36251 - Add a new AddressMap config directive to rewrite incoming socks
36252 addresses. This lets you, for example, declare an implicit
36253 required exit node for certain sites.
36254 - Add a new TrackHostExits config directive to trigger addressmaps
36255 for certain incoming socks addresses -- for sites that break when
36256 your exit keeps changing (based on patch by Mike Perry).
36257 - Redo the client-side dns cache so it's just an addressmap too.
36258 - Notice when our IP changes, and reset stats/uptime/reachability.
36259 - When an application is using socks5, give him the whole variety of
36260 potential socks5 responses (connect refused, host unreachable, etc),
36261 rather than just "success" or "failure".
36262 - A more sane version numbering system. See
36263 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
36264 - New contributed script "exitlist": a simple python script to
36265 parse directories and find Tor nodes that exit to listed
36267 - New contributed script "privoxy-tor-toggle" to toggle whether
36268 Privoxy uses Tor. Seems to be configured for Debian by default.
36269 - Report HTTP reasons to client when getting a response from directory
36270 servers -- so you can actually know what went wrong.
36271 - New config option MaxAdvertisedBandwidth which lets you advertise
36272 a low bandwidthrate (to not attract as many circuits) while still
36273 allowing a higher bandwidthrate in reality.
36275 o Robustness/stability fixes:
36276 - Make Tor use Niels Provos's libevent instead of its current
36277 poll-but-sometimes-select mess. This will let us use faster async
36278 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
36280 - pthread support now too. This was forced because when we forked,
36281 we ended up wasting a lot of duplicate ram over time. Also switch
36282 to foo_r versions of some library calls to allow reentry and
36284 - Better handling for heterogeneous / unreliable nodes:
36285 - Annotate circuits w/ whether they aim to contain high uptime nodes
36286 and/or high capacity nodes. When building circuits, choose
36288 - This means that every single node in an intro rend circuit,
36289 not just the last one, will have a minimum uptime.
36290 - New config option LongLivedPorts to indicate application streams
36291 that will want high uptime circuits.
36292 - Servers reset uptime when a dir fetch entirely fails. This
36293 hopefully reflects stability of the server's network connectivity.
36294 - If somebody starts his tor server in Jan 2004 and then fixes his
36295 clock, don't make his published uptime be a year.
36296 - Reset published uptime when you wake up from hibernation.
36297 - Introduce a notion of 'internal' circs, which are chosen without
36298 regard to the exit policy of the last hop. Intro and rendezvous
36299 circs must be internal circs, to avoid leaking information. Resolve
36300 and connect streams can use internal circs if they want.
36301 - New circuit pooling algorithm: make sure to have enough circs around
36302 to satisfy any predicted ports, and also make sure to have 2 internal
36303 circs around if we've required internal circs lately (and with high
36304 uptime if we've seen that lately too).
36305 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
36306 which describes how often we retry making new circuits if current
36307 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
36308 how long we're willing to make use of an already-dirty circuit.
36309 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
36310 circ as necessary, if there are any completed ones lying around
36311 when we try to launch one.
36312 - Make hidden services try to establish a rendezvous for 30 seconds,
36313 rather than for n (where n=3) attempts to build a circuit.
36314 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
36315 "ShutdownWaitLength".
36316 - Try to be more zealous about calling connection_edge_end when
36317 things go bad with edge conns in connection.c.
36318 - Revise tor-spec to add more/better stream end reasons.
36319 - Revise all calls to connection_edge_end to avoid sending "misc",
36320 and to take errno into account where possible.
36323 - Fix a race condition that can trigger an assert, when we have a
36324 pending create cell and an OR connection fails right then.
36325 - Fix several double-mark-for-close bugs, e.g. where we were finding
36326 a conn for a cell even if that conn is already marked for close.
36327 - Make sequence of log messages when starting on win32 with no config
36328 file more reasonable.
36329 - When choosing an exit node for a new non-internal circ, don't take
36330 into account whether it'll be useful for any pending x.onion
36331 addresses -- it won't.
36332 - Turn addr_policy_compare from a tristate to a quadstate; this should
36333 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
36334 for google.com" problem.
36335 - Make "platform" string in descriptor more accurate for Win32 servers,
36336 so it's not just "unknown platform".
36337 - Fix an edge case in parsing config options (thanks weasel).
36338 If they say "--" on the commandline, it's not an option.
36339 - Reject odd-looking addresses at the client (e.g. addresses that
36340 contain a colon), rather than having the server drop them because
36342 - tor-resolve requests were ignoring .exit if there was a working circuit
36343 they could use instead.
36344 - REUSEADDR on normal platforms means you can rebind to the port
36345 right after somebody else has let it go. But REUSEADDR on win32
36346 means to let you bind to the port _even when somebody else
36347 already has it bound_! So, don't do that on Win32.
36348 - Change version parsing logic: a version is "obsolete" if it is not
36349 recommended and (1) there is a newer recommended version in the
36350 same series, or (2) there are no recommended versions in the same
36351 series, but there are some recommended versions in a newer series.
36352 A version is "new" if it is newer than any recommended version in
36354 - Stop most cases of hanging up on a socks connection without sending
36358 - Require BandwidthRate to be at least 20kB/s for servers.
36359 - When a dirserver causes you to give a warn, mention which dirserver
36361 - New config option DirAllowPrivateAddresses for authdirservers.
36362 Now by default they refuse router descriptors that have non-IP or
36363 private-IP addresses.
36364 - Stop publishing socksport in the directory, since it's not
36365 actually meant to be public. For compatibility, publish a 0 there
36367 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
36368 smart" value, that is low for servers and high for clients.
36369 - If our clock jumps forward by 100 seconds or more, assume something
36370 has gone wrong with our network and abandon all not-yet-used circs.
36371 - Warn when exit policy implicitly allows local addresses.
36372 - If we get an incredibly skewed timestamp from a dirserver mirror
36373 that isn't a verified OR, don't warn -- it's probably him that's
36375 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
36376 cookies to disk and doesn't log each web request to disk. (Thanks
36377 to Brett Carrington for pointing this out.)
36378 - When a client asks us for a dir mirror and we don't have one,
36379 launch an attempt to get a fresh one.
36380 - If we're hibernating and we get a SIGINT, exit immediately.
36381 - Add --with-dmalloc ./configure option, to track memory leaks.
36382 - And try to free all memory on closing, so we can detect what
36384 - Cache local dns resolves correctly even when they're .exit
36386 - Give a better warning when some other server advertises an
36387 ORPort that is actually an apache running ssl.
36388 - Add "opt hibernating 1" to server descriptor to make it clearer
36389 whether the server is hibernating.
36392 Changes in version 0.0.9.6 - 2005-03-24
36393 o Bugfixes on 0.0.9.x (crashes and asserts):
36394 - Add new end stream reasons to maintenance branch. Fix bug where
36395 reason (8) could trigger an assert. Prevent bug from recurring.
36396 - Apparently win32 stat wants paths to not end with a slash.
36397 - Fix assert triggers in assert_cpath_layer_ok(), where we were
36398 blowing away the circuit that conn->cpath_layer points to, then
36399 checking to see if the circ is well-formed. Backport check to make
36400 sure we dont use the cpath on a closed connection.
36401 - Prevent circuit_resume_edge_reading_helper() from trying to package
36402 inbufs for marked-for-close streams.
36403 - Don't crash on hup if your options->address has become unresolvable.
36404 - Some systems (like OS X) sometimes accept() a connection and tell
36405 you the remote host is 0.0.0.0:0. If this happens, due to some
36406 other mis-features, we get confused; so refuse the conn for now.
36408 o Bugfixes on 0.0.9.x (other):
36409 - Fix harmless but scary "Unrecognized content encoding" warn message.
36410 - Add new stream error reason: TORPROTOCOL reason means "you are not
36411 speaking a version of Tor I understand; say bye-bye to your stream."
36412 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
36413 into the future, now that we are more tolerant of skew. This
36414 resolves a bug where a Tor server would refuse to cache a directory
36415 because all the directories it gets are too far in the future;
36416 yet the Tor server never logs any complaints about clock skew.
36417 - Mac packaging magic: make man pages useable, and do not overwrite
36418 existing torrc files.
36419 - Make OS X log happily to /var/log/tor/tor.log
36422 Changes in version 0.0.9.5 - 2005-02-22
36423 o Bugfixes on 0.0.9.x:
36424 - Fix an assert race at exit nodes when resolve requests fail.
36425 - Stop picking unverified dir mirrors--it only leads to misery.
36426 - Patch from Matt Edman to make NT services work better. Service
36427 support is still not compiled into the executable by default.
36428 - Patch from Dmitri Bely so the Tor service runs better under
36429 the win32 SYSTEM account.
36430 - Make tor-resolve actually work (?) on Win32.
36431 - Fix a sign bug when getrlimit claims to have 4+ billion
36432 file descriptors available.
36433 - Stop refusing to start when bandwidthburst == bandwidthrate.
36434 - When create cells have been on the onion queue more than five
36435 seconds, just send back a destroy and take them off the list.
36438 Changes in version 0.0.9.4 - 2005-02-03
36439 o Bugfixes on 0.0.9:
36440 - Fix an assert bug that took down most of our servers: when
36441 a server claims to have 1 GB of bandwidthburst, don't
36443 - Don't crash as badly if we have spawned the max allowed number
36444 of dnsworkers, or we're out of file descriptors.
36445 - Block more file-sharing ports in the default exit policy.
36446 - MaxConn is now automatically set to the hard limit of max
36447 file descriptors we're allowed (ulimit -n), minus a few for
36449 - Give a clearer message when servers need to raise their
36450 ulimit -n when they start running out of file descriptors.
36451 - SGI Compatibility patches from Jan Schaumann.
36452 - Tolerate a corrupt cached directory better.
36453 - When a dirserver hasn't approved your server, list which one.
36454 - Go into soft hibernation after 95% of the bandwidth is used,
36455 not 99%. This is especially important for daily hibernators who
36456 have a small accounting max. Hopefully it will result in fewer
36457 cut connections when the hard hibernation starts.
36458 - Load-balance better when using servers that claim more than
36459 800kB/s of capacity.
36460 - Make NT services work (experimental, only used if compiled in).
36463 Changes in version 0.0.9.3 - 2005-01-21
36464 o Bugfixes on 0.0.9:
36465 - Backport the cpu use fixes from main branch, so busy servers won't
36466 need as much processor time.
36467 - Work better when we go offline and then come back, or when we
36468 run Tor at boot before the network is up. We do this by
36469 optimistically trying to fetch a new directory whenever an
36470 application request comes in and we think we're offline -- the
36471 human is hopefully a good measure of when the network is back.
36472 - Backport some minimal hidserv bugfixes: keep rend circuits open as
36473 long as you keep using them; actually publish hidserv descriptors
36474 shortly after they change, rather than waiting 20-40 minutes.
36475 - Enable Mac startup script by default.
36476 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
36477 - When you update AllowUnverifiedNodes or FirewallPorts via the
36478 controller's setconf feature, we were always appending, never
36480 - When you update HiddenServiceDir via setconf, it was screwing up
36481 the order of reading the lines, making it fail.
36482 - Do not rewrite a cached directory back to the cache; otherwise we
36483 will think it is recent and not fetch a newer one on startup.
36484 - Workaround for webservers that lie about Content-Encoding: Tor
36485 now tries to autodetect compressed directories and compression
36486 itself. This lets us Proxypass dir fetches through apache.
36489 Changes in version 0.0.9.2 - 2005-01-04
36490 o Bugfixes on 0.0.9 (crashes and asserts):
36491 - Fix an assert on startup when the disk is full and you're logging
36493 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
36494 style address, then we'd crash.
36495 - Fix an assert trigger when the running-routers string we get from
36496 a dirserver is broken.
36497 - Make worker threads start and run on win32. Now win32 servers
36499 - Bandaid (not actually fix, but now it doesn't crash) an assert
36500 where the dns worker dies mysteriously and the main Tor process
36501 doesn't remember anything about the address it was resolving.
36503 o Bugfixes on 0.0.9 (Win32):
36504 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
36505 name out of the warning/assert messages.
36506 - Fix a superficial "unhandled error on read" bug on win32.
36507 - The win32 installer no longer requires a click-through for our
36508 license, since our Free Software license grants rights but does not
36510 - Win32: When connecting to a dirserver fails, try another one
36511 immediately. (This was already working for non-win32 Tors.)
36512 - Stop trying to parse $HOME on win32 when hunting for default
36514 - Make tor-resolve.c work on win32 by calling network_init().
36516 o Bugfixes on 0.0.9 (other):
36517 - Make 0.0.9.x build on Solaris again.
36518 - Due to a fencepost error, we were blowing away the \n when reporting
36519 confvalue items in the controller. So asking for multiple config
36520 values at once couldn't work.
36521 - When listing circuits that are pending on an opening OR connection,
36522 if we're an OR we were listing circuits that *end* at us as
36523 being pending on every listener, dns/cpu worker, etc. Stop that.
36524 - Dirservers were failing to create 'running-routers' or 'directory'
36525 strings if we had more than some threshold of routers. Fix them so
36526 they can handle any number of routers.
36527 - Fix a superficial "Duplicate mark for close" bug.
36528 - Stop checking for clock skew for OR connections, even for servers.
36529 - Fix a fencepost error that was chopping off the last letter of any
36530 nickname that is the maximum allowed nickname length.
36531 - Update URLs in log messages so they point to the new website.
36532 - Fix a potential problem in mangling server private keys while
36533 writing to disk (not triggered yet, as far as we know).
36534 - Include the licenses for other free software we include in Tor,
36535 now that we're shipping binary distributions more regularly.
36538 Changes in version 0.0.9.1 - 2004-12-15
36539 o Bugfixes on 0.0.9:
36540 - Make hibernation actually work.
36541 - Make HashedControlPassword config option work.
36542 - When we're reporting event circuit status to a controller,
36543 don't use the stream status code.
36546 Changes in version 0.0.9 - 2004-12-12
36548 - Clean up manpage and torrc.sample file.
36549 - Clean up severities and text of log warnings.
36551 - Make servers trigger an assert when they enter hibernation.
36554 Changes in version 0.0.9rc7 - 2004-12-08
36555 o Bugfixes on 0.0.9rc:
36556 - Fix a stack-trashing crash when an exit node begins hibernating.
36557 - Avoid looking at unallocated memory while considering which
36558 ports we need to build circuits to cover.
36559 - Stop a sigpipe: when an 'end' cell races with eof from the app,
36560 we shouldn't hold-open-until-flush if the eof arrived first.
36561 - Fix a bug with init_cookie_authentication() in the controller.
36562 - When recommending new-format log lines, if the upper bound is
36563 LOG_ERR, leave it implicit.
36565 o Bugfixes on 0.0.8.1:
36566 - Fix a whole slew of memory leaks.
36567 - Fix isspace() and friends so they still make Solaris happy
36568 but also so they don't trigger asserts on win32.
36569 - Fix parse_iso_time on platforms without strptime (eg win32).
36570 - win32: tolerate extra "readable" events better.
36571 - win32: when being multithreaded, leave parent fdarray open.
36572 - Make unit tests work on win32.
36575 Changes in version 0.0.9rc6 - 2004-12-06
36576 o Bugfixes on 0.0.9pre:
36577 - Clean up some more integer underflow opportunities (not exploitable
36579 - While hibernating, hup should not regrow our listeners.
36580 - Send an end to the streams we close when we hibernate, rather
36581 than just chopping them off.
36582 - React to eof immediately on non-open edge connections.
36584 o Bugfixes on 0.0.8.1:
36585 - Calculate timeout for waiting for a connected cell from the time
36586 we sent the begin cell, not from the time the stream started. If
36587 it took a long time to establish the circuit, we would time out
36588 right after sending the begin cell.
36589 - Fix router_compare_addr_to_addr_policy: it was not treating a port
36590 of * as always matching, so we were picking reject *:* nodes as
36591 exit nodes too. Oops.
36594 - New circuit building strategy: keep a list of ports that we've
36595 used in the past 6 hours, and always try to have 2 circuits open
36596 or on the way that will handle each such port. Seed us with port
36597 80 so web users won't complain that Tor is "slow to start up".
36598 - Make kill -USR1 dump more useful stats about circuits.
36599 - When warning about retrying or giving up, print the address, so
36600 the user knows which one it's talking about.
36601 - If you haven't used a clean circuit in an hour, throw it away,
36602 just to be on the safe side. (This means after 6 hours a totally
36603 unused Tor client will have no circuits open.)
36606 Changes in version 0.0.9rc5 - 2004-12-01
36607 o Bugfixes on 0.0.8.1:
36608 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
36609 - Let resolve conns retry/expire also, rather than sticking around
36611 - If we are using select, make sure we stay within FD_SETSIZE.
36613 o Bugfixes on 0.0.9pre:
36614 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
36615 but doesn't seem to be currently; thanks to Ilja van Sprundel for
36617 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
36618 instead. Impose minima and maxima for all *Period options; impose
36619 even tighter maxima for fetching if we are a caching dirserver.
36620 Clip rather than rejecting.
36621 - Fetch cached running-routers from servers that serve it (that is,
36622 authdirservers and servers running 0.0.9rc5-cvs or later.)
36625 - Accept *:706 (silc) in default exit policy.
36626 - Implement new versioning format for post 0.1.
36627 - Support "foo.nickname.exit" addresses, to let Alice request the
36628 address "foo" as viewed by exit node "nickname". Based on a patch
36630 - Make tor --version --version dump the cvs Id of every file.
36633 Changes in version 0.0.9rc4 - 2004-11-28
36634 o Bugfixes on 0.0.8.1:
36635 - Make windows sockets actually non-blocking (oops), and handle
36636 win32 socket errors better.
36638 o Bugfixes on 0.0.9rc1:
36639 - Actually catch the -USR2 signal.
36642 Changes in version 0.0.9rc3 - 2004-11-25
36643 o Bugfixes on 0.0.8.1:
36644 - Flush the log file descriptor after we print "Tor opening log file",
36645 so we don't see those messages days later.
36647 o Bugfixes on 0.0.9rc1:
36648 - Make tor-resolve work again.
36649 - Avoid infinite loop in tor-resolve if tor hangs up on it.
36650 - Fix an assert trigger for clients/servers handling resolves.
36653 Changes in version 0.0.9rc2 - 2004-11-24
36654 o Bugfixes on 0.0.9rc1:
36655 - I broke socks5 support while fixing the eof bug.
36656 - Allow unitless bandwidths and intervals; they default to bytes
36658 - New servers don't start out hibernating; they are active until
36659 they run out of bytes, so they have a better estimate of how
36660 long it takes, and so their operators can know they're working.
36663 Changes in version 0.0.9rc1 - 2004-11-23
36664 o Bugfixes on 0.0.8.1:
36665 - Finally fix a bug that's been plaguing us for a year:
36666 With high load, circuit package window was reaching 0. Whenever
36667 we got a circuit-level sendme, we were reading a lot on each
36668 socket, but only writing out a bit. So we would eventually reach
36669 eof. This would be noticed and acted on even when there were still
36670 bytes sitting in the inbuf.
36671 - When poll() is interrupted, we shouldn't believe the revents values.
36673 o Bugfixes on 0.0.9pre6:
36674 - Fix hibernate bug that caused pre6 to be broken.
36675 - Don't keep rephist info for routers that haven't had activity for
36676 24 hours. (This matters now that clients have keys, since we track
36678 - Never call close_temp_logs while validating log options.
36679 - Fix backslash-escaping on tor.sh.in and torctl.in.
36682 - Implement weekly/monthly/daily accounting: now you specify your
36683 hibernation properties by
36684 AccountingMax N bytes|KB|MB|GB|TB
36685 AccountingStart day|week|month [day] HH:MM
36686 Defaults to "month 1 0:00".
36687 - Let bandwidth and interval config options be specified as 5 bytes,
36688 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
36689 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
36690 get back to normal.)
36691 - If your requested entry or exit node has advertised bandwidth 0,
36693 - Be more greedy about filling up relay cells -- we try reading again
36694 once we've processed the stuff we read, in case enough has arrived
36695 to fill the last cell completely.
36696 - Apply NT service patch from Osamu Fujino. Still needs more work.
36699 Changes in version 0.0.9pre6 - 2004-11-15
36700 o Bugfixes on 0.0.8.1:
36701 - Fix assert failure on malformed socks4a requests.
36702 - Use identity comparison, not nickname comparison, to choose which
36703 half of circuit-ID-space each side gets to use. This is needed
36704 because sometimes we think of a router as a nickname, and sometimes
36705 as a hex ID, and we can't predict what the other side will do.
36706 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
36707 write() call will fail and we handle it there.
36708 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
36709 and smartlist_len, which are two major profiling offenders.
36711 o Bugfixes on 0.0.9pre5:
36712 - Fix a bug in read_all that was corrupting config files on windows.
36713 - When we're raising the max number of open file descriptors to
36714 'unlimited', don't log that we just raised it to '-1'.
36715 - Include event code with events, as required by control-spec.txt.
36716 - Don't give a fingerprint when clients do --list-fingerprint:
36717 it's misleading, because it will never be the same again.
36718 - Stop using strlcpy in tor_strndup, since it was slowing us
36720 - Remove warn on startup about missing cached-directory file.
36721 - Make kill -USR1 work again.
36722 - Hibernate if we start tor during the "wait for wakeup-time" phase
36723 of an accounting interval. Log our hibernation plans better.
36724 - Authoritative dirservers now also cache their directory, so they
36725 have it on start-up.
36728 - Fetch running-routers; cache running-routers; compress
36729 running-routers; serve compressed running-routers.z
36730 - Add NSI installer script contributed by J Doe.
36731 - Commit VC6 and VC7 workspace/project files.
36732 - Commit a tor.spec for making RPM files, with help from jbash.
36733 - Add contrib/torctl.in contributed by Glenn Fink.
36734 - Implement the control-spec's SAVECONF command, to write your
36735 configuration to torrc.
36736 - Get cookie authentication for the controller closer to working.
36737 - Include control-spec.txt in the tarball.
36738 - When set_conf changes our server descriptor, upload a new copy.
36739 But don't upload it too often if there are frequent changes.
36740 - Document authentication config in man page, and document signals
36742 - Clean up confusing parts of man page and torrc.sample.
36743 - Make expand_filename handle ~ and ~username.
36744 - Use autoconf to enable largefile support where necessary. Use
36745 ftello where available, since ftell can fail at 2GB.
36746 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
36747 log more informatively.
36748 - Give a slightly more useful output for "tor -h".
36749 - Refuse application socks connections to port 0.
36750 - Check clock skew for verified servers, but allow unverified
36751 servers and clients to have any clock skew.
36752 - Break DirFetchPostPeriod into:
36753 - DirFetchPeriod for fetching full directory,
36754 - StatusFetchPeriod for fetching running-routers,
36755 - DirPostPeriod for posting server descriptor,
36756 - RendPostPeriod for posting hidden service descriptors.
36757 - Make sure the hidden service descriptors are at a random offset
36758 from each other, to hinder linkability.
36761 Changes in version 0.0.9pre5 - 2004-11-09
36762 o Bugfixes on 0.0.9pre4:
36763 - Fix a seg fault in unit tests (doesn't affect main program).
36764 - Fix an assert bug where a hidden service provider would fail if
36765 the first hop of his rendezvous circuit was down.
36766 - Hidden service operators now correctly handle version 1 style
36767 INTRODUCE1 cells (nobody generates them still, so not a critical
36769 - If do_hup fails, actually notice.
36770 - Handle more errnos from accept() without closing the listener.
36771 Some OpenBSD machines were closing their listeners because
36772 they ran out of file descriptors.
36773 - Send resolve cells to exit routers that are running a new
36774 enough version of the resolve code to work right.
36775 - Better handling of winsock includes on non-MSV win32 compilers.
36776 - Some people had wrapped their tor client/server in a script
36777 that would restart it whenever it died. This did not play well
36778 with our "shut down if your version is obsolete" code. Now people
36779 don't fetch a new directory if their local cached version is
36781 - Make our autogen.sh work on ksh as well as bash.
36784 - Hibernation: New config option "AccountingMaxKB" lets you
36785 set how many KBytes per month you want to allow your server to
36786 consume. Rather than spreading those bytes out evenly over the
36787 month, we instead hibernate for some of the month and pop up
36788 at a deterministic time, work until the bytes are consumed, then
36789 hibernate again. Config option "MonthlyAccountingStart" lets you
36790 specify which day of the month your billing cycle starts on.
36791 - Control interface: a separate program can now talk to your
36792 client/server over a socket, and get/set config options, receive
36793 notifications of circuits and streams starting/finishing/dying,
36794 bandwidth used, etc. The next step is to get some GUIs working.
36795 Let us know if you want to help out. See doc/control-spec.txt .
36796 - Ship a contrib/tor-control.py as an example script to interact
36797 with the control port.
36798 - "tor --hash-password zzyxz" will output a salted password for
36799 use in authenticating to the control interface.
36800 - New log format in config:
36801 "Log minsev[-maxsev] stdout|stderr|syslog" or
36802 "Log minsev[-maxsev] file /var/foo"
36805 - DirPolicy config option, to let people reject incoming addresses
36806 from their dirserver.
36807 - "tor --list-fingerprint" will list your identity key fingerprint
36809 - Add "pass" target for RedirectExit, to make it easier to break
36810 out of a sequence of RedirectExit rules.
36811 - Clients now generate a TLS cert too, in preparation for having
36812 them act more like real nodes.
36813 - Ship src/win32/ in the tarball, so people can use it to build.
36814 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
36816 - New "router-status" line in directory, to better bind each verified
36817 nickname to its identity key.
36818 - Deprecate unofficial config option abbreviations, and abbreviations
36819 not on the command line.
36820 - Add a pure-C tor-resolve implementation.
36821 - Use getrlimit and friends to ensure we can reach MaxConn (currently
36822 1024) file descriptors.
36824 o Code security improvements, inspired by Ilja:
36825 - Replace sprintf with snprintf. (I think they were all safe, but
36827 - Replace strcpy/strncpy with strlcpy in more places.
36828 - Avoid strcat; use snprintf or strlcat instead.
36829 - snprintf wrapper with consistent (though not C99) overflow behavior.
36832 Changes in version 0.0.9pre4 - 2004-10-17
36833 o Bugfixes on 0.0.9pre3:
36834 - If the server doesn't specify an exit policy, use the real default
36835 exit policy, not reject *:*.
36836 - Ignore fascistfirewall when uploading/downloading hidden service
36837 descriptors, since we go through Tor for those; and when using
36838 an HttpProxy, since we assume it can reach them all.
36839 - When looking for an authoritative dirserver, use only the ones
36840 configured at boot. Don't bother looking in the directory.
36841 - The rest of the fix for get_default_conf_file() on older win32.
36842 - Make 'Routerfile' config option obsolete.
36845 - New 'MyFamily nick1,...' config option for a server to
36846 specify other servers that shouldn't be used in the same circuit
36847 with it. Only believed if nick1 also specifies us.
36848 - New 'NodeFamily nick1,nick2,...' config option for a client to
36849 specify nodes that it doesn't want to use in the same circuit.
36850 - New 'Redirectexit pattern address:port' config option for a
36851 server to redirect exit connections, e.g. to a local squid.
36854 Changes in version 0.0.9pre3 - 2004-10-13
36855 o Bugfixes on 0.0.8.1:
36856 - Better torrc example lines for dirbindaddress and orbindaddress.
36857 - Improved bounds checking on parsed ints (e.g. config options and
36858 the ones we find in directories.)
36859 - Better handling of size_t vs int, so we're more robust on 64
36861 - Fix the rest of the bug where a newly started OR would appear
36862 as unverified even after we've added his fingerprint and hupped
36864 - Fix a bug from 0.0.7: when read() failed on a stream, we would
36865 close it without sending back an end. So 'connection refused'
36866 would simply be ignored and the user would get no response.
36868 o Bugfixes on 0.0.9pre2:
36869 - Serving the cached-on-disk directory to people is bad. We now
36870 provide no directory until we've fetched a fresh one.
36871 - Workaround for bug on windows where cached-directories get crlf
36873 - Make get_default_conf_file() work on older windows too.
36874 - If we write a *:* exit policy line in the descriptor, don't write
36875 any more exit policy lines.
36878 - Use only 0.0.9pre1 and later servers for resolve cells.
36879 - Make the dirservers file obsolete.
36880 - Include a dir-signing-key token in directories to tell the
36881 parsing entity which key is being used to sign.
36882 - Remove the built-in bulky default dirservers string.
36883 - New config option "Dirserver %s:%d [fingerprint]", which can be
36884 repeated as many times as needed. If no dirservers specified,
36885 default to moria1,moria2,tor26.
36886 - Make moria2 advertise a dirport of 80, so people behind firewalls
36887 will be able to get a directory.
36888 - Http proxy support
36889 - Dirservers translate requests for http://%s:%d/x to /x
36890 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
36891 be routed through this host.
36892 - Clients ask for /tor/x rather than /x for new enough dirservers.
36893 This way we can one day coexist peacefully with apache.
36894 - Clients specify a "Host: %s%d" http header, to be compatible
36895 with more proxies, and so running squid on an exit node can work.
36898 Changes in version 0.0.8.1 - 2004-10-13
36900 - Fix a seg fault that can be triggered remotely for Tor
36901 clients/servers with an open dirport.
36902 - Fix a rare assert trigger, where routerinfos for entries in
36903 our cpath would expire while we're building the path.
36904 - Fix a bug in OutboundBindAddress so it (hopefully) works.
36905 - Fix a rare seg fault for people running hidden services on
36906 intermittent connections.
36907 - Fix a bug in parsing opt keywords with objects.
36908 - Fix a stale pointer assert bug when a stream detaches and
36910 - Fix a string format vulnerability (probably not exploitable)
36911 in reporting stats locally.
36912 - Fix an assert trigger: sometimes launching circuits can fail
36913 immediately, e.g. because too many circuits have failed recently.
36914 - Fix a compile warning on 64 bit platforms.
36917 Changes in version 0.0.9pre2 - 2004-10-03
36919 - Make fetching a cached directory work for 64-bit platforms too.
36920 - Make zlib.h a required header, not an optional header.
36923 Changes in version 0.0.9pre1 - 2004-10-01
36925 - Stop using separate defaults for no-config-file and
36926 empty-config-file. Now you have to explicitly turn off SocksPort,
36927 if you don't want it open.
36928 - Fix a bug in OutboundBindAddress so it (hopefully) works.
36929 - Improve man page to mention more of the 0.0.8 features.
36930 - Fix a rare seg fault for people running hidden services on
36931 intermittent connections.
36932 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
36934 - Fix more dns related bugs: send back resolve_failed and end cells
36935 more reliably when the resolve fails, rather than closing the
36936 circuit and then trying to send the cell. Also attach dummy resolve
36937 connections to a circuit *before* calling dns_resolve(), to fix
36938 a bug where cached answers would never be sent in RESOLVED cells.
36939 - When we run out of disk space, or other log writing error, don't
36940 crash. Just stop logging to that log and continue.
36941 - We were starting to daemonize before we opened our logs, so if
36942 there were any problems opening logs, we would complain to stderr,
36943 which wouldn't work, and then mysteriously exit.
36944 - Fix a rare bug where sometimes a verified OR would connect to us
36945 before he'd uploaded his descriptor, which would cause us to
36946 assign conn->nickname as though he's unverified. Now we look through
36947 the fingerprint list to see if he's there.
36948 - Fix a rare assert trigger, where routerinfos for entries in
36949 our cpath would expire while we're building the path.
36952 - Clients can ask dirservers for /dir.z to get a compressed version
36953 of the directory. Only works for servers running 0.0.9, of course.
36954 - Make clients cache directories and use them to seed their router
36955 lists at startup. This means clients have a datadir again.
36956 - Configuration infrastructure support for warning on obsolete
36958 - Respond to content-encoding headers by trying to uncompress as
36960 - Reply with a deflated directory when a client asks for "dir.z".
36961 We could use allow-encodings instead, but allow-encodings isn't
36962 specified in HTTP 1.0.
36963 - Raise the max dns workers from 50 to 100.
36964 - Discourage people from setting their dirfetchpostperiod more often
36965 than once per minute.
36966 - Protect dirservers from overzealous descriptor uploading -- wait
36967 10 seconds after directory gets dirty, before regenerating.
36970 Changes in version 0.0.8 - 2004-08-25
36971 o Port it to SunOS 5.9 / Athena
36974 Changes in version 0.0.8rc2 - 2004-08-20
36975 o Make it compile on cygwin again.
36976 o When picking unverified routers, skip those with low uptime and/or
36977 low bandwidth, depending on what properties you care about.
36980 Changes in version 0.0.8rc1 - 2004-08-18
36981 o Changes from 0.0.7.3:
36983 - Fix assert triggers: if the other side returns an address 0.0.0.0,
36984 don't put it into the client dns cache.
36985 - If a begin failed due to exit policy, but we believe the IP address
36986 should have been allowed, switch that router to exitpolicy reject *:*
36987 until we get our next directory.
36989 - Clients choose nodes proportional to advertised bandwidth.
36990 - Avoid using nodes with low uptime as introduction points.
36991 - Handle servers with dynamic IP addresses: don't replace
36992 options->Address with the resolved one at startup, and
36993 detect our address right before we make a routerinfo each time.
36994 - 'FascistFirewall' option to pick dirservers and ORs on specific
36995 ports; plus 'FirewallPorts' config option to tell FascistFirewall
36996 which ports are open. (Defaults to 80,443)
36997 - Be more aggressive about trying to make circuits when the network
36998 has changed (e.g. when you unsuspend your laptop).
36999 - Check for time skew on http headers; report date in response to
37001 - If the entrynode config line has only one node, don't pick it as
37003 - Add strict{entry|exit}nodes config options. If set to 1, then
37004 we refuse to build circuits that don't include the specified entry
37006 - OutboundBindAddress config option, to bind to a specific
37007 IP address for outgoing connect()s.
37008 - End truncated log entries (e.g. directories) with "[truncated]".
37010 o Patches to 0.0.8preX:
37012 - Patches to compile and run on win32 again (maybe)?
37013 - Fix crash when looking for ~/.torrc with no $HOME set.
37014 - Fix a race bug in the unit tests.
37015 - Handle verified/unverified name collisions better when new
37016 routerinfo's arrive in a directory.
37017 - Sometimes routers were getting entered into the stats before
37018 we'd assigned their identity_digest. Oops.
37019 - Only pick and establish intro points after we've gotten a
37022 - AllowUnverifiedNodes config option to let circuits choose no-name
37023 routers in entry,middle,exit,introduction,rendezvous positions.
37024 Allow middle and rendezvous positions by default.
37025 - Add a man page for tor-resolve.
37028 Changes in version 0.0.7.3 - 2004-08-12
37029 o Stop dnsworkers from triggering an assert failure when you
37030 ask them to resolve the host "".
37033 Changes in version 0.0.8pre3 - 2004-08-09
37034 o Changes from 0.0.7.2:
37035 - Allow multiple ORs with same nickname in routerlist -- now when
37036 people give us one identity key for a nickname, then later
37037 another, we don't constantly complain until the first expires.
37038 - Remember used bandwidth (both in and out), and publish 15-minute
37039 snapshots for the past day into our descriptor.
37040 - You can now fetch $DIRURL/running-routers to get just the
37041 running-routers line, not the whole descriptor list. (But
37042 clients don't use this yet.)
37043 - When people mistakenly use Tor as an http proxy, point them
37044 at the tor-doc.html rather than the INSTALL.
37045 - Remove our mostly unused -- and broken -- hex_encode()
37046 function. Use base16_encode() instead. (Thanks to Timo Lindfors
37047 for pointing out this bug.)
37048 - Rotate onion keys every 12 hours, not every 2 hours, so we have
37049 fewer problems with people using the wrong key.
37050 - Change the default exit policy to reject the default edonkey,
37051 kazaa, gnutella ports.
37052 - Add replace_file() to util.[ch] to handle win32's rename().
37054 o Changes from 0.0.8preX:
37055 - Fix two bugs in saving onion keys to disk when rotating, so
37056 hopefully we'll get fewer people using old onion keys.
37057 - Fix an assert error that was making SocksPolicy not work.
37058 - Be willing to expire routers that have an open dirport -- it's
37059 just the authoritative dirservers we want to not forget.
37060 - Reject tor-resolve requests for .onion addresses early, so we
37061 don't build a whole rendezvous circuit and then fail.
37062 - When you're warning a server that he's unverified, don't cry
37063 wolf unpredictably.
37064 - Fix a race condition: don't try to extend onto a connection
37065 that's still handshaking.
37066 - For servers in clique mode, require the conn to be open before
37067 you'll choose it for your path.
37068 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
37069 end relay cell, etc.
37070 - Measure bandwidth capacity over the last 24 hours, not just 12
37071 - Bugfix: authoritative dirservers were making and signing a new
37072 directory for each client, rather than reusing the cached one.
37075 Changes in version 0.0.8pre2 - 2004-08-04
37076 o Changes from 0.0.7.2:
37078 - Check directory signature _before_ you decide whether you're
37079 you're running an obsolete version and should exit.
37080 - Check directory signature _before_ you parse the running-routers
37081 list to decide who's running or verified.
37082 - Bugfixes and features:
37083 - Check return value of fclose while writing to disk, so we don't
37084 end up with broken files when servers run out of disk space.
37085 - Log a warning if the user uses an unsafe socks variant, so people
37086 are more likely to learn about privoxy or socat.
37087 - Dirservers now include RFC1123-style dates in the HTTP headers,
37088 which one day we will use to better detect clock skew.
37090 o Changes from 0.0.8pre1:
37091 - Make it compile without warnings again on win32.
37092 - Log a warning if you're running an unverified server, to let you
37093 know you might want to get it verified.
37094 - Only pick a default nickname if you plan to be a server.
37097 Changes in version 0.0.8pre1 - 2004-07-23
37099 - Made our unit tests compile again on OpenBSD 3.5, and tor
37100 itself compile again on OpenBSD on a sparc64.
37101 - We were neglecting milliseconds when logging on win32, so
37102 everything appeared to happen at the beginning of each second.
37104 o Protocol changes:
37105 - 'Extend' relay cell payloads now include the digest of the
37106 intended next hop's identity key. Now we can verify that we're
37107 extending to the right router, and also extend to routers we
37108 hadn't heard of before.
37111 - Tor nodes can now act as relays (with an advertised ORPort)
37112 without being manually verified by the dirserver operators.
37113 - Uploaded descriptors of unverified routers are now accepted
37114 by the dirservers, and included in the directory.
37115 - Verified routers are listed by nickname in the running-routers
37116 list; unverified routers are listed as "$<fingerprint>".
37117 - We now use hash-of-identity-key in most places rather than
37118 nickname or addr:port, for improved security/flexibility.
37119 - To avoid Sybil attacks, paths still use only verified servers.
37120 But now we have a chance to play around with hybrid approaches.
37121 - Nodes track bandwidth usage to estimate capacity (not used yet).
37122 - ClientOnly option for nodes that never want to become servers.
37123 - Directory caching.
37124 - "AuthoritativeDir 1" option for the official dirservers.
37125 - Now other nodes (clients and servers) will cache the latest
37126 directory they've pulled down.
37127 - They can enable their DirPort to serve it to others.
37128 - Clients will pull down a directory from any node with an open
37129 DirPort, and check the signature/timestamp correctly.
37130 - Authoritative dirservers now fetch directories from other
37131 authdirservers, to stay better synced.
37132 - Running-routers list tells who's down also, along with noting
37133 if they're verified (listed by nickname) or unverified (listed
37135 - Allow dirservers to serve running-router list separately.
37136 This isn't used yet.
37137 - ORs connect-on-demand to other ORs
37138 - If you get an extend cell to an OR you're not connected to,
37139 connect, handshake, and forward the create cell.
37140 - The authoritative dirservers stay connected to everybody,
37141 and everybody stays connected to 0.0.7 servers, but otherwise
37142 clients/servers expire unused connections after 5 minutes.
37143 - When servers get a sigint, they delay 30 seconds (refusing new
37144 connections) then exit. A second sigint causes immediate exit.
37145 - File and name management:
37146 - Look for .torrc if no CONFDIR "torrc" is found.
37147 - If no datadir is defined, then choose, make, and secure ~/.tor
37149 - If torrc not found, exitpolicy reject *:*.
37150 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
37151 - If no nickname is defined, derive default from hostname.
37152 - Rename secret key files, e.g. identity.key -> secret_id_key,
37153 to discourage people from mailing their identity key to tor-ops.
37154 - Refuse to build a circuit before the directory has arrived --
37155 it won't work anyway, since you won't know the right onion keys
37157 - Try other dirservers immediately if the one you try is down. This
37158 should tolerate down dirservers better now.
37159 - Parse tor version numbers so we can do an is-newer-than check
37160 rather than an is-in-the-list check.
37161 - New socks command 'resolve', to let us shim gethostbyname()
37163 - A 'tor_resolve' script to access the socks resolve functionality.
37164 - A new socks-extensions.txt doc file to describe our
37165 interpretation and extensions to the socks protocols.
37166 - Add a ContactInfo option, which gets published in descriptor.
37167 - Publish OR uptime in descriptor (and thus in directory) too.
37168 - Write tor version at the top of each log file
37169 - New docs in the tarball:
37171 - Document that you should proxy your SSL traffic too.
37174 Changes in version 0.0.7.2 - 2004-07-07
37175 o A better fix for the 0.0.0.0 problem, that will hopefully
37176 eliminate the remaining related assertion failures.
37179 Changes in version 0.0.7.1 - 2004-07-04
37180 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
37181 since internally we use 0.0.0.0 to signify "not yet resolved".
37184 Changes in version 0.0.7 - 2004-06-07
37185 o Updated the man page to reflect the new features.
37188 Changes in version 0.0.7rc2 - 2004-06-06
37189 o Changes from 0.0.7rc1:
37190 - Make it build on Win32 again.
37191 o Changes from 0.0.6.2:
37192 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
37196 Changes in version 0.0.7rc1 - 2004-06-02
37198 - On sighup, we were adding another log without removing the first
37199 one. So log messages would get duplicated n times for n sighups.
37200 - Several cases of using a connection after we'd freed it. The
37201 problem was that connections that are pending resolve are in both
37202 the pending_resolve tree, and also the circuit's resolving_streams
37203 list. When you want to remove one, you must remove it from both.
37204 - Fix a double-mark-for-close where an end cell arrived for a
37205 resolving stream, and then the resolve failed.
37206 - Check directory signatures based on name of signer, not on whom
37207 we got the directory from. This will let us cache directories more
37210 - Crank up some of our constants to handle more users.
37213 Changes in version 0.0.7pre1 - 2004-06-02
37214 o Fixes for crashes and other obnoxious bugs:
37215 - Fix an epipe bug: sometimes when directory connections failed
37216 to connect, we would give them a chance to flush before closing
37218 - When we detached from a circuit because of resolvefailed, we
37219 would immediately try the same circuit twice more, and then
37220 give up on the resolve thinking we'd tried three different
37222 - Limit the number of intro circuits we'll attempt to build for a
37223 hidden service per 15-minute period.
37224 - Check recommended-software string *early*, before actually parsing
37225 the directory. Thus we can detect an obsolete version and exit,
37226 even if the new directory format doesn't parse.
37227 o Fixes for security bugs:
37228 - Remember which nodes are dirservers when you startup, and if a
37229 random OR enables his dirport, don't automatically assume he's
37230 a trusted dirserver.
37232 - Directory connections were asking the wrong poll socket to
37233 start writing, and not asking themselves to start writing.
37234 - When we detached from a circuit because we sent a begin but
37235 didn't get a connected, we would use it again the first time;
37236 but after that we would correctly switch to a different one.
37237 - Stop warning when the first onion decrypt attempt fails; they
37238 will sometimes legitimately fail now that we rotate keys.
37239 - Override unaligned-access-ok check when $host_cpu is ia64 or
37240 arm. Apparently they allow it but the kernel whines.
37241 - Dirservers try to reconnect periodically too, in case connections
37243 - Fix some memory leaks in directory servers.
37244 - Allow backslash in Win32 filenames.
37245 - Made Tor build complain-free on FreeBSD, hopefully without
37246 breaking other BSD builds. We'll see.
37248 - Doxygen markup on all functions and global variables.
37249 - Make directory functions update routerlist, not replace it. So
37250 now directory disagreements are not so critical a problem.
37251 - Remove the upper limit on number of descriptors in a dirserver's
37252 directory (not that we were anywhere close).
37253 - Allow multiple logfiles at different severity ranges.
37254 - Allow *BindAddress to specify ":port" rather than setting *Port
37255 separately. Allow multiple instances of each BindAddress config
37256 option, so you can bind to multiple interfaces if you want.
37257 - Allow multiple exit policy lines, which are processed in order.
37258 Now we don't need that huge line with all the commas in it.
37259 - Enable accept/reject policies on SOCKS connections, so you can bind
37260 to 0.0.0.0 but still control who can use your OP.
37263 Changes in version 0.0.6.2 - 2004-05-16
37264 o Our integrity-checking digest was checking only the most recent cell,
37265 not the previous cells like we'd thought.
37266 Thanks to Stefan Mark for finding the flaw!
37269 Changes in version 0.0.6.1 - 2004-05-06
37270 o Fix two bugs in our AES counter-mode implementation (this affected
37271 onion-level stream encryption, but not TLS-level). It turns
37272 out we were doing something much more akin to a 16-character
37273 polyalphabetic cipher. Oops.
37274 Thanks to Stefan Mark for finding the flaw!
37275 o Retire moria3 as a directory server, and add tor26 as a directory
37279 Changes in version 0.0.6 - 2004-05-02
37280 [version bump only]
37283 Changes in version 0.0.6rc4 - 2004-05-01
37284 o Update the built-in dirservers list to use the new directory format
37285 o Fix a rare seg fault: if a node offering a hidden service attempts
37286 to build a circuit to Alice's rendezvous point and fails before it
37287 reaches the last hop, it retries with a different circuit, but
37289 o Handle windows socket errors correctly.
37292 Changes in version 0.0.6rc3 - 2004-04-28
37293 o Don't expire non-general excess circuits (if we had enough
37294 circuits open, we were expiring rendezvous circuits -- even
37295 when they had a stream attached. oops.)
37296 o Fetch randomness from /dev/urandom better (not via fopen/fread)
37297 o Better debugging for tls errors
37298 o Some versions of openssl have an SSL_pending function that erroneously
37299 returns bytes when there is a non-application record pending.
37300 o Set Content-Type on the directory and hidserv descriptor.
37301 o Remove IVs from cipher code, since AES-ctr has none.
37302 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
37303 o We were using an array of length zero in a few places.
37304 o win32's gethostbyname can't resolve an IP to an IP.
37305 o win32's close can't close a socket.
37308 Changes in version 0.0.6rc2 - 2004-04-26
37309 o Fix a bug where we were closing tls connections intermittently.
37310 It turns out openssl keeps its errors around -- so if an error
37311 happens, and you don't ask about it, and then another openssl
37312 operation happens and succeeds, and you ask if there was an error,
37313 it tells you about the first error. Fun fun.
37314 o Fix a bug that's been lurking since 27 may 03 (!)
37315 When passing back a destroy cell, we would use the wrong circ id.
37316 'Mostly harmless', but still worth fixing.
37317 o Since we don't support truncateds much, don't bother sending them;
37318 just close the circ.
37319 o check for <machine/limits.h> so we build on NetBSD again (I hope).
37320 o don't crash if a conn that sent a begin has suddenly lost its circuit
37321 (this was quite rare).
37324 Changes in version 0.0.6rc1 - 2004-04-25
37325 o We now rotate link (tls context) keys and onion keys.
37326 o CREATE cells now include oaep padding, so you can tell
37327 if you decrypted them correctly.
37328 o Add bandwidthburst to server descriptor.
37329 o Directories now say which dirserver signed them.
37330 o Use a tor_assert macro that logs failed assertions too.
37333 Changes in version 0.0.6pre5 - 2004-04-18
37334 o changes from 0.0.6pre4:
37335 - make tor build on broken freebsd 5.2 installs
37336 - fix a failed assert when you try an intro point, get a nack, and try
37337 a second one and it works.
37338 - when alice uses a port that the hidden service doesn't accept,
37339 it now sends back an end cell (denied by exit policy). otherwise
37340 alice would just have to wait to time out.
37341 - fix another rare bug: when we had tried all the intro
37342 points for a hidden service, we fetched the descriptor
37343 again, but we left our introcirc thinking it had already
37344 sent an intro, so it kept waiting for a response...
37345 - bugfix: when you sleep your hidden-service laptop, as soon
37346 as it wakes up it tries to upload a service descriptor, but
37347 socketpair fails for some reason (localhost not up yet?).
37348 now we simply give up on that upload, and we'll try again later.
37349 i'd still like to find the bug though.
37350 - if an intro circ waiting for an ack dies before getting one, then
37352 - we were reusing stale service descriptors and refetching usable
37356 Changes in version 0.0.6pre4 - 2004-04-14
37357 o changes from 0.0.6pre3:
37358 - when bob fails to connect to the rendezvous point, and his
37359 circ didn't fail because of the rendezvous point itself, then
37360 he retries a couple of times
37361 - we expire introduction and rendezvous circs more thoroughly
37362 (sometimes they were hanging around forever)
37363 - we expire unattached rendezvous streams that have been around
37364 too long (they were sticking around forever).
37365 - fix a measly fencepost error that was crashing everybody with
37369 Changes in version 0.0.6pre3 - 2004-04-14
37370 o changes from 0.0.6pre2:
37371 - make hup work again
37372 - fix some memory leaks for dirservers
37373 - allow more skew in rendezvous descriptor timestamps, to help
37374 handle people like blanu who don't know what time it is
37375 - normal circs are 3 hops, but some rend/intro circs are 4, if
37376 the initiator doesn't get to choose the last hop
37377 - send acks for introductions, so alice can know whether to try
37379 - bob publishes intro points more correctly
37380 o changes from 0.0.5:
37381 - fix an assert trigger that's been plaguing us since the days
37382 of 0.0.2prexx (thanks weasel!)
37383 - retry stream correctly when we fail to connect because of
37384 exit-policy-reject (should try another) or can't-resolve-address
37385 (also should try another, because dns on random internet servers
37387 - when we hup a dirserver and we've *removed* a server from the
37388 approved-routers list, now we remove that server from the
37389 in-memory directories too
37392 Changes in version 0.0.6pre2 - 2004-04-08
37393 o We fixed our base32 implementation. Now it works on all architectures.
37396 Changes in version 0.0.6pre1 - 2004-04-08
37398 - Hidden services and rendezvous points are implemented. Go to
37399 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
37400 hidden services. (This only works via a socks4a proxy such as
37401 Privoxy, and currently it's quite slow.)
37404 Changes in version 0.0.5 - 2004-03-30
37405 [version bump only]
37408 Changes in version 0.0.5rc3 - 2004-03-29
37409 o Install torrc as torrc.sample -- we no longer clobber your
37411 o Re-enable recommendedversion checking (we broke it in rc2, oops)
37412 o Add in a 'notice' log level for things the operator should hear
37413 but that aren't warnings
37416 Changes in version 0.0.5rc2 - 2004-03-29
37417 o Hold socks connection open until reply is flushed (if possible)
37418 o Make exit nodes resolve IPs to IPs immediately, rather than asking
37419 the dns farm to do it.
37420 o Fix c99 aliasing warnings in rephist.c
37421 o Don't include server descriptors that are older than 24 hours in the
37423 o Give socks 'reject' replies their whole 15s to attempt to flush,
37424 rather than seeing the 60s timeout and assuming the flush had failed.
37425 o Clean automake droppings from the cvs repository
37428 Changes in version 0.0.5rc1 - 2004-03-28
37429 o Fix mangled-state bug in directory fetching (was causing sigpipes).
37430 o Only build circuits after we've fetched the directory: clients were
37431 using only the directory servers before they'd fetched a directory.
37432 This also means longer startup time; so it goes.
37433 o Fix an assert trigger where an OP would fail to handshake, and we'd
37434 expect it to have a nickname.
37435 o Work around a tsocks bug: do a socks reject when AP connection dies
37436 early, else tsocks goes into an infinite loop.
37439 Changes in version 0.0.4 - 2004-03-26
37440 o When connecting to a dirserver or OR and the network is down,
37444 Changes in version 0.0.3 - 2004-03-26
37445 o Warn and fail if server chose a nickname with illegal characters
37446 o Port to Solaris and Sparc:
37447 - include missing header fcntl.h
37448 - have autoconf find -lsocket -lnsl automatically
37449 - deal with hardware word alignment
37450 - make uname() work (solaris has a different return convention)
37451 - switch from using signal() to sigaction()
37452 o Preliminary work on reputation system:
37453 - Keep statistics on success/fail of connect attempts; they're published
37454 by kill -USR1 currently.
37455 - Add a RunTesting option to try to learn link state by creating test
37456 circuits, even when SocksPort is off.
37457 - Remove unused open circuits when there are too many.
37460 Changes in version 0.0.2 - 2004-03-19
37461 - Include strlcpy and strlcat for safer string ops
37462 - define INADDR_NONE so we compile (but still not run) on solaris
37465 Changes in version 0.0.2pre27 - 2004-03-14
37467 - Allow internal tor networks (we were rejecting internal IPs,
37468 now we allow them if they're set explicitly).
37469 - And fix a few endian issues.
37472 Changes in version 0.0.2pre26 - 2004-03-14
37474 - If a stream times out after 15s without a connected cell, don't
37475 try that circuit again: try a new one.
37476 - Retry streams at most 4 times. Then give up.
37477 - When a dirserver gets a descriptor from an unknown router, it
37478 logs its fingerprint (so the dirserver operator can choose to
37479 accept it even without mail from the server operator).
37480 - Inform unapproved servers when we reject their descriptors.
37481 - Make tor build on Windows again. It works as a client, who knows
37483 - Clearer instructions in the torrc for how to set up a server.
37484 - Be more efficient about reading fd's when our global token bucket
37485 (used for rate limiting) becomes empty.
37487 - Stop asserting that computers always go forward in time. It's
37489 - When we sent a cell (e.g. destroy) and then marked an OR connection
37490 expired, we might close it before finishing a flush if the other
37491 side isn't reading right then.
37492 - Don't allow dirservers to start if they haven't defined
37493 RecommendedVersions
37494 - We were caching transient dns failures. Oops.
37495 - Prevent servers from publishing an internal IP as their address.
37496 - Address a strcat vulnerability in circuit.c
37499 Changes in version 0.0.2pre25 - 2004-03-04
37501 - Put the OR's IP in its router descriptor, not its fqdn. That way
37502 we'll stop being stalled by gethostbyname for nodes with flaky dns,
37505 - If the user typed in an address that didn't resolve, the server
37509 Changes in version 0.0.2pre24 - 2004-03-03
37511 - Fix an assertion failure in dns.c, where we were trying to dequeue
37512 a pending dns resolve even if it wasn't pending
37513 - Fix a spurious socks5 warning about still trying to write after the
37514 connection is finished.
37515 - Hold certain marked_for_close connections open until they're finished
37516 flushing, rather than losing bytes by closing them too early.
37517 - Correctly report the reason for ending a stream
37518 - Remove some duplicate calls to connection_mark_for_close
37519 - Put switch_id and start_daemon earlier in the boot sequence, so it
37520 will actually try to chdir() to options.DataDirectory
37521 - Make 'make test' exit(1) if a test fails; fix some unit tests
37522 - Make tor fail when you use a config option it doesn't know about,
37523 rather than warn and continue.
37524 - Make --version work
37525 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
37528 Changes in version 0.0.2pre23 - 2004-02-29
37530 - Print a statement when the first circ is finished, so the user
37531 knows it's working.
37532 - If a relay cell is unrecognized at the end of the circuit,
37533 send back a destroy. (So attacks to mutate cells are more
37535 - New config option 'excludenodes' to avoid certain nodes for circuits.
37536 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
37537 so you can collect coredumps there.
37539 - Fix a bug in tls flushing where sometimes data got wedged and
37540 didn't flush until more data got sent. Hopefully this bug was
37541 a big factor in the random delays we were seeing.
37542 - Make 'connected' cells include the resolved IP, so the client
37543 dns cache actually gets populated.
37544 - Disallow changing from ORPort=0 to ORPort>0 on hup.
37545 - When we time-out on a stream and detach from the circuit, send an
37546 end cell down it first.
37547 - Only warn about an unknown router (in exitnodes, entrynodes,
37548 excludenodes) after we've fetched a directory.
37551 Changes in version 0.0.2pre22 - 2004-02-26
37553 - Servers publish less revealing uname information in descriptors.
37554 - More memory tracking and assertions, to crash more usefully when
37556 - If the default torrc isn't there, just use some default defaults.
37557 Plus provide an internal dirservers file if they don't have one.
37558 - When the user tries to use Tor as an http proxy, give them an http
37559 501 failure explaining that we're a socks proxy.
37560 - Dump a new router.desc on hup, to help confused people who change
37561 their exit policies and then wonder why router.desc doesn't reflect
37563 - Clean up the generic tor.sh init script that we ship with.
37565 - If the exit stream is pending on the resolve, and a destroy arrives,
37566 then the stream wasn't getting removed from the pending list. I
37567 think this was the one causing recent server crashes.
37568 - Use a more robust poll on OSX 10.3, since their poll is flaky.
37569 - When it couldn't resolve any dirservers, it was useless from then on.
37570 Now it reloads the RouterFile (or default dirservers) if it has no
37572 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
37573 many users don't even *have* a /usr/local/sbin/.
37576 Changes in version 0.0.2pre21 - 2004-02-18
37578 - There's a ChangeLog file that actually reflects the changelog.
37579 - There's a 'torify' wrapper script, with an accompanying
37580 tor-tsocks.conf, that simplifies the process of using tsocks for
37581 tor. It even has a man page.
37582 - The tor binary gets installed to sbin rather than bin now.
37583 - Retry streams where the connected cell hasn't arrived in 15 seconds
37584 - Clean up exit policy handling -- get the default out of the torrc,
37585 so we can update it without forcing each server operator to fix
37587 - Allow imaps and pop3s in default exit policy
37589 - Prevent picking middleman nodes as the last node in the circuit
37592 Changes in version 0.0.2pre20 - 2004-01-30
37594 - We now have a deb package, and it's in debian unstable. Go to
37595 it, apt-getters. :)
37596 - I've split the TotalBandwidth option into BandwidthRate (how many
37597 bytes per second you want to allow, long-term) and
37598 BandwidthBurst (how many bytes you will allow at once before the cap
37599 kicks in). This better token bucket approach lets you, say, set
37600 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
37601 performance while not exceeding your monthly bandwidth quota.
37602 - Push out a tls record's worth of data once you've got it, rather
37603 than waiting until you've read everything waiting to be read. This
37604 may improve performance by pipelining better. We'll see.
37605 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
37606 from failed circuits (if they haven't been connected yet) and attach
37608 - Expire old streams that haven't managed to connect. Some day we'll
37609 have them reattach to new circuits instead.
37612 - Fix several memory leaks that were causing servers to become bloated
37614 - Fix a few very rare assert triggers. A few more remain.
37615 - Setuid to User _before_ complaining about running as root.
37618 Changes in version 0.0.2pre19 - 2004-01-07
37620 - Fix deadlock condition in dns farm. We were telling a child to die by
37621 closing the parent's file descriptor to him. But newer children were
37622 inheriting the open file descriptor from the parent, and since they
37623 weren't closing it, the socket never closed, so the child never read
37624 eof, so he never knew to exit. Similarly, dns workers were holding
37625 open other sockets, leading to all sorts of chaos.
37626 - New cleaner daemon() code for forking and backgrounding.
37627 - If you log to a file, it now prints an entry at the top of the
37628 logfile so you know it's working.
37629 - The onionskin challenge length was 30 bytes longer than necessary.
37630 - Started to patch up the spec so it's not quite so out of date.
37633 Changes in version 0.0.2pre18 - 2004-01-02
37635 - Fix endian issues with the 'integrity' field in the relay header.
37636 - Fix a potential bug where connections in state
37637 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
37640 Changes in version 0.0.2pre17 - 2003-12-30
37642 - Made --debuglogfile (or any second log file, actually) work.
37643 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
37644 adversary could force us into an infinite loop.
37647 - Each onionskin handshake now includes a hash of the computed key,
37648 to prove the server's identity and help perfect forward secrecy.
37649 - Changed cell size from 256 to 512 bytes (working toward compatibility
37651 - Changed cell length to 2 bytes, and moved it to the relay header.
37652 - Implemented end-to-end integrity checking for the payloads of
37654 - Separated streamid from 'recognized' (otherwise circuits will get
37655 messed up when we try to have streams exit from the middle). We
37656 use the integrity-checking to confirm that a cell is addressed to
37658 - Randomize the initial circid and streamid values, so an adversary who
37659 breaks into a node can't learn how many circuits or streams have
37663 Changes in version 0.0.2pre16 - 2003-12-14
37665 - Fixed a bug that made HUP trigger an assert
37666 - Fixed a bug where a circuit that immediately failed wasn't being
37667 counted as a failed circuit in counting retries.
37670 - Now we close the circuit when we get a truncated cell: otherwise we're
37671 open to an anonymity attack where a bad node in the path truncates
37672 the circuit and then we open streams at him.
37673 - Add port ranges to exit policies
37674 - Add a conservative default exit policy
37675 - Warn if you're running tor as root
37676 - on HUP, retry OR connections and close/rebind listeners
37677 - options.EntryNodes: try these nodes first when picking the first node
37678 - options.ExitNodes: if your best choices happen to include any of
37679 your preferred exit nodes, you choose among just those preferred
37681 - options.ExcludedNodes: nodes that are never picked in path building
37684 Changes in version 0.0.2pre15 - 2003-12-03
37685 o Robustness and bugfixes:
37686 - Sometimes clients would cache incorrect DNS resolves, which would
37687 really screw things up.
37688 - An OP that goes offline would slowly leak all its sockets and stop
37690 - A wide variety of bugfixes in exit node selection, exit policy
37691 handling, and processing pending streams when a new circuit is
37693 - Pick nodes for a path only from those the directory says are up
37694 - Choose randomly from all running dirservers, not always the first one
37695 - Increase allowed http header size for directory fetch.
37696 - Stop writing to stderr (if we're daemonized it will be closed).
37697 - Enable -g always, so cores will be more useful to me.
37698 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
37701 - Wrote a man page. It lists commonly used options.
37704 - Change default loglevel to warn.
37705 - Make PidFile default to null rather than littering in your CWD.
37706 - OnionRouter config option is now obsolete. Instead it just checks
37708 - Moved to a single unified torrc file for both clients and servers.
37711 Changes in version 0.0.2pre14 - 2003-11-29
37712 o Robustness and bugfixes:
37713 - Force the admin to make the DataDirectory himself
37714 - to get ownership/permissions right
37715 - so clients no longer make a DataDirectory and then never use it
37716 - fix bug where a client who was offline for 45 minutes would never
37717 pull down a directory again
37718 - fix (or at least hide really well) the dns assert bug that was
37719 causing server crashes
37720 - warnings and improved robustness wrt clockskew for certs
37721 - use the native daemon(3) to daemonize, when available
37722 - exit if bind() fails
37723 - exit if neither socksport nor orport is defined
37724 - include our own tor_timegm (Win32 doesn't have its own)
37725 - bugfix for win32 with lots of connections
37726 - fix minor bias in PRNG
37727 - make dirserver more robust to corrupt cached directory
37730 - Wrote the design document (woo)
37732 o Circuit building and exit policies:
37733 - Circuits no longer try to use nodes that the directory has told them
37735 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
37736 bitcounts (18.0.0.0/8).
37737 - Make AP connections standby for a circuit if no suitable circuit
37738 exists, rather than failing
37739 - Circuits choose exit node based on addr/port, exit policies, and
37740 which AP connections are standing by
37741 - Bump min pathlen from 2 to 3
37742 - Relay end cells have a payload to describe why the stream ended.
37743 - If the stream failed because of exit policy, try again with a new
37745 - Clients have a dns cache to remember resolved addresses.
37746 - Notice more quickly when we have no working circuits
37749 - APPort is now called SocksPort
37750 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
37752 - RecommendedVersions is now a config variable rather than
37753 hardcoded (for dirservers)
37754 - Reloads config on HUP
37755 - Usage info on -h or --help
37756 - If you set User and Group config vars, it'll setu/gid to them.
37759 Changes in version 0.0.2pre13 - 2003-10-19
37760 o General stability:
37761 - SSL_write no longer fails when it returns WANTWRITE and the number
37762 of bytes in the buf has changed by the next SSL_write call.
37763 - Fix segfault fetching directory when network is down
37764 - Fix a variety of minor memory leaks
37765 - Dirservers reload the fingerprints file on HUP, so I don't have
37766 to take down the network when I approve a new router
37767 - Default server config file has explicit Address line to specify fqdn
37770 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
37771 - Make listener connections not ever alloc bufs
37773 o Autoconf improvements:
37774 - don't clobber an external CFLAGS in ./configure
37775 - Make install now works
37776 - create var/lib/tor on make install
37777 - autocreate a tor.sh initscript to help distribs
37778 - autocreate the torrc and sample-server-torrc with correct paths
37780 o Log files and Daemonizing now work:
37781 - If --DebugLogFile is specified, log to it at -l debug
37782 - If --LogFile is specified, use it instead of commandline
37783 - If --RunAsDaemon is set, tor forks and backgrounds on startup