1 This document summarizes new features and bugfixes in each stable
2 release of Tor. If you want to see more detailed descriptions of the
3 changes in each development snapshot, see the ChangeLog file.
5 Changes in version 0.4.5.16 - 2023-01-12
6 This version has one major bugfix for relay and a security fix,
7 TROVE-2022-002, affecting clients. We strongly recommend to upgrade to our
8 0.4.7.x stable series. As a reminder, this series is EOL on February 15th,
11 o Major bugfixes (relay):
12 - When opening a channel because of a circuit request that did not
13 include an Ed25519 identity, record the Ed25519 identity that we
14 actually received, so that we can use the channel for other
15 circuit requests that _do_ list an Ed25519 identity. (Previously
16 we had code to record this identity, but a logic bug caused it to
17 be disabled.) Fixes bug 40563; bugfix on 0.3.0.1-alpha. Patch
20 o Major bugfixes (TROVE-2022-002, client):
21 - The SafeSocks option had its logic inverted for SOCKS4 and
22 SOCKS4a. It would let the unsafe SOCKS4 pass but not the safe
23 SOCKS4a one. This is TROVE-2022-002 which was reported on
24 Hackerone by "cojabo". Fixes bug 40730; bugfix on 0.3.5.1-alpha.
26 o Minor features (fallbackdir):
27 - Regenerate fallback directories generated on January 12, 2023.
29 o Minor features (geoip data):
30 - Update the geoip files to match the IPFire Location Database, as
31 retrieved on 2023/01/12.
34 Changes in version 0.4.5.15 - 2022-12-06
35 This version has several major changes for directory authorities. And a
36 major bugfix on OSX. Again, we strongly recommend to upgrade to our 0.4.7.x
37 series latest stable. This series is EOL on February 15th, 2023.
39 o Directory authority changes (dizum):
40 - Change dizum IP address. Closes ticket 40687.
42 o Directory authority changes (Faravahar):
43 - Remove Faravahar until its operator, Sina, set it back up online
44 outside of Team Cymru network. Closes ticket 40688.
46 o Directory authority changes (moria1):
47 - Rotate the relay identity key and v3 identity key for moria1. They
48 have been online for more than a decade and refreshing keys
49 periodically is good practice. Advertise new ports too, to avoid
50 confusion. Closes ticket 40722.
52 o Major bugfixes (OSX):
53 - Fix coarse-time computation on Apple platforms (like Mac M1) where
54 the Mach absolute time ticks do not correspond directly to
55 nanoseconds. Previously, we computed our shift value wrong, which
56 led us to give incorrect timing results. Fixes bug 40684; bugfix
59 o Major bugfixes (relay):
60 - Improve security of our DNS cache by randomly clipping the TTL
61 value. TROVE-2021-009. Fixes bug 40674; bugfix on 0.3.5.1-alpha.
63 o Minor features (fallbackdir):
64 - Regenerate fallback directories generated on December 06, 2022.
66 o Minor features (geoip data):
67 - Update the geoip files to match the IPFire Location Database, as
68 retrieved on 2022/12/06.
71 Changes in version 0.4.5.14 - 2022-08-12
72 This version updates the geoip cache that we generate from IPFire location
73 database to use the August 9th, 2022 one. Everyone MUST update to this
74 latest release else circuit path selection and relay metrics are badly
77 o Major bugfixes (geoip data):
78 - IPFire informed us on August 12th that databases generated after
79 (including) August 10th did not have proper ARIN network allocations. We
80 are updating the database to use the one generated on August 9th, 2022.
81 Fixes bug 40658; bugfix on 0.4.5.13.
84 Changes in version 0.4.5.13 - 2022-08-11
85 This version contains two major fixes aimed at reducing memory pressure on
86 relays and possible side-channel. The rest of the fixes were backported for
87 stability or safety purposes. We strongly recommend to upgrade your relay to
88 this version or, ideally, to the latest stable of the 0.4.7.x series.
90 o Major bugfixes (relay):
91 - Remove OR connections btrack subsystem entries when the connections
92 close normally. Before this, we would only remove the entry on error and
93 thus leaking memory for each normal OR connections. Fixes bug 40604;
94 bugfix on 0.4.0.1-alpha.
95 - Stop sending TRUNCATED cell and instead close the circuit from which we
96 received a DESTROY cell. This makes every relay in the circuit path to
97 stop queuing cells. Fixes bug 40623; bugfix on 0.1.0.2-rc.
99 o Minor features (fallbackdir):
100 - Regenerate fallback directories generated on August 11, 2022.
102 o Minor features (geoip data):
103 - Update the geoip files to match the IPFire Location Database, as
104 retrieved on 2022/08/11.
106 o Minor features (linux seccomp2 sandbox):
107 - Permit the clone3 syscall, which is apparently used in glibc-2.34
108 and later. Closes ticket 40590.
110 o Minor bugfixes (controller, path bias):
111 - When a circuit's path is specified, in full or in part, from the
112 controller API, do not count that circuit towards our path-bias
113 calculations. (Doing so was incorrect, since we cannot tell
114 whether the controller is selecting relays randomly.) Resolves a
115 "Bug" warning. Fixes bug 40515; bugfix on 0.2.4.10-alpha.
117 o Minor bugfixes (defense in depth):
118 - Change a test in the netflow padding code to make it more
119 _obviously_ safe against remotely triggered crashes. (It was safe
120 against these before, but not obviously so.) Fixes bug 40645;
121 bugfix on 0.3.1.1-alpha.
123 o Minor bugfixes (linux seccomp2 sandbox):
124 - Allow the rseq system call in the sandbox. This solves a crash
125 issue with glibc 2.35 on Linux. Patch from pmu-ipf. Fixes bug
126 40601; bugfix on 0.3.5.11.
128 o Minor bugfixes (metrics port, onion service):
129 - The MetricsPort line for an onion service with multiple ports are now
130 unique that is one line per port. Before this, all ports of an onion
131 service would be on the same line which violates the Prometheus rules of
132 unique labels. Fixes bug 40581; bugfix on 0.4.5.1-alpha.
134 o Minor bugfixes (onion service, client):
135 - Fix a fatal assert due to a guard subsystem recursion triggered by
136 the onion service client. Fixes bug 40579; bugfix on 0.3.5.1-alpha.
138 o Minor bugfixes (performance, DoS):
139 - Fix one case of a not-especially viable denial-of-service attack
140 found by OSS-Fuzz in our consensus-diff parsing code. This attack
141 causes a lot small of memory allocations and then immediately
142 frees them: this is only slow when running with all the sanitizers
143 enabled. Fixes one case of bug 40472; bugfix on 0.3.1.1-alpha.
145 o Minor bugfixes (relay):
146 - Do not propagate either forward or backward a DESTROY remote reason when
147 closing a circuit in order to avoid a possible side channel. Fixes bug
148 40649; bugfix on 0.1.2.4-alpha.
151 Changes in version 0.4.5.12 - 2022-02-04
152 This version contains mostly minor bugfixes for which you can find the
153 details below. The previous release (0.4.5.11) was suppose to update the
154 GeoIP and fallbackdir lists but a problem in our release pipeline prevented
155 those files to be updated correctly. Thus, this release regenerates up to
156 date lists. Furthermore, another fix to highlight is that relays don't
157 advertise onion service v2 support at the protocol version level.
159 o Minor feature (reproducible build):
160 - The repository can now build reproducible tarballs which adds the
161 build command "make dist-reprod" for that purpose. Closes
164 o Minor features (compilation):
165 - Give an error message if trying to build with a version of
166 LibreSSL known not to work with Tor. (There's an incompatibility
167 with LibreSSL versions 3.2.1 through 3.4.0 inclusive because of
168 their incompatibility with OpenSSL 1.1.1's TLSv1.3 APIs.) Closes
171 o Minor features (fallbackdir):
172 - Regenerate fallback directories generated on December 15, 2021.
173 - Regenerate fallback directories generated on February 04, 2022.
175 o Minor features (geoip data):
176 - Update the geoip files to match the IPFire Location Database, as
177 retrieved on 2021/12/15.
178 - Update the geoip files to match the IPFire Location Database, as
179 retrieved on 2022/02/04.
181 o Minor bugfix (logging):
182 - Update a log notice dead URL to a working one. Fixes bug 40544;
183 bugfix on 0.3.5.1-alpha.
185 o Minor bugfix (relay):
186 - Remove the HSDir and HSIntro onion service v2 protocol versions so
187 relay stop advertising that they support them. Fixes bug 40509;
190 o Minor bugfixes (compilation):
191 - Fix a compilation error when trying to build Tor with a compiler
192 that does not support expanding statitically initialized const
193 values in macro's. Fixes bug 40410; bugfix on 0.4.5.1-alpha
194 - Fix our configuration logic to detect whether we had OpenSSL 3:
195 previously, our logic was reversed. This has no other effect than
196 to change whether we suppress deprecated API warnings. Fixes bug
197 40429; bugfix on 0.3.5.13.
199 o Minor bugfixes (MetricsPort, Prometheus):
200 - Add double quotes to the label values of the onion service
201 metrics. Fixes bug 40552; bugfix on 0.4.5.1-alpha.
203 o Minor bugfixes (relay):
204 - Reject IPv6-only DirPorts. Our reachability self-test forces
205 DirPorts to be IPv4, but our configuration parser allowed them to
206 be IPv6-only, which led to an assertion failure. Fixes bug 40494;
207 bugfix on 0.4.5.1-alpha.
210 Changes in version 0.4.5.11 - 2021-10-26
211 The major change in this version is that v2 onion services are now
212 disabled at the client, service, and relay: any Tor nodes running this
213 version and onward will stop supporting v2 onion services. This is the
214 last step in the long deprecation process of v2 onion services.
215 Everyone running an earlier version, whether as a client, a relay, or
216 an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11,
219 o Major feature (onion service v2):
220 - See https://blog.torproject.org/v2-deprecation-timeline for
221 details on how to transition from v2 to v3.
222 - The control port commands HSFETCH and HSPOST no longer allow
223 version 2, and it is no longer possible to create a v2 service
225 - Tor no longer allows creating v2 services, or connecting as a
226 client to a v2 service. Relays will decline to be a v2 HSDir or
227 introduction point. This effectively disables onion service
228 version 2 Tor-wide. Closes ticket 40476.
230 o Minor features (bridge, backport from 0.4.6.8):
231 - We now announce the URL to Tor's new bridge status at
232 https://bridges.torproject.org/ when Tor is configured to run as a
233 bridge relay. Closes ticket 30477.
235 o Minor features (fallbackdir):
236 - Regenerate fallback directories for October 2021. Closes
239 o Minor features (logging, diagnostic, backport from 0.4.6.5):
240 - Log decompression failures at a higher severity level, since they
241 can help provide missing context for other warning messages. We
242 rate-limit these messages, to avoid flooding the logs if they
243 begin to occur frequently. Closes ticket 40175.
245 o Minor features (testing, backport from 0.4.6.8):
246 - On a testing network, relays can now use the
247 TestingMinTimeToReportBandwidth option to change the smallest
248 amount of time over which they're willing to report their observed
249 maximum bandwidth. Previously, this was fixed at 1 day. For
250 safety, values under 2 hours are only supported on testing
251 networks. Part of a fix for ticket 40337.
252 - Relays on testing networks no longer rate-limit how frequently
253 they are willing to report new bandwidth measurements. Part of a
254 fix for ticket 40337.
255 - Relays on testing networks now report their observed bandwidths
256 immediately from startup. Previously, they waited until they had
257 been running for a full day. Closes ticket 40337.
259 o Minor bugfix (CI, onion service):
260 - Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500;
261 bugfix on 0.3.2.1-alpha.
263 o Minor bugfix (onion service, backport from 0.4.6.8):
264 - Do not flag an HSDir as non-running in case the descriptor upload
265 or fetch fails. An onion service closes pending directory
266 connections before uploading a new descriptor which can thus lead
267 to wrongly flagging many relays and thus affecting circuit building
268 path selection. Fixes bug 40434; bugfix on 0.2.0.13-alpha.
270 o Minor bugfixes (compatibility, backport from 0.4.6.8):
271 - Fix compatibility with the most recent Libevent versions, which no
272 longer have an evdns_set_random_bytes() function. Because this
273 function has been a no-op since Libevent 2.0.4-alpha, it is safe
274 for us to just stop calling it. Fixes bug 40371; bugfix
277 o Minor bugfixes (consensus handling, backport from 0.4.6.4-rc):
278 - Avoid a set of bugs that could be caused by inconsistently
279 preferring an out-of-date consensus stored in a stale directory
280 cache over a more recent one stored on disk as the latest
281 consensus. Fixes bug 40375; bugfix on 0.3.1.1-alpha.
283 o Minor bugfixes (onion service, TROVE-2021-008, backport from 0.4.6.8):
284 - Only log v2 access attempts once total, in order to not pollute
285 the logs with warnings and to avoid recording the times on disk
286 when v2 access was attempted. Note that the onion address was
287 _never_ logged. This counts as a Low-severity security issue.
288 Fixes bug 40474; bugfix on 0.4.5.8.
291 Changes in version 0.4.5.10 - 2021-08-16
292 This version fixes several bugs from earlier versions of Tor, including one
293 that could lead to a denial-of-service attack. Everyone running an earlier
294 version, whether as a client, a relay, or an onion service, should upgrade
295 to Tor 0.3.5.16, 0.4.5.10, or 0.4.6.7.
297 o Major bugfixes (cryptography, security):
298 - Resolve an assertion failure caused by a behavior mismatch between our
299 batch-signature verification code and our single-signature verification
300 code. This assertion failure could be triggered remotely, leading to a
301 denial of service attack. We fix this issue by disabling batch
302 verification. Fixes bug 40078; bugfix on 0.2.6.1-alpha. This issue is
303 also tracked as TROVE-2021-007 and CVE-2021-38385. Found by Henry de
306 o Minor feature (fallbackdir):
307 - Regenerate fallback directories list. Closes ticket 40447.
309 o Minor features (geoip data):
310 - Update the geoip files to match the IPFire Location Database,
311 as retrieved on 2021/08/12.
313 o Minor features (testing):
314 - Enable the deterministic RNG for unit tests that covers the address set
315 bloomfilter-based API's. Fixes bug 40419; bugfix on 0.3.3.2-alpha.
317 o Minor bugfix (crypto):
318 - Disable the unused batch verification feature of ed25519-donna. Fixes
319 bug 40078; bugfix on 0.2.6.1-alpha. Found by Henry de Valence.
321 o Minor bugfixes (relay, backport from 0.4.6.x):
322 - Reduce the compression level for data streaming from HIGH to LOW. Fixes
323 bug 40301; bugfix on 0.3.5.1-alpha.
325 o Minor bugfixes (timekeeping, backport from 0.4.6.x):
326 - Calculate the time of day correctly on systems where the time_t
327 type includes leap seconds. (This is not the case on most
328 operating systems, but on those where it occurs, our tor_timegm
329 function did not correctly invert the system's gmtime function,
330 which could result in assertion failures when calculating
331 voting schedules.) Fixes bug 40383; bugfix on 0.2.0.3-alpha.
333 o Minor bugfixes (warnings, portability, backport from 0.4.6.x):
334 - Suppress a strict-prototype warning when building with some versions
335 of NSS. Fixes bug 40409; bugfix on 0.3.5.1-alpha.
338 Changes in version 0.4.5.9 - 2021-06-14
339 Tor 0.4.5.9 fixes several security issues, including a
340 denial-of-service attack against onion service clients, and another
341 denial-of-service attack against relays. Everybody should upgrade to
342 one of 0.3.5.15, 0.4.4.9, 0.4.5.9, or 0.4.6.5.
344 o Major bugfixes (security, backport from 0.4.6.5):
345 - Don't allow relays to spoof RELAY_END or RELAY_RESOLVED cell on
346 half-closed streams. Previously, clients failed to validate which
347 hop sent these cells: this would allow a relay on a circuit to end
348 a stream that wasn't actually built with it. Fixes bug 40389;
349 bugfix on 0.3.5.1-alpha. This issue is also tracked as TROVE-2021-
350 003 and CVE-2021-34548.
352 o Major bugfixes (security, defense-in-depth, backport from 0.4.6.5):
353 - Detect more failure conditions from the OpenSSL RNG code.
354 Previously, we would detect errors from a missing RNG
355 implementation, but not failures from the RNG code itself.
356 Fortunately, it appears those failures do not happen in practice
357 when Tor is using OpenSSL's default RNG implementation. Fixes bug
358 40390; bugfix on 0.2.8.1-alpha. This issue is also tracked as
359 TROVE-2021-004. Reported by Jann Horn at Google's Project Zero.
361 o Major bugfixes (security, denial of service, backport from 0.4.6.5):
362 - Resist a hashtable-based CPU denial-of-service attack against
363 relays. Previously we used a naive unkeyed hash function to look
364 up circuits in a circuitmux object. An attacker could exploit this
365 to construct circuits with chosen circuit IDs, to create
366 collisions and make the hash table inefficient. Now we use a
367 SipHash construction here instead. Fixes bug 40391; bugfix on
368 0.2.4.4-alpha. This issue is also tracked as TROVE-2021-005 and
369 CVE-2021-34549. Reported by Jann Horn from Google's Project Zero.
370 - Fix an out-of-bounds memory access in v3 onion service descriptor
371 parsing. An attacker could exploit this bug by crafting an onion
372 service descriptor that would crash any client that tried to visit
373 it. Fixes bug 40392; bugfix on 0.3.0.1-alpha. This issue is also
374 tracked as TROVE-2021-006 and CVE-2021-34550. Reported by Sergei
375 Glazunov from Google's Project Zero.
377 o Minor features (compatibility, backport from 0.4.6.4-rc):
378 - Remove an assertion function related to TLS renegotiation. It was
379 used nowhere outside the unit tests, and it was breaking
380 compilation with recent alpha releases of OpenSSL 3.0.0. Closes
383 o Minor features (geoip data):
384 - Update the geoip files to match the IPFire Location Database, as
385 retrieved on 2021/06/10.
387 o Minor bugfixes (control, sandbox, backport from 0.4.6.4-rc):
388 - Allow the control command SAVECONF to succeed when the seccomp
389 sandbox is enabled, and make SAVECONF keep only one backup file to
390 simplify implementation. Previously SAVECONF allowed a large
391 number of backup files, which made it incompatible with the
392 sandbox. Fixes bug 40317; bugfix on 0.2.5.4-alpha. Patch by
395 o Minor bugfixes (metrics port, backport from 0.4.6.4-rc):
396 - Fix a bug that made tor try to re-bind() on an already open
397 MetricsPort every 60 seconds. Fixes bug 40370; bugfix
401 Changes in version 0.4.5.8 - 2021-05-10
402 Tor 0.4.5.8 fixes several bugs in earlier version, backporting fixes
403 from the 0.4.6.x series.
405 o Minor features (compatibility, Linux seccomp sandbox, backport from 0.4.6.3-rc):
406 - Add a workaround to enable the Linux sandbox to work correctly
407 with Glibc 2.33. This version of Glibc has started using the
408 fstatat() system call, which previously our sandbox did not allow.
409 Closes ticket 40382; see the ticket for a discussion of trade-offs.
411 o Minor features (compilation, backport from 0.4.6.3-rc):
412 - Make the autoconf script build correctly with autoconf versions
413 2.70 and later. Closes part of ticket 40335.
415 o Minor features (fallback directory list, backport from 0.4.6.2-alpha):
416 - Regenerate the list of fallback directories to contain a new set
417 of 200 relays. Closes ticket 40265.
419 o Minor features (geoip data):
420 - Update the geoip files to match the IPFire Location Database, as
421 retrieved on 2021/05/07.
423 o Minor features (onion services):
424 - Add warning message when connecting to now deprecated v2 onion
425 services. As announced, Tor 0.4.5.x is the last series that will
426 support v2 onions. Closes ticket 40373.
428 o Minor bugfixes (bridge, pluggable transport, backport from 0.4.6.2-alpha):
429 - Fix a regression that made it impossible start Tor using a bridge
430 line with a transport name and no fingerprint. Fixes bug 40360;
431 bugfix on 0.4.5.4-rc.
433 o Minor bugfixes (build, cross-compilation, backport from 0.4.6.3-rc):
434 - Allow a custom "ar" for cross-compilation. Our previous build
435 script had used the $AR environment variable in most places, but
436 it missed one. Fixes bug 40369; bugfix on 0.4.5.1-alpha.
438 o Minor bugfixes (channel, DoS, backport from 0.4.6.2-alpha):
439 - Fix a non-fatal BUG() message due to a too-early free of a string,
440 when listing a client connection from the DoS defenses subsystem.
441 Fixes bug 40345; bugfix on 0.4.3.4-rc.
443 o Minor bugfixes (compiler warnings, backport from 0.4.6.3-rc):
444 - Fix an indentation problem that led to a warning from GCC 11.1.1.
445 Fixes bug 40380; bugfix on 0.3.0.1-alpha.
447 o Minor bugfixes (controller, backport from 0.4.6.1-alpha):
448 - Fix a "BUG" warning that would appear when a controller chooses
449 the first hop for a circuit, and that circuit completes. Fixes bug
450 40285; bugfix on 0.3.2.1-alpha.
452 o Minor bugfixes (onion service, client, memory leak, backport from 0.4.6.3-rc):
453 - Fix a bug where an expired cached descriptor could get overwritten
454 with a new one without freeing it, leading to a memory leak. Fixes
455 bug 40356; bugfix on 0.3.5.1-alpha.
457 o Minor bugfixes (testing, BSD, backport from 0.4.6.2-alpha):
458 - Fix pattern-matching errors when patterns expand to invalid paths
459 on BSD systems. Fixes bug 40318; bugfix on 0.4.5.1-alpha. Patch by
463 Changes in version 0.4.5.7 - 2021-03-16
464 Tor 0.4.5.7 fixes two important denial-of-service bugs in earlier
467 One of these vulnerabilities (TROVE-2021-001) would allow an attacker
468 who can send directory data to a Tor instance to force that Tor
469 instance to consume huge amounts of CPU. This is easiest to exploit
470 against authorities, since anybody can upload to them, but directory
471 caches could also exploit this vulnerability against relays or clients
472 when they download. The other vulnerability (TROVE-2021-002) only
473 affects directory authorities, and would allow an attacker to remotely
474 crash the authority with an assertion failure. Patches have already
475 been provided to the authority operators, to help ensure
478 We recommend that everybody upgrade to one of the releases that fixes
479 these issues (0.3.5.14, 0.4.4.8, or 0.4.5.7) as they become available
482 This release also updates our GeoIP data source, and fixes a few
483 smaller bugs in earlier releases.
485 o Major bugfixes (security, denial of service):
486 - Disable the dump_desc() function that we used to dump unparseable
487 information to disk. It was called incorrectly in several places,
488 in a way that could lead to excessive CPU usage. Fixes bug 40286;
489 bugfix on 0.2.2.1-alpha. This bug is also tracked as TROVE-2021-
490 001 and CVE-2021-28089.
491 - Fix a bug in appending detached signatures to a pending consensus
492 document that could be used to crash a directory authority. Fixes
493 bug 40316; bugfix on 0.2.2.6-alpha. Tracked as TROVE-2021-002
496 o Minor features (geoip data):
497 - We have switched geoip data sources. Previously we shipped IP-to-
498 country mappings from Maxmind's GeoLite2, but in 2019 they changed
499 their licensing terms, so we were unable to update them after that
500 point. We now ship geoip files based on the IPFire Location
501 Database instead. (See https://location.ipfire.org/ for more
502 information). This release updates our geoip files to match the
503 IPFire Location Database as retrieved on 2021/03/12. Closes
506 o Minor bugfixes (directory authority):
507 - Now that exit relays don't allow exit connections to directory
508 authority DirPorts (to prevent network reentry), disable
509 authorities' reachability self test on the DirPort. Fixes bug
510 40287; bugfix on 0.4.5.5-rc.
512 o Minor bugfixes (documentation):
513 - Fix a formatting error in the documentation for
514 VirtualAddrNetworkIPv6. Fixes bug 40256; bugfix on 0.2.9.4-alpha.
516 o Minor bugfixes (Linux, relay):
517 - Fix a bug in determining total available system memory that would
518 have been triggered if the format of Linux's /proc/meminfo file
519 had ever changed to include "MemTotal:" in the middle of a line.
520 Fixes bug 40315; bugfix on 0.2.5.4-alpha.
522 o Minor bugfixes (metrics port):
523 - Fix a BUG() warning on the MetricsPort for an internal missing
524 handler. Fixes bug 40295; bugfix on 0.4.5.1-alpha.
526 o Minor bugfixes (onion service):
527 - Remove a harmless BUG() warning when reloading tor configured with
528 onion services. Fixes bug 40334; bugfix on 0.4.5.1-alpha.
530 o Minor bugfixes (portability):
531 - Fix a non-portable usage of "==" with "test" in the configure
532 script. Fixes bug 40298; bugfix on 0.4.5.1-alpha.
534 o Minor bugfixes (relay):
535 - Remove a spammy log notice falsely claiming that the IPv4/v6
536 address was missing. Fixes bug 40300; bugfix on 0.4.5.1-alpha.
537 - Do not query the address cache early in the boot process when
538 deciding if a relay needs to fetch early directory information
539 from an authority. This bug resulted in a relay falsely believing
540 it didn't have an address and thus triggering an authority fetch
541 at each boot. Related to our fix for 40300.
543 o Removed features (mallinfo deprecated):
544 - Remove mallinfo() usage entirely. Libc 2.33+ now deprecates it.
548 Changes in version 0.4.5.6 - 2021-02-15
549 The Tor 0.4.5.x release series is dedicated to the memory of Karsten
550 Loesing (1979-2020), Tor developer, cypherpunk, husband, and father.
551 Karsten is best known for creating the Tor metrics portal and leading
552 the metrics team, but he was involved in Tor from the early days. For
553 example, while he was still a student he invented and implemented the
554 v2 onion service directory design, and he also served as an ambassador
555 to the many German researchers working in the anonymity field. We
556 loved him and respected him for his patience, his consistency, and his
557 welcoming approach to growing our community.
559 This release series introduces significant improvements in relay IPv6
560 address discovery, a new "MetricsPort" mechanism for relay operators
561 to measure performance, LTTng support, build system improvements to
562 help when using Tor as a static library, and significant bugfixes
563 related to Windows relay performance. It also includes numerous
564 smaller features and bugfixes.
566 Below are the changes since 0.4.4.7. For a list of changes since
567 0.4.5.5-rc, see the ChangeLog file.
569 o Major features (build):
570 - When building Tor, first link all object files into a single
571 static library. This may help with embedding Tor in other
572 programs. Note that most Tor functions do not constitute a part of
573 a stable or supported API: only those functions in tor_api.h
574 should be used if embedding Tor. Closes ticket 40127.
576 o Major features (metrics):
577 - Introduce a new MetricsPort which exposes, through an HTTP
578 interface, a series of metrics that tor collects at runtime. At
579 the moment, the only supported output format is Prometheus data
580 model. Closes ticket 40063. See the manual page for more
581 information and security considerations.
583 o Major features (relay, IPv6):
584 - The torrc option Address now supports IPv6. This unifies our
585 address discovery interface to support IPv4, IPv6, and hostnames.
587 - Launch IPv4 and IPv6 ORPort self-test circuits on relays and
588 bridges. Closes ticket 33222.
589 - Relays now automatically bind on IPv6 for their ORPort, unless
590 specified otherwise with the IPv4Only flag. Closes ticket 33246.
591 - When a relay with IPv6 support is told to open a connection to
592 another relay, and the extend cell lists both IPv4 and IPv6
593 addresses, the first relay now picks randomly which address to
594 use. Closes ticket 33220.
595 - Relays now track their IPv6 ORPort reachability separately from
596 the reachability of their IPv4 ORPort. They will not publish a
597 descriptor unless _both_ ports appear to be externally reachable.
600 o Major features (tracing):
601 - Add event-tracing library support for USDT and LTTng-UST, and a
602 few tracepoints in the circuit subsystem. More will come
603 incrementally. This feature is compiled out by default: it needs
604 to be enabled at configure time. See documentation in
605 doc/HACKING/Tracing.md. Closes ticket 32910.
607 o Major bugfixes (directory cache, performance, windows):
608 - Limit the number of items in the consensus diff cache to 64 on
609 Windows. We hope this will mitigate an issue where Windows relay
610 operators reported Tor using 100% CPU, while we investigate better
611 solutions. Fixes bug 24857; bugfix on 0.3.1.1-alpha.
613 o Major bugfixes (relay, windows):
614 - Fix a bug in our implementation of condition variables on Windows.
615 Previously, a relay on Windows would use 100% CPU after running
616 for some time. Because of this change, Tor now require Windows
617 Vista or later to build and run. Fixes bug 30187; bugfix on
618 0.2.6.3-alpha. (This bug became more serious in 0.3.1.1-alpha with
619 the introduction of consensus diffs.) Patch by Daniel Pinto.
621 o Major bugfixes (TLS, buffer):
622 - When attempting to read N bytes on a TLS connection, really try to
623 read all N bytes. Previously, Tor would stop reading after the
624 first TLS record, which can be smaller than the N bytes requested,
625 and not check for more data until the next mainloop event. Fixes
626 bug 40006; bugfix on 0.1.0.5-rc.
628 o Minor features (address discovery):
629 - If no Address statements are found, relays now prioritize guessing
630 their address by looking at the local interface instead of the
631 local hostname. If the interface address can't be found, the local
632 hostname is used. Closes ticket 33238.
634 o Minor features (admin tools):
635 - Add a new --format argument to -key-expiration option to allow
636 specifying the time format of the expiration date. Adds Unix
637 timestamp format support. Patch by Daniel Pinto. Closes
640 o Minor features (authority, logging):
641 - Log more information for directory authority operators during the
642 consensus voting process, and while processing relay descriptors.
645 o Minor features (bootstrap reporting):
646 - When reporting bootstrapping status on a relay, do not consider
647 connections that have never been the target of an origin circuit.
648 Previously, all connection failures were treated as potential
649 bootstrapping failures, including connections that had been opened
650 because of client requests. Closes ticket 25061.
652 o Minor features (build):
653 - When running the configure script, try to detect version
654 mismatches between the OpenSSL headers and libraries, and suggest
655 that the user should try "--with-openssl-dir". Closes 40138.
656 - If the configure script has given any warnings, remind the user
657 about them at the end of the script. Related to 40138.
659 o Minor features (configuration):
660 - Allow using wildcards (* and ?) with the %include option on
661 configuration files. Closes ticket 25140. Patch by Daniel Pinto.
662 - Allow the configuration options EntryNodes, ExcludeNodes,
663 ExcludeExitNodes, ExitNodes, MiddleNodes, HSLayer2Nodes and
664 HSLayer3Nodes to be specified multiple times. Closes ticket 28361.
665 Patch by Daniel Pinto.
667 o Minor features (control port):
668 - Add a DROPTIMEOUTS command to drop circuit build timeout history
669 and reset the current timeout. Closes ticket 40002.
670 - When a stream enters the AP_CONN_STATE_CONTROLLER_WAIT status,
671 send a control port event. Closes ticket 32190. Patch by
673 - Introduce GETINFO "stats/ntor/{assigned/requested}" and
674 "stats/tap/{assigned/requested}" to get the NTor and TAP circuit
675 onion handshake counts respectively. Closes ticket 28279. Patch by
678 o Minor features (control port, IPv6):
679 - Tor relays now try to report to the controller when they are
680 launching an IPv6 self-test. Closes ticket 34068.
681 - Introduce "GETINFO address/v4" and "GETINFO address/v6" in the
682 control port to fetch the Tor host's respective IPv4 or IPv6
683 address. We keep "GETINFO address" for backwards-compatibility.
684 Closes ticket 40039. Patch by Neel Chauhan.
686 o Minor features (directory authorities):
687 - Add a new consensus method 30 that removes the unnecessary "="
688 padding from ntor-onion-key. Closes ticket 7869. Patch by
690 - Directory authorities now reject descriptors from relays running
691 Tor versions from the obsolete 0.4.1 series. Resolves ticket
692 34357. Patch by Neel Chauhan.
693 - The AssumeReachable option no longer stops directory authorities
694 from checking whether other relays are running. A new
695 AuthDirTestReachability option can be used to disable these
696 checks. Closes ticket 34445.
697 - When looking for possible Sybil attacks, also consider IPv6
698 addresses. Two routers are considered to have "the same" address
699 by this metric if they are in the same /64 network. Patch from
700 Maurice Pibouin. Closes ticket 7193.
702 o Minor features (directory authorities, IPv6):
703 - Make authorities add their IPv6 ORPort (if any) to the trusted
704 servers list. Authorities previously added only their IPv4
705 addresses. Closes ticket 32822.
707 o Minor features (documentation):
708 - Mention the "!badexit" directive that can appear in an authority's
709 approved-routers file, and update the description of the
710 "!invalid" directive. Closes ticket 40188.
712 o Minor features (ed25519, relay):
713 - Save a relay's base64-encoded ed25519 identity key to the data
714 directory in a file named fingerprint-ed25519. Closes ticket
715 30642. Patch by Neel Chauhan.
717 o Minor features (heartbeat):
718 - Include the total number of inbound and outbound IPv4 and IPv6
719 connections in the heartbeat message. Closes ticket 29113.
721 o Minor features (IPv6, ExcludeNodes):
722 - Handle IPv6 addresses in ExcludeNodes; previously they were
723 ignored. Closes ticket 34065. Patch by Neel Chauhan.
725 o Minor features (logging):
726 - Add the running glibc version to the log, and the compiled glibc
727 version to the library list returned when using --library-versions.
728 Patch from Daniel Pinto. Closes ticket 40047.
729 - Consider an HTTP 301 response to be an error (like a 404) when
730 processing a directory response. Closes ticket 40053.
731 - Log directory fetch statistics as a single line. Closes
733 - Provide more complete descriptions of our connections when logging
734 about them. Closes ticket 40041.
735 - When describing a relay in the logs, we now include its ed25519
736 identity. Closes ticket 22668.
738 o Minor features (onion services):
739 - Only overwrite an onion service's existing hostname file if its
740 contents are wrong. This enables read-only onion-service
741 directories. Resolves ticket 40062. Patch by Neel Chauhan.
743 o Minor features (pluggable transports):
744 - Add an OutboundBindAddressPT option to allow users to specify
745 which IPv4 and IPv6 address pluggable transports should use for
746 outgoing IP packets. Tor does not have a way to enforce that the
747 pluggable transport honors this option, so each pluggable transport
748 needs to implement support on its own. Closes ticket 5304.
750 o Minor features (protocol, proxy support, defense in depth):
751 - Respond more deliberately to misbehaving proxies that leave
752 leftover data on their connections, so as to make Tor even less
753 likely to allow the proxies to pass their data off as having come
754 from a relay. Closes ticket 40017.
756 o Minor features (relay address tracking):
757 - We now store relay addresses for OR connections in a more logical
758 way. Previously we would sometimes overwrite the actual address of
759 a connection with a "canonical address", and then store the "real
760 address" elsewhere to remember it. We now track the "canonical
761 address" elsewhere for the cases where we need it, and leave the
762 connection's address alone. Closes ticket 33898.
764 o Minor features (relay):
765 - If a relay is unable to discover its address, attempt to learn it
766 from the NETINFO cell. Closes ticket 40022.
767 - Log immediately when launching a relay self-check. Previously we
768 would try to log before launching checks, or approximately when we
769 intended to launch checks, but this tended to be error-prone.
772 o Minor features (relay, address discovery):
773 - If Address option is not found in torrc, attempt to learn our
774 address with the configured ORPort address if any. Closes
777 o Minor features (relay, IPv6):
778 - Add an AssumeReachableIPv6 option to disable self-checking IPv6
779 reachability. Closes part of ticket 33224.
780 - Add new "assume-reachable" and "assume-reachable-ipv6" consensus
781 parameters to be used in an emergency to tell relays that they
782 should publish even if they cannot complete their ORPort self-
783 checks. Closes ticket 34064 and part of 33224.
784 - Allow relays to send IPv6-only extend cells. Closes ticket 33222.
785 - Declare support for the Relay=3 subprotocol version. Closes
787 - When launching IPv6 ORPort self-test circuits, make sure that the
788 second-last hop can initiate an IPv6 extend. Closes ticket 33222.
790 o Minor features (safety):
791 - Log a warning at startup if Tor is built with compile-time options
792 that are likely to make it less stable or reliable. Closes
795 o Minor features (specification update):
796 - Several fields in microdescriptors, router descriptors, and
797 consensus documents that were formerly optional are now required.
798 Implements proposal 315; closes ticket 40132.
800 o Minor features (state management):
801 - When loading the state file, remove entries from the statefile
802 that have been obsolete for a long time. Ordinarily Tor preserves
803 unrecognized entries in order to keep forward-compatibility, but
804 these entries have not actually been used in any release since
805 before 0.3.5.x. Closes ticket 40137.
807 o Minor features (statistics, ipv6):
808 - Relays now publish IPv6-specific counts of single-direction versus
809 bidirectional relay connections. Closes ticket 33264.
810 - Relays now publish their IPv6 read and write statistics over time,
811 if statistics are enabled. Closes ticket 33263.
813 o Minor features (subprotocol versions):
814 - Use the new limitations on subprotocol versions due to proposal
815 318 to simplify our implementation. Part of ticket 40133.
817 o Minor features (testing configuration):
818 - The TestingTorNetwork option no longer implicitly sets
819 AssumeReachable to 1. This change allows us to test relays' self-
820 testing mechanisms, and to test authorities' relay-testing
821 functionality. Closes ticket 34446.
823 o Minor features (testing):
824 - Added unit tests for channel_matches_target_addr_for_extend().
825 Closes Ticket 33919. Patch by MrSquanchee.
827 o Minor bugfixes (circuit padding):
828 - When circpad_send_padding_cell_for_callback is called,
829 `is_padding_timer_scheduled` flag was not reset. Now it is set to
830 0 at the top of that function. Fixes bug 32671; bugfix
832 - Add a per-circuit padding machine instance counter, so we can
833 differentiate between shutdown requests for old machines on a
834 circuit. Fixes bug 30992; bugfix on 0.4.1.1-alpha.
835 - Add the ability to keep circuit padding machines if they match a
836 set of circuit states or purposes. This allows us to have machines
837 that start up under some conditions but don't shut down under
838 others. We now use this mask to avoid starting up introduction
839 circuit padding again after the machines have already completed.
840 Fixes bug 32040; bugfix on 0.4.1.1-alpha.
842 o Minor bugfixes (circuit, handshake):
843 - In the v3 handshaking code, use connection_or_change_state() to
844 change the state. Previously, we changed the state directly, but
845 this did not pass the state change to the pubsub or channel
846 objects, potentially leading to bugs. Fixes bug 32880; bugfix on
847 0.2.3.6-alpha. Patch by Neel Chauhan.
849 o Minor bugfixes (compilation):
850 - Change the linker flag ordering in our library search code so that
851 it works for compilers that need the libraries to be listed in the
852 right order. Fixes bug 33624; bugfix on 0.1.1.0-alpha.
853 - Fix the "--enable-static-tor" switch to properly set the "-static"
854 compile option onto the tor binary only. Fixes bug 40111; bugfix
857 o Minor bugfixes (configuration):
858 - Exit Tor on a misconfiguration when the Bridge line is configured
859 to use a transport but no corresponding ClientTransportPlugin can
860 be found. Prior to this fix, Tor would attempt to connect to the
861 bridge directly without using the transport, making it easier for
862 adversaries to notice the bridge. Fixes bug 25528; bugfix
865 o Minor bugfixes (control port):
866 - Make sure we send the SOCKS request address in relay begin cells
867 when a stream is attached with the purpose
868 CIRCUIT_PURPOSE_CONTROLLER. Fixes bug 33124; bugfix on 0.0.5.
869 Patch by Neel Chauhan.
871 o Minor bugfixes (crash, relay, signing key):
872 - Avoid assertion failures when we run Tor from the command line
873 with `--key-expiration sign`, but an ORPort is not set. Fixes bug
874 40015; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
876 o Minor bugfixes (logging):
877 - Avoid a spurious log message about missing subprotocol versions,
878 when the consensus that we're reading from is older than the
879 current release. Previously we had made this message nonfatal, but
880 in practice, it is never relevant when the consensus is older than
881 the current release. Fixes bug 40281; bugfix on 0.4.0.1-alpha.
882 - Remove trailing whitespace from control event log messages. Fixes
883 bug 32178; bugfix on 0.1.1.1-alpha. Based on a patch by
885 - Turn warning-level log message about SENDME failure into a debug-
886 level message. (This event can happen naturally, and is no reason
887 for concern). Fixes bug 40142; bugfix on 0.4.1.1-alpha.
888 - When logging a rate-limited message about how many messages have
889 been suppressed in the last N seconds, give an accurate value for
890 N, rounded up to the nearest minute. Previously we would report
891 the size of the rate-limiting interval, regardless of when the
892 messages started to occur. Fixes bug 19431; bugfix
895 o Minor bugfixes (onion services):
896 - Avoid a non-fatal assertion in certain edge-cases when
897 establishing a circuit to an onion service. Fixes bug 32666;
898 bugfix on 0.3.0.3-alpha.
900 o Minor bugfixes (rust, protocol versions):
901 - Declare support for the onion service introduction point denial of
902 service extensions when building with Rust. Fixes bug 34248;
903 bugfix on 0.4.2.1-alpha.
904 - Make Rust protocol version support checks consistent with the
905 undocumented error behavior of the corresponding C code. Fixes bug
906 34251; bugfix on 0.3.3.5-rc.
908 o Minor bugfixes (self-testing):
909 - When receiving an incoming circuit, only accept it as evidence
910 that we are reachable if the declared address of its channel is
911 the same address we think that we have. Otherwise, it could be
912 evidence that we're reachable on some other address. Fixes bug
913 20165; bugfix on 0.1.0.1-rc.
915 o Minor bugfixes (spec conformance):
916 - Use the correct key type when generating signing->link
917 certificates. Fixes bug 40124; bugfix on 0.2.7.2-alpha.
919 o Minor bugfixes (subprotocol versions):
920 - Consistently reject extra commas, instead of only rejecting
921 leading commas. Fixes bug 27194; bugfix on 0.2.9.4-alpha.
922 - In summarize_protover_flags(), treat empty strings the same as
923 NULL. This prevents protocols_known from being set. Previously, we
924 treated empty strings as normal strings, which led to
925 protocols_known being set. Fixes bug 34232; bugfix on
926 0.3.3.2-alpha. Patch by Neel Chauhan.
928 o Code simplification and refactoring:
929 - Add and use a set of functions to perform down-casts on constant
930 connection and channel pointers. Closes ticket 40046.
931 - Refactor our code that logs descriptions of connections, channels,
932 and the peers on them, to use a single call path. This change
933 enables us to refactor the data types that they use, and eliminates
934 many confusing usages of those types. Closes ticket 40041.
935 - Refactor some common node selection code into a single function.
937 - Remove the now-redundant 'outbuf_flushlen' field from our
938 connection type. It was previously used for an older version of
939 our rate-limiting logic. Closes ticket 33097.
940 - Rename "fascist_firewall_*" identifiers to "reachable_addr_*"
941 instead, for consistency with other code. Closes ticket 18106.
942 - Rename functions about "advertised" ports which are not in fact
943 guaranteed to return the ports that have been advertised. Closes
945 - Split implementation of several command line options from
946 options_init_from_torrc into smaller isolated functions. Patch by
947 Daniel Pinto. Closes ticket 40102.
948 - When an extend cell is missing an IPv4 or IPv6 address, fill in
949 the address from the extend info. This is similar to what was done
950 in ticket 33633 for ed25519 keys. Closes ticket 33816. Patch by
953 o Deprecated features:
954 - The "non-builtin" argument to the "--dump-config" command is now
955 deprecated. When it works, it behaves the same as "short", which
956 you should use instead. Closes ticket 33398.
959 - Replace URLs from our old bugtracker so that they refer to the new
960 bugtracker and wiki. Closes ticket 40101.
963 - We no longer ship or build a "tor.service" file for use with
964 systemd. No distribution included this script unmodified, and we
965 don't have the expertise ourselves to maintain this in a way that
966 all the various systemd-based distributions can use. Closes
968 - We no longer ship support for the Android logging API. Modern
969 versions of Android can use the syslog API instead. Closes
971 - The "optimistic data" feature is now always on; there is no longer
972 an option to disable it from the torrc file or from the consensus
973 directory. Closes part of 40139.
974 - The "usecreatefast" network parameter is now removed; there is no
975 longer an option for authorities to turn it off. Closes part
979 - Add unit tests for bandwidth statistics manipulation functions.
980 Closes ticket 33812. Patch by MrSquanchee.
982 o Code simplification and refactoring (autoconf):
983 - Remove autoconf checks for unused funcs and headers. Closes ticket
984 31699; Patch by @bduszel
986 o Code simplification and refactoring (maintainer scripts):
987 - Disable by default the pre-commit hook. Use the environment
988 variable TOR_EXTRA_PRE_COMMIT_CHECKS in order to run it.
989 Furthermore, stop running practracker in the pre-commit hook and
990 make check-local. Closes ticket 40019.
992 o Code simplification and refactoring (relay address):
993 - Most of IPv4 representation was using "uint32_t". It has now been
994 moved to use the internal "tor_addr_t" interface instead. This is
995 so we can properly integrate IPv6 along IPv4 with common
996 interfaces. Closes ticket 40043.
998 o Documentation (manual page):
999 - Move them from doc/ to doc/man/. Closes ticket 40044.
1000 - Describe the status of the "Sandbox" option more accurately. It is
1001 no longer "experimental", but it _is_ dependent on kernel and libc
1002 versions. Closes ticket 23378.
1004 o Documentation (tracing):
1005 - Document in depth the circuit subsystem trace events in the new
1006 doc/tracing/EventsCircuit.md. Closes ticket 40036.
1008 o Removed features (controller):
1009 - Remove the "GETINFO network-status" controller command. It has
1010 been deprecated since 0.3.1.1-alpha. Closes ticket 22473.
1013 Changes in version 0.4.4.6 - 2020-11-12
1014 Tor 0.4.4.6 is the second stable release in the 0.4.4.x series. It
1015 backports fixes from later releases, including a fix for TROVE-2020-
1016 005, a security issue that could be used, under certain cases, by an
1017 adversary to observe traffic patterns on a limited number of circuits
1018 intended for a different relay.
1020 o Major bugfixes (security, backport from 0.4.5.1-alpha):
1021 - When completing a channel, relays now check more thoroughly to
1022 make sure that it matches any pending circuits before attaching
1023 those circuits. Previously, address correctness and Ed25519
1024 identities were not checked in this case, but only when extending
1025 circuits on an existing channel. Fixes bug 40080; bugfix on
1026 0.2.7.2-alpha. Resolves TROVE-2020-005.
1028 o Minor features (directory authorities, backport from 0.4.5.1-alpha):
1029 - Authorities now list a different set of protocols as required and
1030 recommended. These lists have been chosen so that only truly
1031 recommended and/or required protocols are included, and so that
1032 clients using 0.2.9 or later will continue to work (even though
1033 they are not supported), whereas only relays running 0.3.5 or
1034 later will meet the requirements. Closes ticket 40162.
1035 - Make it possible to specify multiple ConsensusParams torrc lines.
1036 Now directory authority operators can for example put the main
1037 ConsensusParams config in one torrc file and then add to it from a
1038 different torrc file. Closes ticket 40164.
1040 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
1041 - Tor no longer allows subprotocol versions larger than 63.
1042 Previously version numbers up to UINT32_MAX were allowed, which
1043 significantly complicated our code. Implements proposal 318;
1044 closes ticket 40133.
1046 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
1047 - Fix a rendezvous cache unit test that was triggering an underflow
1048 on the global rend cache allocation. Fixes bug 40125; bugfix
1050 - Fix another rendezvous cache unit test that was triggering an
1051 underflow on the global rend cache allocation. Fixes bug 40126;
1052 bugfix on 0.2.8.1-alpha.
1054 o Minor bugfixes (compilation, backport from 0.4.5.1-alpha):
1055 - Fix compiler warnings that would occur when building with
1056 "--enable-all-bugs-are-fatal" and "--disable-module-relay" at the
1057 same time. Fixes bug 40129; bugfix on 0.4.4.1-alpha.
1058 - Resolve a compilation warning that could occur in
1059 test_connection.c. Fixes bug 40113; bugfix on 0.2.9.3-alpha.
1061 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
1062 - Remove a debug logging statement that uselessly spammed the logs.
1063 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
1065 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
1066 - Avoid a fatal assert() when failing to create a listener
1067 connection for an address that was in use. Fixes bug 40073; bugfix
1070 o Minor bugfixes (v2 onion services, backport from 0.4.5.1-alpha):
1071 - For HSFETCH commands on v2 onion services addresses, check the
1072 length of bytes decoded, not the base32 length. Fixes bug 34400;
1073 bugfix on 0.4.1.1-alpha. Patch by Neel Chauhan.
1076 Changes in version 0.4.3.7 - 2020-11-12
1077 Tor 0.4.3.7 backports several bugfixes from later releases. It
1078 includes a fix for TROVE-2020-005, a security issue that could be
1079 used, under certain cases, by an adversary to observe traffic patterns
1080 on a limited number of circuits intended for a different relay.
1082 Please be aware that support for the 0.4.3.x series will end on 15
1083 February 2021. Please upgrade to 0.4.4.x or 0.4.5.x before then, or
1084 downgrade to 0.3.5.x, which will be supported until at least 1
1087 o Major features (fallback directory list, backport form 0.4.4.3-alpha):
1088 - Replace the 148 fallback directories originally included in Tor
1089 0.4.1.4-rc (of which around 105 are still functional) with a list
1090 of 144 fallbacks generated in July 2020. Closes ticket 40061.
1092 o Major bugfixes (security, backport from 0.4.5.1-alpha):
1093 - When completing a channel, relays now check more thoroughly to
1094 make sure that it matches any pending circuits before attaching
1095 those circuits. Previously, address correctness and Ed25519
1096 identities were not checked in this case, but only when extending
1097 circuits on an existing channel. Fixes bug 40080; bugfix on
1098 0.2.7.2-alpha. Resolves TROVE-2020-005.
1100 o Major bugfixes (NSS, backport from 0.4.4.3-alpha):
1101 - When running with NSS enabled, make sure that NSS knows to expect
1102 nonblocking sockets. Previously, we set our TCP sockets as
1103 nonblocking, but did not tell NSS, which in turn could lead to
1104 unexpected blocking behavior. Fixes bug 40035; bugfix
1107 o Minor features (security, backport from 0.4.4.4-rc):
1108 - Channels using obsolete versions of the Tor link protocol are no
1109 longer allowed to circumvent address-canonicity checks. (This is
1110 only a minor issue, since such channels have no way to set ed25519
1111 keys, and therefore should always be rejected for circuits that
1112 specify ed25519 identities.) Closes ticket 40081.
1114 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
1115 - Tor no longer allows subprotocol versions larger than 63.
1116 Previously version numbers up to UINT32_MAX were allowed, which
1117 significantly complicated our code. Implements proposal 318;
1118 closes ticket 40133.
1120 o Minor features (tests, backport from 0.4.4.5):
1121 - Our "make check" target now runs the unit tests in 8 parallel
1122 chunks. Doing this speeds up hardened CI builds by more than a
1123 factor of two. Closes ticket 40098.
1125 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
1126 - Fix a rendezvous cache unit test that was triggering an underflow
1127 on the global rend cache allocation. Fixes bug 40125; bugfix
1129 - Fix another rendezvous cache unit test that was triggering an
1130 underflow on the global rend cache allocation. Fixes bug 40126;
1131 bugfix on 0.2.8.1-alpha.
1133 o Minor bugfixes (correctness, buffers, backport from 0.4.4.4-rc):
1134 - Fix a correctness bug that could cause an assertion failure if we
1135 ever tried using the buf_move_all() function with an empty input
1136 buffer. As far as we know, no released versions of Tor do this.
1137 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
1139 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
1140 - Remove a debug logging statement that uselessly spammed the logs.
1141 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
1143 o Minor bugfixes (rate limiting, bridges, pluggable transports, backport from 0.4.4.4-rc):
1144 - On a bridge, treat all connections from an ExtORPort as remote by
1145 default for the purposes of rate-limiting. Previously, bridges
1146 would treat the connection as local unless they explicitly
1147 received a "USERADDR" command. ExtORPort connections still count
1148 as local if there is a USERADDR command with an explicit local
1149 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
1151 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
1152 - Avoid a fatal assert() when failing to create a listener
1153 connection for an address that was in use. Fixes bug 40073; bugfix
1156 o Minor bugfixes (relay, usability, backport from 0.4.4.3-alpha):
1157 - Adjust the rules for when to warn about having too many
1158 connections to other relays. Previously we'd tolerate up to 1.5
1159 connections per relay on average. Now we tolerate more connections
1160 for directory authorities, and raise the number of total
1161 connections we need to see before we warn. Fixes bug 33880; bugfix
1164 o Minor bugfixes (tests, 0.4.4.5):
1165 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
1166 on its own. Previously, it would exit with an error. Fixes bug
1167 40099; bugfix on 0.2.8.1-alpha.
1169 o Minor bugfixes (v2 onion services, backport from 0.4.5.1-alpha):
1170 - For HSFETCH commands on v2 onion services addresses, check the
1171 length of bytes decoded, not the base32 length. Fixes bug 34400;
1172 bugfix on 0.4.1.1-alpha. Patch by Neel Chauhan.
1174 o Minor bugfixes (windows, backport from 0.4.4.4-rc):
1175 - Fix a bug that prevented Tor from starting if its log file grew
1176 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
1178 o Deprecated features (onion service v2, backport form 0.4.4.2-alpha):
1179 - Add a deprecation warning for version 2 onion services. Closes
1182 o Removed features (backport from 0.4.4.3-alpha):
1183 - Our "check-local" test target no longer tries to use the
1184 Coccinelle semantic patching tool parse all the C files. While it
1185 is a good idea to try to make sure Coccinelle works on our C
1186 before we run a Coccinelle patch, doing so on every test run has
1187 proven to be disruptive. You can still run this tool manually with
1188 "make check-cocci". Closes ticket 40030. ticket 40030.
1191 Changes in version 0.3.5.12 - 2020-11-12
1192 Tor 0.4.3.7 backports several bugfixes from later releases. It
1193 includes a fix for TROVE-2020-005, a security issue that could be
1194 used, under certain cases, by an adversary to observe traffic patterns
1195 on a limited number of circuits intended for a different relay.
1197 o Major features (fallback directory list, backport form 0.4.4.3-alpha):
1198 - Replace the 148 fallback directories originally included in Tor
1199 0.4.1.4-rc (of which around 105 are still functional) with a list
1200 of 144 fallbacks generated in July 2020. Closes ticket 40061.
1202 o Major bugfixes (security, backport from 0.4.5.1-alpha):
1203 - When completing a channel, relays now check more thoroughly to
1204 make sure that it matches any pending circuits before attaching
1205 those circuits. Previously, address correctness and Ed25519
1206 identities were not checked in this case, but only when extending
1207 circuits on an existing channel. Fixes bug 40080; bugfix on
1208 0.2.7.2-alpha. Resolves TROVE-2020-005.
1210 o Major bugfixes (NSS, backport from 0.4.4.3-alpha):
1211 - When running with NSS enabled, make sure that NSS knows to expect
1212 nonblocking sockets. Previously, we set our TCP sockets as
1213 nonblocking, but did not tell NSS, which in turn could lead to
1214 unexpected blocking behavior. Fixes bug 40035; bugfix
1217 o Minor features (security, backport from 0.4.4.4-rc):
1218 - Channels using obsolete versions of the Tor link protocol are no
1219 longer allowed to circumvent address-canonicity checks. (This is
1220 only a minor issue, since such channels have no way to set ed25519
1221 keys, and therefore should always be rejected for circuits that
1222 specify ed25519 identities.) Closes ticket 40081.
1224 o Minor features (debugging, directory system):
1225 - Don't crash when we find a non-guard with a guard-fraction value
1226 set. Instead, log a bug warning, in an attempt to figure out how
1227 this happened. Diagnostic for ticket 32868.
1229 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
1230 - Tor no longer allows subprotocol versions larger than 63.
1231 Previously version numbers up to UINT32_MAX were allowed, which
1232 significantly complicated our code. Implements proposal 318;
1233 closes ticket 40133.
1235 o Minor features (tests, backport from 0.4.4.5):
1236 - Our "make check" target now runs the unit tests in 8 parallel
1237 chunks. Doing this speeds up hardened CI builds by more than a
1238 factor of two. Closes ticket 40098.
1240 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
1241 - Fix a rendezvous cache unit test that was triggering an underflow
1242 on the global rend cache allocation. Fixes bug 40125; bugfix
1244 - Fix another rendezvous cache unit test that was triggering an
1245 underflow on the global rend cache allocation. Fixes bug 40126;
1246 bugfix on 0.2.8.1-alpha.
1248 o Minor bugfixes (correctness, buffers, backport from 0.4.4.4-rc):
1249 - Fix a correctness bug that could cause an assertion failure if we
1250 ever tried using the buf_move_all() function with an empty input
1251 buffer. As far as we know, no released versions of Tor do this.
1252 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
1254 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
1255 - Remove a debug logging statement that uselessly spammed the logs.
1256 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
1258 o Minor bugfixes (rate limiting, bridges, pluggable transports, backport from 0.4.4.4-rc):
1259 - On a bridge, treat all connections from an ExtORPort as remote by
1260 default for the purposes of rate-limiting. Previously, bridges
1261 would treat the connection as local unless they explicitly
1262 received a "USERADDR" command. ExtORPort connections still count
1263 as local if there is a USERADDR command with an explicit local
1264 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
1266 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
1267 - Avoid a fatal assert() when failing to create a listener
1268 connection for an address that was in use. Fixes bug 40073; bugfix
1271 o Minor bugfixes (relay, usability, backport from 0.4.4.3-alpha):
1272 - Adjust the rules for when to warn about having too many
1273 connections to other relays. Previously we'd tolerate up to 1.5
1274 connections per relay on average. Now we tolerate more connections
1275 for directory authorities, and raise the number of total
1276 connections we need to see before we warn. Fixes bug 33880; bugfix
1279 o Minor bugfixes (relays, backport from 0.4.4.1-alpha):
1280 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
1281 descriptors, when the IPv6 port was configured as "auto". Fixes
1282 bug 32588; bugfix on 0.2.3.9-alpha.
1284 o Minor bugfixes (tests, 0.4.4.5):
1285 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
1286 on its own. Previously, it would exit with an error. Fixes bug
1287 40099; bugfix on 0.2.8.1-alpha.
1289 o Minor bugfixes (windows, backport from 0.4.4.4-rc):
1290 - Fix a bug that prevented Tor from starting if its log file grew
1291 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
1293 o Deprecated features (onion service v2, backport form 0.4.4.2-alpha):
1294 - Add a deprecation warning for version 2 onion services. Closes
1297 Changes in version 0.4.4.5 - 2020-09-15
1298 Tor 0.4.4.5 is the first stable release in the 0.4.4.x series. This
1299 series improves our guard selection algorithms, adds v3 onion balance
1300 support, improves the amount of code that can be disabled when running
1301 without relay support, and includes numerous small bugfixes and
1302 enhancements. It also lays the ground for some IPv6 features that
1303 we'll be developing more in the next (0.4.5) series.
1305 Per our support policy, we support each stable release series for nine
1306 months after its first stable release, or three months after the first
1307 stable release of the next series: whichever is longer. This means
1308 that 0.4.4.x will be supported until around June 2021--or later, if
1309 0.4.5.x is later than anticipated.
1311 Note also that support for 0.4.2.x has just ended; support for 0.4.3
1312 will continue until Feb 15, 2021. We still plan to continue supporting
1313 0.3.5.x, our long-term stable series, until Feb 2022.
1315 Below are the changes since 0.4.3.6-rc. For a complete list of changes
1316 since 0.4.4.4-rc, see the ChangeLog file.
1318 o Major features (Proposal 310, performance + security):
1319 - Implements Proposal 310, "Bandaid on guard selection". Proposal
1320 310 solves load-balancing issues with older versions of the guard
1321 selection algorithm, and improves its security. Under this new
1322 algorithm, a newly selected guard never becomes Primary unless all
1323 previously sampled guards are unreachable. Implements
1324 recommendation from 32088. (Proposal 310 is linked to the CLAPS
1325 project researching optimal client location-aware path selections.
1326 This project is a collaboration between the UCLouvain Crypto Group,
1327 the U.S. Naval Research Laboratory, and Princeton University.)
1329 o Major features (fallback directory list):
1330 - Replace the 148 fallback directories originally included in Tor
1331 0.4.1.4-rc (of which around 105 are still functional) with a list
1332 of 144 fallbacks generated in July 2020. Closes ticket 40061.
1334 o Major features (IPv6, relay):
1335 - Consider IPv6-only EXTEND2 cells valid on relays. Log a protocol
1336 warning if the IPv4 or IPv6 address is an internal address, and
1337 internal addresses are not allowed. But continue to use the other
1338 address, if it is valid. Closes ticket 33817.
1339 - If a relay can extend over IPv4 and IPv6, and both addresses are
1340 provided, it chooses between them uniformly at random. Closes
1342 - Re-use existing IPv6 connections for circuit extends. Closes
1344 - Relays may extend circuits over IPv6, if the relay has an IPv6
1345 ORPort, and the client supplies the other relay's IPv6 ORPort in
1346 the EXTEND2 cell. IPv6 extends will be used by the relay IPv6
1347 ORPort self-tests in 33222. Closes ticket 33817.
1349 o Major features (v3 onion services):
1350 - Allow v3 onion services to act as OnionBalance backend instances,
1351 by using the HiddenServiceOnionBalanceInstance torrc option.
1352 Closes ticket 32709.
1354 o Major bugfixes (NSS):
1355 - When running with NSS enabled, make sure that NSS knows to expect
1356 nonblocking sockets. Previously, we set our TCP sockets as
1357 nonblocking, but did not tell NSS, which in turn could lead to
1358 unexpected blocking behavior. Fixes bug 40035; bugfix
1361 o Major bugfixes (onion services, DoS):
1362 - Correct handling of parameters for the onion service DoS defense.
1363 Previously, the consensus parameters for the onion service DoS
1364 defenses were overwriting the parameters set by the service
1365 operator using HiddenServiceEnableIntroDoSDefense. Fixes bug
1366 40109; bugfix on 0.4.2.1-alpha.
1368 o Major bugfixes (stats, onion services):
1369 - Fix a bug where we were undercounting the Tor network's total
1370 onion service traffic, by ignoring any traffic originating from
1371 clients. Now we count traffic from both clients and services.
1372 Fixes bug 40117; bugfix on 0.2.6.2-alpha.
1374 o Minor features (security):
1375 - Channels using obsolete versions of the Tor link protocol are no
1376 longer allowed to circumvent address-canonicity checks. (This is
1377 only a minor issue, since such channels have no way to set ed25519
1378 keys, and therefore should always be rejected for circuits that
1379 specify ed25519 identities.) Closes ticket 40081.
1381 o Minor features (bootstrap reporting):
1382 - Report more detailed reasons for bootstrap failure when the
1383 failure happens due to a TLS error. Previously we would just call
1384 these errors "MISC" when they happened during read, and "DONE"
1385 when they happened during any other TLS operation. Closes
1388 o Minor features (client-only compilation):
1389 - Disable more code related to the ext_orport protocol when
1390 compiling without support for relay mode. Closes ticket 33368.
1391 - Disable more of our self-testing code when support for relay mode
1392 is disabled. Closes ticket 33370.
1393 - Most server-side DNS code is now disabled when building without
1394 support for relay mode. Closes ticket 33366.
1396 o Minor features (code safety):
1397 - Check for failures of tor_inet_ntop() and tor_inet_ntoa()
1398 functions in DNS and IP address processing code, and adjust
1399 codepaths to make them less likely to crash entire Tor instances.
1400 Resolves issue 33788.
1402 o Minor features (continuous integration):
1403 - Run unit-test and integration test (Stem, Chutney) jobs with
1404 ALL_BUGS_ARE_FATAL macro being enabled on Travis and Appveyor.
1405 Resolves ticket 32143.
1407 o Minor features (control port):
1408 - If a ClientName was specified in ONION_CLIENT_AUTH_ADD for an
1409 onion service, display it when we use ONION_CLIENT_AUTH_VIEW.
1410 Closes ticket 40089. Patch by Neel Chauhan.
1411 - Return a descriptive error message from the 'GETINFO status/fresh-
1412 relay-descs' command on the control port. Previously, we returned
1413 a generic error of "Error generating descriptor". Closes ticket
1414 32873. Patch by Neel Chauhan.
1416 o Minor features (defense in depth):
1417 - Wipe more data from connection address fields before returning
1418 them to the memory heap. Closes ticket 6198.
1420 o Minor features (denial-of-service memory limiter):
1421 - Allow the user to configure even lower values for the
1422 MaxMemInQueues parameter. Relays now enforce a minimum of 64 MB,
1423 when previously the minimum was 256 MB. On clients, there is no
1424 minimum. Relays and clients will both warn if the value is set so
1425 low that Tor is likely to stop working. Closes ticket 24308.
1427 o Minor features (developer tooling):
1428 - Add a script to help check the alphabetical ordering of option
1429 names in the manual page. Closes ticket 33339.
1430 - Refrain from listing all .a files that are generated by the Tor
1431 build in .gitignore. Add a single wildcard *.a entry that covers
1432 all of them for present and future. Closes ticket 33642.
1433 - Add a script ("git-install-tools.sh") to install git hooks and
1434 helper scripts. Closes ticket 33451.
1436 o Minor features (directory authority):
1437 - Authorities now recommend the protocol versions that are supported
1438 by Tor 0.3.5 and later. (Earlier versions of Tor have been
1439 deprecated since January of this year.) This recommendation will
1440 cause older clients and relays to give a warning on startup, or
1441 when they download a consensus directory. Closes ticket 32696.
1443 o Minor features (directory authority, shared random):
1444 - Refactor more authority-only parts of the shared-random scheduling
1445 code to reside in the dirauth module, and to be disabled when
1446 compiling with --disable-module-dirauth. Closes ticket 33436.
1448 o Minor features (directory):
1449 - Remember the number of bytes we have downloaded for each directory
1450 purpose while bootstrapping, and while fully bootstrapped. Log
1451 this information as part of the heartbeat message. Closes
1454 o Minor features (entry guards):
1455 - Reinstate support for GUARD NEW/UP/DOWN control port events.
1456 Closes ticket 40001.
1458 o Minor features (IPv6 support):
1459 - Adds IPv6 support to tor_addr_is_valid(). Adds tests for the above
1460 changes and tor_addr_is_null(). Closes ticket 33679. Patch
1462 - Allow clients and relays to send dual-stack and IPv6-only EXTEND2
1463 cells. Parse dual-stack and IPv6-only EXTEND2 cells on relays.
1464 Closes ticket 33901.
1466 o Minor features (linux seccomp2 sandbox, portability):
1467 - Allow Tor to build on platforms where it doesn't know how to
1468 report which syscall caused the linux seccomp2 sandbox to fail.
1469 This change should make the sandbox code more portable to less
1470 common Linux architectures. Closes ticket 34382.
1471 - Permit the unlinkat() syscall, which some Libc implementations use
1472 to implement unlink(). Closes ticket 33346.
1474 o Minor features (logging):
1475 - When trying to find our own address, add debug-level logging to
1476 report the sources of candidate addresses. Closes ticket 32888.
1478 o Minor features (onion service client, SOCKS5):
1479 - Add 3 new SocksPort ExtendedErrors (F2, F3, F7) that reports back
1480 new type of onion service connection failures. The semantics of
1481 these error codes are documented in proposal 309. Closes
1484 o Minor features (onion service v3):
1485 - If a service cannot upload its descriptor(s), log why at INFO
1486 level. Closes ticket 33400; bugfix on 0.3.2.1-alpha.
1488 o Minor features (python scripts):
1489 - Stop assuming that /usr/bin/python exists. Instead of using a
1490 hardcoded path in scripts that still use Python 2, use
1491 /usr/bin/env, similarly to the scripts that use Python 3. Fixes
1492 bug 33192; bugfix on 0.4.2.
1494 o Minor features (testing, architecture):
1495 - Our test scripts now double-check that subsystem initialization
1496 order is consistent with the inter-module dependencies established
1497 by our .may_include files. Implements ticket 31634.
1498 - Initialize all subsystems at the beginning of our unit test
1499 harness, to avoid crashes due to uninitialized subsystems. Follow-
1500 up from ticket 33316.
1501 - Our "make check" target now runs the unit tests in 8 parallel
1502 chunks. Doing this speeds up hardened CI builds by more than a
1503 factor of two. Closes ticket 40098.
1505 o Minor features (v3 onion services):
1506 - Add v3 onion service status to the dumpstats() call which is
1507 triggered by a SIGUSR1 signal. Previously, we only did v2 onion
1508 services. Closes ticket 24844. Patch by Neel Chauhan.
1510 o Minor features (windows):
1511 - Add support for console control signals like Ctrl+C in Windows.
1512 Closes ticket 34211. Patch from Damon Harris (TheDcoder).
1514 o Minor bugfixes (control port, onion service):
1515 - Consistently use 'address' in "Invalid v3 address" response to
1516 ONION_CLIENT_AUTH commands. Previously, we would sometimes say
1517 'addr'. Fixes bug 40005; bugfix on 0.4.3.1-alpha.
1519 o Minor bugfixes (correctness, buffers):
1520 - Fix a correctness bug that could cause an assertion failure if we
1521 ever tried using the buf_move_all() function with an empty input
1522 buffer. As far as we know, no released versions of Tor do this.
1523 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
1525 o Minor bugfixes (directory authorities):
1526 - Directory authorities now reject votes that arrive too late. In
1527 particular, once an authority has started fetching missing votes,
1528 it no longer accepts new votes posted by other authorities. This
1529 change helps prevent a consensus split, where only some authorities
1530 have the late vote. Fixes bug 4631; bugfix on 0.2.0.5-alpha.
1532 o Minor bugfixes (git scripts):
1533 - Stop executing the checked-out pre-commit hook from the pre-push
1534 hook. Instead, execute the copy in the user's git directory. Fixes
1535 bug 33284; bugfix on 0.4.1.1-alpha.
1537 o Minor bugfixes (initialization):
1538 - Initialize the subsystems in our code in an order more closely
1539 corresponding to their dependencies, so that every system is
1540 initialized before the ones that (theoretically) depend on it.
1541 Fixes bug 33316; bugfix on 0.4.0.1-alpha.
1543 o Minor bugfixes (IPv4, relay):
1544 - Check for invalid zero IPv4 addresses and ports when sending and
1545 receiving extend cells. Fixes bug 33900; bugfix on 0.2.4.8-alpha.
1547 o Minor bugfixes (IPv6, relay):
1548 - Consider IPv6 addresses when checking if a connection is
1549 canonical. In 17604, relays assumed that a remote relay could
1550 consider an IPv6 connection canonical, but did not set the
1551 canonical flag on their side of the connection. Fixes bug 33899;
1552 bugfix on 0.3.1.1-alpha.
1553 - Log IPv6 addresses on connections where this relay is the
1554 responder. Previously, responding relays would replace the remote
1555 IPv6 address with the IPv4 address from the consensus. Fixes bug
1556 33899; bugfix on 0.3.1.1-alpha.
1558 o Minor bugfixes (linux seccomp2 sandbox):
1559 - Fix a regression on sandboxing rules for the openat() syscall. The
1560 fix for bug 25440 fixed the problem on systems with glibc >= 2.27
1561 but broke with versions of glibc. We now choose a rule based on
1562 the glibc version. Patch from Daniel Pinto. Fixes bug 27315;
1564 - Makes the seccomp sandbox allow the correct syscall for opendir
1565 according to the running glibc version. This fixes crashes when
1566 reloading torrc with sandbox enabled when running on glibc 2.15 to
1567 2.21 and 2.26. Patch from Daniel Pinto. Fixes bug 40020; bugfix
1570 o Minor bugfixes (logging, testing):
1571 - Make all of tor's assertion macros support the ALL_BUGS_ARE_FATAL
1572 and DISABLE_ASSERTS_IN_UNIT_TESTS debugging modes. (IF_BUG_ONCE()
1573 used to log a non-fatal warning, regardless of the debugging
1574 mode.) Fixes bug 33917; bugfix on 0.2.9.1-alpha.
1575 - Remove surprising empty line in the INFO-level log about circuit
1576 build timeout. Fixes bug 33531; bugfix on 0.3.3.1-alpha.
1578 o Minor bugfixes (mainloop):
1579 - Better guard against growing a buffer past its maximum 2GB in
1580 size. Fixes bug 33131; bugfix on 0.3.0.4-rc.
1582 o Minor bugfixes (onion service v3 client):
1583 - Remove a BUG() warning that could occur naturally. Fixes bug
1584 34087; bugfix on 0.3.2.1-alpha.
1586 o Minor bugfixes (onion service, logging):
1587 - Fix a typo in a log message PublishHidServDescriptors is set to 0.
1588 Fixes bug 33779; bugfix on 0.3.2.1-alpha.
1590 o Minor bugfixes (onion services v3):
1591 - Avoid a non-fatal assertion failure in certain edge-cases when
1592 opening an intro circuit as a client. Fixes bug 34084; bugfix
1595 o Minor bugfixes (protocol versions):
1596 - Sort tor's supported protocol version lists, as recommended by the
1597 tor directory specification. Fixes bug 33285; bugfix
1600 o Minor bugfixes (rate limiting, bridges, pluggable transports):
1601 - On a bridge, treat all connections from an ExtORPort as remote by
1602 default for the purposes of rate-limiting. Previously, bridges
1603 would treat the connection as local unless they explicitly
1604 received a "USERADDR" command. ExtORPort connections still count
1605 as local if there is a USERADDR command with an explicit local
1606 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
1608 o Minor bugfixes (refactoring):
1609 - Lift circuit_build_times_disabled() out of the
1610 circuit_expire_building() loop, to save CPU time when there are
1611 many circuits open. Fixes bug 33977; bugfix on 0.3.5.9.
1613 o Minor bugfixes (relay, self-testing):
1614 - When starting up as a relay, if we haven't been able to verify
1615 that we're reachable, only launch reachability tests at most once
1616 a minute. Previously, we had been launching tests up to once a
1617 second, which was needlessly noisy. Fixes bug 40083; bugfix
1620 o Minor bugfixes (relay, usability):
1621 - Adjust the rules for when to warn about having too many
1622 connections to other relays. Previously we'd tolerate up to 1.5
1623 connections per relay on average. Now we tolerate more connections
1624 for directory authorities, and raise the number of total
1625 connections we need to see before we warn. Fixes bug 33880; bugfix
1628 o Minor bugfixes (SOCKS, onion service client):
1629 - Detect v3 onion service addresses of the wrong length when
1630 returning the F6 ExtendedErrors code. Fixes bug 33873; bugfix
1633 o Minor bugfixes (tests):
1634 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
1635 on its own. Previously, it would exit with an error. Fixes bug
1636 40099; bugfix on 0.2.8.1-alpha.
1638 o Minor bugfixes (v3 onion services):
1639 - Remove a BUG() warning that could trigger in certain unlikely
1640 edge-cases. Fixes bug 34086; bugfix on 0.3.2.1-alpha.
1641 - Remove a BUG() that was causing a stacktrace when a descriptor
1642 changed at an unexpected time. Fixes bug 28992; bugfix
1645 o Minor bugfixes (windows):
1646 - Fix a bug that prevented Tor from starting if its log file grew
1647 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
1649 o Code simplification and refactoring:
1650 - Define and use a new constant TOR_ADDRPORT_BUF_LEN which is like
1651 TOR_ADDR_BUF_LEN but includes enough space for an IP address,
1652 brackets, separating colon, and port number. Closes ticket 33956.
1653 Patch by Neel Chauhan.
1654 - Merge the orconn and ocirc events into the "core" subsystem, which
1655 manages or connections and origin circuits. Previously they were
1656 isolated in subsystems of their own.
1657 - Move LOG_PROTOCOL_WARN to app/config. Resolves a dependency
1658 inversion. Closes ticket 33633.
1659 - Move the circuit extend code to the relay module. Split the
1660 circuit extend function into smaller functions. Closes
1662 - Rewrite port_parse_config() to use the default port flags from
1663 port_cfg_new(). Closes ticket 32994. Patch by MrSquanchee.
1664 - Updated comments in 'scheduler.c' to reflect old code changes, and
1665 simplified the scheduler channel state change code. Closes
1667 - Refactor configuration parsing to use the new config subsystem
1668 code. Closes ticket 33014.
1669 - Move a series of functions related to address resolving into their
1670 own files. Closes ticket 33789.
1673 - Replace most http:// URLs in our code and documentation with
1674 https:// URLs. (We have left unchanged the code in src/ext/, and
1675 the text in LICENSE.) Closes ticket 31812. Patch from Jeremy Rand.
1676 - Document the limitations of using %include on config files with
1677 seccomp sandbox enabled. Fixes documentation bug 34133; bugfix on
1678 0.3.1.1-alpha. Patch by Daniel Pinto.
1681 - Our "check-local" test target no longer tries to use the
1682 Coccinelle semantic patching tool parse all the C files. While it
1683 is a good idea to try to make sure Coccinelle works on our C
1684 before we run a Coccinelle patch, doing so on every test run has
1685 proven to be disruptive. You can still run this tool manually with
1686 "make check-cocci". Closes ticket 40030.
1687 - Remove the ClientAutoIPv6ORPort option. This option attempted to
1688 randomly choose between IPv4 and IPv6 for client connections, and
1689 wasn't a true implementation of Happy Eyeballs. Often, this option
1690 failed on IPv4-only or IPv6-only connections. Closes ticket 32905.
1691 Patch by Neel Chauhan.
1692 - Stop shipping contrib/dist/rc.subr file, as it is not being used
1693 on FreeBSD anymore. Closes issue 31576.
1696 - Add a basic IPv6 test to "make test-network". This test only runs
1697 when the local machine has an IPv6 stack. Closes ticket 33300.
1698 - Add test-network-ipv4 and test-network-ipv6 jobs to the Makefile.
1699 These jobs run the IPv4-only and dual-stack chutney flavours from
1700 test-network-all. Closes ticket 33280.
1701 - Remove a redundant distcheck job. Closes ticket 33194.
1702 - Run the test-network-ipv6 Makefile target in the Travis CI IPv6
1703 chutney job. This job runs on macOS, so it's a bit slow. Closes
1705 - Sort the Travis jobs in order of speed. Putting the slowest jobs
1706 first takes full advantage of Travis job concurrency. Closes
1708 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
1709 previously configured to fast_finish (which requires
1710 allow_failure), to speed up the build. Closes ticket 33195.
1711 - Test v3 onion services to tor's mixed IPv4 chutney network. And
1712 add a mixed IPv6 chutney network. These networks are used in the
1713 test-network-all, test-network-ipv4, and test-network-ipv6 make
1714 targets. Closes ticket 33334.
1715 - Use the "bridges+hs-v23" chutney network flavour in "make test-
1716 network". This test requires a recent version of chutney (mid-
1717 February 2020). Closes ticket 28208.
1718 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
1719 tool to produce detailed diagnostic output. Closes ticket 32792.
1721 o Deprecated features (onion service v2):
1722 - Add a deprecation warning for version 2 onion services. Closes
1725 o Documentation (manual page):
1726 - Add cross reference links and a table of contents to the HTML tor
1727 manual page. Closes ticket 33369. Work by Swati Thacker as part of
1728 Google Season of Docs.
1729 - Alphabetize the Denial of Service Mitigation Options, Directory
1730 Authority Server Options, Hidden Service Options, and Testing
1731 Network Options sections of the tor(1) manual page. Closes ticket
1732 33275. Work by Swati Thacker as part of Google Season of Docs.
1733 - Refrain from mentioning nicknames in manpage section for MyFamily
1734 torrc option. Resolves issue 33417.
1735 - Updated the options set by TestingTorNetwork in the manual page.
1736 Closes ticket 33778.
1739 Changes in version 0.3.5.11 - 2020-07-09
1740 Tor 0.3.5.11 backports fixes from later tor releases, including several
1741 usability, portability, and reliability fixes.
1743 This release also fixes TROVE-2020-001, a medium-severity denial of
1744 service vulnerability affecting all versions of Tor when compiled with
1745 the NSS encryption library. (This is not the default configuration.)
1746 Using this vulnerability, an attacker could cause an affected Tor
1747 instance to crash remotely. This issue is also tracked as CVE-2020-
1748 15572. Anybody running a version of Tor built with the NSS library
1749 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
1752 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
1753 - Fix a crash due to an out-of-bound memory access when Tor is
1754 compiled with NSS support. Fixes bug 33119; bugfix on
1755 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
1758 o Major bugfixes (DoS defenses, bridges, pluggable transport, backport from 0.4.3.4-rc):
1759 - Fix a bug that was preventing DoS defenses from running on bridges
1760 with a pluggable transport. Previously, the DoS subsystem was not
1761 given the transport name of the client connection, thus failed to
1762 find the GeoIP cache entry for that client address. Fixes bug
1763 33491; bugfix on 0.3.3.2-alpha.
1765 o Minor features (testing, backport from 0.4.3.4-rc):
1766 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
1767 variable to specify a list of space-separated test cases that
1768 should not be executed. We will use this to disable certain tests
1769 that are failing on Appveyor because of mismatched OpenSSL
1770 libraries. Part of ticket 33643.
1772 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
1773 - Use the correct 64-bit printf format when compiling with MINGW on
1774 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
1776 o Minor bugfix (relay, configuration, backport from 0.4.3.3-alpha):
1777 - Warn if the ContactInfo field is not set, and tell the relay
1778 operator that not having a ContactInfo field set might cause their
1779 relay to get rejected in the future. Fixes bug 33361; bugfix
1782 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
1783 - Resume use of preemptively-built circuits when UseEntryGuards is set
1784 to 0. We accidentally disabled this feature with that config
1785 setting, leading to slower load times. Fixes bug 34303; bugfix
1788 o Minor bugfixes (compiler compatibility, backport from 0.4.3.5):
1789 - Avoid compiler warnings from Clang 10 related to the use of GCC-
1790 style "/* falls through */" comments. Both Clang and GCC allow
1791 __attribute__((fallthrough)) instead, so that's what we're using
1792 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
1794 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
1795 - Fix a compiler warning on platforms with 32-bit time_t values.
1796 Fixes bug 40028; bugfix on 0.3.2.8-rc.
1798 o Minor bugfixes (embedded Tor, backport from 0.4.3.1-alpha):
1799 - When starting Tor any time after the first time in a process,
1800 register the thread in which it is running as the main thread.
1801 Previously, we only did this on Windows, which could lead to bugs
1802 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
1805 o Minor bugfixes (key portability, backport from 0.4.3.4-rc):
1806 - When reading PEM-encoded key data, tolerate CRLF line-endings even
1807 if we are not running on Windows. Previously, non-Windows hosts
1808 would reject these line-endings in certain positions, making
1809 certain key files hard to move from one host to another. Fixes bug
1810 33032; bugfix on 0.3.5.1-alpha.
1812 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
1813 - Downgrade a noisy log message that could occur naturally when
1814 receiving an extrainfo document that we no longer want. Fixes bug
1815 16016; bugfix on 0.2.6.3-alpha.
1817 o Minor bugfixes (onion service v3, client, backport from 0.4.3.3-alpha):
1818 - Remove a BUG() warning that would cause a stack trace if an onion
1819 service descriptor was freed while we were waiting for a
1820 rendezvous circuit to complete. Fixes bug 28992; bugfix
1823 o Testing (CI, backport from 0.4.3.4-rc):
1824 - In our Appveyor Windows CI, copy required DLLs to test and app
1825 directories, before running tor's tests. This ensures that tor.exe
1826 and test*.exe use the correct version of each DLL. This fix is not
1827 required, but we hope it will avoid DLL search issues in future.
1828 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
1829 - On Appveyor, skip the crypto/openssl_version test, which is
1830 failing because of a mismatched library installation. Fix
1834 Changes in version 0.4.2.8 - 2020-07-09
1835 Tor 0.4.2.8 backports various fixes from later releases, including
1836 several that affect usability and portability.
1838 This release also fixes TROVE-2020-001, a medium-severity denial of
1839 service vulnerability affecting all versions of Tor when compiled with
1840 the NSS encryption library. (This is not the default configuration.)
1841 Using this vulnerability, an attacker could cause an affected Tor
1842 instance to crash remotely. This issue is also tracked as CVE-2020-
1843 15572. Anybody running a version of Tor built with the NSS library
1844 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
1847 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
1848 - Fix a crash due to an out-of-bound memory access when Tor is
1849 compiled with NSS support. Fixes bug 33119; bugfix on
1850 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
1853 o Major bugfixes (DoS defenses, bridges, pluggable transport, backport from 0.4.3.4-rc):
1854 - Fix a bug that was preventing DoS defenses from running on bridges
1855 with a pluggable transport. Previously, the DoS subsystem was not
1856 given the transport name of the client connection, thus failed to
1857 find the GeoIP cache entry for that client address. Fixes bug
1858 33491; bugfix on 0.3.3.2-alpha.
1860 o Minor feature (sendme, flow control, backport form 0.4.3.4-rc):
1861 - Default to sending SENDME version 1 cells. (Clients are already
1862 sending these, because of a consensus parameter telling them to do
1863 so: this change only affects what clients would do if the
1864 consensus didn't contain a recommendation.) Closes ticket 33623.
1866 o Minor features (diagnostic, backport from 0.4.3.3-alpha):
1867 - Improve assertions and add some memory-poisoning code to try to
1868 track down possible causes of a rare crash (32564) in the EWMA
1869 code. Closes ticket 33290.
1871 o Minor features (testing, backport from 0.4.3.4-rc):
1872 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
1873 variable to specify a list of space-separated test cases that
1874 should not be executed. We will use this to disable certain tests
1875 that are failing on Appveyor because of mismatched OpenSSL
1876 libraries. Part of ticket 33643.
1878 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
1879 - Use the correct 64-bit printf format when compiling with MINGW on
1880 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
1882 o Minor bugfix (relay, configuration, backport from 0.4.3.3-alpha):
1883 - Warn if the ContactInfo field is not set, and tell the relay
1884 operator that not having a ContactInfo field set might cause their
1885 relay to get rejected in the future. Fixes bug 33361; bugfix
1888 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
1889 - Resume use of preemptively-built circuits when UseEntryGuards is set
1890 to 0. We accidentally disabled this feature with that config
1891 setting, leading to slower load times. Fixes bug 34303; bugfix
1894 o Minor bugfixes (compiler compatibility, backport from 0.4.3.5):
1895 - Avoid compiler warnings from Clang 10 related to the use of GCC-
1896 style "/* falls through */" comments. Both Clang and GCC allow
1897 __attribute__((fallthrough)) instead, so that's what we're using
1898 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
1899 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
1902 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
1903 - Fix a compiler warning on platforms with 32-bit time_t values.
1904 Fixes bug 40028; bugfix on 0.3.2.8-rc.
1906 o Minor bugfixes (controller protocol, backport from 0.4.3.2-alpha):
1907 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
1908 report them as SIGNAL events. Previously we would log a bug
1909 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
1911 o Minor bugfixes (embedded Tor, backport from 0.4.3.1-alpha):
1912 - When starting Tor any time after the first time in a process,
1913 register the thread in which it is running as the main thread.
1914 Previously, we only did this on Windows, which could lead to bugs
1915 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
1918 o Minor bugfixes (key portability, backport from 0.4.3.4-rc):
1919 - When reading PEM-encoded key data, tolerate CRLF line-endings even
1920 if we are not running on Windows. Previously, non-Windows hosts
1921 would reject these line-endings in certain positions, making
1922 certain key files hard to move from one host to another. Fixes bug
1923 33032; bugfix on 0.3.5.1-alpha.
1925 o Minor bugfixes (logging, backport from 0.4.3.2-rc):
1926 - When logging a bug, do not say "Future instances of this warning
1927 will be silenced" unless we are actually going to silence them.
1928 Previously we would say this whenever a BUG() check failed in the
1929 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
1931 o Minor bugfixes (logging, backport from 0.4.3.4-rc):
1932 - Flush stderr, stdout, and file logs during shutdown, if supported
1933 by the OS. This change helps make sure that any final logs are
1934 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
1936 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
1937 - Downgrade a noisy log message that could occur naturally when
1938 receiving an extrainfo document that we no longer want. Fixes bug
1939 16016; bugfix on 0.2.6.3-alpha.
1941 o Minor bugfixes (onion service v3, client, backport from 0.4.3.3-alpha):
1942 - Remove a BUG() warning that would cause a stack trace if an onion
1943 service descriptor was freed while we were waiting for a
1944 rendezvous circuit to complete. Fixes bug 28992; bugfix
1947 o Testing (CI, backport from 0.4.3.4-rc):
1948 - In our Appveyor Windows CI, copy required DLLs to test and app
1949 directories, before running tor's tests. This ensures that tor.exe
1950 and test*.exe use the correct version of each DLL. This fix is not
1951 required, but we hope it will avoid DLL search issues in future.
1952 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
1953 - On Appveyor, skip the crypto/openssl_version test, which is
1954 failing because of a mismatched library installation. Fix
1958 Changes in version 0.4.3.6 - 2020-07-09
1959 Tor 0.4.3.6 backports several bugfixes from later releases, including
1960 some affecting usability.
1962 This release also fixes TROVE-2020-001, a medium-severity denial of
1963 service vulnerability affecting all versions of Tor when compiled with
1964 the NSS encryption library. (This is not the default configuration.)
1965 Using this vulnerability, an attacker could cause an affected Tor
1966 instance to crash remotely. This issue is also tracked as CVE-2020-
1967 15572. Anybody running a version of Tor built with the NSS library
1968 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
1971 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
1972 - Fix a crash due to an out-of-bound memory access when Tor is
1973 compiled with NSS support. Fixes bug 33119; bugfix on
1974 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
1977 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
1978 - Use the correct 64-bit printf format when compiling with MINGW on
1979 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
1981 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
1982 - Resume use of preemptively-built circuits when UseEntryGuards is set
1983 to 0. We accidentally disabled this feature with that config
1984 setting, leading to slower load times. Fixes bug 34303; bugfix
1987 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
1988 - Fix a compiler warning on platforms with 32-bit time_t values.
1989 Fixes bug 40028; bugfix on 0.3.2.8-rc.
1991 o Minor bugfixes (linux seccomp sandbox, nss, backport from 0.4.4.1-alpha):
1992 - Fix a startup crash when tor is compiled with --enable-nss and
1993 sandbox support is enabled. Fixes bug 34130; bugfix on
1994 0.3.5.1-alpha. Patch by Daniel Pinto.
1996 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
1997 - Downgrade a noisy log message that could occur naturally when
1998 receiving an extrainfo document that we no longer want. Fixes bug
1999 16016; bugfix on 0.2.6.3-alpha.
2001 o Minor bugfixes (manual page, backport from 0.4.4.1-alpha):
2002 - Update the man page to reflect that MinUptimeHidServDirectoryV2
2003 defaults to 96 hours. Fixes bug 34299; bugfix on 0.2.6.3-alpha.
2005 o Minor bugfixes (onion service v3, backport from 0.4.4.1-alpha):
2006 - Prevent an assert() that would occur when cleaning the client
2007 descriptor cache, and attempting to close circuits for a non-
2008 decrypted descriptor (lacking client authorization). Fixes bug
2009 33458; bugfix on 0.4.2.1-alpha.
2011 o Minor bugfixes (portability, backport from 0.4.4.1-alpha):
2012 - Fix a portability error in the configure script, where we were
2013 using "==" instead of "=". Fixes bug 34233; bugfix on 0.4.3.5.
2015 o Minor bugfixes (relays, backport from 0.4.4.1-alpha):
2016 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
2017 descriptors, when the IPv6 port was configured as "auto". Fixes
2018 bug 32588; bugfix on 0.2.3.9-alpha.
2020 o Documentation (backport from 0.4.4.1-alpha):
2021 - Fix several doxygen warnings related to imbalanced groups. Closes
2025 Changes in version 0.4.3.5 - 2020-05-15
2026 Tor 0.4.3.5 is the first stable release in the 0.4.3.x series. This
2027 series adds support for building without relay code enabled, and
2028 implements functionality needed for OnionBalance with v3 onion
2029 services. It includes significant refactoring of our configuration and
2030 controller functionality, and fixes numerous smaller bugs and
2033 Per our support policy, we support each stable release series for nine
2034 months after its first stable release, or three months after the first
2035 stable release of the next series: whichever is longer. This means
2036 that 0.4.3.x will be supported until around February 2021--later, if
2037 0.4.4.x is later than anticipated.
2039 Note also that support for 0.4.1.x is about to end on May 20 of this
2040 year; 0.4.2.x will be supported until September 15. We still plan to
2041 continue supporting 0.3.5.x, our long-term stable series, until
2044 Below are the changes since 0.4.2.6. For a list of only the changes
2045 since 0.4.3.4-rc, see the ChangeLog file.
2047 o New system requirements:
2048 - When building Tor, you now need to have Python 3 in order to run
2049 the integration tests. (Python 2 is officially unsupported
2050 upstream, as of 1 Jan 2020.) Closes ticket 32608.
2052 o Major features (build system):
2053 - The relay code can now be disabled using the --disable-module-relay
2054 configure option. When this option is set, we also disable the
2055 dirauth module. Closes ticket 32123.
2056 - When Tor is compiled --disable-module-relay, we also omit the code
2057 used to act as a directory cache. Closes ticket 32487.
2059 o Major features (directory authority, ed25519):
2060 - Add support for banning a relay's ed25519 keys in the approved-
2061 routers file. This will help us migrate away from RSA keys in the
2062 future. Previously, only RSA keys could be banned in approved-
2063 routers. Resolves ticket 22029. Patch by Neel Chauhan.
2065 o Major features (onion services):
2066 - New control port commands to manage client-side onion service
2067 authorization credentials. The ONION_CLIENT_AUTH_ADD command adds
2068 a credential, ONION_CLIENT_AUTH_REMOVE deletes a credential, and
2069 ONION_CLIENT_AUTH_VIEW lists the credentials. Closes ticket 30381.
2070 - Introduce a new SocksPort flag, ExtendedErrors, to support more
2071 detailed error codes in information for applications that support
2072 them. Closes ticket 30382; implements proposal 304.
2074 o Major features (proxy):
2075 - In addition to its current supported proxy types (HTTP CONNECT,
2076 SOCKS4, and SOCKS5), Tor can now make its OR connections through a
2077 HAProxy server. A new torrc option was added to specify the
2078 address/port of the server: TCPProxy <protocol> <host>:<port>.
2079 Currently the only supported protocol for the option is haproxy.
2080 Closes ticket 31518. Patch done by Suphanat Chunhapanya (haxxpop).
2082 o Major bugfixes (security, denial-of-service):
2083 - Fix a denial-of-service bug that could be used by anyone to
2084 consume a bunch of CPU on any Tor relay or authority, or by
2085 directories to consume a bunch of CPU on clients or hidden
2086 services. Because of the potential for CPU consumption to
2087 introduce observable timing patterns, we are treating this as a
2088 high-severity security issue. Fixes bug 33119; bugfix on
2089 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
2090 as TROVE-2020-002 and CVE-2020-10592.
2092 o Major bugfixes (circuit padding, memory leak):
2093 - Avoid a remotely triggered memory leak in the case that a circuit
2094 padding machine is somehow negotiated twice on the same circuit.
2095 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
2096 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
2098 o Major bugfixes (directory authority):
2099 - Directory authorities will now send a 503 (not enough bandwidth)
2100 code to clients when under bandwidth pressure. Known relays and
2101 other authorities will always be answered regardless of the
2102 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
2104 o Major bugfixes (DoS defenses, bridges, pluggable transport):
2105 - Fix a bug that was preventing DoS defenses from running on bridges
2106 with a pluggable transport. Previously, the DoS subsystem was not
2107 given the transport name of the client connection, thus failed to
2108 find the GeoIP cache entry for that client address. Fixes bug
2109 33491; bugfix on 0.3.3.2-alpha.
2111 o Major bugfixes (networking):
2112 - Correctly handle IPv6 addresses in SOCKS5 RESOLVE_PTR requests,
2113 and accept strings as well as binary addresses. Fixes bug 32315;
2114 bugfix on 0.3.5.1-alpha.
2116 o Major bugfixes (onion service):
2117 - Report HS circuit failure back into the HS subsystem so we take
2118 appropriate action with regards to the client introduction point
2119 failure cache. This improves reachability of onion services, since
2120 now clients notice failing introduction circuits properly. Fixes
2121 bug 32020; bugfix on 0.3.2.1-alpha.
2123 o Minor feature (heartbeat, onion service):
2124 - Add the DoS INTRODUCE2 defenses counter to the heartbeat DoS
2125 message. Closes ticket 31371.
2127 o Minor feature (sendme, flow control):
2128 - Default to sending SENDME version 1 cells. (Clients are already
2129 sending these, because of a consensus parameter telling them to do
2130 so: this change only affects what clients would do if the
2131 consensus didn't contain a recommendation.) Closes ticket 33623.
2133 o Minor features (best practices tracker):
2134 - Practracker now supports a --regen-overbroad option to regenerate
2135 the exceptions file, but only to revise exceptions to be _less_
2136 tolerant of best-practices violations. Closes ticket 32372.
2138 o Minor features (configuration validation):
2139 - Configuration validation can now be done by per-module callbacks,
2140 rather than a global validation function. This will let us reduce
2141 the size of config.c and some of its more cumbersome functions.
2142 Closes ticket 31241.
2144 o Minor features (configuration):
2145 - If a configured hardware crypto accelerator in AccelName is
2146 prefixed with "!", Tor now exits when it cannot be found. Closes
2148 - We now use flag-driven logic to warn about obsolete configuration
2149 fields, so that we can include their names. In 0.4.2, we used a
2150 special type, which prevented us from generating good warnings.
2151 Implements ticket 32404.
2153 o Minor features (configure, build system):
2154 - Output a list of enabled/disabled features at the end of the
2155 configure process in a pleasing way. Closes ticket 31373.
2157 o Minor features (continuous integration):
2158 - Run Doxygen Makefile target on Travis, so we can learn about
2159 regressions in our internal documentation. Closes ticket 32455.
2160 - Stop allowing failures on the Travis CI stem tests job. It looks
2161 like all the stem hangs we were seeing before are now fixed.
2162 Closes ticket 33075.
2164 o Minor features (controller):
2165 - Add stream isolation data to STREAM event. Closes ticket 19859.
2166 - Implement a new GETINFO command to fetch microdescriptor
2167 consensus. Closes ticket 31684.
2169 o Minor features (debugging, directory system):
2170 - Don't crash when we find a non-guard with a guard-fraction value
2171 set. Instead, log a bug warning, in an attempt to figure out how
2172 this happened. Diagnostic for ticket 32868.
2174 o Minor features (defense in depth):
2175 - Add additional checks around tor_vasprintf() usage, in case the
2176 function returns an error. Patch by Tobias Stoeckmann. Fixes
2179 o Minor features (developer tools):
2180 - Remove the 0.2.9.x series branches from git scripts (git-merge-
2181 forward.sh, git-pull-all.sh, git-push-all.sh, git-setup-dirs.sh).
2182 Closes ticket 32772.
2183 - Add a check_cocci_parse.sh script that checks that new code is
2184 parseable by Coccinelle. Add an exceptions file for unparseable
2185 files, and run the script from travis CI. Closes ticket 31919.
2186 - Call the check_cocci_parse.sh script from a 'check-cocci' Makefile
2187 target. Closes ticket 31919.
2188 - Add a rename_c_identifiers.py tool to rename a bunch of C
2189 identifiers at once, and generate a well-formed commit message
2190 describing the change. This should help with refactoring. Closes
2192 - Add some scripts in "scripts/coccinelle" to invoke the Coccinelle
2193 semantic patching tool with the correct flags. These flags are
2194 fairly easy to forget, and these scripts should help us use
2195 Coccinelle more effectively in the future. Closes ticket 31705.
2197 o Minor features (diagnostic):
2198 - Improve assertions and add some memory-poisoning code to try to
2199 track down possible causes of a rare crash (32564) in the EWMA
2200 code. Closes ticket 33290.
2202 o Minor features (directory authorities):
2203 - Directory authorities now reject descriptors from relays running
2204 Tor versions from the 0.2.9 and 0.4.0 series. The 0.3.5 series is
2205 still allowed. Resolves ticket 32672. Patch by Neel Chauhan.
2207 o Minor features (Doxygen):
2208 - Update Doxygen configuration file to a more recent template (from
2209 1.8.15). Closes ticket 32110.
2210 - "make doxygen" now works with out-of-tree builds. Closes
2212 - Make sure that doxygen outputs documentation for all of our C
2213 files. Previously, some were missing @file declarations, causing
2214 them to be ignored. Closes ticket 32307.
2215 - Our "make doxygen" target now respects --enable-fatal-warnings by
2216 default, and does not warn about items that are missing
2217 documentation. To warn about missing documentation, run configure
2218 with the "--enable-missing-doc-warnings" flag: doing so suspends
2219 fatal warnings for doxygen. Closes ticket 32385.
2221 o Minor features (git scripts):
2222 - Add TOR_EXTRA_CLONE_ARGS to git-setup-dirs.sh for git clone
2223 customisation. Closes ticket 32347.
2224 - Add git-setup-dirs.sh, which sets up an upstream git repository
2225 and worktrees for tor maintainers. Closes ticket 29603.
2226 - Add TOR_EXTRA_REMOTE_* to git-setup-dirs.sh for a custom extra
2227 remote. Closes ticket 32347.
2228 - Call the check_cocci_parse.sh script from the git commit and push
2229 hooks. Closes ticket 31919.
2230 - Make git-push-all.sh skip unchanged branches when pushing to
2231 upstream. The script already skipped unchanged test branches.
2232 Closes ticket 32216.
2233 - Make git-setup-dirs.sh create a master symlink in the worktree
2234 directory. Closes ticket 32347.
2235 - Skip unmodified source files when doing some existing git hook
2236 checks. Related to ticket 31919.
2238 o Minor features (IPv6, client):
2239 - Make Tor clients tell dual-stack exits that they prefer IPv6
2240 connections. This change is equivalent to setting the PreferIPv6
2241 flag on SOCKSPorts (and most other listener ports). Tor Browser
2242 has been setting this flag for some time, and we want to remove a
2243 client distinguisher at exits. Closes ticket 32637.
2245 o Minor features (portability, android):
2246 - When building for Android, disable some tests that depend on $HOME
2247 and/or pwdb, which Android doesn't have. Closes ticket 32825.
2248 Patch from Hans-Christoph Steiner.
2250 o Minor features (relay modularity):
2251 - Split the relay and server pluggable transport config code into
2252 separate files in the relay module. Disable this code when the
2253 relay module is disabled. Closes part of ticket 32213.
2254 - When the relay module is disabled, reject attempts to set the
2255 ORPort, DirPort, DirCache, BridgeRelay, ExtORPort, or
2256 ServerTransport* options, rather than ignoring the values of these
2257 options. Closes part of ticket 32213.
2258 - When the relay module is disabled, change the default config so
2259 that DirCache is 0, and ClientOnly is 1. Closes ticket 32410.
2261 o Minor features (release tools):
2262 - Port our ChangeLog formatting and sorting tools to Python 3.
2263 Closes ticket 32704.
2265 o Minor features (testing):
2266 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
2267 variable to specify a list of space-separated test cases that
2268 should not be executed. We will use this to disable certain tests
2269 that are failing on Appveyor because of mismatched OpenSSL
2270 libraries. Part of ticket 33643.
2271 - Detect some common failure cases for test_parseconf.sh in
2272 src/test/conf_failures. Closes ticket 32451.
2273 - Allow test_parseconf.sh to test expected log outputs for successful
2274 configs, as well as failed configs. Closes ticket 32451.
2275 - The test_parseconf.sh script now supports result variants for any
2276 combination of the optional libraries lzma, nss, and zstd. Closes
2278 - When running the unit tests on Android, create temporary files in
2279 a subdirectory of /data/local/tmp. Closes ticket 32172. Based on a
2280 patch from Hans-Christoph Steiner.
2282 o Minor features (usability):
2283 - Include more information when failing to parse a configuration
2284 value. This should make it easier to tell what's going wrong when
2285 a configuration file doesn't parse. Closes ticket 33460.
2287 o Minor bugfix (relay, configuration):
2288 - Warn if the ContactInfo field is not set, and tell the relay
2289 operator that not having a ContactInfo field set might cause their
2290 relay to get rejected in the future. Fixes bug 33361; bugfix
2293 o Minor bugfixes (bridges):
2294 - Lowercase the configured value of BridgeDistribution before adding
2295 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
2297 o Minor bugfixes (build system):
2298 - Fix "make autostyle" for out-of-tree builds. Fixes bug 32370;
2299 bugfix on 0.4.1.2-alpha.
2301 o Minor bugfixes (compiler compatibility):
2302 - Avoid compiler warnings from Clang 10 related to the use of GCC-
2303 style "/* falls through */" comments. Both Clang and GCC allow
2304 __attribute__((fallthrough)) instead, so that's what we're using
2305 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
2306 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
2309 o Minor bugfixes (configuration handling):
2310 - Make control_event_conf_changed() take in a config_line_t instead
2311 of a smartlist of alternating key/value entries. Fixes bug 31531;
2312 bugfix on 0.2.3.3-alpha. Patch by Neel Chauhan.
2313 - Check for multiplication overflow when parsing memory units inside
2314 configuration. Fixes bug 30920; bugfix on 0.0.9rc1.
2315 - When dumping the configuration, stop adding a trailing space after
2316 the option name when there is no option value. This issue only
2317 affects options that accept an empty value or list. (Most options
2318 reject empty values, or delete the entire line from the dumped
2319 options.) Fixes bug 32352; bugfix on 0.0.9pre6.
2320 - Avoid changing the user's value of HardwareAccel as stored by
2321 SAVECONF, when AccelName is set but HardwareAccel is not. Fixes
2322 bug 32382; bugfix on 0.2.2.1-alpha.
2323 - When creating a KeyDirectory with the same location as the
2324 DataDirectory (not recommended), respect the DataDirectory's
2325 group-readable setting if one has not been set for the
2326 KeyDirectory. Fixes bug 27992; bugfix on 0.3.3.1-alpha.
2328 o Minor bugfixes (continuous integration):
2329 - Remove the buggy and unused mirroring job. Fixes bug 33213; bugfix
2332 o Minor bugfixes (controller protocol):
2333 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
2334 report them as SIGNAL events. Previously we would log a bug
2335 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
2337 o Minor bugfixes (controller):
2338 - In routerstatus_has_changed(), check all the fields that are
2339 output over the control port. Fixes bug 20218; bugfix
2342 o Minor bugfixes (developer tools):
2343 - Allow paths starting with ./ in scripts/add_c_file.py. Fixes bug
2344 31336; bugfix on 0.4.1.2-alpha.
2346 o Minor bugfixes (dirauth module):
2347 - Split the dirauth config code into a separate file in the dirauth
2348 module. Disable this code when the dirauth module is disabled.
2349 Closes ticket 32213.
2350 - When the dirauth module is disabled, reject attempts to set the
2351 AuthoritativeDir option, rather than ignoring the value of the
2352 option. Fixes bug 32213; bugfix on 0.3.4.1-alpha.
2354 o Minor bugfixes (embedded Tor):
2355 - When starting Tor any time after the first time in a process,
2356 register the thread in which it is running as the main thread.
2357 Previously, we only did this on Windows, which could lead to bugs
2358 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
2361 o Minor bugfixes (git scripts):
2362 - Avoid sleeping before the last push in git-push-all.sh. Closes
2364 - Forward all unrecognised arguments in git-push-all.sh to git push.
2365 Closes ticket 32216.
2367 o Minor bugfixes (key portability):
2368 - When reading PEM-encoded key data, tolerate CRLF line-endings even
2369 if we are not running on Windows. Previously, non-Windows hosts
2370 would reject these line-endings in certain positions, making
2371 certain key files hard to move from one host to another. Fixes bug
2372 33032; bugfix on 0.3.5.1-alpha.
2374 o Minor bugfixes (logging):
2375 - Stop truncating IPv6 addresses and ports in channel and connection
2376 logs. Fixes bug 33918; bugfix on 0.2.4.4-alpha.
2377 - Flush stderr, stdout, and file logs during shutdown, if supported
2378 by the OS. This change helps make sure that any final logs are
2379 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
2380 - Stop closing stderr and stdout during shutdown. Closing these file
2381 descriptors can hide sanitiser logs. Fixes bug 33087; bugfix
2383 - If we encounter a bug when flushing a buffer to a TLS connection,
2384 only log the bug once per invocation of the Tor process.
2385 Previously we would log with every occurrence, which could cause
2386 us to run out of disk space. Fixes bug 33093; bugfix
2388 - When logging a bug, do not say "Future instances of this warning
2389 will be silenced" unless we are actually going to silence them.
2390 Previously we would say this whenever a BUG() check failed in the
2391 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
2393 o Minor bugfixes (onion services v2):
2394 - Move a series of v2 onion service warnings to protocol-warning
2395 level because they can all be triggered remotely by a malformed
2396 request. Fixes bug 32706; bugfix on 0.1.1.14-alpha.
2397 - When sending the INTRO cell for a v2 Onion Service, look at the
2398 failure cache alongside timeout values to check if the intro point
2399 is marked as failed. Previously, we only looked at the relay
2400 timeout values. Fixes bug 25568; bugfix on 0.2.7.3-rc. Patch by
2403 o Minor bugfixes (onion services v3):
2404 - Remove a BUG() warning that would cause a stack trace if an onion
2405 service descriptor was freed while we were waiting for a
2406 rendezvous circuit to complete. Fixes bug 28992; bugfix
2408 - Relax severity of a log message that can appear naturally when
2409 decoding onion service descriptors as a relay. Also add some
2410 diagnostics to debug any future bugs in that area. Fixes bug
2411 31669; bugfix on 0.3.0.1-alpha.
2412 - Fix an assertion failure that could result from a corrupted
2413 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
2414 bugfix on 0.3.3.1-alpha. This issue is also tracked
2416 - Properly handle the client rendezvous circuit timeout. Previously
2417 Tor would sometimes timeout a rendezvous circuit awaiting the
2418 introduction ACK, and find itself unable to re-establish all
2419 circuits because the rendezvous circuit timed out too early. Fixes
2420 bug 32021; bugfix on 0.3.2.1-alpha.
2422 o Minor bugfixes (onion services):
2423 - Do not rely on a "circuit established" flag for intro circuits but
2424 instead always query the HS circuit map. This is to avoid sync
2425 issue with that flag and the map. Fixes bug 32094; bugfix
2428 o Minor bugfixes (onion services, all):
2429 - In cancel_descriptor_fetches(), use
2430 connection_list_by_type_purpose() instead of
2431 connection_list_by_type_state(). Fixes bug 32639; bugfix on
2432 0.3.2.1-alpha. Patch by Neel Chauhan.
2434 o Minor bugfixes (pluggable transports):
2435 - When receiving a message on standard error from a pluggable
2436 transport, log it at info level, rather than as a warning. Fixes
2437 bug 33005; bugfix on 0.4.0.1-alpha.
2439 o Minor bugfixes (rust, build):
2440 - Fix a syntax warning given by newer versions of Rust that was
2441 creating problems for our continuous integration. Fixes bug 33212;
2442 bugfix on 0.3.5.1-alpha.
2444 o Minor bugfixes (scripts):
2445 - Fix update_versions.py for out-of-tree builds. Fixes bug 32371;
2446 bugfix on 0.4.0.1-alpha.
2448 o Minor bugfixes (testing):
2449 - Use the same code to find the tor binary in all of our test
2450 scripts. This change makes sure we are always using the coverage
2451 binary when coverage is enabled. Fixes bug 32368; bugfix
2453 - Stop ignoring "tor --dump-config" errors in test_parseconf.sh.
2454 Fixes bug 32468; bugfix on 0.4.2.1-alpha.
2455 - Our option-validation tests no longer depend on specially
2456 configured non-default, non-passing sets of options. Previously,
2457 the tests had been written to assume that options would _not_ be
2458 set to their defaults, which led to needless complexity and
2459 verbosity. Fixes bug 32175; bugfix on 0.2.8.1-alpha.
2461 o Minor bugfixes (TLS bug handling):
2462 - When encountering a bug in buf_read_from_tls(), return a "MISC"
2463 error code rather than "WANTWRITE". This change might help avoid
2464 some CPU-wasting loops if the bug is ever triggered. Bug reported
2465 by opara. Fixes bug 32673; bugfix on 0.3.0.4-alpha.
2467 o Deprecated features:
2468 - Deprecate the ClientAutoIPv6ORPort option. This option was not
2469 true "Happy Eyeballs", and often failed on connections that
2470 weren't reliably dual-stack. Closes ticket 32942. Patch by
2474 - Provide a quickstart guide for a Circuit Padding Framework, and
2475 documentation for researchers to implement and study circuit
2476 padding machines. Closes ticket 28804.
2477 - Add documentation in 'HelpfulTools.md' to describe how to build a
2478 tag file. Closes ticket 32779.
2479 - Create a high-level description of the long-term software
2480 architecture goals. Closes ticket 32206.
2481 - Describe the --dump-config command in the manual page. Closes
2483 - Unite coding advice from this_not_that.md in torguts repo into our
2484 coding standards document. Resolves ticket 31853.
2487 - Our Doxygen configuration no longer generates LaTeX output. The
2488 reference manual produced by doing this was over 4000 pages long,
2489 and generally unusable. Closes ticket 32099.
2490 - The option "TestingEstimatedDescriptorPropagationTime" is now
2491 marked as obsolete. It has had no effect since 0.3.0.7, when
2492 clients stopped rejecting consensuses "from the future". Closes
2494 - We no longer support consensus methods before method 28; these
2495 methods were only used by authorities running versions of Tor that
2496 are now at end-of-life. In effect, this means that clients,
2497 relays, and authorities now assume that authorities will be
2498 running version 0.3.5.x or later. Closes ticket 32695.
2501 - Avoid conflicts between the fake sockets in tor's unit tests, and
2502 real file descriptors. Resolves issues running unit tests with
2503 GitHub Actions, where the process that embeds or launches the
2504 tests has already opened a large number of file descriptors. Fixes
2505 bug 33782; bugfix on 0.2.8.1-alpha. Found and fixed by
2507 - Add more test cases for tor's UTF-8 validation function. Also,
2508 check the arguments passed to the function for consistency. Closes
2510 - Improve test coverage for relay and dirauth config code, focusing
2511 on option validation and normalization. Closes ticket 32213.
2512 - Improve the consistency of test_parseconf.sh output, and run all
2513 the tests, even if one fails. Closes ticket 32213.
2514 - Run the practracker unit tests in the pre-commit git hook. Closes
2517 o Code simplification and refactoring (channel):
2518 - Channel layer had a variable length cell handler that was not used
2519 and thus removed. Closes ticket 32892.
2521 o Code simplification and refactoring (configuration):
2522 - Immutability is now implemented as a flag on individual
2523 configuration options rather than as part of the option-transition
2524 checking code. Closes ticket 32344.
2525 - Instead of keeping a list of configuration options to check for
2526 relative paths, check all the options whose type is "FILENAME".
2527 Solves part of ticket 32339.
2528 - Our default log (which ordinarily sends NOTICE-level messages to
2529 standard output) is now handled in a more logical manner.
2530 Previously, we replaced the configured log options if they were
2531 empty. Now, we interpret an empty set of log options as meaning
2532 "use the default log". Closes ticket 31999.
2533 - Remove some unused arguments from the options_validate() function,
2534 to simplify our code and tests. Closes ticket 32187.
2535 - Simplify the options_validate() code so that it looks at the
2536 default options directly, rather than taking default options as an
2537 argument. This change lets us simplify its interface. Closes
2539 - Use our new configuration architecture to move most authority-
2540 related options to the directory authority module. Closes
2542 - When parsing the command line, handle options that determine our
2543 "quiet level" and our mode of operation (e.g., --dump-config and
2544 so on) all in one table. Closes ticket 32003.
2546 o Code simplification and refactoring (controller):
2547 - Create a new abstraction for formatting control protocol reply
2548 lines based on key-value pairs. Refactor some existing control
2549 protocol code to take advantage of this. Closes ticket 30984.
2550 - Create a helper function that can fetch network status or
2551 microdesc consensuses. Closes ticket 31684.
2553 o Code simplification and refactoring (dirauth modularization):
2554 - Remove the last remaining HAVE_MODULE_DIRAUTH inside a function.
2555 Closes ticket 32163.
2556 - Replace some confusing identifiers in process_descs.c. Closes
2558 - Simplify some relay and dirauth config code. Closes ticket 32213.
2560 o Code simplification and refactoring (mainloop):
2561 - Simplify the ip_address_changed() function by removing redundant
2562 checks. Closes ticket 33091.
2564 o Code simplification and refactoring (misc):
2565 - Make all the structs we declare follow the same naming convention
2566 of ending with "_t". Closes ticket 32415.
2567 - Move and rename some configuration-related code for clarity.
2568 Closes ticket 32304.
2569 - Our include.am files are now broken up by subdirectory.
2570 Previously, src/core/include.am covered all of the subdirectories
2571 in "core", "feature", and "app". Closes ticket 32137.
2572 - Remove underused NS*() macros from test code: they make our tests
2573 more confusing, especially for code-formatting tools. Closes
2576 o Code simplification and refactoring (relay modularization):
2577 - Disable relay_periodic when the relay module is disabled. Closes
2579 - Disable relay_sys when the relay module is disabled. Closes
2582 o Code simplification and refactoring (tool support):
2583 - Add numerous missing dependencies to our include files, so that
2584 they can be included in different reasonable orders and still
2585 compile. Addresses part of ticket 32764.
2586 - Fix some parts of our code that were difficult for Coccinelle to
2587 parse. Related to ticket 31705.
2588 - Fix some small issues in our code that prevented automatic
2589 formatting tools from working. Addresses part of ticket 32764.
2591 o Documentation (manpage):
2592 - Alphabetize the Server and Directory server sections of the tor
2593 manpage. Also split Statistics options into their own section of
2594 the manpage. Closes ticket 33188. Work by Swati Thacker as part of
2595 Google Season of Docs.
2596 - Document the __OwningControllerProcess torrc option and specify
2597 its polling interval. Resolves issue 32971.
2598 - Split "Circuit Timeout" options and "Node Selection" options into
2599 their own sections of the tor manpage. Closes tickets 32928 and
2600 32929. Work by Swati Thacker as part of Google Season of Docs.
2601 - Alphabetize the Client Options section of the tor manpage. Closes
2603 - Alphabetize the General Options section of the tor manpage. Closes
2605 - In the tor(1) manpage, reword and improve formatting of the
2606 COMMAND-LINE OPTIONS and DESCRIPTION sections. Closes ticket
2607 32277. Based on work by Swati Thacker as part of Google Season
2609 - In the tor(1) manpage, reword and improve formatting of the FILES,
2610 SEE ALSO, and BUGS sections. Closes ticket 32176. Based on work by
2611 Swati Thacker as part of Google Season of Docs.
2613 o Testing (Appveyor CI):
2614 - In our Appveyor Windows CI, copy required DLLs to test and app
2615 directories, before running tor's tests. This ensures that tor.exe
2616 and test*.exe use the correct version of each DLL. This fix is not
2617 required, but we hope it will avoid DLL search issues in future.
2618 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
2619 - On Appveyor, skip the crypto/openssl_version test, which is
2620 failing because of a mismatched library installation. Fix
2623 o Testing (circuit, EWMA):
2624 - Add unit tests for circuitmux and EWMA subsystems. Closes
2627 o Testing (Travis CI):
2628 - Remove a redundant distcheck job. Closes ticket 33194.
2629 - Sort the Travis jobs in order of speed: putting the slowest jobs
2630 first takes full advantage of Travis job concurrency. Closes
2632 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2633 previously configured to fast_finish (which requires
2634 allow_failure), to speed up the build. Closes ticket 33195.
2635 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2636 tool to produce detailed diagnostic output. Closes ticket 32792.
2639 Changes in version 0.4.2.7 - 2020-03-18
2640 This is the third stable release in the 0.4.2.x series. It backports
2641 numerous fixes from later releases, including a fix for TROVE-2020-
2642 002, a major denial-of-service vulnerability that affected all
2643 released Tor instances since 0.2.1.5-alpha. Using this vulnerability,
2644 an attacker could cause Tor instances to consume a huge amount of CPU,
2645 disrupting their operations for several seconds or minutes. This
2646 attack could be launched by anybody against a relay, or by a directory
2647 cache against any client that had connected to it. The attacker could
2648 launch this attack as much as they wanted, thereby disrupting service
2649 or creating patterns that could aid in traffic analysis. This issue
2650 was found by OSS-Fuzz, and is also tracked as CVE-2020-10592.
2652 We do not have reason to believe that this attack is currently being
2653 exploited in the wild, but nonetheless we advise everyone to upgrade
2654 as soon as packages are available.
2656 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
2657 - Fix a denial-of-service bug that could be used by anyone to
2658 consume a bunch of CPU on any Tor relay or authority, or by
2659 directories to consume a bunch of CPU on clients or hidden
2660 services. Because of the potential for CPU consumption to
2661 introduce observable timing patterns, we are treating this as a
2662 high-severity security issue. Fixes bug 33119; bugfix on
2663 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
2664 as TROVE-2020-002 and CVE-2020-10592.
2666 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
2667 - Avoid a remotely triggered memory leak in the case that a circuit
2668 padding machine is somehow negotiated twice on the same circuit.
2669 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
2670 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
2672 o Major bugfixes (directory authority, backport from 0.4.3.3-alpha):
2673 - Directory authorities will now send a 503 (not enough bandwidth)
2674 code to clients when under bandwidth pressure. Known relays and
2675 other authorities will always be answered regardless of the
2676 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
2678 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
2679 - Stop allowing failures on the Travis CI stem tests job. It looks
2680 like all the stem hangs we were seeing before are now fixed.
2681 Closes ticket 33075.
2683 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
2684 - Lowercase the configured value of BridgeDistribution before adding
2685 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
2687 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
2688 - If we encounter a bug when flushing a buffer to a TLS connection,
2689 only log the bug once per invocation of the Tor process.
2690 Previously we would log with every occurrence, which could cause
2691 us to run out of disk space. Fixes bug 33093; bugfix
2694 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
2695 - Fix an assertion failure that could result from a corrupted
2696 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
2697 bugfix on 0.3.3.1-alpha. This issue is also tracked
2700 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
2701 - Fix a syntax warning given by newer versions of Rust that was
2702 creating problems for our continuous integration. Fixes bug 33212;
2703 bugfix on 0.3.5.1-alpha.
2705 o Testing (Travis CI, backport from 0.4.3.3-alpha):
2706 - Remove a redundant distcheck job. Closes ticket 33194.
2707 - Sort the Travis jobs in order of speed: putting the slowest jobs
2708 first takes full advantage of Travis job concurrency. Closes
2710 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2711 previously configured to fast_finish (which requires
2712 allow_failure), to speed up the build. Closes ticket 33195.
2713 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2714 tool to produce detailed diagnostic output. Closes ticket 32792.
2717 Changes in version 0.4.1.9 - 2020-03-18
2718 Tor 0.4.1.9 backports important fixes from later Tor releases,
2719 including a fix for TROVE-2020-002, a major denial-of-service
2720 vulnerability that affected all released Tor instances since
2721 0.2.1.5-alpha. Using this vulnerability, an attacker could cause Tor
2722 instances to consume a huge amount of CPU, disrupting their operations
2723 for several seconds or minutes. This attack could be launched by
2724 anybody against a relay, or by a directory cache against any client
2725 that had connected to it. The attacker could launch this attack as
2726 much as they wanted, thereby disrupting service or creating patterns
2727 that could aid in traffic analysis. This issue was found by OSS-Fuzz,
2728 and is also tracked as CVE-2020-10592.
2730 We do not have reason to believe that this attack is currently being
2731 exploited in the wild, but nonetheless we advise everyone to upgrade
2732 as soon as packages are available.
2734 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
2735 - Fix a denial-of-service bug that could be used by anyone to
2736 consume a bunch of CPU on any Tor relay or authority, or by
2737 directories to consume a bunch of CPU on clients or hidden
2738 services. Because of the potential for CPU consumption to
2739 introduce observable timing patterns, we are treating this as a
2740 high-severity security issue. Fixes bug 33119; bugfix on
2741 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
2742 as TROVE-2020-002 and CVE-2020-10592.
2744 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
2745 - Avoid a remotely triggered memory leak in the case that a circuit
2746 padding machine is somehow negotiated twice on the same circuit.
2747 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
2748 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
2750 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
2751 - Lowercase the configured value of BridgeDistribution before adding
2752 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
2754 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
2755 - If we encounter a bug when flushing a buffer to a TLS connection,
2756 only log the bug once per invocation of the Tor process.
2757 Previously we would log with every occurrence, which could cause
2758 us to run out of disk space. Fixes bug 33093; bugfix
2761 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
2762 - Fix an assertion failure that could result from a corrupted
2763 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
2764 bugfix on 0.3.3.1-alpha. This issue is also tracked
2767 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
2768 - Fix a syntax warning given by newer versions of Rust that was
2769 creating problems for our continuous integration. Fixes bug 33212;
2770 bugfix on 0.3.5.1-alpha.
2772 o Testing (Travis CI, backport from 0.4.3.3-alpha):
2773 - Remove a redundant distcheck job. Closes ticket 33194.
2774 - Sort the Travis jobs in order of speed: putting the slowest jobs
2775 first takes full advantage of Travis job concurrency. Closes
2777 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2778 previously configured to fast_finish (which requires
2779 allow_failure), to speed up the build. Closes ticket 33195.
2780 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2781 tool to produce detailed diagnostic output. Closes ticket 32792.
2784 Changes in version 0.3.5.10 - 2020-03-18
2785 Tor 0.3.5.10 backports many fixes from later Tor releases, including a
2786 fix for TROVE-2020-002, a major denial-of-service vulnerability that
2787 affected all released Tor instances since 0.2.1.5-alpha. Using this
2788 vulnerability, an attacker could cause Tor instances to consume a huge
2789 amount of CPU, disrupting their operations for several seconds or
2790 minutes. This attack could be launched by anybody against a relay, or
2791 by a directory cache against any client that had connected to it. The
2792 attacker could launch this attack as much as they wanted, thereby
2793 disrupting service or creating patterns that could aid in traffic
2794 analysis. This issue was found by OSS-Fuzz, and is also tracked
2797 We do not have reason to believe that this attack is currently being
2798 exploited in the wild, but nonetheless we advise everyone to upgrade
2799 as soon as packages are available.
2801 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
2802 - Fix a denial-of-service bug that could be used by anyone to
2803 consume a bunch of CPU on any Tor relay or authority, or by
2804 directories to consume a bunch of CPU on clients or hidden
2805 services. Because of the potential for CPU consumption to
2806 introduce observable timing patterns, we are treating this as a
2807 high-severity security issue. Fixes bug 33119; bugfix on
2808 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
2809 as TROVE-2020-002 and CVE-2020-10592.
2811 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
2812 - Correct how we use libseccomp. Particularly, stop assuming that
2813 rules are applied in a particular order or that more rules are
2814 processed after the first match. Neither is the case! In
2815 libseccomp <2.4.0 this lead to some rules having no effect.
2816 libseccomp 2.4.0 changed how rules are generated, leading to a
2817 different ordering, which in turn led to a fatal crash during
2818 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
2821 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
2822 - Stop allowing failures on the Travis CI stem tests job. It looks
2823 like all the stem hangs we were seeing before are now fixed.
2824 Closes ticket 33075.
2826 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
2827 - Lowercase the configured value of BridgeDistribution before adding
2828 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
2830 o Minor bugfixes (crash, backport from 0.4.2.4-rc):
2831 - When running Tor with an option like --verify-config or
2832 --dump-config that does not start the event loop, avoid crashing
2833 if we try to exit early because of an error. Fixes bug 32407;
2834 bugfix on 0.3.3.1-alpha.
2836 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
2837 - If we encounter a bug when flushing a buffer to a TLS connection,
2838 only log the bug once per invocation of the Tor process.
2839 Previously we would log with every occurrence, which could cause
2840 us to run out of disk space. Fixes bug 33093; bugfix
2843 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
2844 - Fix an assertion failure that could result from a corrupted
2845 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
2846 bugfix on 0.3.3.1-alpha. This issue is also tracked
2849 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
2850 - Fix a syntax warning given by newer versions of Rust that was
2851 creating problems for our continuous integration. Fixes bug 33212;
2852 bugfix on 0.3.5.1-alpha.
2854 o Testing (backport from 0.4.3.1-alpha):
2855 - Re-enable the Travis CI macOS Chutney build, but don't let it
2856 prevent the Travis job from finishing. (The Travis macOS jobs are
2857 slow, so we don't want to have it delay the whole CI process.)
2858 Closes ticket 32629.
2859 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
2860 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
2861 fix the sandbox errors in 32722. Closes ticket 32240.
2863 o Testing (continuous integration, backport from 0.4.3.1-alpha):
2864 - Use zstd in our Travis Linux builds. Closes ticket 32242.
2866 o Testing (Travis CI, backport from 0.4.3.3-alpha):
2867 - Remove a redundant distcheck job. Closes ticket 33194.
2868 - Sort the Travis jobs in order of speed: putting the slowest jobs
2869 first takes full advantage of Travis job concurrency. Closes
2871 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2872 previously configured to fast_finish (which requires
2873 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2874 tool to produce detailed diagnostic output. Closes ticket 32792.
2877 Changes in version 0.4.2.6 - 2020-01-30
2878 This is the second stable release in the 0.4.2.x series. It backports
2879 several bugfixes from 0.4.3.1-alpha, including some that had affected
2880 the Linux seccomp2 sandbox or Windows services. If you're running with
2881 one of those configurations, you'll probably want to upgrade;
2882 otherwise, you should be fine with 0.4.2.5.
2884 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
2885 - Correct how we use libseccomp. Particularly, stop assuming that
2886 rules are applied in a particular order or that more rules are
2887 processed after the first match. Neither is the case! In
2888 libseccomp <2.4.0 this led to some rules having no effect.
2889 libseccomp 2.4.0 changed how rules are generated, leading to a
2890 different ordering, which in turn led to a fatal crash during
2891 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
2893 - Fix crash when reloading logging configuration while the
2894 experimental sandbox is enabled. Fixes bug 32841; bugfix on
2895 0.4.1.7. Patch by Peter Gerber.
2897 o Minor bugfixes (correctness checks, backport from 0.4.3.1-alpha):
2898 - Use GCC/Clang's printf-checking feature to make sure that
2899 tor_assertf() arguments are correctly typed. Fixes bug 32765;
2900 bugfix on 0.4.1.1-alpha.
2902 o Minor bugfixes (logging, crash, backport from 0.4.3.1-alpha):
2903 - Avoid a possible crash when trying to log a (fatal) assertion
2904 failure about mismatched magic numbers in configuration objects.
2905 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
2907 o Minor bugfixes (testing, backport from 0.4.3.1-alpha):
2908 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
2909 test_practracker.sh script. Doing so caused a test failure. Fixes
2910 bug 32705; bugfix on 0.4.2.1-alpha.
2911 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
2912 skipping practracker checks. Fixes bug 32705; bugfix
2915 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
2916 - Initialize the publish/subscribe system when running as a windows
2917 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
2919 o Testing (backport from 0.4.3.1-alpha):
2920 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
2921 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
2922 fix the sandbox errors in 32722. Closes ticket 32240.
2923 - Re-enable the Travis CI macOS Chutney build, but don't let it
2924 prevent the Travis job from finishing. (The Travis macOS jobs are
2925 slow, so we don't want to have it delay the whole CI process.)
2926 Closes ticket 32629.
2928 o Testing (continuous integration, backport from 0.4.3.1-alpha):
2929 - Use zstd in our Travis Linux builds. Closes ticket 32242.
2932 Changes in version 0.4.1.8 - 2020-01-30
2933 This release backports several bugfixes from later release series,
2934 including some that had affected the Linux seccomp2 sandbox or Windows
2935 services. If you're running with one of those configurations, you'll
2936 probably want to upgrade; otherwise, you should be fine with your
2937 current version of 0.4.1.x.
2939 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
2940 - Correct how we use libseccomp. Particularly, stop assuming that
2941 rules are applied in a particular order or that more rules are
2942 processed after the first match. Neither is the case! In
2943 libseccomp <2.4.0 this led to some rules having no effect.
2944 libseccomp 2.4.0 changed how rules are generated, leading to a
2945 different ordering, which in turn led to a fatal crash during
2946 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
2948 - Fix crash when reloading logging configuration while the
2949 experimental sandbox is enabled. Fixes bug 32841; bugfix on
2950 0.4.1.7. Patch by Peter Gerber.
2952 o Minor bugfixes (crash, backport form 0.4.2.4-rc):
2953 - When running Tor with an option like --verify-config or
2954 --dump-config that does not start the event loop, avoid crashing
2955 if we try to exit early because of an error. Fixes bug 32407;
2956 bugfix on 0.3.3.1-alpha.
2958 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
2959 - Initialize the publish/subscribe system when running as a windows
2960 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
2962 o Testing (backport from 0.4.3.1-alpha):
2963 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
2964 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
2965 fix the sandbox errors in 32722. Closes ticket 32240.
2966 - Re-enable the Travis CI macOS Chutney build, but don't let it
2967 prevent the Travis job from finishing. (The Travis macOS jobs are
2968 slow, so we don't want to have it delay the whole CI process.)
2969 Closes ticket 32629.
2971 o Testing (continuous integration, backport from 0.4.3.1-alpha):
2972 - Use zstd in our Travis Linux builds. Closes ticket 32242.
2975 Changes in version 0.4.2.5 - 2019-12-09
2976 This is the first stable release in the 0.4.2.x series. This series
2977 improves reliability and stability, and includes several stability and
2978 correctness improvements for onion services. It also fixes many smaller
2979 bugs present in previous series.
2981 Per our support policy, we will support the 0.4.2.x series for nine
2982 months, or until three months after the release of a stable 0.4.3.x:
2983 whichever is longer. If you need longer-term support, please stick
2984 with 0.3.5.x, which will we plan to support until Feb 2022.
2986 Below are the changes since 0.4.1.4-rc. For a complete list of only
2987 the changes since 0.4.2.4-rc, see the ChangeLog file.
2989 o Major features (directory authorities):
2990 - Directory authorities now reject relays running all currently
2991 deprecated release series. The currently supported release series
2992 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
2994 o Major features (onion service v3, denial of service):
2995 - Add onion service introduction denial of service defenses. Intro
2996 points can now rate-limit client introduction requests, using
2997 parameters that can be sent by the service within the
2998 ESTABLISH_INTRO cell. If the cell extension for this is not used,
2999 the intro point will honor the consensus parameters. Closes
3002 o Major bugfixes (circuit build, guard):
3003 - When considering upgrading circuits from "waiting for guard" to
3004 "open", always ignore circuits that are marked for close.
3005 Previously we could end up in the situation where a subsystem is
3006 notified of a circuit opening, but the circuit is still marked for
3007 close, leading to undesirable behavior. Fixes bug 30871; bugfix
3010 o Major bugfixes (crash, Linux, Android):
3011 - Tolerate systems (including some Android installations) where
3012 madvise and MADV_DONTDUMP are available at build-time, but not at
3013 run time. Previously, these systems would notice a failed syscall
3014 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
3015 - Tolerate systems (including some Linux installations) where
3016 madvise and/or MADV_DONTFORK are available at build-time, but not
3017 at run time. Previously, these systems would notice a failed
3018 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
3020 o Major bugfixes (embedded Tor):
3021 - Avoid a possible crash when restarting Tor in embedded mode and
3022 enabling a different set of publish/subscribe messages. Fixes bug
3023 31898; bugfix on 0.4.1.1-alpha.
3025 o Major bugfixes (relay):
3026 - Relays now respect their AccountingMax bandwidth again. When
3027 relays entered "soft" hibernation (which typically starts when
3028 we've hit 90% of our AccountingMax), we had stopped checking
3029 whether we should enter hard hibernation. Soft hibernation refuses
3030 new connections and new circuits, but the existing circuits can
3031 continue, meaning that relays could have exceeded their configured
3032 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
3034 o Major bugfixes (torrc parsing):
3035 - Stop ignoring torrc options after an %include directive, when the
3036 included directory ends with a file that does not contain any
3037 config options (but does contain comments or whitespace). Fixes
3038 bug 31408; bugfix on 0.3.1.1-alpha.
3040 o Major bugfixes (v3 onion services):
3041 - Onion services now always use the exact number of intro points
3042 configured with the HiddenServiceNumIntroductionPoints option (or
3043 fewer if nodes are excluded). Before, a service could sometimes
3044 pick more intro points than configured. Fixes bug 31548; bugfix
3047 o Minor feature (onion services, control port):
3048 - The ADD_ONION command's keyword "BEST" now defaults to ED25519-V3
3049 (v3) onion services. Previously it defaulted to RSA1024 (v2).
3050 Closes ticket 29669.
3052 o Minor features (auto-formatting scripts):
3053 - When annotating C macros, never generate a line that our check-
3054 spaces script would reject. Closes ticket 31759.
3055 - When annotating C macros, try to remove cases of double-negation.
3056 Closes ticket 31779.
3058 o Minor features (best practices tracker):
3059 - Our best-practices tracker now integrates with our include-checker
3060 tool to keep track of how many layering violations we have not yet
3061 fixed. We hope to reduce this number over time to improve Tor's
3062 modularity. Closes ticket 31176.
3063 - Add a TOR_PRACTRACKER_OPTIONS variable for passing arguments to
3064 practracker from the environment. We may want this for continuous
3065 integration. Closes ticket 31309.
3066 - Give a warning rather than an error when a practracker exception
3067 is violated by a small amount, add a --list-overbroad option to
3068 practracker that lists exceptions that are stricter than they need
3069 to be, and provide an environment variable for disabling
3070 practracker. Closes ticket 30752.
3071 - Our best-practices tracker now looks at headers as well as C
3072 files. Closes ticket 31175.
3074 o Minor features (build system):
3075 - Make pkg-config use --prefix when cross-compiling, if
3076 PKG_CONFIG_PATH is not set. Closes ticket 32191.
3077 - Add --disable-manpage and --disable-html-manual options to
3078 configure script. This will enable shortening build times by not
3079 building documentation. Resolves issue 19381.
3081 o Minor features (compilation):
3082 - Log a more useful error message when we are compiling and one of
3083 the compile-time hardening options we have selected can be linked
3084 but not executed. Closes ticket 27530.
3086 o Minor features (configuration):
3087 - The configuration code has been extended to allow splitting
3088 configuration data across multiple objects. Previously, all
3089 configuration data needed to be kept in a single object, which
3090 tended to become bloated. Closes ticket 31240.
3092 o Minor features (continuous integration):
3093 - When building on Appveyor and Travis, pass the "-k" flag to make,
3094 so that we are informed of all compilation failures, not just the
3095 first one or two. Closes ticket 31372.
3096 - When running CI builds on Travis, put some random data in
3097 ~/.torrc, to make sure no tests are reading the Tor configuration
3098 file from its default location. Resolves issue 30102.
3100 o Minor features (debugging):
3101 - Log a nonfatal assertion failure if we encounter a configuration
3102 line whose command is "CLEAR" but which has a nonempty value. This
3103 should be impossible, according to the rules of our configuration
3104 line parsing. Closes ticket 31529.
3106 o Minor features (geoip):
3107 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
3108 Country database. Closes ticket 32685.
3110 o Minor features (git hooks):
3111 - Our pre-commit git hook now checks for a special file before
3112 running practracker, so that practracker only runs on branches
3113 that are based on master. Since the pre-push hook calls the pre-
3114 commit hook, practracker will also only run before pushes of
3115 branches based on master. Closes ticket 30979.
3117 o Minor features (git scripts):
3118 - Add a "--" command-line argument, to separate git-push-all.sh
3119 script arguments from arguments that are passed through to git
3120 push. Closes ticket 31314.
3121 - Add a -r <remote-name> argument to git-push-all.sh, so the script
3122 can push test branches to a personal remote. Closes ticket 31314.
3123 - Add a -t <test-branch-prefix> argument to git-merge-forward.sh and
3124 git-push-all.sh, which makes these scripts create, merge forward,
3125 and push test branches. Closes ticket 31314.
3126 - Add a -u argument to git-merge-forward.sh, so that the script can
3127 re-use existing test branches after a merge failure and fix.
3128 Closes ticket 31314.
3129 - Add a TOR_GIT_PUSH env var, which sets the default git push
3130 command and arguments for git-push-all.sh. Closes ticket 31314.
3131 - Add a TOR_PUSH_DELAY variable to git-push-all.sh, which makes the
3132 script push master and maint branches with a delay between each
3133 branch. These delays trigger the CI jobs in a set order, which
3134 should show the most likely failures first. Also make pushes
3135 atomic by default, and make the script pass any command-line
3136 arguments to git push. Closes ticket 29879.
3137 - Call the shellcheck script from the pre-commit hook. Closes
3139 - Skip pushing test branches that are the same as a remote
3140 maint/release/master branch in git-push-all.sh by default. Add a
3141 -s argument, so git-push-all.sh can push all test branches. Closes
3144 o Minor features (IPv6, logging):
3145 - Log IPv6 addresses as well as IPv4 addresses when describing
3146 routerinfos, routerstatuses, and nodes. Closes ticket 21003.
3148 o Minor features (maintenance scripts):
3149 - Add a Coccinelle script to detect bugs caused by incrementing or
3150 decrementing a variable inside a call to log_debug(). Since
3151 log_debug() is a macro whose arguments are conditionally
3152 evaluated, it is usually an error to do this. One such bug was
3153 30628, in which SENDME cells were miscounted by a decrement
3154 operator inside a log_debug() call. Closes ticket 30743.
3156 o Minor features (onion service v3):
3157 - Do not allow single hop clients to fetch or post an HS descriptor
3158 from an HSDir. Closes ticket 24964.
3160 o Minor features (onion service):
3161 - Disallow single-hop clients at the introduction point. We've
3162 removed Tor2web support a while back and single-hop rendezvous
3163 attempts are blocked at the relays. This change should remove load
3164 off the network from spammy clients. Close ticket 24963.
3166 o Minor features (onion services v3):
3167 - Assist users who try to setup v2 client authorization in v3 onion
3168 services by pointing them to the right documentation. Closes
3171 o Minor features (stem tests):
3172 - Change "make test-stem" so it only runs the stem tests that use
3173 tor. This change makes test-stem faster and more reliable. Closes
3176 o Minor features (testing):
3177 - When running tests that attempt to look up hostnames, replace the
3178 libc name lookup functions with ones that do not actually touch
3179 the network. This way, the tests complete more quickly in the
3180 presence of a slow or missing DNS resolver. Closes ticket 31841.
3181 - Add a script to invoke "tor --dump-config" and "tor
3182 --verify-config" with various configuration options, and see
3183 whether tor's resulting configuration or error messages are what
3184 we expect. Use it for integration testing of our +Option and
3185 /Option flags. Closes ticket 31637.
3186 - Improve test coverage for our existing configuration parsing and
3187 management API. Closes ticket 30893.
3188 - Add integration tests to make sure that practracker gives the
3189 outputs we expect. Closes ticket 31477.
3190 - The practracker self-tests are now run as part of the Tor test
3191 suite. Closes ticket 31304.
3193 o Minor features (testing, continuous integration):
3194 - Disable all but one Travis CI macOS build, to mitigate slow
3195 scheduling of Travis macOS jobs. Closes ticket 32177.
3196 - Run the chutney IPv6 networks as part of Travis CI. Closes
3198 - Simplify the Travis CI build matrix, and optimise for build time.
3199 Closes ticket 31859.
3200 - Use Windows Server 2019 instead of Windows Server 2016 in our
3201 Appveyor builds. Closes ticket 32086.
3203 o Minor features (token bucket):
3204 - Implement a generic token bucket that uses a single counter, for
3205 use in anti-DoS onion service work. Closes ticket 30687.
3207 o Minor bugfixes (Appveyor continuous integration):
3208 - Avoid spurious errors when Appveyor CI fails before the install
3209 step. Fixes bug 31884; bugfix on 0.3.4.2-alpha.
3211 o Minor bugfixes (best practices tracker):
3212 - Fix a few issues in the best-practices script, including tests,
3213 tab tolerance, error reporting, and directory-exclusion logic.
3214 Fixes bug 29746; bugfix on 0.4.1.1-alpha.
3215 - When running check-best-practices, only consider files in the src
3216 subdirectory. Previously we had recursively considered all
3217 subdirectories, which made us get confused by the temporary
3218 directories made by "make distcheck". Fixes bug 31578; bugfix
3221 o Minor bugfixes (build system):
3222 - Interpret "--disable-module-dirauth=no" correctly. Fixes bug
3223 32124; bugfix on 0.3.4.1-alpha.
3224 - Interpret "--with-tcmalloc=no" correctly. Fixes bug 32124; bugfix
3226 - Stop failing when jemalloc is requested, but tcmalloc is not
3227 found. Fixes bug 32124; bugfix on 0.3.5.1-alpha.
3228 - When pkg-config is not installed, or a library that depends on
3229 pkg-config is not found, tell the user what to do to fix the
3230 problem. Fixes bug 31922; bugfix on 0.3.1.1-alpha.
3231 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
3232 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
3234 o Minor bugfixes (chutney, makefiles, documentation):
3235 - "make test-network-all" now shows the warnings from each test-
3236 network.sh run on the console, so developers see new warnings
3237 early. We've also improved the documentation for this feature, and
3238 renamed a Makefile variable so the code is self-documenting. Fixes
3239 bug 30455; bugfix on 0.3.0.4-rc.
3241 o Minor bugfixes (client, onion service v3):
3242 - Fix a BUG() assertion that occurs within a very small race window
3243 between when a client intro circuit opens and when its descriptor
3244 gets cleaned up from the cache. The circuit is now closed early,
3245 which will trigger a re-fetch of the descriptor and continue the
3246 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
3248 o Minor bugfixes (code quality):
3249 - Fix "make check-includes" so it runs correctly on out-of-tree
3250 builds. Fixes bug 31335; bugfix on 0.3.5.1-alpha.
3252 o Minor bugfixes (compilation):
3253 - Add more stub functions to fix compilation on Android with link-
3254 time optimization when --disable-module-dirauth is used.
3255 Previously, these compilation settings would make the compiler
3256 look for functions that didn't exist. Fixes bug 31552; bugfix
3258 - Suppress spurious float-conversion warnings from GCC when calling
3259 floating-point classifier functions on FreeBSD. Fixes part of bug
3260 31687; bugfix on 0.3.1.5-alpha.
3262 o Minor bugfixes (configuration):
3263 - Invalid floating-point values in the configuration file are now
3264 treated as errors in the configuration. Previously, they were
3265 ignored and treated as zero. Fixes bug 31475; bugfix on 0.0.1.
3267 o Minor bugfixes (connections):
3268 - Avoid trying to read data from closed connections, which can cause
3269 needless loops in Libevent and infinite loops in Shadow. Fixes bug
3270 30344; bugfix on 0.1.1.1-alpha.
3272 o Minor bugfixes (controller protocol):
3273 - Fix the MAPADDRESS controller command to accept one or more
3274 arguments. Previously, it required two or more arguments, and
3275 ignored the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
3277 o Minor bugfixes (coverity):
3278 - Add an assertion when parsing a BEGIN cell so that coverity can be
3279 sure that we are not about to dereference a NULL address. Fixes
3280 bug 31026; bugfix on 0.2.4.7-alpha. This is CID 1447296.
3281 - In our siphash implementation, when building for coverity, use
3282 memcpy in place of a switch statement, so that coverity can tell
3283 we are not accessing out-of-bounds memory. Fixes bug 31025; bugfix
3284 on 0.2.8.1-alpha. This is tracked as CID 1447293 and 1447295.
3285 - Fix several coverity warnings from our unit tests. Fixes bug
3286 31030; bugfix on 0.2.4.1-alpha, 0.3.2.1-alpha, and 0.4.0.1-alpha.
3288 o Minor bugfixes (crash):
3289 - When running Tor with an option like --verify-config or
3290 --dump-config that does not start the event loop, avoid crashing
3291 if we try to exit early because of an error. Fixes bug 32407;
3292 bugfix on 0.3.3.1-alpha.
3294 o Minor bugfixes (developer tooling):
3295 - Only log git script changes in the post-merge script when the
3296 merge was to the master branch. Fixes bug 31040; bugfix
3299 o Minor bugfixes (directory authorities):
3300 - Return a distinct status when formatting annotations fails. Fixes
3301 bug 30780; bugfix on 0.2.0.8-alpha.
3303 o Minor bugfixes (error handling):
3304 - Always lock the backtrace buffer before it is used. Fixes bug
3305 31734; bugfix on 0.2.5.3-alpha.
3306 - On abort, try harder to flush the output buffers of log messages.
3307 On some platforms (macOS), log messages could be discarded when
3308 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3309 - Report the tor version whenever an assertion fails. Previously, we
3310 only reported the Tor version on some crashes, and some non-fatal
3311 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3312 - When tor aborts due to an error, close log file descriptors before
3313 aborting. Closing the logs makes some OSes flush log file buffers,
3314 rather than deleting buffered log lines. Fixes bug 31594; bugfix
3317 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6):
3318 - When extracting an IPv6 address from a PF-based proxy, verify that
3319 we are actually configured to receive an IPv6 address, and log an
3320 internal error if not. Fixes part of bug 31687; bugfix
3323 o Minor bugfixes (git hooks):
3324 - Remove a duplicate call to practracker from the pre-push hook. The
3325 pre-push hook already calls the pre-commit hook, which calls
3326 practracker. Fixes bug 31462; bugfix on 0.4.1.1-alpha.
3328 o Minor bugfixes (git scripts):
3329 - Stop hard-coding the bash path in the git scripts. Some OSes don't
3330 have bash in /usr/bin, others have an ancient bash at this path.
3331 Fixes bug 30840; bugfix on 0.4.0.1-alpha.
3332 - Stop hard-coding the tor master branch name and worktree path in
3333 the git scripts. Fixes bug 30841; bugfix on 0.4.0.1-alpha.
3334 - Allow git-push-all.sh to be run from any directory. Previously,
3335 the script only worked if run from an upstream worktree directory.
3336 Closes ticket 31678.
3338 o Minor bugfixes (guards):
3339 - When tor is missing descriptors for some primary entry guards,
3340 make the log message less alarming. It's normal for descriptors to
3341 expire, as long as tor fetches new ones soon after. Fixes bug
3342 31657; bugfix on 0.3.3.1-alpha.
3344 o Minor bugfixes (ipv6):
3345 - Check for private IPv6 addresses alongside their IPv4 equivalents
3346 when authorities check descriptors. Previously, we only checked
3347 for private IPv4 addresses. Fixes bug 31088; bugfix on
3348 0.2.3.21-rc. Patch by Neel Chauhan.
3349 - When parsing microdescriptors, we should check the IPv6 exit
3350 policy alongside IPv4. Previously, we checked both exit policies
3351 for only router info structures, while microdescriptors were
3352 IPv4-only. Fixes bug 27284; bugfix on 0.2.3.1-alpha. Patch by
3355 o Minor bugfixes (logging):
3356 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
3357 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
3358 - Disable backtrace signal handlers when shutting down tor. Fixes
3359 bug 31614; bugfix on 0.2.5.2-alpha.
3360 - Rate-limit our the logging message about the obsolete .exit
3361 notation. Previously, there was no limit on this warning, which
3362 could potentially be triggered many times by a hostile website.
3363 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
3364 - When initialising log domain masks, only set known log domains.
3365 Fixes bug 31854; bugfix on 0.2.1.1-alpha.
3366 - Change log level of message "Hash of session info was not as
3367 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
3369 - Fix a code issue that would have broken our parsing of log domains
3370 as soon as we had 33 of them. Fortunately, we still only have 29.
3371 Fixes bug 31451; bugfix on 0.4.1.4-rc.
3373 o Minor bugfixes (logging, protocol violations):
3374 - Do not log a nonfatal assertion failure when receiving a VERSIONS
3375 cell on a connection using the obsolete v1 link protocol. Log a
3376 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
3378 o Minor bugfixes (mainloop, periodic events, in-process API):
3379 - Reset the periodic events' "enabled" flag when Tor is shut down
3380 cleanly. Previously, this flag was left on, which caused periodic
3381 events not to be re-enabled when Tor was relaunched in-process
3382 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
3385 o Minor bugfixes (memory management):
3386 - Stop leaking a small amount of memory in nt_service_install(), in
3387 unreachable code. Fixes bug 30799; bugfix on 0.2.0.7-alpha. Patch
3390 o Minor bugfixes (modules):
3391 - Explain what the optional Directory Authority module is, and what
3392 happens when it is disabled. Fixes bug 31825; bugfix
3395 o Minor bugfixes (multithreading):
3396 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
3397 31736; bugfix on 0.0.7.
3399 o Minor bugfixes (networking, IP addresses):
3400 - When parsing addresses via Tor's internal DNS lookup API, reject
3401 IPv4 addresses in square brackets, and accept IPv6 addresses in
3402 square brackets. This change completes the work started in 23082,
3403 making address parsing consistent between tor's internal DNS
3404 lookup and address parsing APIs. Fixes bug 30721; bugfix
3406 - When parsing addresses via Tor's internal address:port parsing and
3407 DNS lookup APIs, require IPv6 addresses with ports to have square
3408 brackets. But allow IPv6 addresses without ports, whether or not
3409 they have square brackets. Fixes bug 30721; bugfix
3412 o Minor bugfixes (onion service v3):
3413 - When purging the client descriptor cache, close any introduction
3414 point circuits associated with purged cache entries. This avoids
3415 picking those circuits later when connecting to the same
3416 introduction points. Fixes bug 30921; bugfix on 0.3.2.1-alpha.
3418 o Minor bugfixes (onion services):
3419 - In the hs_ident_circuit_t data structure, remove the unused field
3420 circuit_type and the respective argument in hs_ident_circuit_new().
3421 This field was set by clients (for introduction) and services (for
3422 introduction and rendezvous) but was never used afterwards. Fixes
3423 bug 31490; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
3425 o Minor bugfixes (operator tools):
3426 - Make tor-print-ed-signing-cert(1) print certificate expiration
3427 date in RFC 1123 and UNIX timestamp formats, to make output
3428 machine readable. Fixes bug 31012; bugfix on 0.3.5.1-alpha.
3430 o Minor bugfixes (process management):
3431 - Remove overly strict assertions that triggered when a pluggable
3432 transport failed to launch. Fixes bug 31091; bugfix
3434 - Remove an assertion in the Unix process backend. This assertion
3435 would trigger when we failed to find the executable for a child
3436 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
3438 o Minor bugfixes (relay):
3439 - Avoid crashing when starting with a corrupt keys directory where
3440 the old ntor key and the new ntor key are identical. Fixes bug
3441 30916; bugfix on 0.2.4.8-alpha.
3443 o Minor bugfixes (rust):
3444 - Correctly exclude a redundant rust build job in Travis. Fixes bug
3445 31463; bugfix on 0.3.5.4-alpha.
3446 - Raise the minimum rustc version to 1.31.0, as checked by configure
3447 and CI. Fixes bug 31442; bugfix on 0.3.5.4-alpha.
3449 o Minor bugfixes (sendme, code structure):
3450 - Rename the trunnel SENDME file definition from sendme.trunnel to
3451 sendme_cell.trunnel to avoid having twice sendme.{c|h} in the
3452 repository. Fixes bug 30769; bugfix on 0.4.1.1-alpha.
3454 o Minor bugfixes (statistics):
3455 - Stop removing the ed25519 signature if the extra info file is too
3456 big. If the signature data was removed, but the keyword was kept,
3457 this could result in an unparseable extra info file. Fixes bug
3458 30958; bugfix on 0.2.7.2-alpha.
3460 o Minor bugfixes (subsystems):
3461 - Make the subsystem init order match the subsystem module
3462 dependencies. Call windows process security APIs as early as
3463 possible. Initialize logging before network and time, so that
3464 network and time can use logging. Fixes bug 31615; bugfix
3467 o Minor bugfixes (testing):
3468 - Avoid intermittent test failures due to a test that had relied on
3469 inconsistent timing sources. Fixes bug 31995; bugfix
3471 - When testing port rebinding, don't busy-wait for tor to log.
3472 Instead, actually sleep for a short time before polling again.
3473 Also improve the formatting of control commands and log messages.
3474 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
3475 - Teach the util/socketpair_ersatz test to work correctly when we
3476 have no network stack configured. Fixes bug 30804; bugfix
3479 o Minor bugfixes (tests, SunOS):
3480 - Avoid a map_anon_nofork test failure due to a signed/unsigned
3481 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
3483 o Minor bugfixes (tls, logging):
3484 - Log bugs about the TLS read buffer's length only once, rather than
3485 filling the logs with similar warnings. Fixes bug 31939; bugfix
3488 o Minor bugfixes (v2 single onion services):
3489 - Always retry v2 single onion service intro and rend circuits with
3490 a 3-hop path. Previously, v2 single onion services used a 3-hop
3491 path when rendezvous circuits were retried after a remote or
3492 delayed failure, but a 1-hop path for immediate retries. Fixes bug
3493 23818; bugfix on 0.2.9.3-alpha.
3495 o Minor bugfixes (v3 onion services):
3496 - When cleaning up intro circuits for a v3 onion service, don't
3497 remove circuits that have an established or pending circuit, even
3498 if they ran out of retries. This way, we don't remove a circuit on
3499 its last retry. Fixes bug 31652; bugfix on 0.3.2.1-alpha.
3501 o Minor bugfixes (v3 single onion services):
3502 - Always retry v3 single onion service intro and rend circuits with
3503 a 3-hop path. Previously, v3 single onion services used a 3-hop
3504 path when rend circuits were retried after a remote or delayed
3505 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
3506 bugfix on 0.3.2.1-alpha.
3507 - Make v3 single onion services fall back to a 3-hop intro, when all
3508 intro points are unreachable via a 1-hop path. Previously, v3
3509 single onion services failed when all intro nodes were unreachable
3510 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
3512 o Code simplification and refactoring:
3513 - Refactor connection_control_process_inbuf() to reduce the size of
3514 a practracker exception. Closes ticket 31840.
3515 - Refactor the microdescs_parse_from_string() function into smaller
3516 pieces, for better comprehensibility. Closes ticket 31675.
3517 - Use SEVERITY_MASK_IDX() to find the LOG_* mask indexes in the unit
3518 tests and fuzzers, rather than using hard-coded values. Closes
3520 - Interface for function `decrypt_desc_layer` cleaned up. Closes
3524 - Correct the description of "GuardLifetime". Fixes bug 31189;
3525 bugfix on 0.3.0.1-alpha.
3526 - Make clear in the man page, in both the bandwidth section and the
3527 AccountingMax section, that Tor counts in powers of two, not
3528 powers of ten: 1 GByte is 1024*1024*1024 bytes, not one billion
3529 bytes. Resolves ticket 32106.
3530 - Document the signal-safe logging behaviour in the tor man page.
3531 Also add some comments to the relevant functions. Closes
3533 - Explain why we can't destroy the backtrace buffer mutex. Explain
3534 why we don't need to destroy the log mutex. Closes ticket 31736.
3535 - The Tor source code repository now includes a (somewhat dated)
3536 description of Tor's modular architecture, in doc/HACKING/design.
3537 This is based on the old "tor-guts.git" repository, which we are
3538 adopting and superseding. Closes ticket 31849.
3539 - Improve documentation in circuit padding subsystem. Patch by
3540 Tobias Pulls. Closes ticket 31113.
3541 - Include an example usage for IPv6 ORPort in our sample torrc.
3542 Closes ticket 31320; patch from Ali Raheem.
3543 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
3544 notice.html so that operators no longer have to host it
3545 themselves. Closes ticket 31089.
3548 - No longer include recommended package digests in votes as detailed
3549 in proposal 301. The RecommendedPackages torrc option is
3550 deprecated and will no longer have any effect. "package" lines
3551 will still be considered when computing consensuses for consensus
3552 methods that include them. (This change has no effect on the list
3553 of recommended Tor versions, which is still in use.) Closes
3555 - Remove torctl.in from contrib/dist directory. Resolves
3559 - Require C99 standards-conforming code in Travis CI, but allow GNU
3560 gcc extensions. Also activates clang's -Wtypedef-redefinition
3561 warnings. Build some jobs with -std=gnu99, and some jobs without.
3562 Closes ticket 32500.
3563 - Run shellcheck for all non-third-party shell scripts that are
3564 shipped with Tor. Closes ticket 29533.
3565 - When checking shell scripts, ignore any user-created directories.
3566 Closes ticket 30967.
3568 o Code simplification and refactoring (config handling):
3569 - Extract our variable manipulation code from confparse.c to a new
3570 lower-level typedvar.h module. Closes ticket 30864.
3571 - Lower another layer of object management from confparse.c to a
3572 more general tool. Now typed structure members are accessible via
3573 an abstract type. Implements ticket 30914.
3574 - Move our backend logic for working with configuration and state
3575 files into a lower-level library, since it no longer depends on
3576 any tor-specific functionality. Closes ticket 31626.
3577 - Numerous simplifications in configuration-handling logic: remove
3578 duplicated macro definitions, replace magical names with flags,
3579 and refactor "TestingTorNetwork" to use the same default-option
3580 logic as the rest of Tor. Closes ticket 30935.
3581 - Replace our ad-hoc set of flags for configuration variables and
3582 configuration variable types with fine-grained orthogonal flags
3583 corresponding to the actual behavior we want. Closes ticket 31625.
3585 o Code simplification and refactoring (misc):
3586 - Eliminate some uses of lower-level control reply abstractions,
3587 primarily in the onion_helper functions. Closes ticket 30889.
3588 - Rework bootstrap tracking to use the new publish-subscribe
3589 subsystem. Closes ticket 29976.
3590 - Rewrite format_node_description() and router_get_verbose_nickname()
3591 to use strlcpy() and strlcat(). The previous implementation used
3592 memcpy() and pointer arithmetic, which was error-prone. Closes
3593 ticket 31545. This is CID 1452819.
3594 - Split extrainfo_dump_to_string() into smaller functions. Closes
3596 - Use the ptrdiff_t type consistently for expressing variable
3597 offsets and pointer differences. Previously we incorrectly (but
3598 harmlessly) used int and sometimes off_t for these cases. Closes
3600 - Use the subsystems mechanism to manage the main event loop code.
3601 Closes ticket 30806.
3602 - Various simplifications and minor improvements to the circuit
3603 padding machines. Patch by Tobias Pulls. Closes tickets 31112
3606 o Documentation (hard-coded directories):
3607 - Improve the documentation for the DirAuthority and FallbackDir
3608 torrc options. Closes ticket 30955.
3610 o Documentation (tor.1 man page):
3611 - Fix typo in tor.1 man page: the option is "--help", not "-help".
3612 Fixes bug 31008; bugfix on 0.2.2.9-alpha.
3614 o Testing (continuous integration):
3615 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
3616 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
3617 until we can fix some Bionic permissions issues (see ticket
3618 32240). Related to ticket 31919.
3619 - Install the mingw OpenSSL package in Appveyor. This makes sure
3620 that the OpenSSL headers and libraries match in Tor's Appveyor
3621 builds. (This bug was triggered by an Appveyor image update.)
3622 Fixes bug 32449; bugfix on 0.3.5.6-rc.
3623 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
3626 Changes in version 0.4.1.7 - 2019-12-09
3627 This release backports several bugfixes to improve stability and
3628 correctness. Anyone experiencing build problems or crashes with 0.4.1.6,
3629 including all relays relying on AccountingMax, should upgrade.
3631 o Major features (directory authorities, backport from 0.4.2.2-alpha):
3632 - Directory authorities now reject relays running all currently
3633 deprecated release series. The currently supported release series
3634 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
3636 o Major bugfixes (embedded Tor, backport from 0.4.2.2-alpha):
3637 - Avoid a possible crash when restarting Tor in embedded mode and
3638 enabling a different set of publish/subscribe messages. Fixes bug
3639 31898; bugfix on 0.4.1.1-alpha.
3641 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
3642 - Relays now respect their AccountingMax bandwidth again. When
3643 relays entered "soft" hibernation (which typically starts when
3644 we've hit 90% of our AccountingMax), we had stopped checking
3645 whether we should enter hard hibernation. Soft hibernation refuses
3646 new connections and new circuits, but the existing circuits can
3647 continue, meaning that relays could have exceeded their configured
3648 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
3650 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
3651 - Stop ignoring torrc options after an %include directive, when the
3652 included directory ends with a file that does not contain any
3653 config options (but does contain comments or whitespace). Fixes
3654 bug 31408; bugfix on 0.3.1.1-alpha.
3656 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
3657 - Onion services now always use the exact number of intro points
3658 configured with the HiddenServiceNumIntroductionPoints option (or
3659 fewer if nodes are excluded). Before, a service could sometimes
3660 pick more intro points than configured. Fixes bug 31548; bugfix
3663 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
3664 - When building on Appveyor and Travis, pass the "-k" flag to make,
3665 so that we are informed of all compilation failures, not just the
3666 first one or two. Closes ticket 31372.
3668 o Minor features (geoip, backport from 0.4.2.5):
3669 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
3670 Country database. Closes ticket 32685.
3672 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
3673 - Avoid spurious errors when Appveyor CI fails before the install step.
3674 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
3676 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
3677 - Fix a BUG() assertion that occurs within a very small race window
3678 between when a client intro circuit opens and when its descriptor
3679 gets cleaned up from the cache. The circuit is now closed early,
3680 which will trigger a re-fetch of the descriptor and continue the
3681 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
3683 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
3684 - Avoid trying to read data from closed connections, which can cause
3685 needless loops in Libevent and infinite loops in Shadow. Fixes bug
3686 30344; bugfix on 0.1.1.1-alpha.
3688 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
3689 - On abort, try harder to flush the output buffers of log messages.
3690 On some platforms (macOS), log messages could be discarded when
3691 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3692 - Report the tor version whenever an assertion fails. Previously, we
3693 only reported the Tor version on some crashes, and some non-fatal
3694 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3695 - When tor aborts due to an error, close log file descriptors before
3696 aborting. Closing the logs makes some OSes flush log file buffers,
3697 rather than deleting buffered log lines. Fixes bug 31594; bugfix
3700 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
3701 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
3702 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
3703 - Disable backtrace signal handlers when shutting down tor. Fixes
3704 bug 31614; bugfix on 0.2.5.2-alpha.
3705 - Rate-limit our the logging message about the obsolete .exit
3706 notation. Previously, there was no limit on this warning, which
3707 could potentially be triggered many times by a hostile website.
3708 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
3710 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
3711 - Do not log a nonfatal assertion failure when receiving a VERSIONS
3712 cell on a connection using the obsolete v1 link protocol. Log a
3713 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
3715 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
3716 - Reset the periodic events' "enabled" flag when Tor is shut down
3717 cleanly. Previously, this flag was left on, which caused periodic
3718 events not to be re-enabled when Tor was relaunched in-process
3719 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
3722 o Minor bugfixes (multithreading, backport from 0.4.2.2-alpha):
3723 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
3724 31736; bugfix on 0.0.7.
3726 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
3727 - Remove overly strict assertions that triggered when a pluggable
3728 transport failed to launch. Fixes bug 31091; bugfix
3730 - Remove an assertion in the Unix process backend. This assertion
3731 would trigger when we failed to find the executable for a child
3732 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
3734 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
3735 - Avoid crashing when starting with a corrupt keys directory where
3736 the old ntor key and the new ntor key are identical. Fixes bug
3737 30916; bugfix on 0.2.4.8-alpha.
3739 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
3740 - When testing port rebinding, don't busy-wait for tor to log.
3741 Instead, actually sleep for a short time before polling again.
3742 Also improve the formatting of control commands and log messages.
3743 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
3745 o Minor bugfixes (tests, SunOS, backport from 0.4.2.2-alpha):
3746 - Avoid a map_anon_nofork test failure due to a signed/unsigned
3747 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
3749 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
3750 - Log bugs about the TLS read buffer's length only once, rather than
3751 filling the logs with similar warnings. Fixes bug 31939; bugfix
3754 o Documentation (backport from 0.4.2.2-alpha):
3755 - Explain why we can't destroy the backtrace buffer mutex. Explain
3756 why we don't need to destroy the log mutex. Closes ticket 31736.
3758 o Testing (continuous integration, backport from 0.4.2.3-alpha):
3759 - Disable all but one Travis CI macOS build, to mitigate slow
3760 scheduling of Travis macOS jobs. Closes ticket 32177.
3761 - Run the chutney IPv6 networks as part of Travis CI. Closes
3763 - Simplify the Travis CI build matrix, and optimise for build time.
3764 Closes ticket 31859.
3765 - Use Windows Server 2019 instead of Windows Server 2016 in our
3766 Appveyor builds. Closes ticket 32086.
3768 o Testing (continuous integration, backport from 0.4.2.4-rc):
3769 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
3770 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
3771 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
3772 until we can fix some Bionic permissions issues (see ticket
3773 32240). Related to ticket 31919.
3774 - Install the mingw OpenSSL package in Appveyor. This makes sure
3775 that the OpenSSL headers and libraries match in Tor's Appveyor
3776 builds. (This bug was triggered by an Appveyor image update.)
3777 Fixes bug 32449; bugfix on 0.3.5.6-rc.
3779 o Testing (continuous integration, backport from 0.4.2.5):
3780 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
3781 extensions. Also activates clang's -Wtypedef-redefinition warnings.
3782 Build some jobs with -std=gnu99, and some jobs without.
3783 Closes ticket 32500.
3786 Changes in version 0.4.0.6 - 2019-12-09
3787 This is the second stable release in the 0.4.0.x series. This release
3788 backports several bugfixes to improve stability and correctness. Anyone
3789 experiencing build problems or crashes with 0.4.0.5, including all relays
3790 relying on AccountingMax, should upgrade.
3792 Note that, per our support policy, support for the 0.4.0.x series will end
3793 on 2 Feb 2020. Anyone still running 0.4.0.x should plan to upgrade to the
3794 latest stable release, or downgrade to 0.3.5.x, which will get long-term
3795 support until 1 Feb 2022.
3797 o Directory authority changes (backport from 0.4.1.5):
3798 - The directory authority "dizum" has a new IP address. Closes
3801 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
3802 - Consider our directory information to have changed when our list
3803 of bridges changes. Previously, Tor would not re-compute the
3804 status of its directory information when bridges changed, and
3805 therefore would not realize that it was no longer able to build
3806 circuits. Fixes part of bug 29875.
3807 - Do not count previously configured working bridges towards our
3808 total of working bridges. Previously, when Tor's list of bridges
3809 changed, it would think that the old bridges were still usable,
3810 and delay fetching router descriptors for the new ones. Fixes part
3811 of bug 29875; bugfix on 0.3.0.1-alpha.
3813 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
3814 - When considering upgrading circuits from "waiting for guard" to
3815 "open", always ignore circuits that are marked for close. Otherwise,
3816 we can end up in the situation where a subsystem is notified that
3817 a closing circuit has just opened, leading to undesirable
3818 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
3820 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
3821 - Properly clean up the introduction point map when circuits change
3822 purpose from onion service circuits to pathbias, measurement, or
3823 other circuit types. This should fix some service-side instances
3824 of introduction point failure. Fixes bug 29034; bugfix
3827 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
3828 - Fix an unreachable bug in which an introduction point could try to
3829 send an INTRODUCE_ACK with a status code that Trunnel would refuse
3830 to encode, leading the relay to assert(). We've consolidated the
3831 ABI values into Trunnel now. Fixes bug 30454; bugfix
3833 - Clients can now handle unknown status codes from INTRODUCE_ACK
3834 cells. (The NACK behavior will stay the same.) This will allow us
3835 to extend status codes in the future without breaking the normal
3836 client behavior. Fixes another part of bug 30454; bugfix
3839 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
3840 - Relays now respect their AccountingMax bandwidth again. When
3841 relays entered "soft" hibernation (which typically starts when
3842 we've hit 90% of our AccountingMax), we had stopped checking
3843 whether we should enter hard hibernation. Soft hibernation refuses
3844 new connections and new circuits, but the existing circuits can
3845 continue, meaning that relays could have exceeded their configured
3846 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
3848 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
3849 - Stop ignoring torrc options after an %include directive, when the
3850 included directory ends with a file that does not contain any
3851 config options (but does contain comments or whitespace). Fixes
3852 bug 31408; bugfix on 0.3.1.1-alpha.
3854 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
3855 - Onion services now always use the exact number of intro points
3856 configured with the HiddenServiceNumIntroductionPoints option (or
3857 fewer if nodes are excluded). Before, a service could sometimes
3858 pick more intro points than configured. Fixes bug 31548; bugfix
3861 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
3862 - Add a "--list-modules" command to print a list of which compile-
3863 time modules are enabled. Closes ticket 30452.
3865 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
3866 - Remove sudo configuration lines from .travis.yml as they are no
3867 longer needed with current Travis build environment. Resolves
3870 o Minor features (continuous integration, backport from 0.4.1.4-rc):
3871 - Our Travis configuration now uses Chutney to run some network
3872 integration tests automatically. Closes ticket 29280.
3874 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
3875 - When building on Appveyor and Travis, pass the "-k" flag to make,
3876 so that we are informed of all compilation failures, not just the
3877 first one or two. Closes ticket 31372.
3879 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
3880 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
3881 in December 2018 (of which ~122 were still functional), with a
3882 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
3883 in June 2019. Closes ticket 28795.
3885 o Minor features (geoip, backport from 0.4.2.5):
3886 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
3887 Country database. Closes ticket 32685.
3889 o Minor features (stem tests, backport from 0.4.2.1-alpha):
3890 - Change "make test-stem" so it only runs the stem tests that use
3891 tor. This change makes test-stem faster and more reliable. Closes
3894 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
3895 - Avoid spurious errors when Appveyor CI fails before the install step.
3896 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
3898 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
3899 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
3900 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
3902 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
3903 - Fix a logic error that prevented the SessionGroup sub-option from
3904 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
3906 o Minor bugfixes (circuit padding, backport from 0.4.1.4-rc):
3907 - On relays, properly check that a padding machine is absent before
3908 logging a warning about it being absent. Fixes bug 30649; bugfix
3911 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
3912 - Fix a BUG() assertion that occurs within a very small race window
3913 between when a client intro circuit opens and when its descriptor
3914 gets cleaned up from the cache. The circuit is now closed early,
3915 which will trigger a re-fetch of the descriptor and continue the
3916 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
3918 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
3919 - Don't believe clock skew results from NETINFO cells that appear to
3920 arrive before we sent the VERSIONS cells they are responding to.
3921 Previously, we would accept them up to 3 minutes "in the past".
3922 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3924 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
3925 - Fix a compilation warning on Windows about casting a function
3926 pointer for GetTickCount64(). Fixes bug 31374; bugfix
3929 o Minor bugfixes (compilation, backport from 0.4.1.5):
3930 - Avoid using labs() on time_t, which can cause compilation warnings
3931 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3933 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
3934 - Suppress spurious float-conversion warnings from GCC when calling
3935 floating-point classifier functions on FreeBSD. Fixes part of bug
3936 31687; bugfix on 0.3.1.5-alpha.
3938 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
3939 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
3940 due to missing declarations of abort(), and prevent other such
3941 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
3943 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
3944 - Fix a bug that prevented us from supporting SOCKS5 proxies that
3945 want authentication along with configured (but unused!)
3946 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
3948 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
3949 - Avoid trying to read data from closed connections, which can cause
3950 needless loops in Libevent and infinite loops in Shadow. Fixes bug
3951 30344; bugfix on 0.1.1.1-alpha.
3953 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
3954 - Allow the test-stem job to fail in Travis, because it sometimes
3955 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
3956 - Skip test_rebind on macOS in Travis, because it is unreliable on
3957 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3958 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
3959 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3961 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
3962 - Avoid a set of possible code paths that could try to use freed
3963 memory in routerlist_free() while Tor was exiting. Fixes bug
3964 31003; bugfix on 0.1.2.2-alpha.
3966 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
3967 - Stop crashing after parsing an unknown descriptor purpose
3968 annotation. We think this bug can only be triggered by modifying a
3969 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
3971 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
3972 - Move the "bandwidth-file-headers" line in directory authority
3973 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
3976 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
3977 - On abort, try harder to flush the output buffers of log messages.
3978 On some platforms (macOS), log messages could be discarded when
3979 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3980 - Report the tor version whenever an assertion fails. Previously, we
3981 only reported the Tor version on some crashes, and some non-fatal
3982 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3984 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
3985 - When extracting an IPv6 address from a PF-based proxy, verify that
3986 we are actually configured to receive an IPv6 address, and log an
3987 internal error if not. Fixes part of bug 31687; bugfix
3990 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
3991 - When tor is missing descriptors for some primary entry guards,
3992 make the log message less alarming. It's normal for descriptors to
3993 expire, as long as tor fetches new ones soon after. Fixes bug
3994 31657; bugfix on 0.3.3.1-alpha.
3996 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
3997 - Do not log a warning when running with an OpenSSL version other
3998 than the one Tor was compiled with, if the two versions should be
3999 compatible. Previously, we would warn whenever the version was
4000 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
4002 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
4003 - Change log level of message "Hash of session info was not as
4004 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
4007 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
4008 - Rate-limit our the logging message about the obsolete .exit
4009 notation. Previously, there was no limit on this warning, which
4010 could potentially be triggered many times by a hostile website.
4011 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
4013 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
4014 - Do not log a nonfatal assertion failure when receiving a VERSIONS
4015 cell on a connection using the obsolete v1 link protocol. Log a
4016 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
4018 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
4019 - Reset the periodic events' "enabled" flag when Tor is shut down
4020 cleanly. Previously, this flag was left on, which caused periodic
4021 events not to be re-enabled when Tor was relaunched in-process
4022 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
4025 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
4026 - Avoid a minor memory leak that could occur on relays when failing
4027 to create a "keys" directory. Fixes bug 30148; bugfix
4030 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
4031 - Fix a trivial memory leak when parsing an invalid value
4032 from a download schedule in the configuration. Fixes bug
4033 30894; bugfix on 0.3.4.1-alpha.
4035 o Minor bugfixes (NetBSD, backport from 0.4.1.2-alpha):
4036 - Fix usage of minherit() on NetBSD and other platforms that define
4037 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
4038 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
4040 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
4041 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
4042 implemenation) when failing to load an onion service client
4043 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
4045 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
4046 - When purging the DNS cache because of an out-of-memory condition,
4047 try purging just the older entries at first. Previously, we would
4048 always purge the whole thing. Fixes bug 29617; bugfix
4051 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
4052 - Avoid crashing in our tor_vasprintf() implementation on systems
4053 that define neither vasprintf() nor _vscprintf(). (This bug has
4054 been here long enough that we question whether people are running
4055 Tor on such systems, but we're applying the fix out of caution.)
4056 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
4059 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
4060 - Remove overly strict assertions that triggered when a pluggable
4061 transport failed to launch. Fixes bug 31091; bugfix
4063 - Remove an assertion in the Unix process backend. This assertion
4064 would trigger when we failed to find the executable for a child
4065 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
4067 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
4068 - Avoid crashing when starting with a corrupt keys directory where
4069 the old ntor key and the new ntor key are identical. Fixes bug
4070 30916; bugfix on 0.2.4.8-alpha.
4072 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
4073 - Correctly exclude a redundant rust build job in Travis. Fixes bug
4074 31463; bugfix on 0.3.5.4-alpha.
4076 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
4077 - When testing port rebinding, don't busy-wait for tor to log.
4078 Instead, actually sleep for a short time before polling again.
4079 Also improve the formatting of control commands and log messages.
4080 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
4082 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
4083 - Log bugs about the TLS read buffer's length only once, rather than
4084 filling the logs with similar warnings. Fixes bug 31939; bugfix
4087 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
4088 - Always retry v2 single onion service intro and rend circuits with
4089 a 3-hop path. Previously, v2 single onion services used a 3-hop
4090 path when rendezvous circuits were retried after a remote or
4091 delayed failure, but a 1-hop path for immediate retries. Fixes bug
4092 23818; bugfix on 0.2.9.3-alpha.
4093 - Make v3 single onion services fall back to a 3-hop intro, when all
4094 intro points are unreachable via a 1-hop path. Previously, v3
4095 single onion services failed when all intro nodes were unreachable
4096 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
4098 o Documentation (backport from 0.4.2.1-alpha):
4099 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
4100 notice.html so that operators no longer have to host it
4101 themselves. Closes ticket 31089.
4103 o Testing (backport from 0.4.1.2-alpha):
4104 - Specify torrc paths (with empty files) when launching tor in
4105 integration tests; refrain from reading user and system torrcs.
4106 Resolves issue 29702.
4108 o Testing (continuous integration, backport from 0.4.1.1-alpha):
4109 - In Travis, show stem's tor log after failure. Closes ticket 30234.
4111 o Testing (continuous integration, backport from 0.4.1.5):
4112 - In Travis, make stem log a controller trace to the console, and
4113 tail stem's tor log after failure. Closes ticket 30591.
4114 - In Travis, only run the stem tests that use a tor binary. Closes
4117 o Testing (continuous integration, backport from 0.4.2.3-alpha):
4118 - Disable all but one Travis CI macOS build, to mitigate slow
4119 scheduling of Travis macOS jobs. Closes ticket 32177.
4120 - Run the chutney IPv6 networks as part of Travis CI. Closes
4122 - Simplify the Travis CI build matrix, and optimise for build time.
4123 Closes ticket 31859.
4124 - Use Windows Server 2019 instead of Windows Server 2016 in our
4125 Appveyor builds. Closes ticket 32086.
4127 o Testing (continuous integration, backport from 0.4.2.4-rc):
4128 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
4129 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
4130 until we can fix some Bionic permissions issues (see ticket
4131 32240). Related to ticket 31919.
4132 - Install the mingw OpenSSL package in Appveyor. This makes sure
4133 that the OpenSSL headers and libraries match in Tor's Appveyor
4134 builds. (This bug was triggered by an Appveyor image update.)
4135 Fixes bug 32449; bugfix on 0.3.5.6-rc.
4136 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
4138 o Testing (continuous integration, backport from 0.4.2.5):
4139 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
4140 extensions. Also activates clang's -Wtypedef-redefinition warnings.
4141 Build some jobs with -std=gnu99, and some jobs without.
4142 Closes ticket 32500.
4145 Changes in version 0.3.5.9 - 2019-12-09
4146 Tor 0.3.5.9 backports serveral fixes from later releases, including
4147 several that affect bridge users, relay stability, onion services,
4150 o Directory authority changes (backport from 0.4.1.5):
4151 - The directory authority "dizum" has a new IP address. Closes
4154 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
4155 - Consider our directory information to have changed when our list
4156 of bridges changes. Previously, Tor would not re-compute the
4157 status of its directory information when bridges changed, and
4158 therefore would not realize that it was no longer able to build
4159 circuits. Fixes part of bug 29875.
4160 - Do not count previously configured working bridges towards our
4161 total of working bridges. Previously, when Tor's list of bridges
4162 changed, it would think that the old bridges were still usable,
4163 and delay fetching router descriptors for the new ones. Fixes part
4164 of bug 29875; bugfix on 0.3.0.1-alpha.
4166 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
4167 - When considering upgrading circuits from "waiting for guard" to
4168 "open", always ignore circuits that are marked for close. Otherwise,
4169 we can end up in the situation where a subsystem is notified that
4170 a closing circuit has just opened, leading to undesirable
4171 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
4173 o Major bugfixes (NSS, relay, backport from 0.4.0.4-rc):
4174 - When running with NSS, disable TLS 1.2 ciphersuites that use
4175 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
4176 these ciphersuites don't work -- which caused relays to fail to
4177 handshake with one another when these ciphersuites were enabled.
4178 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
4180 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
4181 - Properly clean up the introduction point map when circuits change
4182 purpose from onion service circuits to pathbias, measurement, or
4183 other circuit types. This should fix some service-side instances
4184 of introduction point failure. Fixes bug 29034; bugfix
4187 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
4188 - Fix an unreachable bug in which an introduction point could try to
4189 send an INTRODUCE_ACK with a status code that Trunnel would refuse
4190 to encode, leading the relay to assert(). We've consolidated the
4191 ABI values into Trunnel now. Fixes bug 30454; bugfix
4193 - Clients can now handle unknown status codes from INTRODUCE_ACK
4194 cells. (The NACK behavior will stay the same.) This will allow us
4195 to extend status codes in the future without breaking the normal
4196 client behavior. Fixes another part of bug 30454; bugfix
4199 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
4200 - Stop ignoring torrc options after an %include directive, when the
4201 included directory ends with a file that does not contain any
4202 config options (but does contain comments or whitespace). Fixes
4203 bug 31408; bugfix on 0.3.1.1-alpha.
4205 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
4206 - Onion services now always use the exact number of intro points
4207 configured with the HiddenServiceNumIntroductionPoints option (or
4208 fewer if nodes are excluded). Before, a service could sometimes
4209 pick more intro points than configured. Fixes bug 31548; bugfix
4212 o Minor features (address selection, backport from 0.4.0.3-alpha):
4213 - Treat the subnet 100.64.0.0/10 as public for some purposes;
4214 private for others. This subnet is the RFC 6598 (Carrier Grade
4215 NAT) IP range, and is deployed by many ISPs as an alternative to
4216 RFC 1918 that does not break existing internal networks. Tor now
4217 blocks SOCKS and control ports on these addresses and warns users
4218 if client ports or ExtORPorts are listening on a RFC 6598 address.
4219 Closes ticket 28525. Patch by Neel Chauhan.
4221 o Minor features (bandwidth authority, backport from 0.4.0.4-rc):
4222 - Make bandwidth authorities ignore relays that are reported in the
4223 bandwidth file with the flag "vote=0". This change allows us to
4224 report unmeasured relays for diagnostic reasons without including
4225 their bandwidth in the bandwidth authorities' vote. Closes
4228 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
4229 - Add a "--list-modules" command to print a list of which compile-
4230 time modules are enabled. Closes ticket 30452.
4232 o Minor features (continuous integration, backport from 0.4.0.4-rc):
4233 - On Travis Rust builds, cleanup Rust registry and refrain from
4234 caching the "target/" directory to speed up builds. Resolves
4237 o Minor features (continuous integration, backport from 0.4.0.5):
4238 - In Travis, tell timelimit to use stem's backtrace signals, and
4239 launch python directly from timelimit, so python receives the
4240 signals from timelimit, rather than make. Closes ticket 30117.
4242 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
4243 - Remove sudo configuration lines from .travis.yml as they are no
4244 longer needed with current Travis build environment. Resolves
4247 o Minor features (continuous integration, backport from 0.4.1.4-rc):
4248 - Our Travis configuration now uses Chutney to run some network
4249 integration tests automatically. Closes ticket 29280.
4251 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
4252 - When building on Appveyor and Travis, pass the "-k" flag to make,
4253 so that we are informed of all compilation failures, not just the
4254 first one or two. Closes ticket 31372.
4256 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
4257 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
4258 in December 2018 (of which ~122 were still functional), with a
4259 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
4260 in June 2019. Closes ticket 28795.
4262 o Minor features (geoip, backport from 0.4.2.5):
4263 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
4264 Country database. Closes ticket 32685.
4266 o Minor features (NSS, diagnostic, backport from 0.4.0.4-rc):
4267 - Try to log an error from NSS (if there is any) and a more useful
4268 description of our situation if we are using NSS and a call to
4269 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
4271 o Minor features (stem tests, backport from 0.4.2.1-alpha):
4272 - Change "make test-stem" so it only runs the stem tests that use
4273 tor. This change makes test-stem faster and more reliable. Closes
4276 o Minor bugfixes (security, backport from 0.4.0.4-rc):
4277 - Verify in more places that we are not about to create a buffer
4278 with more than INT_MAX bytes, to avoid possible OOB access in the
4279 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
4280 fixed by Tobias Stoeckmann.
4281 - Fix a potential double free bug when reading huge bandwidth files.
4282 The issue is not exploitable in the current Tor network because
4283 the vulnerable code is only reached when directory authorities
4284 read bandwidth files, but bandwidth files come from a trusted
4285 source (usually the authorities themselves). Furthermore, the
4286 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
4287 which are not used by any of the current authorities. Fixes bug
4288 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
4291 o Minor bugfix (continuous integration, backport from 0.4.0.4-rc):
4292 - Reset coverage state on disk after Travis CI has finished. This
4293 should prevent future coverage merge errors from causing the test
4294 suite for the "process" subsystem to fail. The process subsystem
4295 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
4297 - Terminate test-stem if it takes more than 9.5 minutes to run.
4298 (Travis terminates the job after 10 minutes of no output.)
4299 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
4301 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
4302 - Avoid spurious errors when Appveyor CI fails before the install step.
4303 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
4305 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
4306 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
4307 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
4309 o Minor bugfixes (C correctness, backport from 0.4.0.4-rc):
4310 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
4311 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
4314 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
4315 - Fix a logic error that prevented the SessionGroup sub-option from
4316 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
4318 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
4319 - Fix a BUG() assertion that occurs within a very small race window
4320 between when a client intro circuit opens and when its descriptor
4321 gets cleaned up from the cache. The circuit is now closed early,
4322 which will trigger a re-fetch of the descriptor and continue the
4323 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
4325 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
4326 - Don't believe clock skew results from NETINFO cells that appear to
4327 arrive before we sent the VERSIONS cells they are responding to.
4328 Previously, we would accept them up to 3 minutes "in the past".
4329 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
4331 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
4332 - Fix a compilation warning on Windows about casting a function
4333 pointer for GetTickCount64(). Fixes bug 31374; bugfix
4336 o Minor bugfixes (compilation, backport from 0.4.0.2-alpha):
4337 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
4338 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
4340 o Minor bugfixes (compilation, backport from 0.4.1.5):
4341 - Avoid using labs() on time_t, which can cause compilation warnings
4342 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
4344 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
4345 - Suppress spurious float-conversion warnings from GCC when calling
4346 floating-point classifier functions on FreeBSD. Fixes part of bug
4347 31687; bugfix on 0.3.1.5-alpha.
4349 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
4350 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
4351 due to missing declarations of abort(), and prevent other such
4352 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
4354 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
4355 - Fix a bug that prevented us from supporting SOCKS5 proxies that
4356 want authentication along with configured (but unused!)
4357 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
4359 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
4360 - Avoid trying to read data from closed connections, which can cause
4361 needless loops in Libevent and infinite loops in Shadow. Fixes bug
4362 30344; bugfix on 0.1.1.1-alpha.
4364 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
4365 - Allow the test-stem job to fail in Travis, because it sometimes
4366 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
4367 - Skip test_rebind on macOS in Travis, because it is unreliable on
4368 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
4369 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
4370 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
4372 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
4373 - Avoid a set of possible code paths that could try to use freed
4374 memory in routerlist_free() while Tor was exiting. Fixes bug
4375 31003; bugfix on 0.1.2.2-alpha.
4377 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
4378 - Stop crashing after parsing an unknown descriptor purpose
4379 annotation. We think this bug can only be triggered by modifying a
4380 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
4382 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
4383 - Move the "bandwidth-file-headers" line in directory authority
4384 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
4387 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
4388 - On abort, try harder to flush the output buffers of log messages.
4389 On some platforms (macOS), log messages could be discarded when
4390 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
4391 - Report the tor version whenever an assertion fails. Previously, we
4392 only reported the Tor version on some crashes, and some non-fatal
4393 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
4395 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
4396 - When extracting an IPv6 address from a PF-based proxy, verify that
4397 we are actually configured to receive an IPv6 address, and log an
4398 internal error if not. Fixes part of bug 31687; bugfix
4401 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
4402 - When tor is missing descriptors for some primary entry guards,
4403 make the log message less alarming. It's normal for descriptors to
4404 expire, as long as tor fetches new ones soon after. Fixes bug
4405 31657; bugfix on 0.3.3.1-alpha.
4407 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
4408 - Avoid logging that we are relaxing a circuit timeout when that
4409 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
4411 o Minor bugfixes (logging, backport from 0.4.0.3-alpha):
4412 - Correct a misleading error message when IPv4Only or IPv6Only is
4413 used but the resolved address can not be interpreted as an address
4414 of the specified IP version. Fixes bug 13221; bugfix on
4415 0.2.3.9-alpha. Patch from Kris Katterjohn.
4416 - Log the correct port number for listening sockets when "auto" is
4417 used to let Tor pick the port number. Previously, port 0 was
4418 logged instead of the actual port number. Fixes bug 29144; bugfix
4419 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
4420 - Stop logging a BUG() warning when Tor is waiting for exit
4421 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
4423 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
4424 - Do not log a warning when running with an OpenSSL version other
4425 than the one Tor was compiled with, if the two versions should be
4426 compatible. Previously, we would warn whenever the version was
4427 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
4429 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
4430 - Change log level of message "Hash of session info was not as
4431 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
4434 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
4435 - Rate-limit our the logging message about the obsolete .exit
4436 notation. Previously, there was no limit on this warning, which
4437 could potentially be triggered many times by a hostile website.
4438 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
4440 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
4441 - Do not log a nonfatal assertion failure when receiving a VERSIONS
4442 cell on a connection using the obsolete v1 link protocol. Log a
4443 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
4445 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
4446 - Reset the periodic events' "enabled" flag when Tor is shut down
4447 cleanly. Previously, this flag was left on, which caused periodic
4448 events not to be re-enabled when Tor was relaunched in-process
4449 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
4452 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
4453 - Avoid a minor memory leak that could occur on relays when failing
4454 to create a "keys" directory. Fixes bug 30148; bugfix
4457 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
4458 - Fix a trivial memory leak when parsing an invalid value
4459 from a download schedule in the configuration. Fixes bug
4460 30894; bugfix on 0.3.4.1-alpha.
4462 o Minor bugfixes (memory management, backport from 0.4.0.3-alpha):
4463 - Refactor the shared random state's memory management so that it
4464 actually takes ownership of the shared random value pointers.
4465 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
4467 o Minor bugfixes (memory management, testing, backport from 0.4.0.3-alpha):
4468 - Stop leaking parts of the shared random state in the shared-random
4469 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
4471 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
4472 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
4473 implemenation) when failing to load an onion service client
4474 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
4476 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
4477 - When purging the DNS cache because of an out-of-memory condition,
4478 try purging just the older entries at first. Previously, we would
4479 always purge the whole thing. Fixes bug 29617; bugfix
4482 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
4483 - Avoid crashing in our tor_vasprintf() implementation on systems
4484 that define neither vasprintf() nor _vscprintf(). (This bug has
4485 been here long enough that we question whether people are running
4486 Tor on such systems, but we're applying the fix out of caution.)
4487 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
4490 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
4491 - Avoid crashing when starting with a corrupt keys directory where
4492 the old ntor key and the new ntor key are identical. Fixes bug
4493 30916; bugfix on 0.2.4.8-alpha.
4495 o Minor bugfixes (rust, backport from 0.4.0.5):
4496 - Abort on panic in all build profiles, instead of potentially
4497 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
4499 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
4500 - Correctly exclude a redundant rust build job in Travis. Fixes bug
4501 31463; bugfix on 0.3.5.4-alpha.
4503 o Minor bugfixes (single onion services, backport from 0.4.0.3-alpha):
4504 - Allow connections to single onion services to remain idle without
4505 being disconnected. Previously, relays acting as rendezvous points
4506 for single onion services were mistakenly closing idle rendezvous
4507 circuits after 60 seconds, thinking that they were unused
4508 directory-fetching circuits that had served their purpose. Fixes
4509 bug 29665; bugfix on 0.2.1.26.
4511 o Minor bugfixes (stats, backport from 0.4.0.3-alpha):
4512 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
4513 relay and bridge extra-info documents. Fixes bug 29017; bugfix
4516 o Minor bugfixes (testing, backport from 0.4.0.3-alpha):
4517 - Downgrade some LOG_ERR messages in the address/* tests to
4518 warnings. The LOG_ERR messages were occurring when we had no
4519 configured network. We were failing the unit tests, because we
4520 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
4521 29530; bugfix on 0.3.5.8.
4522 - Fix our gcov wrapper script to look for object files at the
4523 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
4525 o Minor bugfixes (testing, backport from 0.4.0.4-rc):
4526 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
4527 recent test-network.sh to use new chutney features in CI. Fixes
4528 bug 29703; bugfix on 0.2.9.1-alpha.
4529 - Fix a test failure on Windows caused by an unexpected "BUG"
4530 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
4533 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
4534 - When testing port rebinding, don't busy-wait for tor to log.
4535 Instead, actually sleep for a short time before polling again.
4536 Also improve the formatting of control commands and log messages.
4537 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
4539 o Minor bugfixes (TLS protocol, backport form 0.4.0.4-rc):
4540 - When classifying a client's selection of TLS ciphers, if the
4541 client ciphers are not yet available, do not cache the result.
4542 Previously, we had cached the unavailability of the cipher list
4543 and never looked again, which in turn led us to assume that the
4544 client only supported the ancient V1 link protocol. This, in turn,
4545 was causing Stem integration tests to stall in some cases. Fixes
4546 bug 30021; bugfix on 0.2.4.8-alpha.
4548 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
4549 - Log bugs about the TLS read buffer's length only once, rather than
4550 filling the logs with similar warnings. Fixes bug 31939; bugfix
4553 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
4554 - Always retry v2 single onion service intro and rend circuits with
4555 a 3-hop path. Previously, v2 single onion services used a 3-hop
4556 path when rendezvous circuits were retried after a remote or
4557 delayed failure, but a 1-hop path for immediate retries. Fixes bug
4558 23818; bugfix on 0.2.9.3-alpha.
4559 - Make v3 single onion services fall back to a 3-hop intro, when all
4560 intro points are unreachable via a 1-hop path. Previously, v3
4561 single onion services failed when all intro nodes were unreachable
4562 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
4564 o Minor bugfixes (Windows, CI, backport from 0.4.0.3-alpha):
4565 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
4566 Windows Server 2012 R2 job. The remaining 2 jobs still provide
4567 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
4568 fast_finish, so failed jobs terminate the build immediately. Fixes
4569 bug 29601; bugfix on 0.3.5.4-alpha.
4571 o Documentation (backport from 0.4.2.1-alpha):
4572 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
4573 notice.html so that operators no longer have to host it
4574 themselves. Closes ticket 31089.
4576 o Testing (backport from 0.4.1.2-alpha):
4577 - Specify torrc paths (with empty files) when launching tor in
4578 integration tests; refrain from reading user and system torrcs.
4579 Resolves issue 29702.
4581 o Testing (continuous integration, backport from 0.4.1.1-alpha):
4582 - In Travis, show stem's tor log after failure. Closes ticket 30234.
4584 o Testing (continuous integration, backport from 0.4.1.5):
4585 - In Travis, make stem log a controller trace to the console, and
4586 tail stem's tor log after failure. Closes ticket 30591.
4587 - In Travis, only run the stem tests that use a tor binary. Closes
4590 o Testing (continuous integration, backport from 0.4.2.3-alpha):
4591 - Disable all but one Travis CI macOS build, to mitigate slow
4592 scheduling of Travis macOS jobs. Closes ticket 32177.
4593 - Run the chutney IPv6 networks as part of Travis CI. Closes
4595 - Simplify the Travis CI build matrix, and optimise for build time.
4596 Closes ticket 31859.
4597 - Use Windows Server 2019 instead of Windows Server 2016 in our
4598 Appveyor builds. Closes ticket 32086.
4600 o Testing (continuous integration, backport from 0.4.2.4-rc):
4601 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
4602 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
4603 until we can fix some Bionic permissions issues (see ticket
4604 32240). Related to ticket 31919.
4605 - Install the mingw OpenSSL package in Appveyor. This makes sure
4606 that the OpenSSL headers and libraries match in Tor's Appveyor
4607 builds. (This bug was triggered by an Appveyor image update.)
4608 Fixes bug 32449; bugfix on 0.3.5.6-rc.
4609 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
4611 o Testing (continuous integration, backport from 0.4.2.5):
4612 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
4613 extensions. Also activates clang's -Wtypedef-redefinition warnings.
4614 Build some jobs with -std=gnu99, and some jobs without.
4615 Closes ticket 32500.
4618 Changes in version 0.4.1.6 - 2019-09-19
4619 This release backports several bugfixes to improve stability and
4620 correctness. Anyone experiencing build problems or crashes with 0.4.1.5,
4621 or experiencing reliability issues with single onion services, should
4624 o Major bugfixes (crash, Linux, Android, backport from 0.4.2.1-alpha):
4625 - Tolerate systems (including some Android installations) where
4626 madvise and MADV_DONTDUMP are available at build-time, but not at
4627 run time. Previously, these systems would notice a failed syscall
4628 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
4629 - Tolerate systems (including some Linux installations) where
4630 madvise and/or MADV_DONTFORK are available at build-time, but not
4631 at run time. Previously, these systems would notice a failed
4632 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
4634 o Minor features (stem tests, backport from 0.4.2.1-alpha):
4635 - Change "make test-stem" so it only runs the stem tests that use
4636 tor. This change makes test-stem faster and more reliable. Closes
4639 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
4640 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
4641 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
4643 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
4644 - Add more stub functions to fix compilation on Android with link-
4645 time optimization when --disable-module-dirauth is used.
4646 Previously, these compilation settings would make the compiler
4647 look for functions that didn't exist. Fixes bug 31552; bugfix
4649 - Suppress spurious float-conversion warnings from GCC when calling
4650 floating-point classifier functions on FreeBSD. Fixes part of bug
4651 31687; bugfix on 0.3.1.5-alpha.
4653 o Minor bugfixes (controller protocol):
4654 - Fix the MAPADDRESS controller command to accept one or more
4655 arguments. Previously, it required two or more arguments, and ignored
4656 the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
4658 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
4659 - When extracting an IPv6 address from a PF-based proxy, verify that
4660 we are actually configured to receive an IPv6 address, and log an
4661 internal error if not. Fixes part of bug 31687; bugfix
4664 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
4665 - When tor is missing descriptors for some primary entry guards,
4666 make the log message less alarming. It's normal for descriptors to
4667 expire, as long as tor fetches new ones soon after. Fixes bug
4668 31657; bugfix on 0.3.3.1-alpha.
4670 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
4671 - Change log level of message "Hash of session info was not as
4672 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
4675 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
4676 - Correctly exclude a redundant rust build job in Travis. Fixes bug
4677 31463; bugfix on 0.3.5.4-alpha.
4679 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
4680 - Always retry v2 single onion service intro and rend circuits with
4681 a 3-hop path. Previously, v2 single onion services used a 3-hop
4682 path when rendezvous circuits were retried after a remote or
4683 delayed failure, but a 1-hop path for immediate retries. Fixes bug
4684 23818; bugfix on 0.2.9.3-alpha.
4686 o Minor bugfixes (v3 single onion services, backport from 0.4.2.1-alpha):
4687 - Always retry v3 single onion service intro and rend circuits with
4688 a 3-hop path. Previously, v3 single onion services used a 3-hop
4689 path when rend circuits were retried after a remote or delayed
4690 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
4691 bugfix on 0.3.2.1-alpha.
4692 - Make v3 single onion services fall back to a 3-hop intro, when all
4693 intro points are unreachable via a 1-hop path. Previously, v3
4694 single onion services failed when all intro nodes were unreachable
4695 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
4697 o Documentation (backport from 0.4.2.1-alpha):
4698 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
4699 notice.html so that operators no longer have to host it
4700 themselves. Closes ticket 31089.
4703 Changes in version 0.4.1.5 - 2019-08-20
4704 This is the first stable release in the 0.4.1.x series. This series
4705 adds experimental circuit-level padding, authenticated SENDME cells to
4706 defend against certain attacks, and several performance improvements
4707 to save on CPU consumption. It fixes bugs in bootstrapping and v3
4708 onion services. It also includes numerous smaller features and
4709 bugfixes on earlier versions.
4711 Per our support policy, we will support the 0.4.1.x series for nine
4712 months, or until three months after the release of a stable 0.4.2.x:
4713 whichever is longer. If you need longer-term support, please stick
4714 with 0.3.5.x, which will we plan to support until Feb 2022.
4716 Below are the changes since 0.4.0.5. For a list of only the changes
4717 since 0.4.1.4-rc, see the ChangeLog file.
4719 o Directory authority changes:
4720 - The directory authority "dizum" has a new IP address. Closes
4723 o Major features (circuit padding):
4724 - Onion service clients now add padding cells at the start of their
4725 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
4726 look more like general purpose Exit traffic. The overhead for this
4727 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
4728 extra upstream cell and 10 downstream cells for INTRODUCE
4729 circuits. This feature is only enabled when also supported by the
4730 circuit's middle node. (Clients may specify fixed middle nodes
4731 with the MiddleNodes option, and may force-disable this feature
4732 with the CircuitPadding option.) Closes ticket 28634.
4734 o Major features (code organization):
4735 - Tor now includes a generic publish-subscribe message-passing
4736 subsystem that we can use to organize intermodule dependencies. We
4737 hope to use this to reduce dependencies between modules that don't
4738 need to be related, and to generally simplify our codebase. Closes
4741 o Major features (controller protocol):
4742 - Controller commands are now parsed using a generalized parsing
4743 subsystem. Previously, each controller command was responsible for
4744 parsing its own input, which led to strange inconsistencies.
4745 Closes ticket 30091.
4747 o Major features (flow control):
4748 - Implement authenticated SENDMEs as detailed in proposal 289. A
4749 SENDME cell now includes the digest of the traffic that it
4750 acknowledges, so that once an end point receives the SENDME, it
4751 can confirm the other side's knowledge of the previous cells that
4752 were sent, and prevent certain types of denial-of-service attacks.
4753 This behavior is controlled by two new consensus parameters: see
4754 the proposal for more details. Fixes ticket 26288.
4756 o Major features (performance):
4757 - Our node selection algorithm now excludes nodes in linear time.
4758 Previously, the algorithm was quadratic, which could slow down
4759 heavily used onion services. Closes ticket 30307.
4761 o Major features (performance, RNG):
4762 - Tor now constructs a fast secure pseudorandom number generator for
4763 each thread, to use when performance is critical. This PRNG is
4764 based on AES-CTR, using a buffering construction similar to
4765 libottery and the (newer) OpenBSD arc4random() code. It
4766 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
4767 small outputs. Although we believe it to be cryptographically
4768 strong, we are only using it when necessary for performance.
4769 Implements tickets 29023 and 29536.
4771 o Major bugfixes (bridges):
4772 - Consider our directory information to have changed when our list
4773 of bridges changes. Previously, Tor would not re-compute the
4774 status of its directory information when bridges changed, and
4775 therefore would not realize that it was no longer able to build
4776 circuits. Fixes part of bug 29875.
4777 - Do not count previously configured working bridges towards our
4778 total of working bridges. Previously, when Tor's list of bridges
4779 changed, it would think that the old bridges were still usable,
4780 and delay fetching router descriptors for the new ones. Fixes part
4781 of bug 29875; bugfix on 0.3.0.1-alpha.
4783 o Major bugfixes (circuit build, guard):
4784 - On relays, properly check that a padding machine is absent before
4785 logging a warning about it being absent. Fixes bug 30649; bugfix
4787 - When considering upgrading circuits from "waiting for guard" to
4788 "open", always ignore circuits that are marked for close. Otherwise,
4789 we can end up in the situation where a subsystem is notified that
4790 a closing circuit has just opened, leading to undesirable
4791 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
4793 o Major bugfixes (onion service reachability):
4794 - Properly clean up the introduction point map when circuits change
4795 purpose from onion service circuits to pathbias, measurement, or
4796 other circuit types. This should fix some service-side instances
4797 of introduction point failure. Fixes bug 29034; bugfix
4800 o Major bugfixes (onion service v3):
4801 - Fix an unreachable bug in which an introduction point could try to
4802 send an INTRODUCE_ACK with a status code that Trunnel would refuse
4803 to encode, leading the relay to assert(). We've consolidated the
4804 ABI values into Trunnel now. Fixes bug 30454; bugfix
4806 - Clients can now handle unknown status codes from INTRODUCE_ACK
4807 cells. (The NACK behavior will stay the same.) This will allow us
4808 to extend status codes in the future without breaking the normal
4809 client behavior. Fixes another part of bug 30454; bugfix
4812 o Minor features (authenticated SENDME):
4813 - Ensure that there is enough randomness on every circuit to prevent
4814 an attacker from successfully predicting the hashes they will need
4815 to include in authenticated SENDME cells. At a random interval, if
4816 we have not sent randomness already, we now leave some extra space
4817 at the end of a cell that we can fill with random bytes. Closes
4820 o Minor features (circuit padding logging):
4821 - Demote noisy client-side warn logs about circuit padding to protocol
4822 warnings. Add additional log messages and circuit ID fields to help
4823 with bug 30992 and any other future issues.
4825 o Minor features (circuit padding):
4826 - We now use a fast PRNG when scheduling circuit padding. Part of
4828 - Allow the padding machine designer to pick the edges of their
4829 histogram instead of trying to compute them automatically using an
4830 exponential formula. Resolves some undefined behavior in the case
4831 of small histograms and allows greater flexibility on machine
4832 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
4833 - Allow circuit padding machines to hold a circuit open until they
4834 are done padding it. Closes ticket 28780.
4836 o Minor features (compile-time modules):
4837 - Add a "--list-modules" command to print a list of which compile-
4838 time modules are enabled. Closes ticket 30452.
4840 o Minor features (continuous integration):
4841 - Our Travis configuration now uses Chutney to run some network
4842 integration tests automatically. Closes ticket 29280.
4843 - When running coverage builds on Travis, we now set
4844 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
4846 - Remove sudo configuration lines from .travis.yml as they are no
4847 longer needed with current Travis build environment. Resolves
4849 - In Travis, show stem's tor log after failure. Closes ticket 30234.
4851 o Minor features (controller):
4852 - Add onion service version 3 support to the HSFETCH command.
4853 Previously, only version 2 onion services were supported. Closes
4854 ticket 25417. Patch by Neel Chauhan.
4856 o Minor features (debugging):
4857 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
4858 logging of additional information during assert failure. Now we
4859 can use format strings to include information for trouble
4860 shooting. Resolves ticket 29662.
4862 o Minor features (defense in depth):
4863 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
4864 case a bug causes them to be used later. Closes ticket 30176.
4865 Patch from Tobias Stoeckmann.
4866 - Tor now uses a cryptographically strong PRNG even for decisions
4867 that we do not believe are security-sensitive. Previously, for
4868 performance reasons, we had used a trivially predictable linear
4869 congruential generator algorithm for certain load-balancing and
4870 statistical sampling decisions. Now we use our fast RNG in those
4871 cases. Closes ticket 29542.
4873 o Minor features (developer tools):
4874 - Tor's "practracker" test script now checks for files and functions
4875 that seem too long and complicated. Existing overlong functions
4876 and files are accepted for now, but should eventually be
4877 refactored. Closes ticket 29221.
4878 - Add some scripts used for git maintenance to scripts/git. Closes
4880 - Call practracker from pre-push and pre-commit git hooks to let
4881 developers know if they made any code style violations. Closes
4883 - Add a script to check that each header has a well-formed and
4884 unique guard macro. Closes ticket 29756.
4886 o Minor features (fallback directory list):
4887 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
4888 in December 2018 (of which ~122 were still functional), with a
4889 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
4890 in June 2019. Closes ticket 28795.
4892 o Minor features (geoip):
4893 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
4894 Country database. Closes ticket 30852.
4895 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
4896 Country database. Closes ticket 30522.
4898 o Minor features (HTTP tunnel):
4899 - Return an informative web page when the HTTPTunnelPort is used as
4900 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
4902 o Minor features (IPv6, v3 onion services):
4903 - Make v3 onion services put IPv6 addresses in service descriptors.
4904 Before this change, service descriptors only contained IPv4
4905 addresses. Implements 26992.
4907 o Minor features (logging):
4908 - Give a more useful assertion failure message if we think we have
4909 minherit() but we fail to make a region non-inheritable. Give a
4910 compile-time warning if our support for minherit() is incomplete.
4911 Closes ticket 30686.
4913 o Minor features (maintenance):
4914 - Add a new "make autostyle" target that developers can use to apply
4915 all automatic Tor style and consistency conversions to the
4916 codebase. Closes ticket 30539.
4918 o Minor features (modularity):
4919 - The "--disable-module-dirauth" compile-time option now disables
4920 even more dirauth-only code. Closes ticket 30345.
4922 o Minor features (performance):
4923 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
4924 1.1.1 and later), since they tend to be faster than tiny-keccak.
4925 Closes ticket 28837.
4927 o Minor features (testing):
4928 - The circuitpadding tests now use a reproducible RNG implementation,
4929 so that if a test fails, we can learn why. Part of ticket 28878.
4930 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
4931 to set the RNG seed for tests that use a reproducible RNG. Part of
4933 - When running tests in coverage mode, take additional care to make
4934 our coverage deterministic, so that we can accurately track
4935 changes in code coverage. Closes ticket 30519.
4936 - Tor's unit test code now contains helper functions to replace the
4937 PRNG with a deterministic or reproducible version for testing.
4938 Previously, various tests implemented this in various ways.
4939 Implements ticket 29732.
4940 - We now have a script, cov-test-determinism.sh, to identify places
4941 where our unit test coverage has become nondeterministic. Closes
4943 - Check that representative subsets of values of `int` and `unsigned
4944 int` can be represented by `void *`. Resolves issue 29537.
4946 o Minor bugfixes (bridge authority):
4947 - Bridge authorities now set bridges as running or non-running when
4948 about to dump their status to a file. Previously, they set bridges
4949 as running in response to a GETINFO command, but those shouldn't
4950 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
4951 Patch by Neel Chauhan.
4953 o Minor bugfixes (channel padding statistics):
4954 - Channel padding write totals and padding-enabled totals are now
4955 counted properly in relay extrainfo descriptors. Fixes bug 29231;
4956 bugfix on 0.3.1.1-alpha.
4958 o Minor bugfixes (circuit isolation):
4959 - Fix a logic error that prevented the SessionGroup sub-option from
4960 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
4962 o Minor bugfixes (circuit padding):
4963 - Add a "CircuitPadding" torrc option to disable circuit padding.
4964 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
4965 - Allow circuit padding machines to specify that they do not
4966 contribute much overhead, and provide consensus flags and torrc
4967 options to force clients to only use these low overhead machines.
4968 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
4969 - Provide a consensus parameter to fully disable circuit padding, to
4970 be used in emergency network overload situations. Fixes bug 30173;
4971 bugfix on 0.4.0.1-alpha.
4972 - The circuit padding subsystem will no longer schedule padding if
4973 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
4974 - Inspect a circuit-level cell queue before sending padding, to
4975 avoid sending padding while too much data is already queued. Fixes
4976 bug 29204; bugfix on 0.4.0.1-alpha.
4977 - Avoid calling monotime_absolute_usec() in circuit padding machines
4978 that do not use token removal or circuit RTT estimation. Fixes bug
4979 29085; bugfix on 0.4.0.1-alpha.
4981 o Minor bugfixes (clock skew detection):
4982 - Don't believe clock skew results from NETINFO cells that appear to
4983 arrive before we sent the VERSIONS cells they are responding to.
4984 Previously, we would accept them up to 3 minutes "in the past".
4985 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
4987 o Minor bugfixes (compatibility, standards compliance):
4988 - Fix a bug that would invoke undefined behavior on certain
4989 operating systems when trying to asprintf() a string exactly
4990 INT_MAX bytes long. We don't believe this is exploitable, but it's
4991 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
4992 Found and fixed by Tobias Stoeckmann.
4994 o Minor bugfixes (compilation warning):
4995 - Fix a compilation warning on Windows about casting a function
4996 pointer for GetTickCount64(). Fixes bug 31374; bugfix on
4999 o Minor bugfixes (compilation):
5000 - Avoid using labs() on time_t, which can cause compilation warnings
5001 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
5003 o Minor bugfixes (compilation, unusual configurations):
5004 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
5005 due to missing declarations of abort(), and prevent other such
5006 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
5008 o Minor bugfixes (configuration, proxies):
5009 - Fix a bug that prevented us from supporting SOCKS5 proxies that
5010 want authentication along with configured (but unused!)
5011 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
5013 o Minor bugfixes (continuous integration):
5014 - Allow the test-stem job to fail in Travis, because it sometimes
5015 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
5016 - Skip test_rebind on macOS in Travis, because it is unreliable on
5017 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
5018 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
5019 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
5021 o Minor bugfixes (controller protocol):
5022 - Teach the controller parser to distinguish an object preceded by
5023 an argument list from one without. Previously, it couldn't
5024 distinguish an argument list from the first line of a multiline
5025 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
5027 o Minor bugfixes (crash on exit):
5028 - Avoid a set of possible code paths that could try to use freed
5029 memory in routerlist_free() while Tor was exiting. Fixes bug
5030 31003; bugfix on 0.1.2.2-alpha.
5032 o Minor bugfixes (developer tooling):
5033 - Fix pre-push hook to allow fixup and squash commits when pushing
5034 to non-upstream git remote. Fixes bug 30286; bugfix
5037 o Minor bugfixes (directory authorities):
5038 - Stop crashing after parsing an unknown descriptor purpose
5039 annotation. We think this bug can only be triggered by modifying a
5040 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
5041 - Move the "bandwidth-file-headers" line in directory authority
5042 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
5044 - Directory authorities with IPv6 support now always mark themselves
5045 as reachable via IPv6. Fixes bug 24338; bugfix on 0.2.4.1-alpha.
5046 Patch by Neel Chauhan.
5048 o Minor bugfixes (documentation):
5049 - Improve the documentation for using MapAddress with ".exit". Fixes
5050 bug 30109; bugfix on 0.1.0.1-rc.
5051 - Improve the monotonic time module and function documentation to
5052 explain what "monotonic" actually means, and document some results
5053 that have surprised people. Fixes bug 29640; bugfix
5055 - Use proper formatting when providing an example on quoting options
5056 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
5058 o Minor bugfixes (logging):
5059 - Do not log a warning when running with an OpenSSL version other
5060 than the one Tor was compiled with, if the two versions should be
5061 compatible. Previously, we would warn whenever the version was
5062 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
5063 - Warn operators when the MyFamily option is set but ContactInfo is
5064 missing, as the latter should be set too. Fixes bug 25110; bugfix
5067 o Minor bugfixes (memory leaks):
5068 - Avoid a minor memory leak that could occur on relays when failing
5069 to create a "keys" directory. Fixes bug 30148; bugfix
5071 - Fix a trivial memory leak when parsing an invalid value from a
5072 download schedule in the configuration. Fixes bug 30894; bugfix
5075 o Minor bugfixes (NetBSD):
5076 - Fix usage of minherit() on NetBSD and other platforms that define
5077 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
5078 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
5080 o Minor bugfixes (onion services):
5081 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
5082 implemenation) when failing to load an onion service client
5083 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
5084 - When refusing to launch a controller's HSFETCH request because of
5085 rate-limiting, respond to the controller with a new response,
5086 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
5087 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
5089 - When relaunching a circuit to a rendezvous service, mark the
5090 circuit as needing high-uptime routers as appropriate. Fixes bug
5091 17357; bugfix on 0.1.0.1-rc. Patch by Neel Chauhan.
5092 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
5093 (IPv6 support for v3 onion services is still incomplete: see
5094 ticket 23493 for details.) Fixes bug 23588; bugfix on
5095 0.3.2.1-alpha. Patch by Neel Chauhan.
5097 o Minor bugfixes (onion services, performance):
5098 - When building circuits to onion services, call tor_addr_parse()
5099 less often. Previously, we called tor_addr_parse() in
5100 circuit_is_acceptable() even if its output wasn't used. This
5101 change should improve performance when building circuits. Fixes
5102 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
5104 o Minor bugfixes (out-of-memory handler):
5105 - When purging the DNS cache because of an out-of-memory condition,
5106 try purging just the older entries at first. Previously, we would
5107 always purge the whole thing. Fixes bug 29617; bugfix
5110 o Minor bugfixes (performance):
5111 - When checking whether a node is a bridge, use a fast check to make
5112 sure that its identity is set. Previously, we used a constant-time
5113 check, which is not necessary in this case. Fixes bug 30308;
5114 bugfix on 0.3.5.1-alpha.
5116 o Minor bugfixes (pluggable transports):
5117 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
5118 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
5120 o Minor bugfixes (portability):
5121 - Avoid crashing in our tor_vasprintf() implementation on systems
5122 that define neither vasprintf() nor _vscprintf(). (This bug has
5123 been here long enough that we question whether people are running
5124 Tor on such systems, but we're applying the fix out of caution.)
5125 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
5128 o Minor bugfixes (probability distributions):
5129 - Refactor and improve parts of the probability distribution code
5130 that made Coverity complain. Fixes bug 29805; bugfix
5133 o Minor bugfixes (python):
5134 - Stop assuming that /usr/bin/python3 exists. For scripts that work
5135 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
5136 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
5138 o Minor bugfixes (relay):
5139 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
5140 is auto, act as if ExitRelay is 1. Previously, we would ignore
5141 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
5142 0.3.5.1-alpha. Patch by Neel Chauhan.
5144 o Minor bugfixes (static analysis):
5145 - Fix several spurious Coverity warnings about the unit tests, to
5146 lower our chances of missing real warnings in the future. Fixes
5147 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
5149 o Minor bugfixes (stats):
5150 - When ExtraInfoStatistics is 0, stop including bandwidth usage
5151 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
5152 bridge statistics by country in extra-info documents. Fixes bug
5153 29018; bugfix on 0.2.4.1-alpha.
5155 o Minor bugfixes (testing):
5156 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
5157 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
5158 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
5159 - Fix some incorrect code in the v3 onion service unit tests. Fixes
5160 bug 29243; bugfix on 0.3.2.1-alpha.
5161 - In the "routerkeys/*" tests, check the return values of mkdir()
5162 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
5163 Found by Coverity as CID 1444254.
5164 - Split test_utils_general() into several smaller test functions.
5165 This makes it easier to perform resource deallocation on assert
5166 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
5167 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
5169 o Minor bugfixes (tor-resolve):
5170 - Fix a memory leak in tor-resolve that could happen if Tor gave it
5171 a malformed SOCKS response. (Memory leaks in tor-resolve don't
5172 actually matter, but it's good to fix them anyway.) Fixes bug
5173 30151; bugfix on 0.4.0.1-alpha.
5175 o Code simplification and refactoring:
5176 - Abstract out the low-level formatting of replies on the control
5177 port. Implements ticket 30007.
5178 - Add several assertions in an attempt to fix some Coverity
5179 warnings. Closes ticket 30149.
5180 - Introduce a connection_dir_buf_add() helper function that checks
5181 for compress_state of dir_connection_t and automatically writes a
5182 string to directory connection with or without compression.
5183 Resolves issue 28816.
5184 - Make the base32_decode() API return the number of bytes written,
5185 for consistency with base64_decode(). Closes ticket 28913.
5186 - Move most relay-only periodic events out of mainloop.c into the
5187 relay subsystem. Closes ticket 30414.
5188 - Refactor and encapsulate parts of the codebase that manipulate
5189 crypt_path_t objects. Resolves issue 30236.
5190 - Refactor several places in our code that Coverity incorrectly
5191 believed might have memory leaks. Closes ticket 30147.
5192 - Remove redundant return values in crypto_format, and the
5193 associated return value checks elsewhere in the code. Make the
5194 implementations in crypto_format consistent, and remove redundant
5195 code. Resolves ticket 29660.
5196 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
5197 it is not a constant-time function. Closes ticket 30309.
5198 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
5199 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
5200 bugfix on 0.3.2.1-alpha.
5201 - Simplify v3 onion service link specifier handling code. Fixes bug
5202 23576; bugfix on 0.3.2.1-alpha.
5203 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
5204 code. Resolves ticket 29108.
5205 - Split control.c into several submodules, in preparation for
5206 distributing its current responsibilities throughout the codebase.
5207 Closes ticket 29894.
5208 - Start to move responsibility for knowing about periodic events to
5209 the appropriate subsystems, so that the mainloop doesn't need to
5210 know all the periodic events in the rest of the codebase.
5211 Implements tickets 30293 and 30294.
5214 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
5215 Closes ticket 30630.
5216 - Document how to find git commits and tags for bug fixes in
5217 CodingStandards.md. Update some file documentation. Closes
5221 - Remove the linux-tor-prio.sh script from contrib/operator-tools
5222 directory. Resolves issue 29434.
5223 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
5224 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
5228 - Specify torrc paths (with empty files) when launching tor in
5229 integration tests; refrain from reading user and system torrcs.
5230 Resolves issue 29702.
5232 o Code simplification and refactoring (shell scripts):
5233 - Clean up many of our shell scripts to fix shellcheck warnings.
5234 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
5235 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
5236 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
5237 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
5238 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
5239 nagios-check-tor-authority-cert (ticket 29071),
5240 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
5241 (ticket 29060), test_key_expiration.sh (ticket 30002),
5242 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
5245 o Testing (chutney):
5246 - In "make test-network-all", test IPv6-only v3 single onion
5247 services, using the chutney network single-onion-v23-ipv6-md.
5248 Closes ticket 27251.
5250 o Testing (continuous integration):
5251 - In Travis, make stem log a controller trace to the console, and tail
5252 stem's tor log after failure. Closes ticket 30591.
5253 - In Travis, only run the stem tests that use a tor binary.
5254 Closes ticket 30694.
5257 Changes in version 0.4.0.5 - 2019-05-02
5258 This is the first stable release in the 0.4.0.x series. It contains
5259 improvements for power management and bootstrap reporting, as well as
5260 preliminary backend support for circuit padding to prevent some kinds
5261 of traffic analysis. It also continues our work in refactoring Tor for
5262 long-term maintainability.
5264 Per our support policy, we will support the 0.4.0.x series for nine
5265 months, or until three months after the release of a stable 0.4.1.x:
5266 whichever is longer. If you need longer-term support, please stick
5267 with 0.3.5.x, which will we plan to support until Feb 2022.
5269 Below are the changes since 0.3.5.7. For a complete list of changes
5270 since 0.4.0.4-rc, see the ChangeLog file.
5272 o Major features (battery management, client, dormant mode):
5273 - When Tor is running as a client, and it is unused for a long time,
5274 it can now enter a "dormant" state. When Tor is dormant, it avoids
5275 network and CPU activity until it is reawoken either by a user
5276 request or by a controller command. For more information, see the
5277 configuration options starting with "Dormant". Implements tickets
5279 - The client's memory of whether it is "dormant", and how long it
5280 has spent idle, persists across invocations. Implements
5282 - There is a DormantOnFirstStartup option that integrators can use
5283 if they expect that in many cases, Tor will be installed but
5286 o Major features (bootstrap reporting):
5287 - When reporting bootstrap progress, report the first connection
5288 uniformly, regardless of whether it's a connection for building
5289 application circuits. This allows finer-grained reporting of early
5290 progress than previously possible, with the improvements of ticket
5291 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
5292 - When reporting bootstrap progress, treat connecting to a proxy or
5293 pluggable transport as separate from having successfully used that
5294 proxy or pluggable transport to connect to a relay. Closes tickets
5297 o Major features (circuit padding):
5298 - Implement preliminary support for the circuit padding portion of
5299 Proposal 254. The implementation supports Adaptive Padding (aka
5300 WTF-PAD) state machines for use between experimental clients and
5301 relays. Support is also provided for APE-style state machines that
5302 use probability distributions instead of histograms to specify
5303 inter-packet delay. At the moment, Tor does not provide any
5304 padding state machines that are used in normal operation: for now,
5305 this feature exists solely for experimentation. Closes
5308 o Major features (refactoring):
5309 - Tor now uses an explicit list of its own subsystems when
5310 initializing and shutting down. Previously, these systems were
5311 managed implicitly in various places throughout the codebase.
5312 (There may still be some subsystems using the old system.) Closes
5315 o Major bugfixes (cell scheduler, KIST, security):
5316 - Make KIST consider the outbuf length when computing what it can
5317 put in the outbuf. Previously, KIST acted as though the outbuf
5318 were empty, which could lead to the outbuf becoming too full. It
5319 is possible that an attacker could exploit this bug to cause a Tor
5320 client or relay to run out of memory and crash. Fixes bug 29168;
5321 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
5322 TROVE-2019-001 and CVE-2019-8955.
5324 o Major bugfixes (networking):
5325 - Gracefully handle empty username/password fields in SOCKS5
5326 username/password auth message and allow SOCKS5 handshake to
5327 continue. Previously, we had rejected these handshakes, breaking
5328 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
5330 o Major bugfixes (NSS, relay):
5331 - When running with NSS, disable TLS 1.2 ciphersuites that use
5332 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
5333 these ciphersuites don't work -- which caused relays to fail to
5334 handshake with one another when these ciphersuites were enabled.
5335 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
5337 o Major bugfixes (windows, startup):
5338 - When reading a consensus file from disk, detect whether it was
5339 written in text mode, and re-read it in text mode if so. Always
5340 write consensus files in binary mode so that we can map them into
5341 memory later. Previously, we had written in text mode, which
5342 confused us when we tried to map the file on windows. Fixes bug
5343 28614; bugfix on 0.4.0.1-alpha.
5345 o Minor features (address selection):
5346 - Treat the subnet 100.64.0.0/10 as public for some purposes;
5347 private for others. This subnet is the RFC 6598 (Carrier Grade
5348 NAT) IP range, and is deployed by many ISPs as an alternative to
5349 RFC 1918 that does not break existing internal networks. Tor now
5350 blocks SOCKS and control ports on these addresses and warns users
5351 if client ports or ExtORPorts are listening on a RFC 6598 address.
5352 Closes ticket 28525. Patch by Neel Chauhan.
5354 o Minor features (bandwidth authority):
5355 - Make bandwidth authorities ignore relays that are reported in the
5356 bandwidth file with the flag "vote=0". This change allows us to
5357 report unmeasured relays for diagnostic reasons without including
5358 their bandwidth in the bandwidth authorities' vote. Closes
5360 - When a directory authority is using a bandwidth file to obtain the
5361 bandwidth values that will be included in the next vote, serve
5362 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
5365 o Minor features (bootstrap reporting):
5366 - When reporting bootstrap progress, stop distinguishing between
5367 situations where only internal paths are available and situations
5368 where external paths are available. Previously, Tor would often
5369 erroneously report that it had only internal paths. Closes
5372 o Minor features (compilation):
5373 - Compile correctly when OpenSSL is built with engine support
5374 disabled, or with deprecated APIs disabled. Closes ticket 29026.
5375 Patches from "Mangix".
5377 o Minor features (continuous integration):
5378 - On Travis Rust builds, cleanup Rust registry and refrain from
5379 caching the "target/" directory to speed up builds. Resolves
5381 - Log Python version during each Travis CI job. Resolves
5383 - In Travis, tell timelimit to use stem's backtrace signals, and
5384 launch python directly from timelimit, so python receives the
5385 signals from timelimit, rather than make. Closes ticket 30117.
5387 o Minor features (controller):
5388 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
5389 Implements ticket 28843.
5391 o Minor features (developer tooling):
5392 - Check that bugfix versions in changes files look like Tor versions
5393 from the versions spec. Warn when bugfixes claim to be on a future
5394 release. Closes ticket 27761.
5395 - Provide a git pre-commit hook that disallows committing if we have
5396 any failures in our code and changelog formatting checks. It is
5397 now available in scripts/maint/pre-commit.git-hook. Implements
5399 - Provide a git hook script to prevent "fixup!" and "squash!"
5400 commits from ending up in the master branch, as scripts/main/pre-
5401 push.git-hook. Closes ticket 27993.
5403 o Minor features (diagnostic):
5404 - Add more diagnostic log messages in an attempt to solve the issue
5405 of NUL bytes appearing in a microdescriptor cache. Related to
5408 o Minor features (directory authority):
5409 - When a directory authority is using a bandwidth file to obtain
5410 bandwidth values, include the digest of that file in the vote.
5411 Closes ticket 26698.
5412 - Directory authorities support a new consensus algorithm, under
5413 which the family lines in microdescriptors are encoded in a
5414 canonical form. This change makes family lines more compressible
5415 in transit, and on the client. Closes ticket 28266; implements
5418 o Minor features (directory authority, relay):
5419 - Authorities now vote on a "StaleDesc" flag to indicate that a
5420 relay's descriptor is so old that the relay should upload again
5421 soon. Relays treat this flag as a signal to upload a new
5422 descriptor. This flag will eventually let us remove the
5423 'published' date from routerstatus entries, and make our consensus
5424 diffs much smaller. Closes ticket 26770; implements proposal 293.
5426 o Minor features (dormant mode):
5427 - Add a DormantCanceledByStartup option to tell Tor that it should
5428 treat a startup event as cancelling any previous dormant state.
5429 Integrators should use this option with caution: it should only be
5430 used if Tor is being started because of something that the user
5431 did, and not if Tor is being automatically started in the
5432 background. Closes ticket 29357.
5434 o Minor features (fallback directory mirrors):
5435 - Update the fallback whitelist based on operator opt-ins and opt-
5436 outs. Closes ticket 24805, patch by Phoul.
5438 o Minor features (FreeBSD):
5439 - On FreeBSD-based systems, warn relay operators if the
5440 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
5441 Closes ticket 28518.
5443 o Minor features (geoip):
5444 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
5445 Country database. Closes ticket 29992.
5447 o Minor features (HTTP standards compliance):
5448 - Stop sending the header "Content-type: application/octet-stream"
5449 along with transparently compressed documents: this confused
5450 browsers. Closes ticket 28100.
5452 o Minor features (IPv6):
5453 - We add an option ClientAutoIPv6ORPort, to make clients randomly
5454 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
5455 every time a node is loaded from a new consensus or bridge config.
5456 We expect that this option will enable clients to bootstrap more
5457 quickly without having to determine whether they support IPv4,
5458 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
5459 - When using addrs_in_same_network_family(), avoid choosing circuit
5460 paths that pass through the same IPv6 subnet more than once.
5461 Previously, we only checked IPv4 subnets. Closes ticket 24393.
5462 Patch by Neel Chauhan.
5464 o Minor features (log messages):
5465 - Improve log message in v3 onion services that could print out
5466 negative revision counters. Closes ticket 27707. Patch
5469 o Minor features (memory usage):
5470 - Save memory by storing microdescriptor family lists with a more
5471 compact representation. Closes ticket 27359.
5472 - Tor clients now use mmap() to read consensus files from disk, so
5473 that they no longer need keep the full text of a consensus in
5474 memory when parsing it or applying a diff. Closes ticket 27244.
5476 o Minor features (NSS, diagnostic):
5477 - Try to log an error from NSS (if there is any) and a more useful
5478 description of our situation if we are using NSS and a call to
5479 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
5481 o Minor features (parsing):
5482 - Directory authorities now validate that router descriptors and
5483 ExtraInfo documents are in a valid subset of UTF-8, and reject
5484 them if they are not. Closes ticket 27367.
5486 o Minor features (performance):
5487 - Cache the results of summarize_protocol_flags(), so that we don't
5488 have to parse the same protocol-versions string over and over.
5489 This should save us a huge number of malloc calls on startup, and
5490 may reduce memory fragmentation with some allocators. Closes
5492 - Remove a needless memset() call from get_token_arguments, thereby
5493 speeding up the tokenization of directory objects by about 20%.
5494 Closes ticket 28852.
5495 - Replace parse_short_policy() with a faster implementation, to
5496 improve microdescriptor parsing time. Closes ticket 28853.
5497 - Speed up directory parsing a little by avoiding use of the non-
5498 inlined strcmp_len() function. Closes ticket 28856.
5499 - Speed up microdescriptor parsing by about 30%, to help improve
5500 startup time. Closes ticket 28839.
5502 o Minor features (pluggable transports):
5503 - Add support for emitting STATUS updates to Tor's control port from
5504 a pluggable transport process. Closes ticket 28846.
5505 - Add support for logging to Tor's logging subsystem from a
5506 pluggable transport process. Closes ticket 28180.
5508 o Minor features (process management):
5509 - Add a new process API for handling child processes. This new API
5510 allows Tor to have bi-directional communication with child
5511 processes on both Unix and Windows. Closes ticket 28179.
5512 - Use the subsystem manager to initialize and shut down the process
5513 module. Closes ticket 28847.
5515 o Minor features (relay):
5516 - When listing relay families, list them in canonical form including
5517 the relay's own identity, and try to give a more useful set of
5518 warnings. Part of ticket 28266 and proposal 298.
5520 o Minor features (required protocols):
5521 - Before exiting because of a missing required protocol, Tor will
5522 now check the publication time of the consensus, and not exit
5523 unless the consensus is newer than the Tor program's own release
5524 date. Previously, Tor would not check the consensus publication
5525 time, and so might exit because of a missing protocol that might
5526 no longer be required in a current consensus. Implements proposal
5527 297; closes ticket 27735.
5529 o Minor features (testing):
5530 - Treat all unexpected ERR and BUG messages as test failures. Closes
5532 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
5533 networks. Closes ticket 28840. Patch by Rob Jansen.
5534 - Use the approx_time() function when setting the "Expires" header
5535 in directory replies, to make them more testable. Needed for
5538 o Minor bugfixes (security):
5539 - Fix a potential double free bug when reading huge bandwidth files.
5540 The issue is not exploitable in the current Tor network because
5541 the vulnerable code is only reached when directory authorities
5542 read bandwidth files, but bandwidth files come from a trusted
5543 source (usually the authorities themselves). Furthermore, the
5544 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
5545 which are not used by any of the current authorities. Fixes bug
5546 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
5548 - Verify in more places that we are not about to create a buffer
5549 with more than INT_MAX bytes, to avoid possible OOB access in the
5550 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
5551 fixed by Tobias Stoeckmann.
5553 o Minor bugfix (continuous integration):
5554 - Reset coverage state on disk after Travis CI has finished. This
5555 should prevent future coverage merge errors from causing the test
5556 suite for the "process" subsystem to fail. The process subsystem
5557 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
5559 - Terminate test-stem if it takes more than 9.5 minutes to run.
5560 (Travis terminates the job after 10 minutes of no output.)
5561 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
5563 o Minor bugfixes (build, compatibility, rust):
5564 - Update Cargo.lock file to match the version made by the latest
5565 version of Rust, so that "make distcheck" will pass again. Fixes
5566 bug 29244; bugfix on 0.3.3.4-alpha.
5568 o Minor bugfixes (C correctness):
5569 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
5570 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
5573 o Minor bugfixes (client, clock skew):
5574 - Bootstrap successfully even when Tor's clock is behind the clocks
5575 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
5576 - Select guards even if the consensus has expired, as long as the
5577 consensus is still reasonably live. Fixes bug 24661; bugfix
5580 o Minor bugfixes (compilation):
5581 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
5582 29169; bugfix on 0.4.0.1-alpha.
5583 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
5584 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
5585 - Compile correctly on OpenBSD; previously, we were missing some
5586 headers required in order to detect it properly. Fixes bug 28938;
5587 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
5589 o Minor bugfixes (directory clients):
5590 - Mark outdated dirservers when Tor only has a reasonably live
5591 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
5593 o Minor bugfixes (directory mirrors):
5594 - Even when a directory mirror's clock is behind the clocks on the
5595 authorities, we now allow the mirror to serve "future"
5596 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
5598 o Minor bugfixes (DNS):
5599 - Gracefully handle an empty or absent resolve.conf file by falling
5600 back to using "localhost" as a DNS server (and hoping it works).
5601 Previously, we would just stop running as an exit. Fixes bug
5602 21900; bugfix on 0.2.1.10-alpha.
5604 o Minor bugfixes (documentation):
5605 - Describe the contents of the v3 onion service client authorization
5606 files correctly: They hold public keys, not private keys. Fixes
5607 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
5609 o Minor bugfixes (guards):
5610 - In count_acceptable_nodes(), the minimum number is now one bridge
5611 or guard node, and two non-guard nodes for a circuit. Previously,
5612 we had added up the sum of all nodes with a descriptor, but that
5613 could cause us to build failing circuits when we had either too
5614 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
5615 0.2.3.1-alpha. Patch by Neel Chauhan.
5617 o Minor bugfixes (IPv6):
5618 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
5619 IPv6 socket was bound using an address family of AF_INET instead
5620 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
5623 o Minor bugfixes (linux seccomp sandbox):
5624 - Fix startup crash when experimental sandbox support is enabled.
5625 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
5627 o Minor bugfixes (logging):
5628 - Correct a misleading error message when IPv4Only or IPv6Only is
5629 used but the resolved address can not be interpreted as an address
5630 of the specified IP version. Fixes bug 13221; bugfix on
5631 0.2.3.9-alpha. Patch from Kris Katterjohn.
5632 - Log the correct port number for listening sockets when "auto" is
5633 used to let Tor pick the port number. Previously, port 0 was
5634 logged instead of the actual port number. Fixes bug 29144; bugfix
5635 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
5636 - Stop logging a BUG() warning when Tor is waiting for exit
5637 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
5638 - Avoid logging that we are relaxing a circuit timeout when that
5639 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
5640 - Log more information at "warning" level when unable to read a
5641 private key; log more information at "info" level when unable to
5642 read a public key. We had warnings here before, but they were lost
5643 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
5644 - Rework rep_hist_log_link_protocol_counts() to iterate through all
5645 link protocol versions when logging incoming/outgoing connection
5646 counts. Tor no longer skips version 5, and we won't have to
5647 remember to update this function when new link protocol version is
5648 developed. Fixes bug 28920; bugfix on 0.2.6.10.
5650 o Minor bugfixes (memory management):
5651 - Refactor the shared random state's memory management so that it
5652 actually takes ownership of the shared random value pointers.
5653 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
5654 - Stop leaking parts of the shared random state in the shared-random
5655 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
5657 o Minor bugfixes (misc):
5658 - The amount of total available physical memory is now determined
5659 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
5660 when it is defined and a 64-bit variant is not available. Fixes
5661 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
5663 o Minor bugfixes (networking):
5664 - Introduce additional checks into tor_addr_parse() to reject
5665 certain incorrect inputs that previously were not detected. Fixes
5666 bug 23082; bugfix on 0.2.0.10-alpha.
5668 o Minor bugfixes (onion service v3, client):
5669 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
5670 connection waiting for a descriptor that we actually have in the
5671 cache. It turns out that this can actually happen, though it is
5672 rare. Now, tor will recover and retry the descriptor. Fixes bug
5673 28669; bugfix on 0.3.2.4-alpha.
5675 o Minor bugfixes (onion services):
5676 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
5677 than one private key for a hidden service. Fixes bug 29040; bugfix
5679 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
5680 "debug" level. Tor used to log it as a warning, which caused very
5681 long log lines to appear for some users. Fixes bug 29135; bugfix
5683 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
5684 as a warning. Instead, log it as a protocol warning, because there
5685 is nothing that relay operators can do to fix it. Fixes bug 29029;
5686 bugfix on 0.2.5.7-rc.
5688 o Minor bugfixes (periodic events):
5689 - Refrain from calling routerlist_remove_old_routers() from
5690 check_descriptor_callback(). Instead, create a new hourly periodic
5691 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
5693 o Minor bugfixes (pluggable transports):
5694 - Make sure that data is continously read from standard output and
5695 standard error pipes of a pluggable transport child-process, to
5696 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
5697 bugfix on 0.2.3.6-alpha.
5699 o Minor bugfixes (rust):
5700 - Abort on panic in all build profiles, instead of potentially
5701 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
5703 o Minor bugfixes (scheduler):
5704 - When re-adding channels to the pending list, check the correct
5705 channel's sched_heap_idx. This issue has had no effect in mainline
5706 Tor, but could have led to bugs down the road in improved versions
5707 of our circuit scheduling code. Fixes bug 29508; bugfix
5710 o Minor bugfixes (shellcheck):
5711 - Look for scripts in their correct locations during "make
5712 shellcheck". Previously we had looked in the wrong place during
5713 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
5715 o Minor bugfixes (single onion services):
5716 - Allow connections to single onion services to remain idle without
5717 being disconnected. Previously, relays acting as rendezvous points
5718 for single onion services were mistakenly closing idle rendezvous
5719 circuits after 60 seconds, thinking that they were unused
5720 directory-fetching circuits that had served their purpose. Fixes
5721 bug 29665; bugfix on 0.2.1.26.
5723 o Minor bugfixes (stats):
5724 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
5725 relay and bridge extra-info documents. Fixes bug 29017; bugfix
5728 o Minor bugfixes (testing):
5729 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
5730 recent test-network.sh to use new chutney features in CI. Fixes
5731 bug 29703; bugfix on 0.2.9.1-alpha.
5732 - Fix a test failure on Windows caused by an unexpected "BUG"
5733 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
5735 - Downgrade some LOG_ERR messages in the address/* tests to
5736 warnings. The LOG_ERR messages were occurring when we had no
5737 configured network. We were failing the unit tests, because we
5738 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
5739 29530; bugfix on 0.3.5.8.
5740 - Fix our gcov wrapper script to look for object files at the
5741 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
5742 - Decrease the false positive rate of stochastic probability
5743 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
5744 - Fix intermittent failures on an adaptive padding test. Fixes one
5745 case of bug 29122; bugfix on 0.4.0.1-alpha.
5746 - Disable an unstable circuit-padding test that was failing
5747 intermittently because of an ill-defined small histogram. Such
5748 histograms will be allowed again after 29298 is implemented. Fixes
5749 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
5750 - Detect and suppress "bug" warnings from the util/time test on
5751 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
5752 - Do not log an error-level message if we fail to find an IPv6
5753 network interface from the unit tests. Fixes bug 29160; bugfix
5755 - Instead of relying on hs_free_all() to clean up all onion service
5756 objects in test_build_descriptors(), we now deallocate them one by
5757 one. This lets Coverity know that we are not leaking memory there
5758 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
5759 - Check the time in the "Expires" header using approx_time(). Fixes
5760 bug 30001; bugfix on 0.4.0.4-rc.
5762 o Minor bugfixes (TLS protocol):
5763 - When classifying a client's selection of TLS ciphers, if the
5764 client ciphers are not yet available, do not cache the result.
5765 Previously, we had cached the unavailability of the cipher list
5766 and never looked again, which in turn led us to assume that the
5767 client only supported the ancient V1 link protocol. This, in turn,
5768 was causing Stem integration tests to stall in some cases. Fixes
5769 bug 30021; bugfix on 0.2.4.8-alpha.
5771 o Minor bugfixes (UI):
5772 - Lower log level of unlink() errors during bootstrap. Fixes bug
5773 29930; bugfix on 0.4.0.1-alpha.
5775 o Minor bugfixes (usability):
5776 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
5777 Some users took this phrasing to mean that the mentioned guard was
5778 under their control or responsibility, which it is not. Fixes bug
5779 28895; bugfix on Tor 0.3.0.1-alpha.
5781 o Minor bugfixes (Windows, CI):
5782 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
5783 Windows Server 2012 R2 job. The remaining 2 jobs still provide
5784 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
5785 fast_finish, so failed jobs terminate the build immediately. Fixes
5786 bug 29601; bugfix on 0.3.5.4-alpha.
5788 o Code simplification and refactoring:
5789 - Introduce a connection_dir_buf_add() helper function that detects
5790 whether compression is in use, and adds a string accordingly.
5791 Resolves issue 28816.
5792 - Refactor handle_get_next_bandwidth() to use
5793 connection_dir_buf_add(). Implements ticket 29897.
5794 - Reimplement NETINFO cell parsing and generation to rely on
5795 trunnel-generated wire format handling code. Closes ticket 27325.
5796 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
5798 - Rework SOCKS wire format handling to rely on trunnel-generated
5799 parsing/generation code. Resolves ticket 27620.
5800 - Split out bootstrap progress reporting from control.c into a
5801 separate file. Part of ticket 27402.
5802 - The .may_include files that we use to describe our directory-by-
5803 directory dependency structure now describe a noncircular
5804 dependency graph over the directories that they cover. Our
5805 checkIncludes.py tool now enforces this noncircularity. Closes
5809 - Clarify that Tor performs stream isolation among *Port listeners
5810 by default. Resolves issue 29121.
5811 - In the manpage entry describing MapAddress torrc setting, use
5812 example IP addresses from ranges specified for use in documentation
5813 by RFC 5737. Resolves issue 28623.
5814 - Mention that you cannot add a new onion service if Tor is already
5815 running with Sandbox enabled. Closes ticket 28560.
5816 - Improve ControlPort documentation. Mention that it accepts
5817 address:port pairs, and can be used multiple times. Closes
5819 - Document the exact output of "tor --version". Closes ticket 28889.
5822 - Remove the old check-tor script. Resolves issue 29072.
5823 - Stop responding to the 'GETINFO status/version/num-concurring' and
5824 'GETINFO status/version/num-versioning' control port commands, as
5825 those were deprecated back in 0.2.0.30. Also stop listing them in
5826 output of 'GETINFO info/names'. Resolves ticket 28757.
5827 - The scripts used to generate and maintain the list of fallback
5828 directories have been extracted into a new "fallback-scripts"
5829 repository. Closes ticket 27914.
5832 - Run shellcheck for scripts in the in scripts/ directory. Closes
5834 - Add unit tests for tokenize_string() and get_next_token()
5835 functions. Resolves ticket 27625.
5837 o Code simplification and refactoring (onion service v3):
5838 - Consolidate the authorized client descriptor cookie computation
5839 code from client and service into one function. Closes
5842 o Code simplification and refactoring (shell scripts):
5843 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
5845 - Fix issues that shellcheck found in chutney-git-bisect.sh.
5846 Resolves ticket 28006.
5847 - Fix issues that shellcheck found in updateRustDependencies.sh.
5848 Resolves ticket 28012.
5849 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
5850 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
5851 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
5852 - Fix shellcheck warnings in scripts/test/coverage. Resolves
5856 Changes in version 0.3.5.8 - 2019-02-21
5857 Tor 0.3.5.8 backports several fixes from later releases, including fixes
5858 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
5861 It also includes a fix for a medium-severity security bug affecting Tor
5862 0.3.2.1-alpha and later. All Tor instances running an affected release
5863 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
5865 o Major bugfixes (cell scheduler, KIST, security):
5866 - Make KIST consider the outbuf length when computing what it can
5867 put in the outbuf. Previously, KIST acted as though the outbuf
5868 were empty, which could lead to the outbuf becoming too full. It
5869 is possible that an attacker could exploit this bug to cause a Tor
5870 client or relay to run out of memory and crash. Fixes bug 29168;
5871 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
5872 TROVE-2019-001 and CVE-2019-8955.
5874 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
5875 - Gracefully handle empty username/password fields in SOCKS5
5876 username/password auth messsage and allow SOCKS5 handshake to
5877 continue. Previously, we had rejected these handshakes, breaking
5878 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
5880 o Minor features (compilation, backport from 0.4.0.2-alpha):
5881 - Compile correctly when OpenSSL is built with engine support
5882 disabled, or with deprecated APIs disabled. Closes ticket 29026.
5883 Patches from "Mangix".
5885 o Minor features (geoip):
5886 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
5887 Country database. Closes ticket 29478.
5889 o Minor features (testing, backport from 0.4.0.2-alpha):
5890 - Treat all unexpected ERR and BUG messages as test failures. Closes
5893 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
5894 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
5895 connection waiting for a descriptor that we actually have in the
5896 cache. It turns out that this can actually happen, though it is
5897 rare. Now, tor will recover and retry the descriptor. Fixes bug
5898 28669; bugfix on 0.3.2.4-alpha.
5900 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
5901 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
5902 IPv6 socket was bound using an address family of AF_INET instead
5903 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
5906 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
5907 - Update Cargo.lock file to match the version made by the latest
5908 version of Rust, so that "make distcheck" will pass again. Fixes
5909 bug 29244; bugfix on 0.3.3.4-alpha.
5911 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
5912 - Select guards even if the consensus has expired, as long as the
5913 consensus is still reasonably live. Fixes bug 24661; bugfix
5916 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
5917 - Compile correctly on OpenBSD; previously, we were missing some
5918 headers required in order to detect it properly. Fixes bug 28938;
5919 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
5921 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
5922 - Describe the contents of the v3 onion service client authorization
5923 files correctly: They hold public keys, not private keys. Fixes
5924 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
5926 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
5927 - Rework rep_hist_log_link_protocol_counts() to iterate through all
5928 link protocol versions when logging incoming/outgoing connection
5929 counts. Tor no longer skips version 5, and we won't have to
5930 remember to update this function when new link protocol version is
5931 developed. Fixes bug 28920; bugfix on 0.2.6.10.
5933 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
5934 - Log more information at "warning" level when unable to read a
5935 private key; log more information at "info" level when unable to
5936 read a public key. We had warnings here before, but they were lost
5937 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
5939 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
5940 - The amount of total available physical memory is now determined
5941 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
5942 when it is defined and a 64-bit variant is not available. Fixes
5943 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
5945 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
5946 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
5947 than one private key for a hidden service. Fixes bug 29040; bugfix
5949 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
5950 "debug" level. Tor used to log it as a warning, which caused very
5951 long log lines to appear for some users. Fixes bug 29135; bugfix
5953 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
5954 as a warning. Instead, log it as a protocol warning, because there
5955 is nothing that relay operators can do to fix it. Fixes bug 29029;
5956 bugfix on 0.2.5.7-rc.
5958 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
5959 - Mark outdated dirservers when Tor only has a reasonably live
5960 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
5962 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
5963 - Detect and suppress "bug" warnings from the util/time test on
5964 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
5965 - Do not log an error-level message if we fail to find an IPv6
5966 network interface from the unit tests. Fixes bug 29160; bugfix
5969 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
5970 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
5971 Some users took this phrasing to mean that the mentioned guard was
5972 under their control or responsibility, which it is not. Fixes bug
5973 28895; bugfix on Tor 0.3.0.1-alpha.
5976 Changes in version 0.3.4.11 - 2019-02-21
5977 Tor 0.3.4.11 is the third stable release in its series. It includes
5978 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
5979 later. All Tor instances running an affected release should upgrade to
5980 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
5982 o Major bugfixes (cell scheduler, KIST, security):
5983 - Make KIST consider the outbuf length when computing what it can
5984 put in the outbuf. Previously, KIST acted as though the outbuf
5985 were empty, which could lead to the outbuf becoming too full. It
5986 is possible that an attacker could exploit this bug to cause a Tor
5987 client or relay to run out of memory and crash. Fixes bug 29168;
5988 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
5989 TROVE-2019-001 and CVE-2019-8955.
5991 o Minor features (geoip):
5992 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
5993 Country database. Closes ticket 29478.
5995 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
5996 - Update Cargo.lock file to match the version made by the latest
5997 version of Rust, so that "make distcheck" will pass again. Fixes
5998 bug 29244; bugfix on 0.3.3.4-alpha.
6000 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
6001 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
6002 as a warning. Instead, log it as a protocol warning, because there
6003 is nothing that relay operators can do to fix it. Fixes bug 29029;
6004 bugfix on 0.2.5.7-rc.
6007 Changes in version 0.3.3.12 - 2019-02-21
6008 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
6009 0.3.2.1-alpha and later. All Tor instances running an affected release
6010 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
6012 This release marks the end of support for the Tor 0.3.3.x series. We
6013 recommend that users switch to either the Tor 0.3.4 series (supported
6014 until at least 10 June 2019), or the Tor 0.3.5 series, which will
6015 receive long-term support until at least 1 Feb 2022.
6017 o Major bugfixes (cell scheduler, KIST, security):
6018 - Make KIST consider the outbuf length when computing what it can
6019 put in the outbuf. Previously, KIST acted as though the outbuf
6020 were empty, which could lead to the outbuf becoming too full. It
6021 is possible that an attacker could exploit this bug to cause a Tor
6022 client or relay to run out of memory and crash. Fixes bug 29168;
6023 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
6024 TROVE-2019-001 and CVE-2019-8955.
6026 o Minor features (geoip):
6027 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
6028 Country database. Closes ticket 29478.
6030 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
6031 - Update Cargo.lock file to match the version made by the latest
6032 version of Rust, so that "make distcheck" will pass again. Fixes
6033 bug 29244; bugfix on 0.3.3.4-alpha.
6035 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
6036 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
6037 as a warning. Instead, log it as a protocol warning, because there
6038 is nothing that relay operators can do to fix it. Fixes bug 29029;
6039 bugfix on 0.2.5.7-rc.
6042 Changes in version 0.3.3.11 - 2019-01-07
6043 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
6044 numerous fixes, including an important fix for anyone using OpenSSL
6045 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
6046 to this version, or to a later series.
6048 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
6049 We anticipate that this will be the last release of Tor 0.3.3, unless
6050 some major bug is before then. Some time between now and then, users
6051 should switch to either the Tor 0.3.4 series (supported until at least
6052 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
6053 support until at least 1 Feb 2022.
6055 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
6056 - Fix our usage of named groups when running as a TLS 1.3 client in
6057 OpenSSL 1.1.1. Previously, we only initialized EC groups when
6058 running as a relay, which caused clients to fail to negotiate TLS
6059 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
6062 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
6063 - Fix a use-after-free error that could be caused by passing Tor an
6064 impossible set of options that would fail during options_act().
6065 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
6067 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
6068 - Only run one online rust build in Travis, to reduce network
6069 errors. Skip offline rust builds on Travis for Linux gcc, because
6070 they're redundant. Implements ticket 27252.
6071 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
6072 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
6073 Linux with default settings, because all the non-default builds
6074 use gcc on Linux. Implements ticket 27252.
6076 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
6077 - Use the Travis Homebrew addon to install packages on macOS during
6078 Travis CI. The package list is the same, but the Homebrew addon
6079 does not do a `brew update` by default. Implements ticket 27738.
6081 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
6082 - Replace the 150 fallbacks originally introduced in Tor
6083 0.3.3.1-alpha in January 2018 (of which ~115 were still
6084 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
6085 removed) generated in December 2018. Closes ticket 24803.
6087 o Minor features (geoip):
6088 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
6089 Country database. Closes ticket 29012.
6091 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
6092 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
6093 key export function from handling long labels. When this bug is
6094 detected, Tor will disable TLS 1.3. We recommend upgrading to a
6095 version of OpenSSL without this bug when it becomes available.
6096 Closes ticket 28973.
6098 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
6099 - Update relay descriptor on bandwidth changes only when the uptime
6100 is smaller than 24h, in order to reduce the efficiency of guard
6101 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
6103 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
6104 - Avoid undefined behavior in an end-of-string check when parsing
6105 the BEGIN line in a directory object. Fixes bug 28202; bugfix
6108 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
6109 - Rewrite our assertion macros so that they no longer suppress the
6110 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
6112 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
6113 - Initialize a variable unconditionally in aes_new_cipher(), since
6114 some compilers cannot tell that we always initialize it before
6115 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
6117 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
6118 - Log additional info when we get a relay that shares an ed25519 ID
6119 with a different relay, instead making a BUG() warning. Fixes bug
6120 27800; bugfix on 0.3.2.1-alpha.
6122 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
6123 - When a user requests a group-readable DataDirectory, give it to
6124 them. Previously, when the DataDirectory and the CacheDirectory
6125 were the same, the default setting (0) for
6126 CacheDirectoryGroupReadable would override the setting for
6127 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
6130 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
6131 - When the onion service directory can't be created or has the wrong
6132 permissions, do not log a stack trace. Fixes bug 27335; bugfix
6135 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
6136 - Close all SOCKS request (for the same .onion) if the newly fetched
6137 descriptor is unusable. Before that, we would close only the first
6138 one leaving the other hanging and let to time out by themselves.
6139 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
6141 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
6142 - Don't warn so loudly when Tor is unable to decode an onion
6143 descriptor. This can now happen as a normal use case if a client
6144 gets a descriptor with client authorization but the client is not
6145 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
6147 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
6148 - When deleting an ephemeral onion service (DEL_ONION), do not close
6149 any rendezvous circuits in order to let the existing client
6150 connections finish by themselves or closed by the application. The
6151 HS v2 is doing that already so now we have the same behavior for
6152 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
6154 o Minor bugfixes (HTTP tunnel):
6155 - Fix a bug warning when closing an HTTP tunnel connection due to
6156 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
6159 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
6160 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
6161 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
6163 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
6164 - Ensure circuitmux queues are empty before scheduling or sending
6165 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
6167 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
6168 - Reject protocol names containing bytes other than alphanumeric
6169 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
6172 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
6173 - Compute protover votes correctly in the rust version of the
6174 protover code. Previously, the protover rewrite in 24031 allowed
6175 repeated votes from the same voter for the same protocol version
6176 to be counted multiple times in protover_compute_vote(). Fixes bug
6177 27649; bugfix on 0.3.3.5-rc.
6178 - Reject protover names that contain invalid characters. Fixes bug
6179 27687; bugfix on 0.3.3.1-alpha.
6181 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
6182 - protover_all_supported() would attempt to allocate up to 16GB on
6183 some inputs, leading to a potential memory DoS. Fixes bug 27206;
6184 bugfix on 0.3.3.5-rc.
6186 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
6187 - Fix a potential null dereference in protover_all_supported(). Add
6188 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
6189 - Return a string that can be safely freed by C code, not one
6190 created by the rust allocator, in protover_all_supported(). Fixes
6191 bug 27740; bugfix on 0.3.3.1-alpha.
6192 - Fix an API mismatch in the rust implementation of
6193 protover_compute_vote(). This bug could have caused crashes on any
6194 directory authorities running Tor with Rust (which we do not yet
6195 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
6197 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
6198 - If a unit test running in a subprocess exits abnormally or with a
6199 nonzero status code, treat the test as having failed, even if the
6200 test reported success. Without this fix, memory leaks don't cause
6201 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
6202 bugfix on 0.2.2.4-alpha.
6204 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
6205 - Treat backtrace test failures as expected on BSD-derived systems
6206 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
6207 (FreeBSD failures have been treated as expected since 18204 in
6208 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
6210 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
6211 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
6212 bugfix on 0.3.0.1-alpha.
6215 Changes in version 0.3.4.10 - 2019-01-07
6216 Tor 0.3.4.9 is the second stable release in its series; it backports
6217 numerous fixes, including an important fix for relays, and for anyone
6218 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
6221 As a reminder, the Tor 0.3.4 series will be supported until 10 June
6222 2019. Some time between now and then, users should switch to the Tor
6223 0.3.5 series, which will receive long-term support until at least 1
6226 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
6227 - Fix our usage of named groups when running as a TLS 1.3 client in
6228 OpenSSL 1.1.1. Previously, we only initialized EC groups when
6229 running as a relay, which caused clients to fail to negotiate TLS
6230 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
6233 o Major bugfixes (relay, directory, backport from 0.3.5.7):
6234 - Always reactivate linked connections in the main loop so long as
6235 any linked connection has been active. Previously, connections
6236 serving directory information wouldn't get reactivated after the
6237 first chunk of data was sent (usually 32KB), which would prevent
6238 clients from bootstrapping. Fixes bug 28912; bugfix on
6239 0.3.4.1-alpha. Patch by "cypherpunks3".
6241 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
6242 - Always show the configure and test logs, and upload them as build
6243 artifacts, when building for Windows using Appveyor CI.
6246 o Minor features (controller, backport from 0.3.5.1-alpha):
6247 - For purposes of CIRC_BW-based dropped cell detection, track half-
6248 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
6249 bias check cells to arrive without counting it as dropped until
6250 either the END arrives, or the windows are empty. Closes
6253 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
6254 - Replace the 150 fallbacks originally introduced in Tor
6255 0.3.3.1-alpha in January 2018 (of which ~115 were still
6256 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
6257 removed) generated in December 2018. Closes ticket 24803.
6259 o Minor features (geoip):
6260 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
6261 Country database. Closes ticket 28395.
6263 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
6264 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
6265 key export function from handling long labels. When this bug is
6266 detected, Tor will disable TLS 1.3. We recommend upgrading to a
6267 version of OpenSSL without this bug when it becomes available.
6268 Closes ticket 28973.
6270 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
6271 - Initialize a variable unconditionally in aes_new_cipher(), since
6272 some compilers cannot tell that we always initialize it before
6273 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
6275 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
6276 - Avoid a logging a BUG() stacktrace when closing connection held
6277 open because the write side is rate limited but not the read side.
6278 Now, the connection read side is simply shut down until Tor is
6279 able to flush the connection and close it. Fixes bug 27750; bugfix
6282 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
6283 - Manually configure the zstd compiler options, when building using
6284 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
6285 not come with a pkg-config file. Fixes bug 28454; bugfix
6287 - Stop using an external OpenSSL install, and stop installing MSYS2
6288 packages, when building using mingw on Appveyor Windows CI. Fixes
6289 bug 28399; bugfix on 0.3.4.1-alpha.
6291 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
6292 - Explicitly specify the path to the OpenSSL library and do not
6293 download OpenSSL from Pacman, but instead use the library that is
6294 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
6296 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
6297 - When a user requests a group-readable DataDirectory, give it to
6298 them. Previously, when the DataDirectory and the CacheDirectory
6299 were the same, the default setting (0) for
6300 CacheDirectoryGroupReadable would override the setting for
6301 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
6304 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
6305 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
6306 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
6308 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
6309 - Don't warn so loudly when Tor is unable to decode an onion
6310 descriptor. This can now happen as a normal use case if a client
6311 gets a descriptor with client authorization but the client is not
6312 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
6314 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
6315 - When deleting an ephemeral onion service (DEL_ONION), do not close
6316 any rendezvous circuits in order to let the existing client
6317 connections finish by themselves or closed by the application. The
6318 HS v2 is doing that already so now we have the same behavior for
6319 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
6321 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
6322 - Update relay descriptor on bandwidth changes only when the uptime
6323 is smaller than 24h, in order to reduce the efficiency of guard
6324 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
6326 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
6327 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
6328 bugfix on 0.3.0.1-alpha.
6331 Changes in version 0.3.5.7 - 2019-01-07
6332 Tor 0.3.5.7 is the first stable release in its series; it includes
6333 compilation and portability fixes, and a fix for a severe problem
6334 affecting directory caches.
6336 The Tor 0.3.5 series includes several new features and performance
6337 improvements, including client authorization for v3 onion services,
6338 cleanups to bootstrap reporting, support for improved bandwidth-
6339 measurement tools, experimental support for NSS in place of OpenSSL,
6340 and much more. It also begins a full reorganization of Tor's code
6341 layout, for improved modularity and maintainability in the future.
6342 Finally, there is the usual set of performance improvements and
6343 bugfixes that we try to do in every release series.
6345 There are a couple of changes in the 0.3.5 that may affect
6346 compatibility. First, the default version for newly created onion
6347 services is now v3. Use the HiddenServiceVersion option if you want to
6348 override this. Second, some log messages related to bootstrapping have
6349 changed; if you use stem, you may need to update to the latest version
6350 so it will recognize them.
6352 We have designated 0.3.5 as a "long-term support" (LTS) series: we
6353 will continue to patch major bugs in typical configurations of 0.3.5
6354 until at least 1 Feb 2022. (We do not plan to provide long-term
6355 support for embedding, Rust support, NSS support, running a directory
6356 authority, or unsupported platforms. For these, you will need to stick
6357 with the latest stable release.)
6359 Below are the changes since 0.3.4.9. For a complete list of changes
6360 since 0.3.5.6-rc, see the ChangeLog file.
6362 o Major features (bootstrap):
6363 - Don't report directory progress until after a connection to a
6364 relay or bridge has succeeded. Previously, we'd report 80%
6365 progress based on cached directory information when we couldn't
6366 even connect to the network. Closes ticket 27169.
6368 o Major features (new code layout):
6369 - Nearly all of Tor's source code has been moved around into more
6370 logical places. The "common" directory is now divided into a set
6371 of libraries in "lib", and files in the "or" directory have been
6372 split into "core" (logic absolutely needed for onion routing),
6373 "feature" (independent modules in Tor), and "app" (to configure
6374 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
6375 more information. Closes ticket 26481.
6377 This refactoring is not complete: although the libraries have been
6378 refactored to be acyclic, the main body of Tor is still too
6379 interconnected. We will attempt to improve this in the future.
6381 o Major features (onion services v3):
6382 - Implement onion service client authorization at the descriptor
6383 level: only authorized clients can decrypt a service's descriptor
6384 to find out how to contact it. A new torrc option was added to
6385 control this client side: ClientOnionAuthDir <path>. On the
6386 service side, if the "authorized_clients/" directory exists in the
6387 onion service directory path, client configurations are read from
6388 the files within. See the manpage for more details. Closes ticket
6389 27547. Patch done by Suphanat Chunhapanya (haxxpop).
6390 - Improve revision counter generation in next-gen onion services.
6391 Onion services can now scale by hosting multiple instances on
6392 different hosts without synchronization between them, which was
6393 previously impossible because descriptors would get rejected by
6394 HSDirs. Addresses ticket 25552.
6395 - Version 3 onion services can now use the per-service
6396 HiddenServiceExportCircuitID option to differentiate client
6397 circuits. It communicates with the service by using the HAProxy
6398 protocol to assign virtual IP addresses to inbound client
6399 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
6401 o Major features (onion services, UI change):
6402 - For a newly created onion service, the default version is now 3.
6403 Tor still supports existing version 2 services, but the operator
6404 now needs to set "HiddenServiceVersion 2" in order to create a new
6405 version 2 service. For existing services, Tor now learns the
6406 version by reading the key file. Closes ticket 27215.
6408 o Major features (portability, cryptography, experimental, TLS):
6409 - Tor now has the option to compile with the NSS library instead of
6410 OpenSSL. This feature is experimental, and we expect that bugs may
6411 remain. It is mainly intended for environments where Tor's
6412 performance is not CPU-bound, and where NSS is already known to be
6413 installed. To try it out, configure Tor with the --enable-nss
6414 flag. Closes tickets 26631, 26815, and 26816.
6416 If you are experimenting with this option and using an old cached
6417 consensus, Tor may fail to start. To solve this, delete your
6418 "cached-consensus" and "cached-microdesc-consensus" files,
6419 (if present), and restart Tor.
6421 o Major features (relay, UI change):
6422 - Relays no longer run as exits by default. If the "ExitRelay"
6423 option is auto (or unset), and no exit policy is specified with
6424 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
6425 Previously in this case, we allowed exit traffic and logged a
6426 warning message. Closes ticket 21530. Patch by Neel Chauhan.
6427 - Tor now validates that the ContactInfo config option is valid UTF-
6428 8 when parsing torrc. Closes ticket 27428.
6430 o Major bugfixes (compilation):
6431 - Fix compilation on ARM (and other less-used CPUs) when compiling
6432 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
6434 o Major bugfixes (compilation, rust):
6435 - Rust tests can now build and run successfully with the
6436 --enable-fragile-hardening option enabled. Doing this currently
6437 requires the rust beta channel; it will be possible with stable
6438 rust once Rust version 1.31 is released. Patch from Alex Crichton.
6439 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
6441 o Major bugfixes (directory authority):
6442 - Actually check that the address we get from DirAuthority
6443 configuration line is valid IPv4. Explicitly disallow DirAuthority
6444 address to be a DNS hostname. Fixes bug 26488; bugfix
6447 o Major bugfixes (embedding, main loop):
6448 - When DisableNetwork becomes set, actually disable periodic events
6449 that are already enabled. (Previously, we would refrain from
6450 enabling new ones, but we would leave the old ones turned on.)
6451 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
6453 o Major bugfixes (main loop, bootstrap):
6454 - Make sure Tor bootstraps and works properly if only the
6455 ControlPort is set. Prior to this fix, Tor would only bootstrap
6456 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
6457 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
6459 o Major bugfixes (onion service v3):
6460 - On an intro point for a version 3 onion service, stop closing
6461 introduction circuits on a NACK. This lets the client decide
6462 whether to reuse the circuit or discard it. Previously, we closed
6463 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
6464 0.3.2.1-alpha. Patch by Neel Chaunan.
6466 o Major bugfixes (OpenSSL, portability):
6467 - Fix our usage of named groups when running as a TLS 1.3 client in
6468 OpenSSL 1.1.1. Previously, we only initialized EC groups when
6469 running as a relay, which caused clients to fail to negotiate TLS
6470 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
6473 o Major bugfixes (relay bandwidth statistics):
6474 - When we close relayed circuits, report the data in the circuit
6475 queues as being written in our relay bandwidth stats. This
6476 mitigates guard discovery and other attacks that close circuits
6477 for the explicit purpose of noticing this discrepancy in
6478 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
6480 o Major bugfixes (relay):
6481 - When our write bandwidth limit is exhausted, stop writing on the
6482 connection. Previously, we had a typo in the code that would make
6483 us stop reading instead, leading to relay connections being stuck
6484 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
6486 - Always reactivate linked connections in the main loop so long as
6487 any linked connection has been active. Previously, connections
6488 serving directory information wouldn't get reactivated after the
6489 first chunk of data was sent (usually 32KB), which would prevent
6490 clients from bootstrapping. Fixes bug 28912; bugfix on
6491 0.3.4.1-alpha. Patch by "cypherpunks3".
6493 o Major bugfixes (restart-in-process):
6494 - Fix a use-after-free error that could be caused by passing Tor an
6495 impossible set of options that would fail during options_act().
6496 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
6498 o Minor features (admin tools):
6499 - Add a new --key-expiration option to print the expiration date of
6500 the signing cert in an ed25519_signing_cert file. Resolves
6503 o Minor features (build):
6504 - If you pass the "--enable-pic" option to configure, Tor will try
6505 to tell the compiler to build position-independent code suitable
6506 to link into a dynamic library. (The default remains -fPIE, for
6507 code suitable for a relocatable executable.) Closes ticket 23846.
6509 o Minor features (code correctness, testing):
6510 - Tor's build process now includes a "check-includes" make target to
6511 verify that no module of Tor relies on any headers from a higher-
6512 level module. We hope to use this feature over time to help
6513 refactor our codebase. Closes ticket 26447.
6515 o Minor features (code layout):
6516 - We have a new "lowest-level" error-handling API for use by code
6517 invoked from within the logging module. With this interface, the
6518 logging code is no longer at risk of calling into itself if a
6519 failure occurs while it is trying to log something. Closes
6522 o Minor features (compilation):
6523 - When possible, place our warning flags in a separate file, to
6524 avoid flooding verbose build logs. Closes ticket 28924.
6525 - Tor's configure script now supports a --with-malloc= option to
6526 select your malloc implementation. Supported options are
6527 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
6528 default). Addresses part of ticket 20424. Based on a patch from
6531 o Minor features (config):
6532 - The "auto" keyword in torrc is now case-insensitive. Closes
6535 o Minor features (continuous integration):
6536 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
6538 - Add new CI job to Travis configuration to run stem-based
6539 integration tests. Closes ticket 27913.
6540 - Use the Travis Homebrew addon to install packages on macOS during
6541 Travis CI. The package list is the same, but the Homebrew addon
6542 does not do a `brew update` by default. Implements ticket 27738.
6543 - Report what program produced the mysterious core file that we
6544 occasionally see on Travis CI during make distcheck. Closes
6546 - Don't do a distcheck with --disable-module-dirauth in Travis.
6547 Implements ticket 27252.
6548 - Install libcap-dev and libseccomp2-dev so these optional
6549 dependencies get tested on Travis CI. Closes ticket 26560.
6550 - Only run one online rust build in Travis, to reduce network
6551 errors. Skip offline rust builds on Travis for Linux gcc, because
6552 they're redundant. Implements ticket 27252.
6553 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
6554 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
6555 Linux with default settings, because all the non-default builds
6556 use gcc on Linux. Implements ticket 27252.
6558 o Minor features (continuous integration, Windows):
6559 - Always show the configure and test logs, and upload them as build
6560 artifacts, when building for Windows using Appveyor CI.
6562 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
6563 Appveyor's CI. Closes ticket 28318.
6565 o Minor features (controller):
6566 - Emit CIRC_BW events as soon as we detect that we processed an
6567 invalid or otherwise dropped cell on a circuit. This allows
6568 vanguards and other controllers to react more quickly to dropped
6569 cells. Closes ticket 27678.
6570 - For purposes of CIRC_BW-based dropped cell detection, track half-
6571 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
6572 bias check cells to arrive without counting it as dropped until
6573 either the END arrives, or the windows are empty. Closes
6575 - Implement a 'GETINFO md/all' controller command to enable getting
6576 all known microdescriptors. Closes ticket 8323.
6577 - The GETINFO command now support an "uptime" argument, to return
6578 Tor's uptime in seconds. Closes ticket 25132.
6580 o Minor features (denial-of-service avoidance):
6581 - Make our OOM handler aware of the DNS cache so that it doesn't
6582 fill up the memory. This check is important for our DoS mitigation
6583 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
6585 o Minor features (development):
6586 - Tor's makefile now supports running the "clippy" Rust style tool
6587 on our Rust code. Closes ticket 22156.
6589 o Minor features (directory authority):
6590 - There is no longer an artificial upper limit on the length of
6591 bandwidth lines. Closes ticket 26223.
6592 - When a bandwidth file is used to obtain the bandwidth measurements,
6593 include this bandwidth file headers in the votes. Closes
6595 - Improved support for networks with only a single authority or a
6596 single fallback directory. Patch from Gabriel Somlo. Closes
6599 o Minor features (embedding API):
6600 - The Tor controller API now supports a function to launch Tor with
6601 a preconstructed owning controller FD, so that embedding
6602 applications don't need to manage controller ports and
6603 authentication. Closes ticket 24204.
6604 - The Tor controller API now has a function that returns the name
6605 and version of the backend implementing the API. Closes
6608 o Minor features (fallback directory list):
6609 - Replace the 150 fallbacks originally introduced in Tor
6610 0.3.3.1-alpha in January 2018 (of which ~115 were still
6611 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
6612 removed) generated in December 2018. Closes ticket 24803.
6614 o Minor features (geoip):
6615 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
6616 Country database. Closes ticket 29012.
6618 o Minor features (memory management):
6619 - Get Libevent to use the same memory allocator as Tor, by calling
6620 event_set_mem_functions() during initialization. Resolves
6623 o Minor features (memory usage):
6624 - When not using them, store legacy TAP public onion keys in DER-
6625 encoded format, rather than as expanded public keys. This should
6626 save several megabytes on typical clients. Closes ticket 27246.
6628 o Minor features (OpenSSL bug workaround):
6629 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
6630 key export function from handling long labels. When this bug is
6631 detected, Tor will disable TLS 1.3. We recommend upgrading to a
6632 version of OpenSSL without this bug when it becomes available.
6633 Closes ticket 28973.
6635 o Minor features (OpenSSL):
6636 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
6637 than our own. Resolves ticket 19979.
6639 o Minor features (performance):
6640 - Remove about 96% of the work from the function that we run at
6641 startup to test our curve25519_basepoint implementation. Since
6642 this function has yet to find an actual failure, we now only run
6643 it for 8 iterations instead of 200. Based on our profile
6644 information, this change should save around 8% of our startup time
6645 on typical desktops, and may have a similar effect on other
6646 platforms. Closes ticket 28838.
6647 - Stop re-validating our hardcoded Diffie-Hellman parameters on
6648 every startup. Doing this wasted time and cycles, especially on
6649 low-powered devices. Closes ticket 28851.
6651 o Minor features (Rust, code quality):
6652 - Improve rust code quality in the rust protover implementation by
6653 making it more idiomatic. Includes changing an internal API to
6654 take &str instead of &String. Closes ticket 26492.
6656 o Minor features (testing):
6657 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
6658 chutney. Implements ticket 27211.
6660 o Minor features (tor-resolve):
6661 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
6662 Side-effect of the refactoring for ticket 26526.
6664 o Minor features (UI):
6665 - Log each included configuration file or directory as we read it,
6666 to provide more visibility about where Tor is reading from. Patch
6667 from Unto Sten; closes ticket 27186.
6668 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
6669 Closes ticket 26703.
6671 o Minor bugfixes (32-bit OSX and iOS, timing):
6672 - Fix an integer overflow bug in our optimized 32-bit millisecond-
6673 difference algorithm for 32-bit Apple platforms. Previously, it
6674 would overflow when calculating the difference between two times
6675 more than 47 days apart. Fixes part of bug 27139; bugfix
6677 - Improve the precision of our 32-bit millisecond difference
6678 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
6679 bugfix on 0.3.4.1-alpha.
6680 - Relax the tolerance on the mainloop/update_time_jumps test when
6681 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
6684 o Minor bugfixes (bootstrap):
6685 - Try harder to get descriptors in non-exit test networks, by using
6686 the mid weight for the third hop when there are no exits. Fixes
6687 bug 27237; bugfix on 0.2.6.2-alpha.
6689 o Minor bugfixes (C correctness):
6690 - Avoid casting smartlist index to int implicitly, as it may trigger
6691 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
6692 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
6693 - Use time_t for all values in
6694 predicted_ports_prediction_time_remaining(). Rework the code that
6695 computes difference between durations/timestamps. Fixes bug 27165;
6696 bugfix on 0.3.1.1-alpha.
6698 o Minor bugfixes (client, memory usage):
6699 - When not running as a directory cache, there is no need to store
6700 the text of the current consensus networkstatus in RAM.
6701 Previously, however, clients would store it anyway, at a cost of
6702 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
6705 o Minor bugfixes (client, ReachableAddresses):
6706 - Instead of adding a "reject *:*" line to ReachableAddresses when
6707 loading the configuration, add one to the policy after parsing it
6708 in parse_reachable_addresses(). This prevents extra "reject *.*"
6709 lines from accumulating on reloads. Fixes bug 20874; bugfix on
6710 0.1.1.5-alpha. Patch by Neel Chauhan.
6712 o Minor bugfixes (code quality):
6713 - Rename sandbox_getaddrinfo() and other functions to no longer
6714 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
6715 bugfix on 0.2.7.1-alpha.
6717 o Minor bugfixes (code safety):
6718 - Rewrite our assertion macros so that they no longer suppress the
6719 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
6722 o Minor bugfixes (compilation):
6723 - Initialize a variable unconditionally in aes_new_cipher(), since
6724 some compilers cannot tell that we always initialize it before
6725 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
6727 o Minor bugfixes (configuration):
6728 - Refuse to start with relative file paths and RunAsDaemon set
6729 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
6732 o Minor bugfixes (configuration, Onion Services):
6733 - In rend_service_parse_port_config(), disallow any input to remain
6734 after address-port pair was parsed. This will catch address and
6735 port being whitespace-separated by mistake of the user. Fixes bug
6736 27044; bugfix on 0.2.9.10.
6738 o Minor bugfixes (connection, relay):
6739 - Avoid a logging a BUG() stacktrace when closing connection held
6740 open because the write side is rate limited but not the read side.
6741 Now, the connection read side is simply shut down until Tor is
6742 able to flush the connection and close it. Fixes bug 27750; bugfix
6745 o Minor bugfixes (continuous integration, Windows):
6746 - Stop reinstalling identical packages in our Windows CI. Fixes bug
6747 27464; bugfix on 0.3.4.1-alpha.
6748 - Install only the necessary mingw packages during our appveyor
6749 builds. This change makes the build a little faster, and prevents
6750 a conflict with a preinstalled mingw openssl that appveyor now
6751 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
6752 - Explicitly specify the path to the OpenSSL library and do not
6753 download OpenSSL from Pacman, but instead use the library that is
6754 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
6755 - Manually configure the zstd compiler options, when building using
6756 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
6757 not come with a pkg-config file. Fixes bug 28454; bugfix
6759 - Stop using an external OpenSSL install, and stop installing MSYS2
6760 packages, when building using mingw on Appveyor Windows CI. Fixes
6761 bug 28399; bugfix on 0.3.4.1-alpha.
6763 o Minor bugfixes (controller):
6764 - Consider all routerinfo errors other than "not a server" to be
6765 transient for the purpose of "GETINFO exit-policy/*" controller
6766 request. Print stacktrace in the unlikely case of failing to
6767 recompute routerinfo digest. Fixes bug 27034; bugfix
6770 o Minor bugfixes (correctness):
6771 - Fix an unreached code path where we checked the value of
6772 "hostname" inside send_resolved_hostname_cell(). Previously, we
6773 used it before checking it; now we check it first. Fixes bug
6774 28879; bugfix on 0.1.2.7-alpha.
6776 o Minor bugfixes (directory connection shutdown):
6777 - Avoid a double-close when shutting down a stalled directory
6778 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
6780 o Minor bugfixes (directory permissions):
6781 - When a user requests a group-readable DataDirectory, give it to
6782 them. Previously, when the DataDirectory and the CacheDirectory
6783 were the same, the default setting (0) for
6784 CacheDirectoryGroupReadable would override the setting for
6785 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
6788 o Minor bugfixes (HTTP tunnel):
6789 - Fix a bug warning when closing an HTTP tunnel connection due to an
6790 HTTP request we couldn't handle. Fixes bug 26470; bugfix
6793 o Minor bugfixes (ipv6):
6794 - In addrs_in_same_network_family(), we choose the subnet size based
6795 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
6796 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
6797 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
6799 o Minor bugfixes (Linux seccomp2 sandbox):
6800 - Permit the "shutdown()" system call, which is apparently used by
6801 OpenSSL under some circumstances. Fixes bug 28183; bugfix
6804 o Minor bugfixes (logging):
6805 - Stop talking about the Named flag in log messages. Clients have
6806 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
6808 - As a precaution, do an early return from log_addr_has_changed() if
6809 Tor is running as client. Also, log a stack trace for debugging as
6810 this function should only be called when Tor runs as server. Fixes
6811 bug 26892; bugfix on 0.1.1.9-alpha.
6812 - Refrain from mentioning bug 21018 in the logs, as it is already
6813 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
6815 o Minor bugfixes (logging, documentation):
6816 - When SafeLogging is enabled, scrub IP address in
6817 channel_tls_process_netinfo_cell(). Also, add a note to manpage
6818 that scrubbing is not guaranteed on loglevels below Notice. Fixes
6819 bug 26882; bugfix on 0.2.4.10-alpha.
6821 o Minor bugfixes (memory leaks):
6822 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
6823 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
6824 - Fix a small memory leak when calling Tor with --dump-config. Fixes
6825 bug 27893; bugfix on 0.3.2.1-alpha.
6827 o Minor bugfixes (netflow padding):
6828 - Ensure circuitmux queues are empty before scheduling or sending
6829 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
6831 o Minor bugfixes (onion service v2):
6832 - Log at level "info", not "warning", in the case that we do not
6833 have a consensus when a .onion request comes in. This can happen
6834 normally while bootstrapping. Fixes bug 27040; bugfix
6837 o Minor bugfixes (onion service v3):
6838 - When deleting an ephemeral onion service (DEL_ONION), do not close
6839 any rendezvous circuits in order to let the existing client
6840 connections finish by themselves or closed by the application. The
6841 HS v2 is doing that already so now we have the same behavior for
6842 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
6843 - Build the service descriptor's signing key certificate before
6844 uploading, so we always have a fresh one: leaving no chances for
6845 it to expire service side. Fixes bug 27838; bugfix
6847 - Stop dumping a stack trace when trying to connect to an intro
6848 point without having a descriptor for it. Fixes bug 27774; bugfix
6850 - When selecting a v3 rendezvous point, don't only look at the
6851 protover, but also check whether the curve25519 onion key is
6852 present. This way we avoid picking a relay that supports the v3
6853 rendezvous but for which we don't have the microdescriptor. Fixes
6854 bug 27797; bugfix on 0.3.2.1-alpha.
6855 - Close all SOCKS request (for the same .onion) if the newly fetched
6856 descriptor is unusable. Before that, we would close only the first
6857 one leaving the other hanging and let to time out by themselves.
6858 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
6859 - When the onion service directory can't be created or has the wrong
6860 permissions, do not log a stack trace. Fixes bug 27335; bugfix
6862 - When replacing a descriptor in the client cache, make sure to
6863 close all client introduction circuits for the old descriptor, so
6864 we don't end up with unusable leftover circuits. Fixes bug 27471;
6865 bugfix on 0.3.2.1-alpha.
6867 o Minor bugfixes (OS compatibility):
6868 - Properly handle configuration changes that move a listener to/from
6869 wildcard IP address. If the first attempt to bind a socket fails,
6870 close the old listener and try binding the socket again. Fixes bug
6871 17873; bugfix on 0.0.8pre-1.
6873 o Minor bugfixes (performance)::
6874 - Rework node_is_a_configured_bridge() to no longer call
6875 node_get_all_orports(), which was performing too many memory
6876 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
6878 o Minor bugfixes (protover):
6879 - Reject protocol names containing bytes other than alphanumeric
6880 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
6883 o Minor bugfixes (protover, rust):
6884 - Reject extra commas in version strings. Fixes bug 27197; bugfix
6886 - protover_all_supported() would attempt to allocate up to 16GB on
6887 some inputs, leading to a potential memory DoS. Fixes bug 27206;
6888 bugfix on 0.3.3.5-rc.
6889 - Compute protover votes correctly in the rust version of the
6890 protover code. Previously, the protover rewrite in 24031 allowed
6891 repeated votes from the same voter for the same protocol version
6892 to be counted multiple times in protover_compute_vote(). Fixes bug
6893 27649; bugfix on 0.3.3.5-rc.
6894 - Reject protover names that contain invalid characters. Fixes bug
6895 27687; bugfix on 0.3.3.1-alpha.
6897 o Minor bugfixes (relay shutdown, systemd):
6898 - Notify systemd of ShutdownWaitLength so it can be set to longer
6899 than systemd's TimeoutStopSec. In Tor's systemd service file, set
6900 TimeoutSec to 60 seconds to allow Tor some time to shut down.
6901 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
6903 o Minor bugfixes (relay statistics):
6904 - Update relay descriptor on bandwidth changes only when the uptime
6905 is smaller than 24h, in order to reduce the efficiency of guard
6906 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
6908 o Minor bugfixes (relay):
6909 - Consider the fact that we'll be making direct connections to our
6910 entry and guard nodes when computing the fraction of nodes that
6911 have their descriptors. Also, if we are using bridges and there is
6912 at least one bridge with a full descriptor, treat the fraction of
6913 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
6914 Patch by Neel Chauhan.
6915 - Update the message logged on relays when DirCache is disabled.
6916 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
6917 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
6919 o Minor bugfixes (testing):
6920 - Stop running stem's unit tests as part of "make test-stem", but
6921 continue to run stem's unit and online tests during "make test-
6922 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
6923 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
6924 bugfix on 0.3.0.1-alpha.
6925 - Make the hs_service tests use the same time source when creating
6926 the introduction point and when testing it. Now tests work better
6927 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
6929 - Revise the "conditionvar_timeout" test so that it succeeds even on
6930 heavily loaded systems where the test threads are not scheduled
6931 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
6932 - Fix two unit tests to work when HOME environment variable is not
6933 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
6934 - If a unit test running in a subprocess exits abnormally or with a
6935 nonzero status code, treat the test as having failed, even if the
6936 test reported success. Without this fix, memory leaks don't cause
6937 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
6938 bugfix on 0.2.2.4-alpha.
6939 - When logging a version mismatch in our openssl_version tests,
6940 report the actual offending version strings. Fixes bug 26152;
6941 bugfix on 0.2.9.1-alpha.
6942 - Fix forking tests on Windows when there is a space somewhere in
6943 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
6945 o Minor bugfixes (Windows):
6946 - Correctly identify Windows 8.1, Windows 10, and Windows Server
6947 2008 and later from their NT versions. Fixes bug 28096; bugfix on
6948 0.2.2.34; reported by Keifer Bly.
6949 - On recent Windows versions, the GetVersionEx() function may report
6950 an earlier Windows version than the running OS. To avoid user
6951 confusion, add "[or later]" to Tor's version string on affected
6952 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
6954 - Remove Windows versions that were never supported by the
6955 GetVersionEx() function. Stop duplicating the latest Windows
6956 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
6957 reported by Keifer Bly.
6959 o Code simplification and refactoring:
6960 - When parsing a port configuration, make it more obvious to static
6961 analyzer tools that we always initialize the address. Closes
6963 - Divide more large Tor source files -- especially ones that span
6964 multiple areas of functionality -- into smaller parts, including
6965 onion.c and main.c. Closes ticket 26747.
6966 - Divide the "routerparse.c" module into separate modules for each
6967 group of parsed objects. Closes ticket 27924.
6968 - Move protover_rust.c to the same place protover.c was moved to.
6969 Closes ticket 27814.
6970 - Split directory.c into separate pieces for client, server, and
6971 common functionality. Closes ticket 26744.
6972 - Split the non-statistics-related parts from the rephist.c and
6973 geoip.c modules. Closes ticket 27892.
6974 - Split the router.c file into relay-only and shared components, to
6975 help with future modularization. Closes ticket 27864.
6976 - Divide the routerlist.c and dirserv.c modules into smaller parts.
6977 Closes ticket 27799.
6978 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
6979 longer needed. Closes ticket 26502.
6980 - Include paths to header files within Tor are now qualified by
6981 directory within the top-level src directory.
6982 - Many structures have been removed from the centralized "or.h"
6983 header, and moved into their own headers. This will allow us to
6984 reduce the number of places in the code that rely on each
6985 structure's contents and layout. Closes ticket 26383.
6986 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
6987 - Remove GetAdaptersAddresses_fn_t. The code that used it was
6988 removed as part of the 26481 refactor. Closes ticket 27467.
6989 - Rework Tor SOCKS server code to use Trunnel and benefit from
6990 autogenerated functions for parsing and generating SOCKS wire
6991 format. New implementation is cleaner, more maintainable and
6992 should be less prone to heartbleed-style vulnerabilities.
6993 Implements a significant fraction of ticket 3569.
6994 - Split sampled_guards_update_from_consensus() and
6995 select_entry_guard_for_circuit() into subfunctions. In
6996 entry_guards_update_primary() unite three smartlist enumerations
6997 into one and move smartlist comparison code out of the function.
6998 Closes ticket 21349.
6999 - Tor now assumes that you have standards-conformant stdint.h and
7000 inttypes.h headers when compiling. Closes ticket 26626.
7001 - Unify our bloom filter logic. Previously we had two copies of this
7002 code: one for routerlist filtering, and one for address set
7003 calculations. Closes ticket 26510.
7004 - Use the simpler strcmpstart() helper in
7005 rend_parse_v2_service_descriptor instead of strncmp(). Closes
7007 - Utility functions that can perform a DNS lookup are now wholly
7008 separated from those that can't, in separate headers and C
7009 modules. Closes ticket 26526.
7012 - In the tor-resolve(1) manpage, fix the reference to socks-
7013 extensions.txt by adding a web URL. Resolves ticket 27853.
7014 - Mention that we require Python to be 2.7 or newer for some
7015 integration tests that we ship with Tor. Resolves ticket 27677.
7016 - Copy paragraph and URL to Tor's code of conduct document from
7017 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
7018 - Remove old instructions from INSTALL document. Closes ticket 26588.
7019 - Warn users that they should not include MyFamily line(s) in their
7020 torrc when running Tor bridge. Closes ticket 26908.
7023 - Tor no longer supports building with the dmalloc library. For
7024 debugging memory issues, we suggest using gperftools or msan
7025 instead. Closes ticket 26426.
7026 - Tor no longer attempts to run on Windows environments without the
7027 GetAdaptersAddresses() function. This function has existed since
7028 Windows XP, which is itself already older than we support.
7029 - Remove Tor2web functionality for version 2 onion services. The
7030 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
7031 (This feature was never shipped in vanilla Tor and it was only
7032 possible to use this feature by building the support at compile
7033 time. Tor2webMode is not implemented for version 3 onion services.)
7034 Closes ticket 26367.
7037 - Increase logging and tag all log entries with timestamps in
7038 test_rebind.py. Provides diagnostics for issue 28229.
7040 o Code simplification and refactoring (shared random, dirauth):
7041 - Change many tor_assert() to use BUG() instead. The idea is to not
7042 crash a dirauth but rather scream loudly with a stacktrace and let
7043 it continue run. The shared random subsystem is very resilient and
7044 if anything wrong happens with it, at worst a non coherent value
7045 will be put in the vote and discarded by the other authorities.
7046 Closes ticket 19566.
7048 o Documentation (onion services):
7049 - Improve HSv3 client authorization by making some options more
7050 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
7051 - Document in the man page that changing ClientOnionAuthDir value or
7052 adding a new file in the directory will not work at runtime upon
7053 sending a HUP if Sandbox 1. Closes ticket 28128.
7054 - Note in the man page that the only real way to fully revoke an
7055 onion service v3 client authorization is by restarting the tor
7056 process. Closes ticket 28275.
7059 Changes in version 0.3.4.9 - 2018-11-02
7060 Tor 0.3.4.9 is the second stable release in its series; it backports
7061 numerous fixes, including a fix for a bandwidth management bug that
7062 was causing memory exhaustion on relays. Anyone running an earlier
7063 version of Tor 0.3.4.9 should upgrade.
7065 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
7066 - Fix compilation on ARM (and other less-used CPUs) when compiling
7067 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
7069 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
7070 - Make sure Tor bootstraps and works properly if only the
7071 ControlPort is set. Prior to this fix, Tor would only bootstrap
7072 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
7073 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
7075 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
7076 - When our write bandwidth limit is exhausted, stop writing on the
7077 connection. Previously, we had a typo in the code that would make
7078 us stop reading instead, leading to relay connections being stuck
7079 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
7082 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
7083 - Fix a use-after-free error that could be caused by passing Tor an
7084 impossible set of options that would fail during options_act().
7085 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
7087 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
7088 - Don't do a distcheck with --disable-module-dirauth in Travis.
7089 Implements ticket 27252.
7090 - Only run one online rust build in Travis, to reduce network
7091 errors. Skip offline rust builds on Travis for Linux gcc, because
7092 they're redundant. Implements ticket 27252.
7093 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
7094 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
7095 Linux with default settings, because all the non-default builds
7096 use gcc on Linux. Implements ticket 27252.
7098 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
7099 - Use the Travis Homebrew addon to install packages on macOS during
7100 Travis CI. The package list is the same, but the Homebrew addon
7101 does not do a `brew update` by default. Implements ticket 27738.
7103 o Minor features (geoip):
7104 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
7105 Country database. Closes ticket 27991.
7107 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
7108 - Fix an integer overflow bug in our optimized 32-bit millisecond-
7109 difference algorithm for 32-bit Apple platforms. Previously, it
7110 would overflow when calculating the difference between two times
7111 more than 47 days apart. Fixes part of bug 27139; bugfix
7113 - Improve the precision of our 32-bit millisecond difference
7114 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
7115 bugfix on 0.3.4.1-alpha.
7116 - Relax the tolerance on the mainloop/update_time_jumps test when
7117 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
7120 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
7121 - Avoid undefined behavior in an end-of-string check when parsing
7122 the BEGIN line in a directory object. Fixes bug 28202; bugfix
7125 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
7126 - Only install the necessary mingw packages during our appveyor
7127 builds. This change makes the build a little faster, and prevents
7128 a conflict with a preinstalled mingw openssl that appveyor now
7129 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
7131 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
7132 - Rewrite our assertion macros so that they no longer suppress the
7133 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
7135 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
7136 - Stop reinstalling identical packages in our Windows CI. Fixes bug
7137 27464; bugfix on 0.3.4.1-alpha.
7139 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
7140 - Log additional info when we get a relay that shares an ed25519 ID
7141 with a different relay, instead making a BUG() warning. Fixes bug
7142 27800; bugfix on 0.3.2.1-alpha.
7144 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
7145 - Avoid a double-close when shutting down a stalled directory
7146 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
7148 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
7149 - Fix a bug warning when closing an HTTP tunnel connection due to an
7150 HTTP request we couldn't handle. Fixes bug 26470; bugfix
7153 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
7154 - Ensure circuitmux queues are empty before scheduling or sending
7155 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
7157 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
7158 - When the onion service directory can't be created or has the wrong
7159 permissions, do not log a stack trace. Fixes bug 27335; bugfix
7162 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
7163 - Close all SOCKS request (for the same .onion) if the newly fetched
7164 descriptor is unusable. Before that, we would close only the first
7165 one leaving the other hanging and let to time out by themselves.
7166 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
7168 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
7169 - When selecting a v3 rendezvous point, don't only look at the
7170 protover, but also check whether the curve25519 onion key is
7171 present. This way we avoid picking a relay that supports the v3
7172 rendezvous but for which we don't have the microdescriptor. Fixes
7173 bug 27797; bugfix on 0.3.2.1-alpha.
7175 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
7176 - Reject protocol names containing bytes other than alphanumeric
7177 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
7180 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
7181 - Compute protover votes correctly in the rust version of the
7182 protover code. Previously, the protover rewrite in 24031 allowed
7183 repeated votes from the same voter for the same protocol version
7184 to be counted multiple times in protover_compute_vote(). Fixes bug
7185 27649; bugfix on 0.3.3.5-rc.
7186 - Reject protover names that contain invalid characters. Fixes bug
7187 27687; bugfix on 0.3.3.1-alpha.
7189 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
7190 - protover_all_supported() would attempt to allocate up to 16GB on
7191 some inputs, leading to a potential memory DoS. Fixes bug 27206;
7192 bugfix on 0.3.3.5-rc.
7194 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
7195 - Fix an API mismatch in the rust implementation of
7196 protover_compute_vote(). This bug could have caused crashes on any
7197 directory authorities running Tor with Rust (which we do not yet
7198 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
7200 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
7201 - Fix a potential null dereference in protover_all_supported(). Add
7202 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
7203 - Return a string that can be safely freed by C code, not one
7204 created by the rust allocator, in protover_all_supported(). Fixes
7205 bug 27740; bugfix on 0.3.3.1-alpha.
7207 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
7208 - If a unit test running in a subprocess exits abnormally or with a
7209 nonzero status code, treat the test as having failed, even if the
7210 test reported success. Without this fix, memory leaks don't cause
7211 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
7212 bugfix on 0.2.2.4-alpha.
7214 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
7215 - Make the hs_service tests use the same time source when creating
7216 the introduction point and when testing it. Now tests work better
7217 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
7220 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
7221 - Treat backtrace test failures as expected on BSD-derived systems
7222 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
7223 (FreeBSD failures have been treated as expected since 18204 in
7224 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
7227 Changes in version 0.2.9.17 - 2018-09-10
7228 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
7230 o Minor features (compatibility, backport from 0.3.4.8):
7231 - Tell OpenSSL to maintain backward compatibility with previous
7232 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
7233 ciphers are disabled by default. Closes ticket 27344.
7235 o Minor features (continuous integration, backport from 0.3.4.7-rc):
7236 - Enable macOS builds in our Travis CI configuration. Closes
7238 - Install libcap-dev and libseccomp2-dev so these optional
7239 dependencies get tested on Travis CI. Closes ticket 26560.
7240 - Run asciidoc during Travis CI. Implements ticket 27087.
7241 - Use ccache in our Travis CI configuration. Closes ticket 26952.
7243 o Minor features (geoip):
7244 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
7245 Country database. Closes ticket 27089.
7247 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
7248 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
7249 tell the compiler not to include the system malloc implementation.
7250 Fixes bug 20424; bugfix on 0.2.0.20-rc.
7252 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
7253 - Silence a spurious compiler warning on the GetAdaptersAddresses
7254 function pointer cast. This issue is already fixed by 26481 in
7255 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
7256 bugfix on 0.2.3.11-alpha.
7257 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
7258 supported, and always fails. Some compilers warn about the
7259 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
7262 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
7263 - Don't link or search for pthreads when building for Windows, even
7264 if we are using build environment (like mingw) that provides a
7265 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
7267 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
7268 - Skip a pair of unreliable key generation tests on Windows, until
7269 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
7270 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
7272 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
7273 - Pass the module flags to distcheck configure, and log the flags
7274 before running configure. (Backported to 0.2.9 and later as a
7275 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
7277 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
7278 - When a Travis build fails, and showing a log fails, keep trying to
7279 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
7280 - When we use echo in Travis, don't pass a --flag as the first
7281 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
7283 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
7284 - When voting for recommended versions, make sure that all of the
7285 versions are well-formed and parsable. Fixes bug 26485; bugfix
7288 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
7289 - Fix a bug in out sandboxing rules for the openat() syscall.
7290 Previously, no openat() call would be permitted, which would break
7291 filesystem operations on recent glibc versions. Fixes bug 25440;
7292 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
7294 o Minor bugfixes (onion services, backport from 0.3.4.8):
7295 - Silence a spurious compiler warning in
7296 rend_client_send_introduction(). Fixes bug 27463; bugfix
7299 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
7300 - Log a protocol warning when single onion services or Tor2web clients
7301 fail to authenticate direct connections to relays.
7302 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
7304 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
7305 - Disable core dumps in test_bt.sh, to avoid failures in "make
7306 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
7308 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
7309 - Before running make test-network-all, delete old logs and test
7310 result files, to avoid spurious failures. Fixes bug 27295; bugfix
7313 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
7314 - Our "tortls/cert_matches_key" unit test no longer relies on
7315 OpenSSL internals. Previously, it relied on unsupported OpenSSL
7316 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
7317 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
7319 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
7320 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
7321 27185; bugfix on 0.2.2.2-alpha.
7324 Changes in version 0.3.2.12 - 2018-09-10
7325 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
7327 o Minor features (compatibility, backport from 0.3.4.8):
7328 - Tell OpenSSL to maintain backward compatibility with previous
7329 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
7330 ciphers are disabled by default. Closes ticket 27344.
7332 o Minor features (continuous integration, backport from 0.3.4.7-rc):
7333 - Enable macOS builds in our Travis CI configuration. Closes
7335 - Install libcap-dev and libseccomp2-dev so these optional
7336 dependencies get tested on Travis CI. Closes ticket 26560.
7337 - Run asciidoc during Travis CI. Implements ticket 27087.
7338 - Use ccache in our Travis CI configuration. Closes ticket 26952.
7340 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
7341 - Use cargo cache in our Travis CI configuration. Closes
7344 o Minor features (controller, backport from 0.3.4.6-rc):
7345 - The control port now exposes the list of HTTPTunnelPorts and
7346 ExtOrPorts via GETINFO net/listeners/httptunnel and
7347 net/listeners/extor respectively. Closes ticket 26647.
7349 o Minor features (directory authorities, backport from 0.3.4.7-rc):
7350 - Authorities no longer vote to make the subprotocol version
7351 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
7352 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
7354 o Minor features (geoip):
7355 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
7356 Country database. Closes ticket 27089.
7358 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
7359 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
7360 tell the compiler not to include the system malloc implementation.
7361 Fixes bug 20424; bugfix on 0.2.0.20-rc.
7362 - Don't try to use a pragma to temporarily disable the
7363 -Wunused-const-variable warning if the compiler doesn't support
7364 it. Fixes bug 26785; bugfix on 0.3.2.11.
7366 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
7367 - Silence a spurious compiler warning on the GetAdaptersAddresses
7368 function pointer cast. This issue is already fixed by 26481 in
7369 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
7370 bugfix on 0.2.3.11-alpha.
7371 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
7372 supported, and always fails. Some compilers warn about the
7373 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
7376 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
7377 - Don't link or search for pthreads when building for Windows, even
7378 if we are using build environment (like mingw) that provides a
7379 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
7381 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
7382 - Skip a pair of unreliable key generation tests on Windows, until
7383 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
7384 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
7386 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
7387 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
7388 - Pass the module flags to distcheck configure, and log the flags
7389 before running configure. (Backported to 0.2.9 and later as a
7390 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
7392 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
7393 - When a Travis build fails, and showing a log fails, keep trying to
7394 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
7395 - When we use echo in Travis, don't pass a --flag as the first
7396 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
7398 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
7399 - When voting for recommended versions, make sure that all of the
7400 versions are well-formed and parsable. Fixes bug 26485; bugfix
7403 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
7404 - Fix a bug in out sandboxing rules for the openat() syscall.
7405 Previously, no openat() call would be permitted, which would break
7406 filesystem operations on recent glibc versions. Fixes bug 25440;
7407 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
7409 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
7410 - Improve the log message when connection initiators fail to
7411 authenticate direct connections to relays. Fixes bug 26927; bugfix
7414 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
7415 - Fix bug that causes services to not ever rotate their descriptors
7416 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
7419 o Minor bugfixes (onion services, backport from 0.3.4.8):
7420 - Silence a spurious compiler warning in
7421 rend_client_send_introduction(). Fixes bug 27463; bugfix
7424 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
7425 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
7427 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
7428 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
7429 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
7430 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
7432 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
7433 - Log a protocol warning when single onion services or Tor2web clients
7434 fail to authenticate direct connections to relays.
7435 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
7437 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
7438 - Disable core dumps in test_bt.sh, to avoid failures in "make
7439 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
7441 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
7442 - When running make test-network-all, use the mixed+hs-v2 network.
7443 (A previous fix to chutney removed v3 onion services from the
7444 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
7445 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
7446 - Before running make test-network-all, delete old logs and test
7447 result files, to avoid spurious failures. Fixes bug 27295; bugfix
7450 o Minor bugfixes (testing, openssl compatibility):
7451 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
7452 internals. Previously, it relied on unsupported OpenSSL behavior in
7453 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
7454 bugfix on 0.2.5.1-alpha.
7456 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
7457 - Our "tortls/cert_matches_key" unit test no longer relies on
7458 OpenSSL internals. Previously, it relied on unsupported OpenSSL
7459 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
7460 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
7462 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
7463 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
7464 27185; bugfix on 0.2.2.2-alpha.
7467 Changes in version 0.3.3.10 - 2018-09-10
7468 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
7470 o Minor features (bug workaround, backport from 0.3.4.7-rc):
7471 - Compile correctly on systems that provide the C11 stdatomic.h
7472 header, but where C11 atomic functions don't actually compile.
7473 Closes ticket 26779; workaround for Debian issue 903709.
7475 o Minor features (compatibility, backport from 0.3.4.8):
7476 - Tell OpenSSL to maintain backward compatibility with previous
7477 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
7478 ciphers are disabled by default. Closes ticket 27344.
7480 o Minor features (continuous integration, backport from 0.3.4.7-rc):
7481 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
7482 - Enable macOS builds in our Travis CI configuration. Closes
7484 - Install libcap-dev and libseccomp2-dev so these optional
7485 dependencies get tested on Travis CI. Closes ticket 26560.
7486 - Run asciidoc during Travis CI. Implements ticket 27087.
7487 - Use ccache in our Travis CI configuration. Closes ticket 26952.
7489 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
7490 - Use cargo cache in our Travis CI configuration. Closes
7493 o Minor features (controller, backport from 0.3.4.6-rc):
7494 - The control port now exposes the list of HTTPTunnelPorts and
7495 ExtOrPorts via GETINFO net/listeners/httptunnel and
7496 net/listeners/extor respectively. Closes ticket 26647.
7498 o Minor features (directory authorities, backport from 0.3.4.7-rc):
7499 - Authorities no longer vote to make the subprotocol version
7500 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
7501 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
7503 o Minor features (geoip):
7504 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
7505 Country database. Closes ticket 27089.
7507 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
7508 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
7509 tell the compiler not to include the system malloc implementation.
7510 Fixes bug 20424; bugfix on 0.2.0.20-rc.
7511 - Don't try to use a pragma to temporarily disable the
7512 -Wunused-const-variable warning if the compiler doesn't support
7513 it. Fixes bug 26785; bugfix on 0.3.2.11.
7515 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
7516 - Silence a spurious compiler warning on the GetAdaptersAddresses
7517 function pointer cast. This issue is already fixed by 26481 in
7518 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
7519 bugfix on 0.2.3.11-alpha.
7520 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
7521 supported, and always fails. Some compilers warn about the
7522 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
7525 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
7526 - Don't link or search for pthreads when building for Windows, even
7527 if we are using build environment (like mingw) that provides a
7528 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
7530 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
7531 - Skip a pair of unreliable key generation tests on Windows, until
7532 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
7533 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
7535 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
7536 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
7537 - Pass the module flags to distcheck configure, and log the flags
7538 before running configure. (Backported to 0.2.9 and later as a
7539 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
7541 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
7542 - When a Travis build fails, and showing a log fails, keep trying to
7543 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
7544 - When we use echo in Travis, don't pass a --flag as the first
7545 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
7547 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
7548 - When voting for recommended versions, make sure that all of the
7549 versions are well-formed and parsable. Fixes bug 26485; bugfix
7552 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
7553 - Always call tor_free_all() when leaving tor_run_main(). When we
7554 did not, restarting tor in-process would cause an assertion
7555 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
7557 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
7558 - Fix a bug in our sandboxing rules for the openat() syscall.
7559 Previously, no openat() call would be permitted, which would break
7560 filesystem operations on recent glibc versions. Fixes bug 25440;
7561 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
7563 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
7564 - Improve the log message when connection initiators fail to
7565 authenticate direct connections to relays. Fixes bug 26927; bugfix
7568 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
7569 - Fix bug that causes services to not ever rotate their descriptors
7570 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
7573 o Minor bugfixes (onion services, backport from 0.3.4.8):
7574 - Silence a spurious compiler warning in
7575 rend_client_send_introduction(). Fixes bug 27463; bugfix
7578 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
7579 - Work around two different bugs in the OS X 10.10 and later SDKs
7580 that would prevent us from successfully targeting earlier versions
7581 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
7583 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
7584 - Fix compilation of the unit tests on GNU/Hurd, which does not
7585 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
7588 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
7589 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
7591 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
7592 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
7593 - Protover parsing was accepting the presence of whitespace in
7594 version strings, which the C implementation would choke on, e.g.
7595 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
7596 - Protover parsing was ignoring a 2nd hyphen and everything after
7597 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
7599 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
7600 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
7601 - cd to ${abs_top_builddir}/src/rust before running cargo in
7602 src/test/test_rust.sh. This makes the working directory consistent
7603 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
7605 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
7606 - Log a protocol warning when single onion services or Tor2web clients
7607 fail to authenticate direct connections to relays.
7608 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
7610 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
7611 - Disable core dumps in test_bt.sh, to avoid failures in "make
7612 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
7614 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
7615 - When running make test-network-all, use the mixed+hs-v2 network.
7616 (A previous fix to chutney removed v3 onion services from the
7617 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
7618 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
7619 - Before running make test-network-all, delete old logs and test
7620 result files, to avoid spurious failures. Fixes bug 27295; bugfix
7623 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
7624 - Our "tortls/cert_matches_key" unit test no longer relies on
7625 OpenSSL internals. Previously, it relied on unsupported OpenSSL
7626 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
7627 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
7629 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
7630 - Stop sending ed25519 link specifiers in v3 onion service introduce
7631 cells and descriptors, when the rendezvous or introduction point
7632 doesn't support ed25519 link authentication. Fixes bug 26627;
7633 bugfix on 0.3.2.4-alpha.
7635 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
7636 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
7637 27185; bugfix on 0.2.2.2-alpha.
7640 Changes in version 0.3.4.8 - 2018-09-10
7641 Tor 0.3.4.8 is the first stable release in its series; it includes
7642 compilation and portability fixes.
7644 The Tor 0.3.4 series includes improvements for running Tor in
7645 low-power and embedded environments, which should help performance in
7646 general. We've begun work on better modularity, and included preliminary
7647 changes on the directory authority side to accommodate a new bandwidth
7648 measurement system. We've also integrated more continuous-integration
7649 systems into our development process, and made corresponding changes to
7650 Tor's testing infrastructure. Finally, we've continued to refine
7651 our anti-denial-of-service code.
7653 Below are the changes since 0.3.3.9. For a list of only the changes
7654 since 0.3.4.7-rc, see the ChangeLog file.
7656 o New system requirements:
7657 - Tor no longer tries to support old operating systems without
7658 mmap() or some local equivalent. Apparently, compilation on such
7659 systems has been broken for some time, without anybody noticing or
7660 complaining. Closes ticket 25398.
7662 o Major features (directory authority, modularization):
7663 - The directory authority subsystem has been modularized. The code
7664 is now located in src/or/dirauth/, and is compiled in by default.
7665 To disable the module, the configure option
7666 --disable-module-dirauth has been added. This module may be
7667 disabled by default in some future release. Closes ticket 25610.
7669 o Major features (main loop, CPU usage):
7670 - When Tor is disabled (via DisableNetwork or via hibernation), it
7671 no longer needs to run any per-second events. This change should
7672 make it easier for mobile applications to disable Tor while the
7673 device is sleeping, or Tor is not running. Closes ticket 26063.
7674 - Tor no longer enables all of its periodic events by default.
7675 Previously, Tor would enable all possible main loop events,
7676 regardless of whether it needed them. Furthermore, many of these
7677 events are now disabled when Tor is hibernating or DisableNetwork
7678 is set. This is a big step towards reducing client CPU usage by
7679 reducing the amount of wake-ups the daemon does. Closes tickets
7681 - The bandwidth-limitation logic has been refactored so that
7682 bandwidth calculations are performed on-demand, rather than every
7683 TokenBucketRefillInterval milliseconds. This change should improve
7684 the granularity of our bandwidth calculations, and limit the
7685 number of times that the Tor process needs to wake up when it is
7686 idle. Closes ticket 25373.
7687 - Move responsibility for many operations from a once-per-second
7688 callback to a callback that is only scheduled as needed. Moving
7689 this functionality has allowed us to disable the callback when
7690 Tor's network is disabled. Once enough items are removed from our
7691 once-per-second callback, we can eliminate it entirely to conserve
7692 CPU when idle. The functionality removed includes: closing
7693 connections, circuits, and channels (ticket 25932); consensus
7694 voting (25937); flushing log callbacks (25951); honoring delayed
7695 SIGNEWNYM requests (25949); rescanning the consensus cache
7696 (25931); saving the state file to disk (25948); warning relay
7697 operators about unreachable ports (25952); and keeping track of
7698 Tor's uptime (26009).
7700 o Minor features (accounting):
7701 - When Tor becomes dormant, it now uses a scheduled event to wake up
7702 at the right time. Previously, we would use the per-second timer
7703 to check whether to wake up, but we no longer have any per-second
7704 timers enabled when the network is disabled. Closes ticket 26064.
7706 o Minor features (bug workaround):
7707 - Compile correctly on systems that provide the C11 stdatomic.h
7708 header, but where C11 atomic functions don't actually compile.
7709 Closes ticket 26779; workaround for Debian issue 903709.
7711 o Minor features (code quality):
7712 - Add optional spell-checking for the Tor codebase, using the
7713 "misspell" program. To use this feature, run "make check-typos".
7714 Closes ticket 25024.
7716 o Minor features (compatibility):
7717 - Tell OpenSSL to maintain backward compatibility with previous
7718 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
7719 ciphers are disabled by default. Closes ticket 27344.
7720 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
7721 the no-deprecated option, and builds correctly with them. Closes
7722 tickets 19429, 19981, and 25353.
7724 o Minor features (compilation):
7725 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
7726 tell the compiler not to include the system malloc implementation.
7727 Fixes bug 20424; bugfix on 0.2.0.20-rc.
7728 - Don't try to use a pragma to temporarily disable the
7729 -Wunused-const-variable warning if the compiler doesn't support
7730 it. Fixes bug 26785; bugfix on 0.3.2.11.
7731 - When building Tor, prefer to use Python 3 over Python 2, and more
7732 recent (contemplated) versions over older ones. Closes
7735 o Minor features (compression, zstd):
7736 - When running with zstd, Tor now considers using advanced functions
7737 that the zstd maintainers have labeled as potentially unstable. To
7738 prevent breakage, Tor will only use this functionality when the
7739 runtime version of the zstd library matches the version with which
7740 Tor was compiled. Closes ticket 25162.
7742 o Minor features (configuration):
7743 - The "DownloadSchedule" options have been renamed to end with
7744 "DownloadInitialDelay". The old names are still allowed, but will
7745 produce a warning. Comma-separated lists are still permitted for
7746 these options, but all values after the first are ignored (as they
7747 have been since 0.2.9). Closes ticket 23354.
7749 o Minor features (continuous integration):
7750 - Log the compiler path and version during Appveyor builds.
7751 Implements ticket 27449.
7752 - Show config.log and test-suite.log after failed Appveyor builds.
7753 Also upload the zipped full logs as a build artifact. Implements
7755 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
7756 - Enable macOS builds in our Travis CI configuration. Closes
7758 - Install libcap-dev and libseccomp2-dev so these optional
7759 dependencies get tested on Travis CI. Closes ticket 26560.
7760 - Only post Appveyor IRC notifications when the build fails.
7761 Implements ticket 27275.
7762 - Run asciidoc during Travis CI. Implements ticket 27087.
7763 - Use ccache in our Travis CI configuration. Closes ticket 26952.
7764 - Add the necessary configuration files for continuous integration
7765 testing on Windows, via the Appveyor platform. Closes ticket
7766 25549. Patches from Marcin Cieślak and Isis Lovecruft.
7768 o Minor features (continuous integration, rust):
7769 - Use cargo cache in our Travis CI configuration. Closes
7772 o Minor features (control port):
7773 - Introduce GETINFO "current-time/{local,utc}" to return the local
7774 and UTC times respectively in ISO format. This helps a controller
7775 like Tor Browser detect a time-related error. Closes ticket 25511.
7776 Patch by Neel Chauhan.
7777 - Introduce new fields to the CIRC_BW event. There are two new
7778 fields in each of the read and written directions. The DELIVERED
7779 fields report the total valid data on the circuit, as measured by
7780 the payload sizes of verified and error-checked relay command
7781 cells. The OVERHEAD fields report the total unused bytes in each
7782 of these cells. Closes ticket 25903.
7784 o Minor features (controller):
7785 - The control port now exposes the list of HTTPTunnelPorts and
7786 ExtOrPorts via GETINFO net/listeners/httptunnel and
7787 net/listeners/extor respectively. Closes ticket 26647.
7789 o Minor features (directory authorities):
7790 - Stop warning about incomplete bw lines before the first complete
7791 bw line has been found, so that additional header lines can be
7792 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
7793 - Authorities no longer vote to make the subprotocol version
7794 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
7795 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
7797 o Minor features (directory authority):
7798 - Directory authorities now open their key-pinning files as O_SYNC,
7799 to limit their chances of accidentally writing partial lines.
7800 Closes ticket 23909.
7802 o Minor features (directory authority, forward compatibility):
7803 - Make the lines of the measured bandwidth file able to contain
7804 their entries in any order. Previously, the node_id entry needed
7805 to come first. Closes ticket 26004.
7807 o Minor features (entry guards):
7808 - Introduce a new torrc option NumPrimaryGuards for controlling the
7809 number of primary guards. Closes ticket 25843.
7811 o Minor features (geoip):
7812 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
7813 Country database. Closes ticket 27089.
7815 o Minor features (performance):
7816 - Avoid a needless call to malloc() when processing an incoming
7817 relay cell. Closes ticket 24914.
7818 - Make our timing-wheel code run a tiny bit faster on 32-bit
7819 platforms, by preferring 32-bit math to 64-bit. Closes
7821 - Avoid a needless malloc()/free() pair every time we handle an ntor
7822 handshake. Closes ticket 25150.
7824 o Minor features (Rust, portability):
7825 - Rust cross-compilation is now supported. Closes ticket 25895.
7827 o Minor features (testing):
7828 - Add a unit test for voting_schedule_get_start_of_next_interval().
7829 Closes ticket 26014, and helps make unit test coverage
7831 - A new unittests module specifically for testing the functions in
7832 the (new-ish) bridges.c module has been created with new
7833 unittests, raising the code coverage percentages. Closes 25425.
7834 - We now have improved testing for addressmap_get_virtual_address()
7835 function. This should improve our test coverage, and make our test
7836 coverage more deterministic. Closes ticket 25993.
7838 o Minor features (timekeeping, circuit scheduling):
7839 - When keeping track of how busy each circuit have been recently on
7840 a given connection, use coarse-grained monotonic timers rather
7841 than gettimeofday(). This change should marginally increase
7842 accuracy and performance. Implements part of ticket 25927.
7844 o Minor features (unit tests):
7845 - Test complete bandwidth measurements files, and test that
7846 incomplete bandwidth lines only give warnings when the end of the
7847 header has not been detected. Fixes bug 25947; bugfix
7850 o Minor bugfixes (bandwidth management):
7851 - Consider ourselves "low on write bandwidth" if we have exhausted
7852 our write bandwidth some time in the last second. This was the
7853 documented behavior before, but the actual behavior was to change
7854 this value every TokenBucketRefillInterval. Fixes bug 25828;
7855 bugfix on 0.2.3.5-alpha.
7857 o Minor bugfixes (C correctness):
7858 - Add a missing lock acquisition in the shutdown code of the control
7859 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
7860 Coverity; this is CID 1433643.
7862 o Minor bugfixes (code style):
7863 - Fixed multiple includes of transports.h in src/or/connection.c
7864 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
7865 - Remove the unused variable n_possible from the function
7866 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
7868 o Minor bugfixes (compilation):
7869 - Silence a spurious compiler warning on the GetAdaptersAddresses
7870 function pointer cast. This issue is already fixed by 26481 in
7871 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
7872 bugfix on 0.2.3.11-alpha.
7873 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
7874 supported, and always fails. Some compilers warn about the
7875 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
7877 - Fix a compilation warning on some versions of GCC when building
7878 code that calls routerinfo_get_my_routerinfo() twice, assuming
7879 that the second call will succeed if the first one did. Fixes bug
7880 26269; bugfix on 0.2.8.2-alpha.
7881 - Refrain from compiling unit testing related object files when
7882 --disable-unittests is set to configure script. Fixes bug 24891;
7883 bugfix on 0.2.5.1-alpha.
7884 - The --enable-fatal-warnings flag now affects Rust code as well.
7885 Closes ticket 26245.
7886 - Avoid a compiler warning when casting the return value of
7887 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
7888 26283; bugfix on 0.2.4.10-alpha.
7890 o Minor bugfixes (compilation, windows):
7891 - Don't link or search for pthreads when building for Windows, even
7892 if we are using build environment (like mingw) that provides a
7893 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
7895 o Minor bugfixes (continuous integration):
7896 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
7897 - Skip a pair of unreliable key generation tests on Windows, until
7898 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
7899 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
7901 o Minor bugfixes (control port):
7902 - Respond with more human-readable error messages to GETINFO exit-
7903 policy/* requests. Also, let controller know if an error is
7904 transient (response code 551) or not (response code 552). Fixes
7905 bug 25852; bugfix on 0.2.8.1-alpha.
7906 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
7907 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
7908 on 0.3.3.1-alpha. Patch by "akwizgran".
7909 - Make CIRC_BW event reflect the total of all data sent on a
7910 circuit, including padding and dropped cells. Also fix a mis-
7911 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
7912 bugfix on 0.2.5.2-alpha.
7914 o Minor bugfixes (correctness, flow control):
7915 - Upon receiving a stream-level SENDME cell, verify that our window
7916 has not grown too large. Fixes bug 26214; bugfix on svn
7919 o Minor bugfixes (directory authority):
7920 - When voting for recommended versions, make sure that all of the
7921 versions are well-formed and parsable. Fixes bug 26485; bugfix
7924 o Minor bugfixes (directory client):
7925 - When unverified-consensus is verified, rename it to cached-
7926 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
7927 - Fixed launching a certificate fetch always during the scheduled
7928 periodic consensus fetch by fetching only in those cases when
7929 consensus are waiting for certs. Fixes bug 24740; bugfix
7932 o Minor bugfixes (error reporting):
7933 - Improve tolerance for directory authorities with skewed clocks.
7934 Previously, an authority with a clock more than 60 seconds ahead
7935 could cause a client with a correct clock to warn that the
7936 client's clock was behind. Now the clocks of a majority of
7937 directory authorities have to be ahead of the client before this
7938 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
7940 o Minor bugfixes (in-process restart):
7941 - Always call tor_free_all() when leaving tor_run_main(). When we
7942 did not, restarting tor in-process would cause an assertion
7943 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
7945 o Minor bugfixes (Linux seccomp2 sandbox):
7946 - Fix a bug in our sandboxing rules for the openat() syscall.
7947 Previously, no openat() call would be permitted, which would break
7948 filesystem operations on recent glibc versions. Fixes bug 25440;
7949 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
7951 o Minor bugfixes (logging):
7952 - Improve the log message when connection initiators fail to
7953 authenticate direct connections to relays. Fixes bug 26927; bugfix
7956 o Minor bugfixes (onion services):
7957 - Silence a spurious compiler warning in
7958 rend_client_send_introduction(). Fixes bug 27463; bugfix
7960 - Fix bug that causes services to not ever rotate their descriptors
7961 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
7963 - Recompute some consensus information after detecting a clock jump,
7964 or after transitioning from a non-live consensus to a live
7965 consensus. We do this to avoid having an outdated state, and
7966 miscalculating the index for next-generation onion services. Fixes
7967 bug 24977; bugfix on 0.3.2.1-alpha.
7969 o Minor bugfixes (portability):
7970 - Fix compilation of the unit tests on GNU/Hurd, which does not
7971 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
7973 - Work around two different bugs in the OS X 10.10 and later SDKs
7974 that would prevent us from successfully targeting earlier versions
7975 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
7976 - Do not align mmap length, as it is not required by POSIX, and the
7977 getpagesize function is deprecated. Fixes bug 25399; bugfix
7980 o Minor bugfixes (portability, FreeBSD):
7981 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
7982 does not stringify on FreeBSD, so we switch to tor_asprintf().
7983 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
7985 o Minor bugfixes (relay statistics):
7986 - When a relay is collecting internal statistics about how many
7987 create cell requests it has seen of each type, accurately count
7988 the requests from relays that temporarily fall out of the
7989 consensus. (To be extra conservative, we were already ignoring
7990 requests from clients in our counts, and we continue ignoring them
7991 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
7993 o Minor bugfixes (rust):
7994 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
7996 - Protover parsing was accepting the presence of whitespace in
7997 version strings, which the C implementation would choke on, e.g.
7998 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
7999 - Protover parsing was ignoring a 2nd hyphen and everything after
8000 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
8002 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
8003 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
8004 - cd to ${abs_top_builddir}/src/rust before running cargo in
8005 src/test/test_rust.sh. This makes the working directory consistent
8006 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
8008 o Minor bugfixes (single onion services, Tor2web):
8009 - Log a protocol warning when single onion services or Tor2web
8010 clients fail to authenticate direct connections to relays. Fixes
8011 bug 26924; bugfix on 0.2.9.1-alpha.
8013 o Minor bugfixes (test coverage tools):
8014 - Update our "cov-diff" script to handle output from the latest
8015 version of gcov, and to remove extraneous timestamp information
8016 from its output. Fixes bugs 26101 and 26102; bugfix
8019 o Minor bugfixes (testing):
8020 - Disable core dumps in test_bt.sh, to avoid failures in "make
8021 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
8022 - When testing workqueue event-cancellation, make sure that we
8023 actually cancel an event, and that cancel each event with equal
8024 probability. (It was previously possible, though extremely
8025 unlikely, for our event-canceling test not to cancel any events.)
8026 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
8027 - Repeat part of the test in test_client_pick_intro() a number of
8028 times, to give it consistent coverage. Fixes bug 25996; bugfix
8030 - Remove randomness from the hs_common/responsible_hsdirs test, so
8031 that it always takes the same path through the function it tests.
8032 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
8033 - Change the behavior of the "channel/outbound" test so that it
8034 never causes a 10-second rollover for the EWMA circuitmux code.
8035 Previously, this behavior would happen randomly, and result in
8036 fluctuating test coverage. Fixes bug 25994; bugfix
8038 - Use X509_new() to allocate certificates that will be freed later
8039 with X509_free(). Previously, some parts of the unit tests had
8040 used tor_malloc_zero(), which is incorrect, and which caused test
8041 failures on Windows when they were built with extra hardening.
8042 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
8044 - While running the circuit_timeout test, fix the PRNG to a
8045 deterministic AES stream, so that the test coverage from this test
8046 will itself be deterministic. Fixes bug 25995; bugfix
8049 o Minor bugfixes (testing, bootstrap):
8050 - When calculating bootstrap progress, check exit policies and the
8051 exit flag. Previously, Tor would only check the exit flag, which
8052 caused race conditions in small and fast networks like chutney.
8053 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
8055 o Minor bugfixes (testing, chutney):
8056 - When running make test-network-all, use the mixed+hs-v2 network.
8057 (A previous fix to chutney removed v3 onion services from the
8058 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
8059 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
8060 - Before running make test-network-all, delete old logs and test
8061 result files, to avoid spurious failures. Fixes bug 27295; bugfix
8064 o Minor bugfixes (testing, openssl compatibility):
8065 - Our "tortls/cert_matches_key" unit test no longer relies on
8066 OpenSSL internals. Previously, it relied on unsupported OpenSSL
8067 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
8068 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
8070 o Minor bugfixes (v3 onion services):
8071 - Stop sending ed25519 link specifiers in v3 onion service introduce
8072 cells and descriptors, when the rendezvous or introduction point
8073 doesn't support ed25519 link authentication. Fixes bug 26627;
8074 bugfix on 0.3.2.4-alpha.
8076 o Minor bugfixes (vanguards):
8077 - Allow the last hop in a vanguard circuit to be the same as our
8078 first, to prevent the adversary from influencing guard node choice
8079 by choice of last hop. Also prevent the creation of A - B - A
8080 paths, or A - A paths, which are forbidden by relays. Fixes bug
8081 25870; bugfix on 0.3.3.1-alpha.
8083 o Minor bugfixes (Windows, compilation):
8084 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
8085 27185; bugfix on 0.2.2.2-alpha.
8087 o Code simplification and refactoring:
8088 - Remove duplicate code in parse_{c,s}method_line and bootstrap
8089 their functionalities into a single function. Fixes bug 6236;
8090 bugfix on 0.2.3.6-alpha.
8091 - We remove the PortForwarding and PortForwardingHelper options,
8092 related functions, and the port_forwarding tests. These options
8093 were used by the now-deprecated Vidalia to help ordinary users
8094 become Tor relays or bridges. Closes ticket 25409. Patch by
8096 - In order to make the OR and dir checking function in router.c less
8097 confusing we renamed some functions and
8098 consider_testing_reachability() has been split into
8099 router_should_check_reachability() and
8100 router_do_reachability_checks(). Also we improved the documentation
8101 in some functions. Closes ticket 18918.
8102 - Initial work to isolate Libevent usage to a handful of modules in
8103 our codebase, to simplify our call structure, and so that we can
8104 more easily change event loops in the future if needed. Closes
8106 - Introduce a function to call getsockname() and return tor_addr_t,
8107 to save a little complexity throughout the codebase. Closes
8109 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
8110 as hsdir_index is always present. Also, we move hsdir_index_t into
8111 or.h. Closes ticket 23094. Patch by Neel Chauhan.
8112 - Merge functions used for describing nodes and suppress the
8113 functions that do not allocate memory for the output buffer
8114 string. NODE_DESC_BUF_LEN constant and format_node_description()
8115 function cannot be used externally from router.c module anymore.
8116 Closes ticket 25432. Patch by valentecaio.
8117 - Our main loop has been simplified so that all important operations
8118 happen inside events. Previously, some operations had to happen
8119 outside the event loop, to prevent infinite sequences of event
8120 activations. Closes ticket 25374.
8121 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
8122 it in register_intro_circ() and service_intro_point_new(). This
8123 prevents the digest from being re-calculated each time. Closes
8124 ticket 23107. Patch by Neel Chauhan.
8125 - Refactor token-bucket implementations to use a common backend.
8126 Closes ticket 25766.
8127 - Remove extern declaration of stats_n_seconds_working variable from
8128 main, protecting its accesses with get_uptime() and reset_uptime()
8129 functions. Closes ticket 25081, patch by “valentecaio”.
8130 - Remove our previous logic for "cached gettimeofday()" -- our
8131 coarse monotonic timers are fast enough for this purpose, and far
8132 less error-prone. Implements part of ticket 25927.
8133 - Remove the return value for fascist_firewall_choose_address_base(),
8134 and sister functions such as fascist_firewall_choose_address_node()
8135 and fascist_firewall_choose_address_rs(). Also, while we're here,
8136 initialize the ap argument as leaving it uninitialized can pose a
8137 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
8138 - Rename two fields of connection_t struct. timestamp_lastwritten is
8139 renamed to timestamp_last_write_allowed and timestamp_lastread is
8140 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
8142 - Since Tor requires C99, remove our old workaround code for libc
8143 implementations where free(NULL) doesn't work. Closes ticket 24484.
8144 - Use our standard rate-limiting code to deal with excessive
8145 libevent failures, rather than the hand-rolled logic we had
8146 before. Closes ticket 26016.
8147 - We remove the return value of node_get_prim_orport() and
8148 node_get_prim_dirport(), and introduce node_get_prim_orport() in
8149 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
8150 check for a null address. Closes ticket 23873. Patch by
8152 - We switch to should_record_bridge_info() in
8153 geoip_note_client_seen() and options_need_geoip_info() instead of
8154 accessing the configuration values directly. Fixes bug 25290;
8155 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
8157 o Deprecated features:
8158 - As we are not recommending 0.2.5 anymore, we require relays that
8159 once had an ed25519 key associated with their RSA key to always
8160 have that key, instead of allowing them to drop back to a version
8161 that didn't support ed25519. This means they need to use a new RSA
8162 key if they want to downgrade to an older version of tor without
8163 ed25519. Closes ticket 20522.
8166 - Directory authorities will no longer support voting according to
8167 any consensus method before consensus method 25. This keeps
8168 authorities compatible with all authorities running 0.2.9.8 and
8169 later, and does not break any clients or relays. Implements ticket
8170 24378 and proposal 290.
8171 - The PortForwarding and PortForwardingHelper features have been
8172 removed. The reasoning is, given that implementations of NAT
8173 traversal protocols within common consumer grade routers are
8174 frequently buggy, and that the target audience for a NAT punching
8175 feature is a perhaps less-technically-inclined relay operator,
8176 when the helper fails to setup traversal the problems are usually
8177 deep, ugly, and very router specific, making them horrendously
8178 impossible for technical support to reliable assist with, and thus
8179 resulting in frustration all around. Unfortunately, relay
8180 operators who would like to run relays behind NATs will need to
8181 become more familiar with the port forwarding configurations on
8182 their local router. Closes 25409.
8183 - The TestingEnableTbEmptyEvent option has been removed. It was used
8184 in testing simulations to measure how often connection buckets
8185 were emptied, in order to improve our scheduling, but it has not
8186 been actively used in years. Closes ticket 25760.
8187 - The old "round-robin" circuit multiplexer (circuitmux)
8188 implementation has been removed, along with a fairly large set of
8189 code that existed to support it. It has not been the default
8190 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
8191 but it still required an unreasonable amount of memory and CPU.
8192 Closes ticket 25268.
8195 Changes in version 0.3.3.9 - 2018-07-13
8196 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
8197 bridge relays should upgrade.
8199 o Directory authority changes:
8200 - The "Bifroest" bridge authority has been retired; the new bridge
8201 authority is "Serge", and it is operated by George from the
8202 TorBSD project. Closes ticket 26771.
8205 Changes in version 0.3.2.11 - 2018-07-13
8206 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
8207 bridge relays should upgrade. We also take this opportunity to backport
8210 o Directory authority changes:
8211 - The "Bifroest" bridge authority has been retired; the new bridge
8212 authority is "Serge", and it is operated by George from the
8213 TorBSD project. Closes ticket 26771.
8215 o Directory authority changes (backport from 0.3.3.7):
8216 - Add an IPv6 address for the "dannenberg" directory authority.
8217 Closes ticket 26343.
8219 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
8220 - When directory authorities read a zero-byte bandwidth file, they
8221 would previously log a warning with the contents of an
8222 uninitialised buffer. They now log a warning about the empty file
8223 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
8225 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
8226 - Correctly detect when onion services get disabled after HUP. Fixes
8227 bug 25761; bugfix on 0.3.2.1.
8229 o Minor features (sandbox, backport from 0.3.3.4-alpha):
8230 - Explicitly permit the poll() system call when the Linux
8231 seccomp2-based sandbox is enabled: apparently, some versions of
8232 libc use poll() when calling getpwnam(). Closes ticket 25313.
8234 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
8235 - Update the Travis CI configuration to use the stable Rust channel,
8236 now that we have decided to require that. Closes ticket 25714.
8238 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
8239 - Our .travis.yml configuration now includes support for testing the
8240 results of "make distcheck". (It's not uncommon for "make check"
8241 to pass but "make distcheck" to fail.) Closes ticket 25814.
8242 - Our Travis CI configuration now integrates with the Coveralls
8243 coverage analysis tool. Closes ticket 25818.
8245 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
8246 - Add several checks to detect whether Tor relays are uploading
8247 their descriptors without specifying why they regenerated them.
8248 Diagnostic for ticket 25686.
8250 o Minor features (compilation, backport from 0.3.4.4-rc):
8251 - When building Tor, prefer to use Python 3 over Python 2, and more
8252 recent (contemplated) versions over older ones. Closes
8255 o Minor features (geoip):
8256 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
8257 Country database. Closes ticket 26674.
8259 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
8260 - Upon receiving a malformed connected cell, stop processing the
8261 cell immediately. Previously we would mark the connection for
8262 close, but continue processing the cell as if the connection were
8263 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
8265 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
8266 - Allow the nanosleep() system call, which glibc uses to implement
8267 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
8269 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
8270 - When running the hs_ntor_ref.py test, make sure only to pass
8271 strings (rather than "bytes" objects) to the Python subprocess
8272 module. Python 3 on Windows seems to require this. Fixes bug
8273 26535; bugfix on 0.3.1.1-alpha.
8274 - When running the ntor_ref.py test, make sure only to pass strings
8275 (rather than "bytes" objects) to the Python subprocess module.
8276 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
8279 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
8280 - Work around a change in OpenSSL 1.1.1 where return values that
8281 would previously indicate "no password" now indicate an empty
8282 password. Without this workaround, Tor instances running with
8283 OpenSSL 1.1.1 would accept descriptors that other Tor instances
8284 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
8286 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
8287 - Document that the PerConnBW{Rate,Burst} options will fall back to
8288 their corresponding consensus parameters only if those parameters
8289 are set. Previously we had claimed that these values would always
8290 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
8292 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
8293 - Fix a compilation warning on some versions of GCC when building
8294 code that calls routerinfo_get_my_routerinfo() twice, assuming
8295 that the second call will succeed if the first one did. Fixes bug
8296 26269; bugfix on 0.2.8.2-alpha.
8298 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
8299 - Don't consider Tor running as a client if the ControlPort is open,
8300 but no actual client ports are open. Fixes bug 26062; bugfix
8303 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
8304 - Prevent a possible out-of-bounds smartlist read in
8305 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
8307 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
8308 - Fix a very unlikely (impossible, we believe) null pointer
8309 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
8310 Coverity; this is CID 1430932.
8312 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
8313 - Fix a memory leak when a v3 onion service is configured and gets a
8314 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
8315 - When parsing the descriptor signature, look for the token plus an
8316 extra white-space at the end. This is more correct but also will
8317 allow us to support new fields that might start with "signature".
8318 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
8320 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
8321 - Relays now correctly block attempts to re-extend to the previous
8322 relay by Ed25519 identity. Previously they would warn in this
8323 case, but not actually reject the attempt. Fixes bug 26158; bugfix
8326 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
8327 - Avoid a crash when running with DirPort set but ORPort turned off.
8328 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
8330 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
8331 - Silence unused-const-variable warnings in zstd.h with some GCC
8332 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
8334 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
8335 - Avoid intermittent test failures due to a test that had relied on
8336 onion service introduction point creation finishing within 5
8337 seconds of real clock time. Fixes bug 25450; bugfix
8340 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
8341 - Fix a C99 compliance issue in our configuration script that caused
8342 compilation issues when compiling Tor with certain versions of
8343 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
8345 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
8346 - Fix a number of small memory leaks identified by coverity. Fixes
8347 bug 26467; bugfix on numerous Tor versions.
8349 o Code simplification and refactoring (backport from 0.3.3.5-rc):
8350 - Move the list of default directory authorities to its own file.
8351 Closes ticket 24854. Patch by "beastr0".
8354 Changes in version 0.2.9.16 - 2018-07-13
8355 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
8356 bridge relays should upgrade. We also take this opportunity to backport
8359 o Directory authority changes:
8360 - The "Bifroest" bridge authority has been retired; the new bridge
8361 authority is "Serge", and it is operated by George from the
8362 TorBSD project. Closes ticket 26771.
8364 o Directory authority changes (backport from 0.3.3.7):
8365 - Add an IPv6 address for the "dannenberg" directory authority.
8366 Closes ticket 26343.
8368 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
8369 - When directory authorities read a zero-byte bandwidth file, they
8370 would previously log a warning with the contents of an
8371 uninitialised buffer. They now log a warning about the empty file
8372 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
8374 o Minor features (sandbox, backport from 0.3.3.4-alpha):
8375 - Explicitly permit the poll() system call when the Linux
8376 seccomp2-based sandbox is enabled: apparently, some versions of
8377 libc use poll() when calling getpwnam(). Closes ticket 25313.
8379 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
8380 - Our .travis.yml configuration now includes support for testing the
8381 results of "make distcheck". (It's not uncommon for "make check"
8382 to pass but "make distcheck" to fail.) Closes ticket 25814.
8383 - Our Travis CI configuration now integrates with the Coveralls
8384 coverage analysis tool. Closes ticket 25818.
8386 o Minor features (compilation, backport from 0.3.4.4-rc):
8387 - When building Tor, prefer to use Python 3 over Python 2, and more
8388 recent (contemplated) versions over older ones. Closes
8391 o Minor features (geoip):
8392 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
8393 Country database. Closes ticket 26674.
8395 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
8396 - Upon receiving a malformed connected cell, stop processing the
8397 cell immediately. Previously we would mark the connection for
8398 close, but continue processing the cell as if the connection were
8399 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
8401 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
8402 - Allow the nanosleep() system call, which glibc uses to implement
8403 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
8405 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
8406 - When running the ntor_ref.py test, make sure only to pass strings
8407 (rather than "bytes" objects) to the Python subprocess module.
8408 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
8411 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
8412 - Work around a change in OpenSSL 1.1.1 where return values that
8413 would previously indicate "no password" now indicate an empty
8414 password. Without this workaround, Tor instances running with
8415 OpenSSL 1.1.1 would accept descriptors that other Tor instances
8416 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
8418 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
8419 - Fix a compilation warning on some versions of GCC when building
8420 code that calls routerinfo_get_my_routerinfo() twice, assuming
8421 that the second call will succeed if the first one did. Fixes bug
8422 26269; bugfix on 0.2.8.2-alpha.
8424 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
8425 - Don't consider Tor running as a client if the ControlPort is open,
8426 but no actual client ports are open. Fixes bug 26062; bugfix
8429 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
8430 - Prevent a possible out-of-bounds smartlist read in
8431 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
8433 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
8434 - Fix a very unlikely (impossible, we believe) null pointer
8435 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
8436 Coverity; this is CID 1430932.
8438 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
8439 - Fix a number of small memory leaks identified by coverity. Fixes
8440 bug 26467; bugfix on numerous Tor versions.
8442 o Code simplification and refactoring (backport from 0.3.3.5-rc):
8443 - Move the list of default directory authorities to its own file.
8444 Closes ticket 24854. Patch by "beastr0".
8447 Changes in version 0.3.3.8 - 2018-07-09
8448 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
8449 fixes for a memory leak affecting directory authorities.
8451 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
8452 - Stop leaking memory on directory authorities when planning to
8453 vote. This bug was crashing authorities by exhausting their
8454 memory. Fixes bug 26435; bugfix on 0.3.3.6.
8456 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
8457 - Make sure that failing tests in Rust will actually cause the build
8458 to fail: previously, they were ignored. Fixes bug 26258; bugfix
8461 o Minor features (compilation, backport from 0.3.4.4-rc):
8462 - When building Tor, prefer to use Python 3 over Python 2, and more
8463 recent (contemplated) versions over older ones. Closes
8466 o Minor features (geoip):
8467 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
8468 Country database. Closes ticket 26674.
8470 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
8471 - Add several checks to detect whether Tor relays are uploading
8472 their descriptors without specifying why they regenerated them.
8473 Diagnostic for ticket 25686.
8475 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
8476 - Don't count path selection failures as circuit build failures.
8477 This change should eliminate cases where Tor blames its guard or
8478 the network for situations like insufficient microdescriptors
8479 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
8482 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
8483 - Fix a compilation warning on some versions of GCC when building
8484 code that calls routerinfo_get_my_routerinfo() twice, assuming
8485 that the second call will succeed if the first one did. Fixes bug
8486 26269; bugfix on 0.2.8.2-alpha.
8488 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
8489 - Handle the HSADDRESS= argument to the HSPOST command properly.
8490 (Previously, this argument was misparsed and thus ignored.) Fixes
8491 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
8493 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
8494 - Fix a number of small memory leaks identified by coverity. Fixes
8495 bug 26467; bugfix on numerous Tor versions.
8497 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
8498 - Relays now correctly block attempts to re-extend to the previous
8499 relay by Ed25519 identity. Previously they would warn in this
8500 case, but not actually reject the attempt. Fixes bug 26158; bugfix
8503 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
8504 - When shutting down, Tor now clears all the flags in the control.c
8505 module. This should prevent a bug where authentication cookies are
8506 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
8508 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
8509 - When running the hs_ntor_ref.py test, make sure only to pass
8510 strings (rather than "bytes" objects) to the Python subprocess
8511 module. Python 3 on Windows seems to require this. Fixes bug
8512 26535; bugfix on 0.3.1.1-alpha.
8513 - When running the ntor_ref.py test, make sure only to pass strings
8514 (rather than "bytes" objects) to the Python subprocess module.
8515 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
8519 Changes in version 0.3.3.7 - 2018-06-12
8520 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
8521 fixes for bugs affecting compatibility and stability.
8523 o Directory authority changes:
8524 - Add an IPv6 address for the "dannenberg" directory authority.
8525 Closes ticket 26343.
8527 o Minor features (geoip):
8528 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
8529 Country database. Closes ticket 26351.
8531 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
8532 - Work around a change in OpenSSL 1.1.1 where return values that
8533 would previously indicate "no password" now indicate an empty
8534 password. Without this workaround, Tor instances running with
8535 OpenSSL 1.1.1 would accept descriptors that other Tor instances
8536 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
8538 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
8539 - Silence unused-const-variable warnings in zstd.h with some GCC
8540 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
8542 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
8543 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
8544 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
8545 miscounting the total number of circuits for these field values.)
8546 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
8548 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
8549 - Prevent a possible out-of-bounds smartlist read in
8550 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
8552 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
8553 - Only select relays when they have the descriptors we prefer to use
8554 for them. This change fixes a bug where we could select a relay
8555 because it had _some_ descriptor, but reject it later with a
8556 nonfatal assertion error because it didn't have the exact one we
8557 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
8560 Changes in version 0.3.3.6 - 2018-05-22
8561 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
8562 backports several important fixes from the 0.3.4.1-alpha.
8564 The Tor 0.3.3 series includes controller support and other
8565 improvements for v3 onion services, official support for embedding Tor
8566 within other applications, and our first non-trivial module written in
8567 the Rust programming language. (Rust is still not enabled by default
8568 when building Tor.) And as usual, there are numerous other smaller
8569 bugfixes, features, and improvements.
8571 Below are the changes since 0.3.2.10. For a list of only the changes
8572 since 0.3.3.5-rc, see the ChangeLog file.
8574 o New system requirements:
8575 - When built with Rust, Tor now depends on version 0.2.39 of the
8576 libc crate. Closes tickets 25310 and 25664.
8578 o Major features (embedding):
8579 - There is now a documented stable API for programs that need to
8580 embed Tor. See tor_api.h for full documentation and known bugs.
8581 Closes ticket 23684.
8582 - Tor now has support for restarting in the same process.
8583 Controllers that run Tor using the "tor_api.h" interface can now
8584 restart Tor after Tor has exited. This support is incomplete,
8585 however: we fixed crash bugs that prevented it from working at
8586 all, but many bugs probably remain, including a possibility of
8587 security issues. Implements ticket 24581.
8589 o Major features (IPv6, directory documents):
8590 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
8591 consensus. This information makes it easier for IPv6 clients to
8592 bootstrap and choose reachable entry guards. Implements
8594 - Add consensus method 28, which removes IPv6 ORPorts from
8595 microdescriptors. Now that the consensus contains IPv6 ORPorts,
8596 they are redundant in microdescs. This change will be used by Tor
8597 clients on 0.2.8.x and later. (That is to say, with all Tor
8598 clients that have IPv6 bootstrap and guard support.) Implements
8600 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
8601 set by different numbers of authorities. Fixes 23870
8604 o Major features (onion service v3, control port):
8605 - The control port now supports commands and events for v3 onion
8606 services. It is now possible to create ephemeral v3 services using
8607 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
8608 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
8609 DEL_ONION) have been extended to support v3 onion services. Closes
8610 ticket 20699; implements proposal 284.
8612 o Major features (onion services):
8613 - Provide torrc options to pin the second and third hops of onion
8614 service circuits to a list of nodes. The option HSLayer2Guards
8615 pins the second hop, and the option HSLayer3Guards pins the third
8616 hop. These options are for use in conjunction with experiments
8617 with "vanguards" for preventing guard enumeration attacks. Closes
8619 - When v3 onion service clients send introduce cells, they now
8620 include the IPv6 address of the rendezvous point, if it has one.
8621 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
8622 in future Tor versions, IPv6-only v3 single onion services will be
8623 able to use IPv6 addresses to connect directly to the rendezvous
8624 point. Closes ticket 23577. Patch by Neel Chauhan.
8626 o Major features (relay):
8627 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
8628 operator to use a more reasonable ("reduced") exit policy, rather
8629 than the default one. If you want to run an exit node without
8630 thinking too hard about which ports to allow, this one is for you.
8631 Closes ticket 13605. Patch from Neel Chauhan.
8633 o Major features (rust, portability, experimental):
8634 - Tor now ships with an optional implementation of one of its
8635 smaller modules (protover.c) in the Rust programming language. To
8636 try it out, install a Rust build environment, and configure Tor
8637 with "--enable-rust --enable-cargo-online-mode". This should not
8638 cause any user-visible changes, but should help us gain more
8639 experience with Rust, and plan future Rust integration work.
8640 Implementation by Chelsea Komlo. Closes ticket 22840.
8642 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
8643 - When directory authorities read a zero-byte bandwidth file, they
8644 would previously log a warning with the contents of an
8645 uninitialised buffer. They now log a warning about the empty file
8646 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
8648 o Major bugfixes (security, directory authority, denial-of-service):
8649 - Fix a bug that could have allowed an attacker to force a directory
8650 authority to use up all its RAM by passing it a maliciously
8651 crafted protocol versions string. Fixes bug 25517; bugfix on
8652 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
8654 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
8655 - Avoid a rare assertion failure in the circuit build timeout code
8656 if we fail to allow any circuits to actually complete. Fixes bug
8657 25733; bugfix on 0.2.2.2-alpha.
8659 o Major bugfixes (netflow padding):
8660 - Stop adding unneeded channel padding right after we finish
8661 flushing to a connection that has been trying to flush for many
8662 seconds. Instead, treat all partial or complete flushes as
8663 activity on the channel, which will defer the time until we need
8664 to add padding. This fix should resolve confusing and scary log
8665 messages like "Channel padding timeout scheduled 221453ms in the
8666 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
8668 o Major bugfixes (networking):
8669 - Tor will no longer reject IPv6 address strings from Tor Browser
8670 when they are passed as hostnames in SOCKS5 requests. Fixes bug
8671 25036, bugfix on Tor 0.3.1.2.
8673 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
8674 - Correctly detect when onion services get disabled after HUP. Fixes
8675 bug 25761; bugfix on 0.3.2.1.
8677 o Major bugfixes (performance, load balancing):
8678 - Directory authorities no longer vote in favor of the Guard flag
8679 for relays without directory support. Starting in Tor
8680 0.3.0.1-alpha, clients have been avoiding using such relays in the
8681 Guard position, leading to increasingly broken load balancing for
8682 the 5%-or-so of Guards that don't advertise directory support.
8683 Fixes bug 22310; bugfix on 0.3.0.6.
8685 o Major bugfixes (relay):
8686 - If we have failed to connect to a relay and received a connection
8687 refused, timeout, or similar error (at the TCP level), do not try
8688 that same address/port again for 60 seconds after the failure has
8689 occurred. Fixes bug 24767; bugfix on 0.0.6.
8691 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
8692 - Impose a limit on circuit cell queue size. The limit can be
8693 controlled by a consensus parameter. Fixes bug 25226; bugfix
8696 o Minor features (cleanup):
8697 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
8698 when it stops. Closes ticket 23271.
8700 o Minor features (compatibility, backport from 0.3.4.1-alpha):
8701 - Avoid some compilation warnings with recent versions of LibreSSL.
8702 Closes ticket 26006.
8704 o Minor features (config options):
8705 - Change the way the default value for MaxMemInQueues is calculated.
8706 We now use 40% of the hardware RAM if the system has 8 GB RAM or
8707 more. Otherwise we use the former value of 75%. Closes
8710 o Minor features (continuous integration):
8711 - Update the Travis CI configuration to use the stable Rust channel,
8712 now that we have decided to require that. Closes ticket 25714.
8714 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
8715 - Our .travis.yml configuration now includes support for testing the
8716 results of "make distcheck". (It's not uncommon for "make check"
8717 to pass but "make distcheck" to fail.) Closes ticket 25814.
8718 - Our Travis CI configuration now integrates with the Coveralls
8719 coverage analysis tool. Closes ticket 25818.
8721 o Minor features (defensive programming):
8722 - Most of the functions in Tor that free objects have been replaced
8723 with macros that free the objects and set the corresponding
8724 pointers to NULL. This change should help prevent a large class of
8725 dangling pointer bugs. Closes ticket 24337.
8726 - Where possible, the tor_free() macro now only evaluates its input
8727 once. Part of ticket 24337.
8728 - Check that microdesc ed25519 ids are non-zero in
8729 node_get_ed25519_id() before returning them. Implements ticket
8730 24001, patch by "aruna1234".
8732 o Minor features (directory authority):
8733 - When directory authorities are unable to add signatures to a
8734 pending consensus, log the reason why. Closes ticket 24849.
8736 o Minor features (embedding):
8737 - Tor can now start with a preauthenticated control connection
8738 created by the process that launched it. This feature is meant for
8739 use by programs that want to launch and manage a Tor process
8740 without allowing other programs to manage it as well. For more
8741 information, see the __OwningControllerFD option documented in
8742 control-spec.txt. Closes ticket 23900.
8743 - On most errors that would cause Tor to exit, it now tries to
8744 return from the tor_main() function, rather than calling the
8745 system exit() function. Most users won't notice a difference here,
8746 but it should be significant for programs that run Tor inside a
8747 separate thread: they should now be able to survive Tor's exit
8748 conditions rather than having Tor shut down the entire process.
8749 Closes ticket 23848.
8750 - Applications that want to embed Tor can now tell Tor not to
8751 register any of its own POSIX signal handlers, using the
8752 __DisableSignalHandlers option. Closes ticket 24588.
8754 o Minor features (fallback directory list):
8755 - Avoid selecting fallbacks that change their IP addresses too
8756 often. Select more fallbacks by ignoring the Guard flag, and
8757 allowing lower cutoffs for the Running and V2Dir flags. Also allow
8758 a lower bandwidth, and a higher number of fallbacks per operator
8759 (5% of the list). Implements ticket 24785.
8760 - Update the fallback whitelist and blacklist based on opt-ins and
8761 relay changes. Closes tickets 22321, 24678, 22527, 24135,
8764 o Minor features (fallback directory mirror configuration):
8765 - Add a nickname to each fallback in a C comment. This makes it
8766 easier for operators to find their relays, and allows stem to use
8767 nicknames to identify fallbacks. Implements ticket 24600.
8768 - Add a type and version header to the fallback directory mirror
8769 file. Also add a delimiter to the end of each fallback entry. This
8770 helps external parsers like stem and Relay Search. Implements
8772 - Add an extrainfo cache flag for each fallback in a C comment. This
8773 allows stem to use fallbacks to fetch extra-info documents, rather
8774 than using authorities. Implements ticket 22759.
8775 - Add the generateFallbackDirLine.py script for automatically
8776 generating fallback directory mirror lines from relay fingerprints.
8777 No more typos! Add the lookupFallbackDirContact.py script for
8778 automatically looking up operator contact info from relay
8779 fingerprints. Implements ticket 24706, patch by teor and atagar.
8780 - Reject any fallback directory mirror that serves an expired
8781 consensus. Implements ticket 20942, patch by "minik".
8782 - Remove commas and equals signs from external string inputs to the
8783 fallback list. This avoids format confusion attacks. Implements
8785 - Remove the "weight=10" line from fallback directory mirror
8786 entries. Ticket 24681 will maintain the current fallback weights
8787 by changing Tor's default fallback weight to 10. Implements
8789 - Stop logging excessive information about fallback netblocks.
8790 Implements ticket 24791.
8792 o Minor features (forward-compatibility):
8793 - If a relay supports some link authentication protocol that we do
8794 not recognize, then include that relay's ed25519 key when telling
8795 other relays to extend to it. Previously, we treated future
8796 versions as if they were too old to support ed25519 link
8797 authentication. Closes ticket 20895.
8799 o Minor features (geoip):
8800 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
8801 database. Closes ticket 26104.
8803 o Minor features (heartbeat):
8804 - Add onion service information to our heartbeat logs, displaying
8805 stats about the activity of configured onion services. Closes
8808 o Minor features (instrumentation, development):
8809 - Add the MainloopStats option to allow developers to get
8810 instrumentation information from the main event loop via the
8811 heartbeat messages. We hope to use this to improve Tor's behavior
8812 when it's trying to sleep. Closes ticket 24605.
8814 o Minor features (IPv6):
8815 - Make IPv6-only clients wait for microdescs for relays, even if we
8816 were previously using descriptors (or were using them as a bridge)
8817 and have a cached descriptor for them. Implements ticket 23827.
8818 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
8819 them, rather than waiting to download microdescriptors. Implements
8822 o Minor features (log messages):
8823 - Improve log message in the out-of-memory handler to include
8824 information about memory usage from the different compression
8825 backends. Closes ticket 25372.
8826 - Improve a warning message that happens when we fail to re-parse an
8827 old router because of an expired certificate. Closes ticket 20020.
8828 - Make the log more quantitative when we hit MaxMemInQueues
8829 threshold exposing some values. Closes ticket 24501.
8831 o Minor features (logging):
8832 - Clarify the log messages produced when getrandom() or a related
8833 entropy-generation mechanism gives an error. Closes ticket 25120.
8834 - Added support for the Android logging subsystem. Closes
8837 o Minor features (performance):
8838 - Support predictive circuit building for onion service circuits
8839 with multiple layers of guards. Closes ticket 23101.
8840 - Use stdatomic.h where available, rather than mutexes, to implement
8841 atomic_counter_t. Closes ticket 23953.
8843 o Minor features (performance, 32-bit):
8844 - Improve performance on 32-bit systems by avoiding 64-bit division
8845 when calculating the timestamp in milliseconds for channel padding
8846 computations. Implements ticket 24613.
8847 - Improve performance on 32-bit systems by avoiding 64-bit division
8848 when timestamping cells and buffer chunks for OOM calculations.
8849 Implements ticket 24374.
8851 o Minor features (performance, OSX, iOS):
8852 - Use the mach_approximate_time() function (when available) to
8853 implement coarse monotonic time. Having a coarse time function
8854 should avoid a large number of system calls, and improve
8855 performance slightly, especially under load. Closes ticket 24427.
8857 o Minor features (performance, windows):
8858 - Improve performance on Windows Vista and Windows 7 by adjusting
8859 TCP send window size according to the recommendation from
8860 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
8863 o Minor features (sandbox):
8864 - Explicitly permit the poll() system call when the Linux
8865 seccomp2-based sandbox is enabled: apparently, some versions of
8866 libc use poll() when calling getpwnam(). Closes ticket 25313.
8868 o Minor features (storage, configuration):
8869 - Users can store cached directory documents somewhere other than
8870 the DataDirectory by using the CacheDirectory option. Similarly,
8871 the storage location for relay's keys can be overridden with the
8872 KeyDirectory option. Closes ticket 22703.
8874 o Minor features (testing):
8875 - Add a "make test-rust" target to run the rust tests only. Closes
8878 o Minor features (testing, debugging, embedding):
8879 - For development purposes, Tor now has a mode in which it runs for
8880 a few seconds, then stops, and starts again without exiting the
8881 process. This mode is meant to help us debug various issues with
8882 ticket 23847. To use this feature, compile with
8883 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
8884 environment variable. This is expected to crash a lot, and is
8885 really meant for developers only. It will likely be removed in a
8886 future release. Implements ticket 24583.
8888 o Minor bugfixes (build, rust):
8889 - Fix output of autoconf checks to display success messages for Rust
8890 dependencies and a suitable rustc compiler version. Fixes bug
8891 24612; bugfix on 0.3.1.3-alpha.
8892 - Don't pass the --quiet option to cargo: it seems to suppress some
8893 errors, which is not what we want to do when building. Fixes bug
8894 24518; bugfix on 0.3.1.7.
8895 - Build correctly when building from outside Tor's source tree with
8896 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
8899 o Minor bugfixes (C correctness):
8900 - Fix a very unlikely (impossible, we believe) null pointer
8901 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
8902 Coverity; this is CID 1430932.
8904 o Minor bugfixes (channel, client):
8905 - Better identify client connection when reporting to the geoip
8906 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
8908 o Minor bugfixes (circuit, cannibalization):
8909 - Don't cannibalize preemptively-built circuits if we no longer
8910 recognize their first hop. This situation can happen if our Guard
8911 relay went off the consensus after the circuit was created. Fixes
8912 bug 24469; bugfix on 0.0.6.
8914 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
8915 - Don't consider Tor running as a client if the ControlPort is open,
8916 but no actual client ports are open. Fixes bug 26062; bugfix
8919 o Minor bugfixes (compilation):
8920 - Fix a C99 compliance issue in our configuration script that caused
8921 compilation issues when compiling Tor with certain versions of
8922 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
8924 o Minor bugfixes (controller):
8925 - Restore the correct operation of the RESOLVE command, which had
8926 been broken since we added the ability to enable/disable DNS on
8927 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
8928 - Avoid a (nonfatal) assertion failure when extending a one-hop
8929 circuit from the controller to become a multihop circuit. Fixes
8930 bug 24903; bugfix on 0.2.5.2-alpha.
8932 o Minor bugfixes (correctness):
8933 - Remove a nonworking, unnecessary check to see whether a circuit
8934 hop's identity digest was set when the circuit failed. Fixes bug
8935 24927; bugfix on 0.2.4.4-alpha.
8937 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
8938 - Upon receiving a malformed connected cell, stop processing the
8939 cell immediately. Previously we would mark the connection for
8940 close, but continue processing the cell as if the connection were
8941 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
8943 o Minor bugfixes (directory authorities, IPv6):
8944 - When creating a routerstatus (vote) from a routerinfo (descriptor),
8945 set the IPv6 address to the unspecified IPv6 address, and
8946 explicitly initialize the port to zero. Fixes bug 24488; bugfix
8949 o Minor bugfixes (documentation):
8950 - Document that the PerConnBW{Rate,Burst} options will fall back to
8951 their corresponding consensus parameters only if those parameters
8952 are set. Previously we had claimed that these values would always
8953 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
8955 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
8956 - Stop saying in the manual that clients cache ipv4 dns answers from
8957 exit relays. We haven't used them since 0.2.6.3-alpha, and in
8958 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
8959 we forgot to say so in the man page. Fixes bug 26052; bugfix
8962 o Minor bugfixes (exit relay DNS retries):
8963 - Re-attempt timed-out DNS queries 3 times before failure, since our
8964 timeout is 5 seconds for them, but clients wait 10-15. Also allow
8965 slightly more timeouts per resolver when an exit has multiple
8966 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
8968 o Minor bugfixes (fallback directory mirrors):
8969 - Make updateFallbackDirs.py search harder for python. (Some OSs
8970 don't put it in /usr/bin.) Fixes bug 24708; bugfix
8973 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
8974 - When hibernating, close connections normally and allow them to
8975 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
8977 - Do not attempt to launch self-reachability tests when entering
8978 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
8979 - Resolve several bugs related to descriptor fetching on bridge
8980 clients with bandwidth accounting enabled. (This combination is
8981 not recommended!) Fixes a case of bug 12062; bugfix
8983 - When hibernating, do not attempt to launch DNS checks. Fixes a
8984 case of bug 12062; bugfix on 0.1.2.2-alpha.
8985 - When hibernating, do not try to upload or download descriptors.
8986 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
8988 o Minor bugfixes (IPv6, bridges):
8989 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
8990 bugfix on 0.2.8.2-alpha.
8991 - Tor now sets IPv6 address in the routerstatus as well as in the
8992 router descriptors when updating addresses for a bridge. Closes
8993 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
8995 o Minor bugfixes (Linux seccomp2 sandbox):
8996 - When running with the sandbox enabled, reload configuration files
8997 correctly even when %include was used. Previously we would crash.
8998 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
9000 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
9001 - Allow the nanosleep() system call, which glibc uses to implement
9002 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
9004 o Minor bugfixes (logging):
9005 - Fix a (mostly harmless) race condition when invoking
9006 LOG_PROTOCOL_WARN message from a subthread while the torrc options
9007 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
9009 o Minor bugfixes (man page, SocksPort):
9010 - Remove dead code from the old "SocksSocket" option, and rename
9011 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old
9012 option still works, but is deprecated. Fixes bug 24343; bugfix
9015 o Minor bugfixes (memory leaks):
9016 - Avoid possible at-exit memory leaks related to use of Libevent's
9017 event_base_once() function. (This function tends to leak memory if
9018 the event_base is closed before the event fires.) Fixes bug 24584;
9019 bugfix on 0.2.8.1-alpha.
9020 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
9023 o Minor bugfixes (network IPv6 test):
9024 - Tor's test scripts now check if "ping -6 ::1" works when the user
9025 runs "make test-network-all". Fixes bug 24677; bugfix on
9026 0.2.9.3-alpha. Patch by "ffmancera".
9028 o Minor bugfixes (networking):
9029 - string_is_valid_hostname() will not consider IP strings to be
9030 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
9032 o Minor bugfixes (onion service v3):
9033 - Avoid an assertion failure when the next onion service descriptor
9034 rotation type is out of sync with the consensus's valid-after
9035 time. Instead, log a warning message with extra information, so we
9036 can better hunt down the cause of this assertion. Fixes bug 25306;
9037 bugfix on 0.3.2.1-alpha.
9039 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
9040 - Fix a memory leak when a v3 onion service is configured and gets a
9041 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
9042 - When parsing the descriptor signature, look for the token plus an
9043 extra white-space at the end. This is more correct but also will
9044 allow us to support new fields that might start with "signature".
9045 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
9047 o Minor bugfixes (onion services):
9048 - If we are configured to offer a single onion service, don't log
9049 long-term established one hop rendezvous points in the heartbeat.
9050 Fixes bug 25116; bugfix on 0.2.9.6-rc.
9052 o Minor bugfixes (performance):
9053 - Reduce the number of circuits that will be opened at once during
9054 the circuit build timeout phase. This is done by increasing the
9055 idle timeout to 3 minutes, and lowering the maximum number of
9056 concurrent learning circuits to 10. Fixes bug 24769; bugfix
9058 - Avoid calling protocol_list_supports_protocol() from inside tight
9059 loops when running with cached routerinfo_t objects. Instead,
9060 summarize the relevant protocols as flags in the routerinfo_t, as
9061 we do for routerstatus_t objects. This change simplifies our code
9062 a little, and saves a large amount of short-term memory allocation
9063 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
9065 o Minor bugfixes (performance, timeouts):
9066 - Consider circuits for timeout as soon as they complete a hop. This
9067 is more accurate than applying the timeout in
9068 circuit_expire_building() because that function is only called
9069 once per second, which is now too slow for typical timeouts on the
9070 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
9071 - Use onion service circuits (and other circuits longer than 3 hops)
9072 to calculate a circuit build timeout. Previously, Tor only
9073 calculated its build timeout based on circuits that planned to be
9074 exactly 3 hops long. With this change, we include measurements
9075 from all circuits at the point where they complete their third
9076 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
9078 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
9079 - Avoid a crash when running with DirPort set but ORPort turned off.
9080 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
9082 o Minor bugfixes (Rust FFI):
9083 - Fix a minor memory leak which would happen whenever the C code
9084 would call the Rust implementation of
9085 protover_get_supported_protocols(). This was due to the C version
9086 returning a static string, whereas the Rust version newly allocated
9087 a CString to pass across the FFI boundary. Consequently, the C
9088 code was not expecting to need to free() what it was given. Fixes
9089 bug 25127; bugfix on 0.3.2.1-alpha.
9091 o Minor bugfixes (spelling):
9092 - Use the "misspell" tool to detect and fix typos throughout the
9093 source code. Fixes bug 23650; bugfix on various versions of Tor.
9094 Patch from Deepesh Pathak.
9096 o Minor bugfixes (testing):
9097 - Avoid intermittent test failures due to a test that had relied on
9098 onion service introduction point creation finishing within 5
9099 seconds of real clock time. Fixes bug 25450; bugfix
9101 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
9102 bugfix on 0.2.3.1-alpha.
9104 o Minor bugfixes (unit test, monotonic time):
9105 - Increase a constant (1msec to 10msec) in the monotonic time test
9106 that makes sure the nsec/usec/msec times read are synchronized.
9107 This change was needed to accommodate slow systems like armel or
9108 when the clock_gettime() is not a VDSO on the running kernel.
9109 Fixes bug 25113; bugfix on 0.2.9.1.
9111 o Code simplification and refactoring:
9112 - Move the list of default directory authorities to its own file.
9113 Closes ticket 24854. Patch by "beastr0".
9114 - Remove the old (deterministic) directory retry logic entirely:
9115 We've used exponential backoff exclusively for some time. Closes
9117 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
9119 - Remove a series of counters used to track circuit extend attempts
9120 and connection status but that in reality we aren't using for
9121 anything other than stats logged by a SIGUSR1 signal. Closes
9123 - Remove /usr/athena from search path in configure.ac. Closes
9125 - Remove duplicate code in node_has_curve25519_onion_key() and
9126 node_get_curve25519_onion_key(), and add a check for a zero
9127 microdesc curve25519 onion key. Closes ticket 23966, patch by
9128 "aruna1234" and teor.
9129 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
9130 memory allocations with large numbers of OR connections (e.g.
9131 relays). Closes ticket 24119.
9132 - Separate the function that deletes ephemeral files when Tor
9134 - Small changes to Tor's buf_t API to make it suitable for use as a
9135 general-purpose safe string constructor. Closes ticket 22342.
9136 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
9137 avoid source code identifier confusion. Closes ticket 24467.
9138 - The tor_git_revision[] constant no longer needs to be redeclared
9139 by everything that links against the rest of Tor. Done as part of
9140 ticket 23845, to simplify our external API.
9141 - We make extend_info_from_node() use node_get_curve25519_onion_key()
9142 introduced in ticket 23577 to access the curve25519 public keys
9143 rather than accessing it directly. Closes ticket 23760. Patch by
9145 - Add a function to log channels' scheduler state changes to aid
9146 debugging efforts. Closes ticket 24531.
9149 - Improved the documentation of AccountingStart parameter. Closes
9151 - Update the documentation for "Log" to include the current list of
9152 logging domains. Closes ticket 25378.
9153 - Add documentation on how to build tor with Rust dependencies
9154 without having to be online. Closes ticket 22907; bugfix
9156 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
9157 traffic. Closes ticket 24318.
9158 - Document that OutboundBindAddress doesn't apply to DNS requests.
9159 Closes ticket 22145. Patch from Aruna Maurya.
9161 o Code simplification and refactoring (channels):
9162 - Remove the incoming and outgoing channel queues. These were never
9163 used, but still took up a step in our fast path.
9164 - The majority of the channel unit tests have been rewritten and the
9165 code coverage has now been raised to 83.6% for channel.c. Closes
9167 - Remove other dead code from the channel subsystem: All together,
9168 this cleanup has removed more than 1500 lines of code overall and
9169 adding very little except for unit test.
9171 o Code simplification and refactoring (circuit rendezvous):
9172 - Split the client-side rendezvous circuit lookup into two
9173 functions: one that returns only established circuits and another
9174 that returns all kinds of circuits. Closes ticket 23459.
9176 o Code simplification and refactoring (controller):
9177 - Make most of the variables in networkstatus_getinfo_by_purpose()
9178 const. Implements ticket 24489.
9180 o Documentation (backport from 0.3.4.1-alpha):
9181 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
9182 ticket 25857. Patch from "CTassisF".
9184 o Documentation (man page):
9185 - The HiddenServiceVersion torrc option accepts only one number:
9186 either version 2 or 3. Closes ticket 25026; bugfix
9189 o Documentation (manpage, denial of service):
9190 - Provide more detail about the denial-of-service options, by
9191 listing each mitigation and explaining how they relate. Closes
9195 Changes in version 0.3.1.10 - 2018-03-03
9196 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
9199 It includes an important security fix for a remote crash attack
9200 against directory authorities, tracked as TROVE-2018-001.
9202 This release also backports our new system for improved resistance to
9203 denial-of-service attacks against relays.
9205 This release also fixes several minor bugs and annoyances from
9208 All directory authorities should upgrade to one of the versions
9209 released today. Relays running 0.3.1.x may wish to update to one of
9210 the versions released today, for the DoS mitigations.
9212 Please note: according to our release calendar, Tor 0.3.1 will no
9213 longer be supported after 1 July 2018. If you will be running Tor
9214 after that date, you should make sure to plan to upgrade to the latest
9215 stable version, or downgrade to 0.2.9 (which will receive long-term
9218 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
9219 - Fix a protocol-list handling bug that could be used to remotely crash
9220 directory authorities with a null-pointer exception. Fixes bug 25074;
9221 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
9224 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
9225 - Give relays some defenses against the recent network overload. We
9226 start with three defenses (default parameters in parentheses).
9227 First: if a single client address makes too many concurrent
9228 connections (>100), hang up on further connections. Second: if a
9229 single client address makes circuits too quickly (more than 3 per
9230 second, with an allowed burst of 90) while also having too many
9231 connections open (3), refuse new create cells for the next while
9232 (1-2 hours). Third: if a client asks to establish a rendezvous
9233 point to you directly, ignore the request. These defenses can be
9234 manually controlled by new torrc options, but relays will also
9235 take guidance from consensus parameters, so there's no need to
9236 configure anything manually. Implements ticket 24902.
9238 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
9239 - Update the sandbox rules so that they should now work correctly
9240 with Glibc 2.26. Closes ticket 24315.
9242 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
9243 - Fix an "off by 2" error in counting rendezvous failures on the
9244 onion service side. While we thought we would stop the rendezvous
9245 attempt after one failed circuit, we were actually making three
9246 circuit attempts before giving up. Now switch to a default of 2,
9247 and allow the consensus parameter "hs_service_max_rdv_failures" to
9248 override. Fixes bug 24895; bugfix on 0.0.6.
9250 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
9251 - Add Link protocol version 5 to the supported protocols list. Fixes
9252 bug 25070; bugfix on 0.3.1.1-alpha.
9254 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
9255 - Fix a set of false positives where relays would consider
9256 connections to other relays as being client-only connections (and
9257 thus e.g. deserving different link padding schemes) if those
9258 relays fell out of the consensus briefly. Now we look only at the
9259 initial handshake and whether the connection authenticated as a
9260 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
9262 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
9263 - Make our OOM handler aware of the geoip client history cache so it
9264 doesn't fill up the memory. This check is important for IPv6 and
9265 our DoS mitigation subsystem. Closes ticket 25122.
9267 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
9268 - Change relay bandwidth reporting stats interval from 4 hours to 24
9269 hours in order to reduce the efficiency of guard discovery
9270 attacks. Fixes ticket 23856.
9272 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
9273 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
9274 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
9275 since they neither disabled TLS 1.3 nor enabled any of the
9276 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
9277 Closes ticket 24978.
9279 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
9280 - The fallback directory list has been re-generated based on the
9281 current status of the network. Tor uses fallback directories to
9282 bootstrap when it doesn't yet have up-to-date directory
9283 information. Closes ticket 24801.
9284 - Make the default DirAuthorityFallbackRate 0.1, so that clients
9285 prefer to bootstrap from fallback directory mirrors. This is a
9286 follow-up to 24679, which removed weights from the default
9287 fallbacks. Implements ticket 24681.
9289 o Minor features (geoip):
9290 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
9293 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
9294 - Use the actual observed address of an incoming relay connection,
9295 not the canonical address of the relay from its descriptor, when
9296 making decisions about how to handle the incoming connection.
9297 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
9299 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
9300 - Directory authorities, when refusing a descriptor from a rejected
9301 relay, now explicitly tell the relay (in its logs) to set a valid
9302 ContactInfo address and contact the bad-relays@ mailing list.
9303 Fixes bug 25170; bugfix on 0.2.9.1.
9305 o Minor bugfixes (address selection, backport from 0.3.2.9):
9306 - When the fascist_firewall_choose_address_ functions don't find a
9307 reachable address, set the returned address to the null address
9308 and port. This is a precautionary measure, because some callers do
9309 not check the return value. Fixes bug 24736; bugfix
9312 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
9313 - Fetch descriptors aggressively whenever we lack enough to build
9314 circuits, regardless of how many descriptors we are missing.
9315 Previously, we would delay launching the fetch when we had fewer
9316 than 15 missing descriptors, even if some of those descriptors
9317 were blocking circuits from building. Fixes bug 23985; bugfix on
9318 0.1.1.11-alpha. The effects of this bug became worse in
9319 0.3.0.3-alpha, when we began treating missing descriptors from our
9320 primary guards as a reason to delay circuits.
9321 - Don't try fetching microdescriptors from relays that have failed
9322 to deliver them in the past. Fixes bug 23817; bugfix
9325 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
9326 - Fix a signed/unsigned comparison warning introduced by our fix to
9327 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
9329 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
9330 - Avoid a crash when attempting to use the seccomp2 sandbox together
9331 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
9334 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
9335 - Fix a possible crash on malformed consensus. If a consensus had
9336 contained an unparseable protocol line, it could have made clients
9337 and relays crash with a null-pointer exception. To exploit this
9338 issue, however, an attacker would need to be able to subvert the
9339 directory authority system. Fixes bug 25251; bugfix on
9340 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
9342 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
9343 - Recover better from empty or corrupt files in the consensus cache
9344 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
9345 - When a consensus diff calculation is only partially successful,
9346 only record the successful parts as having succeeded. Partial
9347 success can happen if (for example) one compression method fails
9348 but the others succeed. Previously we misrecorded all the
9349 calculations as having succeeded, which would later cause a
9350 nonfatal assertion failure. Fixes bug 24086; bugfix
9353 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
9354 - Tor now updates its guard state when it reads a consensus
9355 regardless of whether it's missing descriptors. That makes tor use
9356 its primary guards to fetch descriptors in some edge cases where
9357 it would previously have used fallback directories. Fixes bug
9358 23862; bugfix on 0.3.0.1-alpha.
9360 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
9361 - Don't treat inability to store a cached consensus object as a bug:
9362 it can happen normally when we are out of disk space. Fixes bug
9363 24859; bugfix on 0.3.1.1-alpha.
9365 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
9366 - When queuing DESTROY cells on a channel, only queue the circuit-id
9367 and reason fields: not the entire 514-byte cell. This fix should
9368 help mitigate any bugs or attacks that fill up these queues, and
9369 free more RAM for other uses. Fixes bug 24666; bugfix
9372 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
9373 - When closing a connection via close_connection_immediately(), we
9374 mark it as "not blocked on bandwidth", to prevent later calls from
9375 trying to unblock it, and give it permission to read. This fixes a
9376 backtrace warning that can happen on relays under various
9377 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
9379 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
9380 - When selecting relays by bandwidth, avoid a rounding error that
9381 could sometimes cause load to be imbalanced incorrectly.
9382 Previously, we would always round upwards; now, we round towards
9383 the nearest integer. This had the biggest effect when a relay's
9384 weight adjustments should have given it weight 0, but it got
9385 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
9386 - When calculating the fraction of nodes that have descriptors, and
9387 all nodes in the network have zero bandwidths, count the number of
9388 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
9389 - Actually log the total bandwidth in compute_weighted_bandwidths().
9390 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
9392 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
9393 - Improve the performance of our consensus-diff application code
9394 when Tor is built with the --enable-fragile-hardening option set.
9395 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
9397 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
9398 - Don't exit the Tor process if setrlimit() fails to change the file
9399 limit (which can happen sometimes on some versions of OSX). Fixes
9400 bug 21074; bugfix on 0.0.9pre5.
9402 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
9403 - Fix a bug in the bit-counting parts of our timing-wheel code on
9404 MSVC. (Note that MSVC is still not a supported build platform, due
9405 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
9408 o Minor bugfixes (relay, partial backport):
9409 - Make the internal channel_is_client() function look at what sort
9410 of connection handshake the other side used, rather than whether
9411 the other side ever sent a create_fast cell to us. Backports part
9412 of the fixes from bugs 22805 and 24898.
9414 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
9415 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
9417 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
9418 bugfix on 0.2.9.4-alpha.
9420 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
9421 - Update the "rust dependencies" submodule to be a project-level
9422 repository, rather than a user repository. Closes ticket 25323.
9425 Changes in version 0.2.9.15 - 2018-03-03
9426 Tor 0.2.9.15 backports important security and stability bugfixes from
9429 It includes an important security fix for a remote crash attack
9430 against directory authorities, tracked as TROVE-2018-001.
9432 This release also backports our new system for improved resistance to
9433 denial-of-service attacks against relays.
9435 This release also fixes several minor bugs and annoyances from
9438 All directory authorities should upgrade to one of the versions
9439 released today. Relays running 0.2.9.x may wish to update to one of
9440 the versions released today, for the DoS mitigations.
9442 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
9443 - Fix a protocol-list handling bug that could be used to remotely crash
9444 directory authorities with a null-pointer exception. Fixes bug 25074;
9445 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
9448 o Major features (denial-of-service mitigation):
9449 - Give relays some defenses against the recent network overload. We
9450 start with three defenses (default parameters in parentheses).
9451 First: if a single client address makes too many concurrent
9452 connections (>100), hang up on further connections. Second: if a
9453 single client address makes circuits too quickly (more than 3 per
9454 second, with an allowed burst of 90) while also having too many
9455 connections open (3), refuse new create cells for the next while
9456 (1-2 hours). Third: if a client asks to establish a rendezvous
9457 point to you directly, ignore the request. These defenses can be
9458 manually controlled by new torrc options, but relays will also
9459 take guidance from consensus parameters, so there's no need to
9460 configure anything manually. Implements ticket 24902.
9462 o Major bugfixes (bootstrapping):
9463 - Fetch descriptors aggressively whenever we lack enough to build
9464 circuits, regardless of how many descriptors we are missing.
9465 Previously, we would delay launching the fetch when we had fewer
9466 than 15 missing descriptors, even if some of those descriptors
9467 were blocking circuits from building. Fixes bug 23985; bugfix on
9468 0.1.1.11-alpha. The effects of this bug became worse in
9469 0.3.0.3-alpha, when we began treating missing descriptors from our
9470 primary guards as a reason to delay circuits.
9472 o Major bugfixes (onion services, retry behavior):
9473 - Fix an "off by 2" error in counting rendezvous failures on the
9474 onion service side. While we thought we would stop the rendezvous
9475 attempt after one failed circuit, we were actually making three
9476 circuit attempts before giving up. Now switch to a default of 2,
9477 and allow the consensus parameter "hs_service_max_rdv_failures" to
9478 override. Fixes bug 24895; bugfix on 0.0.6.
9480 o Minor feature (relay statistics):
9481 - Change relay bandwidth reporting stats interval from 4 hours to 24
9482 hours in order to reduce the efficiency of guard discovery
9483 attacks. Fixes ticket 23856.
9485 o Minor features (compatibility, OpenSSL):
9486 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
9487 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
9488 since they neither disabled TLS 1.3 nor enabled any of the
9489 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
9490 Closes ticket 24978.
9492 o Minor features (denial-of-service avoidance):
9493 - Make our OOM handler aware of the geoip client history cache so it
9494 doesn't fill up the memory. This check is important for IPv6 and
9495 our DoS mitigation subsystem. Closes ticket 25122.
9497 o Minor features (fallback directory mirrors):
9498 - The fallback directory list has been re-generated based on the
9499 current status of the network. Tor uses fallback directories to
9500 bootstrap when it doesn't yet have up-to-date directory
9501 information. Closes ticket 24801.
9502 - Make the default DirAuthorityFallbackRate 0.1, so that clients
9503 prefer to bootstrap from fallback directory mirrors. This is a
9504 follow-up to 24679, which removed weights from the default
9505 fallbacks. Implements ticket 24681.
9507 o Minor features (geoip):
9508 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
9511 o Minor features (linux seccomp2 sandbox):
9512 - Update the sandbox rules so that they should now work correctly
9513 with Glibc 2.26. Closes ticket 24315.
9515 o Minor bugfix (channel connection):
9516 - Use the actual observed address of an incoming relay connection,
9517 not the canonical address of the relay from its descriptor, when
9518 making decisions about how to handle the incoming connection.
9519 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
9521 o Minor bugfix (directory authority):
9522 - Directory authorities, when refusing a descriptor from a rejected
9523 relay, now explicitly tell the relay (in its logs) to set a valid
9524 ContactInfo address and contact the bad-relays@ mailing list.
9525 Fixes bug 25170; bugfix on 0.2.9.1.
9527 o Minor bugfixes (address selection):
9528 - When the fascist_firewall_choose_address_ functions don't find a
9529 reachable address, set the returned address to the null address
9530 and port. This is a precautionary measure, because some callers do
9531 not check the return value. Fixes bug 24736; bugfix
9534 o Minor bugfixes (compilation):
9535 - Fix a signed/unsigned comparison warning introduced by our fix to
9536 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
9538 o Minor bugfixes (control port, linux seccomp2 sandbox):
9539 - Avoid a crash when attempting to use the seccomp2 sandbox together
9540 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
9543 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
9544 - Fix a possible crash on malformed consensus. If a consensus had
9545 contained an unparseable protocol line, it could have made clients
9546 and relays crash with a null-pointer exception. To exploit this
9547 issue, however, an attacker would need to be able to subvert the
9548 directory authority system. Fixes bug 25251; bugfix on
9549 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
9551 o Minor bugfixes (memory usage):
9552 - When queuing DESTROY cells on a channel, only queue the circuit-id
9553 and reason fields: not the entire 514-byte cell. This fix should
9554 help mitigate any bugs or attacks that fill up these queues, and
9555 free more RAM for other uses. Fixes bug 24666; bugfix
9558 o Minor bugfixes (network layer):
9559 - When closing a connection via close_connection_immediately(), we
9560 mark it as "not blocked on bandwidth", to prevent later calls from
9561 trying to unblock it, and give it permission to read. This fixes a
9562 backtrace warning that can happen on relays under various
9563 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
9565 o Minor bugfixes (OSX):
9566 - Don't exit the Tor process if setrlimit() fails to change the file
9567 limit (which can happen sometimes on some versions of OSX). Fixes
9568 bug 21074; bugfix on 0.0.9pre5.
9570 o Minor bugfixes (path selection):
9571 - When selecting relays by bandwidth, avoid a rounding error that
9572 could sometimes cause load to be imbalanced incorrectly.
9573 Previously, we would always round upwards; now, we round towards
9574 the nearest integer. This had the biggest effect when a relay's
9575 weight adjustments should have given it weight 0, but it got
9576 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
9577 - When calculating the fraction of nodes that have descriptors, and
9578 all nodes in the network have zero bandwidths, count the number of
9579 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
9580 - Actually log the total bandwidth in compute_weighted_bandwidths().
9581 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
9583 o Minor bugfixes (portability, msvc):
9584 - Fix a bug in the bit-counting parts of our timing-wheel code on
9585 MSVC. (Note that MSVC is still not a supported build platform, due
9586 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
9589 o Minor bugfixes (relay):
9590 - Make the internal channel_is_client() function look at what sort
9591 of connection handshake the other side used, rather than whether
9592 the other side ever sent a create_fast cell to us. Backports part
9593 of the fixes from bugs 22805 and 24898.
9595 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
9596 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
9598 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
9599 bugfix on 0.2.9.4-alpha.
9602 Changes in version 0.3.2.10 - 2018-03-03
9603 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
9604 backports a number of bugfixes, including important fixes for security
9607 It includes an important security fix for a remote crash attack
9608 against directory authorities, tracked as TROVE-2018-001.
9610 Additionally, it backports a fix for a bug whose severity we have
9611 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
9612 triggered in order to crash relays with a use-after-free pattern. As
9613 such, we are now tracking that bug as TROVE-2018-002 and
9614 CVE-2018-0491, and backporting it to earlier releases. This bug
9615 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
9618 This release also backports our new system for improved resistance to
9619 denial-of-service attacks against relays.
9621 This release also fixes several minor bugs and annoyances from
9624 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
9625 today, for the fix to TROVE-2018-002. Directory authorities should
9626 also upgrade. (Relays on earlier versions might want to update too for
9627 the DoS mitigations.)
9629 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
9630 - Fix a protocol-list handling bug that could be used to remotely crash
9631 directory authorities with a null-pointer exception. Fixes bug 25074;
9632 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
9635 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
9636 - Avoid adding the same channel twice in the KIST scheduler pending
9637 list, which could lead to remote denial-of-service use-after-free
9638 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
9640 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
9641 - Give relays some defenses against the recent network overload. We
9642 start with three defenses (default parameters in parentheses).
9643 First: if a single client address makes too many concurrent
9644 connections (>100), hang up on further connections. Second: if a
9645 single client address makes circuits too quickly (more than 3 per
9646 second, with an allowed burst of 90) while also having too many
9647 connections open (3), refuse new create cells for the next while
9648 (1-2 hours). Third: if a client asks to establish a rendezvous
9649 point to you directly, ignore the request. These defenses can be
9650 manually controlled by new torrc options, but relays will also
9651 take guidance from consensus parameters, so there's no need to
9652 configure anything manually. Implements ticket 24902.
9654 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
9655 - Fix an "off by 2" error in counting rendezvous failures on the
9656 onion service side. While we thought we would stop the rendezvous
9657 attempt after one failed circuit, we were actually making three
9658 circuit attempts before giving up. Now switch to a default of 2,
9659 and allow the consensus parameter "hs_service_max_rdv_failures" to
9660 override. Fixes bug 24895; bugfix on 0.0.6.
9661 - New-style (v3) onion services now obey the "max rendezvous circuit
9662 attempts" logic. Previously they would make as many rendezvous
9663 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
9664 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
9666 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
9667 - Add Link protocol version 5 to the supported protocols list. Fixes
9668 bug 25070; bugfix on 0.3.1.1-alpha.
9670 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
9671 - Fix a set of false positives where relays would consider
9672 connections to other relays as being client-only connections (and
9673 thus e.g. deserving different link padding schemes) if those
9674 relays fell out of the consensus briefly. Now we look only at the
9675 initial handshake and whether the connection authenticated as a
9676 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
9678 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
9679 - The scheduler subsystem was failing to promptly notice changes in
9680 consensus parameters, making it harder to switch schedulers
9681 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
9683 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
9684 - Make our OOM handler aware of the geoip client history cache so it
9685 doesn't fill up the memory. This check is important for IPv6 and
9686 our DoS mitigation subsystem. Closes ticket 25122.
9688 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
9689 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
9690 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
9691 since they neither disabled TLS 1.3 nor enabled any of the
9692 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
9693 Closes ticket 24978.
9695 o Minor features (geoip):
9696 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
9699 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
9700 - When logging a failure to create an onion service's descriptor,
9701 also log what the problem with the descriptor was. Diagnostic
9704 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
9705 - Use the actual observed address of an incoming relay connection,
9706 not the canonical address of the relay from its descriptor, when
9707 making decisions about how to handle the incoming connection.
9708 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
9710 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
9711 - Fix a possible crash on malformed consensus. If a consensus had
9712 contained an unparseable protocol line, it could have made clients
9713 and relays crash with a null-pointer exception. To exploit this
9714 issue, however, an attacker would need to be able to subvert the
9715 directory authority system. Fixes bug 25251; bugfix on
9716 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
9718 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
9719 - Directory authorities, when refusing a descriptor from a rejected
9720 relay, now explicitly tell the relay (in its logs) to set a valid
9721 ContactInfo address and contact the bad-relays@ mailing list.
9722 Fixes bug 25170; bugfix on 0.2.9.1.
9724 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
9725 - When building with Rust on OSX, link against libresolv, to work
9726 around the issue at https://github.com/rust-lang/rust/issues/46797.
9727 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
9729 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
9730 - Remove a BUG() statement when a client fetches an onion descriptor
9731 that has a lower revision counter than the one in its cache. This
9732 can happen in normal circumstances due to HSDir desync. Fixes bug
9733 24976; bugfix on 0.3.2.1-alpha.
9735 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
9736 - Don't treat inability to store a cached consensus object as a bug:
9737 it can happen normally when we are out of disk space. Fixes bug
9738 24859; bugfix on 0.3.1.1-alpha.
9740 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
9741 - Improve the performance of our consensus-diff application code
9742 when Tor is built with the --enable-fragile-hardening option set.
9743 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
9745 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
9746 - Don't exit the Tor process if setrlimit() fails to change the file
9747 limit (which can happen sometimes on some versions of OSX). Fixes
9748 bug 21074; bugfix on 0.0.9pre5.
9750 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
9751 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
9753 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
9754 bugfix on 0.2.9.4-alpha.
9756 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
9757 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
9758 25005; bugfix on 0.3.2.7-rc.
9760 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
9761 - Look at the "HSRend" protocol version, not the "HSDir" protocol
9762 version, when deciding whether a consensus entry can support the
9763 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
9764 bugfix on 0.3.2.1-alpha.
9766 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
9767 - Update the "rust dependencies" submodule to be a project-level
9768 repository, rather than a user repository. Closes ticket 25323.
9770 o Documentation (backport from 0.3.3.1-alpha)
9771 - Document that operators who run more than one relay or bridge are
9772 expected to set MyFamily and ContactInfo correctly. Closes
9776 Changes in version 0.3.2.9 - 2018-01-09
9777 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
9779 The 0.3.2 series includes our long-anticipated new onion service
9780 design, with numerous security features. (For more information, see
9781 our blog post at https://blog.torproject.org/fall-harvest.) We also
9782 have a new circuit scheduler algorithm for improved performance on
9783 relays everywhere (see https://blog.torproject.org/kist-and-tell),
9784 along with many smaller features and bugfixes.
9786 Per our stable release policy, we plan to support each stable release
9787 series for at least the next nine months, or for three months after
9788 the first stable release of the next series: whichever is longer. If
9789 you need a release with long-term support, we recommend that you stay
9790 with the 0.2.9 series.
9792 Below is a list of the changes since 0.3.1.7. For a list of all
9793 changes since 0.3.2.8-rc, see the ChangeLog file.
9795 o Directory authority changes:
9796 - Add "Bastet" as a ninth directory authority to the default list.
9797 Closes ticket 23910.
9798 - The directory authority "Longclaw" has changed its IP address.
9799 Closes ticket 23592.
9800 - Remove longclaw's IPv6 address, as it will soon change. Authority
9801 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9802 3/8 directory authorities with IPv6 addresses, but there are also
9803 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9804 - Add an IPv6 address for the "bastet" directory authority. Closes
9807 o Major features (next-generation onion services):
9808 - Tor now supports the next-generation onion services protocol for
9809 clients and services! As part of this release, the core of
9810 proposal 224 has been implemented and is available for
9811 experimentation and testing by our users. This newer version of
9812 onion services ("v3") features many improvements over the legacy
9815 a) Better crypto (replaced SHA1/DH/RSA1024
9816 with SHA3/ed25519/curve25519)
9818 b) Improved directory protocol, leaking much less information to
9821 c) Improved directory protocol, with smaller surface for
9824 d) Better onion address security against impersonation.
9826 e) More extensible introduction/rendezvous protocol.
9828 f) A cleaner and more modular codebase.
9830 You can identify a next-generation onion address by its length:
9831 they are 56 characters long, as in
9832 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
9834 In the future, we will release more options and features for v3
9835 onion services, but we first need a testing period, so that the
9836 current codebase matures and becomes more robust. Planned features
9837 include: offline keys, advanced client authorization, improved
9838 guard algorithms, and statistics. For full details, see
9841 Legacy ("v2") onion services will still work for the foreseeable
9842 future, and will remain the default until this new codebase gets
9843 tested and hardened. Service operators who want to experiment with
9844 the new system can use the 'HiddenServiceVersion 3' torrc
9845 directive along with the regular onion service configuration
9846 options. For more information, see our blog post at
9847 "https://blog.torproject.org/fall-harvest". Enjoy!
9849 o Major feature (scheduler, channel):
9850 - Tor now uses new schedulers to decide which circuits should
9851 deliver cells first, in order to improve congestion at relays. The
9852 first type is called "KIST" ("Kernel Informed Socket Transport"),
9853 and is only available on Linux-like systems: it uses feedback from
9854 the kernel to prevent the kernel's TCP buffers from growing too
9855 full. The second new scheduler type is called "KISTLite": it
9856 behaves the same as KIST, but runs on systems without kernel
9857 support for inspecting TCP implementation details. The old
9858 scheduler is still available, under the name "Vanilla". To change
9859 the default scheduler preference order, use the new "Schedulers"
9860 option. (The default preference order is "KIST,KISTLite,Vanilla".)
9862 Matt Traudt implemented KIST, based on research by Rob Jansen,
9863 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
9864 more information, see the design paper at
9865 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
9866 followup implementation paper at https://arxiv.org/abs/1709.01044.
9867 Closes ticket 12541. For more information, see our blog post at
9868 "https://blog.torproject.org/kist-and-tell".
9870 o Major bugfixes (security, general):
9871 - Fix a denial of service bug where an attacker could use a
9872 malformed directory object to cause a Tor instance to pause while
9873 OpenSSL would try to read a passphrase from the terminal. (Tor
9874 instances run without a terminal, which is the case for most Tor
9875 packages, are not impacted.) Fixes bug 24246; bugfix on every
9876 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9877 Found by OSS-Fuzz as testcase 6360145429790720.
9879 o Major bugfixes (security, directory authority):
9880 - Fix a denial of service issue where an attacker could crash a
9881 directory authority using a malformed router descriptor. Fixes bug
9882 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9885 o Major bugfixes (security, onion service v2):
9886 - Fix a use-after-free error that could crash v2 Tor onion services
9887 when they failed to open circuits while expiring introduction
9888 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9889 also tracked as TROVE-2017-013 and CVE-2017-8823.
9890 - When checking for replays in the INTRODUCE1 cell data for a
9891 (legacy) onion service, correctly detect replays in the RSA-
9892 encrypted part of the cell. We were previously checking for
9893 replays on the entire cell, but those can be circumvented due to
9894 the malleability of Tor's legacy hybrid encryption. This fix helps
9895 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9896 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9899 o Major bugfixes (security, relay):
9900 - When running as a relay, make sure that we never build a path
9901 through ourselves, even in the case where we have somehow lost the
9902 version of our descriptor appearing in the consensus. Fixes part
9903 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9904 as TROVE-2017-012 and CVE-2017-8822.
9905 - When running as a relay, make sure that we never choose ourselves
9906 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
9907 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
9909 o Major bugfixes (bootstrapping):
9910 - Fetch descriptors aggressively whenever we lack enough to build
9911 circuits, regardless of how many descriptors we are missing.
9912 Previously, we would delay launching the fetch when we had fewer
9913 than 15 missing descriptors, even if some of those descriptors
9914 were blocking circuits from building. Fixes bug 23985; bugfix on
9915 0.1.1.11-alpha. The effects of this bug became worse in
9916 0.3.0.3-alpha, when we began treating missing descriptors from our
9917 primary guards as a reason to delay circuits.
9918 - Don't try fetching microdescriptors from relays that have failed
9919 to deliver them in the past. Fixes bug 23817; bugfix
9922 o Major bugfixes (circuit prediction):
9923 - Fix circuit prediction logic so that a client doesn't treat a port
9924 as being "handled" by a circuit if that circuit already has
9925 isolation settings on it. This change should make Tor clients more
9926 responsive by improving their chances of having a pre-created
9927 circuit ready for use when a request arrives. Fixes bug 18859;
9928 bugfix on 0.2.3.3-alpha.
9930 o Major bugfixes (exit relays, DNS):
9931 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9932 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9933 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9934 identifying and finding a workaround to this bug and to Moritz,
9935 Arthur Edelstein, and Roger for helping to track it down and
9938 o Major bugfixes (relay, crash, assertion failure):
9939 - Fix a timing-based assertion failure that could occur when the
9940 circuit out-of-memory handler freed a connection's output buffer.
9941 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9943 o Major bugfixes (usability, control port):
9944 - Report trusted clock skew indications as bootstrap errors, so
9945 controllers can more easily alert users when their clocks are
9946 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
9948 o Minor features (bridge):
9949 - Bridge relays can now set the BridgeDistribution config option to
9950 add a "bridge-distribution-request" line to their bridge
9951 descriptor, which tells BridgeDB how they'd like their bridge
9952 address to be given out. (Note that as of Oct 2017, BridgeDB does
9953 not yet implement this feature.) As a side benefit, this feature
9954 provides a way to distinguish bridge descriptors from non-bridge
9955 descriptors. Implements tickets 18329.
9956 - When handling the USERADDR command on an ExtOrPort, warn when the
9957 transports provides a USERADDR with no port. In a future version,
9958 USERADDR commands of this format may be rejected. Detects problems
9959 related to ticket 23080.
9961 o Minor features (bug detection):
9962 - Log a warning message with a stack trace for any attempt to call
9963 get_options() during option validation. This pattern has caused
9964 subtle bugs in the past. Closes ticket 22281.
9966 o Minor features (build, compilation):
9967 - The "check-changes" feature is now part of the "make check" tests;
9968 we'll use it to try to prevent misformed changes files from
9969 accumulating. Closes ticket 23564.
9970 - Tor builds should now fail if there are any mismatches between the
9971 C type representing a configuration variable and the C type the
9972 data-driven parser uses to store a value there. Previously, we
9973 needed to check these by hand, which sometimes led to mistakes.
9974 Closes ticket 23643.
9976 o Minor features (client):
9977 - You can now use Tor as a tunneled HTTP proxy: use the new
9978 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
9979 requests. Closes ticket 22407.
9980 - Add an extra check to make sure that we always use the newer guard
9981 selection code for picking our guards. Closes ticket 22779.
9982 - When downloading (micro)descriptors, don't split the list into
9983 multiple requests unless we want at least 32 descriptors.
9984 Previously, we split at 4, not 32, which led to significant
9985 overhead in HTTP request size and degradation in compression
9986 performance. Closes ticket 23220.
9987 - Improve log messages when missing descriptors for primary guards.
9988 Resolves ticket 23670.
9990 o Minor features (command line):
9991 - Add a new commandline option, --key-expiration, which prints when
9992 the current signing key is going to expire. Implements ticket
9993 17639; patch by Isis Lovecruft.
9995 o Minor features (control port):
9996 - If an application tries to use the control port as an HTTP proxy,
9997 respond with a meaningful "This is the Tor control port" message,
9998 and log the event. Closes ticket 1667. Patch from Ravi
10000 - Provide better error message for GETINFO desc/(id|name) when not
10001 fetching router descriptors. Closes ticket 5847. Patch by
10003 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
10004 whether Tor will try to download router descriptors and
10005 microdescriptors respectively. Closes ticket 22684.
10006 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
10007 so controllers can tell whether the geoip databases are loaded.
10008 Closes ticket 23237.
10009 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
10010 events. Closes ticket 19254. Patch by "DonnchaC".
10012 o Minor features (development support):
10013 - Developers can now generate a call-graph for Tor using the
10014 "calltool" python program, which post-processes object dumps. It
10015 should work okay on many Linux and OSX platforms, and might work
10016 elsewhere too. To run it, install calltool from
10017 https://gitweb.torproject.org/user/nickm/calltool.git and run
10018 "make callgraph". Closes ticket 19307.
10020 o Minor features (directory authority):
10021 - Make the "Exit" flag assignment only depend on whether the exit
10022 policy allows connections to ports 80 and 443. Previously relays
10023 would get the Exit flag if they allowed connections to one of
10024 these ports and also port 6667. Resolves ticket 23637.
10026 o Minor features (ed25519):
10027 - Add validation function to checks for torsion components in
10028 ed25519 public keys, used by prop224 client-side code. Closes
10029 ticket 22006. Math help by Ian Goldberg.
10031 o Minor features (exit relay, DNS):
10032 - Improve the clarity and safety of the log message from evdns when
10033 receiving an apparently spoofed DNS reply. Closes ticket 3056.
10035 o Minor features (fallback directory mirrors):
10036 - The fallback directory list has been re-generated based on the
10037 current status of the network. Tor uses fallback directories to
10038 bootstrap when it doesn't yet have up-to-date directory
10039 information. Closes ticket 24801.
10040 - Make the default DirAuthorityFallbackRate 0.1, so that clients
10041 prefer to bootstrap from fallback directory mirrors. This is a
10042 follow-up to 24679, which removed weights from the default
10043 fallbacks. Implements ticket 24681.
10045 o Minor features (geoip):
10046 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
10049 o Minor features (integration, hardening):
10050 - Add a new NoExec option to prevent Tor from running other
10051 programs. When this option is set to 1, Tor will never try to run
10052 another program, regardless of the settings of
10053 PortForwardingHelper, ClientTransportPlugin, or
10054 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
10055 without restarting Tor. Closes ticket 22976.
10057 o Minor features (linux seccomp2 sandbox):
10058 - Update the sandbox rules so that they should now work correctly
10059 with Glibc 2.26. Closes ticket 24315.
10061 o Minor features (logging):
10062 - Provide better warnings when the getrandom() syscall fails. Closes
10064 - Downgrade a pair of log messages that could occur when an exit's
10065 resolver gave us an unusual (but not forbidden) response. Closes
10067 - Improve the message we log when re-enabling circuit build timeouts
10068 after having received a consensus. Closes ticket 20963.
10069 - Log more circuit information whenever we are about to try to
10070 package a relay cell on a circuit with a nonexistent n_chan.
10071 Attempt to diagnose ticket 8185.
10072 - Improve info-level log identification of particular circuits, to
10073 help with debugging. Closes ticket 23645.
10074 - Improve the warning message for specifying a relay by nickname.
10075 The previous message implied that nickname registration was still
10076 part of the Tor network design, which it isn't. Closes
10078 - If the sandbox filter fails to load, suggest to the user that
10079 their kernel might not support seccomp2. Closes ticket 23090.
10081 o Minor features (onion service, circuit, logging):
10082 - Improve logging of many callsite in the circuit subsystem to print
10083 the circuit identifier(s).
10084 - Log when we cleanup an intro point from a service so we know when
10085 and for what reason it happened. Closes ticket 23604.
10087 o Minor features (portability):
10088 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
10089 (It doesn't yet work with the sandbox enabled.) Closes
10091 - Check at configure time whether uint8_t is the same type as
10092 unsigned char. Lots of existing code already makes this
10093 assumption, and there could be strict aliasing issues if the
10094 assumption is violated. Closes ticket 22410.
10096 o Minor features (relay):
10097 - When choosing which circuits can be expired as unused, consider
10098 circuits from clients even if those clients used regular CREATE
10099 cells to make them; and do not consider circuits from relays even
10100 if they were made with CREATE_FAST. Part of ticket 22805.
10101 - Reject attempts to use relative file paths when RunAsDaemon is
10102 set. Previously, Tor would accept these, but the directory-
10103 changing step of RunAsDaemon would give strange and/or confusing
10104 results. Closes ticket 22731.
10106 o Minor features (relay statistics):
10107 - Change relay bandwidth reporting stats interval from 4 hours to 24
10108 hours in order to reduce the efficiency of guard discovery
10109 attacks. Fixes ticket 23856.
10111 o Minor features (reverted deprecations):
10112 - The ClientDNSRejectInternalAddresses flag can once again be set in
10113 non-testing Tor networks, so long as they do not use the default
10114 directory authorities. This change also removes the deprecation of
10115 this flag from 0.2.9.2-alpha. Closes ticket 21031.
10117 o Minor features (robustness):
10118 - Change several fatal assertions when flushing buffers into non-
10119 fatal assertions, to prevent any recurrence of 23690.
10121 o Minor features (startup, safety):
10122 - When configured to write a PID file, Tor now exits if it is unable
10123 to do so. Previously, it would warn and continue. Closes
10126 o Minor features (static analysis):
10127 - The BUG() macro has been changed slightly so that Coverity no
10128 longer complains about dead code if the bug is impossible. Closes
10131 o Minor features (testing):
10132 - Our fuzzing tests now test the encrypted portions of v3 onion
10133 service descriptors. Implements more of 21509.
10134 - Add a unit test to make sure that our own generated platform
10135 string will be accepted by directory authorities. Closes
10137 - The default chutney network tests now include tests for the v3
10138 onion service design. Make sure you have the latest version of
10139 chutney if you want to run these. Closes ticket 22437.
10140 - Add a unit test to verify that we can parse a hardcoded v2 onion
10141 service descriptor. Closes ticket 15554.
10143 o Minor bugfixes (address selection):
10144 - When the fascist_firewall_choose_address_ functions don't find a
10145 reachable address, set the returned address to the null address
10146 and port. This is a precautionary measure, because some callers do
10147 not check the return value. Fixes bug 24736; bugfix
10150 o Minor bugfixes (bootstrapping):
10151 - When warning about state file clock skew, report the correct
10152 direction for the detected skew. Fixes bug 23606; bugfix
10155 o Minor bugfixes (bridge clients, bootstrap):
10156 - Retry directory downloads when we get our first bridge descriptor
10157 during bootstrap or while reconnecting to the network. Keep
10158 retrying every time we get a bridge descriptor, until we have a
10159 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
10160 - Stop delaying bridge descriptor fetches when we have cached bridge
10161 descriptors. Instead, only delay bridge descriptor fetches when we
10162 have at least one reachable bridge. Fixes part of bug 24367;
10163 bugfix on 0.2.0.3-alpha.
10164 - Stop delaying directory fetches when we have cached bridge
10165 descriptors. Instead, only delay bridge descriptor fetches when
10166 all our bridges are definitely unreachable. Fixes part of bug
10167 24367; bugfix on 0.2.0.3-alpha.
10169 o Minor bugfixes (bridge):
10170 - Overwrite the bridge address earlier in the process of retrieving
10171 its descriptor, to make sure we reach it on the configured
10172 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
10174 o Minor bugfixes (build, compilation):
10175 - Fix a compilation warning when building with zstd support on
10176 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
10177 and fixed by Andreas Stieger.
10178 - When searching for OpenSSL, don't accept any OpenSSL library that
10179 lacks TLSv1_1_method(): Tor doesn't build with those versions.
10180 Additionally, look in /usr/local/opt/openssl, if it's present.
10181 These changes together repair the default build on OSX systems
10182 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
10183 - Fix a signed/unsigned comparison warning introduced by our fix to
10184 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
10185 - Fix a memory leak warning in one of the libevent-related
10186 configuration tests that could occur when manually specifying
10187 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
10188 Found and patched by Alex Xu.
10189 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
10190 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
10192 o Minor bugfixes (certificate handling):
10193 - Fix a time handling bug in Tor certificates set to expire after
10194 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
10195 Coverity as CID 1415728.
10197 o Minor bugfixes (client):
10198 - By default, do not enable storage of client-side DNS values. These
10199 values were unused by default previously, but they should not have
10200 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
10202 o Minor bugfixes (client, usability):
10203 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
10204 SOCKS4a requests that contain IP address strings, even when
10205 SafeSocks in enabled, as this prevents user from connecting to
10206 known IP addresses without relying on DNS for resolving. SafeSocks
10207 still rejects SOCKS connections that connect to IP addresses when
10208 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
10209 bugfix on Tor 0.2.6.2-alpha.
10211 o Minor bugfixes (code correctness):
10212 - Call htons() in extend_cell_format() for encoding a 16-bit value.
10213 Previously we used ntohs(), which happens to behave the same on
10214 all the platforms we support, but which isn't really correct.
10215 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
10216 - For defense-in-depth, make the controller's write_escaped_data()
10217 function robust to extremely long inputs. Fixes bug 19281; bugfix
10218 on 0.1.1.1-alpha. Reported by Guido Vranken.
10219 - Fix several places in our codebase where a C compiler would be
10220 likely to eliminate a check, based on assuming that undefined
10221 behavior had not happened elsewhere in the code. These cases are
10222 usually a sign of redundant checking or dubious arithmetic. Found
10223 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
10224 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
10227 o Minor bugfixes (compression):
10228 - Handle a pathological case when decompressing Zstandard data when
10229 the output buffer size is zero. Fixes bug 23551; bugfix
10232 o Minor bugfixes (consensus expiry):
10233 - Check for adequate directory information correctly. Previously, Tor
10234 would reconsider whether it had sufficient directory information
10235 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
10237 o Minor bugfixes (control port, linux seccomp2 sandbox):
10238 - Avoid a crash when attempting to use the seccomp2 sandbox together
10239 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
10242 o Minor bugfixes (control port, onion services):
10243 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
10244 HS_DESC event when a service is not able to upload a descriptor.
10245 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
10247 o Minor bugfixes (directory cache):
10248 - Recover better from empty or corrupt files in the consensus cache
10249 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
10250 - When a consensus diff calculation is only partially successful,
10251 only record the successful parts as having succeeded. Partial
10252 success can happen if (for example) one compression method fails
10253 but the others succeed. Previously we misrecorded all the
10254 calculations as having succeeded, which would later cause a
10255 nonfatal assertion failure. Fixes bug 24086; bugfix
10258 o Minor bugfixes (directory client):
10259 - On failure to download directory information, delay retry attempts
10260 by a random amount based on the "decorrelated jitter" algorithm.
10261 Our previous delay algorithm tended to produce extra-long delays
10262 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
10264 o Minor bugfixes (directory protocol):
10265 - Directory servers now include a "Date:" http header for response
10266 codes other than 200. Clients starting with a skewed clock and a
10267 recent consensus were getting "304 Not modified" responses from
10268 directory authorities, so without the Date header, the client
10269 would never hear about a wrong clock. Fixes bug 23499; bugfix
10271 - Make clients wait for 6 seconds before trying to download a
10272 consensus from an authority. Fixes bug 17750; bugfix
10275 o Minor bugfixes (documentation):
10276 - Document better how to read gcov, and what our gcov postprocessing
10277 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
10278 - Fix manpage to not refer to the obsolete (and misspelled)
10279 UseEntryGuardsAsDirectoryGuards parameter in the description of
10280 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
10282 o Minor bugfixes (DoS-resistance):
10283 - If future code asks if there are any running bridges, without
10284 checking if bridges are enabled, log a BUG warning rather than
10285 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
10287 o Minor bugfixes (entry guards):
10288 - Tor now updates its guard state when it reads a consensus
10289 regardless of whether it's missing descriptors. That makes tor use
10290 its primary guards to fetch descriptors in some edge cases where
10291 it would previously have used fallback directories. Fixes bug
10292 23862; bugfix on 0.3.0.1-alpha.
10294 o Minor bugfixes (format strictness):
10295 - Restrict several data formats to decimal. Previously, the
10296 BuildTimeHistogram entries in the state file, the "bw=" entries in
10297 the bandwidth authority file, and the process IDs passed to the
10298 __OwningControllerProcess option could all be specified in hex or
10299 octal as well as in decimal. This was not an intentional feature.
10300 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
10303 o Minor bugfixes (heartbeat):
10304 - If we fail to write a heartbeat message, schedule a retry for the
10305 minimum heartbeat interval number of seconds in the future. Fixes
10306 bug 19476; bugfix on 0.2.3.1-alpha.
10308 o Minor bugfixes (logging):
10309 - Suppress a log notice when relay descriptors arrive. We already
10310 have a bootstrap progress for this so no need to log notice
10311 everytime tor receives relay descriptors. Microdescriptors behave
10312 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
10313 - Remove duplicate log messages regarding opening non-local
10314 SocksPorts upon parsing config and opening listeners at startup.
10315 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
10316 - Use a more comprehensible log message when telling the user
10317 they've excluded every running exit node. Fixes bug 7890; bugfix
10319 - When logging the number of descriptors we intend to download per
10320 directory request, do not log a number higher than then the number
10321 of descriptors we're fetching in total. Fixes bug 19648; bugfix
10323 - When warning about a directory owned by the wrong user, log the
10324 actual name of the user owning the directory. Previously, we'd log
10325 the name of the process owner twice. Fixes bug 23487; bugfix
10327 - Fix some messages on unexpected errors from the seccomp2 library.
10328 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
10329 - The tor specification says hop counts are 1-based, so fix two log
10330 messages that mistakenly logged 0-based hop counts. Fixes bug
10331 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
10332 Credit to Xiaofan Li for reporting this issue.
10334 o Minor bugfixes (logging, relay shutdown, annoyance):
10335 - When a circuit is marked for close, do not attempt to package any
10336 cells for channels on that circuit. Previously, we would detect
10337 this condition lower in the call stack, when we noticed that the
10338 circuit had no attached channel, and log an annoying message.
10339 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
10341 o Minor bugfixes (memory safety, defensive programming):
10342 - Clear the target address when node_get_prim_orport() returns
10343 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
10345 o Minor bugfixes (memory usage):
10346 - When queuing DESTROY cells on a channel, only queue the circuit-id
10347 and reason fields: not the entire 514-byte cell. This fix should
10348 help mitigate any bugs or attacks that fill up these queues, and
10349 free more RAM for other uses. Fixes bug 24666; bugfix
10352 o Minor bugfixes (network layer):
10353 - When closing a connection via close_connection_immediately(), we
10354 mark it as "not blocked on bandwidth", to prevent later calls from
10355 trying to unblock it, and give it permission to read. This fixes a
10356 backtrace warning that can happen on relays under various
10357 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
10359 o Minor bugfixes (onion services):
10360 - The introduction circuit was being timed out too quickly while
10361 waiting for the rendezvous circuit to complete. Keep the intro
10362 circuit around longer instead of timing out and reopening new ones
10363 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
10364 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
10365 so it matches dir-spec.txt. Fixes bug 24262; bugfix
10367 - When handling multiple SOCKS request for the same .onion address,
10368 only fetch the service descriptor once.
10369 - Avoid a possible double close of a circuit by the intro point on
10370 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
10371 bugfix on 0.3.0.1-alpha.
10372 - When reloading configured onion services, copy all information
10373 from the old service object. Previously, some data was omitted,
10374 causing delays in descriptor upload, and other bugs. Fixes bug
10375 23790; bugfix on 0.2.1.9-alpha.
10377 o Minor bugfixes (path selection):
10378 - When selecting relays by bandwidth, avoid a rounding error that
10379 could sometimes cause load to be imbalanced incorrectly.
10380 Previously, we would always round upwards; now, we round towards
10381 the nearest integer. This had the biggest effect when a relay's
10382 weight adjustments should have given it weight 0, but it got
10383 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
10384 - When calculating the fraction of nodes that have descriptors, and
10385 all nodes in the network have zero bandwidths, count the number of
10386 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
10387 - Actually log the total bandwidth in compute_weighted_bandwidths().
10388 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
10390 o Minor bugfixes (portability):
10391 - Stop using the PATH_MAX variable, which is not defined on GNU
10392 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
10393 - Fix a bug in the bit-counting parts of our timing-wheel code on
10394 MSVC. (Note that MSVC is still not a supported build platform, due
10395 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
10398 o Minor bugfixes (relay):
10399 - When uploading our descriptor for the first time after startup,
10400 report the reason for uploading as "Tor just started" rather than
10401 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
10402 - Avoid unnecessary calls to directory_fetches_from_authorities() on
10403 relays, to prevent spurious address resolutions and descriptor
10404 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
10405 bugfix on in 0.2.8.1-alpha.
10406 - Avoid a crash when transitioning from client mode to bridge mode.
10407 Previously, we would launch the worker threads whenever our
10408 "public server" mode changed, but not when our "server" mode
10409 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
10411 o Minor bugfixes (testing):
10412 - Fix a spurious fuzzing-only use of an uninitialized value. Found
10413 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
10414 - Test that IPv6-only clients can use microdescriptors when running
10415 "make test-network-all". Requires chutney master 61c28b9 or later.
10416 Closes ticket 24109.
10417 - Prevent scripts/test/coverage from attempting to move gcov output
10418 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
10419 - Capture and detect several "Result does not fit" warnings in unit
10420 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
10422 - Fix additional channelpadding unit test failures by using mocked
10423 time instead of actual time for all tests. Fixes bug 23608; bugfix
10425 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
10426 to correctly handle cases where a caller gives it an RSA key of
10427 under 160 bits. (This is not actually a bug in Tor itself, but
10428 rather in our fuzzing code.) Fixes bug 24247; bugfix on
10429 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
10430 - Fix a broken unit test for the OutboundAddress option: the parsing
10431 function was never returning an error on failure. Fixes bug 23366;
10432 bugfix on 0.3.0.3-alpha.
10433 - Fix a signed-integer overflow in the unit tests for
10434 dir/download_status_random_backoff, which was untriggered until we
10435 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
10437 o Minor bugfixes (usability, control port):
10438 - Stop making an unnecessary routerlist check in NETINFO clock skew
10439 detection; this was preventing clients from reporting NETINFO clock
10440 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
10442 o Code simplification and refactoring:
10443 - Remove various ways of testing circuits and connections for
10444 "clientness"; instead, favor channel_is_client(). Part of
10446 - Extract the code for handling newly-open channels into a separate
10447 function from the general code to handle channel state
10448 transitions. This change simplifies our callgraph, reducing the
10449 size of the largest strongly connected component by roughly a
10450 factor of two. Closes ticket 22608.
10451 - Remove dead code for largely unused statistics on the number of
10452 times we've attempted various public key operations. Fixes bug
10453 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
10454 - Remove several now-obsolete functions for asking about old
10455 variants directory authority status. Closes ticket 22311; patch
10457 - Remove some of the code that once supported "Named" and "Unnamed"
10458 routers. Authorities no longer vote for these flags. Closes
10460 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
10461 and old hidden services, to indicate that they aren't suitable for
10462 new protocols or formats. Closes ticket 23026.
10463 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
10464 22521. Patch from Neel Chauhan.
10465 - Split the enormous circuit_send_next_onion_skin() function into
10466 multiple subfunctions. Closes ticket 22804.
10467 - Split the portions of the buffer.c module that handle particular
10468 protocols into separate modules. Part of ticket 23149.
10469 - Use our test macros more consistently, to produce more useful
10470 error messages when our unit tests fail. Add coccinelle patches to
10471 allow us to re-check for test macro uses. Closes ticket 22497.
10473 o Deprecated features:
10474 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
10475 now deprecated; they do not apply to relays, and they have had no
10476 effect on clients since 0.2.8.x. Closes ticket 19704.
10477 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
10478 only applies to direct unencrypted HTTP connections to your
10479 directory server, which your Tor probably isn't using. Closes
10483 - Add notes in man page regarding OS support for the various
10484 scheduler types. Attempt to use less jargon in the scheduler
10485 section. Closes ticket 24254.
10486 - Clarify that the Address option is entirely about setting an
10487 advertised IPv4 address. Closes ticket 18891.
10488 - Clarify the manpage's use of the term "address" to clarify what
10489 kind of address is intended. Closes ticket 21405.
10490 - Document that onion service subdomains are allowed, and ignored.
10491 Closes ticket 18736.
10492 - Clarify in the manual that "Sandbox 1" is only supported on Linux
10493 kernels. Closes ticket 22677.
10494 - Document all values of PublishServerDescriptor in the manpage.
10495 Closes ticket 15645.
10496 - Improve the documentation for the directory port part of the
10497 DirAuthority line. Closes ticket 20152.
10498 - Restore documentation for the authorities' "approved-routers"
10499 file. Closes ticket 21148.
10501 o Removed features:
10502 - The AllowDotExit option has been removed as unsafe. It has been
10503 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
10504 - The ClientDNSRejectInternalAddresses flag can no longer be set on
10505 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
10506 Closes ticket 21031.
10507 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
10508 nobody was using it any longer. Closes ticket 22377.
10511 Changes in version 0.3.1.9 - 2017-12-01:
10512 Tor 0.3.1.9 backports important security and stability fixes from the
10513 0.3.2 development series. All Tor users should upgrade to this
10514 release, or to another of the releases coming out today.
10516 o Major bugfixes (security, backport from 0.3.2.6-alpha):
10517 - Fix a denial of service bug where an attacker could use a
10518 malformed directory object to cause a Tor instance to pause while
10519 OpenSSL would try to read a passphrase from the terminal. (Tor
10520 instances run without a terminal, which is the case for most Tor
10521 packages, are not impacted.) Fixes bug 24246; bugfix on every
10522 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10523 Found by OSS-Fuzz as testcase 6360145429790720.
10524 - Fix a denial of service issue where an attacker could crash a
10525 directory authority using a malformed router descriptor. Fixes bug
10526 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
10528 - When checking for replays in the INTRODUCE1 cell data for a
10529 (legacy) onion service, correctly detect replays in the RSA-
10530 encrypted part of the cell. We were previously checking for
10531 replays on the entire cell, but those can be circumvented due to
10532 the malleability of Tor's legacy hybrid encryption. This fix helps
10533 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10534 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10537 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
10538 - Fix a use-after-free error that could crash v2 Tor onion services
10539 when they failed to open circuits while expiring introduction
10540 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
10541 also tracked as TROVE-2017-013 and CVE-2017-8823.
10543 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
10544 - When running as a relay, make sure that we never build a path
10545 through ourselves, even in the case where we have somehow lost the
10546 version of our descriptor appearing in the consensus. Fixes part
10547 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
10548 as TROVE-2017-012 and CVE-2017-8822.
10549 - When running as a relay, make sure that we never choose ourselves
10550 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
10551 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
10553 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
10554 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
10555 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
10556 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
10557 identifying and finding a workaround to this bug and to Moritz,
10558 Arthur Edelstein, and Roger for helping to track it down and
10561 o Minor features (bridge):
10562 - Bridges now include notice in their descriptors that they are
10563 bridges, and notice of their distribution status, based on their
10564 publication settings. Implements ticket 18329. For more fine-
10565 grained control of how a bridge is distributed, upgrade to 0.3.2.x
10568 o Minor features (directory authority, backport from 0.3.2.6-alpha):
10569 - Add an IPv6 address for the "bastet" directory authority. Closes
10572 o Minor features (geoip):
10573 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
10576 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
10577 - Avoid unnecessary calls to directory_fetches_from_authorities() on
10578 relays, to prevent spurious address resolutions and descriptor
10579 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
10580 bugfix on in 0.2.8.1-alpha.
10582 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
10583 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
10584 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
10586 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
10587 - When a circuit is marked for close, do not attempt to package any
10588 cells for channels on that circuit. Previously, we would detect
10589 this condition lower in the call stack, when we noticed that the
10590 circuit had no attached channel, and log an annoying message.
10591 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
10593 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
10594 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
10595 so it matches dir-spec.txt. Fixes bug 24262; bugfix
10598 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
10599 - Avoid a crash when transitioning from client mode to bridge mode.
10600 Previously, we would launch the worker threads whenever our
10601 "public server" mode changed, but not when our "server" mode
10602 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
10605 Changes in version 0.3.0.13 - 2017-12-01
10606 Tor 0.3.0.13 backports important security and stability bugfixes from
10607 later Tor releases. All Tor users should upgrade to this release, or
10608 to another of the releases coming out today.
10610 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
10611 2018. If you need a release with long-term support, please stick with
10612 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10614 o Major bugfixes (security, backport from 0.3.2.6-alpha):
10615 - Fix a denial of service bug where an attacker could use a
10616 malformed directory object to cause a Tor instance to pause while
10617 OpenSSL would try to read a passphrase from the terminal. (Tor
10618 instances run without a terminal, which is the case for most Tor
10619 packages, are not impacted.) Fixes bug 24246; bugfix on every
10620 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10621 Found by OSS-Fuzz as testcase 6360145429790720.
10622 - Fix a denial of service issue where an attacker could crash a
10623 directory authority using a malformed router descriptor. Fixes bug
10624 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
10626 - When checking for replays in the INTRODUCE1 cell data for a
10627 (legacy) onion service, correctly detect replays in the RSA-
10628 encrypted part of the cell. We were previously checking for
10629 replays on the entire cell, but those can be circumvented due to
10630 the malleability of Tor's legacy hybrid encryption. This fix helps
10631 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10632 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10635 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
10636 - Fix a use-after-free error that could crash v2 Tor onion services
10637 when they failed to open circuits while expiring introduction
10638 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
10639 also tracked as TROVE-2017-013 and CVE-2017-8823.
10641 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
10642 - When running as a relay, make sure that we never build a path
10643 through ourselves, even in the case where we have somehow lost the
10644 version of our descriptor appearing in the consensus. Fixes part
10645 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
10646 as TROVE-2017-012 and CVE-2017-8822.
10647 - When running as a relay, make sure that we never choose ourselves
10648 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
10649 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
10651 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
10652 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
10653 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
10654 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
10655 identifying and finding a workaround to this bug and to Moritz,
10656 Arthur Edelstein, and Roger for helping to track it down and
10659 o Minor features (security, windows, backport from 0.3.1.1-alpha):
10660 - Enable a couple of pieces of Windows hardening: one
10661 (HeapEnableTerminationOnCorruption) that has been on-by-default
10662 since Windows 8, and unavailable before Windows 7; and one
10663 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
10664 affect us, but shouldn't do any harm. Closes ticket 21953.
10666 o Minor features (bridge, backport from 0.3.1.9):
10667 - Bridges now include notice in their descriptors that they are
10668 bridges, and notice of their distribution status, based on their
10669 publication settings. Implements ticket 18329. For more fine-
10670 grained control of how a bridge is distributed, upgrade to 0.3.2.x
10673 o Minor features (directory authority, backport from 0.3.2.6-alpha):
10674 - Add an IPv6 address for the "bastet" directory authority. Closes
10677 o Minor features (geoip):
10678 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
10681 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
10682 - Avoid unnecessary calls to directory_fetches_from_authorities() on
10683 relays, to prevent spurious address resolutions and descriptor
10684 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
10685 bugfix on in 0.2.8.1-alpha.
10687 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
10688 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
10689 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
10691 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
10692 - When a circuit is marked for close, do not attempt to package any
10693 cells for channels on that circuit. Previously, we would detect
10694 this condition lower in the call stack, when we noticed that the
10695 circuit had no attached channel, and log an annoying message.
10696 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
10698 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
10699 - Avoid a crash when transitioning from client mode to bridge mode.
10700 Previously, we would launch the worker threads whenever our
10701 "public server" mode changed, but not when our "server" mode
10702 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
10704 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
10705 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
10706 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
10709 Changes in version 0.2.9.14 - 2017-12-01
10710 Tor 0.3.0.13 backports important security and stability bugfixes from
10711 later Tor releases. All Tor users should upgrade to this release, or
10712 to another of the releases coming out today.
10714 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
10715 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
10716 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
10717 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
10718 identifying and finding a workaround to this bug and to Moritz,
10719 Arthur Edelstein, and Roger for helping to track it down and
10722 o Major bugfixes (security, backport from 0.3.2.6-alpha):
10723 - Fix a denial of service bug where an attacker could use a
10724 malformed directory object to cause a Tor instance to pause while
10725 OpenSSL would try to read a passphrase from the terminal. (Tor
10726 instances run without a terminal, which is the case for most Tor
10727 packages, are not impacted.) Fixes bug 24246; bugfix on every
10728 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10729 Found by OSS-Fuzz as testcase 6360145429790720.
10730 - Fix a denial of service issue where an attacker could crash a
10731 directory authority using a malformed router descriptor. Fixes bug
10732 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
10734 - When checking for replays in the INTRODUCE1 cell data for a
10735 (legacy) onion service, correctly detect replays in the RSA-
10736 encrypted part of the cell. We were previously checking for
10737 replays on the entire cell, but those can be circumvented due to
10738 the malleability of Tor's legacy hybrid encryption. This fix helps
10739 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10740 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10743 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
10744 - Fix a use-after-free error that could crash v2 Tor onion services
10745 when they failed to open circuits while expiring introduction
10746 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
10747 also tracked as TROVE-2017-013 and CVE-2017-8823.
10749 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
10750 - When running as a relay, make sure that we never build a path
10751 through ourselves, even in the case where we have somehow lost the
10752 version of our descriptor appearing in the consensus. Fixes part
10753 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
10754 as TROVE-2017-012 and CVE-2017-8822.
10756 o Minor features (bridge, backport from 0.3.1.9):
10757 - Bridges now include notice in their descriptors that they are
10758 bridges, and notice of their distribution status, based on their
10759 publication settings. Implements ticket 18329. For more fine-
10760 grained control of how a bridge is distributed, upgrade to 0.3.2.x
10763 o Minor features (directory authority, backport from 0.3.2.6-alpha):
10764 - Add an IPv6 address for the "bastet" directory authority. Closes
10767 o Minor features (geoip):
10768 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
10771 o Minor features (security, windows, backport from 0.3.1.1-alpha):
10772 - Enable a couple of pieces of Windows hardening: one
10773 (HeapEnableTerminationOnCorruption) that has been on-by-default
10774 since Windows 8, and unavailable before Windows 7; and one
10775 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
10776 affect us, but shouldn't do any harm. Closes ticket 21953.
10778 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
10779 - Avoid unnecessary calls to directory_fetches_from_authorities() on
10780 relays, to prevent spurious address resolutions and descriptor
10781 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
10782 bugfix on in 0.2.8.1-alpha.
10784 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
10785 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
10786 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
10788 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
10789 - When a circuit is marked for close, do not attempt to package any
10790 cells for channels on that circuit. Previously, we would detect
10791 this condition lower in the call stack, when we noticed that the
10792 circuit had no attached channel, and log an annoying message.
10793 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
10795 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
10796 - Avoid a crash when transitioning from client mode to bridge mode.
10797 Previously, we would launch the worker threads whenever our
10798 "public server" mode changed, but not when our "server" mode
10799 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
10801 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
10802 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
10803 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
10806 Changes in version 0.2.8.17 - 2017-12-01
10807 Tor 0.2.8.17 backports important security and stability bugfixes from
10808 later Tor releases. All Tor users should upgrade to this release, or
10809 to another of the releases coming out today.
10811 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
10812 2018. If you need a release with long-term support, please upgrade with
10813 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10815 o Major bugfixes (security, backport from 0.3.2.6-alpha):
10816 - Fix a denial of service bug where an attacker could use a
10817 malformed directory object to cause a Tor instance to pause while
10818 OpenSSL would try to read a passphrase from the terminal. (Tor
10819 instances run without a terminal, which is the case for most Tor
10820 packages, are not impacted.) Fixes bug 24246; bugfix on every
10821 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10822 Found by OSS-Fuzz as testcase 6360145429790720.
10823 - When checking for replays in the INTRODUCE1 cell data for a
10824 (legacy) onion service, correctly detect replays in the RSA-
10825 encrypted part of the cell. We were previously checking for
10826 replays on the entire cell, but those can be circumvented due to
10827 the malleability of Tor's legacy hybrid encryption. This fix helps
10828 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10829 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10832 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
10833 - Fix a use-after-free error that could crash v2 Tor onion services
10834 when they failed to open circuits while expiring introduction
10835 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
10836 also tracked as TROVE-2017-013 and CVE-2017-8823.
10838 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
10839 - When running as a relay, make sure that we never build a path through
10840 ourselves, even in the case where we have somehow lost the version of
10841 our descriptor appearing in the consensus. Fixes part of bug 21534;
10842 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
10845 o Minor features (bridge, backport from 0.3.1.9):
10846 - Bridges now include notice in their descriptors that they are
10847 bridges, and notice of their distribution status, based on their
10848 publication settings. Implements ticket 18329. For more fine-
10849 grained control of how a bridge is distributed, upgrade to 0.3.2.x
10852 o Minor features (directory authority, backport from 0.3.2.6-alpha):
10853 - Add an IPv6 address for the "bastet" directory authority. Closes
10856 o Minor features (geoip):
10857 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
10860 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
10861 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
10862 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
10865 Changes in version 0.2.5.16 - 2017-12-01
10866 Tor 0.2.5.13 backports important security and stability bugfixes from
10867 later Tor releases. All Tor users should upgrade to this release, or
10868 to another of the releases coming out today.
10870 Note: the Tor 0.2.5 series will no longer be supported after 1 May
10871 2018. If you need a release with long-term support, please upgrade to
10872 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10874 o Major bugfixes (security, backport from 0.3.2.6-alpha):
10875 - Fix a denial of service bug where an attacker could use a
10876 malformed directory object to cause a Tor instance to pause while
10877 OpenSSL would try to read a passphrase from the terminal. (Tor
10878 instances run without a terminal, which is the case for most Tor
10879 packages, are not impacted.) Fixes bug 24246; bugfix on every
10880 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10881 Found by OSS-Fuzz as testcase 6360145429790720.
10882 - When checking for replays in the INTRODUCE1 cell data for a
10883 (legacy) onion service, correctly detect replays in the RSA-
10884 encrypted part of the cell. We were previously checking for
10885 replays on the entire cell, but those can be circumvented due to
10886 the malleability of Tor's legacy hybrid encryption. This fix helps
10887 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10888 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10891 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
10892 - When running as a relay, make sure that we never build a path
10893 through ourselves, even in the case where we have somehow lost the
10894 version of our descriptor appearing in the consensus. Fixes part
10895 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
10896 as TROVE-2017-012 and CVE-2017-8822.
10898 o Minor features (bridge, backport from 0.3.1.9):
10899 - Bridges now include notice in their descriptors that they are
10900 bridges, and notice of their distribution status, based on their
10901 publication settings. Implements ticket 18329. For more fine-
10902 grained control of how a bridge is distributed, upgrade to 0.3.2.x
10905 o Minor features (geoip):
10906 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
10910 Changes in version 0.2.5.15 - 2017-10-25
10911 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
10912 series. It also adds a new directory authority, Bastet.
10914 Note: the Tor 0.2.5 series will no longer be supported after 1 May
10915 2018. If you need a release with long-term support, please upgrade to
10916 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10918 o Directory authority changes:
10919 - Add "Bastet" as a ninth directory authority to the default list.
10920 Closes ticket 23910.
10921 - The directory authority "Longclaw" has changed its IP address.
10922 Closes ticket 23592.
10924 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10925 - Avoid an assertion failure bug affecting our implementation of
10926 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10927 handling of "0xx" differs from what we had expected. Fixes bug
10928 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10930 o Minor features (geoip):
10931 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10934 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
10935 - Fix a memset() off the end of an array when packing cells. This
10936 bug should be harmless in practice, since the corrupted bytes are
10937 still in the same structure, and are always padding bytes,
10938 ignored, or immediately overwritten, depending on compiler
10939 behavior. Nevertheless, because the memset()'s purpose is to make
10940 sure that any other cell-handling bugs can't expose bytes to the
10941 network, we need to fix it. Fixes bug 22737; bugfix on
10942 0.2.4.11-alpha. Fixes CID 1401591.
10944 o Build features (backport from 0.3.1.5-alpha):
10945 - Tor's repository now includes a Travis Continuous Integration (CI)
10946 configuration file (.travis.yml). This is meant to help new
10947 developers and contributors who fork Tor to a Github repository be
10948 better able to test their changes, and understand what we expect
10949 to pass. To use this new build feature, you must fork Tor to your
10950 Github account, then go into the "Integrations" menu in the
10951 repository settings for your fork and enable Travis, then push
10952 your changes. Closes ticket 22636.
10955 Changes in version 0.2.8.16 - 2017-10-25
10956 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
10957 series, including a bugfix for a crash issue that had affected relays
10958 under memory pressure. It also adds a new directory authority, Bastet.
10960 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
10961 2018. If you need a release with long-term support, please stick with
10962 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10964 o Directory authority changes:
10965 - Add "Bastet" as a ninth directory authority to the default list.
10966 Closes ticket 23910.
10967 - The directory authority "Longclaw" has changed its IP address.
10968 Closes ticket 23592.
10970 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10971 - Fix a timing-based assertion failure that could occur when the
10972 circuit out-of-memory handler freed a connection's output buffer.
10973 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10975 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10976 - Remove longclaw's IPv6 address, as it will soon change. Authority
10977 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10978 3/8 directory authorities with IPv6 addresses, but there are also
10979 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10981 o Minor features (geoip):
10982 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10986 Changes in version 0.2.9.13 - 2017-10-25
10987 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
10988 series, including a bugfix for a crash issue that had affected relays
10989 under memory pressure. It also adds a new directory authority, Bastet.
10991 o Directory authority changes:
10992 - Add "Bastet" as a ninth directory authority to the default list.
10993 Closes ticket 23910.
10994 - The directory authority "Longclaw" has changed its IP address.
10995 Closes ticket 23592.
10997 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10998 - Fix a timing-based assertion failure that could occur when the
10999 circuit out-of-memory handler freed a connection's output buffer.
11000 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
11002 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
11003 - Remove longclaw's IPv6 address, as it will soon change. Authority
11004 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
11005 3/8 directory authorities with IPv6 addresses, but there are also
11006 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
11008 o Minor features (geoip):
11009 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
11012 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
11013 - When a directory authority rejects a descriptor or extrainfo with
11014 a given digest, mark that digest as undownloadable, so that we do
11015 not attempt to download it again over and over. We previously
11016 tried to avoid downloading such descriptors by other means, but we
11017 didn't notice if we accidentally downloaded one anyway. This
11018 behavior became problematic in 0.2.7.2-alpha, when authorities
11019 began pinning Ed25519 keys. Fixes bug 22349; bugfix
11022 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
11023 - Clear the address when node_get_prim_orport() returns early.
11024 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
11026 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
11027 - When running as a Windows service, set the ID of the main thread
11028 correctly. Failure to do so made us fail to send log messages to
11029 the controller in 0.2.1.16-rc, slowed down controller event
11030 delivery in 0.2.7.3-rc and later, and crash with an assertion
11031 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
11032 Patch and diagnosis from "Vort".
11035 Changes in version 0.3.0.12 - 2017-10-25
11036 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
11037 series, including a bugfix for a crash issue that had affected relays
11038 under memory pressure. It also adds a new directory authority, Bastet.
11040 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
11041 2018. If you need a release with long-term support, please stick with
11042 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11044 o Directory authority changes:
11045 - Add "Bastet" as a ninth directory authority to the default list.
11046 Closes ticket 23910.
11047 - The directory authority "Longclaw" has changed its IP address.
11048 Closes ticket 23592.
11050 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
11051 - Fix a timing-based assertion failure that could occur when the
11052 circuit out-of-memory handler freed a connection's output buffer.
11053 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
11055 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
11056 - Remove longclaw's IPv6 address, as it will soon change. Authority
11057 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
11058 3/8 directory authorities with IPv6 addresses, but there are also
11059 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
11061 o Minor features (geoip):
11062 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
11065 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
11066 - When a directory authority rejects a descriptor or extrainfo with
11067 a given digest, mark that digest as undownloadable, so that we do
11068 not attempt to download it again over and over. We previously
11069 tried to avoid downloading such descriptors by other means, but we
11070 didn't notice if we accidentally downloaded one anyway. This
11071 behavior became problematic in 0.2.7.2-alpha, when authorities
11072 began pinning Ed25519 keys. Fixes bug 22349; bugfix
11075 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
11076 - Avoid a possible double close of a circuit by the intro point on
11077 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
11078 bugfix on 0.3.0.1-alpha.
11080 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
11081 - Clear the address when node_get_prim_orport() returns early.
11082 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
11084 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
11085 - When running as a Windows service, set the ID of the main thread
11086 correctly. Failure to do so made us fail to send log messages to
11087 the controller in 0.2.1.16-rc, slowed down controller event
11088 delivery in 0.2.7.3-rc and later, and crash with an assertion
11089 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
11090 Patch and diagnosis from "Vort".
11093 Changes in version 0.3.1.8 - 2017-10-25
11094 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
11095 It includes several bugfixes, including a bugfix for a crash issue
11096 that had affected relays under memory pressure. It also adds
11097 a new directory authority, Bastet.
11099 o Directory authority changes:
11100 - Add "Bastet" as a ninth directory authority to the default list.
11101 Closes ticket 23910.
11102 - The directory authority "Longclaw" has changed its IP address.
11103 Closes ticket 23592.
11105 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
11106 - Fix a timing-based assertion failure that could occur when the
11107 circuit out-of-memory handler freed a connection's output buffer.
11108 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
11110 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
11111 - Remove longclaw's IPv6 address, as it will soon change. Authority
11112 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
11113 3/8 directory authorities with IPv6 addresses, but there are also
11114 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
11116 o Minor features (geoip):
11117 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
11120 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
11121 - Fix a compilation warning when building with zstd support on
11122 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
11123 and fixed by Andreas Stieger.
11125 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
11126 - Handle a pathological case when decompressing Zstandard data when
11127 the output buffer size is zero. Fixes bug 23551; bugfix
11130 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
11131 - Remove the length limit on HTTP status lines that authorities can
11132 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
11134 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
11135 - Avoid a possible double close of a circuit by the intro point on
11136 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
11137 bugfix on 0.3.0.1-alpha.
11139 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
11140 - Clear the address when node_get_prim_orport() returns early.
11141 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
11143 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
11144 - Fix additional channelpadding unit test failures by using mocked
11145 time instead of actual time for all tests. Fixes bug 23608; bugfix
11149 Changes in version 0.2.8.15 - 2017-09-18
11150 Tor 0.2.8.15 backports a collection of bugfixes from later
11153 Most significantly, it includes a fix for TROVE-2017-008, a
11154 security bug that affects hidden services running with the
11155 SafeLogging option disabled. For more information, see
11156 https://trac.torproject.org/projects/tor/ticket/23490
11158 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
11159 2018. We suggest that you upgrade to the latest stable release if
11160 possible. If you can't, we recommend that you upgrade at least to
11161 0.2.9, which will be supported until 2020.
11163 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
11164 - Avoid an assertion failure bug affecting our implementation of
11165 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11166 handling of "0xx" differs from what we had expected. Fixes bug
11167 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11170 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
11173 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
11174 - Backport a fix for an "unused variable" warning that appeared
11175 in some versions of mingw. Fixes bug 22838; bugfix on
11178 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
11179 - Fix a memset() off the end of an array when packing cells. This
11180 bug should be harmless in practice, since the corrupted bytes are
11181 still in the same structure, and are always padding bytes,
11182 ignored, or immediately overwritten, depending on compiler
11183 behavior. Nevertheless, because the memset()'s purpose is to make
11184 sure that any other cell-handling bugs can't expose bytes to the
11185 network, we need to fix it. Fixes bug 22737; bugfix on
11186 0.2.4.11-alpha. Fixes CID 1401591.
11188 o Build features (backport from 0.3.1.5-alpha):
11189 - Tor's repository now includes a Travis Continuous Integration (CI)
11190 configuration file (.travis.yml). This is meant to help new
11191 developers and contributors who fork Tor to a Github repository be
11192 better able to test their changes, and understand what we expect
11193 to pass. To use this new build feature, you must fork Tor to your
11194 Github account, then go into the "Integrations" menu in the
11195 repository settings for your fork and enable Travis, then push
11196 your changes. Closes ticket 22636.
11199 Changes in version 0.2.9.12 - 2017-09-18
11200 Tor 0.2.9.12 backports a collection of bugfixes from later
11203 Most significantly, it includes a fix for TROVE-2017-008, a
11204 security bug that affects hidden services running with the
11205 SafeLogging option disabled. For more information, see
11206 https://trac.torproject.org/projects/tor/ticket/23490
11208 o Major features (security, backport from 0.3.0.2-alpha):
11209 - Change the algorithm used to decide DNS TTLs on client and server
11210 side, to better resist DNS-based correlation attacks like the
11211 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
11212 Feamster. Now relays only return one of two possible DNS TTL
11213 values, and clients are willing to believe DNS TTL values up to 3
11214 hours long. Closes ticket 19769.
11216 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
11217 - Fix a rare crash when sending a begin cell on a circuit whose
11218 linked directory connection had already been closed. Fixes bug
11219 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
11221 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
11222 - Fix a bug that prevented exit nodes from caching DNS records for
11223 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
11225 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
11226 - Fix a typo that had prevented TPROXY-based transparent proxying
11227 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
11228 Patch from "d4fq0fQAgoJ".
11230 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
11231 - Avoid an assertion failure bug affecting our implementation of
11232 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11233 handling of "0xx" differs from what we had expected. Fixes bug
11234 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11236 o Minor features (code style, backport from 0.3.1.3-alpha):
11237 - Add "Falls through" comments to our codebase, in order to silence
11238 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
11239 Stieger. Closes ticket 22446.
11241 o Minor features (geoip):
11242 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
11245 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
11246 - Roll over monthly accounting at the configured hour and minute,
11247 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
11248 Found by Andrey Karpov with PVS-Studio.
11250 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
11251 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
11252 bugfix on 0.2.8.1-alpha.
11253 - Fix warnings when building with libscrypt and openssl scrypt support
11254 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
11255 - When building with certain versions the mingw C header files, avoid
11256 float-conversion warnings when calling the C functions isfinite(),
11257 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
11259 o Minor bugfixes (compilation, backport from 0.3.1.7):
11260 - Avoid compiler warnings in the unit tests for running tor_sscanf()
11261 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
11263 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
11264 - Backport a fix for an "unused variable" warning that appeared
11265 in some versions of mingw. Fixes bug 22838; bugfix on
11268 o Minor bugfixes (controller, backport from 0.3.1.7):
11269 - Do not crash when receiving a HSPOST command with an empty body.
11270 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
11271 - Do not crash when receiving a POSTDESCRIPTOR command with an
11272 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
11274 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
11275 - Avoid Coverity build warnings related to our BUG() macro. By
11276 default, Coverity treats BUG() as the Linux kernel does: an
11277 instant abort(). We need to override that so our BUG() macro
11278 doesn't prevent Coverity from analyzing functions that use it.
11279 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
11281 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
11282 - Fix a memset() off the end of an array when packing cells. This
11283 bug should be harmless in practice, since the corrupted bytes are
11284 still in the same structure, and are always padding bytes,
11285 ignored, or immediately overwritten, depending on compiler
11286 behavior. Nevertheless, because the memset()'s purpose is to make
11287 sure that any other cell-handling bugs can't expose bytes to the
11288 network, we need to fix it. Fixes bug 22737; bugfix on
11289 0.2.4.11-alpha. Fixes CID 1401591.
11291 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
11292 - When setting the maximum number of connections allowed by the OS,
11293 always allow some extra file descriptors for other files. Fixes
11294 bug 22797; bugfix on 0.2.0.10-alpha.
11296 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
11297 - Avoid a sandbox failure when trying to re-bind to a socket and
11298 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
11300 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
11301 - Permit the fchmod system call, to avoid crashing on startup when
11302 starting with the seccomp2 sandbox and an unexpected set of
11303 permissions on the data directory or its contents. Fixes bug
11304 22516; bugfix on 0.2.5.4-alpha.
11306 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
11307 - Avoid a double-marked-circuit warning that could happen when we
11308 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
11311 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
11312 - Reject version numbers with non-numeric prefixes (such as +, -, or
11313 whitespace). Disallowing whitespace prevents differential version
11314 parsing between POSIX-based and Windows platforms. Fixes bug 21507
11315 and part of 21508; bugfix on 0.0.8pre1.
11317 o Build features (backport from 0.3.1.5-alpha):
11318 - Tor's repository now includes a Travis Continuous Integration (CI)
11319 configuration file (.travis.yml). This is meant to help new
11320 developers and contributors who fork Tor to a Github repository be
11321 better able to test their changes, and understand what we expect
11322 to pass. To use this new build feature, you must fork Tor to your
11323 Github account, then go into the "Integrations" menu in the
11324 repository settings for your fork and enable Travis, then push
11325 your changes. Closes ticket 22636.
11328 Changes in version 0.3.0.11 - 2017-09-18
11329 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
11332 Most significantly, it includes a fix for TROVE-2017-008, a
11333 security bug that affects hidden services running with the
11334 SafeLogging option disabled. For more information, see
11335 https://trac.torproject.org/projects/tor/ticket/23490
11337 o Minor features (code style, backport from 0.3.1.7):
11338 - Add "Falls through" comments to our codebase, in order to silence
11339 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
11340 Stieger. Closes ticket 22446.
11343 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
11346 o Minor bugfixes (compilation, backport from 0.3.1.7):
11347 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
11348 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
11350 o Minor bugfixes (controller, backport from 0.3.1.7):
11351 - Do not crash when receiving a HSPOST command with an empty body.
11352 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
11353 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
11354 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
11356 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
11357 - When setting the maximum number of connections allowed by the OS,
11358 always allow some extra file descriptors for other files. Fixes
11359 bug 22797; bugfix on 0.2.0.10-alpha.
11361 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
11362 - Remove a forgotten debugging message when an introduction point
11363 successfully establishes a hidden service prop224 circuit with
11365 - Change three other log_warn() for an introduction point to
11366 protocol warnings, because they can be failure from the network
11367 and are not relevant to the operator. Fixes bug 23078; bugfix on
11368 0.3.0.1-alpha and 0.3.0.2-alpha.
11371 Changes in version 0.3.1.7 - 2017-09-18
11372 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
11374 With the 0.3.1 series, Tor now serves and downloads directory
11375 information in more compact formats, to save on bandwidth overhead. It
11376 also contains a new padding system to resist netflow-based traffic
11377 analysis, and experimental support for building parts of Tor in Rust
11378 (though no parts of Tor are in Rust yet). There are also numerous
11379 small features, bugfixes on earlier release series, and groundwork for
11380 the hidden services revamp of 0.3.2.
11382 This release also includes a fix for TROVE-2017-008, a security bug
11383 that affects hidden services running with the SafeLogging option
11384 disabled. For more information, see
11385 https://trac.torproject.org/projects/tor/ticket/23490
11387 Per our stable release policy, we plan to support each stable release
11388 series for at least the next nine months, or for three months after
11389 the first stable release of the next series: whichever is longer. If
11390 you need a release with long-term support, we recommend that you stay
11391 with the 0.2.9 series.
11393 Below is a list of the changes since 0.3.0. For a list of all
11394 changes since 0.3.1.6-rc, see the ChangeLog file.
11396 o New dependencies:
11397 - To build with zstd and lzma support, Tor now requires the
11398 pkg-config tool at build time.
11400 o Major bugfixes (security, hidden services, loggging):
11401 - Fix a bug where we could log uninitialized stack when a certain
11402 hidden service error occurred while SafeLogging was disabled.
11403 Fixes bug #23490; bugfix on 0.2.7.2-alpha.
11404 This is also tracked as TROVE-2017-008 and CVE-2017-0380.
11406 o Major features (build system, continuous integration):
11407 - Tor's repository now includes a Travis Continuous Integration (CI)
11408 configuration file (.travis.yml). This is meant to help new
11409 developers and contributors who fork Tor to a Github repository be
11410 better able to test their changes, and understand what we expect
11411 to pass. To use this new build feature, you must fork Tor to your
11412 Github account, then go into the "Integrations" menu in the
11413 repository settings for your fork and enable Travis, then push
11414 your changes. Closes ticket 22636.
11416 o Major features (directory protocol):
11417 - Tor relays and authorities can now serve clients an abbreviated
11418 version of the consensus document, containing only the changes
11419 since an older consensus document that the client holds. Clients
11420 now request these documents when available. When both client and
11421 server use this new protocol, they will use far less bandwidth (up
11422 to 94% less) to keep the client's consensus up-to-date. Implements
11423 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
11424 - Tor can now compress directory traffic with lzma or with zstd
11425 compression algorithms, which can deliver better bandwidth
11426 performance. Because lzma is computationally expensive, it's only
11427 used for documents that can be compressed once and served many
11428 times. Support for these algorithms requires that tor is built
11429 with the libzstd and/or liblzma libraries available. Implements
11430 proposal 278; closes ticket 21662.
11431 - Relays now perform the more expensive compression operations, and
11432 consensus diff generation, in worker threads. This separation
11433 avoids delaying the main thread when a new consensus arrives.
11435 o Major features (experimental):
11436 - Tor can now build modules written in Rust. To turn this on, pass
11437 the "--enable-rust" flag to the configure script. It's not time to
11438 get excited yet: currently, there is no actual Rust functionality
11439 beyond some simple glue code, and a notice at startup to tell you
11440 that Rust is running. Still, we hope that programmers and
11441 packagers will try building Tor with Rust support, so that we can
11442 find issues and solve portability problems. Closes ticket 22106.
11444 o Major features (traffic analysis resistance):
11445 - Connections between clients and relays now send a padding cell in
11446 each direction every 1.5 to 9.5 seconds (tunable via consensus
11447 parameters). This padding will not resist specialized
11448 eavesdroppers, but it should be enough to make many ISPs' routine
11449 network flow logging less useful in traffic analysis against
11452 Padding is negotiated using Tor's link protocol, so both relays
11453 and clients must upgrade for this to take effect. Clients may
11454 still send padding despite the relay's version by setting
11455 ConnectionPadding 1 in torrc, and may disable padding by setting
11456 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
11457 users with the torrc option ReducedConnectionPadding. Implements
11458 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
11459 - Relays will publish 24 hour totals of padding and non-padding cell
11460 counts to their extra-info descriptors, unless PaddingStatistics 0
11461 is set in torrc. These 24 hour totals are also rounded to
11462 multiples of 10000.
11464 o Major bugfixes (hidden service, relay, security):
11465 - Fix a remotely triggerable assertion failure when a hidden service
11466 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
11467 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
11468 - Fix a remotely triggerable assertion failure caused by receiving a
11469 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11470 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11473 o Major bugfixes (path selection, security):
11474 - When choosing which guard to use for a circuit, avoid the exit's
11475 family along with the exit itself. Previously, the new guard
11476 selection logic avoided the exit, but did not consider its family.
11477 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
11478 006 and CVE-2017-0377.
11480 o Major bugfixes (connection usage):
11481 - We use NETINFO cells to try to determine if both relays involved
11482 in a connection will agree on the canonical status of that
11483 connection. We prefer the connections where this is the case for
11484 extend cells, and try to close connections where relays disagree
11485 on their canonical status early. Also, we now prefer the oldest
11486 valid connection for extend cells. These two changes should reduce
11487 the number of long-term connections that are kept open between
11488 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
11489 - Relays now log hourly statistics (look for
11490 "channel_check_for_duplicates" lines) on the total number of
11491 connections to other relays. If the number of connections per
11492 relay is unexpectedly large, this log message is at notice level.
11493 Otherwise it is at info.
11495 o Major bugfixes (entry guards):
11496 - When starting with an old consensus, do not add new entry guards
11497 unless the consensus is "reasonably live" (under 1 day old). Fixes
11498 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
11499 - Don't block bootstrapping when a primary bridge is offline and we
11500 can't get its descriptor. Fixes bug 22325; fixes one case of bug
11501 21969; bugfix on 0.3.0.3-alpha.
11503 o Major bugfixes (linux TPROXY support):
11504 - Fix a typo that had prevented TPROXY-based transparent proxying
11505 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
11506 Patch from "d4fq0fQAgoJ".
11508 o Major bugfixes (openbsd, denial-of-service):
11509 - Avoid an assertion failure bug affecting our implementation of
11510 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11511 handling of "0xx" differs from what we had expected. Fixes bug
11512 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11514 o Major bugfixes (relay, link handshake):
11515 - When performing the v3 link handshake on a TLS connection, report
11516 that we have the x509 certificate that we actually used on that
11517 connection, even if we have changed certificates since that
11518 connection was first opened. Previously, we would claim to have
11519 used our most recent x509 link certificate, which would sometimes
11520 make the link handshake fail. Fixes one case of bug 22460; bugfix
11523 o Major bugfixes (relays, key management):
11524 - Regenerate link and authentication certificates whenever the key
11525 that signs them changes; also, regenerate link certificates
11526 whenever the signed key changes. Previously, these processes were
11527 only weakly coupled, and we relays could (for minutes to hours)
11528 wind up with an inconsistent set of keys and certificates, which
11529 other relays would not accept. Fixes two cases of bug 22460;
11530 bugfix on 0.3.0.1-alpha.
11531 - When sending an Ed25519 signing->link certificate in a CERTS cell,
11532 send the certificate that matches the x509 certificate that we
11533 used on the TLS connection. Previously, there was a race condition
11534 if the TLS context rotated after we began the TLS handshake but
11535 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
11538 o Minor features (security, windows):
11539 - Enable a couple of pieces of Windows hardening: one
11540 (HeapEnableTerminationOnCorruption) that has been on-by-default
11541 since Windows 8, and unavailable before Windows 7; and one
11542 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
11543 affect us, but shouldn't do any harm. Closes ticket 21953.
11545 o Minor features (bridge authority):
11546 - Add "fingerprint" lines to the networkstatus-bridges file produced
11547 by bridge authorities. Closes ticket 22207.
11549 o Minor features (code style):
11550 - Add "Falls through" comments to our codebase, in order to silence
11551 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
11552 Stieger. Closes ticket 22446.
11554 o Minor features (config options):
11555 - Allow "%include" directives in torrc configuration files. These
11556 directives import the settings from other files, or from all the
11557 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
11558 - Make SAVECONF return an error when overwriting a torrc that has
11559 includes. Using SAVECONF with the FORCE option will allow it to
11560 overwrite torrc even if includes are used. Related to ticket 1922.
11561 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
11562 will work without the FORCE option. Related to ticket 1922.
11564 o Minor features (controller):
11565 - Warn the first time that a controller requests data in the long-
11566 deprecated 'GETINFO network-status' format. Closes ticket 21703.
11568 o Minor features (defaults):
11569 - The default value for UseCreateFast is now 0: clients which
11570 haven't yet received a consensus document will now use a proper
11571 ntor handshake to talk to their directory servers whenever they
11572 can. Closes ticket 21407.
11573 - Onion key rotation and expiry intervals are now defined as a
11574 network consensus parameter, per proposal 274. The default
11575 lifetime of an onion key is increased from 7 to 28 days. Old onion
11576 keys will expire after 7 days by default. This change will make
11577 consensus diffs much smaller, and save significant bandwidth.
11578 Closes ticket 21641.
11580 o Minor features (defensive programming):
11581 - Create a pair of consensus parameters, nf_pad_tor2web and
11582 nf_pad_single_onion, to disable netflow padding in the consensus
11583 for non-anonymous connections in case the overhead is high. Closes
11586 o Minor features (diagnostic):
11587 - Add a stack trace to the bug warnings that can be logged when
11588 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
11589 attempt for bug 23105.
11590 - Add logging messages to try to diagnose a rare bug that seems to
11591 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
11592 think this is happening because of incorrect system clocks, but
11593 we'd like to know for certain. Diagnostic for bug 22466.
11594 - Avoid an assertion failure, and log a better error message, when
11595 unable to remove a file from the consensus cache on Windows.
11596 Attempts to mitigate and diagnose bug 22752.
11598 o Minor features (directory authority):
11599 - Improve the message that authorities report to relays that present
11600 RSA/Ed25519 keypairs that conflict with previously pinned keys.
11601 Closes ticket 22348.
11603 o Minor features (directory cache, consensus diff):
11604 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
11605 operators with low-resource environments to adjust the number of
11606 consensuses they'll store and generate diffs from. Most cache
11607 operators should leave it unchanged. Helps to work around
11610 o Minor features (fallback directory list):
11611 - Update the fallback directory mirror whitelist and blacklist based
11612 on operator emails. Closes task 21121.
11613 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11614 December 2016 (of which ~126 were still functional) with a list of
11615 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11616 2017. Resolves ticket 21564.
11618 o Minor features (geoip):
11619 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
11622 o Minor features (hidden services, logging):
11623 - Log a message when a hidden service descriptor has fewer
11624 introduction points than specified in
11625 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
11626 - Log a message when a hidden service reaches its introduction point
11627 circuit limit, and when that limit is reset. Follow up to ticket
11628 21594; closes ticket 21622.
11629 - Warn user if multiple entries in EntryNodes and at least one
11630 HiddenService are used together. Pinning EntryNodes along with a
11631 hidden service can be possibly harmful; for instance see ticket
11632 14917 or 21155. Closes ticket 21155.
11634 o Minor features (linux seccomp2 sandbox):
11635 - We now have a document storage backend compatible with the Linux
11636 seccomp2 sandbox. This backend is used for consensus documents and
11637 diffs between them; in the long term, we'd like to use it for
11638 unparseable directory material too. Closes ticket 21645
11639 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
11640 from 1MB to 16MB. This was necessary with the glibc allocator in
11641 order to allow worker threads to allocate more memory -- which in
11642 turn is necessary because of our new use of worker threads for
11643 compression. Closes ticket 22096.
11645 o Minor features (logging):
11646 - Log files are no longer created world-readable by default.
11647 (Previously, most distributors would store the logs in a non-
11648 world-readable location to prevent inappropriate access. This
11649 change is an extra precaution.) Closes ticket 21729; patch
11652 o Minor features (performance):
11653 - Our Keccak (SHA-3) implementation now accesses memory more
11654 efficiently, especially on little-endian systems. Closes
11656 - Add an O(1) implementation of channel_find_by_global_id(), to
11657 speed some controller functions.
11659 o Minor features (relay, configuration):
11660 - The MyFamily option may now be repeated as many times as desired,
11661 for relays that want to configure large families. Closes ticket
11662 4998; patch by Daniel Pinto.
11664 o Minor features (relay, performance):
11665 - Always start relays with at least two worker threads, to prevent
11666 priority inversion on slow tasks. Part of the fix for bug 22883.
11667 - Allow background work to be queued with different priorities, so
11668 that a big pile of slow low-priority jobs will not starve out
11669 higher priority jobs. This lays the groundwork for a fix for
11672 o Minor features (safety):
11673 - Add an explicit check to extrainfo_parse_entry_from_string() for
11674 NULL inputs. We don't believe this can actually happen, but it may
11675 help silence a warning from the Clang analyzer. Closes
11678 o Minor features (testing):
11679 - Add more tests for compression backend initialization. Closes
11681 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
11682 When Tor is compiled with this option, we disable a number of
11683 redundant memory-safety failsafes that are intended to stop bugs
11684 from becoming security issues. This makes it easier to hunt for
11685 bugs that would be security issues without the failsafes turned
11686 on. Closes ticket 21439.
11687 - Add a general event-tracing instrumentation support to Tor. This
11688 subsystem will enable developers and researchers to add fine-
11689 grained instrumentation to their Tor instances, for use when
11690 examining Tor network performance issues. There are no trace
11691 events yet, and event-tracing is off by default unless enabled at
11692 compile time. Implements ticket 13802.
11693 - Improve our version parsing tests: add tests for typical version
11694 components, add tests for invalid versions, including numeric
11695 range and non-numeric prefixes. Unit tests 21278, 21450, and
11696 21507. Partially implements 21470.
11698 o Minor bugfixes (bandwidth accounting):
11699 - Roll over monthly accounting at the configured hour and minute,
11700 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
11701 Found by Andrey Karpov with PVS-Studio.
11703 o Minor bugfixes (code correctness):
11704 - Accurately identify client connections by their lack of peer
11705 authentication. This means that we bail out earlier if asked to
11706 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
11709 o Minor bugfixes (compilation warnings):
11710 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
11711 22915; bugfix on 0.2.8.1-alpha.
11712 - Fix warnings when building with libscrypt and openssl scrypt
11713 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
11714 - When building with certain versions of the mingw C header files,
11715 avoid float-conversion warnings when calling the C functions
11716 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
11719 o Minor bugfixes (compilation):
11720 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
11721 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
11723 o Minor bugfixes (compression):
11724 - When spooling compressed data to an output buffer, don't try to
11725 spool more data when there is no more data to spool and we are not
11726 trying to flush the input. Previously, we would sometimes launch
11727 compression requests with nothing to do, which interferes with our
11728 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
11730 o Minor bugfixes (configuration):
11731 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
11732 bug 22252; bugfix on 0.2.9.3-alpha.
11734 o Minor bugfixes (connection lifespan):
11735 - Allow more control over how long TLS connections are kept open:
11736 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
11737 single option called CircuitsAvailableTimeout. Also, allow the
11738 consensus to control the default values for both this preference
11739 and the lifespan of relay-to-relay connections. Fixes bug 17592;
11740 bugfix on 0.2.5.5-alpha.
11741 - Increase the initial circuit build timeout testing frequency, to
11742 help ensure that ReducedConnectionPadding clients finish learning
11743 a timeout before their orconn would expire. The initial testing
11744 rate was set back in the days of TAP and before the Tor Browser
11745 updater, when we had to be much more careful about new clients
11746 making lots of circuits. With this change, a circuit build timeout
11747 is learned in about 15-20 minutes, instead of 100-120 minutes.
11749 o Minor bugfixes (controller):
11750 - Do not crash when receiving a HSPOST command with an empty body.
11751 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
11752 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
11753 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
11754 - GETINFO onions/current and onions/detached no longer respond with
11755 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
11756 - Trigger HS descriptor events on the control port when the client
11757 fails to pick a hidden service directory for a hidden service.
11758 This can happen if all the hidden service directories are in
11759 ExcludeNodes, or they have all been queried within the last 15
11760 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
11762 o Minor bugfixes (correctness):
11763 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11764 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11766 o Minor bugfixes (coverity build support):
11767 - Avoid Coverity build warnings related to our BUG() macro. By
11768 default, Coverity treats BUG() as the Linux kernel does: an
11769 instant abort(). We need to override that so our BUG() macro
11770 doesn't prevent Coverity from analyzing functions that use it.
11771 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
11773 o Minor bugfixes (defensive programming):
11774 - Detect and break out of infinite loops in our compression code. We
11775 don't think that any such loops exist now, but it's best to be
11776 safe. Closes ticket 22672.
11777 - Fix a memset() off the end of an array when packing cells. This
11778 bug should be harmless in practice, since the corrupted bytes are
11779 still in the same structure, and are always padding bytes,
11780 ignored, or immediately overwritten, depending on compiler
11781 behavior. Nevertheless, because the memset()'s purpose is to make
11782 sure that any other cell-handling bugs can't expose bytes to the
11783 network, we need to fix it. Fixes bug 22737; bugfix on
11784 0.2.4.11-alpha. Fixes CID 1401591.
11786 o Minor bugfixes (directory authority):
11787 - When a directory authority rejects a descriptor or extrainfo with
11788 a given digest, mark that digest as undownloadable, so that we do
11789 not attempt to download it again over and over. We previously
11790 tried to avoid downloading such descriptors by other means, but we
11791 didn't notice if we accidentally downloaded one anyway. This
11792 behavior became problematic in 0.2.7.2-alpha, when authorities
11793 began pinning Ed25519 keys. Fixes bug 22349; bugfix
11795 - When rejecting a router descriptor for running an obsolete version
11796 of Tor without ntor support, warn about the obsolete tor version,
11797 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
11798 - Prevent the shared randomness subsystem from asserting when
11799 initialized by a bridge authority with an incomplete configuration
11800 file. Fixes bug 21586; bugfix on 0.2.9.8.
11802 o Minor bugfixes (error reporting, windows):
11803 - When formatting Windows error messages, use the English format to
11804 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
11807 o Minor bugfixes (exit-side DNS):
11808 - Fix an untriggerable assertion that checked the output of a
11809 libevent DNS error, so that the assertion actually behaves as
11810 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
11811 Karpov using PVS-Studio.
11813 o Minor bugfixes (fallback directories):
11814 - Make the usage example in updateFallbackDirs.py actually work, and
11815 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
11816 - Decrease the guard flag average required to be a fallback. This
11817 allows us to keep relays that have their guard flag removed when
11818 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
11819 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
11820 bugfix on 0.2.8.1-alpha.
11821 - Make sure fallback directory mirrors have the same address, port,
11822 and relay identity key for at least 30 days before they are
11823 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
11825 o Minor bugfixes (file limits, osx):
11826 - When setting the maximum number of connections allowed by the OS,
11827 always allow some extra file descriptors for other files. Fixes
11828 bug 22797; bugfix on 0.2.0.10-alpha.
11830 o Minor bugfixes (hidden services):
11831 - Increase the number of circuits that a service is allowed to
11832 open over a specific period of time. The value was lower than it
11833 should be (8 vs 12) in the normal case of 3 introduction points.
11834 Fixes bug 22159; bugfix on 0.3.0.5-rc.
11835 - Fix a BUG warning during HSv3 descriptor decoding that could be
11836 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
11837 on 0.3.0.1-alpha. Bug found by "haxxpop".
11838 - Stop printing a cryptic warning when a hidden service gets a
11839 request to connect to a virtual port that it hasn't configured.
11840 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
11841 - Simplify hidden service descriptor creation by using an existing
11842 flag to check if an introduction point is established. Fixes bug
11843 21599; bugfix on 0.2.7.2-alpha.
11845 o Minor bugfixes (link handshake):
11846 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
11847 months, and regenerate it when it is within one month of expiring.
11848 Previously, we had generated this certificate at startup with a
11849 ten-year lifetime, but that could lead to weird behavior when Tor
11850 was started with a grossly inaccurate clock. Mitigates bug 22466;
11851 mitigation on 0.3.0.1-alpha.
11853 o Minor bugfixes (linux seccomp2 sandbox):
11854 - Avoid a sandbox failure when trying to re-bind to a socket and
11855 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
11856 - Permit the fchmod system call, to avoid crashing on startup when
11857 starting with the seccomp2 sandbox and an unexpected set of
11858 permissions on the data directory or its contents. Fixes bug
11859 22516; bugfix on 0.2.5.4-alpha.
11861 o Minor bugfixes (logging):
11862 - When decompressing, do not warn if we fail to decompress using a
11863 compression method that we merely guessed. Fixes part of bug
11864 22670; bugfix on 0.1.1.14-alpha.
11865 - When decompressing, treat mismatch between content-encoding and
11866 actual compression type as a protocol warning. Fixes part of bug
11867 22670; bugfix on 0.1.1.9-alpha.
11868 - Downgrade "assigned_to_cpuworker failed" message to info-level
11869 severity. In every case that can reach it, either a better warning
11870 has already been logged, or no warning is warranted. Fixes bug
11871 22356; bugfix on 0.2.6.3-alpha.
11872 - Log a better message when a directory authority replies to an
11873 upload with an unexpected status code. Fixes bug 11121; bugfix
11875 - Downgrade a log statement about unexpected relay cells from "bug"
11876 to "protocol warning", because there is at least one use case
11877 where it can be triggered by a buggy tor implementation. Fixes bug
11878 21293; bugfix on 0.1.1.14-alpha.
11880 o Minor bugfixes (logging, relay):
11881 - Remove a forgotten debugging message when an introduction point
11882 successfully establishes a hidden service prop224 circuit with
11884 - Change three other log_warn() for an introduction point to
11885 protocol warnings, because they can be failure from the network
11886 and are not relevant to the operator. Fixes bug 23078; bugfix on
11887 0.3.0.1-alpha and 0.3.0.2-alpha.
11889 o Minor bugfixes (relay):
11890 - Inform the geoip and rephist modules about all requests, even on
11891 relays that are only fetching microdescriptors. Fixes a bug
11892 related to 21585; bugfix on 0.3.0.1-alpha.
11894 o Minor bugfixes (memory leaks):
11895 - Fix a small memory leak at exit from the backtrace handler code.
11896 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
11897 - When directory authorities reject a router descriptor due to
11898 keypinning, free the router descriptor rather than leaking the
11899 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
11900 - Fix a small memory leak when validating a configuration that uses
11901 two or more AF_UNIX sockets for the same port type. Fixes bug
11902 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
11904 o Minor bugfixes (process behavior):
11905 - When exiting because of an error, always exit with a nonzero exit
11906 status. Previously, we would fail to report an error in our exit
11907 status in cases related to __OwningControllerProcess failure,
11908 lockfile contention, and Ed25519 key initialization. Fixes bug
11909 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
11910 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
11913 o Minor bugfixes (robustness, error handling):
11914 - Improve our handling of the cases where OpenSSL encounters a
11915 memory error while encoding keys and certificates. We haven't
11916 observed these errors in the wild, but if they do happen, we now
11917 detect and respond better. Fixes bug 19418; bugfix on all versions
11918 of Tor. Reported by Guido Vranken.
11920 o Minor bugfixes (testing):
11921 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
11922 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
11923 - Use unbuffered I/O for utility functions around the
11924 process_handle_t type. This fixes unit test failures reported on
11925 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
11926 - Make display of captured unit test log messages consistent. Fixes
11927 bug 21510; bugfix on 0.2.9.3-alpha.
11928 - Make test-network.sh always call chutney's test-network.sh.
11929 Previously, this only worked on systems which had bash installed,
11930 due to some bash-specific code in the script. Fixes bug 19699;
11931 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
11932 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
11933 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
11934 - The unit tests now pass on systems where localhost is misconfigured
11935 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
11938 o Minor bugfixes (voting consistency):
11939 - Reject version numbers with non-numeric prefixes (such as +, -, or
11940 whitespace). Disallowing whitespace prevents differential version
11941 parsing between POSIX-based and Windows platforms. Fixes bug 21507
11942 and part of 21508; bugfix on 0.0.8pre1.
11944 o Minor bugfixes (Windows service):
11945 - When running as a Windows service, set the ID of the main thread
11946 correctly. Failure to do so made us fail to send log messages to
11947 the controller in 0.2.1.16-rc, slowed down controller event
11948 delivery in 0.2.7.3-rc and later, and crash with an assertion
11949 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
11950 Patch and diagnosis from "Vort".
11952 o Minor bugfixes (windows, relay):
11953 - Resolve "Failure from drain_fd: No error" warnings on Windows
11954 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
11956 o Code simplification and refactoring:
11957 - Break up the 630-line function connection_dir_client_reached_eof()
11958 into a dozen smaller functions. This change should help
11959 maintainability and readability of the client directory code.
11960 - Isolate our use of the openssl headers so that they are only
11961 included from our crypto wrapper modules, and from tests that
11962 examine those modules' internals. Closes ticket 21841.
11963 - Simplify our API to launch directory requests, making it more
11964 extensible and less error-prone. Now it's easier to add extra
11965 headers to directory requests. Closes ticket 21646.
11966 - Our base64 decoding functions no longer overestimate the output
11967 space that they need when parsing unpadded inputs. Closes
11969 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
11970 Resolves ticket 22213.
11971 - The logic that directory caches use to spool request to clients,
11972 serving them one part at a time so as not to allocate too much
11973 memory, has been refactored for consistency. Previously there was
11974 a separate spooling implementation per type of spoolable data. Now
11975 there is one common spooling implementation, with extensible data
11976 types. Closes ticket 21651.
11977 - Tor's compression module now supports multiple backends. Part of
11978 the implementation for proposal 278; closes ticket 21663.
11981 - Add a manpage description for the key-pinning-journal file. Closes
11983 - Correctly note that bandwidth accounting values are stored in the
11984 state file, and the bw_accounting file is now obsolete. Closes
11986 - Document more of the files in the Tor data directory, including
11987 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
11988 approved-routers, sr-random, and diff-cache. Found while fixing
11990 - Clarify the manpage for the (deprecated) torify script. Closes
11992 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
11993 Closes ticket 21873.
11994 - Correct documentation about the default DataDirectory value.
11995 Closes ticket 21151.
11996 - Document the default behavior of NumEntryGuards and
11997 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
11999 - Document key=value pluggable transport arguments for Bridge lines
12000 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
12001 - Note that bandwidth-limiting options don't affect TCP headers or
12002 DNS. Closes ticket 17170.
12004 o Removed features (configuration options, all in ticket 22060):
12005 - These configuration options are now marked Obsolete, and no longer
12006 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
12007 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
12008 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
12009 in 0.2.9.2-alpha and have now been removed. The previous default
12010 behavior is now always chosen; the previous (less secure) non-
12011 default behavior is now unavailable.
12012 - CloseHSClientCircuitsImmediatelyOnTimeout and
12013 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
12014 0.2.9.2-alpha and now have been removed. HS circuits never close
12015 on circuit build timeout; they have a longer timeout period.
12016 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
12017 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
12018 (and others) to configure listen-only and advertise-only addresses.
12020 o Removed features (tools):
12021 - We've removed the tor-checkkey tool from src/tools. Long ago, we
12022 used it to help people detect RSA keys that were generated by
12023 versions of Debian affected by CVE-2008-0166. But those keys have
12024 been out of circulation for ages, and this tool is no longer
12025 required. Closes ticket 21842.
12028 Changes in version 0.3.0.10 - 2017-08-02
12029 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
12030 from the current Tor alpha series. OpenBSD users and TPROXY users
12031 should upgrade; others are probably okay sticking with 0.3.0.9.
12033 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
12034 - Tor's repository now includes a Travis Continuous Integration (CI)
12035 configuration file (.travis.yml). This is meant to help new
12036 developers and contributors who fork Tor to a Github repository be
12037 better able to test their changes, and understand what we expect
12038 to pass. To use this new build feature, you must fork Tor to your
12039 Github account, then go into the "Integrations" menu in the
12040 repository settings for your fork and enable Travis, then push
12041 your changes. Closes ticket 22636.
12043 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
12044 - Fix a typo that had prevented TPROXY-based transparent proxying
12045 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
12046 Patch from "d4fq0fQAgoJ".
12048 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
12049 - Avoid an assertion failure bug affecting our implementation of
12050 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
12051 handling of "0xbar" differs from what we had expected. Fixes bug
12052 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
12054 o Minor features (backport from 0.3.1.5-alpha):
12055 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
12058 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
12059 - Roll over monthly accounting at the configured hour and minute,
12060 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
12061 Found by Andrey Karpov with PVS-Studio.
12063 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
12064 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
12065 bugfix on 0.2.8.1-alpha.
12066 - Fix warnings when building with libscrypt and openssl scrypt
12067 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
12068 - When building with certain versions of the mingw C header files,
12069 avoid float-conversion warnings when calling the C functions
12070 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
12073 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
12074 - Backport a fix for an "unused variable" warning that appeared
12075 in some versions of mingw. Fixes bug 22838; bugfix on
12078 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
12079 - Avoid Coverity build warnings related to our BUG() macro. By
12080 default, Coverity treats BUG() as the Linux kernel does: an
12081 instant abort(). We need to override that so our BUG() macro
12082 doesn't prevent Coverity from analyzing functions that use it.
12083 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
12085 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
12086 - When rejecting a router descriptor for running an obsolete version
12087 of Tor without ntor support, warn about the obsolete tor version,
12088 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
12090 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
12091 - Avoid a sandbox failure when trying to re-bind to a socket and
12092 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
12094 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
12095 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
12096 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
12099 Changes in version 0.3.0.9 - 2017-06-29
12100 Tor 0.3.0.9 fixes a path selection bug that would allow a client
12101 to use a guard that was in the same network family as a chosen exit
12102 relay. This is a security regression; all clients running earlier
12103 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
12106 This release also backports several other bugfixes from the 0.3.1.x
12109 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
12110 - When choosing which guard to use for a circuit, avoid the exit's
12111 family along with the exit itself. Previously, the new guard
12112 selection logic avoided the exit, but did not consider its family.
12113 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
12114 006 and CVE-2017-0377.
12116 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
12117 - Don't block bootstrapping when a primary bridge is offline and we
12118 can't get its descriptor. Fixes bug 22325; fixes one case of bug
12119 21969; bugfix on 0.3.0.3-alpha.
12121 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
12122 - When starting with an old consensus, do not add new entry guards
12123 unless the consensus is "reasonably live" (under 1 day old). Fixes
12124 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
12126 o Minor features (geoip):
12127 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
12130 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
12131 - Reject version numbers with non-numeric prefixes (such as +, -, or
12132 whitespace). Disallowing whitespace prevents differential version
12133 parsing between POSIX-based and Windows platforms. Fixes bug 21507
12134 and part of 21508; bugfix on 0.0.8pre1.
12136 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
12137 - Permit the fchmod system call, to avoid crashing on startup when
12138 starting with the seccomp2 sandbox and an unexpected set of
12139 permissions on the data directory or its contents. Fixes bug
12140 22516; bugfix on 0.2.5.4-alpha.
12142 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
12143 - Fix a memset() off the end of an array when packing cells. This
12144 bug should be harmless in practice, since the corrupted bytes are
12145 still in the same structure, and are always padding bytes,
12146 ignored, or immediately overwritten, depending on compiler
12147 behavior. Nevertheless, because the memset()'s purpose is to make
12148 sure that any other cell-handling bugs can't expose bytes to the
12149 network, we need to fix it. Fixes bug 22737; bugfix on
12150 0.2.4.11-alpha. Fixes CID 1401591.
12153 Changes in version 0.3.0.8 - 2017-06-08
12154 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
12155 remotely crash a hidden service with an assertion failure. Anyone
12156 running a hidden service should upgrade to this version, or to some
12157 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
12159 Tor 0.3.0.8 also includes fixes for several key management bugs
12160 that sometimes made relays unreliable, as well as several other
12161 bugfixes described below.
12163 o Major bugfixes (hidden service, relay, security, backport
12164 from 0.3.1.3-alpha):
12165 - Fix a remotely triggerable assertion failure when a hidden service
12166 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
12167 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
12168 - Fix a remotely triggerable assertion failure caused by receiving a
12169 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12170 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12173 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
12174 - When performing the v3 link handshake on a TLS connection, report
12175 that we have the x509 certificate that we actually used on that
12176 connection, even if we have changed certificates since that
12177 connection was first opened. Previously, we would claim to have
12178 used our most recent x509 link certificate, which would sometimes
12179 make the link handshake fail. Fixes one case of bug 22460; bugfix
12182 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
12183 - Regenerate link and authentication certificates whenever the key
12184 that signs them changes; also, regenerate link certificates
12185 whenever the signed key changes. Previously, these processes were
12186 only weakly coupled, and we relays could (for minutes to hours)
12187 wind up with an inconsistent set of keys and certificates, which
12188 other relays would not accept. Fixes two cases of bug 22460;
12189 bugfix on 0.3.0.1-alpha.
12190 - When sending an Ed25519 signing->link certificate in a CERTS cell,
12191 send the certificate that matches the x509 certificate that we
12192 used on the TLS connection. Previously, there was a race condition
12193 if the TLS context rotated after we began the TLS handshake but
12194 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
12197 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
12198 - Stop rejecting v3 hidden service descriptors because their size
12199 did not match an old padding rule. Fixes bug 22447; bugfix on
12202 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
12203 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
12204 December 2016 (of which ~126 were still functional) with a list of
12205 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
12206 2017. Resolves ticket 21564.
12208 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
12209 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
12210 bug 22252; bugfix on 0.2.9.3-alpha.
12212 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
12213 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12214 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12216 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
12217 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
12218 months, and regenerate it when it is within one month of expiring.
12219 Previously, we had generated this certificate at startup with a
12220 ten-year lifetime, but that could lead to weird behavior when Tor
12221 was started with a grossly inaccurate clock. Mitigates bug 22466;
12222 mitigation on 0.3.0.1-alpha.
12224 o Minor bugfixes (memory leak, directory authority, backport from
12226 - When directory authorities reject a router descriptor due to
12227 keypinning, free the router descriptor rather than leaking the
12228 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
12231 Changes in version 0.2.9.11 - 2017-06-08
12232 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
12233 remotely crash a hidden service with an assertion failure. Anyone
12234 running a hidden service should upgrade to this version, or to some
12235 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
12236 are not affected by TROVE-2017-004.)
12238 Tor 0.2.9.11 also backports fixes for several key management bugs
12239 that sometimes made relays unreliable, as well as several other
12240 bugfixes described below.
12242 o Major bugfixes (hidden service, relay, security, backport
12243 from 0.3.1.3-alpha):
12244 - Fix a remotely triggerable assertion failure caused by receiving a
12245 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12246 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12249 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
12250 - When performing the v3 link handshake on a TLS connection, report
12251 that we have the x509 certificate that we actually used on that
12252 connection, even if we have changed certificates since that
12253 connection was first opened. Previously, we would claim to have
12254 used our most recent x509 link certificate, which would sometimes
12255 make the link handshake fail. Fixes one case of bug 22460; bugfix
12258 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
12259 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
12260 December 2016 (of which ~126 were still functional) with a list of
12261 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
12262 2017. Resolves ticket 21564.
12264 o Minor features (future-proofing, backport from 0.3.0.7):
12265 - Tor no longer refuses to download microdescriptors or descriptors if
12266 they are listed as "published in the future". This change will
12267 eventually allow us to stop listing meaningful "published" dates
12268 in microdescriptor consensuses, and thereby allow us to reduce the
12269 resources required to download consensus diffs by over 50%.
12270 Implements part of ticket 21642; implements part of proposal 275.
12272 o Minor features (directory authorities, backport from 0.3.0.4-rc)
12273 - Directory authorities now reject relays running versions
12274 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
12275 suffer from bug 20499 and don't keep their consensus cache
12276 up-to-date. Resolves ticket 20509.
12278 o Minor features (geoip):
12279 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12282 o Minor bugfixes (control port, backport from 0.3.0.6):
12283 - The GETINFO extra-info/digest/<digest> command was broken because
12284 of a wrong base16 decode return value check, introduced when
12285 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
12287 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
12288 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12289 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12291 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
12292 - The getpid() system call is now permitted under the Linux seccomp2
12293 sandbox, to avoid crashing with versions of OpenSSL (and other
12294 libraries) that attempt to learn the process's PID by using the
12295 syscall rather than the VDSO code. Fixes bug 21943; bugfix
12298 o Minor bugfixes (memory leak, directory authority, backport
12299 from 0.3.1.2-alpha):
12300 - When directory authorities reject a router descriptor due to
12301 keypinning, free the router descriptor rather than leaking the
12302 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
12304 Changes in version 0.2.8.14 - 2017-06-08
12305 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
12306 remotely crash a hidden service with an assertion failure. Anyone
12307 running a hidden service should upgrade to this version, or to some
12308 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
12309 are not affected by TROVE-2017-004.)
12311 o Major bugfixes (hidden service, relay, security):
12312 - Fix a remotely triggerable assertion failure caused by receiving a
12313 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12314 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12317 o Minor features (geoip):
12318 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12321 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
12322 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
12323 December 2016 (of which ~126 were still functional) with a list of
12324 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
12325 2017. Resolves ticket 21564.
12327 o Minor bugfixes (correctness):
12328 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12329 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12331 Changes in version 0.2.7.8 - 2017-06-08
12332 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
12333 remotely crash a hidden service with an assertion failure. Anyone
12334 running a hidden service should upgrade to this version, or to some
12335 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
12336 are not affected by TROVE-2017-004.)
12338 o Major bugfixes (hidden service, relay, security):
12339 - Fix a remotely triggerable assertion failure caused by receiving a
12340 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12341 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12344 o Minor features (geoip):
12345 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12348 o Minor bugfixes (correctness):
12349 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12350 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12353 Changes in version 0.2.6.12 - 2017-06-08
12354 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
12355 remotely crash a hidden service with an assertion failure. Anyone
12356 running a hidden service should upgrade to this version, or to some
12357 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
12358 are not affected by TROVE-2017-004.)
12360 o Major bugfixes (hidden service, relay, security):
12361 - Fix a remotely triggerable assertion failure caused by receiving a
12362 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12363 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12366 o Minor features (geoip):
12367 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12370 o Minor bugfixes (correctness):
12371 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12372 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12374 Changes in version 0.2.5.14 - 2017-06-08
12375 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
12376 remotely crash a hidden service with an assertion failure. Anyone
12377 running a hidden service should upgrade to this version, or to some
12378 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
12379 are not affected by TROVE-2017-004.)
12381 o Major bugfixes (hidden service, relay, security):
12382 - Fix a remotely triggerable assertion failure caused by receiving a
12383 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12384 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12387 o Minor features (geoip):
12388 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12391 o Minor bugfixes (correctness):
12392 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12393 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12395 Changes in version 0.2.4.29 - 2017-06-08
12396 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
12397 remotely crash a hidden service with an assertion failure. Anyone
12398 running a hidden service should upgrade to this version, or to some
12399 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
12400 are not affected by TROVE-2017-004.)
12402 o Major bugfixes (hidden service, relay, security):
12403 - Fix a remotely triggerable assertion failure caused by receiving a
12404 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12405 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12408 o Minor features (geoip):
12409 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12412 o Minor bugfixes (correctness):
12413 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12414 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12417 Changes in version 0.3.0.7 - 2017-05-15
12418 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
12419 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
12420 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
12421 clients are not affected.
12423 o Major bugfixes (hidden service directory, security):
12424 - Fix an assertion failure in the hidden service directory code, which
12425 could be used by an attacker to remotely cause a Tor relay process to
12426 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
12427 should upgrade. This security issue is tracked as TROVE-2017-002.
12428 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
12431 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12434 o Minor features (future-proofing):
12435 - Tor no longer refuses to download microdescriptors or descriptors
12436 if they are listed as "published in the future". This change will
12437 eventually allow us to stop listing meaningful "published" dates
12438 in microdescriptor consensuses, and thereby allow us to reduce the
12439 resources required to download consensus diffs by over 50%.
12440 Implements part of ticket 21642; implements part of proposal 275.
12442 o Minor bugfixes (Linux seccomp2 sandbox):
12443 - The getpid() system call is now permitted under the Linux seccomp2
12444 sandbox, to avoid crashing with versions of OpenSSL (and other
12445 libraries) that attempt to learn the process's PID by using the
12446 syscall rather than the VDSO code. Fixes bug 21943; bugfix
12450 Changes in version 0.3.0.6 - 2017-04-26
12451 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
12453 With the 0.3.0 series, clients and relays now use Ed25519 keys to
12454 authenticate their link connections to relays, rather than the old
12455 RSA1024 keys that they used before. (Circuit crypto has been
12456 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
12457 the guard selection and replacement algorithm to behave more robustly
12458 in the presence of unreliable networks, and to resist guard-
12461 This series also includes numerous other small features and bugfixes,
12462 along with more groundwork for the upcoming hidden-services revamp.
12464 Per our stable release policy, we plan to support the Tor 0.3.0
12465 release series for at least the next nine months, or for three months
12466 after the first stable release of the 0.3.1 series: whichever is
12467 longer. If you need a release with long-term support, we recommend
12468 that you stay with the 0.2.9 series.
12470 Below are the changes since 0.2.9.10. For a list of only the changes
12471 since 0.3.0.5-rc, see the ChangeLog file.
12473 o Major features (directory authority, security):
12474 - The default for AuthDirPinKeys is now 1: directory authorities
12475 will reject relays where the RSA identity key matches a previously
12476 seen value, but the Ed25519 key has changed. Closes ticket 18319.
12478 o Major features (guard selection algorithm):
12479 - Tor's guard selection algorithm has been redesigned from the
12480 ground up, to better support unreliable networks and restrictive
12481 sets of entry nodes, and to better resist guard-capture attacks by
12482 hostile local networks. Implements proposal 271; closes
12485 o Major features (next-generation hidden services):
12486 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
12487 prop224 aka "Next Generation Hidden Services". Service and clients
12488 don't use this functionality yet. Closes ticket 19043. Based on
12489 initial code by Alec Heifetz.
12490 - Relays now support the HSDir version 3 protocol, so that they can
12491 can store and serve v3 descriptors. This is part of the next-
12492 generation onion service work detailed in proposal 224. Closes
12495 o Major features (protocol, ed25519 identity keys):
12496 - Clients now support including Ed25519 identity keys in the EXTEND2
12497 cells they generate. By default, this is controlled by a consensus
12498 parameter, currently disabled. You can turn this feature on for
12499 testing by setting ExtendByEd25519ID in your configuration. This
12500 might make your traffic appear different than the traffic
12501 generated by other users, however. Implements part of ticket
12502 15056; part of proposal 220.
12503 - Relays now understand requests to extend to other relays by their
12504 Ed25519 identity keys. When an Ed25519 identity key is included in
12505 an EXTEND2 cell, the relay will only extend the circuit if the
12506 other relay can prove ownership of that identity. Implements part
12507 of ticket 15056; part of proposal 220.
12508 - Relays now use Ed25519 to prove their Ed25519 identities and to
12509 one another, and to clients. This algorithm is faster and more
12510 secure than the RSA-based handshake we've been doing until now.
12511 Implements the second big part of proposal 220; Closes
12514 o Major features (security):
12515 - Change the algorithm used to decide DNS TTLs on client and server
12516 side, to better resist DNS-based correlation attacks like the
12517 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
12518 Feamster. Now relays only return one of two possible DNS TTL
12519 values, and clients are willing to believe DNS TTL values up to 3
12520 hours long. Closes ticket 19769.
12522 o Major bugfixes (client, onion service, also in 0.2.9.9):
12523 - Fix a client-side onion service reachability bug, where multiple
12524 socks requests to an onion service (or a single slow request)
12525 could cause us to mistakenly mark some of the service's
12526 introduction points as failed, and we cache that failure so
12527 eventually we run out and can't reach the service. Also resolves a
12528 mysterious "Remote server sent bogus reason code 65021" log
12529 warning. The bug was introduced in ticket 17218, where we tried to
12530 remember the circuit end reason as a uint16_t, which mangled
12531 negative values. Partially fixes bug 21056 and fixes bug 20307;
12532 bugfix on 0.2.8.1-alpha.
12534 o Major bugfixes (crash, directory connections):
12535 - Fix a rare crash when sending a begin cell on a circuit whose
12536 linked directory connection had already been closed. Fixes bug
12537 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
12539 o Major bugfixes (directory authority):
12540 - During voting, when marking a relay as a probable sybil, do not
12541 clear its BadExit flag: sybils can still be bad in other ways
12542 too. (We still clear the other flags.) Fixes bug 21108; bugfix
12545 o Major bugfixes (DNS):
12546 - Fix a bug that prevented exit nodes from caching DNS records for
12547 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
12549 o Major bugfixes (IPv6 Exits):
12550 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
12551 any IPv6 addresses. Instead, only reject a port over IPv6 if the
12552 exit policy rejects that port on more than an IPv6 /16 of
12553 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
12554 which rejected a relay's own IPv6 address by default. Fixes bug
12555 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
12557 o Major bugfixes (parsing):
12558 - Fix an integer underflow bug when comparing malformed Tor
12559 versions. This bug could crash Tor when built with
12560 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12561 0.2.9.8, which were built with -ftrapv by default. In other cases
12562 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12563 on 0.0.8pre1. Found by OSS-Fuzz.
12564 - When parsing a malformed content-length field from an HTTP
12565 message, do not read off the end of the buffer. This bug was a
12566 potential remote denial-of-service attack against Tor clients and
12567 relays. A workaround was released in October 2016, to prevent this
12568 bug from crashing Tor. This is a fix for the underlying issue,
12569 which should no longer matter (if you applied the earlier patch).
12570 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
12571 using AFL (http://lcamtuf.coredump.cx/afl/).
12573 o Major bugfixes (scheduler):
12574 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
12575 caused the channel scheduler to behave more or less randomly,
12576 rather than preferring channels with higher-priority circuits.
12577 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
12579 o Major bugfixes (security, also in 0.2.9.9):
12580 - Downgrade the "-ftrapv" option from "always on" to "only on when
12581 --enable-expensive-hardening is provided." This hardening option,
12582 like others, can turn survivable bugs into crashes--and having it
12583 on by default made a (relatively harmless) integer overflow bug
12584 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
12585 bugfix on 0.2.9.1-alpha.
12587 o Minor feature (client):
12588 - Enable IPv6 traffic on the SocksPort by default. To disable this,
12589 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
12591 o Minor feature (fallback scripts):
12592 - Add a check_existing mode to updateFallbackDirs.py, which checks
12593 if fallbacks in the hard-coded list are working. Closes ticket
12594 20174. Patch by haxxpop.
12596 o Minor feature (protocol versioning):
12597 - Add new protocol version for proposal 224. HSIntro now advertises
12598 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
12600 o Minor features (ciphersuite selection):
12601 - Allow relays to accept a wider range of ciphersuites, including
12602 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
12603 - Clients now advertise a list of ciphersuites closer to the ones
12604 preferred by Firefox. Closes part of ticket 15426.
12606 o Minor features (controller):
12607 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
12608 shared-random values to the controller. Closes ticket 19925.
12609 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
12610 rather than "unrecognized." Closes ticket 20389; patch from
12613 o Minor features (controller, configuration):
12614 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
12615 and so on, now comes with a __*Port variant that will not be saved
12616 to the torrc file by the controller's SAVECONF command. This
12617 change allows TorBrowser to set up a single-use domain socket for
12618 each time it launches Tor. Closes ticket 20956.
12619 - The GETCONF command can now query options that may only be
12620 meaningful in context-sensitive lists. This allows the controller
12621 to query the mixed SocksPort/__SocksPort style options introduced
12622 in feature 20956. Implements ticket 21300.
12624 o Minor features (diagnostic, directory client):
12625 - Warn when we find an unexpected inconsistency in directory
12626 download status objects. Prevents some negative consequences of
12629 o Minor features (directory authorities):
12630 - Directory authorities now reject descriptors that claim to be
12631 malformed versions of Tor. Helps prevent exploitation of
12633 - Reject version numbers with components that exceed INT32_MAX.
12634 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
12635 Fixes bug 21450; bugfix on 0.0.8pre1.
12637 o Minor features (directory authority):
12638 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
12639 default) to control whether authorities should try to probe relays
12640 by their Ed25519 link keys. This option will go away in a few
12641 releases--unless we encounter major trouble in our ed25519 link
12642 protocol rollout, in which case it will serve as a safety option.
12644 o Minor features (directory cache):
12645 - Relays and bridges will now refuse to serve the consensus they
12646 have if they know it is too old for a client to use. Closes
12649 o Minor features (ed25519 link handshake):
12650 - Advertise support for the ed25519 link handshake using the
12651 subprotocol-versions mechanism, so that clients can tell which
12652 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
12654 o Minor features (entry guards):
12655 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
12656 break regression tests.
12657 - Require UseEntryGuards when UseBridges is set, in order to make
12658 sure bridges aren't bypassed. Resolves ticket 20502.
12660 o Minor features (fallback directories):
12661 - Allow 3 fallback relays per operator, which is safe now that we
12662 are choosing 200 fallback relays. Closes ticket 20912.
12663 - Annotate updateFallbackDirs.py with the bandwidth and consensus
12664 weight for each candidate fallback. Closes ticket 20878.
12665 - Display the relay fingerprint when downloading consensuses from
12666 fallbacks. Closes ticket 20908.
12667 - Exclude relays affected by bug 20499 from the fallback list.
12668 Exclude relays from the fallback list if they are running versions
12669 known to be affected by bug 20499, or if in our tests they deliver
12670 a stale consensus (i.e. one that expired more than 24 hours ago).
12671 Closes ticket 20539.
12672 - Make it easier to change the output sort order of fallbacks.
12673 Closes ticket 20822.
12674 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
12676 - Require fallback directories to have the same address and port for
12677 7 days (now that we have enough relays with this stability).
12678 Relays whose OnionOO stability timer is reset on restart by bug
12679 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
12680 this issue. Closes ticket 20880; maintains short-term fix
12682 - Require fallbacks to have flags for 90% of the time (weighted
12683 decaying average), rather than 95%. This allows at least 73% of
12684 clients to bootstrap in the first 5 seconds without contacting an
12685 authority. Part of ticket 18828.
12686 - Select 200 fallback directories for each release. Closes
12689 o Minor features (fingerprinting resistance, authentication):
12690 - Extend the length of RSA keys used for TLS link authentication to
12691 2048 bits. (These weren't used for forward secrecy; for forward
12692 secrecy, we used P256.) Closes ticket 13752.
12694 o Minor features (geoip):
12695 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
12698 o Minor features (geoip, also in 0.2.9.9):
12699 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
12702 o Minor features (infrastructure):
12703 - Implement smartlist_add_strdup() function. Replaces the use of
12704 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
12706 o Minor features (linting):
12707 - Enhance the changes file linter to warn on Tor versions that are
12708 prefixed with "tor-". Closes ticket 21096.
12710 o Minor features (logging):
12711 - In several places, describe unset ed25519 keys as "<unset>",
12712 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
12714 o Minor features (portability, compilation):
12715 - Autoconf now checks to determine if OpenSSL structures are opaque,
12716 instead of explicitly checking for OpenSSL version numbers. Part
12718 - Support building with recent LibreSSL code that uses opaque
12719 structures. Closes ticket 21359.
12721 o Minor features (relay):
12722 - We now allow separation of exit and relay traffic to different
12723 source IP addresses, using the OutboundBindAddressExit and
12724 OutboundBindAddressOR options respectively. Closes ticket 17975.
12725 Written by Michael Sonntag.
12727 o Minor features (reliability, crash):
12728 - Try better to detect problems in buffers where they might grow (or
12729 think they have grown) over 2 GB in size. Diagnostic for
12732 o Minor features (testing):
12733 - During 'make test-network-all', if tor logs any warnings, ask
12734 chutney to output them. Requires a recent version of chutney with
12735 the 21572 patch. Implements 21570.
12737 o Minor bugfix (control protocol):
12738 - The reply to a "GETINFO config/names" request via the control
12739 protocol now spells the type "Dependent" correctly. This is a
12740 breaking change in the control protocol. (The field seems to be
12741 ignored by the most common known controllers.) Fixes bug 18146;
12742 bugfix on 0.1.1.4-alpha.
12743 - The GETINFO extra-info/digest/<digest> command was broken because
12744 of a wrong base16 decode return value check, introduced when
12745 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
12747 o Minor bugfix (logging):
12748 - Don't recommend the use of Tor2web in non-anonymous mode.
12749 Recommending Tor2web is a bad idea because the client loses all
12750 anonymity. Tor2web should only be used in specific cases by users
12751 who *know* and understand the issues. Fixes bug 21294; bugfix
12754 o Minor bugfixes (bug resilience):
12755 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
12756 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
12757 Hans Jerry Illikainen.
12759 o Minor bugfixes (build):
12760 - Replace obsolete Autoconf macros with their modern equivalent and
12761 prevent similar issues in the future. Fixes bug 20990; bugfix
12764 o Minor bugfixes (certificate expiration time):
12765 - Avoid using link certificates that don't become valid till some
12766 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
12768 o Minor bugfixes (client):
12769 - Always recover from failures in extend_info_from_node(), in an
12770 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
12771 bugfix on 0.2.3.1-alpha.
12772 - When clients that use bridges start up with a cached consensus on
12773 disk, they were ignoring it and downloading a new one. Now they
12774 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
12776 o Minor bugfixes (code correctness):
12777 - Repair a couple of (unreachable or harmless) cases of the risky
12778 comparison-by-subtraction pattern that caused bug 21278.
12780 o Minor bugfixes (config):
12781 - Don't assert on startup when trying to get the options list and
12782 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
12783 options so of course they aren't ready yet. Fixes bug 21062;
12784 bugfix on 0.2.9.3-alpha.
12786 o Minor bugfixes (configuration):
12787 - Accept non-space whitespace characters after the severity level in
12788 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
12789 - Support "TByte" and "TBytes" units in options given in bytes.
12790 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
12791 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
12793 o Minor bugfixes (configure, autoconf):
12794 - Rename the configure option --enable-expensive-hardening to
12795 --enable-fragile-hardening. Expensive hardening makes the tor
12796 daemon abort when some kinds of issues are detected. Thus, it
12797 makes tor more at risk of remote crashes but safer against RCE or
12798 heartbleed bug category. We now try to explain this issue in a
12799 message from the configure script. Fixes bug 21290; bugfix
12802 o Minor bugfixes (consensus weight):
12803 - Add new consensus method that initializes bw weights to 1 instead
12804 of 0. This prevents a zero weight from making it all the way to
12805 the end (happens in small testing networks) and causing an error.
12806 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
12808 o Minor bugfixes (crash prevention):
12809 - Fix an (currently untriggerable, but potentially dangerous) crash
12810 bug when base32-encoding inputs whose sizes are not a multiple of
12811 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
12813 o Minor bugfixes (dead code):
12814 - Remove a redundant check for PidFile changes at runtime in
12815 options_transition_allowed(): this check is already performed
12816 regardless of whether the sandbox is active. Fixes bug 21123;
12817 bugfix on 0.2.5.4-alpha.
12819 o Minor bugfixes (descriptors):
12820 - Correctly recognise downloaded full descriptors as valid, even
12821 when using microdescriptors as circuits. This affects clients with
12822 FetchUselessDescriptors set, and may affect directory authorities.
12823 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
12825 o Minor bugfixes (directory mirrors):
12826 - Allow relays to use directory mirrors without a DirPort: these
12827 relays need to be contacted over their ORPorts using a begindir
12828 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
12829 - Clarify the message logged when a remote relay is unexpectedly
12830 missing an ORPort or DirPort: users were confusing this with a
12831 local port. Fixes another case of bug 20711; bugfix
12834 o Minor bugfixes (directory system):
12835 - Bridges and relays now use microdescriptors (like clients do)
12836 rather than old-style router descriptors. Now bridges will blend
12837 in with clients in terms of the circuits they build. Fixes bug
12838 6769; bugfix on 0.2.3.2-alpha.
12839 - Download all consensus flavors, descriptors, and authority
12840 certificates when FetchUselessDescriptors is set, regardless of
12841 whether tor is a directory cache or not. Fixes bug 20667; bugfix
12842 on all recent tor versions.
12844 o Minor bugfixes (documentation):
12845 - Update the tor manual page to document every option that can not
12846 be changed while tor is running. Fixes bug 21122.
12848 o Minor bugfixes (ed25519 certificates):
12849 - Correctly interpret ed25519 certificates that would expire some
12850 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
12852 o Minor bugfixes (fallback directories):
12853 - Avoid checking fallback candidates' DirPorts if they are down in
12854 OnionOO. When a relay operator has multiple relays, this
12855 prioritizes relays that are up over relays that are down. Fixes
12856 bug 20926; bugfix on 0.2.8.3-alpha.
12857 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
12858 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
12859 - Stop failing when a relay has no uptime data in
12860 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
12862 o Minor bugfixes (hidden service):
12863 - Clean up the code for expiring intro points with no associated
12864 circuits. It was causing, rarely, a service with some expiring
12865 introduction points to not open enough additional introduction
12866 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
12867 - Resolve two possible underflows which could lead to creating and
12868 closing a lot of introduction point circuits in a non-stop loop.
12869 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
12870 - Stop setting the torrc option HiddenServiceStatistics to "0" just
12871 because we're not a bridge or relay. Instead, we preserve whatever
12872 value the user set (or didn't set). Fixes bug 21150; bugfix
12875 o Minor bugfixes (hidden services):
12876 - Make hidden services check for failed intro point connections,
12877 even when they have exceeded their intro point creation limit.
12878 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
12879 - Make hidden services with 8 to 10 introduction points check for
12880 failed circuits immediately after startup. Previously, they would
12881 wait for 5 minutes before performing their first checks. Fixes bug
12882 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
12883 - Stop ignoring misconfigured hidden services. Instead, refuse to
12884 start tor until the misconfigurations have been corrected. Fixes
12885 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
12888 o Minor bugfixes (IPv6):
12889 - Make IPv6-using clients try harder to find an IPv6 directory
12890 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
12891 - When IPv6 addresses have not been downloaded yet (microdesc
12892 consensus documents don't list relay IPv6 addresses), use hard-
12893 coded addresses for authorities, fallbacks, and configured
12894 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
12895 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
12897 o Minor bugfixes (memory leak at exit):
12898 - Fix a small harmless memory leak at exit of the previously unused
12899 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
12902 o Minor bugfixes (onion services):
12903 - Allow the number of introduction points to be as low as 0, rather
12904 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
12906 o Minor bugfixes (portability):
12907 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
12908 It is supported by OpenBSD itself, and also by most OpenBSD
12909 variants (such as Bitrig). Fixes bug 20980; bugfix
12912 o Minor bugfixes (portability, also in 0.2.9.9):
12913 - Avoid crashing when Tor is built using headers that contain
12914 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
12915 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
12917 - Fix Libevent detection on platforms without Libevent 1 headers
12918 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
12920 o Minor bugfixes (relay):
12921 - Avoid a double-marked-circuit warning that could happen when we
12922 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
12924 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
12925 initializing the keys would reset the DataDirectory to 0700
12926 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
12927 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
12929 o Minor bugfixes (testing):
12930 - Fix Raspbian build issues related to missing socket errno in
12931 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
12932 - Remove undefined behavior from the backtrace generator by removing
12933 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
12934 - Use bash in src/test/test-network.sh. This ensures we reliably
12935 call chutney's newer tools/test-network.sh when available. Fixes
12936 bug 21562; bugfix on 0.2.9.1-alpha.
12938 o Minor bugfixes (tor-resolve):
12939 - The tor-resolve command line tool now rejects hostnames over 255
12940 characters in length. Previously, it would silently truncate them,
12941 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
12942 Patch by "junglefowl".
12944 o Minor bugfixes (unit tests):
12945 - Allow the unit tests to pass even when DNS lookups of bogus
12946 addresses do not fail as expected. Fixes bug 20862 and 20863;
12947 bugfix on unit tests introduced in 0.2.8.1-alpha
12948 through 0.2.9.4-alpha.
12950 o Minor bugfixes (util):
12951 - When finishing writing a file to disk, if we were about to replace
12952 the file with the temporary file created before and we fail to
12953 replace it, remove the temporary file so it doesn't stay on disk.
12954 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
12956 o Minor bugfixes (Windows services):
12957 - Be sure to initialize the monotonic time subsystem before using
12958 it, even when running as an NT service. Fixes bug 21356; bugfix
12961 o Minor bugfixes (Windows):
12962 - Check for getpagesize before using it to mmap files. This fixes
12963 compilation in some MinGW environments. Fixes bug 20530; bugfix on
12964 0.1.2.1-alpha. Reported by "ice".
12966 o Code simplification and refactoring:
12967 - Abolish all global guard context in entrynodes.c; replace with new
12968 guard_selection_t structure as preparation for proposal 271.
12969 Closes ticket 19858.
12970 - Extract magic numbers in circuituse.c into defined variables.
12971 - Introduce rend_service_is_ephemeral() that tells if given onion
12972 service is ephemeral. Replace unclear NULL-checkings for service
12973 directory with this function. Closes ticket 20526.
12974 - Refactor circuit_is_available_for_use to remove unnecessary check.
12975 - Refactor circuit_predict_and_launch_new for readability and
12976 testability. Closes ticket 18873.
12977 - Refactor code to manipulate global_origin_circuit_list into
12978 separate functions. Closes ticket 20921.
12979 - Refactor large if statement in purpose_needs_anonymity to use
12980 switch statement instead. Closes part of ticket 20077.
12981 - Refactor the hashing API to return negative values for errors, as
12982 is done as throughout the codebase. Closes ticket 20717.
12983 - Remove data structures that were used to index or_connection
12984 objects by their RSA identity digests. These structures are fully
12985 redundant with the similar structures used in the
12986 channel abstraction.
12987 - Remove duplicate code in the channel_write_*cell() functions.
12988 Closes ticket 13827; patch from Pingl.
12989 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
12990 use only purpose_needs_anonymity. Closes part of ticket 20077.
12991 - The code to generate and parse EXTEND and EXTEND2 cells has been
12992 replaced with code automatically generated by the
12995 o Documentation (formatting):
12996 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
12997 blocks were incorrectly appearing. Closes ticket 20885.
12999 o Documentation (man page):
13000 - Clarify many options in tor.1 and add some min/max values for
13001 HiddenService options. Closes ticket 21058.
13004 - Change '1' to 'weight_scale' in consensus bw weights calculation
13005 comments, as that is reality. Closes ticket 20273. Patch
13007 - Clarify that when ClientRejectInternalAddresses is enabled (which
13008 is the default), multicast DNS hostnames for machines on the local
13009 network (of the form *.local) are also rejected. Closes
13011 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
13012 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
13013 - Include the "TBits" unit in Tor's man page. Fixes part of bug
13014 20622; bugfix on 0.2.5.1-alpha.
13015 - Small fixes to the fuzzing documentation. Closes ticket 21472.
13016 - Stop the man page from incorrectly stating that HiddenServiceDir
13017 must already exist. Fixes 20486.
13018 - Update the description of the directory server options in the
13019 manual page, to clarify that a relay no longer needs to set
13020 DirPort in order to be a directory cache. Closes ticket 21720.
13022 o Removed features:
13023 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
13024 limit for relays running on a single IP applies to authority IP
13025 addresses as well as to non-authority IP addresses. Closes
13027 - The UseDirectoryGuards torrc option no longer exists: all users
13028 that use entry guards will also use directory guards. Related to
13029 proposal 271; implements part of ticket 20831.
13032 - Add tests for networkstatus_compute_bw_weights_v10.
13033 - Add unit tests circuit_predict_and_launch_new.
13034 - Extract dummy_origin_circuit_new so it can be used by other
13036 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
13037 from "overcaffeinated".
13038 - Perform the coding style checks when running the tests and fail
13039 when coding style violations are found. Closes ticket 5500.
13042 Changes in version 0.2.8.13 - 2017-03-03
13043 Tor 0.2.8.13 backports a security fix from later Tor
13044 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
13045 this release, if for some reason they cannot upgrade to a later
13046 release series, and if they build Tor with the --enable-expensive-hardening
13049 Note that support for Tor 0.2.8.x is ending next year: we will not issue
13050 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
13051 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
13053 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
13054 - Fix an integer underflow bug when comparing malformed Tor
13055 versions. This bug could crash Tor when built with
13056 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13057 0.2.9.8, which were built with -ftrapv by default. In other cases
13058 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13059 on 0.0.8pre1. Found by OSS-Fuzz.
13061 o Minor features (geoip):
13062 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13066 Changes in version 0.2.7.7 - 2017-03-03
13067 Tor 0.2.7.7 backports a number of security fixes from later Tor
13068 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
13069 this release, if for some reason they cannot upgrade to a later
13072 Note that support for Tor 0.2.7.x is ending this year: we will not issue
13073 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
13074 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
13076 o Directory authority changes (backport from 0.2.8.5-rc):
13077 - Urras is no longer a directory authority. Closes ticket 19271.
13079 o Directory authority changes (backport from 0.2.9.2-alpha):
13080 - The "Tonga" bridge authority has been retired; the new bridge
13081 authority is "Bifroest". Closes tickets 19728 and 19690.
13083 o Directory authority key updates (backport from 0.2.8.1-alpha):
13084 - Update the V3 identity key for the dannenberg directory authority:
13085 it was changed on 18 November 2015. Closes task 17906. Patch
13088 o Major bugfixes (parsing, security, backport from 0.2.9.8):
13089 - Fix a bug in parsing that could cause clients to read a single
13090 byte past the end of an allocated region. This bug could be used
13091 to cause hardened clients (built with --enable-expensive-hardening)
13092 to crash if they tried to visit a hostile hidden service. Non-
13093 hardened clients are only affected depending on the details of
13094 their platform's memory allocator. Fixes bug 21018; bugfix on
13095 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13096 2016-12-002 and as CVE-2016-1254.
13098 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
13099 - Stop a crash that could occur when a client running with DNSPort
13100 received a query with multiple address types, and the first
13101 address type was not supported. Found and fixed by Scott Dial.
13102 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
13103 - Prevent a class of security bugs caused by treating the contents
13104 of a buffer chunk as if they were a NUL-terminated string. At
13105 least one such bug seems to be present in all currently used
13106 versions of Tor, and would allow an attacker to remotely crash
13107 most Tor instances, especially those compiled with extra compiler
13108 hardening. With this defense in place, such bugs can't crash Tor,
13109 though we should still fix them as they occur. Closes ticket
13110 20384 (TROVE-2016-10-001).
13112 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
13113 - Avoid a difficult-to-trigger heap corruption attack when extending
13114 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
13115 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
13116 Reported by Guido Vranken.
13118 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
13119 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
13120 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
13122 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
13123 - If OpenSSL fails to generate an RSA key, do not retain a dangling
13124 pointer to the previous (uninitialized) key value. The impact here
13125 should be limited to a difficult-to-trigger crash, if OpenSSL is
13126 running an engine that makes key generation failures possible, or
13127 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
13128 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
13131 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
13132 - Fix an integer underflow bug when comparing malformed Tor
13133 versions. This bug could crash Tor when built with
13134 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13135 0.2.9.8, which were built with -ftrapv by default. In other cases
13136 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13137 on 0.0.8pre1. Found by OSS-Fuzz.
13139 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
13140 - Make memwipe() do nothing when passed a NULL pointer or buffer of
13141 zero size. Check size argument to memwipe() for underflow. Fixes
13142 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
13145 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
13146 - Make Tor survive errors involving connections without a
13147 corresponding event object. Previously we'd fail with an
13148 assertion; now we produce a log message. Related to bug 16248.
13150 o Minor features (geoip):
13151 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13155 Changes in version 0.2.6.11 - 2017-03-03
13156 Tor 0.2.6.11 backports a number of security fixes from later Tor
13157 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
13158 this release, if for some reason they cannot upgrade to a later
13161 Note that support for Tor 0.2.6.x is ending this year: we will not issue
13162 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
13163 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
13165 o Directory authority changes (backport from 0.2.8.5-rc):
13166 - Urras is no longer a directory authority. Closes ticket 19271.
13168 o Directory authority changes (backport from 0.2.9.2-alpha):
13169 - The "Tonga" bridge authority has been retired; the new bridge
13170 authority is "Bifroest". Closes tickets 19728 and 19690.
13172 o Directory authority key updates (backport from 0.2.8.1-alpha):
13173 - Update the V3 identity key for the dannenberg directory authority:
13174 it was changed on 18 November 2015. Closes task 17906. Patch
13177 o Major features (security fixes, backport from 0.2.9.4-alpha):
13178 - Prevent a class of security bugs caused by treating the contents
13179 of a buffer chunk as if they were a NUL-terminated string. At
13180 least one such bug seems to be present in all currently used
13181 versions of Tor, and would allow an attacker to remotely crash
13182 most Tor instances, especially those compiled with extra compiler
13183 hardening. With this defense in place, such bugs can't crash Tor,
13184 though we should still fix them as they occur. Closes ticket
13185 20384 (TROVE-2016-10-001).
13187 o Major bugfixes (parsing, security, backport from 0.2.9.8):
13188 - Fix a bug in parsing that could cause clients to read a single
13189 byte past the end of an allocated region. This bug could be used
13190 to cause hardened clients (built with --enable-expensive-hardening)
13191 to crash if they tried to visit a hostile hidden service. Non-
13192 hardened clients are only affected depending on the details of
13193 their platform's memory allocator. Fixes bug 21018; bugfix on
13194 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13195 2016-12-002 and as CVE-2016-1254.
13197 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
13198 - Stop a crash that could occur when a client running with DNSPort
13199 received a query with multiple address types, and the first
13200 address type was not supported. Found and fixed by Scott Dial.
13201 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
13203 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
13204 - Fix an error that could cause us to read 4 bytes before the
13205 beginning of an openssl string. This bug could be used to cause
13206 Tor to crash on systems with unusual malloc implementations, or
13207 systems with unusual hardening installed. Fixes bug 17404; bugfix
13210 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
13211 - Avoid a difficult-to-trigger heap corruption attack when extending
13212 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
13213 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
13214 Reported by Guido Vranken.
13216 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
13217 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
13218 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
13220 o Major bugfixes (guard selection, backport from 0.2.7.6):
13221 - Actually look at the Guard flag when selecting a new directory
13222 guard. When we implemented the directory guard design, we
13223 accidentally started treating all relays as if they have the Guard
13224 flag during guard selection, leading to weaker anonymity and worse
13225 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
13228 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
13229 - If OpenSSL fails to generate an RSA key, do not retain a dangling
13230 pointer to the previous (uninitialized) key value. The impact here
13231 should be limited to a difficult-to-trigger crash, if OpenSSL is
13232 running an engine that makes key generation failures possible, or
13233 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
13234 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
13237 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
13238 - Fix an integer underflow bug when comparing malformed Tor
13239 versions. This bug could crash Tor when built with
13240 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13241 0.2.9.8, which were built with -ftrapv by default. In other cases
13242 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13243 on 0.0.8pre1. Found by OSS-Fuzz.
13245 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
13246 - Make memwipe() do nothing when passed a NULL pointer or buffer of
13247 zero size. Check size argument to memwipe() for underflow. Fixes
13248 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
13251 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
13252 - Make Tor survive errors involving connections without a
13253 corresponding event object. Previously we'd fail with an
13254 assertion; now we produce a log message. Related to bug 16248.
13256 o Minor features (geoip):
13257 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13260 o Minor bugfixes (compilation, backport from 0.2.7.6):
13261 - Fix a compilation warning with Clang 3.6: Do not check the
13262 presence of an address which can never be NULL. Fixes bug 17781.
13265 Changes in version 0.2.5.13 - 2017-03-03
13266 Tor 0.2.5.13 backports a number of security fixes from later Tor
13267 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
13268 this release, if for some reason they cannot upgrade to a later
13271 Note that support for Tor 0.2.5.x is ending next year: we will not issue
13272 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
13273 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
13275 o Directory authority changes (backport from 0.2.8.5-rc):
13276 - Urras is no longer a directory authority. Closes ticket 19271.
13278 o Directory authority changes (backport from 0.2.9.2-alpha):
13279 - The "Tonga" bridge authority has been retired; the new bridge
13280 authority is "Bifroest". Closes tickets 19728 and 19690.
13282 o Directory authority key updates (backport from 0.2.8.1-alpha):
13283 - Update the V3 identity key for the dannenberg directory authority:
13284 it was changed on 18 November 2015. Closes task 17906. Patch
13287 o Major features (security fixes, backport from 0.2.9.4-alpha):
13288 - Prevent a class of security bugs caused by treating the contents
13289 of a buffer chunk as if they were a NUL-terminated string. At
13290 least one such bug seems to be present in all currently used
13291 versions of Tor, and would allow an attacker to remotely crash
13292 most Tor instances, especially those compiled with extra compiler
13293 hardening. With this defense in place, such bugs can't crash Tor,
13294 though we should still fix them as they occur. Closes ticket
13295 20384 (TROVE-2016-10-001).
13297 o Major bugfixes (parsing, security, backport from 0.2.9.8):
13298 - Fix a bug in parsing that could cause clients to read a single
13299 byte past the end of an allocated region. This bug could be used
13300 to cause hardened clients (built with --enable-expensive-hardening)
13301 to crash if they tried to visit a hostile hidden service. Non-
13302 hardened clients are only affected depending on the details of
13303 their platform's memory allocator. Fixes bug 21018; bugfix on
13304 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13305 2016-12-002 and as CVE-2016-1254.
13307 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
13308 - Stop a crash that could occur when a client running with DNSPort
13309 received a query with multiple address types, and the first
13310 address type was not supported. Found and fixed by Scott Dial.
13311 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
13313 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
13314 - Fix an error that could cause us to read 4 bytes before the
13315 beginning of an openssl string. This bug could be used to cause
13316 Tor to crash on systems with unusual malloc implementations, or
13317 systems with unusual hardening installed. Fixes bug 17404; bugfix
13320 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
13321 - Avoid a difficult-to-trigger heap corruption attack when extending
13322 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
13323 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
13324 Reported by Guido Vranken.
13326 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
13327 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
13328 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
13330 o Major bugfixes (guard selection, backport from 0.2.7.6):
13331 - Actually look at the Guard flag when selecting a new directory
13332 guard. When we implemented the directory guard design, we
13333 accidentally started treating all relays as if they have the Guard
13334 flag during guard selection, leading to weaker anonymity and worse
13335 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
13338 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
13339 - If OpenSSL fails to generate an RSA key, do not retain a dangling
13340 pointer to the previous (uninitialized) key value. The impact here
13341 should be limited to a difficult-to-trigger crash, if OpenSSL is
13342 running an engine that makes key generation failures possible, or
13343 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
13344 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
13347 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
13348 - Fix an integer underflow bug when comparing malformed Tor
13349 versions. This bug could crash Tor when built with
13350 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13351 0.2.9.8, which were built with -ftrapv by default. In other cases
13352 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13353 on 0.0.8pre1. Found by OSS-Fuzz.
13355 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
13356 - Make memwipe() do nothing when passed a NULL pointer or buffer of
13357 zero size. Check size argument to memwipe() for underflow. Fixes
13358 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
13361 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
13362 - Make Tor survive errors involving connections without a
13363 corresponding event object. Previously we'd fail with an
13364 assertion; now we produce a log message. Related to bug 16248.
13366 o Minor features (geoip):
13367 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13370 o Minor bugfixes (compilation, backport from 0.2.7.6):
13371 - Fix a compilation warning with Clang 3.6: Do not check the
13372 presence of an address which can never be NULL. Fixes bug 17781.
13374 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
13375 - Check for failures from crypto_early_init, and refuse to continue.
13376 A previous typo meant that we could keep going with an
13377 uninitialized crypto library, and would have OpenSSL initialize
13378 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
13379 when implementing ticket 4900. Patch by "teor".
13381 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
13382 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13383 a client authorized hidden service. Fixes bug 15823; bugfix
13387 Changes in version 0.2.4.28 - 2017-03-03
13388 Tor 0.2.4.28 backports a number of security fixes from later Tor
13389 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
13390 this release, if for some reason they cannot upgrade to a later
13393 Note that support for Tor 0.2.4.x is ending soon: we will not issue
13394 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
13395 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
13397 o Directory authority changes (backport from 0.2.8.5-rc):
13398 - Urras is no longer a directory authority. Closes ticket 19271.
13400 o Directory authority changes (backport from 0.2.9.2-alpha):
13401 - The "Tonga" bridge authority has been retired; the new bridge
13402 authority is "Bifroest". Closes tickets 19728 and 19690.
13404 o Directory authority key updates (backport from 0.2.8.1-alpha):
13405 - Update the V3 identity key for the dannenberg directory authority:
13406 it was changed on 18 November 2015. Closes task 17906. Patch
13409 o Major features (security fixes, backport from 0.2.9.4-alpha):
13410 - Prevent a class of security bugs caused by treating the contents
13411 of a buffer chunk as if they were a NUL-terminated string. At
13412 least one such bug seems to be present in all currently used
13413 versions of Tor, and would allow an attacker to remotely crash
13414 most Tor instances, especially those compiled with extra compiler
13415 hardening. With this defense in place, such bugs can't crash Tor,
13416 though we should still fix them as they occur. Closes ticket
13417 20384 (TROVE-2016-10-001).
13419 o Major bugfixes (parsing, security, backport from 0.2.9.8):
13420 - Fix a bug in parsing that could cause clients to read a single
13421 byte past the end of an allocated region. This bug could be used
13422 to cause hardened clients (built with --enable-expensive-hardening)
13423 to crash if they tried to visit a hostile hidden service. Non-
13424 hardened clients are only affected depending on the details of
13425 their platform's memory allocator. Fixes bug 21018; bugfix on
13426 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13427 2016-12-002 and as CVE-2016-1254.
13429 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
13430 - Fix an error that could cause us to read 4 bytes before the
13431 beginning of an openssl string. This bug could be used to cause
13432 Tor to crash on systems with unusual malloc implementations, or
13433 systems with unusual hardening installed. Fixes bug 17404; bugfix
13436 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
13437 - Avoid a difficult-to-trigger heap corruption attack when extending
13438 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
13439 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
13440 Reported by Guido Vranken.
13442 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
13443 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
13444 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
13446 o Major bugfixes (guard selection, backport from 0.2.7.6):
13447 - Actually look at the Guard flag when selecting a new directory
13448 guard. When we implemented the directory guard design, we
13449 accidentally started treating all relays as if they have the Guard
13450 flag during guard selection, leading to weaker anonymity and worse
13451 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
13454 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
13455 - If OpenSSL fails to generate an RSA key, do not retain a dangling
13456 pointer to the previous (uninitialized) key value. The impact here
13457 should be limited to a difficult-to-trigger crash, if OpenSSL is
13458 running an engine that makes key generation failures possible, or
13459 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
13460 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
13463 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
13464 - Fix an integer underflow bug when comparing malformed Tor
13465 versions. This bug could crash Tor when built with
13466 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13467 0.2.9.8, which were built with -ftrapv by default. In other cases
13468 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13469 on 0.0.8pre1. Found by OSS-Fuzz.
13471 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
13472 - Make memwipe() do nothing when passed a NULL pointer or buffer of
13473 zero size. Check size argument to memwipe() for underflow. Fixes
13474 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
13477 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
13478 - Make Tor survive errors involving connections without a
13479 corresponding event object. Previously we'd fail with an
13480 assertion; now we produce a log message. Related to bug 16248.
13482 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
13483 - Make it harder for attackers to overload hidden services with
13484 introductions, by blocking multiple introduction requests on the
13485 same circuit. Resolves ticket 15515.
13487 o Minor features (geoip):
13488 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13491 o Minor bugfixes (compilation, backport from 0.2.7.6):
13492 - Fix a compilation warning with Clang 3.6: Do not check the
13493 presence of an address which can never be NULL. Fixes bug 17781.
13495 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
13496 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13497 a client authorized hidden service. Fixes bug 15823; bugfix
13501 Changes in version 0.2.9.10 - 2017-03-01
13502 Tor 0.2.9.10 backports a security fix from later Tor release. It also
13503 includes fixes for some major issues affecting directory authorities,
13504 LibreSSL compatibility, and IPv6 correctness.
13506 The Tor 0.2.9.x release series is now marked as a long-term-support
13507 series. We intend to backport security fixes to 0.2.9.x until at
13508 least January of 2020.
13510 o Major bugfixes (directory authority, 0.3.0.3-alpha):
13511 - During voting, when marking a relay as a probable sybil, do not
13512 clear its BadExit flag: sybils can still be bad in other ways
13513 too. (We still clear the other flags.) Fixes bug 21108; bugfix
13516 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
13517 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
13518 any IPv6 addresses. Instead, only reject a port over IPv6 if the
13519 exit policy rejects that port on more than an IPv6 /16 of
13520 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
13521 which rejected a relay's own IPv6 address by default. Fixes bug
13522 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
13524 o Major bugfixes (parsing, also in 0.3.0.4-rc):
13525 - Fix an integer underflow bug when comparing malformed Tor
13526 versions. This bug could crash Tor when built with
13527 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13528 0.2.9.8, which were built with -ftrapv by default. In other cases
13529 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13530 on 0.0.8pre1. Found by OSS-Fuzz.
13532 o Minor features (directory authorities, also in 0.3.0.4-rc):
13533 - Directory authorities now reject descriptors that claim to be
13534 malformed versions of Tor. Helps prevent exploitation of
13536 - Reject version numbers with components that exceed INT32_MAX.
13537 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
13538 Fixes bug 21450; bugfix on 0.0.8pre1.
13540 o Minor features (geoip):
13541 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13544 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
13545 - Autoconf now checks to determine if OpenSSL structures are opaque,
13546 instead of explicitly checking for OpenSSL version numbers. Part
13548 - Support building with recent LibreSSL code that uses opaque
13549 structures. Closes ticket 21359.
13551 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
13552 - Repair a couple of (unreachable or harmless) cases of the risky
13553 comparison-by-subtraction pattern that caused bug 21278.
13555 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
13556 - The tor-resolve command line tool now rejects hostnames over 255
13557 characters in length. Previously, it would silently truncate them,
13558 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
13559 Patch by "junglefowl".
13562 Changes in version 0.2.9.9 - 2017-01-23
13563 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
13564 cause relays and clients to crash, even if they were not built with
13565 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
13566 versions, and also affects 0.3.0.1-alpha: all relays running an affected
13567 version should upgrade.
13569 This release also resolves a client-side onion service reachability
13570 bug, and resolves a pair of small portability issues.
13572 o Major bugfixes (security):
13573 - Downgrade the "-ftrapv" option from "always on" to "only on when
13574 --enable-expensive-hardening is provided." This hardening option,
13575 like others, can turn survivable bugs into crashes -- and having
13576 it on by default made a (relatively harmless) integer overflow bug
13577 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
13578 bugfix on 0.2.9.1-alpha.
13580 o Major bugfixes (client, onion service):
13581 - Fix a client-side onion service reachability bug, where multiple
13582 socks requests to an onion service (or a single slow request)
13583 could cause us to mistakenly mark some of the service's
13584 introduction points as failed, and we cache that failure so
13585 eventually we run out and can't reach the service. Also resolves a
13586 mysterious "Remote server sent bogus reason code 65021" log
13587 warning. The bug was introduced in ticket 17218, where we tried to
13588 remember the circuit end reason as a uint16_t, which mangled
13589 negative values. Partially fixes bug 21056 and fixes bug 20307;
13590 bugfix on 0.2.8.1-alpha.
13592 o Minor features (geoip):
13593 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
13596 o Minor bugfixes (portability):
13597 - Avoid crashing when Tor is built using headers that contain
13598 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
13599 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
13601 - Fix Libevent detection on platforms without Libevent 1 headers
13602 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
13605 Changes in version 0.2.8.12 - 2016-12-19
13606 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
13607 below) where Tor clients could crash when attempting to visit a
13608 hostile hidden service. Clients are recommended to upgrade as packages
13609 become available for their systems.
13611 It also includes an updated list of fallback directories, backported
13614 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
13615 backported to 0.2.8 in the future.
13617 o Major bugfixes (parsing, security, backported from 0.2.9.8):
13618 - Fix a bug in parsing that could cause clients to read a single
13619 byte past the end of an allocated region. This bug could be used
13620 to cause hardened clients (built with --enable-expensive-hardening)
13621 to crash if they tried to visit a hostile hidden service. Non-
13622 hardened clients are only affected depending on the details of
13623 their platform's memory allocator. Fixes bug 21018; bugfix on
13624 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13625 2016-12-002 and as CVE-2016-1254.
13627 o Minor features (fallback directory list, backported from 0.2.9.8):
13628 - Replace the 81 remaining fallbacks of the 100 originally
13629 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
13630 fallbacks (123 new, 54 existing, 27 removed) generated in December
13631 2016. Resolves ticket 20170.
13633 o Minor features (geoip, backported from 0.2.9.7-rc):
13634 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
13638 Changes in version 0.2.9.8 - 2016-12-19
13639 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
13641 The Tor 0.2.9 series makes mandatory a number of security features
13642 that were formerly optional. It includes support for a new shared-
13643 randomness protocol that will form the basis for next generation
13644 hidden services, includes a single-hop hidden service mode for
13645 optimizing .onion services that don't actually want to be hidden,
13646 tries harder not to overload the directory authorities with excessive
13647 downloads, and supports a better protocol versioning scheme for
13648 improved compatibility with other implementations of the Tor protocol.
13650 And of course, there are numerous other bugfixes and improvements.
13652 This release also includes a fix for a medium-severity issue (bug
13653 21018 below) where Tor clients could crash when attempting to visit a
13654 hostile hidden service. Clients are recommended to upgrade as packages
13655 become available for their systems.
13657 Below are listed the changes since Tor 0.2.8.11. For a list of
13658 changes since 0.2.9.7-rc, see the ChangeLog file.
13660 o New system requirements:
13661 - When building with OpenSSL, Tor now requires version 1.0.1 or
13662 later. OpenSSL 1.0.0 and earlier are no longer supported by the
13663 OpenSSL team, and should not be used. Closes ticket 20303.
13664 - Tor now requires Libevent version 2.0.10-stable or later. Older
13665 versions of Libevent have less efficient backends for several
13666 platforms, and lack the DNS code that we use for our server-side
13667 DNS support. This implements ticket 19554.
13668 - Tor now requires zlib version 1.2 or later, for security,
13669 efficiency, and (eventually) gzip support. (Back when we started,
13670 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
13671 released in 2003. We recommend the latest version.)
13673 o Deprecated features:
13674 - A number of DNS-cache-related sub-options for client ports are now
13675 deprecated for security reasons, and may be removed in a future
13676 version of Tor. (We believe that client-side DNS caching is a bad
13677 idea for anonymity, and you should not turn it on.) The options
13678 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
13679 UseIPv4Cache, and UseIPv6Cache.
13680 - A number of options are deprecated for security reasons, and may
13681 be removed in a future version of Tor. The options are:
13682 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
13683 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
13684 CloseHSClientCircuitsImmediatelyOnTimeout,
13685 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
13686 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
13687 UseNTorHandshake, and WarnUnsafeSocks.
13688 - The *ListenAddress options are now deprecated as unnecessary: the
13689 corresponding *Port options should be used instead. These options
13690 may someday be removed. The affected options are:
13691 ControlListenAddress, DNSListenAddress, DirListenAddress,
13692 NATDListenAddress, ORListenAddress, SocksListenAddress,
13693 and TransListenAddress.
13695 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
13696 - Fix a bug in parsing that could cause clients to read a single
13697 byte past the end of an allocated region. This bug could be used
13698 to cause hardened clients (built with --enable-expensive-hardening)
13699 to crash if they tried to visit a hostile hidden service. Non-
13700 hardened clients are only affected depending on the details of
13701 their platform's memory allocator. Fixes bug 21018; bugfix on
13702 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13703 2016-12-002 and as CVE-2016-1254.
13705 o Major features (build, hardening):
13706 - Tor now builds with -ftrapv by default on compilers that support
13707 it. This option detects signed integer overflow (which C forbids),
13708 and turns it into a hard-failure. We do not apply this option to
13709 code that needs to run in constant time to avoid side-channels;
13710 instead, we use -fwrapv in that code. Closes ticket 17983.
13711 - When --enable-expensive-hardening is selected, stop applying the
13712 clang/gcc sanitizers to code that needs to run in constant time.
13713 Although we are aware of no introduced side-channels, we are not
13714 able to prove that there are none. Related to ticket 17983.
13716 o Major features (circuit building, security):
13717 - Authorities, relays, and clients now require ntor keys in all
13718 descriptors, for all hops (except for rare hidden service protocol
13719 cases), for all circuits, and for all other roles. Part of
13721 - Authorities, relays, and clients only use ntor, except for
13722 rare cases in the hidden service protocol. Part of ticket 19163.
13724 o Major features (compilation):
13725 - Our big list of extra GCC warnings is now enabled by default when
13726 building with GCC (or with anything like Clang that claims to be
13727 GCC-compatible). To make all warnings into fatal compilation
13728 errors, pass --enable-fatal-warnings to configure. Closes
13730 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
13731 turn on C and POSIX extensions. (Previously, we attempted to do
13732 this on an ad hoc basis.) Closes ticket 19139.
13734 o Major features (directory authorities, hidden services):
13735 - Directory authorities can now perform the shared randomness
13736 protocol specified by proposal 250. Using this protocol, directory
13737 authorities generate a global fresh random value every day. In the
13738 future, this value will be used by hidden services to select
13739 HSDirs. This release implements the directory authority feature;
13740 the hidden service side will be implemented in the future as part
13741 of proposal 224. Resolves ticket 16943; implements proposal 250.
13743 o Major features (downloading, random exponential backoff):
13744 - When we fail to download an object from a directory service, wait
13745 for an (exponentially increasing) randomized amount of time before
13746 retrying, rather than a fixed interval as we did before. This
13747 prevents a group of Tor instances from becoming too synchronized,
13748 or a single Tor instance from becoming too predictable, in its
13749 download schedule. Closes ticket 15942.
13751 o Major features (resource management):
13752 - Tor can now notice it is about to run out of sockets, and
13753 preemptively close connections of lower priority. (This feature is
13754 off by default for now, since the current prioritizing method is
13755 yet not mature enough. You can enable it by setting
13756 "DisableOOSCheck 0", but watch out: it might close some sockets
13757 you would rather have it keep.) Closes ticket 18640.
13759 o Major features (single-hop "hidden" services):
13760 - Add experimental HiddenServiceSingleHopMode and
13761 HiddenServiceNonAnonymousMode options. When both are set to 1,
13762 every hidden service on that Tor instance becomes a non-anonymous
13763 Single Onion Service. Single Onions make one-hop (direct)
13764 connections to their introduction and rendezvous points. One-hop
13765 circuits make Single Onion servers easily locatable, but clients
13766 remain location-anonymous. This is compatible with the existing
13767 hidden service implementation, and works on the current Tor
13768 network without any changes to older relays or clients. Implements
13769 proposal 260, completes ticket 17178. Patch by teor and asn.
13771 o Major features (subprotocol versions):
13772 - Tor directory authorities now vote on a set of recommended
13773 "subprotocol versions", and on a set of required subprotocol
13774 versions. Clients and relays that lack support for a _required_
13775 subprotocol version will not start; those that lack support for a
13776 _recommended_ subprotocol version will warn the user to upgrade.
13777 This change allows compatible implementations of the Tor protocol(s)
13778 to exist without pretending to be 100% bug-compatible with
13779 particular releases of Tor itself. Closes ticket 19958; implements
13780 part of proposal 264.
13782 o Major bugfixes (circuit building):
13783 - Hidden service client-to-intro-point and service-to-rendezvous-
13784 point circuits use the TAP key supplied by the protocol, to avoid
13785 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
13787 o Major bugfixes (download scheduling):
13788 - Avoid resetting download status for consensuses hourly, since we
13789 already have another, smarter retry mechanism. Fixes bug 8625;
13790 bugfix on 0.2.0.9-alpha.
13791 - If a consensus expires while we are waiting for certificates to
13792 download, stop waiting for certificates.
13793 - If we stop waiting for certificates less than a minute after we
13794 started downloading them, do not consider the certificate download
13795 failure a separate failure. Fixes bug 20533; bugfix
13797 - When using exponential backoff in test networks, use a lower
13798 exponent, so the delays do not vary as much. This helps test
13799 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
13801 o Major bugfixes (exit policies):
13802 - Avoid disclosing exit outbound bind addresses, configured port
13803 bind addresses, and local interface addresses in relay descriptors
13804 by default under ExitPolicyRejectPrivate. Instead, only reject
13805 these (otherwise unlisted) addresses if
13806 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
13807 0.2.7.2-alpha. Patch by teor.
13809 o Major bugfixes (hidden services):
13810 - Allow Tor clients with appropriate controllers to work with
13811 FetchHidServDescriptors set to 0. Previously, this option also
13812 disabled descriptor cache lookup, thus breaking hidden services
13813 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
13814 - Clients now require hidden services to include the TAP keys for
13815 their intro points in the hidden service descriptor. This prevents
13816 an inadvertent upgrade to ntor, which a malicious hidden service
13817 could use to distinguish clients by consensus version. Fixes bug
13818 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
13820 o Major bugfixes (relay, resolver, logging):
13821 - For relays that don't know their own address, avoid attempting a
13822 local hostname resolve for each descriptor we download. This
13823 will cut down on the number of "Success: chose address 'x.x.x.x'"
13824 log lines, and also avoid confusing clock jumps if the resolver
13825 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
13827 o Minor features (port flags):
13828 - Add new flags to the *Port options to give finer control over which
13829 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
13830 and the synthetic flag OnionTrafficOnly, which is equivalent to
13831 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
13832 18693; patch by "teor".
13834 o Minor features (build, hardening):
13835 - Detect and work around a libclang_rt problem that would prevent
13836 clang from finding __mulodi4() on some 32-bit platforms, and thus
13837 keep -ftrapv from linking on those systems. Closes ticket 19079.
13838 - When building on a system without runtime support for the runtime
13839 hardening options, try to log a useful warning at configuration
13840 time, rather than an incomprehensible warning at link time. If
13841 expensive hardening was requested, this warning becomes an error.
13842 Closes ticket 18895.
13844 o Minor features (client, directory):
13845 - Since authorities now omit all routers that lack the Running and
13846 Valid flags, we assume that any relay listed in the consensus must
13847 have those flags. Closes ticket 20001; implements part of
13850 o Minor features (code safety):
13851 - In our integer-parsing functions, ensure that the maximum value we
13852 allow is no smaller than the minimum value. Closes ticket 19063;
13853 patch from "U+039b".
13855 o Minor features (compilation, portability):
13856 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
13859 o Minor features (config):
13860 - Warn users when descriptor and port addresses are inconsistent.
13861 Mitigates bug 13953; patch by teor.
13863 o Minor features (controller):
13864 - Allow controllers to configure basic client authorization on
13865 hidden services when they create them with the ADD_ONION controller
13866 command. Implements ticket 15588. Patch by "special".
13867 - Fire a STATUS_SERVER controller event whenever the hibernation
13868 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
13869 - Implement new GETINFO queries for all downloads that use
13870 download_status_t to schedule retries. This allows controllers to
13871 examine the schedule for pending downloads. Closes ticket 19323.
13873 o Minor features (development tools, etags):
13874 - Teach the "make tags" Makefile target how to correctly find
13875 "MOCK_IMPL" function definitions. Patch from nherring; closes
13878 o Minor features (directory authority):
13879 - After voting, if the authorities decide that a relay is not
13880 "Valid", they no longer include it in the consensus at all. Closes
13881 ticket 20002; implements part of proposal 272.
13882 - Directory authorities now only give the Guard flag to a relay if
13883 they are also giving it the Stable flag. This change allows us to
13884 simplify path selection for clients. It should have minimal effect
13885 in practice, since >99% of Guards already have the Stable flag.
13886 Implements ticket 18624.
13887 - Directory authorities now write their v3-status-votes file out to
13888 disk earlier in the consensus process, so we have a record of the
13889 votes even if we abort the consensus process. Resolves
13892 o Minor features (fallback directory list, new since 0.2.9.7-rc):
13893 - Replace the 81 remaining fallbacks of the 100 originally
13894 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
13895 fallbacks (123 new, 54 existing, 27 removed) generated in December
13896 2016. Resolves ticket 20170.
13898 o Minor features (hidden service):
13899 - Stop being so strict about the payload length of "rendezvous1"
13900 cells. We used to be locked in to the "TAP" handshake length, and
13901 now we can handle better handshakes like "ntor". Resolves
13904 o Minor features (infrastructure, time):
13905 - Tor now includes an improved timer backend, so that we can
13906 efficiently support tens or hundreds of thousands of concurrent
13907 timers, as will be needed for some of our planned anti-traffic-
13908 analysis work. This code is based on William Ahern's "timeout.c"
13909 project, which implements a "tickless hierarchical timing wheel".
13910 Closes ticket 18365.
13911 - Tor now uses the operating system's monotonic timers (where
13912 available) for internal fine-grained timing. Previously we would
13913 look at the system clock, and then attempt to compensate for the
13914 clock running backwards. Closes ticket 18908.
13916 o Minor features (logging):
13917 - Add a set of macros to check nonfatal assertions, for internal
13918 use. Migrating more of our checks to these should help us avoid
13919 needless crash bugs. Closes ticket 18613.
13920 - Provide a more useful warning message when configured with an
13921 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
13922 - When dumping unparseable router descriptors, optionally store them
13923 in separate files, named by digest, up to a configurable size
13924 limit. You can change the size limit by setting the
13925 MaxUnparseableDescSizeToLog option, and disable this feature by
13926 setting that option to 0. Closes ticket 18322.
13928 o Minor features (performance):
13929 - Change the "optimistic data" extension from "off by default" to
13930 "on by default". The default was ordinarily overridden by a
13931 consensus option, but when clients were bootstrapping for the
13932 first time, they would not have a consensus to get the option
13933 from. Changing this default saves a round-trip during startup.
13934 Closes ticket 18815.
13936 o Minor features (relay, usability):
13937 - When the directory authorities refuse a bad relay's descriptor,
13938 encourage the relay operator to contact us. Many relay operators
13939 won't notice this line in their logs, but it's a win if even a few
13940 learn why we don't like what their relay was doing. Resolves
13943 o Minor features (security, TLS):
13944 - Servers no longer support clients that lack AES ciphersuites.
13945 (3DES is no longer considered an acceptable cipher.) We believe
13946 that no such Tor clients currently exist, since Tor has required
13947 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
13949 o Minor features (testing):
13950 - Disable memory protections on OpenBSD when performing our unit
13951 tests for memwipe(). The test deliberately invokes undefined
13952 behavior, and the OpenBSD protections interfere with this. Patch
13953 from "rubiate". Closes ticket 20066.
13954 - Move the test-network.sh script to chutney, and modify tor's test-
13955 network.sh to call the (newer) chutney version when available.
13956 Resolves ticket 19116. Patch by teor.
13957 - Use the lcov convention for marking lines as unreachable, so that
13958 we don't count them when we're generating test coverage data.
13959 Update our coverage tools to understand this convention. Closes
13961 - Our link-handshake unit tests now check that when invalid
13962 handshakes fail, they fail with the error messages we expected.
13963 - Our unit testing code that captures log messages no longer
13964 prevents them from being written out if the user asked for them
13965 (by passing --debug or --info or --notice or --warn to the "test"
13966 binary). This change prevents us from missing unexpected log
13967 messages simply because we were looking for others. Related to
13969 - The unit tests now log all warning messages with the "BUG" flag.
13970 Previously, they only logged errors by default. This change will
13971 help us make our testing code more correct, and make sure that we
13972 only hit this code when we mean to. In the meantime, however,
13973 there will be more warnings in the unit test logs than before.
13974 This is preparatory work for ticket 19999.
13975 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
13976 assertion as a test failure.
13977 - We've done significant work to make the unit tests run faster.
13979 o Minor features (testing, ipv6):
13980 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
13981 tests. Remove bridges+hs, as it's somewhat redundant. This
13982 requires a recent chutney version that supports IPv6 clients,
13983 relays, and authorities. Closes ticket 20069; patch by teor.
13984 - Add the single-onion and single-onion-ipv6 chutney targets to
13985 "make test-network-all". This requires a recent chutney version
13986 with the single onion network flavors (git c72a652 or later).
13987 Closes ticket 20072; patch by teor.
13989 o Minor features (Tor2web):
13990 - Make Tor2web clients respect ReachableAddresses. This feature was
13991 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
13992 0.2.8.7. Implements feature 20034. Patch by teor.
13994 o Minor features (unix domain sockets):
13995 - When configuring a unix domain socket for a SocksPort,
13996 ControlPort, or Hidden service, you can now wrap the address in
13997 quotes, using C-style escapes inside the quotes. This allows unix
13998 domain socket paths to contain spaces. Resolves ticket 18753.
14000 o Minor features (user interface):
14001 - Tor now supports the ability to declare options deprecated, so
14002 that we can recommend that people stop using them. Previously, this
14003 was done in an ad-hoc way. There is a new --list-deprecated-options
14004 command-line option to list all of the deprecated options. Closes
14007 o Minor features (virtual addresses):
14008 - Increase the maximum number of bits for the IPv6 virtual network
14009 prefix from 16 to 104. In this way, the condition for address
14010 allocation is less restrictive. Closes ticket 20151; feature
14013 o Minor bug fixes (circuits):
14014 - Use the CircuitBuildTimeout option whenever
14015 LearnCircuitBuildTimeout is disabled. Previously, we would respect
14016 the option when a user disabled it, but not when it was disabled
14017 because some other option was set. Fixes bug 20073; bugfix on
14018 0.2.4.12-alpha. Patch by teor.
14020 o Minor bugfixes (build):
14021 - The current Git revision when building from a local repository is
14022 now detected correctly when using git worktrees. Fixes bug 20492;
14023 bugfix on 0.2.3.9-alpha.
14025 o Minor bugfixes (relay address discovery):
14026 - Stop reordering IP addresses returned by the OS. This makes it
14027 more likely that Tor will guess the same relay IP address every
14028 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
14029 Reported by René Mayrhofer, patch by "cypherpunks".
14031 o Minor bugfixes (memory allocation):
14032 - Change how we allocate memory for large chunks on buffers, to
14033 avoid a (currently impossible) integer overflow, and to waste less
14034 space when allocating unusually large chunks. Fixes bug 20081;
14035 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
14037 o Minor bugfixes (bootstrap):
14038 - Remember the directory server we fetched the consensus or previous
14039 certificates from, and use it to fetch future authority
14040 certificates. This change improves bootstrapping performance.
14041 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
14043 o Minor bugfixes (circuits):
14044 - Make sure extend_info_from_router() is only called on servers.
14045 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
14047 o Minor bugfixes (client, fascistfirewall):
14048 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
14049 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
14051 o Minor bugfixes (client, unix domain sockets):
14052 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
14053 the client address is meaningless. Fixes bug 20261; bugfix
14056 o Minor bugfixes (code style):
14057 - Fix an integer signedness conversion issue in the case conversion
14058 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
14060 o Minor bugfixes (compilation):
14061 - Build correctly on versions of libevent2 without support for
14062 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
14064 - When building with Clang, use a full set of GCC warnings.
14065 (Previously, we included only a subset, because of the way we
14066 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
14067 - Detect Libevent2 functions correctly on systems that provide
14068 libevent2, but where libevent1 is linked with -levent. Fixes bug
14069 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
14070 - Run correctly when built on Windows build environments that
14071 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
14073 o Minor bugfixes (configuration):
14074 - When parsing quoted configuration values from the torrc file,
14075 handle Windows line endings correctly. Fixes bug 19167; bugfix on
14076 0.2.0.16-alpha. Patch from "Pingl".
14078 o Minor bugfixes (directory authority):
14079 - Authorities now sort the "package" lines in their votes, for ease
14080 of debugging. (They are already sorted in consensus documents.)
14081 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
14082 - Die with a more useful error when the operator forgets to place
14083 the authority_signing_key file into the keys directory. This
14084 avoids an uninformative assert & traceback about having an invalid
14085 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
14086 - When allowing private addresses, mark Exits that only exit to
14087 private locations as such. Fixes bug 20064; bugfix
14089 - When parsing a detached signature, make sure we use the length of
14090 the digest algorithm instead of a hardcoded DIGEST256_LEN in
14091 order to avoid comparing bytes out-of-bounds with a smaller digest
14092 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
14094 o Minor bugfixes (getpass):
14095 - Defensively fix a non-triggerable heap corruption at do_getpass()
14096 to protect ourselves from mistakes in the future. Fixes bug
14097 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
14100 o Minor bugfixes (guard selection):
14101 - Don't mark guards as unreachable if connection_connect() fails.
14102 That function fails for local reasons, so it shouldn't reveal
14103 anything about the status of the guard. Fixes bug 14334; bugfix
14105 - Use a single entry guard even if the NumEntryGuards consensus
14106 parameter is not provided. Fixes bug 17688; bugfix
14109 o Minor bugfixes (hidden services):
14110 - Increase the minimum number of internal circuits we preemptively
14111 build from 2 to 3, so a circuit is available when a client
14112 connects to another onion service. Fixes bug 13239; bugfix
14114 - Allow hidden services to run on IPv6 addresses even when the
14115 IPv6Exit option is not set. Fixes bug 18357; bugfix
14117 - Stop logging intro point details to the client log on certain
14118 error conditions. Fixed as part of bug 20012; bugfix on
14119 0.2.4.8-alpha. Patch by teor.
14120 - When deleting an ephemeral hidden service, close its intro points
14121 even if they are not completely open. Fixes bug 18604; bugfix
14123 - When configuring hidden services, check every hidden service
14124 directory's permissions. Previously, we only checked the last
14125 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
14127 o Minor bugfixes (IPv6, testing):
14128 - Check for IPv6 correctly on Linux when running test networks.
14129 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
14131 o Minor bugfixes (Linux seccomp2 sandbox):
14132 - Add permission to run the sched_yield() and sigaltstack() system
14133 calls, in order to support versions of Tor compiled with asan or
14134 ubsan code that use these calls. Now "sandbox 1" and
14135 "--enable-expensive-hardening" should be compatible on more
14136 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
14138 o Minor bugfixes (logging):
14139 - Downgrade a harmless log message about the
14140 pending_entry_connections list from "warn" to "info". Mitigates
14142 - Log a more accurate message when we fail to dump a microdescriptor.
14143 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
14144 - When logging a directory ownership mismatch, log the owning
14145 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
14146 - When we are unable to remove the bw_accounting file, do not warn
14147 if the reason we couldn't remove it was that it didn't exist.
14148 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
14150 o Minor bugfixes (memory leak):
14151 - Fix a series of slow memory leaks related to parsing torrc files
14152 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
14153 - Avoid a small memory leak when informing worker threads about
14154 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
14155 - Fix a small memory leak when receiving AF_UNIX connections on a
14156 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
14157 - When moving a signed descriptor object from a source to an
14158 existing destination, free the allocated memory inside that
14159 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
14160 - Fix a memory leak and use-after-free error when removing entries
14161 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
14162 0.2.5.5-alpha. Patch from "cypherpunks".
14163 - Fix a small, uncommon memory leak that could occur when reading a
14164 truncated ed25519 key file. Fixes bug 18956; bugfix
14167 o Minor bugfixes (option parsing):
14168 - Count unix sockets when counting client listeners (SOCKS, Trans,
14169 NATD, and DNS). This has no user-visible behavior changes: these
14170 options are set once, and never read. Required for correct
14171 behavior in ticket 17178. Fixes bug 19677; bugfix on
14172 0.2.6.3-alpha. Patch by teor.
14174 o Minor bugfixes (options):
14175 - Check the consistency of UseEntryGuards and EntryNodes more
14176 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
14178 - Stop changing the configured value of UseEntryGuards on
14179 authorities and Tor2web clients. Fixes bug 20074; bugfix on
14180 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
14183 o Minor bugfixes (relay):
14184 - Ensure relays don't make multiple connections during bootstrap.
14185 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
14186 - Do not try to parallelize workers more than 16x without the user
14187 explicitly configuring us to do so, even if we do detect more than
14188 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
14190 o Minor bugfixes (testing):
14191 - The test-stem and test-network makefile targets now depend only on
14192 the tor binary that they are testing. Previously, they depended on
14193 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
14194 patch from "cypherpunks".
14195 - Allow clients to retry HSDirs much faster in test networks. Fixes
14196 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
14197 - Avoid a unit test failure on systems with over 16 detectable CPU
14198 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
14199 - Let backtrace tests work correctly under AddressSanitizer:
14200 disable ASAN's detection of segmentation faults while running
14201 test_bt.sh, so that we can make sure that our own backtrace
14202 generation code works. Fixes bug 18934; bugfix
14203 on 0.2.5.2-alpha. Patch from "cypherpunks".
14204 - Fix the test-network-all target on out-of-tree builds by using the
14205 correct path to the test driver script. Fixes bug 19421; bugfix
14207 - Stop spurious failures in the local interface address discovery
14208 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
14210 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
14211 removed the ECDH ciphers which caused the tests to fail on
14212 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
14213 - The tor_tls_server_info_callback unit test no longer crashes when
14214 debug-level logging is turned on. Fixes bug 20041; bugfix
14217 o Minor bugfixes (time):
14218 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
14219 bugfix on all released tor versions.
14220 - When computing the difference between two times in milliseconds,
14221 we now round to the nearest millisecond correctly. Previously, we
14222 could sometimes round in the wrong direction. Fixes bug 19428;
14223 bugfix on 0.2.2.2-alpha.
14225 o Minor bugfixes (Tor2web):
14226 - Prevent Tor2web clients from running hidden services: these services
14227 are not anonymous due to the one-hop client paths. Fixes bug
14228 19678. Patch by teor.
14230 o Minor bugfixes (user interface):
14231 - Display a more accurate number of suppressed messages in the log
14232 rate-limiter. Previously, there was a potential integer overflow
14233 in the counter. Now, if the number of messages hits a maximum, the
14234 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
14236 - Fix a typo in the passphrase prompt for the ed25519 identity key.
14237 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
14239 o Code simplification and refactoring:
14240 - Remove redundant declarations of the MIN macro. Closes
14242 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
14243 Closes ticket 18462; patch from "icanhasaccount".
14244 - Split the 600-line directory_handle_command_get function into
14245 separate functions for different URL types. Closes ticket 16698.
14248 - Add module-level internal documentation for 36 C files that
14249 previously didn't have a high-level overview. Closes ticket 20385.
14250 - Correct the IPv6 syntax in our documentation for the
14251 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
14252 - Correct the minimum bandwidth value in torrc.sample, and queue a
14253 corresponding change for torrc.minimal. Closes ticket 20085.
14254 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
14255 ticket 19153. Patch from "U+039b".
14256 - Module-level documentation for several more modules. Closes
14257 tickets 19287 and 19290.
14258 - Document the --passphrase-fd option in the tor manpage. Fixes bug
14259 19504; bugfix on 0.2.7.3-rc.
14260 - Document the default PathsNeededToBuildCircuits value that's used
14261 by clients when the directory authorities don't set
14262 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
14263 Patch by teor, reported by Jesse V.
14264 - Fix manual for the User option: it takes a username, not a UID.
14265 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
14267 - Fix the description of the --passphrase-fd option in the
14268 tor-gencert manpage. The option is used to pass the number of a
14269 file descriptor to read the passphrase from, not to read the file
14270 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
14273 - We no longer include the (dead, deprecated) bufferevent code in
14274 Tor. Closes ticket 19450. Based on a patch from "U+039b".
14276 o Removed features:
14277 - Remove support for "GET /tor/bytes.txt" DirPort request, and
14278 "GETINFO dir-usage" controller request, which were only available
14279 via a compile-time option in Tor anyway. Feature was added in
14280 0.2.2.1-alpha. Resolves ticket 19035.
14281 - There is no longer a compile-time option to disable support for
14282 TransPort. (If you don't want TransPort, just don't use it.) Patch
14283 from "U+039b". Closes ticket 19449.
14286 - Run more workqueue tests as part of "make check". These had
14287 previously been implemented, but you needed to know special
14288 command-line options to enable them.
14289 - We now have unit tests for our code to reject zlib "compression
14290 bombs". (Fortunately, the code works fine.)
14293 Changes in version 0.2.8.11 - 2016-12-08
14294 Tor 0.2.8.11 backports fixes for additional portability issues that
14295 could prevent Tor from building correctly on OSX Sierra, or with
14296 OpenSSL 1.1. Affected users should upgrade; others can safely stay
14299 o Minor bugfixes (portability):
14300 - Avoid compilation errors when building on OSX Sierra. Sierra began
14301 to support the getentropy() and clock_gettime() APIs, but created
14302 a few problems in doing so. Tor 0.2.9 has a more thorough set of
14303 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
14304 monotonic time interfaces. Fixes bug 20865. Bugfix
14307 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
14308 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
14309 architectures. Closes ticket 20588.
14312 Changes in version 0.2.8.10 - 2016-12-02
14313 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
14314 unusable after they left standby mode. It also backports fixes for
14315 a few portability issues and a small but problematic memory leak.
14317 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
14318 - When Tor leaves standby because of a new application request, open
14319 circuits as needed to serve that request. Previously, we would
14320 potentially wait a very long time. Fixes part of bug 19969; bugfix
14323 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
14324 - Clients now respond to new application stream requests immediately
14325 when they arrive, rather than waiting up to one second before
14326 starting to handle them. Fixes part of bug 19969; bugfix
14329 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
14330 - Work around a bug in the OSX 10.12 SDK that would prevent us from
14331 successfully targeting earlier versions of OSX. Resolves
14334 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
14335 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
14336 20551; bugfix on 0.2.1.1-alpha.
14338 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
14339 - Work around a memory leak in OpenSSL 1.1 when encoding public
14340 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
14342 o Minor features (geoip):
14343 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
14347 Changes in version 0.2.8.9 - 2016-10-17
14348 Tor 0.2.8.9 backports a fix for a security hole in previous versions
14349 of Tor that would allow a remote attacker to crash a Tor client,
14350 hidden service, relay, or authority. All Tor users should upgrade to
14351 this version, or to 0.2.9.4-alpha. Patches will be released for older
14354 o Major features (security fixes, also in 0.2.9.4-alpha):
14355 - Prevent a class of security bugs caused by treating the contents
14356 of a buffer chunk as if they were a NUL-terminated string. At
14357 least one such bug seems to be present in all currently used
14358 versions of Tor, and would allow an attacker to remotely crash
14359 most Tor instances, especially those compiled with extra compiler
14360 hardening. With this defense in place, such bugs can't crash Tor,
14361 though we should still fix them as they occur. Closes ticket
14362 20384 (TROVE-2016-10-001).
14364 o Minor features (geoip):
14365 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
14369 Changes in version 0.2.8.8 - 2016-09-23
14370 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
14371 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
14372 who select public relays as their bridges.
14374 o Major bugfixes (crash):
14375 - Fix a complicated crash bug that could affect Tor clients
14376 configured to use bridges when replacing a networkstatus consensus
14377 in which one of their bridges was mentioned. OpenBSD users saw
14378 more crashes here, but all platforms were potentially affected.
14379 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
14381 o Major bugfixes (relay, OOM handler):
14382 - Fix a timing-dependent assertion failure that could occur when we
14383 tried to flush from a circuit after having freed its cells because
14384 of an out-of-memory condition. Fixes bug 20203; bugfix on
14385 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
14388 o Minor feature (fallback directories):
14389 - Remove broken fallbacks from the hard-coded fallback directory
14390 list. Closes ticket 20190; patch by teor.
14392 o Minor features (geoip):
14393 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
14397 Changes in version 0.2.8.7 - 2016-08-24
14398 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
14399 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
14400 who sets the ReachableAddresses option, and all bridges, are strongly
14401 encouraged to upgrade.
14403 o Directory authority changes:
14404 - The "Tonga" bridge authority has been retired; the new bridge
14405 authority is "Bifroest". Closes tickets 19728 and 19690.
14407 o Major bugfixes (client, security):
14408 - Only use the ReachableAddresses option to restrict the first hop
14409 in a path. In earlier versions of 0.2.8.x, it would apply to
14410 every hop in the path, with a possible degradation in anonymity
14411 for anyone using an uncommon ReachableAddress setting. Fixes bug
14412 19973; bugfix on 0.2.8.2-alpha.
14414 o Minor features (geoip):
14415 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
14418 o Minor bugfixes (compilation):
14419 - Remove an inappropriate "inline" in tortls.c that was causing
14420 warnings on older versions of GCC. Fixes bug 19903; bugfix
14423 o Minor bugfixes (fallback directories):
14424 - Avoid logging a NULL string pointer when loading fallback
14425 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
14426 and 0.2.8.1-alpha. Report and patch by "rubiate".
14429 Changes in version 0.2.8.6 - 2016-08-02
14431 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
14433 The Tor 0.2.8 series improves client bootstrapping performance,
14434 completes the authority-side implementation of improved identity
14435 keys for relays, and includes numerous bugfixes and performance
14436 improvements throughout the program. This release continues to
14437 improve the coverage of Tor's test suite. For a full list of
14438 changes since Tor 0.2.7, see the ReleaseNotes file.
14440 Below is a list of the changes since Tor 0.2.7.
14442 o New system requirements:
14443 - Tor no longer attempts to support platforms where the "time_t"
14444 type is unsigned. (To the best of our knowledge, only OpenVMS does
14445 this, and Tor has never actually built on OpenVMS.) Closes
14447 - Tor no longer supports versions of OpenSSL with a broken
14448 implementation of counter mode. (This bug was present in OpenSSL
14449 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
14450 longer runs with, these versions.
14451 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
14452 later (released in 2008 and 2009 respectively). If you are
14453 building Tor from the git repository instead of from the source
14454 distribution, and your tools are older than this, you will need to
14455 upgrade. Closes ticket 17732.
14457 o Directory authority changes:
14458 - Update the V3 identity key for the dannenberg directory authority:
14459 it was changed on 18 November 2015. Closes task 17906. Patch
14461 - Urras is no longer a directory authority. Closes ticket 19271.
14463 o Major features (directory system):
14464 - Include a trial list of default fallback directories, based on an
14465 opt-in survey of suitable relays. Doing this should make clients
14466 bootstrap more quickly and reliably, and reduce the load on the
14467 directory authorities. Closes ticket 15775. Patch by teor.
14468 Candidates identified using an OnionOO script by weasel, teor,
14469 gsathya, and karsten.
14470 - Previously only relays that explicitly opened a directory port
14471 (DirPort) accepted directory requests from clients. Now all
14472 relays, with and without a DirPort, accept and serve tunneled
14473 directory requests that they receive through their ORPort. You can
14474 disable this behavior using the new DirCache option. Closes
14476 - When bootstrapping multiple consensus downloads at a time, use the
14477 first one that starts downloading, and close the rest. This
14478 reduces failures when authorities or fallback directories are slow
14479 or down. Together with the code for feature 15775, this feature
14480 should reduces failures due to fallback churn. Implements ticket
14481 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
14482 mikeperry and teor.
14484 o Major features (security, Linux):
14485 - When Tor starts as root on Linux and is told to switch user ID, it
14486 can now retain the capability to bind to low ports. By default,
14487 Tor will do this only when it's switching user ID and some low
14488 ports have been configured. You can change this behavior with the
14489 new option KeepBindCapabilities. Closes ticket 8195.
14491 o Major bugfixes (client, bootstrapping):
14492 - Check if bootstrap consensus downloads are still needed when the
14493 linked connection attaches. This prevents tor making unnecessary
14494 begindir-style connections, which are the only directory
14495 connections tor clients make since the fix for 18483 was merged.
14496 - Fix some edge cases where consensus download connections may not
14497 have been closed, even though they were not needed. Related to fix
14499 - Make relays retry consensus downloads the correct number of times,
14500 rather than the more aggressive client retry count. Fixes part of
14503 o Major bugfixes (dns proxy mode, crash):
14504 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
14505 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
14507 o Major bugfixes (ed25519, voting):
14508 - Actually enable support for authorities to match routers by their
14509 Ed25519 identities. Previously, the code had been written, but
14510 some debugging code that had accidentally been left in the
14511 codebase made it stay turned off. Fixes bug 17702; bugfix
14513 - When collating votes by Ed25519 identities, authorities now
14514 include a "NoEdConsensus" flag if the ed25519 value (or lack
14515 thereof) for a server does not reflect the majority consensus.
14516 Related to bug 17668; bugfix on 0.2.7.2-alpha.
14517 - When generating a vote with keypinning disabled, never include two
14518 entries for the same ed25519 identity. This bug was causing
14519 authorities to generate votes that they could not parse when a
14520 router violated key pinning by changing its RSA identity but
14521 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
14522 18318. Bugfix on 0.2.7.2-alpha.
14524 o Major bugfixes (key management):
14525 - If OpenSSL fails to generate an RSA key, do not retain a dangling
14526 pointer to the previous (uninitialized) key value. The impact here
14527 should be limited to a difficult-to-trigger crash, if OpenSSL is
14528 running an engine that makes key generation failures possible, or
14529 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
14530 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
14533 o Major bugfixes (security, client, DNS proxy):
14534 - Stop a crash that could occur when a client running with DNSPort
14535 received a query with multiple address types, and the first
14536 address type was not supported. Found and fixed by Scott Dial.
14537 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
14539 o Major bugfixes (security, compilation):
14540 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
14541 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
14542 cause a compiler warning, thereby making other checks fail, and
14543 needlessly disabling compiler-hardening support. Fixes one case of
14544 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
14545 - Repair hardened builds under the clang compiler. Previously, our
14546 use of _FORTIFY_SOURCE would conflict with clang's address
14547 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
14549 o Major bugfixes (security, pointers):
14550 - Avoid a difficult-to-trigger heap corruption attack when extending
14551 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
14552 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
14553 Reported by Guido Vranken.
14555 o Major bugfixes (testing):
14556 - Fix a bug that would block 'make test-network-all' on systems where
14557 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
14559 o Major bugfixes (user interface):
14560 - Correctly give a warning in the cases where a relay is specified
14561 by nickname, and one such relay is found, but it is not officially
14562 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
14564 o Minor features (accounting):
14565 - Added two modes to the AccountingRule option: One for limiting
14566 only the number of bytes sent ("AccountingRule out"), and one for
14567 limiting only the number of bytes received ("AccountingRule in").
14568 Closes ticket 15989; patch from "unixninja92".
14570 o Minor features (bug-resistance):
14571 - Make Tor survive errors involving connections without a
14572 corresponding event object. Previously we'd fail with an
14573 assertion; now we produce a log message. Related to bug 16248.
14574 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
14575 level code, to harden against accidental failures to NUL-
14576 terminate. Part of ticket 17852. Patch from jsturgix. Found
14579 o Minor features (build):
14580 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
14581 as having possible IPFW support. Closes ticket 18448. Patch from
14582 Steven Chamberlain.
14583 - Since our build process now uses "make distcheck", we no longer
14584 force "make dist" to depend on "make check". Closes ticket 17893;
14585 patch from "cypherpunks".
14586 - Tor now builds once again with the recent OpenSSL 1.1 development
14587 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
14588 tracking OpenSSL 1.1 development as it has progressed, and fixing
14589 numerous compatibility issues as they arose. See tickets
14590 17549, 17921, 17984, 19499, and 18286.
14591 - When building manual pages, set the timezone to "UTC", so that the
14592 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
14593 Patch from intrigeri.
14595 o Minor features (clients):
14596 - Make clients, onion services, and bridge relays always use an
14597 encrypted begindir connection for directory requests. Resolves
14598 ticket 18483. Patch by teor.
14600 o Minor features (controller):
14601 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
14602 controllers can examine the the reject rules added by
14603 ExitPolicyRejectPrivate. This makes it easier for stem to display
14605 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
14606 tickets 16774 and 17817. Patch by George Tankersley.
14607 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
14608 service descriptor from a service's local hidden service
14609 descriptor cache. Closes ticket 14846.
14611 o Minor features (crypto):
14612 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
14613 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
14615 - Improve performance when hashing non-multiple of 8 sized buffers,
14616 based on Andrew Moon's public domain SipHash-2-4 implementation.
14617 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
14618 - Validate the hard-coded Diffie-Hellman parameters and ensure that
14619 p is a safe prime, and g is a suitable generator. Closes
14621 - When allocating a digest state object, allocate no more space than
14622 we actually need. Previously, we would allocate as much space as
14623 the state for the largest algorithm would need. This change saves
14624 up to 672 bytes per circuit. Closes ticket 17796.
14626 o Minor features (directory downloads):
14627 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
14628 directory mirrors. The default is 1; set it to 0 to disable
14629 fallbacks. Implements ticket 17576. Patch by teor.
14630 - Wait for busy authorities and fallback directories to become non-
14631 busy when bootstrapping. (A similar change was made in 6c443e987d
14632 for directory caches chosen from the consensus.) Closes ticket
14633 17864; patch by teor.
14635 o Minor features (geoip):
14636 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
14639 o Minor features (hidden service directory):
14640 - Streamline relay-side hsdir handling: when relays consider whether
14641 to accept an uploaded hidden service descriptor, they no longer
14642 check whether they are one of the relays in the network that is
14643 "supposed" to handle that descriptor. Implements ticket 18332.
14645 o Minor features (IPv6):
14646 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
14647 to 1, tor prefers IPv6 directory addresses.
14648 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
14649 avoids using IPv4 for client OR and directory connections.
14650 - Add address policy assume_action support for IPv6 addresses.
14651 - Add an argument 'ipv6=address:orport' to the DirAuthority and
14652 FallbackDir torrc options, to specify an IPv6 address for an
14653 authority or fallback directory. Add hard-coded ipv6 addresses for
14654 directory authorities that have them. Closes ticket 17327; patch
14655 from Nick Mathewson and teor.
14656 - Allow users to configure directory authorities and fallback
14657 directory servers with IPv6 addresses and ORPorts. Resolves
14659 - Limit IPv6 mask bits to 128.
14660 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
14661 17638; bugfix on 0.0.2pre8. Patch by teor.
14662 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
14663 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
14664 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
14665 - Warn when comparing against an AF_UNSPEC address in a policy, it's
14666 almost always a bug. Closes ticket 17863; patch by teor.
14667 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
14668 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
14670 o Minor features (Linux seccomp2 sandbox):
14671 - Reject attempts to change our Address with "Sandbox 1" enabled.
14672 Changing Address with Sandbox turned on would never actually work,
14673 but previously it would fail in strange and confusing ways. Found
14674 while fixing 18548.
14676 o Minor features (logging):
14677 - When logging to syslog, allow a tag to be added to the syslog
14678 identity (the string prepended to every log message). The tag can
14679 be configured with SyslogIdentityTag and defaults to none. Setting
14680 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
14683 o Minor features (portability):
14684 - Use timingsafe_memcmp() where available. Closes ticket 17944;
14685 patch from <logan@hackers.mu>.
14687 o Minor features (relay, address discovery):
14688 - Add a family argument to get_interface_addresses_raw() and
14689 subfunctions to make network interface address interogation more
14690 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
14691 types of interfaces from the operating system. Resolves
14693 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
14694 fails to enumerate interface addresses using the platform-specific
14695 API, have it rely on the UDP socket fallback technique to try and
14696 find out what IP addresses (both IPv4 and IPv6) our machine has.
14697 Resolves ticket 17951.
14699 o Minor features (replay cache):
14700 - The replay cache now uses SHA256 instead of SHA1. Implements
14701 feature 8961. Patch by teor, issue reported by rransom.
14703 o Minor features (robustness):
14704 - Exit immediately with an error message if the code attempts to use
14705 Libevent without having initialized it. This should resolve some
14706 frequently-made mistakes in our unit tests. Closes ticket 18241.
14708 o Minor features (security, clock):
14709 - Warn when the system clock appears to move back in time (when the
14710 state file was last written in the future). Tor doesn't know that
14711 consensuses have expired if the clock is in the past. Patch by
14712 teor. Implements ticket 17188.
14714 o Minor features (security, exit policies):
14715 - ExitPolicyRejectPrivate now rejects more private addresses by
14716 default. Specifically, it now rejects the relay's outbound bind
14717 addresses (if configured), and the relay's configured port
14718 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
14719 0.2.0.11-alpha. Patch by teor.
14721 o Minor features (security, memory erasure):
14722 - Make memwipe() do nothing when passed a NULL pointer or buffer of
14723 zero size. Check size argument to memwipe() for underflow. Fixes
14724 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
14726 - Set the unused entries in a smartlist to NULL. This helped catch
14727 a (harmless) bug, and shouldn't affect performance too much.
14728 Implements ticket 17026.
14729 - Use SecureMemoryWipe() function to securely clean memory on
14730 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
14731 Implements feature 17986.
14732 - Use explicit_bzero or memset_s when present. Previously, we'd use
14733 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
14734 from <logan@hackers.mu> and <selven@hackers.mu>.
14736 o Minor features (security, RNG):
14737 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
14738 positively are not allowed to fail. Previously we depended on
14739 internal details of OpenSSL's behavior. Closes ticket 17686.
14740 - Never use the system entropy output directly for anything besides
14741 seeding the PRNG. When we want to generate important keys, instead
14742 of using system entropy directly, we now hash it with the PRNG
14743 stream. This may help resist certain attacks based on broken OS
14744 entropy implementations. Closes part of ticket 17694.
14745 - Use modern system calls (like getentropy() or getrandom()) to
14746 generate strong entropy on platforms that have them. Closes
14749 o Minor features (security, win32):
14750 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
14751 attack. Fixes bug 18123; bugfix on all tor versions. Patch
14754 o Minor features (unix domain sockets):
14755 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
14756 Unix domain sockets without checking the permissions on the parent
14757 directory. (Tor checks permissions by default because some
14758 operating systems only check permissions on the parent directory.
14759 However, some operating systems do look at permissions on the
14760 socket, and tor's default check is unneeded.) Closes ticket 18458.
14763 o Minor features (unix file permissions):
14764 - Defer creation of Unix sockets until after setuid. This avoids
14765 needing CAP_CHOWN and CAP_FOWNER when using systemd's
14766 CapabilityBoundingSet, or chown and fowner when using SELinux.
14767 Implements part of ticket 17562. Patch from Jamie Nguyen.
14768 - If any directory created by Tor is marked as group readable, the
14769 filesystem group is allowed to be either the default GID or the
14770 root user. Allowing root to read the DataDirectory prevents the
14771 need for CAP_READ_SEARCH when using systemd's
14772 CapabilityBoundingSet, or dac_read_search when using SELinux.
14773 Implements part of ticket 17562. Patch from Jamie Nguyen.
14774 - Introduce a new DataDirectoryGroupReadable option. If it is set to
14775 1, the DataDirectory will be made readable by the default GID.
14776 Implements part of ticket 17562. Patch from Jamie Nguyen.
14778 o Minor bugfixes (accounting):
14779 - The max bandwidth when using 'AccountRule sum' is now correctly
14780 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
14781 from "unixninja92".
14783 o Minor bugfixes (assert, portability):
14784 - Fix an assertion failure in memarea.c on systems where "long" is
14785 shorter than the size of a pointer. Fixes bug 18716; bugfix
14788 o Minor bugfixes (bootstrap):
14789 - Consistently use the consensus download schedule for authority
14790 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
14792 o Minor bugfixes (build):
14793 - Avoid spurious failures from configure files related to calling
14794 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
14795 0.2.0.1-alpha. Patch from "cypherpunks".
14796 - Do not link the unit tests against both the testing and non-
14797 testing versions of the static libraries. Fixes bug 18490; bugfix
14799 - Resolve warnings when building on systems that are concerned with
14800 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
14802 - Silence spurious clang-scan warnings in the ed25519_donna code by
14803 explicitly initializing some objects. Fixes bug 18384; bugfix on
14804 0.2.7.2-alpha. Patch by teor.
14805 - When libscrypt.h is found, but no libscrypt library can be linked,
14806 treat libscrypt as absent. Fixes bug 19161; bugfix
14808 - Cause the unit tests to compile correctly on mingw64 versions that
14809 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
14810 - Don't try to use the pthread_condattr_setclock() function unless
14811 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
14812 17819; bugfix on 0.2.6.3-alpha.
14813 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
14815 - Fix search for libevent libraries on OpenBSD (and other systems
14816 that install libevent 1 and libevent 2 in parallel). Fixes bug
14817 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
14818 - Isolate environment variables meant for tests from the rest of the
14819 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
14820 - Mark all object files that include micro-revision.i as depending
14821 on it, so as to make parallel builds more reliable. Fixes bug
14822 17826; bugfix on 0.2.5.1-alpha.
14823 - Remove config.log only from make distclean, not from make clean.
14824 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
14825 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
14827 - Remove an #endif from configure.ac so that we correctly detect the
14828 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
14831 o Minor bugfixes (client, bootstrap):
14832 - Count receipt of new microdescriptors as progress towards
14833 bootstrapping. Previously, with EntryNodes set, Tor might not
14834 successfully repopulate the guard set on bootstrapping. Fixes bug
14835 16825; bugfix on 0.2.3.1-alpha.
14837 o Minor bugfixes (code correctness):
14838 - Fix a bad memory handling bug that would occur if we had queued a
14839 cell on a channel's incoming queue. Fortunately, we can't actually
14840 queue a cell like that as our code is constructed today, but it's
14841 best to avoid this kind of error, even if there isn't any code
14842 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
14843 - Assert that allocated memory held by the reputation code is freed
14844 according to its internal counters. Fixes bug 17753; bugfix
14846 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
14848 - Update to the latest version of Trunnel, which tries harder to
14849 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
14850 by clang address sanitizer. Fixes bug 18373; bugfix
14852 - When closing an entry connection, generate a warning if we should
14853 have sent an end cell for it but we haven't. Fixes bug 17876;
14854 bugfix on 0.2.3.2-alpha.
14856 o Minor bugfixes (configuration):
14857 - Fix a tiny memory leak when parsing a port configuration ending in
14858 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
14860 o Minor bugfixes (containers):
14861 - If we somehow attempt to construct a heap with more than
14862 1073741822 elements, avoid an integer overflow when maintaining
14863 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
14865 o Minor bugfixes (controller, microdescriptors):
14866 - Make GETINFO dir/status-vote/current/consensus conform to the
14867 control specification by returning "551 Could not open cached
14868 consensus..." when not caching consensuses. Fixes bug 18920;
14869 bugfix on 0.2.2.6-alpha.
14871 o Minor bugfixes (crypto):
14872 - Check the return value of HMAC() and assert on failure. Fixes bug
14873 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
14875 o Minor bugfixes (directories):
14876 - When fetching extrainfo documents, compare their SHA256 digests
14877 and Ed25519 signing key certificates with the routerinfo that led
14878 us to fetch them, rather than with the most recent routerinfo.
14879 Otherwise we generate many spurious warnings about mismatches.
14880 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
14881 - When generating a URL for a directory server on an IPv6 address,
14882 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
14883 on 0.2.3.9-alpha. Patch from Malek.
14885 o Minor bugfixes (downloading):
14886 - Predict more correctly whether we'll be downloading over HTTP when
14887 we determine the maximum length of a URL. This should avoid a
14888 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
14891 o Minor bugfixes (exit policies, security):
14892 - Refresh an exit relay's exit policy when interface addresses
14893 change. Previously, tor only refreshed the exit policy when the
14894 configured external address changed. Fixes bug 18208; bugfix on
14895 0.2.7.3-rc. Patch by teor.
14897 o Minor bugfixes (fallback directories):
14898 - Mark fallbacks as "too busy" when they return a 503 response,
14899 rather than just marking authorities. Fixes bug 17572; bugfix on
14900 0.2.4.7-alpha. Patch by teor.
14901 - When requesting extrainfo descriptors from a trusted directory
14902 server, check whether it is an authority or a fallback directory
14903 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
14904 0.2.4.7-alpha. Reported by atagar, patch by teor.
14906 o Minor bugfixes (hidden service, client):
14907 - Handle the case where the user makes several fast consecutive
14908 requests to the same .onion address. Previously, the first six
14909 requests would each trigger a descriptor fetch, each picking a
14910 directory (there are 6 overall) and the seventh one would fail
14911 because no directories were left, thereby triggering a close on
14912 all current directory connections asking for the hidden service.
14913 The solution here is to not close the connections if we have
14914 pending directory fetches. Fixes bug 15937; bugfix
14917 o Minor bugfixes (hidden service, control port):
14918 - Add the onion address to the HS_DESC event for the UPLOADED action
14919 both on success or failure. It was previously hardcoded with
14920 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
14922 o Minor bugfixes (hidden service, directory):
14923 - Bridges now refuse "rendezvous2" (hidden service descriptor)
14924 publish attempts. Suggested by ticket 18332.
14926 o Minor bugfixes (IPv6):
14927 - Update the limits in max_dl_per_request for IPv6 address length.
14928 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
14930 o Minor bugfixes (Linux seccomp2 sandbox):
14931 - Allow more syscalls when running with "Sandbox 1" enabled:
14932 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
14933 some systems, these are required for Tor to start. Fixes bug
14934 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
14935 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
14936 so that get_interface_address6_via_udp_socket_hack() can work.
14937 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
14938 - Allow the setrlimit syscall, and the prlimit and prlimit64
14939 syscalls, which some libc implementations use under the hood.
14940 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
14941 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
14942 enabled and no DNS resolvers configured. This should help TAILS
14943 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
14944 - Fix a crash when using offline master ed25519 keys with the Linux
14945 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
14946 - Allow statistics to be written to disk when "Sandbox 1" is
14947 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
14948 0.2.6.1-alpha respectively.
14950 o Minor bugfixes (logging):
14951 - In log messages that include a function name, use __FUNCTION__
14952 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
14953 with clang __PRETTY_FUNCTION__ has extra information we don't
14954 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
14956 - Remove needless quotes from a log message about unparseable
14957 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
14958 - Scrub service name in "unrecognized service ID" log messages.
14959 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
14960 - When logging information about an unparsable networkstatus vote or
14961 consensus, do not say "vote" when we mean consensus. Fixes bug
14962 18368; bugfix on 0.2.0.8-alpha.
14963 - When we can't generate a signing key because OfflineMasterKey is
14964 set, do not imply that we should have been able to load it. Fixes
14965 bug 18133; bugfix on 0.2.7.2-alpha.
14966 - When logging a malformed hostname received through socks4, scrub
14967 it if SafeLogging says we should. Fixes bug 17419; bugfix
14970 o Minor bugfixes (memory safety):
14971 - Avoid freeing an uninitialized pointer when opening a socket fails
14972 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
14973 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
14975 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
14976 18672; bugfix on 0.2.5.1-alpha.
14977 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
14980 o Minor bugfixes (pluggable transports):
14981 - Avoid reporting a spurious error when we decide that we don't need
14982 to terminate a pluggable transport because it has already exited.
14983 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
14985 o Minor bugfixes (pointer arithmetic):
14986 - Fix a bug in memarea_alloc() that could have resulted in remote
14987 heap write access, if Tor had ever passed an unchecked size to
14988 memarea_alloc(). Fortunately, all the sizes we pass to
14989 memarea_alloc() are pre-checked to be less than 128 kilobytes.
14990 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
14993 o Minor bugfixes (private directory):
14994 - Prevent a race condition when creating private directories. Fixes
14995 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
14996 Patch from jsturgix. Found with Flawfinder.
14998 o Minor bugfixes (relays):
14999 - Check that both the ORPort and DirPort (if present) are reachable
15000 before publishing a relay descriptor. Otherwise, relays publish a
15001 descriptor with DirPort 0 when the DirPort reachability test takes
15002 longer than the ORPort reachability test. Fixes bug 18050; bugfix
15003 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
15004 - Resolve some edge cases where we might launch an ORPort
15005 reachability check even when DisableNetwork is set. Noticed while
15006 fixing bug 18616; bugfix on 0.2.3.9-alpha.
15008 o Minor bugfixes (relays, hidden services):
15009 - Refuse connection requests to private OR addresses unless
15010 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
15011 then refuse to send any cells to a private address. Fixes bugs
15012 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
15014 o Minor bugfixes (security, hidden services):
15015 - Prevent hidden services connecting to client-supplied rendezvous
15016 addresses that are reserved as internal or multicast. Fixes bug
15017 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
15019 o Minor bugfixes (statistics):
15020 - Consistently check for overflow in round_*_to_next_multiple_of
15021 functions, and add unit tests with additional and maximal values.
15022 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
15023 - Handle edge cases in the laplace functions: avoid division by
15024 zero, avoid taking the log of zero, and silence clang type
15025 conversion warnings using round and trunc. Add unit tests for edge
15026 cases with maximal values. Fixes part of bug 13192; bugfix
15028 - We now include consensus downloads via IPv6 in our directory-
15029 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
15031 o Minor bugfixes (test networks, IPv6):
15032 - Allow internal IPv6 addresses in descriptors in test networks.
15033 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
15036 o Minor bugfixes (testing):
15037 - Check the full results of SHA256 and SHA512 digests in the unit
15038 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
15039 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
15041 - Fix a small memory leak that would occur when the
15042 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
15043 bugfix on 0.2.5.2-alpha.
15044 - Make unit tests pass on IPv6-only systems, and systems without
15045 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
15046 bugfix on 0.2.7.3-rc. Patch by teor.
15047 - The test for log_heartbeat was incorrectly failing in timezones
15048 with non-integer offsets. Instead of comparing the end of the time
15049 string against a constant, compare it to the output of
15050 format_local_iso_time when given the correct input. Fixes bug
15051 18039; bugfix on 0.2.5.4-alpha.
15052 - We no longer disable assertions in the unit tests when coverage is
15053 enabled. Instead, we require you to say --disable-asserts-in-tests
15054 to the configure script if you need assertions disabled in the
15055 unit tests (for example, if you want to perform branch coverage).
15056 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
15058 o Minor bugfixes (time handling):
15059 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
15060 field. Otherwise, our unit tests crash on Windows. Fixes bug
15061 18977; bugfix on 0.2.2.25-alpha.
15062 - Avoid overflow in tor_timegm when parsing dates in and after 2038
15063 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
15064 0.0.2pre14. Patch by teor.
15066 o Minor bugfixes (tor-gencert):
15067 - Correctly handle the case where an authority operator enters a
15068 passphrase but sends an EOF before sending a newline. Fixes bug
15069 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
15071 o Code simplification and refactoring:
15072 - Clean up a little duplicated code in
15073 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
15075 - Decouple the list of streams waiting to be attached to circuits
15076 from the overall connection list. This change makes it possible to
15077 attach streams quickly while simplifying Tor's callgraph and
15078 avoiding O(N) scans of the entire connection list. Closes
15080 - Extract the more complicated parts of circuit_mark_for_close()
15081 into a new function that we run periodically before circuits are
15082 freed. This change removes more than half of the functions
15083 currently in the "blob". Closes ticket 17218.
15084 - Move logging of redundant policy entries in
15085 policies_parse_exit_policy_internal into its own function. Closes
15086 ticket 17608; patch from "juce".
15087 - Quote all the string interpolations in configure.ac -- even those
15088 which we are pretty sure can't contain spaces. Closes ticket
15089 17744. Patch from zerosion.
15090 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
15091 use them. Closes ticket 17926.
15092 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
15093 inplace, so there's no need to have a separate implementation for
15094 the non-inplace code. Closes ticket 18258. Patch from Malek.
15095 - Simplify return types for some crypto functions that can't
15096 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
15097 - When a direct directory request fails immediately on launch,
15098 instead of relaunching that request from inside the code that
15099 launches it, instead mark the connection for teardown. This change
15100 simplifies Tor's callback and prevents the directory-request
15101 launching code from invoking itself recursively. Closes
15105 - Add a description of the correct use of the '--keygen' command-
15106 line option. Closes ticket 17583; based on text by 's7r'.
15107 - Change build messages to refer to "Fedora" instead of "Fedora
15108 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
15109 Patches from "icanhasaccount" and "cypherpunks".
15110 - Document the contents of the 'datadir/keys' subdirectory in the
15111 manual page. Closes ticket 17621.
15112 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
15113 - Explain actual minima for BandwidthRate. Closes ticket 16382.
15114 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
15115 - Mention torspec URL in the manpage and point the reader to it
15116 whenever we mention a document that belongs in torspce. Fixes
15118 - Stop recommending use of nicknames to identify relays in our
15119 MapAddress documentation. Closes ticket 18312.
15121 o Removed features:
15122 - Remove client-side support for connecting to Tor relays running
15123 versions of Tor before 0.2.3.6-alpha. These relays didn't support
15124 the v3 TLS handshake protocol, and are no longer allowed on the
15125 Tor network. Implements the client side of ticket 11150. Based on
15126 patches by Tom van der Woerdt.
15127 - We no longer maintain an internal freelist in memarea.c.
15128 Allocators should be good enough to make this code unnecessary,
15129 and it's doubtful that it ever had any performance benefit.
15132 - Add unit tests to check for common RNG failure modes, such as
15133 returning all zeroes, identical values, or incrementing values
15134 (OpenSSL's rand_predictable feature). Patch by teor.
15135 - Always test both ed25519 backends, so that we can be sure that our
15136 batch-open replacement code works. Part of ticket 16794.
15137 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
15138 portion of ticket 16831.
15139 - Fix several warnings from clang's address sanitizer produced in
15141 - Log more information when the backtrace tests fail. Closes ticket
15142 17892. Patch from "cypherpunks."
15143 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
15144 util_format.c, directory.c, and options_validate.c. Closes tickets
15145 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
15147 - Treat backtrace test failures as expected on FreeBSD until we
15148 solve bug 17808. Closes ticket 18204.
15149 - Unit tests for directory_handle_command_get. Closes ticket 17004.
15150 Patch from Reinaldo de Souza Jr.
15153 Changes in version 0.2.7.6 - 2015-12-10
15154 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
15155 well as a minor bug in hidden service reliability.
15157 o Major bugfixes (guard selection):
15158 - Actually look at the Guard flag when selecting a new directory
15159 guard. When we implemented the directory guard design, we
15160 accidentally started treating all relays as if they have the Guard
15161 flag during guard selection, leading to weaker anonymity and worse
15162 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
15165 o Minor features (geoip):
15166 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
15169 o Minor bugfixes (compilation):
15170 - When checking for net/pfvar.h, include netinet/in.h if possible.
15171 This fixes transparent proxy detection on OpenBSD. Fixes bug
15172 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
15173 - Fix a compilation warning with Clang 3.6: Do not check the
15174 presence of an address which can never be NULL. Fixes bug 17781.
15176 o Minor bugfixes (correctness):
15177 - When displaying an IPv6 exit policy, include the mask bits
15178 correctly even when the number is greater than 31. Fixes bug
15179 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
15180 - The wrong list was used when looking up expired intro points in a
15181 rend service object, causing what we think could be reachability
15182 issues for hidden services, and triggering a BUG log. Fixes bug
15183 16702; bugfix on 0.2.7.2-alpha.
15184 - Fix undefined behavior in the tor_cert_checksig function. Fixes
15185 bug 17722; bugfix on 0.2.7.2-alpha.
15188 Changes in version 0.2.7.5 - 2015-11-20
15189 The Tor 0.2.7 release series is dedicated to the memory of Tor user
15190 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
15191 tirelessly to advocate human rights regardless of national borders,
15192 and oppose the encroachments of mass surveillance. He opposed national
15193 exceptionalism, he brought clarity to legal and policy debates, he
15194 understood and predicted the impact of mass surveillance on the world,
15195 and he laid the groundwork for resisting it. While serving on the Tor
15196 Project's board of directors, he brought us his uncompromising focus
15197 on technical excellence in the service of humankind. Caspar was an
15198 inimitable force for good and a wonderful friend. He was kind,
15199 humorous, generous, gallant, and believed we should protect one
15200 another without exception. We honor him here for his ideals, his
15201 efforts, and his accomplishments. Please honor his memory with works
15202 that would make him proud.
15204 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
15206 The 0.2.7 series adds a more secure identity key type for relays,
15207 improves cryptography performance, resolves several longstanding
15208 hidden-service performance issues, improves controller support for
15209 hidden services, and includes small bugfixes and performance
15210 improvements throughout the program. This release series also includes
15211 more tests than before, and significant simplifications to which parts
15212 of Tor invoke which others. For a full list of changes, see below.
15214 o New system requirements:
15215 - Tor no longer includes workarounds to support Libevent versions
15216 before 1.3e. Libevent 2.0 or later is recommended. Closes
15218 - Tor no longer supports copies of OpenSSL that are missing support
15219 for Elliptic Curve Cryptography. (We began using ECC when
15220 available in 0.2.4.8-alpha, for more safe and efficient key
15221 negotiation.) In particular, support for at least one of P256 or
15222 P224 is now required, with manual configuration needed if only
15223 P224 is available. Resolves ticket 16140.
15224 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
15225 on an operating system that has not upgraded to OpenSSL 1.0 or
15226 later, and you compile Tor from source, you will need to install a
15227 more recent OpenSSL to link Tor against.) These versions of
15228 OpenSSL are still supported by the OpenSSL, but the numerous
15229 cryptographic improvements in later OpenSSL releases makes them a
15230 clear choice. Resolves ticket 16034.
15232 o Major features (controller):
15233 - Add the ADD_ONION and DEL_ONION commands that allow the creation
15234 and management of hidden services via the controller. Closes
15236 - New "GETINFO onions/current" and "GETINFO onions/detached"
15237 commands to get information about hidden services created via the
15238 controller. Part of ticket 6411.
15239 - New HSFETCH command to launch a request for a hidden service
15240 descriptor. Closes ticket 14847.
15241 - New HSPOST command to upload a hidden service descriptor. Closes
15242 ticket 3523. Patch by "DonnchaC".
15244 o Major features (Ed25519 identity keys, Proposal 220):
15245 - Add support for offline encrypted Ed25519 master keys. To use this
15246 feature on your tor relay, run "tor --keygen" to make a new master
15247 key (or to make a new signing key if you already have a master
15248 key). Closes ticket 13642.
15249 - All relays now maintain a stronger identity key, using the Ed25519
15250 elliptic curve signature format. This master key is designed so
15251 that it can be kept offline. Relays also generate an online
15252 signing key, and a set of other Ed25519 keys and certificates.
15253 These are all automatically regenerated and rotated as needed.
15254 Implements part of ticket 12498.
15255 - Directory authorities now vote on Ed25519 identity keys along with
15256 RSA1024 keys. Implements part of ticket 12498.
15257 - Directory authorities track which Ed25519 identity keys have been
15258 used with which RSA1024 identity keys, and do not allow them to
15259 vary freely. Implements part of ticket 12498.
15260 - Microdescriptors now include Ed25519 identity keys. Implements
15261 part of ticket 12498.
15262 - Add a --newpass option to allow changing or removing the
15263 passphrase of an encrypted key with tor --keygen. Implements part
15265 - Add a new OfflineMasterKey option to tell Tor never to try loading
15266 or generating a secret Ed25519 identity key. You can use this in
15267 combination with tor --keygen to manage offline and/or encrypted
15268 Ed25519 keys. Implements ticket 16944.
15269 - On receiving a HUP signal, check to see whether the Ed25519
15270 signing key has changed, and reload it if so. Closes ticket 16790.
15271 - Significant usability improvements for Ed25519 key management. Log
15272 messages are better, and the code can recover from far more
15273 failure conditions. Thanks to "s7r" for reporting and diagnosing
15276 o Major features (ECC performance):
15277 - Improve the runtime speed of Ed25519 signature verification by
15278 using Ed25519-donna's batch verification support. Implements
15280 - Improve the speed of Ed25519 operations and Curve25519 keypair
15281 generation when built targeting 32 bit x86 platforms with SSE2
15282 available. Implements ticket 16535.
15283 - Improve the runtime speed of Ed25519 operations by using the
15284 public-domain Ed25519-donna by Andrew M. ("floodyberry").
15285 Implements ticket 16467.
15286 - Improve the runtime speed of the ntor handshake by using an
15287 optimized curve25519 basepoint scalarmult implementation from the
15288 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
15289 ideas by Adam Langley. Implements ticket 9663.
15291 o Major features (Hidden services):
15292 - Hidden services, if using the EntryNodes option, are required to
15293 use more than one EntryNode, in order to avoid a guard discovery
15294 attack. (This would only affect people who had configured hidden
15295 services and manually specified the EntryNodes option with a
15296 single entry-node. The impact was that it would be easy to
15297 remotely identify the guard node used by such a hidden service.
15298 See ticket for more information.) Fixes ticket 14917.
15299 - Add the torrc option HiddenServiceNumIntroductionPoints, to
15300 specify a fixed number of introduction points. Its maximum value
15301 is 10 and default is 3. Using this option can increase a hidden
15302 service's reliability under load, at the cost of making it more
15303 visible that the hidden service is facing extra load. Closes
15305 - Remove the adaptive algorithm for choosing the number of
15306 introduction points, which used to change the number of
15307 introduction points (poorly) depending on the number of
15308 connections the HS sees. Closes ticket 4862.
15310 o Major features (onion key cross-certification):
15311 - Relay descriptors now include signatures of their own identity
15312 keys, made using the TAP and ntor onion keys. These signatures
15313 allow relays to prove ownership of their own onion keys. Because
15314 of this change, microdescriptors will no longer need to include
15315 RSA identity keys. Implements proposal 228; closes ticket 12499.
15317 o Major bugfixes (client-side privacy, also in 0.2.6.9):
15318 - Properly separate out each SOCKSPort when applying stream
15319 isolation. The error occurred because each port's session group
15320 was being overwritten by a default value when the listener
15321 connection was initialized. Fixes bug 16247; bugfix on
15322 0.2.6.3-alpha. Patch by "jojelino".
15324 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
15325 - Stop refusing to store updated hidden service descriptors on a
15326 client. This reverts commit 9407040c59218 (which indeed fixed bug
15327 14219, but introduced a major hidden service reachability
15328 regression detailed in bug 16381). This is a temporary fix since
15329 we can live with the minor issue in bug 14219 (it just results in
15330 some load on the network) but the regression of 16381 is too much
15331 of a setback. First-round fix for bug 16381; bugfix
15334 o Major bugfixes (hidden services):
15335 - Revert commit that made directory authorities assign the HSDir
15336 flag to relays without a DirPort; this was bad because such relays
15337 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
15339 - When cannibalizing a circuit for an introduction point, always
15340 extend to the chosen exit node (creating a 4 hop circuit).
15341 Previously Tor would use the current circuit exit node, which
15342 changed the original choice of introduction point, and could cause
15343 the hidden service to skip excluded introduction points or
15344 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
15347 o Major bugfixes (memory leaks):
15348 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
15349 17398; bugfix on 0.2.6.1-alpha.
15351 o Major bugfixes (open file limit):
15352 - The open file limit wasn't checked before calling
15353 tor_accept_socket_nonblocking(), which would make Tor exceed the
15354 limit. Now, before opening a new socket, Tor validates the open
15355 file limit just before, and if the max has been reached, return an
15356 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
15358 o Major bugfixes (security, correctness):
15359 - Fix an error that could cause us to read 4 bytes before the
15360 beginning of an openssl string. This bug could be used to cause
15361 Tor to crash on systems with unusual malloc implementations, or
15362 systems with unusual hardening installed. Fixes bug 17404; bugfix
15365 o Major bugfixes (stability, also in 0.2.6.10):
15366 - Stop crashing with an assertion failure when parsing certain kinds
15367 of malformed or truncated microdescriptors. Fixes bug 16400;
15368 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
15369 by "cypherpunks_backup".
15370 - Stop random client-side assertion failures that could occur when
15371 connecting to a busy hidden service, or connecting to a hidden
15372 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
15375 o Minor features (client, SOCKS):
15376 - Add GroupWritable and WorldWritable options to unix-socket based
15377 SocksPort and ControlPort options. These options apply to a single
15378 socket, and override {Control,Socks}SocketsGroupWritable. Closes
15380 - Relax the validation done to hostnames in SOCKS5 requests, and
15381 allow a single trailing '.' to cope with clients that pass FQDNs
15382 using that syntax to explicitly indicate that the domain name is
15383 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
15384 - Relax the validation of hostnames in SOCKS5 requests, allowing the
15385 character '_' to appear, in order to cope with domains observed in
15386 the wild that are serving non-RFC compliant records. Resolves
15389 o Minor features (client-side privacy):
15390 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
15391 lifespan when IsolateSOCKSAuth and streams with SOCKS
15392 authentication are attached to the circuit. This allows
15393 applications like TorBrowser to manage circuit lifetime on their
15394 own. Implements feature 15482.
15395 - When logging malformed hostnames from SOCKS5 requests, respect
15396 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
15398 o Minor features (clock-jump tolerance):
15399 - Recover better when our clock jumps back many hours, like might
15400 happen for Tails or Whonix users who start with a very wrong
15401 hardware clock, use Tor to discover a more accurate time, and then
15402 fix their clock. Resolves part of ticket 8766.
15404 o Minor features (command-line interface):
15405 - Make --hash-password imply --hush to prevent unnecessary noise.
15406 Closes ticket 15542. Patch from "cypherpunks".
15407 - Print a warning whenever we find a relative file path being used
15408 as torrc option. Resolves issue 14018.
15410 o Minor features (compilation):
15411 - Give a warning as early as possible when trying to build with an
15412 unsupported OpenSSL version. Closes ticket 16901.
15413 - Use C99 variadic macros when the compiler is not GCC. This avoids
15414 failing compilations on MSVC, and fixes a log-file-based race
15415 condition in our old workarounds. Original patch from Gisle Vanem.
15417 o Minor features (control protocol):
15418 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
15419 the control protocol. Resolves ticket 15358.
15421 o Minor features (controller):
15422 - Add DirAuthority lines for default directory authorities to the
15423 output of the "GETINFO config/defaults" command if not already
15424 present. Implements ticket 14840.
15425 - Controllers can now use "GETINFO hs/client/desc/id/..." to
15426 retrieve items from the client's hidden service descriptor cache.
15427 Closes ticket 14845.
15428 - Implement a new controller command "GETINFO status/fresh-relay-
15429 descs" to fetch a descriptor/extrainfo pair that was generated on
15430 demand just for the controller's use. Implements ticket 14784.
15432 o Minor features (directory authorities):
15433 - Directory authorities no longer vote against the "Fast", "Stable",
15434 and "HSDir" flags just because they were going to vote against
15435 "Running": if the consensus turns out to be that the router was
15436 running, then the authority's vote should count. Patch from Peter
15437 Retzlaff; closes issue 8712.
15439 o Minor features (directory authorities, security, also in 0.2.6.9):
15440 - The HSDir flag given by authorities now requires the Stable flag.
15441 For the current network, this results in going from 2887 to 2806
15442 HSDirs. Also, it makes it harder for an attacker to launch a sybil
15443 attack by raising the effort for a relay to become Stable to
15444 require at the very least 7 days, while maintaining the 96 hours
15445 uptime requirement for HSDir. Implements ticket 8243.
15447 o Minor features (DoS-resistance):
15448 - Make it harder for attackers to overload hidden services with
15449 introductions, by blocking multiple introduction requests on the
15450 same circuit. Resolves ticket 15515.
15452 o Minor features (geoip):
15453 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
15456 o Minor features (hidden services):
15457 - Add the new options "HiddenServiceMaxStreams" and
15458 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
15459 limit the maximum number of simultaneous streams per circuit, and
15460 optionally tear down the circuit when the limit is exceeded. Part
15462 - Client now uses an introduction point failure cache to know when
15463 to fetch or keep a descriptor in their cache. Previously, failures
15464 were recorded implicitly, but not explicitly remembered. Closes
15466 - Relays need to have the Fast flag to get the HSDir flag. As this
15467 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
15468 drop. This change should make some attacks against the hidden
15469 service directory system harder. Fixes ticket 15963.
15470 - Turn on hidden service statistics collection by setting the torrc
15471 option HiddenServiceStatistics to "1" by default. (This keeps
15472 track only of the fraction of traffic used by hidden services, and
15473 the total number of hidden services in existence.) Closes
15475 - To avoid leaking HS popularity, don't cycle the introduction point
15476 when we've handled a fixed number of INTRODUCE2 cells but instead
15477 cycle it when a random number of introductions is reached, thus
15478 making it more difficult for an attacker to find out the amount of
15479 clients that have used the introduction point for a specific HS.
15480 Closes ticket 15745.
15482 o Minor features (logging):
15483 - Include the Tor version in all LD_BUG log messages, since people
15484 tend to cut and paste those into the bugtracker. Implements
15487 o Minor features (pluggable transports):
15488 - When launching managed pluggable transports on Linux systems,
15489 attempt to have the kernel deliver a SIGTERM on tor exit if the
15490 pluggable transport process is still running. Resolves
15492 - When launching managed pluggable transports, setup a valid open
15493 stdin in the child process that can be used to detect if tor has
15494 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
15495 can be used by implementations to detect this new behavior.
15496 Resolves ticket 15435.
15498 o Minor bugfixes (torrc exit policies):
15499 - In each instance above, usage advice is provided to avoid the
15500 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
15501 16069; bugfix on 0.2.4.7-alpha.
15502 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
15503 produce IPv6 wildcard addresses. Previously they would produce
15504 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
15505 of bug 16069; bugfix on 0.2.4.7-alpha.
15506 - When parsing torrc ExitPolicies, we now issue an info-level
15507 message when expanding an "accept/reject *" line to include both
15508 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
15509 - When parsing torrc ExitPolicies, we now warn for a number of cases
15510 where the user's intent is likely to differ from Tor's actual
15511 behavior. These include: using an IPv4 address with an accept6 or
15512 reject6 line; using "private" on an accept6 or reject6 line; and
15513 including any ExitPolicy lines after accept *:* or reject *:*.
15514 Related to ticket 16069.
15516 o Minor bugfixes (command-line interface):
15517 - When "--quiet" is provided along with "--validate-config", do not
15518 write anything to stdout on success. Fixes bug 14994; bugfix
15520 - When complaining about bad arguments to "--dump-config", use
15521 stderr, not stdout.
15522 - Print usage information for --dump-config when it is used without
15523 an argument. Also, fix the error message to use different wording
15524 and add newline at the end. Fixes bug 15541; bugfix
15527 o Minor bugfixes (compilation):
15528 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
15529 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
15530 - Repair compilation with the most recent (unreleased, alpha)
15531 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
15533 o Minor bugfixes (compilation, also in 0.2.6.9):
15534 - Build with --enable-systemd correctly when libsystemd is
15535 installed, but systemd is not. Fixes bug 16164; bugfix on
15536 0.2.6.3-alpha. Patch from Peter Palfrader.
15538 o Minor bugfixes (configuration, unit tests):
15539 - Only add the default fallback directories when the DirAuthorities,
15540 AlternateDirAuthority, and FallbackDir directory config options
15541 are set to their defaults. The default fallback directory list is
15542 currently empty, this fix will only change tor's behavior when it
15543 has default fallback directories. Includes unit tests for
15544 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
15545 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
15547 o Minor bugfixes (controller):
15548 - Add the descriptor ID in each HS_DESC control event. It was
15549 missing, but specified in control-spec.txt. Fixes bug 15881;
15550 bugfix on 0.2.5.2-alpha.
15552 o Minor bugfixes (correctness):
15553 - For correctness, avoid modifying a constant string in
15554 handle_control_postdescriptor. Fixes bug 15546; bugfix
15556 - Remove side-effects from tor_assert() calls. This was harmless,
15557 because we never disable assertions, but it is bad style and
15558 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
15560 - When calling channel_free_list(), avoid calling smartlist_remove()
15561 while inside a FOREACH loop. This partially reverts commit
15562 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
15563 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
15565 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
15566 - Check for failures from crypto_early_init, and refuse to continue.
15567 A previous typo meant that we could keep going with an
15568 uninitialized crypto library, and would have OpenSSL initialize
15569 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
15570 when implementing ticket 4900. Patch by "teor".
15572 o Minor bugfixes (hidden service):
15573 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
15574 a client authorized hidden service. Fixes bug 15823; bugfix
15576 - Remove an extraneous newline character from the end of hidden
15577 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
15579 o Minor bugfixes (Linux seccomp2 sandbox):
15580 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
15581 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
15582 - Allow bridge authorities to run correctly under the seccomp2
15583 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
15584 - Add the "hidserv-stats" filename to our sandbox filter for the
15585 HiddenServiceStatistics option to work properly. Fixes bug 17354;
15586 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
15588 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
15589 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
15590 these when eventfd2() support is missing. Fixes bug 16363; bugfix
15591 on 0.2.6.3-alpha. Patch from "teor".
15593 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
15594 - Allow systemd connections to work with the Linux seccomp2 sandbox
15595 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
15597 - Fix sandboxing to work when running as a relay, by allowing the
15598 renaming of secret_id_key, and allowing the eventfd2 and futex
15599 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
15602 o Minor bugfixes (logging):
15603 - When building Tor under Clang, do not include an extra set of
15604 parentheses in log messages that include function names. Fixes bug
15605 15269; bugfix on every released version of Tor when compiled with
15606 recent enough Clang.
15608 o Minor bugfixes (network):
15609 - When attempting to use fallback technique for network interface
15610 lookup, disregard loopback and multicast addresses since they are
15611 unsuitable for public communications.
15613 o Minor bugfixes (open file limit):
15614 - Fix set_max_file_descriptors() to set by default the max open file
15615 limit to the current limit when setrlimit() fails. Fixes bug
15616 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
15618 o Minor bugfixes (portability):
15619 - Check correctly for Windows socket errors in the workqueue
15620 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
15621 - Try harder to normalize the exit status of the Tor process to the
15622 standard-provided range. Fixes bug 16975; bugfix on every version
15624 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
15625 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
15627 o Minor bugfixes (relay):
15628 - Ensure that worker threads actually exit when a fatal error or
15629 shutdown is indicated. This fix doesn't currently affect the
15630 behavior of Tor, because Tor workers never indicates fatal error
15631 or shutdown except in the unit tests. Fixes bug 16868; bugfix
15633 - Fix a rarely-encountered memory leak when failing to initialize
15634 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
15635 from "cypherpunks".
15636 - Unblock threads before releasing the work queue mutex to ensure
15637 predictable scheduling behavior. Fixes bug 16644; bugfix
15640 o Minor bugfixes (security, exit policies):
15641 - ExitPolicyRejectPrivate now also rejects the relay's published
15642 IPv6 address (if any), and any publicly routable IPv4 or IPv6
15643 addresses on any local interfaces. ticket 17027. Patch by "teor".
15644 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
15646 o Minor bugfixes (statistics):
15647 - Disregard the ConnDirectionStatistics torrc options when Tor is
15648 not a relay since in that mode of operation no sensible data is
15649 being collected and because Tor might run into measurement hiccups
15650 when running as a client for some time, then becoming a relay.
15651 Fixes bug 15604; bugfix on 0.2.2.35.
15653 o Minor bugfixes (systemd):
15654 - Tor's systemd unit file no longer contains extraneous spaces.
15655 These spaces would sometimes confuse tools like deb-systemd-
15656 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
15658 o Minor bugfixes (test networks):
15659 - When self-testing reachability, use ExtendAllowPrivateAddresses to
15660 determine if local/private addresses imply reachability. The
15661 previous fix used TestingTorNetwork, which implies
15662 ExtendAllowPrivateAddresses, but this excluded rare configurations
15663 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
15664 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
15665 issue discovered by CJ Ess.
15667 o Minor bugfixes (tests, also in 0.2.6.9):
15668 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
15669 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
15671 o Code simplification and refactoring:
15672 - Change the function that's called when we need to retry all
15673 downloads so that it only reschedules the downloads to happen
15674 immediately, rather than launching them all at once itself. This
15675 further simplifies Tor's callgraph.
15676 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
15677 to ensure they remain consistent and visible everywhere.
15678 - Move some format-parsing functions out of crypto.c and
15679 crypto_curve25519.c into crypto_format.c and/or util_format.c.
15680 - Move the client-only parts of init_keys() into a separate
15681 function. Closes ticket 16763.
15682 - Move the hacky fallback code out of get_interface_address6() into
15683 separate function and get it covered with unit-tests. Resolves
15685 - Refactor hidden service client-side cache lookup to intelligently
15686 report its various failure cases, and disentangle failure cases
15687 involving a lack of introduction points. Closes ticket 14391.
15688 - Remove some vestigial workarounds for the MSVC6 compiler. We
15689 haven't supported that in ages.
15690 - Remove the unused "nulterminate" argument from buf_pullup().
15691 - Simplify the microdesc_free() implementation so that it no longer
15692 appears (to code analysis tools) to potentially invoke a huge
15693 suite of other microdesc functions.
15694 - Simply the control graph further by deferring the inner body of
15695 directory_all_unreachable() into a callback. Closes ticket 16762.
15696 - The link authentication code has been refactored for better
15697 testability and reliability. It now uses code generated with the
15698 "trunnel" binary encoding generator, to reduce the risk of bugs
15699 due to programmer error. Done as part of ticket 12498.
15700 - Treat the loss of an owning controller as equivalent to a SIGTERM
15701 signal. This removes a tiny amount of duplicated code, and
15702 simplifies our callgraph. Closes ticket 16788.
15703 - Use our own Base64 encoder instead of OpenSSL's, to allow more
15704 control over the output. Part of ticket 15652.
15705 - When generating an event to send to the controller, we no longer
15706 put the event over the network immediately. Instead, we queue
15707 these events, and use a Libevent callback to deliver them. This
15708 change simplifies Tor's callgraph by reducing the number of
15709 functions from which all other Tor functions are reachable. Closes
15711 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
15712 that try to scan or compile every file on Unix won't decide that
15716 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
15717 - Improve the descriptions of statistics-related torrc options in
15718 the manpage to describe rationale and possible uses cases. Fixes
15720 - Improve the layout and formatting of ./configure --help messages.
15721 Closes ticket 15024. Patch from "cypherpunks".
15722 - Include a specific and (hopefully) accurate documentation of the
15723 torrc file's meta-format in doc/torrc_format.txt. This is mainly
15724 of interest to people writing programs to parse or generate torrc
15725 files. This document is not a commitment to long-term
15726 compatibility; some aspects of the current format are a bit
15727 ridiculous. Closes ticket 2325.
15728 - Include the TUNING document in our source tarball. It is referred
15729 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
15731 - Note that HiddenServicePorts can take a unix domain socket. Closes
15733 - Recommend a 40 GB example AccountingMax in torrc.sample rather
15734 than a 4 GB max. Closes ticket 16742.
15735 - Standardize on the term "server descriptor" in the manual page.
15736 Previously, we had used "router descriptor", "server descriptor",
15737 and "relay descriptor" interchangeably. Part of ticket 14987.
15738 - Advise users on how to configure separate IPv4 and IPv6 exit
15739 policies in the manpage and sample torrcs. Related to ticket 16069.
15740 - Fix an error in the manual page and comments for
15741 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
15742 required "ORPort connectivity". While this is true, it is in no
15743 way unique to the HSDir flag. Of all the flags, only HSDirs need a
15744 DirPort configured in order for the authorities to assign that
15745 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
15747 - Fix the usage message of tor-resolve(1) so that it no longer lists
15748 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
15751 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
15752 and always use the internal Base64 decoder. The internal decoder
15753 has been part of tor since 0.2.0.10-alpha, and no one should
15754 be using the OpenSSL one. Part of ticket 15652.
15755 - Remove the 'tor_strclear()' function; use memwipe() instead.
15756 Closes ticket 14922.
15757 - Remove the code that would try to aggressively flush controller
15758 connections while writing to them. This code was introduced in
15759 0.1.2.7-alpha, in order to keep output buffers from exceeding
15760 their limits. But there is no longer a maximum output buffer size,
15761 and flushing data in this way caused some undesirable recursions
15762 in our call graph. Closes ticket 16480.
15763 - The internal pure-C tor-fw-helper tool is now removed from the Tor
15764 distribution, in favor of the pure-Go clone available from
15765 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
15766 used by the C tor-fw-helper are not, in our opinion, very
15767 confidence- inspiring in their secure-programming techniques.
15768 Closes ticket 13338.
15770 o Removed features:
15771 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
15772 fingerprinting we now recommend pluggable transports; for forward-
15773 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
15774 - Remove the HidServDirectoryV2 option. Now all relays offer to
15775 store hidden service descriptors. Related to 16543.
15776 - Remove the VoteOnHidServDirectoriesV2 option, since all
15777 authorities have long set it to 1. Closes ticket 16543.
15778 - Remove the undocumented "--digests" command-line option. It
15779 complicated our build process, caused subtle build issues on
15780 multiple platforms, and is now redundant since we started
15781 including git version identifiers. Closes ticket 14742.
15782 - Tor no longer contains checks for ancient directory cache versions
15783 that didn't know about microdescriptors.
15784 - Tor no longer contains workarounds for stat files generated by
15785 super-old versions of Tor that didn't choose guards sensibly.
15788 - The test-network.sh script now supports performance testing.
15789 Requires corresponding chutney performance testing changes. Patch
15790 by "teor". Closes ticket 14175.
15791 - Add a new set of callgraph analysis scripts that use clang to
15792 produce a list of which Tor functions are reachable from which
15793 other Tor functions. We're planning to use these to help simplify
15794 our code structure by identifying illogical dependencies.
15795 - Add new 'test-full' and 'test-full-online' targets to run all
15796 tests, including integration tests with stem and chutney.
15797 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
15798 by-side in the same parent directory. Closes ticket 16903. Patch
15800 - Document use of coverity, clang static analyzer, and clang dynamic
15801 undefined behavior and address sanitizers in doc/HACKING. Include
15802 detailed usage instructions in the blacklist. Patch by "teor".
15803 Closes ticket 15817.
15804 - Make "bridges+hs" the default test network. This tests almost all
15805 tor functionality during make test-network, while allowing tests
15806 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
15807 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
15808 (chutney). Patches by "teor".
15809 - Make the test-workqueue test work on Windows by initializing the
15810 network before we begin.
15811 - New make target (make test-network-all) to run multiple applicable
15812 chutney test cases. Patch from Teor; closes 16953.
15813 - Now that OpenSSL has its own scrypt implementation, add an unit
15814 test that checks for interoperability between libscrypt_scrypt()
15815 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
15816 and rely on EVP_PBE_scrypt() whenever possible. Resolves
15818 - The link authentication protocol code now has extensive tests.
15819 - The relay descriptor signature testing code now has
15821 - The test_workqueue program now runs faster, and is enabled by
15822 default as a part of "make check".
15823 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
15824 functions in dns.c. Implements a portion of ticket 16831.
15825 - Use environment variables rather than autoconf substitutions to
15826 send variables from the build system to the test scripts. This
15827 change should be easier to maintain, and cause 'make distcheck' to
15828 work better than before. Fixes bug 17148.
15829 - When building Tor with testing coverage enabled, run Chutney tests
15830 (if any) using the 'tor-cov' coverage binary.
15831 - When running test-network or test-stem, check for the absence of
15832 stem/chutney before doing any build operations.
15833 - Add a test to verify that the compiler does not eliminate our
15834 memwipe() implementation. Closes ticket 15377.
15835 - Add make rule `check-changes` to verify the format of changes
15836 files. Closes ticket 15180.
15837 - Add unit tests for control_event_is_interesting(). Add a compile-
15838 time check that the number of events doesn't exceed the capacity
15839 of control_event_t.event_mask. Closes ticket 15431, checks for
15840 bugs similar to 13085. Patch by "teor".
15841 - Command-line argument tests moved to Stem. Resolves ticket 14806.
15842 - Integrate the ntor, backtrace, and zero-length keys tests into the
15843 automake test suite. Closes ticket 15344.
15844 - Remove assertions during builds to determine Tor's test coverage.
15845 We don't want to trigger these even in assertions, so including
15846 them artificially makes our branch coverage look worse than it is.
15847 This patch provides the new test-stem-full and coverage-html-full
15848 configure options. Implements ticket 15400.
15849 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
15850 explicitly manage consensus flags in testing networks. Patch by
15851 "robgjansen", modified by "teor". Implements part of ticket 14882.
15852 - Check for matching value in server response in ntor_ref.py. Fixes
15853 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
15855 - Set the severity correctly when testing
15856 get_interface_addresses_ifaddrs() and
15857 get_interface_addresses_win32(), so that the tests fail gracefully
15858 instead of triggering an assertion. Fixes bug 15759; bugfix on
15859 0.2.6.3-alpha. Reported by Nicolas Derive.
15861 Changes in version 0.2.6.10 - 2015-07-12
15862 Tor version 0.2.6.10 fixes some significant stability and hidden
15863 service client bugs, bulletproofs the cryptography init process, and
15864 fixes a bug when using the sandbox code with some older versions of
15865 Linux. Everyone running an older version, especially an older version
15866 of 0.2.6, should upgrade.
15868 o Major bugfixes (hidden service clients, stability):
15869 - Stop refusing to store updated hidden service descriptors on a
15870 client. This reverts commit 9407040c59218 (which indeed fixed bug
15871 14219, but introduced a major hidden service reachability
15872 regression detailed in bug 16381). This is a temporary fix since
15873 we can live with the minor issue in bug 14219 (it just results in
15874 some load on the network) but the regression of 16381 is too much
15875 of a setback. First-round fix for bug 16381; bugfix
15878 o Major bugfixes (stability):
15879 - Stop crashing with an assertion failure when parsing certain kinds
15880 of malformed or truncated microdescriptors. Fixes bug 16400;
15881 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
15882 by "cypherpunks_backup".
15883 - Stop random client-side assertion failures that could occur when
15884 connecting to a busy hidden service, or connecting to a hidden
15885 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
15888 o Minor features (geoip):
15889 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
15890 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
15892 o Minor bugfixes (crypto error-handling):
15893 - Check for failures from crypto_early_init, and refuse to continue.
15894 A previous typo meant that we could keep going with an
15895 uninitialized crypto library, and would have OpenSSL initialize
15896 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
15897 when implementing ticket 4900. Patch by "teor".
15899 o Minor bugfixes (Linux seccomp2 sandbox):
15900 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
15901 these when eventfd2() support is missing. Fixes bug 16363; bugfix
15902 on 0.2.6.3-alpha. Patch from "teor".
15905 Changes in version 0.2.6.9 - 2015-06-11
15906 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
15907 requirements for receiving an HSDir flag, and addresses some other small
15908 bugs in the systemd and sandbox code. Clients using circuit isolation
15909 should upgrade; all directory authorities should upgrade.
15911 o Major bugfixes (client-side privacy):
15912 - Properly separate out each SOCKSPort when applying stream
15913 isolation. The error occurred because each port's session group was
15914 being overwritten by a default value when the listener connection
15915 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
15918 o Minor feature (directory authorities, security):
15919 - The HSDir flag given by authorities now requires the Stable flag.
15920 For the current network, this results in going from 2887 to 2806
15921 HSDirs. Also, it makes it harder for an attacker to launch a sybil
15922 attack by raising the effort for a relay to become Stable which
15923 takes at the very least 7 days to do so and by keeping the 96
15924 hours uptime requirement for HSDir. Implements ticket 8243.
15926 o Minor bugfixes (compilation):
15927 - Build with --enable-systemd correctly when libsystemd is
15928 installed, but systemd is not. Fixes bug 16164; bugfix on
15929 0.2.6.3-alpha. Patch from Peter Palfrader.
15931 o Minor bugfixes (Linux seccomp2 sandbox):
15932 - Fix sandboxing to work when running as a relaymby renaming of
15933 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
15934 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
15935 - Allow systemd connections to work with the Linux seccomp2 sandbox
15936 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
15939 o Minor bugfixes (tests):
15940 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
15941 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
15944 Changes in version 0.2.6.8 - 2015-05-21
15945 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
15946 fixes an authority-side bug in assigning the HSDir flag. All directory
15947 authorities should upgrade.
15949 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
15950 - Revert commit that made directory authorities assign the HSDir
15951 flag to relays without a DirPort; this was bad because such relays
15952 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
15955 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
15956 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
15957 a client authorized hidden service. Fixes bug 15823; bugfix
15960 o Minor features (geoip):
15961 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
15962 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
15966 Changes in version 0.2.6.7 - 2015-04-06
15967 Tor 0.2.6.7 fixes two security issues that could be used by an
15968 attacker to crash hidden services, or crash clients visiting hidden
15969 services. Hidden services should upgrade as soon as possible; clients
15970 should upgrade whenever packages become available.
15972 This release also contains two simple improvements to make hidden
15973 services a bit less vulnerable to denial-of-service attacks.
15975 o Major bugfixes (security, hidden service):
15976 - Fix an issue that would allow a malicious client to trigger an
15977 assertion failure and halt a hidden service. Fixes bug 15600;
15978 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
15979 - Fix a bug that could cause a client to crash with an assertion
15980 failure when parsing a malformed hidden service descriptor. Fixes
15981 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
15983 o Minor features (DoS-resistance, hidden service):
15984 - Introduction points no longer allow multiple INTRODUCE1 cells to
15985 arrive on the same circuit. This should make it more expensive for
15986 attackers to overwhelm hidden services with introductions.
15987 Resolves ticket 15515.
15988 - Decrease the amount of reattempts that a hidden service performs
15989 when its rendezvous circuits fail. This reduces the computational
15990 cost for running a hidden service under heavy load. Resolves
15994 Changes in version 0.2.5.12 - 2015-04-06
15995 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
15996 could be used by an attacker to crash hidden services, or crash clients
15997 visiting hidden services. Hidden services should upgrade as soon as
15998 possible; clients should upgrade whenever packages become available.
16000 This release also backports a simple improvement to make hidden
16001 services a bit less vulnerable to denial-of-service attacks.
16003 o Major bugfixes (security, hidden service):
16004 - Fix an issue that would allow a malicious client to trigger an
16005 assertion failure and halt a hidden service. Fixes bug 15600;
16006 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
16007 - Fix a bug that could cause a client to crash with an assertion
16008 failure when parsing a malformed hidden service descriptor. Fixes
16009 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
16011 o Minor features (DoS-resistance, hidden service):
16012 - Introduction points no longer allow multiple INTRODUCE1 cells to
16013 arrive on the same circuit. This should make it more expensive for
16014 attackers to overwhelm hidden services with introductions.
16015 Resolves ticket 15515.
16018 Changes in version 0.2.4.27 - 2015-04-06
16019 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
16020 could be used by an attacker to crash hidden services, or crash clients
16021 visiting hidden services. Hidden services should upgrade as soon as
16022 possible; clients should upgrade whenever packages become available.
16024 This release also backports a simple improvement to make hidden
16025 services a bit less vulnerable to denial-of-service attacks.
16027 o Major bugfixes (security, hidden service):
16028 - Fix an issue that would allow a malicious client to trigger an
16029 assertion failure and halt a hidden service. Fixes bug 15600;
16030 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
16031 - Fix a bug that could cause a client to crash with an assertion
16032 failure when parsing a malformed hidden service descriptor. Fixes
16033 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
16035 o Minor features (DoS-resistance, hidden service):
16036 - Introduction points no longer allow multiple INTRODUCE1 cells to
16037 arrive on the same circuit. This should make it more expensive for
16038 attackers to overwhelm hidden services with introductions.
16039 Resolves ticket 15515.
16042 Changes in version 0.2.6.6 - 2015-03-24
16043 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
16045 It adds numerous safety, security, correctness, and performance
16046 improvements. Client programs can be configured to use more kinds of
16047 sockets, AutomapHosts works better, the multithreading backend is
16048 improved, cell transmission is refactored, test coverage is much
16049 higher, more denial-of-service attacks are handled, guard selection is
16050 improved to handle long-term guards better, pluggable transports
16051 should work a bit better, and some annoying hidden service performance
16052 bugs should be addressed.
16054 o New compiler and system requirements:
16055 - Tor 0.2.6.x requires that your compiler support more of the C99
16056 language standard than before. The 'configure' script now detects
16057 whether your compiler supports C99 mid-block declarations and
16058 designated initializers. If it does not, Tor will not compile.
16060 We may revisit this requirement if it turns out that a significant
16061 number of people need to build Tor with compilers that don't
16062 bother implementing a 15-year-old standard. Closes ticket 13233.
16063 - Tor no longer supports systems without threading support. When we
16064 began working on Tor, there were several systems that didn't have
16065 threads, or where the thread support wasn't able to run the
16066 threads of a single process on multiple CPUs. That no longer
16067 holds: every system where Tor needs to run well now has threading
16068 support. Resolves ticket 12439.
16070 o Deprecated versions and removed support:
16071 - Tor relays older than 0.2.4.18-rc are no longer allowed to
16072 advertise themselves on the network. Closes ticket 13555.
16073 - Tor clients no longer support connecting to hidden services
16074 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
16075 option has been removed. (There shouldn't be any hidden services
16076 running these versions on the network.) Closes ticket 7803.
16078 o Directory authority changes:
16079 - The directory authority Faravahar has a new IP address. This
16080 closes ticket 14487.
16081 - Remove turtles as a directory authority.
16082 - Add longclaw as a new (v3) directory authority. This implements
16083 ticket 13296. This keeps the directory authority count at 9.
16085 o Major features (bridges):
16086 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
16087 transports if they are configured via the "TOR_PT_PROXY"
16088 environment variable. Implements proposal 232. Resolves
16091 o Major features (changed defaults):
16092 - Prevent relay operators from unintentionally running exits: When a
16093 relay is configured as an exit node, we now warn the user unless
16094 the "ExitRelay" option is set to 1. We warn even more loudly if
16095 the relay is configured with the default exit policy, since this
16096 can indicate accidental misconfiguration. Setting "ExitRelay 0"
16097 stops Tor from running as an exit relay. Closes ticket 10067.
16099 o Major features (client performance, hidden services):
16100 - Allow clients to use optimistic data when connecting to a hidden
16101 service, which should remove a round-trip from hidden service
16102 initialization. See proposal 181 for details. Implements
16105 o Major features (directory system):
16106 - Upon receiving an unparseable directory object, if its digest
16107 matches what we expected, then don't try to download it again.
16108 Previously, when we got a descriptor we didn't like, we would keep
16109 trying to download it over and over. Closes ticket 11243.
16110 - When downloading server- or microdescriptors from a directory
16111 server, we no longer launch multiple simultaneous requests to the
16112 same server. This reduces load on the directory servers,
16113 especially when directory guards are in use. Closes ticket 9969.
16114 - When downloading server- or microdescriptors over a tunneled
16115 connection, do not limit the length of our requests to what the
16116 Squid proxy is willing to handle. Part of ticket 9969.
16117 - Authorities can now vote on the correct digests and latest
16118 versions for different software packages. This allows packages
16119 that include Tor to use the Tor authority system as a way to get
16120 notified of updates and their correct digests. Implements proposal
16121 227. Closes ticket 10395.
16123 o Major features (guards):
16124 - Introduce the Guardfraction feature to improves load balancing on
16125 guard nodes. Specifically, it aims to reduce the traffic gap that
16126 guard nodes experience when they first get the Guard flag. This is
16127 a required step if we want to increase the guard lifetime to 9
16128 months or greater. Closes ticket 9321.
16130 o Major features (hidden services):
16131 - Make HS port scanning more difficult by immediately closing the
16132 circuit when a user attempts to connect to a nonexistent port.
16133 Closes ticket 13667.
16134 - Add a HiddenServiceStatistics option that allows Tor relays to
16135 gather and publish statistics about the overall size and volume of
16136 hidden service usage. Specifically, when this option is turned on,
16137 an HSDir will publish an approximate number of hidden services
16138 that have published descriptors to it the past 24 hours. Also, if
16139 a relay has acted as a hidden service rendezvous point, it will
16140 publish the approximate amount of rendezvous cells it has relayed
16141 the past 24 hours. The statistics themselves are obfuscated so
16142 that the exact values cannot be derived. For more details see
16143 proposal 238, "Better hidden service stats from Tor relays". This
16144 feature is currently disabled by default. Implements feature 13192.
16146 o Major features (performance):
16147 - Make the CPU worker implementation more efficient by avoiding the
16148 kernel and lengthening pipelines. The original implementation used
16149 sockets to transfer data from the main thread to the workers, and
16150 didn't allow any thread to be assigned more than a single piece of
16151 work at once. The new implementation avoids communications
16152 overhead by making requests in shared memory, avoiding kernel IO
16153 where possible, and keeping more requests in flight at once.
16154 Implements ticket 9682.
16156 o Major features (relay):
16157 - Raise the minimum acceptable configured bandwidth rate for bridges
16158 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
16159 20 KiB/sec.) Closes ticket 13822.
16160 - Complete revision of the code that relays use to decide which cell
16161 to send next. Formerly, we selected the best circuit to write on
16162 each channel, but we didn't select among channels in any
16163 sophisticated way. Now, we choose the best circuits globally from
16164 among those whose channels are ready to deliver traffic.
16166 This patch implements a new inter-cmux comparison API, a global
16167 high/low watermark mechanism and a global scheduler loop for
16168 transmission prioritization across all channels as well as among
16169 circuits on one channel. This schedule is currently tuned to
16170 (tolerantly) avoid making changes in network performance, but it
16171 should form the basis for major circuit performance increases in
16172 the future. Code by Andrea; tuning by Rob Jansen; implements
16175 o Major features (sample torrc):
16176 - Add a new, infrequently-changed "torrc.minimal". This file is
16177 similar to torrc.sample, but it will change as infrequently as
16178 possible, for the benefit of users whose systems prompt them for
16179 intervention whenever a default configuration file is changed.
16180 Making this change allows us to update torrc.sample to be a more
16181 generally useful "sample torrc".
16183 o Major features (security, unix domain sockets):
16184 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
16185 applications can reach Tor without having to create AF_INET or
16186 AF_INET6 sockets, meaning they can completely disable their
16187 ability to make non-Tor network connections. To create a socket of
16188 this type, use "SocksPort unix:/path/to/socket". Implements
16190 - Support mapping hidden service virtual ports to AF_UNIX sockets.
16191 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
16192 Implements ticket 11485.
16194 o Major bugfixes (client, automap):
16195 - Repair automapping with IPv6 addresses. This automapping should
16196 have worked previously, but one piece of debugging code that we
16197 inserted to detect a regression actually caused the regression to
16198 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
16199 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
16202 o Major bugfixes (crash, OSX, security):
16203 - Fix a remote denial-of-service opportunity caused by a bug in
16204 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
16207 o Major bugfixes (directory authorities):
16208 - Do not assign the HSDir flag to relays if they are not Valid, or
16209 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
16211 o Major bugfixes (directory bandwidth performance):
16212 - Don't flush the zlib buffer aggressively when compressing
16213 directory information for clients. This should save about 7% of
16214 the bandwidth currently used for compressed descriptors and
16215 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
16217 o Major bugfixes (exit node stability):
16218 - Fix an assertion failure that could occur under high DNS load.
16219 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
16220 diagnosed and fixed by "cypherpunks".
16222 o Major bugfixes (FreeBSD IPFW transparent proxy):
16223 - Fix address detection with FreeBSD transparent proxies, when
16224 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
16227 o Major bugfixes (hidden services):
16228 - When closing an introduction circuit that was opened in parallel
16229 with others, don't mark the introduction point as unreachable.
16230 Previously, the first successful connection to an introduction
16231 point would make the other introduction points get marked as
16232 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
16234 o Major bugfixes (Linux seccomp2 sandbox):
16235 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
16236 crash during attempts to call wait4. Fixes bug 15088; bugfix on
16237 0.2.5.1-alpha. Patch from "sanic".
16239 o Major bugfixes (mixed relay-client operation):
16240 - When running as a relay and client at the same time (not
16241 recommended), if we decide not to use a new guard because we want
16242 to retry older guards, only close the locally-originating circuits
16243 passing through that guard. Previously we would close all the
16244 circuits through that guard. Fixes bug 9819; bugfix on
16245 0.2.1.1-alpha. Reported by "skruffy".
16247 o Major bugfixes (pluggable transports):
16248 - Initialize the extended OR Port authentication cookie before
16249 launching pluggable transports. This prevents a race condition
16250 that occurred when server-side pluggable transports would cache the
16251 authentication cookie before it has been (re)generated. Fixes bug
16252 15240; bugfix on 0.2.5.1-alpha.
16254 o Major bugfixes (relay, stability, possible security):
16255 - Fix a bug that could lead to a relay crashing with an assertion
16256 failure if a buffer of exactly the wrong layout is passed to
16257 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
16258 0.2.0.10-alpha. Patch from "cypherpunks".
16259 - Do not assert if the 'data' pointer on a buffer is advanced to the
16260 very end of the buffer; log a BUG message instead. Only assert if
16261 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
16263 o Minor features (build):
16264 - New --disable-system-torrc compile-time option to prevent Tor from
16265 looking for the system-wide torrc or torrc-defaults files.
16266 Resolves ticket 13037.
16268 o Minor features (client):
16269 - Clients are now willing to send optimistic data (before they
16270 receive a 'connected' cell) to relays of any version. (Relays
16271 without support for optimistic data are no longer supported on the
16272 Tor network.) Resolves ticket 13153.
16274 o Minor features (client):
16275 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
16276 is enabled, reject requests with IP addresses as hostnames.
16277 Resolves ticket 13315.
16279 o Minor features (controller):
16280 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
16281 write an unscheduled heartbeat message to the log. Implements
16283 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
16284 events so controllers can observe circuit isolation inputs. Closes
16286 - ControlPort now supports the unix:/path/to/socket syntax as an
16287 alternative to the ControlSocket option, for consistency with
16288 SocksPort and HiddenServicePort. Closes ticket 14451.
16289 - New "GETINFO bw-event-cache" to get information about recent
16290 bandwidth events. Closes ticket 14128. Useful for controllers to
16291 get recent bandwidth history after the fix for ticket 13988.
16292 - Messages about problems in the bootstrap process now include
16293 information about the server we were trying to connect to when we
16294 noticed the problem. Closes ticket 15006.
16296 o Minor features (Denial of service resistance):
16297 - Count the total number of bytes used storing hidden service
16298 descriptors against the value of MaxMemInQueues. If we're low on
16299 memory, and more than 20% of our memory is used holding hidden
16300 service descriptors, free them until no more than 10% of our
16301 memory holds hidden service descriptors. Free the least recently
16302 fetched descriptors first. Resolves ticket 13806.
16303 - When we have recently been under memory pressure (over 3/4 of
16304 MaxMemInQueues is allocated), then allocate smaller zlib objects
16305 for small requests. Closes ticket 11791.
16307 o Minor features (directory authorities):
16308 - Don't list relays with a bandwidth estimate of 0 in the consensus.
16309 Implements a feature proposed during discussion of bug 13000.
16310 - In tor-gencert, report an error if the user provides the same
16311 argument more than once.
16312 - If a directory authority can't find a best consensus method in the
16313 votes that it holds, it now falls back to its favorite consensus
16314 method. Previously, it fell back to method 1. Neither of these is
16315 likely to get enough signatures, but "fall back to favorite"
16316 doesn't require us to maintain support an obsolete consensus
16317 method. Implements part of proposal 215.
16319 o Minor features (geoip):
16320 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
16321 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
16324 o Minor features (guard nodes):
16325 - Reduce the time delay before saving guard status to disk from 10
16326 minutes to 30 seconds (or from one hour to 10 minutes if
16327 AvoidDiskWrites is set). Closes ticket 12485.
16329 o Minor features (heartbeat):
16330 - On relays, report how many connections we negotiated using each
16331 version of the Tor link protocols. This information will let us
16332 know if removing support for very old versions of the Tor
16333 protocols is harming the network. Closes ticket 15212.
16335 o Minor features (hidden service):
16336 - Make Sybil attacks against hidden services harder by changing the
16337 minimum time required to get the HSDir flag from 25 hours up to 96
16338 hours. Addresses ticket 14149.
16339 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
16340 services to disable the anti-scanning feature introduced in
16341 0.2.6.2-alpha. With this option not set, a connection to an
16342 unlisted port closes the circuit. With this option set, only a
16343 RELAY_DONE cell is sent. Closes ticket 14084.
16344 - When re-enabling the network, don't try to build introduction
16345 circuits until we have successfully built a circuit. This makes
16346 hidden services come up faster when the network is re-enabled.
16347 Patch from "akwizgran". Closes ticket 13447.
16348 - When we fail to retrieve a hidden service descriptor, send the
16349 controller an "HS_DESC FAILED" controller event. Implements
16351 - New HiddenServiceDirGroupReadable option to cause hidden service
16352 directories and hostname files to be created group-readable. Patch
16353 from "anon", David Stainton, and "meejah". Closes ticket 11291.
16355 o Minor features (interface):
16356 - Implement "-f -" command-line option to read torrc configuration
16357 from standard input, if you don't want to store the torrc file in
16358 the file system. Implements feature 13865.
16360 o Minor features (logging):
16361 - Add a count of unique clients to the bridge heartbeat message.
16362 Resolves ticket 6852.
16363 - Suppress "router info incompatible with extra info" message when
16364 reading extrainfo documents from cache. (This message got loud
16365 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
16367 - Elevate hidden service authorized-client message from DEBUG to
16368 INFO. Closes ticket 14015.
16369 - On Unix-like systems, you can now use named pipes as the target of
16370 the Log option, and other options that try to append to files.
16371 Closes ticket 12061. Patch from "carlo von lynX".
16372 - When opening a log file at startup, send it every log message that
16373 we generated between startup and opening it. Previously, log
16374 messages that were generated before opening the log file were only
16375 logged to stdout. Closes ticket 6938.
16376 - Add a TruncateLogFile option to overwrite logs instead of
16377 appending to them. Closes ticket 5583.
16378 - Quiet some log messages in the heartbeat and at startup. Closes
16381 o Minor features (portability, Solaris):
16382 - Threads are no longer disabled by default on Solaris; we believe
16383 that the versions of Solaris with broken threading support are all
16384 obsolete by now. Resolves ticket 9495.
16386 o Minor features (relay):
16387 - Re-check our address after we detect a changed IP address from
16388 getsockname(). This ensures that the controller command "GETINFO
16389 address" will report the correct value. Resolves ticket 11582.
16391 - A new AccountingRule option lets Relays set whether they'd like
16392 AccountingMax to be applied separately to inbound and outbound
16393 traffic, or applied to the sum of inbound and outbound traffic.
16394 Resolves ticket 961. Patch by "chobe".
16395 - When identity keypair is generated for first time, log a
16396 congratulatory message that links to the new relay lifecycle
16397 document. Implements feature 10427.
16399 o Minor features (security, memory wiping):
16400 - Ensure we securely wipe keys from memory after
16401 crypto_digest_get_digest and init_curve25519_keypair_from_file
16402 have finished using them. Resolves ticket 13477.
16404 o Minor features (security, out-of-memory handling):
16405 - When handling an out-of-memory condition, allocate less memory for
16406 temporary data structures. Fixes issue 10115.
16407 - When handling an out-of-memory condition, consider more types of
16408 buffers, including those on directory connections, and zlib
16409 buffers. Resolves ticket 11792.
16411 o Minor features (stability):
16412 - Add assertions in our hash-table iteration code to check for
16413 corrupted values that could cause infinite loops. Closes
16416 o Minor features (systemd):
16417 - Various improvements and modernizations in systemd hardening
16418 support. Closes ticket 13805. Patch from Craig Andrews.
16419 - Where supported, when running with systemd, report successful
16420 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
16421 - When running with systemd, support systemd watchdog messages. Part
16422 of ticket 11016. Patch by Michael Scherer.
16424 o Minor features (testing networks):
16425 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
16426 the "Exit" flag regardless of their uptime, bandwidth, or exit
16427 policy. TestingTorNetwork must be set for this option to have any
16428 effect. Previously, authorities would take up to 35 minutes to
16429 give nodes the Exit flag in a test network. Partially implements
16431 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
16432 and the default on a testing network to 2 minutes. Drop the
16433 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
16434 keep the default on a testing network at 30 seconds. This reduces
16435 HS bootstrap time to around 25 seconds. Also, change the default
16436 time in test-network.sh to match. Closes ticket 13401. Patch
16438 - Create TestingDirAuthVoteHSDir to correspond to
16439 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
16440 HSDir flag for the listed relays regardless of uptime or ORPort
16441 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
16442 Partial implementation for ticket 14067. Patch by "teor".
16444 o Minor features (tor2web mode):
16445 - Introduce the config option Tor2webRendezvousPoints, which allows
16446 clients in Tor2webMode to select a specific Rendezvous Point to be
16447 used in HS circuits. This might allow better performance for
16448 Tor2Web nodes. Implements ticket 12844.
16450 o Minor features (transparent proxy):
16451 - Update the transparent proxy option checks to allow for both ipfw
16452 and pf on OS X. Closes ticket 14002.
16453 - Use the correct option when using IPv6 with transparent proxy
16454 support on Linux. Resolves 13808. Patch by Francisco Blas
16457 o Minor features (validation):
16458 - Check all date/time values passed to tor_timegm and
16459 parse_rfc1123_time for validity, taking leap years into account.
16460 Improves HTTP header validation. Implemented with bug 13476.
16461 - In correct_tm(), limit the range of values returned by system
16462 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
16463 This means we don't have to deal with negative or too large dates,
16464 even if a clock is wrong. Otherwise we might fail to read a file
16465 written by us which includes such a date. Fixes bug 13476.
16466 - Stop allowing invalid address patterns like "*/24" that contain
16467 both a wildcard address and a bit prefix length. This affects all
16468 our address-range parsing code. Fixes bug 7484; bugfix
16471 o Minor bugfixes (bridge clients):
16472 - When configured to use a bridge without an identity digest (not
16473 recommended), avoid launching an extra channel to it when
16474 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
16476 o Minor bugfixes (bridges):
16477 - When DisableNetwork is set, do not launch pluggable transport
16478 plugins, and if any are running, terminate them. Fixes bug 13213;
16479 bugfix on 0.2.3.6-alpha.
16481 o Minor bugfixes (C correctness):
16482 - Fix several instances of possible integer overflow/underflow/NaN.
16483 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
16485 - In circuit_build_times_calculate_timeout() in circuitstats.c,
16486 avoid dividing by zero in the pareto calculations. This traps
16487 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
16489 - Fix an integer overflow in format_time_interval(). Fixes bug
16490 13393; bugfix on 0.2.0.10-alpha.
16491 - Set the correct day of year value when the system's localtime(_r)
16492 or gmtime(_r) functions fail to set struct tm. Not externally
16493 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
16494 - Avoid unlikely signed integer overflow in tor_timegm on systems
16495 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
16497 o Minor bugfixes (certificate handling):
16498 - If an authority operator accidentally makes a signing certificate
16499 with a future publication time, do not discard its real signing
16500 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
16501 - Remove any old authority certificates that have been superseded
16502 for at least two days. Previously, we would keep superseded
16503 certificates until they expired, if they were published close in
16504 time to the certificate that superseded them. Fixes bug 11454;
16505 bugfix on 0.2.1.8-alpha.
16507 o Minor bugfixes (client):
16508 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
16509 BadExit flag are not considered worthy candidates. Fixes bug
16510 13066; bugfix on 0.1.2.3-alpha.
16511 - Use the consensus schedule for downloading consensuses, and not
16512 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
16513 - Handle unsupported or malformed SOCKS5 requests properly by
16514 responding with the appropriate error message before closing the
16515 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
16517 o Minor bugfixes (client, automapping):
16518 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
16519 no value follows the option. Fixes bug 14142; bugfix on
16520 0.2.4.7-alpha. Patch by "teor".
16521 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
16522 14195; bugfix on 0.1.0.1-rc.
16523 - Prevent changes to other options from removing the wildcard value
16524 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
16526 - Allow MapAddress and AutomapHostsOnResolve to work together when
16527 an address is mapped into another address type (like .onion) that
16528 must be automapped at resolve time. Fixes bug 7555; bugfix
16531 o Minor bugfixes (client, bridges):
16532 - When we are using bridges and we had a network connectivity
16533 problem, only retry connecting to our currently configured
16534 bridges, not all bridges we know about and remember using. Fixes
16535 bug 14216; bugfix on 0.2.2.17-alpha.
16537 o Minor bugfixes (client, DNS):
16538 - Report the correct cached DNS expiration times on SOCKS port or in
16539 DNS replies. Previously, we would report everything as "never
16540 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
16541 - Avoid a small memory leak when we find a cached answer for a
16542 reverse DNS lookup in a client-side DNS cache. (Remember, client-
16543 side DNS caching is off by default, and is not recommended.) Fixes
16544 bug 14259; bugfix on 0.2.0.1-alpha.
16546 o Minor bugfixes (client, IPv6):
16547 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
16548 flag is not set; and not because the NoIPv4Traffic flag was set.
16549 Previously we'd looked at the NoIPv4Traffic flag for both types of
16550 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
16552 o Minor bugfixes (client, microdescriptors):
16553 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
16554 computing which microdescriptors to download. This keeps us from
16555 erroneous download behavior if two microdescriptor digests ever
16556 have the same first 160 bits. Fixes part of bug 13399; bugfix
16558 - Reset a router's status if its microdescriptor digest changes,
16559 even if the first 160 bits remain the same. Fixes part of bug
16560 13399; bugfix on 0.2.3.1-alpha.
16562 o Minor bugfixes (client, torrc):
16563 - Stop modifying the value of our DirReqStatistics torrc option just
16564 because we're not a bridge or relay. This bug was causing Tor
16565 Browser users to write "DirReqStatistics 0" in their torrc files
16566 as if they had chosen to change the config. Fixes bug 4244; bugfix
16568 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
16569 that our options have changed every time we SIGHUP. Fixes bug
16570 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
16572 o Minor bugfixes (compilation):
16573 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
16575 - Silence clang warnings under --enable-expensive-hardening,
16576 including implicit truncation of 64 bit values to 32 bit, const
16577 char assignment to self, tautological compare, and additional
16578 parentheses around equality tests. Fixes bug 13577; bugfix
16580 - Fix a clang warning about checking whether an address in the
16581 middle of a structure is NULL. Fixes bug 14001; bugfix
16583 - The address of an array in the middle of a structure will always
16584 be non-NULL. clang recognises this and complains. Disable the
16585 tautologous and redundant check to silence this warning. Fixes bug
16586 14001; bugfix on 0.2.1.2-alpha.
16587 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
16588 Addresses ticket 14188.
16589 - Build without warnings with the stock OpenSSL srtp.h header, which
16590 has a duplicate declaration of SSL_get_selected_srtp_profile().
16591 Fixes bug 14220; this is OpenSSL's bug, not ours.
16592 - Do not compile any code related to Tor2Web mode when Tor2Web mode
16593 is not enabled at compile time. Previously, this code was included
16594 in a disabled state. See discussion on ticket 12844.
16595 - Allow our configure script to build correctly with autoconf 2.62
16596 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
16597 - Improve the error message from ./configure to make it clear that
16598 when asciidoc has not been found, the user will have to either add
16599 --disable-asciidoc argument or install asciidoc. Resolves
16602 o Minor bugfixes (controller):
16603 - Report "down" in response to the "GETINFO entry-guards" command
16604 when relays are down with an unreachable_since value. Previously,
16605 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
16606 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
16607 14116; bugfix on 0.2.2.9-alpha.
16609 o Minor bugfixes (controller):
16610 - Return an error when the second or later arguments of the
16611 "setevents" controller command are invalid events. Previously we
16612 would return success while silently skipping invalid events. Fixes
16613 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
16615 o Minor bugfixes (directory authority):
16616 - Allow directory authorities to fetch more data from one another if
16617 they find themselves missing lots of votes. Previously, they had
16618 been bumping against the 10 MB queued data limit. Fixes bug 14261;
16619 bugfix on 0.1.2.5-alpha.
16620 - Do not attempt to download extrainfo documents which we will be
16621 unable to validate with a matching server descriptor. Fixes bug
16622 13762; bugfix on 0.2.0.1-alpha.
16623 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
16624 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
16625 - Enlarge the buffer to read bwauth generated files to avoid an
16626 issue when parsing the file in dirserv_read_measured_bandwidths().
16627 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
16628 - When running as a v3 directory authority, advertise that you serve
16629 extra-info documents so that clients who want them can find them
16630 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
16632 o Minor bugfixes (directory system):
16633 - Always believe that v3 directory authorities serve extra-info
16634 documents, whether they advertise "caches-extra-info" or not.
16635 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
16636 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
16637 Previously, directories offering BRIDGE_DIRINFO and some other
16638 flag (i.e. microdescriptors or extrainfo) would be ignored when
16639 looking for bridges. Partially fixes bug 13163; bugfix
16642 o Minor bugfixes (file handling):
16643 - Stop failing when key files are zero-length. Instead, generate new
16644 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
16645 on all versions of Tor. Patch by "teor".
16646 - Stop generating a fresh .old RSA onion key file when the .old file
16647 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
16648 - Avoid overwriting .old key files with empty key files.
16649 - Skip loading zero-length extrainfo store, router store, stats,
16650 state, and key files.
16651 - Avoid crashing when trying to reload a torrc specified as a
16652 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
16655 o Minor bugfixes (hidden services):
16656 - Close the introduction circuit when we have no more usable intro
16657 points, instead of waiting for it to time out. This also ensures
16658 that no follow-up HS descriptor fetch is triggered when the
16659 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
16660 - When fetching a hidden service descriptor for a down service that
16661 was recently up, do not keep refetching until we try the same
16662 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
16663 - Correctly send a controller event when we find that a rendezvous
16664 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
16665 - Pre-check directory permissions for new hidden-services to avoid
16666 at least one case of "Bug: Acting on config options left us in a
16667 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
16668 - When fetching hidden service descriptors, we now check not only
16669 for whether we got the hidden service we had in mind, but also
16670 whether we got the particular descriptors we wanted. This prevents
16671 a class of inefficient but annoying DoS attacks by hidden service
16672 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
16675 o Minor bugfixes (Linux seccomp2 sandbox):
16676 - Make transparent proxy support work along with the seccomp2
16677 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
16678 by Francisco Blas Izquierdo Riera.
16679 - Fix a memory leak in tor-resolve when running with the sandbox
16680 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
16681 - Allow glibc fatal errors to be sent to stderr before Tor exits.
16682 Previously, glibc would try to write them to /dev/tty, and the
16683 sandbox would trap the call and make Tor exit prematurely. Fixes
16684 bug 14759; bugfix on 0.2.5.1-alpha.
16686 o Minor bugfixes (logging):
16687 - Avoid crashing when there are more log domains than entries in
16688 domain_list. Bugfix on 0.2.3.1-alpha.
16689 - Downgrade warnings about RSA signature failures to info log level.
16690 Emit a warning when an extra info document is found incompatible
16691 with a corresponding router descriptor. Fixes bug 9812; bugfix
16693 - Make connection_ap_handshake_attach_circuit() log the circuit ID
16694 correctly. Fixes bug 13701; bugfix on 0.0.6.
16696 o Minor bugfixes (networking):
16697 - Check for orconns and use connection_or_close_for_error() rather
16698 than connection_mark_for_close() directly in the getsockopt()
16699 failure case of connection_handle_write_impl(). Fixes bug 11302;
16700 bugfix on 0.2.4.4-alpha.
16702 o Minor bugfixes (parsing):
16703 - Stop accepting milliseconds (or other junk) at the end of
16704 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
16705 - Support two-number and three-number version numbers correctly, in
16706 case we change the Tor versioning system in the future. Fixes bug
16707 13661; bugfix on 0.0.8pre1.
16709 o Minor bugfixes (portability):
16710 - Fix the ioctl()-based network interface lookup code so that it
16711 will work on systems that have variable-length struct ifreq, for
16713 - Use the correct datatype in the SipHash-2-4 function to prevent
16714 compilers from assuming any sort of alignment. Fixes bug 15436;
16715 bugfix on 0.2.5.3-alpha.
16717 o Minor bugfixes (preventative security, C safety):
16718 - When reading a hexadecimal, base-32, or base-64 encoded value from
16719 a string, always overwrite the whole output buffer. This prevents
16720 some bugs where we would look at (but fortunately, not reveal)
16721 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
16723 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
16724 just the part that's used. This makes it harder for data leak bugs
16725 to occur in the event of other programming failures. Resolves
16728 o Minor bugfixes (relay):
16729 - When generating our family list, remove spaces from around the
16730 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
16731 - If our previous bandwidth estimate was 0 bytes, allow publishing a
16732 new relay descriptor immediately. Fixes bug 13000; bugfix
16735 o Minor bugfixes (shutdown):
16736 - When shutting down, always call event_del() on lingering read or
16737 write events before freeing them. Otherwise, we risk double-frees
16738 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
16741 o Minor bugfixes (small memory leaks):
16742 - Avoid leaking memory when using IPv6 virtual address mappings.
16743 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
16746 o Minor bugfixes (statistics):
16747 - Increase period over which bandwidth observations are aggregated
16748 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
16750 o Minor bugfixes (systemd support):
16751 - Run correctly under systemd with the RunAsDaemon option set. Fixes
16752 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
16753 - Inform the systemd supervisor about more changes in the Tor
16754 process status. Implements part of ticket 14141. Patch from
16757 o Minor bugfixes (testing networks):
16758 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
16759 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
16760 - Stop using the default authorities in networks which provide both
16761 AlternateDirAuthority and AlternateBridgeAuthority. Partially
16762 fixes bug 13163; bugfix on 0.2.0.13-alpha.
16764 o Minor bugfixes (testing networks, fast startup):
16765 - Allow Tor to build circuits using a consensus with no exits. If
16766 the consensus has no exits (typical of a bootstrapping test
16767 network), allow Tor to build circuits once enough descriptors have
16768 been downloaded. This assists in bootstrapping a testing Tor
16769 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
16771 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
16772 header to directory servers. This allows us to obtain consensuses
16773 promptly when the consensus interval is very short. This assists
16774 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
16775 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
16776 - Stop assuming that private addresses are local when checking
16777 reachability in a TestingTorNetwork. Instead, when testing, assume
16778 all OR connections are remote. (This is necessary due to many test
16779 scenarios running all relays on localhost.) This assists in
16780 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
16781 0.1.0.1-rc. Patch by "teor".
16782 - Avoid building exit circuits from a consensus with no exits. Now
16783 thanks to our fix for 13718, we accept a no-exit network as not
16784 wholly lost, but we need to remember not to try to build exit
16785 circuits on it. Closes ticket 13814; patch by "teor".
16786 - Stop requiring exits to have non-zero bandwithcapacity in a
16787 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
16788 ignore exit bandwidthcapacity. This assists in bootstrapping a
16789 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
16790 on 0.2.0.3-alpha. Patch by "teor".
16791 - Add "internal" to some bootstrap statuses when no exits are
16792 available. If the consensus does not contain Exits, Tor will only
16793 build internal circuits. In this case, relevant statuses will
16794 contain the word "internal" as indicated in the Tor control-
16795 spec.txt. When bootstrap completes, Tor will be ready to build
16796 internal circuits. If a future consensus contains Exits, exit
16797 circuits may become available. Fixes part of bug 13718; bugfix on
16798 0.2.4.10-alpha. Patch by "teor".
16799 - Decrease minimum consensus interval to 10 seconds when
16800 TestingTorNetwork is set, or 5 seconds for the first consensus.
16801 Fix assumptions throughout the code that assume larger intervals.
16802 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
16804 - Avoid excluding guards from path building in minimal test
16805 networks, when we're in a test network and excluding guards would
16806 exclude all relays. This typically occurs in incredibly small tor
16807 networks, and those using "TestingAuthVoteGuard *". Fixes part of
16808 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
16810 o Minor bugfixes (testing):
16811 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
16812 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
16813 - Stop spawn test failures due to a race condition between the
16814 SIGCHLD handler updating the process status, and the test reading
16815 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
16816 - Avoid passing an extra backslash when creating a temporary
16817 directory for running the unit tests on Windows. Fixes bug 12392;
16818 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
16820 o Minor bugfixes (TLS):
16821 - Check more thoroughly throughout the TLS code for possible
16822 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
16824 o Minor bugfixes (transparent proxy):
16825 - Use getsockname, not getsockopt, to retrieve the address for a
16826 TPROXY-redirected connection. Fixes bug 13796; bugfix
16829 o Minor bugfixes (windows):
16830 - Remove code to special-case handling of NTE_BAD_KEYSET when
16831 acquiring windows CryptoAPI context. This error can't actually
16832 occur for the parameters we're providing. Fixes bug 10816; bugfix
16835 o Minor bugfixes (zlib):
16836 - Avoid truncating a zlib stream when trying to finalize it with an
16837 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
16839 o Code simplification and refactoring:
16840 - Change the entry_is_live() function to take named bitfield
16841 elements instead of an unnamed list of booleans. Closes
16843 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
16844 Resolves ticket 12205.
16845 - Use calloc and reallocarray functions instead of multiply-
16846 then-malloc. This makes it less likely for us to fall victim to an
16847 integer overflow attack when allocating. Resolves ticket 12855.
16848 - Use the standard macro name SIZE_MAX, instead of our
16850 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
16851 functions which take them as arguments. Replace 0 with NO_DIRINFO
16852 in a function call for clarity. Seeks to prevent future issues
16854 - Avoid 4 null pointer errors under clang static analysis by using
16855 tor_assert() to prove that the pointers aren't null. Fixes
16857 - Rework the API of policies_parse_exit_policy() to use a bitmask to
16858 represent parsing options, instead of a confusing mess of
16859 booleans. Resolves ticket 8197.
16860 - Introduce a helper function to parse ExitPolicy in
16861 or_options_t structure.
16862 - Move fields related to isolating and configuring client ports into
16863 a shared structure. Previously, they were duplicated across
16864 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
16865 to copy them correctly had been the cause of at least one bug in
16866 the past. Closes ticket 8546.
16867 - Refactor the get_interface_addresses_raw() doom-function into
16868 multiple smaller and simpler subfunctions. Cover the resulting
16869 subfunctions with unit-tests. Fixes a significant portion of
16871 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
16872 only for version <= 0.2.2.24 which is now deprecated. Closes
16874 - Remove a test for a long-defunct broken version-one
16876 - Refactor main loop to extract the 'loop' part. This makes it
16877 easier to run Tor under Shadow. Closes ticket 15176.
16878 - Stop using can_complete_circuits as a global variable; access it
16879 with a function instead.
16880 - Avoid using operators directly as macro arguments: this lets us
16881 apply coccinelle transformations to our codebase more directly.
16882 Closes ticket 13172.
16883 - Combine the functions used to parse ClientTransportPlugin and
16884 ServerTransportPlugin into a single function. Closes ticket 6456.
16885 - Add inline functions and convenience macros for inspecting channel
16886 state. Refactor the code to use convenience macros instead of
16887 checking channel state directly. Fixes issue 7356.
16888 - Document all members of was_router_added_t and rename
16889 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
16890 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
16891 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
16892 constant instead of hardcoded value. Fixes issue 13840.
16893 - Refactor our generic strmap and digestmap types into a single
16894 implementation, so that we can add a new digest256map
16898 - Add a doc/TUNING document with tips for handling large numbers of
16899 TCP connections when running busy Tor relay. Update the warning
16900 message to point to this file when running out of sockets
16901 operating system is allowing to use simultaneously. Resolves
16903 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
16904 for writing the OpenBSD-specific tips. Resolves ticket 13702.
16905 - Make the tor-resolve documentation match its help string and its
16906 options. Resolves part of ticket 14325.
16907 - Log a more useful error message from tor-resolve when failing to
16908 look up a hidden service address. Resolves part of ticket 14325.
16909 - Document the bridge-authority-only 'networkstatus-bridges' file.
16910 Closes ticket 13713; patch from "tom".
16911 - Fix typo in PredictedPortsRelevanceTime option description in
16912 manpage. Resolves issue 13707.
16913 - Stop suggesting that users specify relays by nickname: it isn't a
16914 good idea. Also, properly cross-reference how to specify relays in
16915 all parts of manual documenting options that take a list of
16916 relays. Closes ticket 13381.
16917 - Clarify the HiddenServiceDir option description in manpage to make
16918 it clear that relative paths are taken with respect to the current
16919 working directory. Also clarify that this behavior is not
16920 guaranteed to remain indefinitely. Fixes issue 13913.
16922 o Distribution (systemd):
16923 - systemd unit file: only allow tor to write to /var/lib/tor and
16924 /var/log/tor. The rest of the filesystem is accessible for reading
16925 only. Patch by intrigeri; resolves ticket 12751.
16926 - systemd unit file: ensure that the process and all its children
16927 can never gain new privileges. Patch by intrigeri; resolves
16929 - systemd unit file: set up /var/run/tor as writable for the Tor
16930 service. Patch by intrigeri; resolves ticket 13196.
16932 o Downgraded warnings:
16933 - Don't warn when we've attempted to contact a relay using the wrong
16934 ntor onion key. Closes ticket 9635.
16937 - Remove some lingering dead code that once supported mempools.
16938 Mempools were disabled by default in 0.2.5, and removed entirely
16939 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
16942 o Removed features (directory authorities):
16943 - Remove code that prevented authorities from listing Tor relays
16944 affected by CVE-2011-2769 as guards. These relays are already
16945 rejected altogether due to the minimum version requirement of
16946 0.2.3.16-alpha. Closes ticket 13152.
16947 - The "AuthDirRejectUnlisted" option no longer has any effect, as
16948 the fingerprints file (approved-routers) has been deprecated.
16949 - Directory authorities do not support being Naming dirauths anymore.
16950 The "NamingAuthoritativeDir" config option is now obsolete.
16951 - Directory authorities do not support giving out the BadDirectory
16953 - Directory authorities no longer advertise or support consensus
16954 methods 1 through 12 inclusive. These consensus methods were
16955 obsolete and/or insecure: maintaining the ability to support them
16956 served no good purpose. Implements part of proposal 215; closes
16959 o Removed features:
16960 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
16961 longer silently accepted as an alias for "ExitNodes".
16962 - The --enable-mempool and --enable-buf-freelists options, which
16963 were originally created to work around bad malloc implementations,
16964 no longer exist. They were off-by-default in 0.2.5. Closes
16966 - We no longer remind the user about configuration options that have
16967 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
16968 - Remove our old, non-weighted bandwidth-based node selection code.
16969 Previously, we used it as a fallback when we couldn't perform
16970 weighted bandwidth-based node selection. But that would only
16971 happen in the cases where we had no consensus, or when we had a
16972 consensus generated by buggy or ancient directory authorities. In
16973 either case, it's better to use the more modern, better maintained
16974 algorithm, with reasonable defaults for the weights. Closes
16976 - Remove the --disable-curve25519 configure option. Relays and
16977 clients now are required to support curve25519 and the
16979 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
16980 used to be deprecated synonyms for "StrictNodes", are now marked
16981 obsolete. Resolves ticket 12226.
16982 - Clients don't understand the BadDirectory flag in the consensus
16983 anymore, and ignore it.
16985 o Removed platform support:
16986 - We no longer include special code to build on Windows CE; as far
16987 as we know, nobody has used Tor on Windows CE in a very long time.
16988 Closes ticket 11446.
16990 o Testing (test-network.sh):
16991 - Stop using "echo -n", as some shells' built-in echo doesn't
16992 support "-n". Instead, use "/bin/echo -n". Partially fixes
16994 - Stop an apparent test-network hang when used with make -j2. Fixes
16996 - Add a --delay option to test-network.sh, which configures the
16997 delay before the chutney network tests for data transmission.
16998 Partially implements ticket 13161.
17001 - Test that tor does not fail when key files are zero-length. Check
17002 that tor generates new keys, and overwrites the empty key files.
17003 - Test that tor generates new keys when keys are missing
17004 (existing behavior).
17005 - Test that tor does not overwrite key files that already contain
17006 data (existing behavior). Tests bug 13111. Patch by "teor".
17007 - New "make test-stem" target to run stem integration tests.
17008 Requires that the "STEM_SOURCE_DIR" environment variable be set.
17009 Closes ticket 14107.
17010 - Make the test_cmdline_args.py script work correctly on Windows.
17011 Patch from Gisle Vanem.
17012 - Move the slower unit tests into a new "./src/test/test-slow"
17013 binary that can be run independently of the other tests. Closes
17015 - New tests for many parts of channel, relay, and circuitmux
17016 functionality. Code by Andrea; part of 9262.
17017 - New tests for parse_transport_line(). Part of ticket 6456.
17018 - In the unit tests, use chgrp() to change the group of the unit
17019 test temporary directory to the current user, so that the sticky
17020 bit doesn't interfere with tests that check directory groups.
17022 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
17024 - Refactor the function that chooses guard nodes so that it can more
17025 easily be tested; write some tests for it.
17026 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
17027 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
17028 - Create unit tests for format_time_interval(). With bug 13393.
17029 - Add unit tests for tor_timegm signed overflow, tor_timegm and
17030 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
17031 tests (visible) fixes in bug 13476.
17032 - Add a "coverage-html" make target to generate HTML-visualized
17033 coverage results when building with --enable-coverage. (Requires
17034 lcov.) Patch from Kevin Murray.
17035 - Enable the backtrace handler (where supported) when running the
17037 - Revise all unit tests that used the legacy test_* macros to
17038 instead use the recommended tt_* macros. This patch was generated
17039 with coccinelle, to avoid manual errors. Closes ticket 13119.
17041 Changes in version 0.2.5.11 - 2015-03-17
17042 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
17044 It backports several bugfixes from the 0.2.6 branch, including a
17045 couple of medium-level security fixes for relays and exit nodes.
17046 It also updates the list of directory authorities.
17048 o Directory authority changes:
17049 - Remove turtles as a directory authority.
17050 - Add longclaw as a new (v3) directory authority. This implements
17051 ticket 13296. This keeps the directory authority count at 9.
17052 - The directory authority Faravahar has a new IP address. This
17053 closes ticket 14487.
17055 o Major bugfixes (crash, OSX, security):
17056 - Fix a remote denial-of-service opportunity caused by a bug in
17057 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
17060 o Major bugfixes (relay, stability, possible security):
17061 - Fix a bug that could lead to a relay crashing with an assertion
17062 failure if a buffer of exactly the wrong layout was passed to
17063 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
17064 0.2.0.10-alpha. Patch from 'cypherpunks'.
17065 - Do not assert if the 'data' pointer on a buffer is advanced to the
17066 very end of the buffer; log a BUG message instead. Only assert if
17067 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
17069 o Major bugfixes (exit node stability):
17070 - Fix an assertion failure that could occur under high DNS load.
17071 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
17072 diagnosed and fixed by "cypherpunks".
17074 o Major bugfixes (Linux seccomp2 sandbox):
17075 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
17076 crash during attempts to call wait4. Fixes bug 15088; bugfix on
17077 0.2.5.1-alpha. Patch from "sanic".
17079 o Minor features (controller):
17080 - New "GETINFO bw-event-cache" to get information about recent
17081 bandwidth events. Closes ticket 14128. Useful for controllers to
17082 get recent bandwidth history after the fix for ticket 13988.
17084 o Minor features (geoip):
17085 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
17086 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
17089 o Minor bugfixes (client, automapping):
17090 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
17091 no value follows the option. Fixes bug 14142; bugfix on
17092 0.2.4.7-alpha. Patch by "teor".
17093 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
17094 14195; bugfix on 0.1.0.1-rc.
17096 o Minor bugfixes (compilation):
17097 - Build without warnings with the stock OpenSSL srtp.h header, which
17098 has a duplicate declaration of SSL_get_selected_srtp_profile().
17099 Fixes bug 14220; this is OpenSSL's bug, not ours.
17101 o Minor bugfixes (directory authority):
17102 - Allow directory authorities to fetch more data from one another if
17103 they find themselves missing lots of votes. Previously, they had
17104 been bumping against the 10 MB queued data limit. Fixes bug 14261;
17105 bugfix on 0.1.2.5-alpha.
17106 - Enlarge the buffer to read bwauth generated files to avoid an
17107 issue when parsing the file in dirserv_read_measured_bandwidths().
17108 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
17110 o Minor bugfixes (statistics):
17111 - Increase period over which bandwidth observations are aggregated
17112 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
17114 o Minor bugfixes (preventative security, C safety):
17115 - When reading a hexadecimal, base-32, or base-64 encoded value from
17116 a string, always overwrite the whole output buffer. This prevents
17117 some bugs where we would look at (but fortunately, not reveal)
17118 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
17122 Changes in version 0.2.4.26 - 2015-03-17
17123 Tor 0.2.4.26 includes an updated list of directory authorities. It
17124 also backports a couple of stability and security bugfixes from 0.2.5
17127 o Directory authority changes:
17128 - Remove turtles as a directory authority.
17129 - Add longclaw as a new (v3) directory authority. This implements
17130 ticket 13296. This keeps the directory authority count at 9.
17131 - The directory authority Faravahar has a new IP address. This
17132 closes ticket 14487.
17134 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
17135 - Fix an assertion failure that could occur under high DNS load.
17136 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
17137 diagnosed and fixed by "cypherpunks".
17139 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
17140 - Fix a bug that could lead to a relay crashing with an assertion
17141 failure if a buffer of exactly the wrong layout was passed to
17142 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
17143 0.2.0.10-alpha. Patch from 'cypherpunks'.
17144 - Do not assert if the 'data' pointer on a buffer is advanced to the
17145 very end of the buffer; log a BUG message instead. Only assert if
17146 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
17148 o Minor features (geoip):
17149 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
17150 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
17153 Changes in version 0.2.5.10 - 2014-10-24
17154 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
17156 It adds several new security features, including improved
17157 denial-of-service resistance for relays, new compiler hardening
17158 options, and a system-call sandbox for hardened installations on Linux
17159 (requires seccomp2). The controller protocol has several new features,
17160 resolving IPv6 addresses should work better than before, and relays
17161 should be a little more CPU-efficient. We've added support for more
17162 OpenBSD and FreeBSD transparent proxy types. We've improved the build
17163 system and testing infrastructure to allow unit testing of more parts
17164 of the Tor codebase. Finally, we've addressed several nagging pluggable
17165 transport usability issues, and included numerous other small bugfixes
17166 and features mentioned below.
17168 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
17169 have accumulated many known flaws; everyone should upgrade.
17171 o Major features (security):
17172 - The ntor handshake is now on-by-default, no matter what the
17173 directory authorities recommend. Implements ticket 8561.
17174 - Make the "tor-gencert" tool used by directory authority operators
17175 create 2048-bit signing keys by default (rather than 1024-bit, since
17176 1024-bit is uncomfortably small these days). Addresses ticket 10324.
17177 - Warn about attempts to run hidden services and relays in the same
17178 process: that's probably not a good idea. Closes ticket 12908.
17179 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
17180 today support TLS 1.0 or later, so we can safely turn off support
17181 for this old (and insecure) protocol. Fixes bug 13426.
17183 o Major features (relay security, DoS-resistance):
17184 - When deciding whether we have run out of memory and we need to
17185 close circuits, also consider memory allocated in buffers for
17186 streams attached to each circuit.
17188 This change, which extends an anti-DoS feature introduced in
17189 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
17190 better resist more memory-based DoS attacks than before. Since the
17191 MaxMemInCellQueues option now applies to all queues, it is renamed
17192 to MaxMemInQueues. This feature fixes bug 10169.
17193 - Avoid hash-flooding denial-of-service attacks by using the secure
17194 SipHash-2-4 hash function for our hashtables. Without this
17195 feature, an attacker could degrade performance of a targeted
17196 client or server by flooding their data structures with a large
17197 number of entries to be stored at the same hash table position,
17198 thereby slowing down the Tor instance. With this feature, hash
17199 table positions are derived from a randomized cryptographic key,
17200 and an attacker cannot predict which entries will collide. Closes
17202 - If you don't specify MaxMemInQueues yourself, Tor now tries to
17203 pick a good value based on your total system memory. Previously,
17204 the default was always 8 GB. You can still override the default by
17205 setting MaxMemInQueues yourself. Resolves ticket 11396.
17207 o Major features (bridges and pluggable transports):
17208 - Add support for passing arguments to managed pluggable transport
17209 proxies. Implements ticket 3594.
17210 - Bridges now track GeoIP information and the number of their users
17211 even when pluggable transports are in use, and report usage
17212 statistics in their extra-info descriptors. Resolves tickets 4773
17214 - Don't launch pluggable transport proxies if we don't have any
17215 bridges configured that would use them. Now we can list many
17216 pluggable transports, and Tor will dynamically start one when it
17217 hears a bridge address that needs it. Resolves ticket 5018.
17218 - The bridge directory authority now assigns status flags (Stable,
17219 Guard, etc) to bridges based on thresholds calculated over all
17220 Running bridges. Now bridgedb can finally make use of its features
17221 to e.g. include at least one Stable bridge in its answers. Fixes
17224 o Major features (controller):
17225 - Extend ORCONN controller event to include an "ID" parameter,
17226 and add four new controller event types CONN_BW, CIRC_BW,
17227 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
17228 The new events are emitted in private Tor networks only, with the
17229 goal of being able to better track performance and load during
17230 full-network simulations. Implements proposal 218 and ticket 7359.
17232 o Major features (relay performance):
17233 - Speed up server-side lookups of rendezvous and introduction point
17234 circuits by using hashtables instead of linear searches. These
17235 functions previously accounted between 3 and 7% of CPU usage on
17236 some busy relays. Resolves ticket 9841.
17237 - Avoid wasting CPU when extending a circuit over a channel that is
17238 nearly out of circuit IDs. Previously, we would do a linear scan
17239 over possible circuit IDs before finding one or deciding that we
17240 had exhausted our possibilities. Now, we try at most 64 random
17241 circuit IDs before deciding that we probably won't succeed. Fixes
17242 a possible root cause of ticket 11553.
17244 o Major features (seccomp2 sandbox, Linux only):
17245 - Use the seccomp2 syscall filtering facility on Linux to limit
17246 which system calls Tor can invoke. This is an experimental,
17247 Linux-only feature to provide defense-in-depth against unknown
17248 attacks. To try turning it on, set "Sandbox 1" in your torrc
17249 file. Please be ready to report bugs. We hope to add support
17250 for better sandboxing in the future, including more fine-grained
17251 filters, better division of responsibility, and support for more
17252 platforms. This work has been done by Cristian-Matei Toader for
17253 Google Summer of Code. Resolves tickets 11351 and 11465.
17255 o Major features (testing networks):
17256 - Make testing Tor networks bootstrap better: lower directory fetch
17257 retry schedules and maximum interval without directory requests,
17258 and raise maximum download tries. Implements ticket 6752.
17259 - Add make target 'test-network' to run tests on a Chutney network.
17260 Implements ticket 8530.
17262 o Major features (other):
17263 - On some platforms (currently: recent OSX versions, glibc-based
17264 platforms that support the ELF format, and a few other
17265 Unix-like operating systems), Tor can now dump stack traces
17266 when a crash occurs or an assertion fails. By default, traces
17267 are dumped to stderr (if possible) and to any logs that are
17268 reporting errors. Implements ticket 9299.
17270 o Deprecated versions:
17271 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
17272 attention for some while.
17274 o Major bugfixes (security, directory authorities):
17275 - Directory authorities now include a digest of each relay's
17276 identity key as a part of its microdescriptor.
17278 This is a workaround for bug 11743 (reported by "cypherpunks"),
17279 where Tor clients do not support receiving multiple
17280 microdescriptors with the same SHA256 digest in the same
17281 consensus. When clients receive a consensus like this, they only
17282 use one of the relays. Without this fix, a hostile relay could
17283 selectively disable some client use of target relays by
17284 constructing a router descriptor with a different identity and the
17285 same microdescriptor parameters and getting the authorities to
17286 list it in a microdescriptor consensus. This fix prevents an
17287 attacker from causing a microdescriptor collision, because the
17288 router's identity is not forgeable.
17290 o Major bugfixes (openssl bug workaround):
17291 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
17292 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
17293 bug 13471. This is a workaround for an OpenSSL bug.
17295 o Major bugfixes (client):
17296 - Perform circuit cleanup operations even when circuit
17297 construction operations are disabled (because the network is
17298 disabled, or because there isn't enough directory information).
17299 Previously, when we were not building predictive circuits, we
17300 were not closing expired circuits either. Fixes bug 8387; bugfix on
17301 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
17302 became more strict about when we have "enough directory information
17303 to build circuits".
17305 o Major bugfixes (client, pluggable transports):
17306 - When managing pluggable transports, use OS notification facilities
17307 to learn if they have crashed, and don't attempt to kill any
17308 process that has already exited. Fixes bug 8746; bugfix
17311 o Major bugfixes (relay denial of service):
17312 - Instead of writing destroy cells directly to outgoing connection
17313 buffers, queue them and intersperse them with other outgoing cells.
17314 This can prevent a set of resource starvation conditions where too
17315 many pending destroy cells prevent data cells from actually getting
17316 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
17317 bugfix on 0.2.0.1-alpha.
17319 o Major bugfixes (relay):
17320 - Avoid queuing or sending destroy cells for circuit ID zero when we
17321 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
17322 Found and fixed by "cypherpunks".
17323 - Fix ORPort reachability detection on relays running behind a
17324 proxy, by correctly updating the "local" mark on the controlling
17325 channel when changing the address of an or_connection_t after the
17326 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
17327 - Use a direct dirport connection when uploading non-anonymous
17328 descriptors to the directory authorities. Previously, relays would
17329 incorrectly use tunnel connections under a fairly wide variety of
17330 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
17331 - When a circuit accidentally has the same circuit ID for its
17332 forward and reverse direction, correctly detect the direction of
17333 cells using that circuit. Previously, this bug made roughly one
17334 circuit in a million non-functional. Fixes bug 12195; this is a
17335 bugfix on every version of Tor.
17337 o Minor features (security):
17338 - New --enable-expensive-hardening option to enable security
17339 hardening options that consume nontrivial amounts of CPU and
17340 memory. Right now, this includes AddressSanitizer and UbSan, which
17341 are supported in newer versions of GCC and Clang. Closes ticket
17343 - Authorities now assign the Guard flag to the fastest 25% of the
17344 network (it used to be the fastest 50%). Also raise the consensus
17345 weight that guarantees the Guard flag from 250 to 2000. For the
17346 current network, this results in about 1100 guards, down from 2500.
17347 This step paves the way for moving the number of entry guards
17348 down to 1 (proposal 236) while still providing reasonable expected
17349 performance for most users. Implements ticket 12690.
17351 o Minor features (security, memory management):
17352 - Memory allocation tricks (mempools and buffer freelists) are now
17353 disabled by default. You can turn them back on with
17354 --enable-mempools and --enable-buf-freelists respectively. We're
17355 disabling these features because malloc performance is good enough
17356 on most platforms, and a similar feature in OpenSSL exacerbated
17357 exploitation of the Heartbleed attack. Resolves ticket 11476.
17359 o Minor features (bridge client):
17360 - Report a more useful failure message when we can't connect to a
17361 bridge because we don't have the right pluggable transport
17362 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
17364 o Minor features (bridge):
17365 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
17366 cookie file for the ExtORPort g+r by default.
17368 o Minor features (bridges, pluggable transports):
17369 - Bridges now write the SHA1 digest of their identity key
17370 fingerprint (that is, a hash of a hash of their public key) to
17371 notice-level logs, and to a new hashed-fingerprint file. This
17372 information will help bridge operators look up their bridge in
17373 Globe and similar tools. Resolves ticket 10884.
17374 - Improve the message that Tor displays when running as a bridge
17375 using pluggable transports without an Extended ORPort listener.
17376 Also, log the message in the log file too. Resolves ticket 11043.
17377 - Add threshold cutoffs to the networkstatus document created by
17378 the Bridge Authority. Fixes bug 1117.
17379 - On Windows, spawn background processes using the CREATE_NO_WINDOW
17380 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
17381 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
17382 Vidalia set this option for us.) Implements ticket 10297.
17384 o Minor features (build):
17385 - The configure script has a --disable-seccomp option to turn off
17386 support for libseccomp on systems that have it, in case it (or
17387 Tor's use of it) is broken. Resolves ticket 11628.
17388 - Assume that a user using ./configure --host wants to cross-compile,
17389 and give an error if we cannot find a properly named
17390 tool-chain. Add a --disable-tool-name-check option to proceed
17391 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
17392 - If we run ./configure and the compiler recognizes -fstack-protector
17393 but the linker rejects it, warn the user about a potentially missing
17394 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
17395 - Add support for `--library-versions` flag. Implements ticket 6384.
17396 - Return the "unexpected sendme" warnings to a warn severity, but make
17397 them rate limited, to help diagnose ticket 8093.
17398 - Detect a missing asciidoc, and warn the user about it, during
17399 configure rather than at build time. Fixes issue 6506. Patch from
17402 o Minor features (client):
17403 - Add a new option, PredictedPortsRelevanceTime, to control how long
17404 after having received a request to connect to a given port Tor
17405 will try to keep circuits ready in anticipation of future requests
17406 for that port. Patch from "unixninja92"; implements ticket 9176.
17408 o Minor features (config options and command line):
17409 - Add an --allow-missing-torrc commandline option that tells Tor to
17410 run even if the configuration file specified by -f is not available.
17411 Implements ticket 10060.
17412 - Add support for the TPROXY transparent proxying facility on Linux.
17413 See documentation for the new TransProxyType option for more
17414 details. Implementation by "thomo". Closes ticket 10582.
17416 o Minor features (config options):
17417 - Config (torrc) lines now handle fingerprints which are missing
17418 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
17419 - Support a --dump-config option to print some or all of the
17420 configured options. Mainly useful for debugging the command-line
17421 option parsing code. Helps resolve ticket 4647.
17422 - Raise awareness of safer logging: notify user of potentially
17423 unsafe config options, like logging more verbosely than severity
17424 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
17425 - Add a new configuration option TestingV3AuthVotingStartOffset
17426 that bootstraps a network faster by changing the timing for
17427 consensus votes. Addresses ticket 8532.
17428 - Add a new torrc option "ServerTransportOptions" that allows
17429 bridge operators to pass configuration parameters to their
17430 pluggable transports. Resolves ticket 8929.
17431 - The config (torrc) file now accepts bandwidth and space limits in
17432 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
17433 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
17436 o Minor features (controller):
17437 - Make the entire exit policy available from the control port via
17438 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
17440 - Because of the fix for ticket 11396, the real limit for memory
17441 usage may no longer match the configured MaxMemInQueues value. The
17442 real limit is now exposed via GETINFO limits/max-mem-in-queues.
17443 - Add a new "HS_DESC" controller event that reports activities
17444 related to hidden service descriptors. Resolves ticket 8510.
17445 - New "DROPGUARDS" controller command to forget all current entry
17446 guards. Not recommended for ordinary use, since replacing guards
17447 too frequently makes several attacks easier. Resolves ticket 9934;
17449 - Implement the TRANSPORT_LAUNCHED control port event that
17450 notifies controllers about new launched pluggable
17451 transports. Resolves ticket 5609.
17453 o Minor features (diagnostic):
17454 - When logging a warning because of bug 7164, additionally check the
17455 hash table for consistency (as proposed on ticket 11737). This may
17456 help diagnose bug 7164.
17457 - When we log a heartbeat, log how many one-hop circuits we have
17458 that are at least 30 minutes old, and log status information about
17459 a few of them. This is an attempt to track down bug 8387.
17460 - When encountering an unexpected CR while writing text to a file on
17461 Windows, log the name of the file. Should help diagnosing
17463 - Give more specific warnings when a client notices that an onion
17464 handshake has failed. Fixes ticket 9635.
17465 - Add significant new logging code to attempt to diagnose bug 12184,
17466 where relays seem to run out of available circuit IDs.
17467 - Improve the diagnostic log message for bug 8387 even further to
17468 try to improve our odds of figuring out why one-hop directory
17469 circuits sometimes do not get closed.
17470 - Add more log messages to diagnose bug 7164, which causes
17471 intermittent "microdesc_free() called but md was still referenced"
17472 warnings. We now include more information, to figure out why we
17473 might be cleaning a microdescriptor for being too old if it's
17474 still referenced by a live node_t object.
17475 - Log current accounting state (bytes sent and received + remaining
17476 time for the current accounting period) in the relay's heartbeat
17477 message. Implements ticket 5526; patch from Peter Retzlaff.
17479 o Minor features (geoip):
17480 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
17483 o Minor features (interface):
17484 - Generate a warning if any ports are listed in the SocksPolicy,
17485 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
17486 AuthDirBadExit options. (These options only support address
17487 ranges.) Fixes part of ticket 11108.
17489 o Minor features (kernel API usage):
17490 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
17491 sockets in a single system call. Implements ticket 5129.
17493 o Minor features (log messages):
17494 - When ServerTransportPlugin is set on a bridge, Tor can write more
17495 useful statistics about bridge use in its extrainfo descriptors,
17496 but only if the Extended ORPort ("ExtORPort") is set too. Add a
17497 log message to inform the user in this case. Resolves ticket 9651.
17498 - When receiving a new controller connection, log the origin address.
17499 Resolves ticket 9698; patch from "sigpipe".
17500 - When logging OpenSSL engine status at startup, log the status of
17501 more engines. Fixes ticket 10043; patch from Joshua Datko.
17503 o Minor features (log verbosity):
17504 - Demote the message that we give when a flushing connection times
17505 out for too long from NOTICE to INFO. It was usually meaningless.
17506 Resolves ticket 5286.
17507 - Don't log so many notice-level bootstrapping messages at startup
17508 about downloading descriptors. Previously, we'd log a notice
17509 whenever we learned about more routers. Now, we only log a notice
17510 at every 5% of progress. Fixes bug 9963.
17511 - Warn less verbosely when receiving a malformed
17512 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
17514 o Minor features (performance):
17515 - If we're using the pure-C 32-bit curve25519_donna implementation
17516 of curve25519, build it with the -fomit-frame-pointer option to
17517 make it go faster on register-starved hosts. This improves our
17518 handshake performance by about 6% on i386 hosts without nacl.
17519 Closes ticket 8109.
17521 o Minor features (relay):
17522 - If a circuit timed out for at least 3 minutes, check if we have a
17523 new external IP address, and publish a new descriptor with the new
17524 IP address if it changed. Resolves ticket 2454.
17526 o Minor features (testing):
17527 - If Python is installed, "make check" now runs extra tests beyond
17528 the unit test scripts.
17529 - When bootstrapping a test network, sometimes very few relays get
17530 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
17531 specify a set of relays which should be voted Guard regardless of
17532 their uptime or bandwidth. Addresses ticket 9206.
17534 o Minor features (transparent proxy, *BSD):
17535 - Support FreeBSD's ipfw firewall interface for TransPort ports on
17536 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
17537 10267; patch from "yurivict".
17538 - Support OpenBSD's divert-to rules with the pf firewall for
17539 transparent proxy ports. To enable it, set "TransProxyType
17540 pf-divert". This allows Tor to run a TransPort transparent proxy
17541 port on OpenBSD 4.4 or later without root privileges. See the
17542 pf.conf(5) manual page for information on configuring pf to use
17543 divert-to rules. Closes ticket 10896; patch from Dana Koch.
17545 o Minor bugfixes (bridge client):
17546 - Stop accepting bridge lines containing hostnames. Doing so would
17547 cause clients to perform DNS requests on the hostnames, which was
17548 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
17550 o Minor bugfixes (bridges):
17551 - Avoid potential crashes or bad behavior when launching a
17552 server-side managed proxy with ORPort or ExtORPort temporarily
17553 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
17554 - Fix a bug where the first connection works to a bridge that uses a
17555 pluggable transport with client-side parameters, but we don't send
17556 the client-side parameters on subsequent connections. (We don't
17557 use any pluggable transports with client-side parameters yet,
17558 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
17559 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
17561 o Minor bugfixes (build, auxiliary programs):
17562 - Stop preprocessing the "torify" script with autoconf, since
17563 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
17565 - The tor-fw-helper program now follows the standard convention and
17566 exits with status code "0" on success. Fixes bug 9030; bugfix on
17567 0.2.3.1-alpha. Patch by Arlo Breault.
17568 - Corrected ./configure advice for what openssl dev package you should
17569 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
17571 o Minor bugfixes (client):
17572 - Avoid "Tried to open a socket with DisableNetwork set" warnings
17573 when starting a client with bridges configured and DisableNetwork
17574 set. (Tor launcher starts Tor with DisableNetwork set the first
17575 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
17576 - Improve the log message when we can't connect to a hidden service
17577 because all of the hidden service directory nodes hosting its
17578 descriptor are excluded. Improves on our fix for bug 10722, which
17579 was a bugfix on 0.2.0.10-alpha.
17580 - Raise a control port warning when we fail to connect to all of
17581 our bridges. Previously, we didn't inform the controller, and
17582 the bootstrap process would stall. Fixes bug 11069; bugfix on
17584 - Exit immediately when a process-owning controller exits.
17585 Previously, tor relays would wait for a little while after their
17586 controller exited, as if they had gotten an INT signal -- but this
17587 was problematic, since there was no feedback for the user. To do a
17588 clean shutdown, controllers should send an INT signal and give Tor
17589 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
17590 - Stop attempting to connect to bridges before our pluggable
17591 transports are configured (harmless but resulted in some erroneous
17592 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
17593 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
17594 generating incorrect SOCKS5 responses, and confusing client
17595 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
17597 o Minor bugfixes (client, DNSPort):
17598 - When using DNSPort, try to respond to AAAA requests with AAAA
17599 answers. Previously, we hadn't looked at the request type when
17600 deciding which answer type to prefer. Fixes bug 10468; bugfix on
17602 - When receiving a DNS query for an unsupported record type, reply
17603 with no answer rather than with a NOTIMPL error. This behavior
17604 isn't correct either, but it will break fewer client programs, we
17605 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
17608 o Minor bugfixes (client, logging during bootstrap):
17609 - Only report the first fatal bootstrap error on a given OR
17610 connection. This stops us from telling the controller bogus error
17611 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
17612 - Avoid generating spurious warnings when starting with
17613 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
17616 o Minor bugfixes (closing OR connections):
17617 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
17618 check if it's an or_connection_t and correctly call
17619 connection_or_close_for_error() rather than
17620 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
17622 - When closing all connections on setting DisableNetwork to 1, use
17623 connection_or_close_normally() rather than closing OR connections
17624 out from under the channel layer. Fixes bug 11306; bugfix on
17627 o Minor bugfixes (code correctness):
17628 - Previously we used two temporary files when writing descriptors to
17629 disk; now we only use one. Fixes bug 1376.
17630 - Remove an erroneous (but impossible and thus harmless) pointer
17631 comparison that would have allowed compilers to skip a bounds
17632 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
17633 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
17634 - Fix an always-true assertion in pluggable transports code so it
17635 actually checks what it was trying to check. Fixes bug 10046;
17636 bugfix on 0.2.3.9-alpha. Found by "dcb".
17638 o Minor bugfixes (command line):
17639 - Use a single command-line parser for parsing torrc options on the
17640 command line and for finding special command-line options to avoid
17641 inconsistent behavior for torrc option arguments that have the same
17642 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
17644 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
17645 9573; bugfix on 0.0.9pre5.
17647 o Minor bugfixes (compilation):
17648 - Compile correctly with builds and forks of OpenSSL (such as
17649 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
17650 0.2.1.1-alpha. Patch from "dhill".
17651 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
17652 turned off (that is, without support for v2 link handshakes). Fixes
17653 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
17654 - In routerlist_assert_ok(), don't take the address of a
17655 routerinfo's cache_info member unless that routerinfo is non-NULL.
17656 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
17657 - Fix a large number of false positive warnings from the clang
17658 analyzer static analysis tool. This should make real warnings
17659 easier for clang analyzer to find. Patch from "teor". Closes
17661 - Resolve GCC complaints on OpenBSD about discarding constness in
17662 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
17663 on 0.1.1.23. Patch from Dana Koch.
17664 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
17665 treatment of long and time_t as comparable types. Fixes part of
17666 bug 11633. Patch from Dana Koch.
17667 - When deciding whether to build the 64-bit curve25519
17668 implementation, detect platforms where we can compile 128-bit
17669 arithmetic but cannot link it. Fixes bug 11729; bugfix on
17670 0.2.4.8-alpha. Patch from "conradev".
17671 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
17672 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
17673 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
17675 - Build and run correctly on systems like OpenBSD-current that have
17676 patched OpenSSL to remove get_cipher_by_char and/or its
17677 implementations. Fixes issue 13325.
17679 o Minor bugfixes (controller and command-line):
17680 - If changing a config option via "setconf" fails in a recoverable
17681 way, we used to nonetheless write our new control ports to the
17682 file described by the "ControlPortWriteToFile" option. Now we only
17683 write out that file if we successfully switch to the new config
17684 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
17686 o Minor bugfixes (directory server):
17687 - No longer accept malformed http headers when parsing urls from
17688 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
17689 bugfix on 0.0.6pre1.
17690 - When sending a compressed set of descriptors or microdescriptors,
17691 make sure to finalize the zlib stream. Previously, we would write
17692 all the compressed data, but if the last descriptor we wanted to
17693 send was missing or too old, we would not mark the stream as
17694 finished. This caused problems for decompression tools. Fixes bug
17695 11648; bugfix on 0.1.1.23.
17697 o Minor bugfixes (hidden service):
17698 - Only retry attempts to connect to a chosen rendezvous point 8
17699 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
17701 o Minor bugfixes (interface):
17702 - Reject relative control socket paths and emit a warning. Previously,
17703 single-component control socket paths would be rejected, but Tor
17704 would not log why it could not validate the config. Fixes bug 9258;
17705 bugfix on 0.2.3.16-alpha.
17707 o Minor bugfixes (log messages):
17708 - Fix a bug where clients using bridges would report themselves
17709 as 50% bootstrapped even without a live consensus document.
17710 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
17711 - Suppress a warning where, if there's only one directory authority
17712 in the network, we would complain that votes and signatures cannot
17713 be uploaded to other directory authorities. Fixes bug 10842;
17714 bugfix on 0.2.2.26-beta.
17715 - Report bootstrapping progress correctly when we're downloading
17716 microdescriptors. We had updated our "do we have enough microdescs
17717 to begin building circuits?" logic most recently in 0.2.4.10-alpha
17718 (see bug 5956), but we left the bootstrap status event logic at
17719 "how far through getting 1/4 of them are we?" Fixes bug 9958;
17720 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
17722 o Minor bugfixes (logging):
17723 - Downgrade "Unexpected onionskin length after decryption" warning
17724 to a protocol-warn, since there's nothing relay operators can do
17725 about a client that sends them a malformed create cell. Resolves
17726 bug 12996; bugfix on 0.0.6rc1.
17727 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
17728 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
17729 - When logging information about an EXTEND2 or EXTENDED2 cell, log
17730 their names correctly. Fixes part of bug 12700; bugfix
17732 - When logging information about a relay cell whose command we don't
17733 recognize, log its command as an integer. Fixes part of bug 12700;
17734 bugfix on 0.2.1.10-alpha.
17735 - Escape all strings from the directory connection before logging
17736 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
17737 - Squelch a spurious LD_BUG message "No origin circuit for
17738 successful SOCKS stream" in certain hidden service failure cases;
17740 - Downgrade the severity of the 'unexpected sendme cell from client'
17741 from 'warn' to 'protocol warning'. Closes ticket 8093.
17743 o Minor bugfixes (misc code correctness):
17744 - In munge_extrainfo_into_routerinfo(), check the return value of
17745 memchr(). This would have been a serious issue if we ever passed
17746 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
17748 - On the chance that somebody manages to build Tor on a
17749 platform where time_t is unsigned, correct the way that
17750 microdesc_add_to_cache() handles negative time arguments.
17751 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
17752 - Fix various instances of undefined behavior in channeltls.c,
17753 tor_memmem(), and eventdns.c that would cause us to construct
17754 pointers to memory outside an allocated object. (These invalid
17755 pointers were not accessed, but C does not even allow them to
17756 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
17757 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
17758 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
17759 fix some miscellaneous errors in our tests and codebase. Fixes bug
17760 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
17761 - Always check return values for unlink, munmap, UnmapViewOfFile;
17762 check strftime return values more often. In some cases all we can
17763 do is report a warning, but this may help prevent deeper bugs from
17764 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
17766 - Fix numerous warnings from the clang "scan-build" static analyzer.
17767 Some of these are programming style issues; some of them are false
17768 positives that indicated awkward code; some are undefined behavior
17769 cases related to constructing (but not using) invalid pointers;
17770 some are assumptions about API behavior; some are (harmlessly)
17771 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
17772 correct; and one or two are genuine bugs that weren't reachable
17773 from the rest of the program. Fixes bug 8793; bugfixes on many,
17776 o Minor bugfixes (node selection):
17777 - If ExcludeNodes is set, consider non-excluded hidden service
17778 directory servers before excluded ones. Do not consider excluded
17779 hidden service directory servers at all if StrictNodes is
17780 set. (Previously, we would sometimes decide to connect to those
17781 servers, and then realize before we initiated a connection that
17782 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
17783 Reported by "mr-4".
17784 - If we set the ExitNodes option but it doesn't include any nodes
17785 that have the Exit flag, we would choose not to bootstrap. Now we
17786 bootstrap so long as ExitNodes includes nodes which can exit to
17787 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
17789 o Minor bugfixes (performance):
17790 - Avoid a bug where every successful connection made us recompute
17791 the flag telling us whether we have sufficient information to
17792 build circuits. Previously, we would forget our cached value
17793 whenever we successfully opened a channel (or marked a router as
17794 running or not running for any other reason), regardless of
17795 whether we had previously believed the router to be running. This
17796 forced us to run an expensive update operation far too often.
17797 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
17798 - Avoid using tor_memeq() for checking relay cell integrity. This
17799 removes a possible performance bottleneck. Fixes part of bug
17800 12169; bugfix on 0.2.1.31.
17802 o Minor bugfixes (platform-specific):
17803 - When dumping a malformed directory object to disk, save it in
17804 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
17806 - Don't report failures from make_socket_reuseable() on incoming
17807 sockets on OSX: this can happen when incoming connections close
17808 early. Fixes bug 10081.
17810 o Minor bugfixes (pluggable transports):
17811 - Avoid another 60-second delay when starting Tor in a pluggable-
17812 transport-using configuration when we already have cached
17813 descriptors for our bridges. Fixes bug 11965; bugfix
17816 o Minor bugfixes (protocol correctness):
17817 - When receiving a VERSIONS cell with an odd number of bytes, close
17818 the connection immediately since the cell is malformed. Fixes bug
17819 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
17822 o Minor bugfixes (relay, other):
17823 - We now drop CREATE cells for already-existent circuit IDs and for
17824 zero-valued circuit IDs, regardless of other factors that might
17825 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
17827 - When rejecting DATA cells for stream_id zero, still count them
17828 against the circuit's deliver window so that we don't fail to send
17829 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
17831 o Minor bugfixes (relay, threading):
17832 - Check return code on spawn_func() in cpuworker code, so that we
17833 don't think we've spawned a nonworking cpuworker and write junk to
17834 it forever. Fix related to bug 4345; bugfix on all released Tor
17835 versions. Found by "skruffy".
17836 - Use a pthread_attr to make sure that spawn_func() cannot return an
17837 error while at the same time launching a thread. Fix related to
17838 bug 4345; bugfix on all released Tor versions. Reported
17841 o Minor bugfixes (relays and bridges):
17842 - Avoid crashing on a malformed resolv.conf file when running a
17843 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
17844 - Non-exit relays no longer launch mock DNS requests to check for
17845 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
17846 non-exit relays stopped servicing DNS requests. Fixes bug 965;
17847 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
17848 - Bridges now report complete directory request statistics. Related
17849 to bug 5824; bugfix on 0.2.2.1-alpha.
17850 - Bridges now never collect statistics that were designed for
17851 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
17853 o Minor bugfixes (testing):
17854 - Fix all valgrind warnings produced by the unit tests. There were
17855 over a thousand memory leak warnings previously, mostly produced
17856 by forgetting to free things in the unit test code. Fixes bug
17857 11618, bugfixes on many versions of Tor.
17859 o Minor bugfixes (tor-fw-helper):
17860 - Give a correct log message when tor-fw-helper fails to launch.
17861 (Previously, we would say something like "tor-fw-helper sent us a
17862 string we could not parse".) Fixes bug 9781; bugfix
17865 o Minor bugfixes (trivial memory leaks):
17866 - Fix a small memory leak when signing a directory object. Fixes bug
17867 11275; bugfix on 0.2.4.13-alpha.
17868 - Resolve some memory leaks found by coverity in the unit tests, on
17869 exit in tor-gencert, and on a failure to compute digests for our
17870 own keys when generating a v3 networkstatus vote. These leaks
17871 should never have affected anyone in practice.
17873 o Code simplification and refactoring:
17874 - Remove some old fallback code designed to keep Tor clients working
17875 in a network with only two working relays. Elsewhere in the code we
17876 have long since stopped supporting such networks, so there wasn't
17877 much point in keeping it around. Addresses ticket 9926.
17878 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
17879 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
17880 - Extract the common duplicated code for creating a subdirectory
17881 of the data directory and writing to a file in it. Fixes ticket
17882 4282; patch from Peter Retzlaff.
17883 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
17884 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
17885 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
17886 - Add a set of accessor functions for the circuit timeout data
17887 structure. Fixes ticket 6153; patch from "piet".
17888 - Clean up exit paths from connection_listener_new(). Closes ticket
17889 8789. Patch from Arlo Breault.
17890 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
17891 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
17892 - Use a doubly-linked list to implement the global circuit list.
17893 Resolves ticket 9108. Patch from Marek Majkowski.
17894 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
17895 - Remove constants and tests for PKCS1 padding; it's insecure and
17896 shouldn't be used for anything new. Fixes bug 8792; patch
17898 - Remove instances of strcpy() from the unit tests. They weren't
17899 hurting anything, since they were only in the unit tests, but it's
17900 embarrassing to have strcpy() in the code at all, and some analysis
17901 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
17902 0.2.3.8-alpha. Patch from Arlo Breault.
17903 - Remove is_internal_IP() function. Resolves ticket 4645.
17904 - Remove unused function circuit_dump_by_chan from circuitlist.c.
17905 Closes issue 9107; patch from "marek".
17906 - Change our use of the ENUM_BF macro to avoid declarations that
17908 - Get rid of router->address, since in all cases it was just the
17909 string representation of router->addr. Resolves ticket 5528.
17912 - Adjust the URLs in the README to refer to the new locations of
17913 several documents on the website. Fixes bug 12830. Patch from
17915 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
17917 - Update manpage to describe some of the files you can expect to
17918 find in Tor's DataDirectory. Addresses ticket 9839.
17919 - Clean up several option names in the manpage to match their real
17920 names, add the missing documentation for a couple of testing and
17921 directory authority options, remove the documentation for a
17922 V2-directory fetching option that no longer exists. Resolves
17924 - Correct the documentation so that it lists the correct directory
17925 for the stats files. (They are in a subdirectory called "stats",
17927 - In the manpage, move more authority-only options into the
17928 directory authority section so that operators of regular directory
17929 caches don't get confused.
17930 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
17931 11061; bugfix on 0.2.4.7-alpha.
17932 - Resolve warnings from Doxygen.
17933 - Document in the manpage that "KBytes" may also be written as
17934 "kilobytes" or "KB", that "Kbits" may also be written as
17935 "kilobits", and so forth. Closes ticket 9222.
17936 - Document that the ClientOnly config option overrides ORPort.
17937 Our old explanation made ClientOnly sound as though it did
17938 nothing at all. Resolves bug 9059.
17939 - Explain that SocksPolicy, DirPolicy, and similar options don't
17940 take port arguments. Fixes the other part of ticket 11108.
17941 - Fix a comment about the rend_server_descriptor_t.protocols field
17942 to more accurately describe its range. Also, make that field
17943 unsigned, to more accurately reflect its usage. Fixes bug 9099;
17944 bugfix on 0.2.1.5-alpha.
17945 - Fix the manpage's description of HiddenServiceAuthorizeClient:
17946 the maximum client name length is 16, not 19. Fixes bug 11118;
17947 bugfix on 0.2.1.6-alpha.
17950 - The contrib directory has been sorted and tidied. Before, it was
17951 an unsorted dumping ground for useful and not-so-useful things.
17952 Now, it is divided based on functionality, and the items which
17953 seemed to be nonfunctional or useless have been removed. Resolves
17954 ticket 8966; based on patches from "rl1987".
17956 o Removed code and features:
17957 - Clients now reject any directory authority certificates lacking
17958 a dir-key-crosscert element. These have been included since
17959 0.2.1.9-alpha, so there's no real reason for them to be optional
17960 any longer. Completes proposal 157. Resolves ticket 10162.
17961 - Remove all code that existed to support the v2 directory system,
17962 since there are no longer any v2 directory authorities. Resolves
17964 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
17965 options, which were used for designating authorities as "Hidden
17966 service authorities". There has been no use of hidden service
17967 authorities since 0.2.2.1-alpha, when we stopped uploading or
17968 downloading v0 hidden service descriptors. Fixes bug 10881; also
17969 part of a fix for bug 10841.
17970 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
17971 and MTBF calculations, but that nobody was using. Fixes bug 11742.
17972 - The TunnelDirConns and PreferTunnelledDirConns options no longer
17973 exist; tunneled directory connections have been available since
17974 0.1.2.5-alpha, and turning them off is not a good idea. This is a
17975 brute-force fix for 10849, where "TunnelDirConns 0" would break
17977 - Remove all code for the long unused v1 directory protocol.
17978 Resolves ticket 11070.
17979 - Remove all remaining code related to version-0 hidden service
17980 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
17981 the rest of bug 10841.
17982 - Remove migration code from when we renamed the "cached-routers"
17983 file to "cached-descriptors" back in 0.2.0.8-alpha. This
17984 incidentally resolves ticket 6502 by cleaning up the related code
17985 a bit. Patch from Akshay Hebbar.
17987 o Test infrastructure:
17988 - Tor now builds each source file in two modes: a mode that avoids
17989 exposing identifiers needlessly, and another mode that exposes
17990 more identifiers for testing. This lets the compiler do better at
17991 optimizing the production code, while enabling us to take more
17992 radical measures to let the unit tests test things.
17993 - The production builds no longer include functions used only in
17994 the unit tests; all functions exposed from a module only for
17995 unit-testing are now static in production builds.
17996 - Add an --enable-coverage configuration option to make the unit
17997 tests (and a new src/or/tor-cov target) to build with gcov test
17999 - Update to the latest version of tinytest.
18000 - Improve the tinytest implementation of string operation tests so
18001 that comparisons with NULL strings no longer crash the tests; they
18002 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
18003 - New macros in test.h to simplify writing mock-functions for unit
18004 tests. Part of ticket 11507. Patch from Dana Koch.
18005 - We now have rudimentary function mocking support that our unit
18006 tests can use to test functions in isolation. Function mocking
18007 lets the tests temporarily replace a function's dependencies with
18008 stub functions, so that the tests can check the function without
18009 invoking the other functions it calls.
18012 - Complete tests for the status.c module. Resolves ticket 11507.
18013 Patch from Dana Koch.
18014 - Add more unit tests for the <circid,channel>->circuit map, and
18015 the destroy-cell-tracking code to fix bug 7912.
18016 - Unit tests for failing cases of the TAP onion handshake.
18017 - More unit tests for address-manipulation functions.
18019 o Distribution (systemd):
18020 - Include a tor.service file in contrib/dist for use with systemd.
18021 Some distributions will be able to use this file unmodified;
18022 others will need to tweak it, or write their own. Patch from Jamie
18023 Nguyen; resolves ticket 8368.
18024 - Verify configuration file via ExecStartPre in the systemd unit
18025 file. Patch from intrigeri; resolves ticket 12730.
18026 - Explicitly disable RunAsDaemon in the systemd unit file. Our
18027 current systemd unit uses "Type = simple", so systemd does not
18028 expect tor to fork. If the user has "RunAsDaemon 1" in their
18029 torrc, then things won't work as expected. This is e.g. the case
18030 on Debian (and derivatives), since there we pass "--defaults-torrc
18031 /usr/share/tor/tor-service-defaults-torrc" (that contains
18032 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
18036 Changes in version 0.2.4.25 - 2014-10-20
18037 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
18038 (even though POODLE does not affect Tor). It also works around a crash
18039 bug caused by some operating systems' response to the "POODLE" attack
18040 (which does affect Tor).
18042 o Major security fixes (also in 0.2.5.9-rc):
18043 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
18044 today support TLS 1.0 or later, so we can safely turn off support
18045 for this old (and insecure) protocol. Fixes bug 13426.
18047 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
18048 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
18049 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
18050 13471. This is a workaround for an OpenSSL bug.
18053 Changes in version 0.2.4.24 - 2014-09-22
18054 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
18055 connecting to hidden services, and it updates the location of one of
18056 the directory authorities.
18059 - Clients now send the correct address for their chosen rendezvous
18060 point when trying to access a hidden service. They used to send
18061 the wrong address, which would still work some of the time because
18062 they also sent the identity digest of the rendezvous point, and if
18063 the hidden service happened to try connecting to the rendezvous
18064 point from a relay that already had a connection open to it,
18065 the relay would reuse that connection. Now connections to hidden
18066 services should be more robust and faster. Also, this bug meant
18067 that clients were leaking to the hidden service whether they were
18068 on a little-endian (common) or big-endian (rare) system, which for
18069 some users might have reduced their anonymity. Fixes bug 13151;
18070 bugfix on 0.2.1.5-alpha.
18072 o Directory authority changes:
18073 - Change IP address for gabelmoo (v3 directory authority).
18075 o Minor features (geoip):
18076 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
18080 Changes in version 0.2.4.23 - 2014-07-28
18081 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
18082 guard rotation, and also backports several important fixes from the
18083 Tor 0.2.5 alpha release series.
18086 - Clients now look at the "usecreatefast" consensus parameter to
18087 decide whether to use CREATE_FAST or CREATE cells for the first hop
18088 of their circuit. This approach can improve security on connections
18089 where Tor's circuit handshake is stronger than the available TLS
18090 connection security levels, but the tradeoff is more computational
18091 load on guard relays. Implements proposal 221. Resolves ticket 9386.
18092 - Make the number of entry guards configurable via a new
18093 NumEntryGuards consensus parameter, and the number of directory
18094 guards configurable via a new NumDirectoryGuards consensus
18095 parameter. Implements ticket 12688.
18098 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
18099 implementation that caused incorrect results on 32-bit
18100 implementations when certain malformed inputs were used along with
18101 a small class of private ntor keys. This bug does not currently
18102 appear to allow an attacker to learn private keys or impersonate a
18103 Tor server, but it could provide a means to distinguish 32-bit Tor
18104 implementations from 64-bit Tor implementations. Fixes bug 12694;
18105 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
18109 - Warn and drop the circuit if we receive an inbound 'relay early'
18110 cell. Those used to be normal to receive on hidden service circuits
18111 due to bug 1038, but the buggy Tor versions are long gone from
18112 the network so we can afford to resume watching for them. Resolves
18113 the rest of bug 1038; bugfix on 0.2.1.19.
18114 - Correct a confusing error message when trying to extend a circuit
18115 via the control protocol but we don't know a descriptor or
18116 microdescriptor for one of the specified relays. Fixes bug 12718;
18117 bugfix on 0.2.3.1-alpha.
18118 - Avoid an illegal read from stack when initializing the TLS
18119 module using a version of OpenSSL without all of the ciphers
18120 used by the v2 link handshake. Fixes bug 12227; bugfix on
18121 0.2.4.8-alpha. Found by "starlight".
18124 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
18128 Changes in version 0.2.4.22 - 2014-05-16
18129 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
18130 alpha release series. These include blocking all authority signing
18131 keys that may have been affected by the OpenSSL "heartbleed" bug,
18132 choosing a far more secure set of TLS ciphersuites by default, closing
18133 a couple of memory leaks that could be used to run a target relay out
18134 of RAM, and several others.
18136 o Major features (security, backport from 0.2.5.4-alpha):
18137 - Block authority signing keys that were used on authorities
18138 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
18139 don't have any evidence that these keys _were_ compromised; we're
18140 doing this to be prudent.) Resolves ticket 11464.
18142 o Major bugfixes (security, OOM):
18143 - Fix a memory leak that could occur if a microdescriptor parse
18144 fails during the tokenizing step. This bug could enable a memory
18145 exhaustion attack by directory servers. Fixes bug 11649; bugfix
18148 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
18149 - The relay ciphersuite list is now generated automatically based on
18150 uniform criteria, and includes all OpenSSL ciphersuites with
18151 acceptable strength and forward secrecy. Previously, we had left
18152 some perfectly fine ciphersuites unsupported due to omission or
18153 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
18154 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
18155 - Relays now trust themselves to have a better view than clients of
18156 which TLS ciphersuites are better than others. (Thanks to bug
18157 11513, the relay list is now well-considered, whereas the client
18158 list has been chosen mainly for anti-fingerprinting purposes.)
18159 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
18160 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
18161 AES128. Resolves ticket 11528.
18162 - Clients now try to advertise the same list of ciphersuites as
18163 Firefox 28. This change enables selection of (fast) GCM
18164 ciphersuites, disables some strange old ciphers, and stops
18165 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
18166 Resolves ticket 11438.
18168 o Minor bugfixes (configuration, security):
18169 - When running a hidden service, do not allow TunneledDirConns 0:
18170 trying to set that option together with a hidden service would
18171 otherwise prevent the hidden service from running, and also make
18172 it publish its descriptors directly over HTTP. Fixes bug 10849;
18173 bugfix on 0.2.1.1-alpha.
18175 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
18176 - Avoid sending a garbage value to the controller when a circuit is
18177 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
18179 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
18180 - Stop leaking memory when we successfully resolve a PTR record.
18181 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
18183 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
18184 - Avoid 60-second delays in the bootstrapping process when Tor is
18185 launching for a second time while using bridges. Fixes bug 9229;
18186 bugfix on 0.2.0.3-alpha.
18188 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
18189 - Give the correct URL in the warning message when trying to run a
18190 relay on an ancient version of Windows. Fixes bug 9393.
18192 o Minor bugfixes (compilation):
18193 - Fix a compilation error when compiling with --disable-curve25519.
18194 Fixes bug 9700; bugfix on 0.2.4.17-rc.
18197 - Downgrade the warning severity for the the "md was still
18198 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
18199 for trying to diagnose this bug, and the current warning in
18200 earlier versions of tor achieves nothing useful. Addresses warning
18203 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
18204 - When we run out of usable circuit IDs on a channel, log only one
18205 warning for the whole channel, and describe how many circuits
18206 there were on the channel. Fixes part of ticket 11553.
18208 o Minor features (security, backport from 0.2.5.4-alpha):
18209 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
18210 leave the default at 8GBytes), to better support Raspberry Pi
18211 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
18213 o Documentation (backport from 0.2.5.4-alpha):
18214 - Correctly document that we search for a system torrc file before
18215 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
18219 Changes in version 0.2.4.21 - 2014-02-28
18220 Tor 0.2.4.21 further improves security against potential adversaries who
18221 find breaking 1024-bit crypto doable, and backports several stability
18222 and robustness patches from the 0.2.5 branch.
18224 o Major features (client security):
18225 - When we choose a path for a 3-hop circuit, make sure it contains
18226 at least one relay that supports the NTor circuit extension
18227 handshake. Otherwise, there is a chance that we're building
18228 a circuit that's worth attacking by an adversary who finds
18229 breaking 1024-bit crypto doable, and that chance changes the game
18230 theory. Implements ticket 9777.
18233 - Do not treat streams that fail with reason
18234 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
18235 since it could also indicate an ENETUNREACH connection error. Fixes
18236 part of bug 10777; bugfix on 0.2.4.8-alpha.
18238 o Code simplification and refactoring:
18239 - Remove data structures which were introduced to implement the
18240 CellStatistics option: they are now redundant with the new timestamp
18241 field in the regular packed_cell_t data structure, which we did
18242 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
18245 - Always clear OpenSSL bignums before freeing them -- even bignums
18246 that don't contain secrets. Resolves ticket 10793. Patch by
18248 - Build without warnings under clang 3.4. (We have some macros that
18249 define static functions only some of which will get used later in
18250 the module. Starting with clang 3.4, these give a warning unless the
18251 unused attribute is set on them.) Resolves ticket 10904.
18252 - Update geoip and geoip6 files to the February 7 2014 Maxmind
18253 GeoLite2 Country database.
18256 - Set the listen() backlog limit to the largest actually supported
18257 on the system, not to the value in a header file. Fixes bug 9716;
18258 bugfix on every released Tor.
18259 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
18260 exit node as a NOROUTE error, not an INTERNAL error, since they
18261 can apparently happen when trying to connect to the wrong sort
18262 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
18263 - Fix build warnings about missing "a2x" comment when building the
18264 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
18265 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
18266 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
18267 not entirely remove it from the connection lists. Fixes bug 9602;
18268 bugfix on 0.2.4.4-alpha.
18269 - Fix a segmentation fault in our benchmark code when running with
18270 Fedora's OpenSSL package, or any other OpenSSL that provides
18271 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
18272 - Turn "circuit handshake stats since last time" log messages into a
18273 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
18275 o Documentation fixes:
18276 - Document that all but one DirPort entry must have the NoAdvertise
18277 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
18280 Changes in version 0.2.4.20 - 2013-12-22
18281 Tor 0.2.4.20 fixes potentially poor random number generation for users
18282 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
18283 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
18284 and 4) have no state file in their DataDirectory (as would happen on
18285 first start). Users who generated relay or hidden service identity
18286 keys in such a situation should discard them and generate new ones.
18288 This release also fixes a logic error that caused Tor clients to build
18289 many more preemptive circuits than they actually need.
18292 - Do not allow OpenSSL engines to replace the PRNG, even when
18293 HardwareAccel is set. The only default builtin PRNG engine uses
18294 the Intel RDRAND instruction to replace the entire PRNG, and
18295 ignores all attempts to seed it with more entropy. That's
18296 cryptographically stupid: the right response to a new alleged
18297 entropy source is never to discard all previously used entropy
18298 sources. Fixes bug 10402; works around behavior introduced in
18299 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
18301 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
18302 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
18303 - Avoid launching spurious extra circuits when a stream is pending.
18304 This fixes a bug where any circuit that _wasn't_ unusable for new
18305 streams would be treated as if it were, causing extra circuits to
18306 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
18309 - Avoid a crash bug when starting with a corrupted microdescriptor
18310 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
18311 - If we fail to dump a previously cached microdescriptor to disk, avoid
18312 freeing duplicate data later on. Fixes bug 10423; bugfix on
18313 0.2.4.13-alpha. Spotted by "bobnomnom".
18316 Changes in version 0.2.4.19 - 2013-12-11
18317 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
18318 (1986-2013). Aaron worked on diverse projects including helping to guide
18319 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
18320 transparency to the U.S government's PACER documents, and contributing
18321 design and development for Tor and Tor2Web. Aaron was one of the latest
18322 martyrs in our collective fight for civil liberties and human rights,
18323 and his death is all the more painful because he was one of us.
18325 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
18326 a new circuit handshake and link encryption that use ECC to provide
18327 better security and efficiency; makes relays better manage circuit
18328 creation requests; uses "directory guards" to reduce client enumeration
18329 risks; makes bridges collect and report statistics about the pluggable
18330 transports they support; cleans up and improves our geoip database;
18331 gets much closer to IPv6 support for clients, bridges, and relays; makes
18332 directory authorities use measured bandwidths rather than advertised
18333 ones when computing flags and thresholds; disables client-side DNS
18334 caching to reduce tracking risks; and fixes a big bug in bridge
18335 reachability testing. This release introduces two new design
18336 abstractions in the code: a new "channel" abstraction between circuits
18337 and or_connections to allow for implementing alternate relay-to-relay
18338 transports, and a new "circuitmux" abstraction storing the queue of
18339 circuits for a channel. The release also includes many stability,
18340 security, and privacy fixes.
18342 o Major features (new circuit handshake):
18343 - Tor now supports a new circuit extension handshake designed by Ian
18344 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
18345 circuit extension handshake, later called "TAP", was a bit slow
18346 (especially on the relay side), had a fragile security proof, and
18347 used weaker keys than we'd now prefer. The new circuit handshake
18348 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
18349 function, making it significantly more secure than the older
18350 handshake, and significantly faster. Tor can use one of two built-in
18351 pure-C curve25519-donna implementations by Adam Langley, or it
18352 can link against the "nacl" library for a tuned version if present.
18354 The built-in version is very fast for 64-bit systems when building
18355 with GCC. The built-in 32-bit version is still faster than the
18356 old TAP protocol, but using libnacl is better on most such hosts.
18358 Implements proposal 216; closes ticket 7202.
18360 o Major features (better link encryption):
18361 - Relays can now enable the ECDHE TLS ciphersuites when available
18362 and appropriate. These ciphersuites let us negotiate forward-secure
18363 TLS secret keys more safely and more efficiently than with our
18364 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
18365 public relays prefer the (faster) P224 group, and bridges prefer
18366 the (more common) P256 group; you can override this with the
18369 This feature requires clients running 0.2.3.17-beta or later,
18370 and requires both sides to be running OpenSSL 1.0.0 or later
18371 with ECC support. OpenSSL 1.0.1, with the compile-time option
18372 "enable-ec_nistp_64_gcc_128", is highly recommended.
18374 Implements the relay side of proposal 198; closes ticket 7200.
18376 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
18377 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
18378 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
18379 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
18380 them to solve bug 6033.)
18382 o Major features (relay performance):
18383 - Instead of limiting the number of queued onionskins (aka circuit
18384 create requests) to a fixed, hard-to-configure number, we limit
18385 the size of the queue based on how many we expect to be able to
18386 process in a given amount of time. We estimate the time it will
18387 take to process an onionskin based on average processing time
18388 of previous onionskins. Closes ticket 7291. You'll never have to
18389 configure MaxOnionsPending again.
18390 - Relays process the new "NTor" circuit-level handshake requests
18391 with higher priority than the old "TAP" circuit-level handshake
18392 requests. We still process some TAP requests to not totally starve
18393 0.2.3 clients when NTor becomes popular. A new consensus parameter
18394 "NumNTorsPerTAP" lets us tune the balance later if we need to.
18395 Implements ticket 9574.
18397 o Major features (client bootstrapping resilience):
18398 - Add a new "FallbackDir" torrc option to use when we can't use
18399 a directory mirror from the consensus (either because we lack a
18400 consensus, or because they're all down). Currently, all authorities
18401 are fallbacks by default, and there are no other default fallbacks,
18402 but that will change. This option will allow us to give clients a
18403 longer list of servers to try to get a consensus from when first
18404 connecting to the Tor network, and thereby reduce load on the
18405 directory authorities. Implements proposal 206, "Preconfigured
18406 directory sources for bootstrapping". We also removed the old
18407 "FallbackNetworkstatus" option, since we never got it working well
18408 enough to use it. Closes bug 572.
18409 - If we have no circuits open, use a relaxed timeout (the
18410 95th-percentile cutoff) until a circuit succeeds. This heuristic
18411 should allow Tor to succeed at building circuits even when the
18412 network connection drastically changes. Should help with bug 3443.
18414 o Major features (use of guards):
18415 - Support directory guards (proposal 207): when possible, clients now
18416 use their entry guards for non-anonymous directory requests. This
18417 can help prevent client enumeration. Note that this behavior only
18418 works when we have a usable consensus directory, and when options
18419 about what to download are more or less standard. In the future we
18420 should re-bootstrap from our guards, rather than re-bootstrapping
18421 from the preconfigured list of directory sources that ships with
18422 Tor. Resolves ticket 6526.
18423 - Raise the default time that a client keeps an entry guard from
18424 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
18425 2012 paper. (We would make it even longer, but we need better client
18426 load balancing first.) Also, make the guard lifetime controllable
18427 via a new GuardLifetime torrc option and a GuardLifetime consensus
18428 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
18430 o Major features (bridges with pluggable transports):
18431 - Bridges now report the pluggable transports they support to the
18432 bridge authority, so it can pass the supported transports on to
18433 bridgedb and/or eventually do reachability testing. Implements
18435 - Automatically forward the TCP ports of pluggable transport
18436 proxies using tor-fw-helper if PortForwarding is enabled. Implements
18439 o Major features (geoip database):
18440 - Maxmind began labelling Tor relays as being in country "A1",
18441 which breaks by-country node selection inside Tor. Now we use a
18442 script to replace "A1" ("Anonymous Proxy") entries in our geoip
18443 file with real country codes. This script fixes about 90% of "A1"
18444 entries automatically and uses manual country code assignments to
18445 fix the remaining 10%. See src/config/README.geoip for details.
18447 - Add GeoIP database for IPv6 addresses. The new config option
18449 - Update to the October 2 2013 Maxmind GeoLite Country database.
18451 o Major features (IPv6):
18452 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
18453 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
18454 to happen. Implements ticket 5535.
18455 - All kind of relays, not just bridges, can now advertise an IPv6
18456 OR port. Implements ticket 6362.
18457 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
18458 connectivity, then set the IPv6Exit flag to 1. Also make sure your
18459 exit policy reads as you would like: the address * applies to all
18460 address families, whereas *4 is IPv4 address only, and *6 is IPv6
18461 addresses only. On the client side, you'll need to wait for enough
18462 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
18463 and use Socks5. Closes ticket 5547, implements proposal 117 as
18464 revised in proposal 208.
18465 - Bridge authorities now accept IPv6 bridge addresses and include
18466 them in network status documents. Implements ticket 5534.
18467 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
18469 o Major features (directory authorities):
18470 - Directory authorities now prefer using measured bandwidths to
18471 advertised ones when computing flags and thresholds. Resolves
18473 - Directory authorities that vote measured bandwidths about more
18474 than a threshold number of relays now treat relays with
18475 unmeasured bandwidths as having bandwidth 0 when computing their
18476 flags. Resolves ticket 8435.
18477 - Directory authorities now support a new consensus method (17)
18478 where they cap the published bandwidth of relays for which
18479 insufficient bandwidth measurements exist. Fixes part of bug 2286.
18480 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
18481 serve any v2 directory information. Now we can test disabling the
18482 old deprecated v2 directory format, and see whether doing so has
18483 any effect on network load. Begins to fix bug 6783.
18485 o Major features (build and portability):
18486 - Switch to a nonrecursive Makefile structure. Now instead of each
18487 Makefile.am invoking other Makefile.am's, there is a master
18488 Makefile.am that includes the others. This change makes our build
18489 process slightly more maintainable, and improves parallelism for
18490 building with make -j. Original patch by Stewart Smith; various
18491 fixes by Jim Meyering.
18492 - Where available, we now use automake's "silent" make rules by
18493 default, so that warnings are easier to spot. You can get the old
18494 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
18495 - Resume building correctly with MSVC and Makefile.nmake. This patch
18496 resolves numerous bugs and fixes reported by ultramage, including
18497 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
18499 o Security features:
18500 - Switch to a completely time-invariant approach for picking nodes
18501 weighted by bandwidth. Our old approach would run through the
18502 part of the loop after it had made its choice slightly slower
18503 than it ran through the part of the loop before it had made its
18504 choice. Addresses ticket 6538.
18505 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
18506 by tor2web clients allows hidden services to identify tor2web
18507 clients through their repeated selection of the same rendezvous
18508 and introduction point circuit endpoints (their guards). Resolves
18511 o Major bugfixes (relay denial of service):
18512 - When we have too much memory queued in circuits (according to a new
18513 MaxMemInCellQueues option), close the circuits that have the oldest
18514 queued cells, on the theory that those are most responsible for
18515 us running low on memory. This prevents us from running out of
18516 memory as a relay if circuits fill up faster than they can be
18517 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
18518 Tor. This bug is a further fix beyond bug 6252, whose fix was
18519 merged into 0.2.3.21-rc.
18520 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
18521 ID: these could be used to create unexpected streams and circuits
18522 which would count as "present" to some parts of Tor but "absent"
18523 to others, leading to zombie circuits and streams or to a bandwidth
18524 denial-of-service. Fixes bug 7889; bugfix on every released version
18525 of Tor. Reported by "oftc_must_be_destroyed".
18526 - Avoid a bug where our response to TLS renegotiation under certain
18527 network conditions could lead to a busy-loop, with 100% CPU
18528 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
18530 o Major bugfixes (asserts, crashes, leaks):
18531 - Prevent the get_freelists() function from running off the end of
18532 the list of freelists if it somehow gets an unrecognized
18533 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
18535 - Avoid a memory leak where we would leak a consensus body when we
18536 find that a consensus which we couldn't previously verify due to
18537 missing certificates is now verifiable. Fixes bug 8719; bugfix
18539 - If we are unable to save a microdescriptor to the journal, do not
18540 drop it from memory and then reattempt downloading it. Fixes bug
18541 9645; bugfix on 0.2.2.6-alpha.
18542 - Fix an assertion failure that would occur when disabling the
18543 ORPort setting on a running Tor process while accounting was
18544 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
18545 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
18546 when an exit connection with optimistic data succeeds immediately
18547 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
18549 - Fix a memory leak that would occur whenever a configuration
18550 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
18552 o Major bugfixes (relay rate limiting):
18553 - When a TLS write is partially successful but incomplete, remember
18554 that the flushed part has been flushed, and notice that bytes were
18555 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
18556 bugfix on Tor 0.1.0.5-rc.
18557 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
18558 to 1GB/1GB. The previous defaults were intended to be "basically
18559 infinite", but it turns out they're now limiting our 100mbit+
18560 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
18561 last time we raised it).
18562 - No longer stop reading or writing on cpuworker connections when
18563 our rate limiting buckets go empty. Now we should handle circuit
18564 handshake requests more promptly. Resolves bug 9731.
18566 o Major bugfixes (client-side privacy):
18567 - When we mark a circuit as unusable for new circuits, have it
18568 continue to be unusable for new circuits even if MaxCircuitDirtiness
18569 is increased too much at the wrong time, or the system clock jumps
18570 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
18571 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
18572 which have resolved to internal addresses") is set, apply that
18573 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
18574 - When an exit relay rejects a stream with reason "exit policy", but
18575 we only know an exit policy summary (e.g. from the microdesc
18576 consensus) for it, do not mark the relay as useless for all exiting.
18577 Instead, mark just the circuit as unsuitable for that particular
18578 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
18580 o Major bugfixes (stream isolation):
18581 - Allow applications to get proper stream isolation with
18582 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
18583 username/password authentication also offer "no authentication". Tor
18584 had previously preferred "no authentication", so the applications
18585 never actually sent Tor their auth details. Now Tor selects
18586 username/password authentication if it's offered. You can disable
18587 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
18588 bug 8117; bugfix on 0.2.3.3-alpha.
18589 - Follow the socks5 protocol when offering username/password
18590 authentication. The fix for bug 8117 exposed this bug, and it
18591 turns out real-world applications like Pidgin do care. Bugfix on
18592 0.2.3.2-alpha; fixes bug 8879.
18594 o Major bugfixes (client circuit building):
18595 - Alter circuit build timeout measurement to start at the point
18596 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
18597 initialization). This should make our timeout measurements more
18598 uniform. Previously, we were sometimes including ORconn setup time
18599 in our circuit build time measurements. Should resolve bug 3443.
18600 - If the circuit build timeout logic is disabled (via the consensus,
18601 or because we are an authority), then don't build testing circuits.
18602 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
18604 o Major bugfixes (client-side DNS):
18605 - Turn off the client-side DNS cache by default. Updating and using
18606 the DNS cache is now configurable on a per-client-port
18607 level. SOCKSPort, DNSPort, etc lines may now contain
18608 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
18609 cache these types of DNS answers when we receive them from an
18610 exit node in response to an application request on this port, and
18611 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
18612 cached DNS answers of these types, we shouldn't use them. It's
18613 potentially risky to use cached DNS answers at the client, since
18614 doing so can indicate to one exit what answers we've gotten
18615 for DNS lookups in the past. With IPv6, this becomes especially
18616 problematic. Using cached DNS answers for requests on the same
18617 circuit would present less linkability risk, since all traffic
18618 on a circuit is already linkable, but it would also provide
18619 little performance benefit: the exit node caches DNS replies
18620 too. Implements a simplified version of Proposal 205. Implements
18623 o Major bugfixes (hidden service privacy):
18624 - Limit hidden service descriptors to at most ten introduction
18625 points, to slow one kind of guard enumeration. Fixes bug 9002;
18626 bugfix on 0.1.1.11-alpha.
18628 o Major bugfixes (directory fetching):
18629 - If the time to download the next old-style networkstatus is in
18630 the future, do not decline to consider whether to download the
18631 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
18633 - We used to always request authority certificates by identity digest,
18634 meaning we'd get the newest one even when we wanted one with a
18635 different signing key. Then we would complain about being given
18636 a certificate we already had, and never get the one we really
18637 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
18638 resource to request the one we want. Fixes bug 5595; bugfix on
18641 o Major bugfixes (bridge reachability):
18642 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
18643 previously they did not, which prevented them from receiving
18644 successful connections from relays for self-test or bandwidth
18645 testing. Also, when a relay is extending a circuit to a bridge,
18646 it needs to send a NETINFO cell, even when the bridge hasn't sent
18647 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
18649 o Major bugfixes (control interface):
18650 - When receiving a new configuration file via the control port's
18651 LOADCONF command, do not treat the defaults file as absent.
18652 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
18654 o Major bugfixes (directory authorities):
18655 - Stop marking every relay as having been down for one hour every
18656 time we restart a directory authority. These artificial downtimes
18657 were messing with our Stable and Guard flag calculations. Fixes
18658 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
18659 - When computing directory thresholds, ignore any rejected-as-sybil
18660 nodes during the computation so that they can't influence Fast,
18661 Guard, etc. (We should have done this for proposal 109.) Fixes
18663 - When marking a node as a likely sybil, reset its uptime metrics
18664 to zero, so that it cannot time towards getting marked as Guard,
18665 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
18667 - Fix a bug in the voting algorithm that could yield incorrect results
18668 when a non-naming authority declared too many flags. Fixes bug 9200;
18669 bugfix on 0.2.0.3-alpha.
18671 o Internal abstraction features:
18672 - Introduce new channel_t abstraction between circuits and
18673 or_connection_t to allow for implementing alternate OR-to-OR
18674 transports. A channel_t is an abstract object which can either be a
18675 cell-bearing channel, which is responsible for authenticating and
18676 handshaking with the remote OR and transmitting cells to and from
18677 it, or a listening channel, which spawns new cell-bearing channels
18678 at the request of remote ORs. Implements part of ticket 6465.
18679 - Make a channel_tls_t subclass of channel_t, adapting it to the
18680 existing or_connection_t code. The V2/V3 protocol handshaking
18681 code which formerly resided in command.c has been moved below the
18682 channel_t abstraction layer and may be found in channeltls.c now.
18683 Implements the rest of ticket 6465.
18684 - Introduce new circuitmux_t storing the queue of circuits for
18685 a channel; this encapsulates and abstracts the queue logic and
18686 circuit selection policy, and allows the latter to be overridden
18687 easily by switching out a policy object. The existing EWMA behavior
18688 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
18690 o New build requirements:
18691 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
18692 strongly recommended.
18693 - Tor maintainers now require Automake version 1.9 or later to build
18694 Tor from the Git repository. (Automake is not required when building
18695 from a source distribution.)
18697 o Minor features (protocol):
18698 - No longer include the "opt" prefix when generating routerinfos
18699 or v2 directories: it has been needless since Tor 0.1.2. Closes
18701 - Reject EXTEND cells sent to nonexistent streams. According to the
18702 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
18703 we were only checking for stream IDs that were currently in use.
18704 Found while hunting for more instances of bug 6271. Bugfix on
18705 0.0.2pre8, which introduced incremental circuit construction.
18706 - Tor relays and clients now support a better CREATE/EXTEND cell
18707 format, allowing the sender to specify multiple address, identity,
18708 and handshake types. Implements Robert Ransom's proposal 200;
18709 closes ticket 7199.
18710 - Reject as invalid most directory objects containing a NUL.
18711 Belt-and-suspender fix for bug 8037.
18713 o Minor features (security):
18714 - Clear keys and key-derived material left on the stack in
18715 rendservice.c and rendclient.c. Check return value of
18716 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
18717 These fixes should make us more forward-secure against cold-boot
18718 attacks and the like. Fixes bug 2385.
18719 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
18720 Irix's random() only return 15 bits; Solaris's random() returns more
18721 bits but its RAND_MAX says it only returns 15, and so on. Motivated
18722 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
18724 o Minor features (control protocol):
18725 - Add a "GETINFO signal/names" control port command. Implements
18727 - Provide default values for all options via "GETINFO config/defaults".
18728 Implements ticket 4971.
18729 - Allow an optional $ before the node identity digest in the
18730 controller command GETINFO ns/id/<identity>, for consistency with
18731 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
18732 - Add CACHED keyword to ADDRMAP events in the control protocol
18733 to indicate whether a DNS result will be cached or not. Resolves
18735 - Generate bootstrapping status update events correctly when fetching
18736 microdescriptors. Fixes bug 9927.
18738 o Minor features (path selection):
18739 - When deciding whether we have enough descriptors to build circuits,
18740 instead of looking at raw relay counts, look at which fraction
18741 of (bandwidth-weighted) paths we're able to build. This approach
18742 keeps clients from building circuits if their paths are likely to
18743 stand out statistically. The default fraction of paths needed is
18744 taken from the consensus directory; you can override it with the
18745 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
18746 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
18747 and we have GeoIP information, also exclude all nodes with unknown
18748 countries "??" and "A1". This behavior is controlled by the
18749 new GeoIPExcludeUnknown option: you can make such nodes always
18750 excluded with "GeoIPExcludeUnknown 1", and disable the feature
18751 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
18752 gets you the default behavior. Implements feature 7706.
18754 o Minor features (hidden services):
18755 - Improve circuit build timeout handling for hidden services.
18756 In particular: adjust build timeouts more accurately depending
18757 upon the number of hop-RTTs that a particular circuit type
18758 undergoes. Additionally, launch intro circuits in parallel
18759 if they timeout, and take the first one to reply as valid.
18760 - The Tor client now ignores sub-domain components of a .onion
18761 address. This change makes HTTP "virtual" hosting
18762 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
18763 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
18764 hosted on the same hidden service. Implements proposal 204.
18765 - Enable Tor to read configuration, state, and key information from
18766 a FIFO. Previously Tor would only read from files with a positive
18767 stat.st_size. Code from meejah; fixes bug 6044.
18769 o Minor features (clients):
18770 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
18771 microdescriptor-related dir requests, and only fall back to normal
18772 descriptors if none of their bridges can handle microdescriptors
18773 (as opposed to the fix in ticket 4013, which caused them to fall
18774 back to normal descriptors if *any* of their bridges preferred
18775 them). Resolves ticket 4994.
18776 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
18777 TCP ports to forward. In the past it only accepted two ports:
18778 the ORPort and the DirPort.
18780 o Minor features (protecting client timestamps):
18781 - Clients no longer send timestamps in their NETINFO cells. These were
18782 not used for anything, and they provided one small way for clients
18783 to be distinguished from each other as they moved from network to
18784 network or behind NAT. Implements part of proposal 222.
18785 - Clients now round timestamps in INTRODUCE cells down to the nearest
18786 10 minutes. If a new Support022HiddenServices option is set to 0, or
18787 if it's set to "auto" and the feature is disabled in the consensus,
18788 the timestamp is sent as 0 instead. Implements part of proposal 222.
18789 - Stop sending timestamps in AUTHENTICATE cells. This is not such
18790 a big deal from a security point of view, but it achieves no actual
18791 good purpose, and isn't needed. Implements part of proposal 222.
18792 - Reduce down accuracy of timestamps in hidden service descriptors.
18793 Implements part of proposal 222.
18795 o Minor features (bridges):
18796 - Make bridge relays check once a minute for whether their IP
18797 address has changed, rather than only every 15 minutes. Resolves
18798 bugs 1913 and 1992.
18799 - Bridge statistics now count bridge clients connecting over IPv6:
18800 bridge statistics files now list "bridge-ip-versions" and
18801 extra-info documents list "geoip6-db-digest". The control protocol
18802 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
18803 implementation by "shkoo", addressing ticket 5055.
18804 - Add a new torrc option "ServerTransportListenAddr" to let bridge
18805 operators select the address where their pluggable transports will
18806 listen for connections. Resolves ticket 7013.
18807 - Randomize the lifetime of our SSL link certificate, so censors can't
18808 use the static value for filtering Tor flows. Resolves ticket 8443;
18809 related to ticket 4014 which was included in 0.2.2.33.
18811 o Minor features (relays):
18812 - Option OutboundBindAddress can be specified multiple times and
18813 accepts IPv6 addresses. Resolves ticket 6876.
18815 o Minor features (IPv6, client side):
18816 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
18817 prefer to hand out virtual IPv6 addresses, since there are more of
18818 them and we can't run out. To override this behavior and make IPv4
18819 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
18820 or DNSPort you're using for resolving. Implements ticket 7571.
18821 - AutomapHostsOnResolve responses are now randomized, to avoid
18822 annoying situations where Tor is restarted and applications
18823 connect to the wrong addresses.
18824 - Never try more than 1000 times to pick a new virtual address when
18825 AutomapHostsOnResolve is set. That's good enough so long as we
18826 aren't close to handing out our entire virtual address space;
18827 if you're getting there, it's best to switch to IPv6 virtual
18830 o Minor features (IPv6, relay/authority side):
18831 - New config option "AuthDirHasIPv6Connectivity 1" that directory
18832 authorities should set if they have IPv6 connectivity and want to
18833 do reachability tests for IPv6 relays. Implements feature 5974.
18834 - A relay with an IPv6 OR port now sends that address in NETINFO
18835 cells (in addition to its other address). Implements ticket 6364.
18837 o Minor features (directory authorities):
18838 - Directory authorities no long accept descriptors for any version of
18839 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
18840 These versions are insecure, unsupported, or both. Implements
18842 - When directory authorities are computing thresholds for flags,
18843 never let the threshold for the Fast flag fall below 4096
18844 bytes. Also, do not consider nodes with extremely low bandwidths
18845 when deciding thresholds for various directory flags. This change
18846 should raise our threshold for Fast relays, possibly in turn
18847 improving overall network performance; see ticket 1854. Resolves
18849 - Directory authorities now include inside each vote a statement of
18850 the performance thresholds they used when assigning flags.
18851 Implements ticket 8151.
18852 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
18853 in directory authority votes to describe whether they have enough
18854 measured bandwidths to ignore advertised (relay descriptor)
18855 bandwidth claims. Resolves ticket 8711.
18857 o Minor features (path bias detection):
18858 - Path Use Bias: Perform separate accounting for successful circuit
18859 use. Keep separate statistics on stream attempt rates versus stream
18860 success rates for each guard. Provide configurable thresholds to
18861 determine when to emit log messages or disable use of guards that
18862 fail too many stream attempts. Resolves ticket 7802.
18863 - Create three levels of Path Bias log messages, as opposed to just
18864 two. These are configurable via consensus as well as via the torrc
18865 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
18866 The default values are 0.70, 0.50, and 0.30 respectively.
18867 - Separate the log message levels from the decision to drop guards,
18868 which also is available via torrc option PathBiasDropGuards.
18869 PathBiasDropGuards still defaults to 0 (off).
18870 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
18871 in combination with PathBiasExtremeRate.
18872 - Increase the default values for PathBiasScaleThreshold and
18873 PathBiasCircThreshold from (200, 20) to (300, 150).
18874 - Add in circuit usage accounting to path bias. If we try to use a
18875 built circuit but fail for any reason, it counts as path bias.
18876 Certain classes of circuits where the adversary gets to pick your
18877 destination node are exempt from this accounting. Usage accounting
18878 can be specifically disabled via consensus parameter or torrc.
18879 - Convert all internal path bias state to double-precision floating
18880 point, to avoid roundoff error and other issues.
18881 - Only record path bias information for circuits that have completed
18882 *two* hops. Assuming end-to-end tagging is the attack vector, this
18883 makes us more resilient to ambient circuit failure without any
18884 detection capability loss.
18886 o Minor features (build):
18887 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
18888 dhill. Resolves ticket 6982.
18889 - Compile on win64 using mingw64. Fixes bug 7260; patches from
18891 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
18892 separate error codes; or at least, don't break for that reason.
18893 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
18895 o Build improvements (autotools):
18896 - Warn if building on a platform with an unsigned time_t: there
18897 are too many places where Tor currently assumes that time_t can
18898 hold negative values. We'd like to fix them all, but probably
18900 - Do not report status verbosely from autogen.sh unless the -v flag
18901 is specified. Fixes issue 4664. Patch from Onizuka.
18902 - Detect and reject attempts to build Tor with threading support
18903 when OpenSSL has been compiled without threading support.
18905 - Try to detect if we are ever building on a platform where
18906 memset(...,0,...) does not set the value of a double to 0.0. Such
18907 platforms are permitted by the C standard, though in practice
18908 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
18909 currently support them, but it's better to detect them and fail
18910 than to perform erroneously.
18911 - We no longer warn so much when generating manpages from their
18913 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
18914 the signs of types during autoconf. This is better than our old
18915 approach, which didn't work when cross-compiling.
18917 o Minor features (log messages, warnings):
18918 - Detect when we're running with a version of OpenSSL other than the
18919 one we compiled with. This conflict has occasionally given people
18920 hard-to-track-down errors.
18921 - Warn users who run hidden services on a Tor client with
18922 UseEntryGuards disabled that their hidden services will be
18923 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
18924 attack which motivated Tor to support entry guards in the first
18925 place). Resolves ticket 6889.
18926 - Warn when we are binding low ports when hibernation is enabled;
18927 previously we had warned when we were _advertising_ low ports with
18928 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
18929 - Issue a warning when running with the bufferevents backend enabled.
18930 It's still not stable, and people should know that they're likely
18931 to hit unexpected problems. Closes ticket 9147.
18933 o Minor features (log messages, notices):
18934 - Refactor resolve_my_address() so it returns the method by which we
18935 decided our public IP address (explicitly configured, resolved from
18936 explicit hostname, guessed from interfaces, learned by gethostname).
18937 Now we can provide more helpful log messages when a relay guesses
18938 its IP address incorrectly (e.g. due to unexpected lines in
18939 /etc/hosts). Resolves ticket 2267.
18940 - Track how many "TAP" and "NTor" circuit handshake requests we get,
18941 and how many we complete, and log it every hour to help relay
18942 operators follow trends in network load. Addresses ticket 9658.
18944 o Minor features (log messages, diagnostics):
18945 - If we fail to free a microdescriptor because of bug 7164, log
18946 the filename and line number from which we tried to free it.
18947 - We compute the overhead from passing onionskins back and forth to
18948 cpuworkers, and report it when dumping statistics in response to
18949 SIGUSR1. Supports ticket 7291.
18950 - Add another diagnostic to the heartbeat message: track and log
18951 overhead that TLS is adding to the data we write. If this is
18952 high, we are sending too little data to SSL_write at a time.
18953 Diagnostic for bug 7707.
18954 - Log packaged cell fullness as part of the heartbeat message.
18955 Diagnosis to try to determine the extent of bug 7743.
18956 - Add more detail to a log message about relaxed timeouts, to help
18958 - When learning a fingerprint for a bridge, log its corresponding
18959 transport type. Implements ticket 7896.
18960 - Warn more aggressively when flushing microdescriptors to a
18961 microdescriptor cache fails, in an attempt to mitigate bug 8031,
18962 or at least make it more diagnosable.
18963 - Improve the log message when "Bug/attack: unexpected sendme cell
18964 from client" occurs, to help us track bug 8093.
18965 - Improve debugging output to help track down bug 8185 ("Bug:
18966 outgoing relay cell has n_chan==NULL. Dropping.")
18968 o Minor features (log messages, quieter bootstrapping):
18969 - Log fewer lines at level "notice" about our OpenSSL and Libevent
18970 versions and capabilities when everything is going right. Resolves
18971 part of ticket 6736.
18972 - Omit the first heartbeat log message, because it never has anything
18973 useful to say, and it clutters up the bootstrapping messages.
18974 Resolves ticket 6758.
18975 - Don't log about reloading the microdescriptor cache at startup. Our
18976 bootstrap warnings are supposed to tell the user when there's a
18977 problem, and our bootstrap notices say when there isn't. Resolves
18978 ticket 6759; bugfix on 0.2.2.6-alpha.
18979 - Don't log "I learned some more directory information" when we're
18980 reading cached directory information. Reserve it for when new
18981 directory information arrives in response to a fetch. Resolves
18983 - Don't complain about bootstrapping problems while hibernating.
18984 These complaints reflect a general code problem, but not one
18985 with any problematic effects (no connections are actually
18986 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
18988 o Minor features (testing):
18989 - In our testsuite, create temporary directories with a bit more
18990 entropy in their name to make name collisions less likely. Fixes
18992 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
18993 (P-256) Diffie-Hellman handshakes to src/or/bench.
18994 - Add benchmark functions to test onion handshake performance.
18997 - The DirServer option is now DirAuthority, for consistency with
18998 current naming patterns. You can still use the old DirServer form.
19000 o Minor bugfixes (protocol):
19001 - Fix the handling of a TRUNCATE cell when it arrives while the
19002 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
19003 - When a Tor client gets a "truncated" relay cell, the first byte of
19004 its payload specifies why the circuit was truncated. We were
19005 ignoring this 'reason' byte when tearing down the circuit, resulting
19006 in the controller not being told why the circuit closed. Now we
19007 pass the reason from the truncated cell to the controller. Bugfix
19008 on 0.1.2.3-alpha; fixes bug 7039.
19009 - Fix a misframing issue when reading the version numbers in a
19010 VERSIONS cell. Previously we would recognize [00 01 00 02] as
19011 'version 1, version 2, and version 0x100', when it should have
19012 only included versions 1 and 2. Fixes bug 8059; bugfix on
19013 0.2.0.10-alpha. Reported pseudonymously.
19014 - Make the format and order of STREAM events for DNS lookups
19015 consistent among the various ways to launch DNS lookups. Fixes
19016 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
19018 o Minor bugfixes (syscalls and disk interaction):
19019 - Always check the return values of functions fcntl() and
19020 setsockopt(). We don't believe these are ever actually failing in
19021 practice, but better safe than sorry. Also, checking these return
19022 values should please analysis tools like Coverity. Patch from
19023 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
19024 - Avoid double-closing the listener socket in our socketpair()
19025 replacement (used on Windows) in the case where the addresses on
19026 our opened sockets don't match what we expected. Fixes bug 9400;
19027 bugfix on 0.0.2pre7. Found by Coverity.
19028 - Correctly store microdescriptors and extrainfo descriptors that
19029 include an internal NUL byte. Fixes bug 8037; bugfix on
19030 0.2.0.1-alpha. Bug reported by "cypherpunks".
19031 - If for some reason we fail to write a microdescriptor while
19032 rebuilding the cache, do not let the annotations from that
19033 microdescriptor linger in the cache file, and do not let the
19034 microdescriptor stay recorded as present in its old location.
19035 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
19036 - Use direct writes rather than stdio when building microdescriptor
19037 caches, in an attempt to mitigate bug 8031, or at least make it
19040 o Minor fixes (config options):
19041 - Warn and fail if a server is configured not to advertise any
19042 ORPorts at all. (We need *something* to put in our descriptor,
19043 or we just won't work.)
19044 - Behave correctly when the user disables LearnCircuitBuildTimeout
19045 but doesn't tell us what they would like the timeout to be. Fixes
19046 bug 6304; bugfix on 0.2.2.14-alpha.
19047 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
19048 to start with a triple-underscore so the controller won't touch it.
19049 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
19050 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
19051 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
19052 - When autodetecting the number of CPUs, use the number of available
19053 CPUs in preference to the number of configured CPUs. Inform the
19054 user if this reduces the number of available CPUs. Fixes bug 8002;
19055 bugfix on 0.2.3.1-alpha.
19056 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
19057 - Make it an error when you set EntryNodes but disable UseGuardNodes,
19058 since it will (surprisingly to some users) ignore EntryNodes. Fixes
19059 bug 8180; bugfix on 0.2.3.11-alpha.
19060 - Avoid overflows when the user sets MaxCircuitDirtiness to a
19061 ridiculously high value, by imposing a (ridiculously high) 30-day
19062 maximum on MaxCircuitDirtiness.
19064 o Minor bugfixes (control protocol):
19065 - Stop sending a stray "(null)" in some cases for the server status
19066 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
19068 - The ADDRMAP command can no longer generate an ill-formed error
19069 code on a failed MAPADDRESS. It now says "internal" rather than
19070 an English sentence fragment with spaces in the middle. Bugfix on
19071 Tor 0.2.0.19-alpha.
19073 o Minor bugfixes (clients / edges):
19074 - When we receive a RELAY_END cell with the reason DONE, or with no
19075 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
19076 status as "connection refused". Previously we reported these cases
19077 as success but then immediately closed the connection. Fixes bug
19078 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
19079 - If the guard we choose first doesn't answer, we would try the
19080 second guard, but once we connected to the second guard we would
19081 abandon it and retry the first one, slowing down bootstrapping.
19082 The fix is to treat all our initially chosen guards as acceptable
19083 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
19084 - When choosing which stream on a formerly stalled circuit to wake
19085 first, make better use of the platform's weak RNG. Previously,
19086 we had been using the % ("modulo") operator to try to generate a
19087 1/N chance of picking each stream, but this behaves badly with
19088 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
19091 o Minor bugfixes (path bias detection):
19092 - If the state file's path bias counts are invalid (presumably from a
19093 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
19094 additional checks and log messages to the scaling of Path Bias
19095 counts, in case there still are remaining issues with scaling.
19096 Should help resolve bug 8235.
19097 - Prevent rounding error in path bias counts when scaling
19098 them down, and use the correct scale factor default. Also demote
19099 some path bias related log messages down a level and make others
19100 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
19101 - Remove a source of rounding error during path bias count scaling;
19102 don't count cannibalized circuits as used for path bias until we
19103 actually try to use them; and fix a circuit_package_relay_cell()
19104 warning message about n_chan==NULL. Fixes bug 7802.
19105 - Paste the description for PathBias parameters from the man
19106 page into or.h, so the code documents them too. Fixes bug 7982;
19107 bugfix on 0.2.3.17-beta.
19109 o Minor bugfixes (relays):
19110 - Stop trying to resolve our hostname so often (e.g. every time we
19111 think about doing a directory fetch). Now we reuse the cached
19112 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
19113 and 2410 (bugfix on 0.1.2.2-alpha).
19114 - When examining the list of network interfaces to find our address,
19115 do not consider non-running or disabled network interfaces. Fixes
19116 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
19118 o Minor bugfixes (blocking resistance):
19119 - Only disable TLS session ticket support when running as a TLS
19120 server. Now clients will blend better with regular Firefox
19121 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
19123 o Minor bugfixes (IPv6):
19124 - Use square brackets around IPv6 addresses in numerous places
19125 that needed them, including log messages, HTTPS CONNECT proxy
19126 requests, TransportProxy statefile entries, and pluggable transport
19127 extra-info lines. Fixes bug 7011; patch by David Fifield.
19129 o Minor bugfixes (directory authorities):
19130 - Reject consensus votes with more than 64 known-flags. We aren't even
19131 close to that limit yet, and our code doesn't handle it correctly.
19132 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
19133 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
19134 bugfix on 0.2.0.3-alpha.
19136 o Minor bugfixes (memory leaks):
19137 - Avoid leaking memory if we fail to compute a consensus signature
19138 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
19139 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
19140 on 0.2.1.1-alpha; fixes bug 7816.
19141 - Fix a memory leak during safe-cookie controller authentication.
19142 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
19143 - Free some more still-in-use memory at exit, to make hunting for
19144 memory leaks easier. Resolves bug 7029.
19146 o Minor bugfixes (code correctness):
19147 - Increase the width of the field used to remember a connection's
19148 link protocol version to two bytes. Harmless for now, since the
19149 only currently recognized versions are one byte long. Reported
19150 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
19151 - Fix a crash when debugging unit tests on Windows: deallocate a
19152 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
19153 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
19154 - When detecting the largest possible file descriptor (in order to
19155 close all file descriptors when launching a new program), actually
19156 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
19157 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
19159 - Avoid a crash if we fail to generate an extrainfo descriptor.
19160 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
19161 this is CID 718634.
19162 - Avoid an off-by-one error when checking buffer boundaries when
19163 formatting the exit status of a pluggable transport helper.
19164 This is probably not an exploitable bug, but better safe than
19165 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
19167 - Get rid of a couple of harmless clang warnings, where we compared
19168 enums to ints. These warnings are newly introduced in clang 3.2.
19170 o Minor bugfixes (code cleanliness):
19171 - Avoid use of reserved identifiers in our C code. The C standard
19172 doesn't like us declaring anything that starts with an
19173 underscore, so let's knock it off before we get in trouble. Fix
19174 for bug 1031; bugfix on the first Tor commit.
19175 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
19176 with large values. This situation was untriggered, but nevertheless
19177 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
19178 - Fix an impossible buffer overrun in the AES unit tests. Fixes
19179 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
19180 - Fix handling of rendezvous client authorization types over 8.
19181 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
19182 - Remove a couple of extraneous semicolons that were upsetting the
19183 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
19184 bugfix on 0.2.2.1-alpha.
19185 - When complaining about a client port on a public address, log
19186 which address we're complaining about. Fixes bug 4020; bugfix on
19187 0.2.3.3-alpha. Patch by Tom Fitzhenry.
19189 o Minor bugfixes (log messages, warnings):
19190 - If we encounter a write failure on a SOCKS connection before we
19191 finish our SOCKS handshake, don't warn that we closed the
19192 connection before we could send a SOCKS reply. Fixes bug 8427;
19193 bugfix on 0.1.0.1-rc.
19194 - Fix a directory authority warn caused when we have a large amount
19195 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
19196 - Downgrade "Failed to hand off onionskin" messages to "debug"
19197 severity, since they're typically redundant with the "Your computer
19198 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
19199 - Avoid spurious warnings when configuring multiple client ports of
19200 which only some are nonlocal. Previously, we had claimed that some
19201 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
19204 o Minor bugfixes (log messages, other):
19205 - Fix log messages and comments to avoid saying "GMT" when we mean
19206 "UTC". Fixes bug 6113.
19207 - When rejecting a configuration because we were unable to parse a
19208 quoted string, log an actual error message. Fixes bug 7950; bugfix
19210 - Correctly recognize that [::1] is a loopback address. Fixes
19211 bug 8377; bugfix on 0.2.1.3-alpha.
19212 - Don't log inappropriate heartbeat messages when hibernating: a
19213 hibernating node is _expected_ to drop out of the consensus,
19214 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
19215 bugfix on 0.2.3.1-alpha.
19216 - Eliminate several instances where we use "Nickname=ID" to refer to
19217 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
19218 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
19221 o Minor bugfixes (build):
19222 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
19223 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
19224 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
19226 o Documentation fixes:
19227 - Make the torify manpage no longer refer to tsocks; torify hasn't
19228 supported tsocks since 0.2.3.14-alpha.
19229 - Make the tor manpage no longer reference tsocks.
19230 - Fix the GeoIPExcludeUnknown documentation to refer to
19231 ExcludeExitNodes rather than the currently nonexistent
19232 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
19233 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
19235 - Say "KBytes" rather than "KB" in the man page (for various values
19236 of K), to further reduce confusion about whether Tor counts in
19237 units of memory or fractions of units of memory. Resolves ticket 7054.
19238 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
19239 names match. Fixes bug 7768.
19240 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
19241 message is logged at notice, not at info.
19242 - Clarify the usage and risks of setting the ContactInfo torrc line
19243 for your relay or bridge. Resolves ticket 9854.
19244 - Add anchors to the manpage so we can link to the html version of
19245 the documentation for specific options. Resolves ticket 9866.
19246 - Replace remaining references to DirServer in man page and
19247 log entries. Resolves ticket 10124.
19249 o Removed features:
19250 - Stop exporting estimates of v2 and v3 directory traffic shares
19251 in extrainfo documents. They were unneeded and sometimes inaccurate.
19252 Also stop exporting any v2 directory request statistics. Resolves
19254 - Drop support for detecting and warning about versions of Libevent
19255 before 1.3e. Nothing reasonable ships with them any longer; warning
19256 the user about them shouldn't be needed. Resolves ticket 6826.
19257 - Now that all versions before 0.2.2.x are disallowed, we no longer
19258 need to work around their missing features. Remove a bunch of
19259 compatibility code.
19262 - The tor-tsocks.conf is no longer distributed or installed. We
19263 recommend that tsocks users use torsocks instead. Resolves
19265 - Remove some of the older contents of doc/ as obsolete; move others
19266 to torspec.git. Fixes bug 8965.
19268 o Code simplification:
19269 - Avoid using character buffers when constructing most directory
19270 objects: this approach was unwieldy and error-prone. Instead,
19271 build smartlists of strings, and concatenate them when done.
19272 - Rename "isin" functions to "contains", for grammar. Resolves
19274 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
19275 with the natural logarithm function from the system libm. Resolves
19277 - Start using OpenBSD's implementation of queue.h, so that we don't
19278 need to hand-roll our own pointer and list structures whenever we
19279 need them. (We can't rely on a sys/queue.h, since some operating
19280 systems don't have them, and the ones that do have them don't all
19281 present the same extensions.)
19282 - Start using OpenBSD's implementation of queue.h (originally by
19284 - Enhance our internal sscanf replacement so that we can eliminate
19285 the last remaining uses of the system sscanf. (Though those uses
19286 of sscanf were safe, sscanf itself is generally error prone, so
19287 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
19289 - Replace all calls to snprintf() outside of src/ext with
19290 tor_snprintf(). Also remove the #define to replace snprintf with
19291 _snprintf on Windows; they have different semantics, and all of
19292 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
19295 - Add a wrapper function for the common "log a message with a
19297 - Split the onion.c file into separate modules for the onion queue
19298 and the different handshakes it supports.
19299 - Move the client-side address-map/virtual-address/DNS-cache code
19300 out of connection_edge.c into a new addressmap.c module.
19301 - Move the entry node code from circuitbuild.c to its own file.
19302 - Move the circuit build timeout tracking code from circuitbuild.c
19304 - Source files taken from other packages now reside in src/ext;
19305 previously they were scattered around the rest of Tor.
19306 - Move the generic "config" code into a new file, and have "config.c"
19307 hold only torrc- and state-related code. Resolves ticket 6823.
19308 - Move the core of our "choose a weighted element at random" logic
19309 into its own function, and give it unit tests. Now the logic is
19310 testable, and a little less fragile too.
19311 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
19312 - Move last_reachable and testing_since from routerinfo_t to node_t.
19313 Implements ticket 5529.
19314 - Add replaycache_t structure, functions and unit tests, then refactor
19315 rend_service_introduce() to be more clear to read, improve, debug,
19316 and test. Resolves bug 6177.
19319 - Remove some now-needless code that tried to aggressively flush
19320 OR connections as data was added to them. Since 0.2.0.1-alpha, our
19321 cell queue logic has saved us from the failure mode that this code
19322 was supposed to prevent. Removing this code will limit the number
19323 of baroque control flow paths through Tor's network logic. Reported
19324 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
19325 - Remove unused code for parsing v1 directories and "running routers"
19326 documents. Fixes bug 6887.
19327 - Remove the marshalling/unmarshalling code for sending requests to
19328 cpuworkers over a socket, and instead just send structs. The
19329 recipient will always be the same Tor binary as the sender, so
19330 any encoding is overkill.
19331 - Remove the testing_since field of node_t, which hasn't been used
19332 for anything since 0.2.0.9-alpha.
19333 - Finally remove support for malloc_good_size and malloc_usable_size.
19334 We had hoped that these functions would let us eke a little more
19335 memory out of our malloc implementation. Unfortunately, the only
19336 implementations that provided these functions are also ones that
19337 are already efficient about not overallocation: they never got us
19338 more than 7 or so bytes per allocation. Removing them saves us a
19339 little code complexity and a nontrivial amount of build complexity.
19342 Changes in version 0.2.3.25 - 2012-11-19
19343 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
19344 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
19345 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
19346 programmer, and friend. Unstinting in his dedication to the cause of
19347 freedom, he inspired and helped many of us as we began our work on
19348 anonymity, and inspires us still. Please honor his memory by writing
19349 software to protect people's freedoms, and by helping others to do so.
19351 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
19352 significantly reduced directory overhead (via microdescriptors),
19353 enormous crypto performance improvements for fast relays on new
19354 enough hardware, a new v3 TLS handshake protocol that can better
19355 resist fingerprinting, support for protocol obfuscation plugins (aka
19356 pluggable transports), better scalability for hidden services, IPv6
19357 support for bridges, performance improvements like allowing clients
19358 to skip the first round-trip on the circuit ("optimistic data") and
19359 refilling token buckets more often, a new "stream isolation" design
19360 to isolate different applications on different circuits, and many
19361 stability, security, and privacy fixes.
19363 Major features (v3 directory protocol):
19364 - Clients now use microdescriptors instead of regular descriptors
19365 to build circuits. Microdescriptors are authority-generated
19366 summaries of regular descriptors' contents, designed to change very
19367 rarely (see proposal 158 for details). This feature is designed
19368 to save bandwidth, especially for clients on slow internet
19369 connections. Use "UseMicrodescriptors 0" to disable it.
19370 - Caches now download, cache, and serve microdescriptors, as well
19371 as multiple "flavors" of the consensus, including a flavor that
19372 describes microdescriptors.
19374 o Major features (build hardening):
19375 - Enable gcc and ld hardening by default. Resolves ticket 5210.
19377 o Major features (relay scaling):
19378 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
19379 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
19380 vectorized AES implementations as appropriate. These can be much,
19381 much faster than other AES implementations.
19382 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
19383 implementation. It makes AES_CTR about 7% faster than our old one
19384 (which was about 10% faster than the one OpenSSL used to provide).
19385 Resolves ticket 4526.
19386 - Use OpenSSL's EVP interface for AES encryption, so that all AES
19387 operations can use hardware acceleration (if present). Resolves
19389 - Unconditionally use OpenSSL's AES implementation instead of our
19390 old built-in one. OpenSSL's AES has been better for a while, and
19391 relatively few servers should still be on any version of OpenSSL
19392 that doesn't have good optimized assembly AES.
19394 o Major features (blocking resistance):
19395 - Update TLS cipher list to match Firefox 8 and later. Resolves
19397 - Remove support for clients falsely claiming to support standard
19398 ciphersuites that they can actually provide. As of modern OpenSSL
19399 versions, it's not necessary to fake any standard ciphersuite,
19400 and doing so prevents us from using better ciphersuites in the
19401 future, since servers can't know whether an advertised ciphersuite
19402 is really supported or not. Some hosts -- notably, ones with very
19403 old versions of OpenSSL or where OpenSSL has been built with ECC
19404 disabled -- will stand out because of this change; TBB users should
19405 not be affected. Implements the client side of proposal 198.
19406 - Implement a new handshake protocol (v3) for authenticating Tors to
19407 each other over TLS. It should be more resistant to fingerprinting
19408 than previous protocols, and should require less TLS hacking for
19409 future Tor implementations. Implements proposal 176.
19410 - Allow variable-length padding cells, to disguise the length of
19411 Tor's TLS records. Implements part of proposal 184.
19412 - While we're trying to bootstrap, record how many TLS connections
19413 fail in each state, and report which states saw the most failures
19414 in response to any bootstrap failures. This feature may speed up
19415 diagnosis of censorship events. Implements ticket 3116.
19417 o Major features (pluggable transports):
19418 - Clients and bridges can now be configured to use a separate
19419 "transport" proxy. This approach makes the censorship arms race
19420 easier by allowing bridges to use protocol obfuscation plugins.
19421 Implements proposal 180 (tickets 2841 and 3472).
19423 o Major features (DoS resistance):
19424 - Now that Tor 0.2.0.x is completely deprecated, enable the final
19425 part of "Proposal 110: Avoiding infinite length circuits" by
19426 refusing all circuit-extend requests that do not use a relay_early
19427 cell. This change helps Tor resist a class of denial-of-service
19428 attacks by limiting the maximum circuit length.
19429 - Tear down the circuit if we get an unexpected SENDME cell. Clients
19430 could use this trick to make their circuits receive cells faster
19431 than our flow control would have allowed, or to gum up the network,
19432 or possibly to do targeted memory denial-of-service attacks on
19433 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
19434 from July 2002, before the release of Tor 0.0.0.
19436 o Major features (hidden services):
19437 - Adjust the number of introduction points that a hidden service
19438 will try to maintain based on how long its introduction points
19439 remain in use and how many introductions they handle. Fixes
19441 - Add a "tor2web mode" for clients that want to connect to hidden
19442 services non-anonymously (and possibly more quickly). As a safety
19443 measure to try to keep users from turning this on without knowing
19444 what they are doing, tor2web mode must be explicitly enabled at
19445 compile time, and a copy of Tor compiled to run in tor2web mode
19446 cannot be used as a normal Tor client. Implements feature 2553.
19448 o Major features (IPv6):
19449 - Clients can now connect to private bridges over IPv6. Bridges
19450 still need at least one IPv4 address in order to connect to
19451 other relays. Note that we don't yet handle the case where the
19452 user has two bridge lines for the same bridge (one IPv4, one
19453 IPv6). Implements parts of proposal 186.
19455 o Major features (directory authorities):
19456 - Use a more secure consensus parameter voting algorithm. Now at
19457 least three directory authorities or a majority of them must
19458 vote on a given parameter before it will be included in the
19459 consensus. Implements proposal 178.
19460 - Remove the artificially low cutoff of 20KB to guarantee the Fast
19461 flag. In the past few years the average relay speed has picked
19462 up, and while the "top 7/8 of the network get the Fast flag" and
19463 "all relays with 20KB or more of capacity get the Fast flag" rules
19464 used to have the same result, now the top 7/8 of the network has
19465 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
19467 o Major features (performance):
19468 - Exit nodes now accept and queue data on not-yet-connected streams.
19469 Previously, the client wasn't allowed to send data until the
19470 stream was connected, which slowed down all connections. This
19471 change will enable clients to perform a "fast-start" on streams
19472 and send data without having to wait for a confirmation that the
19473 stream has opened. Patch from Ian Goldberg; implements the server
19474 side of Proposal 174.
19475 - When using an exit relay running 0.2.3.x, clients can now
19476 "optimistically" send data before the exit relay reports that
19477 the stream has opened. This saves a round trip when starting
19478 connections where the client speaks first (such as web browsing).
19479 This behavior is controlled by a consensus parameter (currently
19480 disabled). To turn it on or off manually, use the "OptimisticData"
19481 torrc option. Implements proposal 181; code by Ian Goldberg.
19482 - Add a new TokenBucketRefillInterval option to refill token buckets
19483 more frequently than once per second. This should improve network
19484 performance, alleviate queueing problems, and make traffic less
19485 bursty. Implements proposal 183; closes ticket 3630. Design by
19486 Florian Tschorsch and Björn Scheuermann; implementation by
19488 - Raise the threshold of server descriptors needed (75%) and exit
19489 server descriptors needed (50%) before we will declare ourselves
19490 bootstrapped. This will make clients start building circuits a
19491 little later, but makes the initially constructed circuits less
19492 skewed and less in conflict with further directory fetches. Fixes
19495 o Major features (relays):
19496 - Relays now try regenerating and uploading their descriptor more
19497 frequently if they are not listed in the consensus, or if the
19498 version of their descriptor listed in the consensus is too
19499 old. This fix should prevent situations where a server declines
19500 to re-publish itself because it has done so too recently, even
19501 though the authorities decided not to list its recent-enough
19502 descriptor. Fix for bug 3327.
19504 o Major features (stream isolation):
19505 - You can now configure Tor so that streams from different
19506 applications are isolated on different circuits, to prevent an
19507 attacker who sees your streams as they leave an exit node from
19508 linking your sessions to one another. To do this, choose some way
19509 to distinguish the applications: have them connect to different
19510 SocksPorts, or have one of them use SOCKS4 while the other uses
19511 SOCKS5, or have them pass different authentication strings to the
19512 SOCKS proxy. Then, use the new SocksPort syntax to configure the
19513 degree of isolation you need. This implements Proposal 171.
19514 - There's a new syntax for specifying multiple client ports (such as
19515 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
19516 multiple *Port entries with full addr:port syntax on each.
19517 The old *ListenAddress format is still supported, but you can't
19518 mix it with the new *Port syntax.
19520 o Major features (bufferevents):
19521 - Tor can now optionally build with the "bufferevents" buffered IO
19522 backend provided by Libevent 2. To use this feature, make sure you
19523 have the latest possible version of Libevent, and pass the
19524 --enable-bufferevents flag to configure when building Tor from
19525 source. This feature will make our networking code more flexible,
19526 let us stack layers on each other, and let us use more efficient
19527 zero-copy transports where available.
19528 - Add experimental support for running on Windows with IOCP and no
19529 kernel-space socket buffers. This feature is controlled by a new
19530 "UserspaceIOCPBuffers" config option (off by default), which has
19531 no effect unless Tor has been built with bufferevents enabled,
19532 you're running on Windows, and you've set "DisableIOCP 0". In the
19533 long run, this may help solve or mitigate bug 98.
19535 o Major features (path selection):
19536 - The EntryNodes option can now include country codes like {de} or IP
19537 addresses or network masks. Previously we had disallowed these
19538 options because we didn't have an efficient way to keep the list up
19539 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
19542 o Major features (port forwarding):
19543 - Add support for automatic port mapping on the many home routers
19544 that support NAT-PMP or UPnP. To build the support code, you'll
19545 need to have the libnatpnp library and/or the libminiupnpc library,
19546 and you'll need to enable the feature specifically by passing
19547 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
19548 it on, use the new PortForwarding option.
19550 o Major features (logging):
19551 - Add a new 'Heartbeat' log message type to periodically log a message
19552 describing Tor's status at level Notice. This feature is meant for
19553 operators who log at notice, and want to make sure that their Tor
19554 server is still working. Implementation by George Kadianakis.
19555 - Make logging resolution configurable with a new LogTimeGranularity
19556 option, and change the default from 1 millisecond to 1 second.
19557 Implements enhancement 1668.
19559 o Major features (other):
19560 - New "DisableNetwork" config option to prevent Tor from launching any
19561 connections or accepting any connections except on a control port.
19562 Bundles and controllers can set this option before letting Tor talk
19563 to the rest of the network, for example to prevent any connections
19564 to a non-bridge address. Packages like Orbot can also use this
19565 option to instruct Tor to save power when the network is off.
19566 - Try to use system facilities for enumerating local interface
19567 addresses, before falling back to our old approach (which was
19568 binding a UDP socket, and calling getsockname() on it). That
19569 approach was scaring OS X users whose draconian firewall
19570 software warned about binding to UDP sockets regardless of
19571 whether packets were sent. Now we try to use getifaddrs(),
19572 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
19573 system supports. Resolves ticket 1827.
19574 - Add experimental support for a "defaults" torrc file to be parsed
19575 before the regular torrc. Torrc options override the defaults file's
19576 options in the same way that the command line overrides the torrc.
19577 The SAVECONF controller command saves only those options which
19578 differ between the current configuration and the defaults file. HUP
19579 reloads both files. Implements task 4552.
19581 o New directory authorities:
19582 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
19583 authority. Closes ticket 5749.
19585 o Security/privacy fixes:
19586 - Avoid read-from-freed-memory and double-free bugs that could occur
19587 when a DNS request fails while launching it. Fixes bug 6480;
19588 bugfix on 0.2.0.1-alpha.
19589 - Reject any attempt to extend to an internal address. Without
19590 this fix, a router could be used to probe addresses on an internal
19591 network to see whether they were accepting connections. Fixes bug
19592 6710; bugfix on 0.0.8pre1.
19593 - Close any connection that sends unrecognized junk before the TLS
19594 handshake. Solves an issue noted in bug 4369.
19595 - The advertised platform of a relay now includes only its operating
19596 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
19597 its service pack level (for Windows) or its CPU architecture
19598 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
19599 can insert an extra string in the platform line by setting the
19600 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
19601 - Disable TLS session tickets. OpenSSL's implementation was giving
19602 our TLS session keys the lifetime of our TLS context objects, when
19603 perfect forward secrecy would want us to discard anything that
19604 could decrypt a link connection as soon as the link connection
19605 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
19606 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
19607 - Tor tries to wipe potentially sensitive data after using it, so
19608 that if some subsequent security failure exposes Tor's memory,
19609 the damage will be limited. But we had a bug where the compiler
19610 was eliminating these wipe operations when it decided that the
19611 memory was no longer visible to a (correctly running) program,
19612 hence defeating our attempt at defense in depth. We fix that
19613 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
19614 is unlikely to optimize away. Future versions of Tor may use
19615 a less ridiculously heavy approach for this. Fixes bug 7352.
19616 Reported in an article by Andrey Karpov.
19618 o Major bugfixes (crashes and asserts):
19619 - Avoid a pair of double-free and use-after-mark bugs that can
19620 occur with certain timings in canceled and re-received DNS
19621 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
19622 - Fix a denial of service attack by which any directory authority
19623 could crash all the others, or by which a single v2 directory
19624 authority could crash everybody downloading v2 directory
19625 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
19626 - Fix an assert that directory authorities could trigger on sighup
19627 during some configuration state transitions. We now don't treat
19628 it as a fatal error when the new descriptor we just generated in
19629 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
19630 - Avoid segfault when starting up having run with an extremely old
19631 version of Tor and parsing its state file. Fixes bug 6801; bugfix
19634 o Major bugfixes (clients):
19635 - If we are unable to find any exit that supports our predicted ports,
19636 stop calling them predicted, so that we don't loop and build
19637 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
19638 which introduced predicted ports.
19639 - Check at each new consensus whether our entry guards were picked
19640 long enough ago that we should rotate them. Previously, we only
19641 did this check at startup, which could lead to us holding a guard
19642 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
19643 - When fetching a bridge descriptor from a bridge authority,
19644 always do so anonymously, whether we have been able to open
19645 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
19646 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
19647 but we'll need to wait for bug 6010 before it's actually usable.
19649 o Major bugfixes (directory voting):
19650 - Check more thoroughly to prevent a rogue authority from
19651 double-voting on any consensus directory parameter. Previously,
19652 authorities would crash in this case if the total number of
19653 votes for any parameter exceeded the number of active voters,
19654 but would let it pass otherwise. Partially fixes bug 5786; bugfix
19656 - When computing weight parameters, behave more robustly in the
19657 presence of a bad bwweightscale value. Previously, the authorities
19658 would crash if they agreed on a sufficiently broken weight_scale
19659 value; now, they use a reasonable default and carry on. Fixes the
19660 rest of bug 5786; bugfix on 0.2.2.17-alpha.
19661 - If authorities are unable to get a v2 consensus document from other
19662 directory authorities, they no longer fall back to fetching
19663 them from regular directory caches. Fixes bug 5635; bugfix on
19664 0.2.2.26-beta, where routers stopped downloading v2 consensus
19665 documents entirely.
19667 o Major bugfixes (relays):
19668 - Fix a bug handling SENDME cells on nonexistent streams that could
19669 result in bizarre window values. Report and patch contributed
19670 pseudonymously. Fixes part of bug 6271. This bug was introduced
19671 before the first Tor release, in svn commit r152.
19672 - Don't update the AccountingSoftLimitHitAt state file entry whenever
19673 tor gets started. This prevents a wrong average bandwidth
19674 estimate, which would cause relays to always start a new accounting
19675 interval at the earliest possible moment. Fixes bug 2003; bugfix
19676 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
19677 immensely in tracking this bug down.
19678 - Fix a possible crash bug when checking for deactivated circuits
19679 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
19680 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
19681 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
19682 connections. This change should allow busy exit relays to stop
19683 running out of available sockets as quickly. Fixes bug 4950;
19684 bugfix on 0.2.2.26-beta.
19686 o Major bugfixes (blocking resistance):
19687 - Bridges no longer include their address in NETINFO cells on outgoing
19688 OR connections, to allow them to blend in better with clients.
19689 Removes another avenue for enumerating bridges. Reported by
19690 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
19691 cells were introduced.
19692 - Warn the user when HTTPProxy, but no other proxy type, is
19693 configured. This can cause surprising behavior: it doesn't send
19694 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
19695 directory traffic only. Resolves ticket 4663.
19697 o Major bugfixes (hidden services):
19698 - Improve hidden service robustness: when an attempt to connect to
19699 a hidden service ends, be willing to refetch its hidden service
19700 descriptors from each of the HSDir relays responsible for them
19701 immediately. Previously, we would not consider refetching the
19702 service's descriptors from each HSDir for 15 minutes after the last
19703 fetch, which was inconvenient if the hidden service was not running
19704 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
19705 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
19706 They used to check that the timestamp was within 30 minutes
19707 of their system clock, so they could cap the size of their
19708 replay-detection cache, but that approach unnecessarily refused
19709 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
19710 the v3 intro-point protocol (the first one which sent a timestamp
19711 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
19712 - When one of a hidden service's introduction points appears to be
19713 unreachable, stop trying it. Previously, we would keep trying
19714 to build circuits to the introduction point until we lost the
19715 descriptor, usually because the user gave up and restarted Tor.
19716 Fixes part of bug 3825.
19718 o Changes to default torrc file:
19719 - Stop listing "socksport 9050" in torrc.sample. We open a socks
19720 port on 9050 by default anyway, so this should not change anything
19722 - Stop mentioning the deprecated *ListenAddress options in
19723 torrc.sample. Fixes bug 5438.
19724 - Document unit of bandwidth-related options in sample torrc.
19726 - Fix broken URLs in the sample torrc file, and tell readers about
19727 the OutboundBindAddress, ExitPolicyRejectPrivate, and
19728 PublishServerDescriptor options. Addresses bug 4652.
19730 o Minor features (directory authorities):
19731 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
19732 change when the authority is deciding whether to accept a newly
19733 uploaded descriptor. Implements ticket 6423.
19734 - Directory authorities are now a little more lenient at accepting
19735 older router descriptors, or newer router descriptors that don't
19736 make big changes. This should help ameliorate past and future
19737 issues where routers think they have uploaded valid descriptors,
19738 but the authorities don't think so. Fix for ticket 2479.
19739 - Authority operators can now vote for all relays in a given
19740 set of countries to be BadDir/BadExit/Invalid/Rejected.
19741 - Provide two consensus parameters (FastFlagMinThreshold and
19742 FastFlagMaxThreshold) to control the range of allowable bandwidths
19743 for the Fast directory flag. These allow authorities to run
19744 experiments on appropriate requirements for being a "Fast" node.
19745 The AuthDirFastGuarantee config value still applies. Implements
19748 o Minor features (bridges / bridge authorities):
19749 - Make bridge SSL certificates a bit more stealthy by using random
19750 serial numbers, in the same fashion as OpenSSL when generating
19751 self-signed certificates. Implements ticket 4584.
19752 - Tag a bridge's descriptor as "never to be sent unencrypted".
19753 This shouldn't matter, since bridges don't open non-anonymous
19754 connections to the bridge authority and don't allow unencrypted
19755 directory connections from clients, but we might as well make
19756 sure. Closes bug 5139.
19757 - The Bridge Authority now writes statistics on how many bridge
19758 descriptors it gave out in total, and how many unique descriptors
19759 it gave out. It also lists how often the most and least commonly
19760 fetched descriptors were given out, as well as the median and
19761 25th/75th percentile. Implements tickets 4200 and 4294.
19763 o Minor features (IPv6):
19764 - Make the code that clients use to detect an address change be
19765 IPv6-aware, so that it won't fill clients' logs with error
19766 messages when trying to get the IPv4 address of an IPv6
19767 connection. Implements ticket 5537.
19768 - Relays now understand an IPv6 address when they get one from a
19769 directory server. Resolves ticket 4875.
19771 o Minor features (hidden services):
19772 - Expire old or over-used hidden service introduction points.
19773 Required by fix for bug 3460.
19774 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
19775 public key replay-detection cache from 60 minutes to 5 minutes. This
19776 replay-detection cache is now used only to detect multiple
19777 INTRODUCE2 cells specifying the same rendezvous point, so we can
19778 avoid launching multiple simultaneous attempts to connect to it.
19779 - When a hidden service's introduction point times out, consider
19780 trying it again during the next attempt to connect to the
19781 HS. Previously, we would not try it again unless a newly fetched
19782 descriptor contained it. Required by fixes for bugs 1297 and 3825.
19784 o Minor features (relays):
19785 - Relays now include a reason for regenerating their descriptors
19786 in an HTTP header when uploading to the authorities. This will
19787 make it easier to debug descriptor-upload issues in the future.
19788 - Turn on directory request statistics by default and include them in
19789 extra-info descriptors. Don't break if we have no GeoIP database.
19790 - Replace files in stats/ rather than appending to them. Now that we
19791 include statistics in extra-info descriptors, it makes no sense to
19792 keep old statistics forever. Implements ticket 2930.
19793 - Relays that set "ConnDirectionStatistics 1" write statistics on the
19794 bidirectional use of connections to disk every 24 hours.
19795 - Add a GeoIP file digest to the extra-info descriptor. Implements
19798 o Minor features (new config options):
19799 - New config option "DynamicDHGroups" (disabled by default) provides
19800 each bridge with a unique prime DH modulus to be used during
19801 SSL handshakes. This option attempts to help against censors
19802 who might use the Apache DH modulus as a static identifier for
19803 bridges. Addresses ticket 4548.
19804 - New config option "DisableDebuggerAttachment" (on by default)
19805 to prevent basic debugging attachment attempts by other processes.
19806 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
19807 - Ordinarily, Tor does not count traffic from private addresses (like
19808 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
19809 There is now a new option, CountPrivateBandwidth, to disable this
19810 behavior. Patch from Daniel Cagara.
19812 o Minor features (different behavior for old config options):
19813 - Allow MapAddress directives to specify matches against super-domains,
19814 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
19815 Implements issue 933.
19816 - Don't disable the DirPort when we cannot exceed our AccountingMax
19817 limit during this interval because the effective bandwidthrate is
19818 low enough. This is useful in a situation where AccountMax is only
19819 used as an additional safeguard or to provide statistics.
19820 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
19821 implements ticket 3439.
19822 - When configuring a large set of nodes in EntryNodes, and there are
19823 enough of them listed as Guard so that we don't need to consider
19824 the non-guard entries, prefer the ones listed with the Guard flag.
19825 - If you set the NumCPUs option to 0, Tor will now try to detect how
19826 many CPUs you have. This is the new default behavior.
19827 - The NodeFamily option -- which let you declare that you want to
19828 consider nodes to be part of a family whether they list themselves
19829 that way or not -- now allows IP address ranges and country codes.
19831 o Minor features (new command-line config behavior):
19832 - Slightly change behavior of "list" options (that is, config
19833 options that can appear more than once) when they appear both in
19834 torrc and on the command line. Previously, the command-line options
19835 would be appended to the ones from torrc. Now, the command-line
19836 options override the torrc options entirely. This new behavior
19837 allows the user to override list options (like exit policies and
19838 ports to listen on) from the command line, rather than simply
19839 appending to the list.
19840 - You can get the old (appending) command-line behavior for "list"
19841 options by prefixing the option name with a "+".
19842 - You can remove all the values for a "list" option from the command
19843 line without adding any new ones by prefixing the option name
19846 o Minor features (controller, new events):
19847 - Extend the control protocol to report flags that control a circuit's
19848 path selection in CIRC events and in replies to 'GETINFO
19849 circuit-status'. Implements part of ticket 2411.
19850 - Extend the control protocol to report the hidden service address
19851 and current state of a hidden-service-related circuit in CIRC
19852 events and in replies to 'GETINFO circuit-status'. Implements part
19854 - Include the creation time of a circuit in CIRC and CIRC2
19855 control-port events and the list produced by the 'GETINFO
19856 circuit-status' control-port command.
19857 - Add a new CONF_CHANGED event so that controllers can be notified
19858 of any configuration changes made by other controllers, or by the
19859 user. Implements ticket 1692.
19860 - Add a new SIGNAL event to the controller interface so that
19861 controllers can be notified when Tor handles a signal. Resolves
19862 issue 1955. Patch by John Brooks.
19864 o Minor features (controller, new getinfo options):
19865 - Expose our view of whether we have gone dormant to the controller,
19866 via a new "GETINFO dormant" value. Torbutton and other controllers
19867 can use this to avoid doing periodic requests through Tor while
19868 it's dormant (bug 4718). Resolves ticket 5954.
19869 - Add a new GETINFO option to get total bytes read and written. Patch
19870 from pipe, revised by atagar. Resolves ticket 2345.
19871 - Implement new GETINFO controller fields to provide information about
19872 the Tor process's pid, euid, username, and resource limits.
19874 o Minor features (controller, other):
19875 - Allow controllers to request an event notification whenever a
19876 circuit is cannibalized or its purpose is changed. Implements
19877 part of ticket 3457.
19878 - Use absolute path names when reporting the torrc filename in the
19879 control protocol, so a controller can more easily find the torrc
19880 file. Resolves bug 1101.
19881 - When reporting the path to the cookie file to the controller,
19882 give an absolute path. Resolves ticket 4881.
19884 o Minor features (log messages):
19885 - Add more information to a log statement that might help track down
19886 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
19887 non-IP address" messages (or any Bug messages, for that matter!),
19888 please let us know about it.
19889 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
19890 EntryNodes will have no effect. Resolves issue 2571.
19891 - Try to make the introductory warning message that Tor prints on
19892 startup more useful for actually finding help and information.
19893 Resolves ticket 2474.
19894 - When the system call to create a listener socket fails, log the
19895 error message explaining why. This may help diagnose bug 4027.
19897 o Minor features (other):
19898 - When we fail to initialize Libevent, retry with IOCP disabled so we
19899 don't need to turn on multi-threading support in Libevent, which in
19900 turn requires a working socketpair(). This is a workaround for bug
19901 4457, which affects Libevent versions from 2.0.1-alpha through
19903 - When starting as root and then changing our UID via the User
19904 control option, and we have a ControlSocket configured, make sure
19905 that the ControlSocket is owned by the same account that Tor will
19906 run under. Implements ticket 3421; fix by Jérémy Bobbio.
19907 - Accept attempts to include a password authenticator in the
19908 handshake, as supported by SOCKS5. This handles SOCKS clients that
19909 don't know how to omit a password when authenticating. Resolves
19911 - Check for and recover from inconsistency in the microdescriptor
19912 cache. This will make it harder for us to accidentally free a
19913 microdescriptor without removing it from the appropriate data
19914 structures. Fixes issue 3135; issue noted by "wanoskarnet".
19915 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
19917 o Minor bugfixes (code security):
19918 - Prevent a null-pointer dereference when receiving a data cell
19919 for a nonexistent stream when the circuit in question has an
19920 empty deliver window. We don't believe this is triggerable,
19921 since we don't currently allow deliver windows to become empty,
19922 but the logic is tricky enough that it's better to make the code
19923 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
19924 - Fix a (harmless) integer overflow in cell statistics reported by
19925 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
19926 - Fix our implementation of crypto_random_hostname() so it can't
19927 overflow on ridiculously large inputs. (No Tor version has ever
19928 provided this kind of bad inputs, but let's be correct in depth.)
19929 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
19930 - Add a (probably redundant) memory clear between iterations of
19931 the router status voting loop, to prevent future coding errors
19932 where data might leak between iterations of the loop. Resolves
19935 o Minor bugfixes (wrapper functions):
19936 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
19937 utility function used in the control-port code). This shouldn't
19938 ever happen unless Tor is completely out of memory, but if it did
19939 happen and Tor somehow recovered from it, Tor could have sent a log
19940 message to a control port in the middle of a reply to a controller
19941 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
19942 - Fix some (not actually triggerable) buffer size checks in usage of
19943 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
19945 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
19946 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
19947 - Enforce correct return behavior of tor_vsscanf() when the '%%'
19948 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
19949 - Make our replacement implementation of strtok_r() compatible with
19950 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
19951 bugfix on 0.2.2.1-alpha.
19952 - Find more places in the code that should have been testing for
19953 invalid sockets using the SOCKET_OK macro. Required for a fix
19954 for bug 4533. Bugfix on 0.2.2.28-beta.
19956 o Minor bugfixes (code correctness):
19957 - Check return value of fputs() when writing authority certificate
19958 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
19959 - When building Tor on Windows with -DUNICODE (not default), ensure
19960 that error messages, filenames, and DNS server names are always
19961 NUL-terminated when we convert them to a single-byte encoding.
19962 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
19963 - Fix a memory leak when trying to launch a DNS request when the
19964 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
19966 - Correct file sizes when reading binary files on Cygwin, to avoid
19967 a bug where Tor would fail to read its state file. Fixes bug 6844;
19968 bugfix on 0.1.2.7-alpha.
19969 - Make sure to set *socket_error in all error cases in
19970 connection_connect(), so it can't produce a warning about
19971 errno being zero from errno_to_orconn_end_reason(). Bugfix on
19972 0.2.1.1-alpha; resolves ticket 6028.
19973 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
19974 bug 4532; found by "troll_un".
19976 o Minor bugfixes (clients):
19977 - Allow one-hop directory-fetching circuits the full "circuit build
19978 timeout" period, rather than just half of it, before failing them
19979 and marking the relay down. This fix should help reduce cases where
19980 clients declare relays (or worse, bridges) unreachable because
19981 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
19982 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
19984 - Ensure we don't cannibalize circuits that are longer than three hops
19985 already, so we don't end up making circuits with 5 or more
19986 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
19987 0.1.0.1-rc which introduced cannibalization.
19989 o Minor bugfixes (relays):
19990 - Don't publish a new relay descriptor when we reload our onion key,
19991 unless the onion key has actually changed. Fixes bug 3263 and
19992 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
19993 - When relays refuse a "create" cell because their queue of pending
19994 create cells is too big (typically because their cpu can't keep up
19995 with the arrival rate), send back reason "resource limit" rather
19996 than reason "internal", so network measurement scripts can get a
19997 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
19998 - Exit nodes don't need to fetch certificates for authorities that
19999 they don't recognize; only directory authorities, bridges,
20000 and caches need to do that. Fixes part of bug 2297; bugfix on
20003 o Minor bugfixes (directory authority / mirrors):
20004 - Avoid O(n^2) performance characteristics when parsing a large
20005 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
20006 - Authorities no longer include any router in their microdescriptor
20007 consensuses for which they couldn't generate or agree on a
20008 microdescriptor. Fixes the second piece of bug 6404; fix on
20010 - When checking for requested signatures on the latest consensus
20011 before serving it to a client, make sure to check the right
20012 consensus flavor. Bugfix on 0.2.2.6-alpha.
20013 - Fix an edge case where TestingTorNetwork is set but the authorities
20014 and relays all have an uptime of zero, so the private Tor network
20015 could briefly lack support for hidden services. Fixes bug 3886;
20016 bugfix on 0.2.2.18-alpha.
20017 - Directory caches no longer refuse to clean out descriptors because
20018 of missing v2 networkstatus documents, unless they're configured
20019 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
20020 0.2.2.26-beta. Patch by Daniel Bryg.
20021 - Don't serve or accept v2 hidden service descriptors over a relay's
20022 DirPort. It's never correct to do so, and disabling it might
20023 make it more annoying to exploit any bugs that turn up in the
20024 descriptor-parsing code. Fixes bug 7149.
20026 o Minor bugfixes (hidden services, client-side):
20027 - Assert that hidden-service-related operations are not performed
20028 using single-hop circuits. Previously, Tor would assert that
20029 client-side streams are not attached to single-hop circuits,
20030 but not that other sensitive operations on the client and service
20031 side are not performed using single-hop circuits. Fixes bug 3332;
20033 - Avoid undefined behavior when parsing the list of supported
20034 rendezvous/introduction protocols in a hidden service descriptor.
20035 Previously, Tor would have confused (as-yet-unused) protocol version
20036 numbers greater than 32 with lower ones on many platforms. Fixes
20037 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
20038 - Don't close hidden service client circuits which have almost
20039 finished connecting to their destination when they reach
20040 the normal circuit-build timeout. Previously, we would close
20041 introduction circuits which are waiting for an acknowledgement
20042 from the introduction point, and rendezvous circuits which have
20043 been specified in an INTRODUCE1 cell sent to a hidden service,
20044 after the normal CBT. Now, we mark them as 'timed out', and launch
20045 another rendezvous attempt in parallel. This behavior change can
20046 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
20047 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
20049 o Minor bugfixes (hidden services, service-side):
20050 - Don't close hidden-service-side rendezvous circuits when they
20051 reach the normal circuit-build timeout. This behavior change can
20052 be disabled using the new
20053 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
20054 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
20055 - Don't launch more than 10 service-side introduction-point circuits
20056 for a hidden service in five minutes. Previously, we would consider
20057 launching more introduction-point circuits if at least one second
20058 had passed without any introduction-point circuits failing. Fixes
20059 bug 4607; bugfix on 0.0.7pre1.
20061 o Minor bugfixes (config option behavior):
20062 - If the user tries to set MyFamily on a bridge, refuse to
20063 do so, and warn about the security implications. Fixes bug 4657;
20064 bugfix on 0.2.0.3-alpha.
20065 - The "--quiet" and "--hush" options now apply not only to Tor's
20066 behavior before logs are configured, but also to Tor's behavior in
20067 the absence of configured logs. Fixes bug 3550; bugfix on
20069 - Change the AllowDotExit rules so they should actually work.
20070 We now enforce AllowDotExit only immediately after receiving an
20071 address via SOCKS or DNSPort: other sources are free to provide
20072 .exit addresses after the resolution occurs. Fixes bug 3940;
20073 bugfix on 0.2.2.1-alpha.
20074 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
20075 don't depend on the consensus parameters or compute adaptive
20076 timeouts when it is disabled. Fixes bug 5049; bugfix on
20078 - After we pick a directory mirror, we would refuse to use it if
20079 it's in our ExcludeExitNodes list, resulting in mysterious failures
20080 to bootstrap for people who just wanted to avoid exiting from
20081 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
20082 - When told to add a bridge with the same digest as a preexisting
20083 bridge but a different addr:port, change the addr:port as
20084 requested. Previously we would not notice the change. Fixes half
20085 of bug 5603; fix on 0.2.2.26-beta.
20087 o Minor bugfixes (controller):
20088 - Allow manual 'authenticate' commands to the controller interface
20089 from netcat (nc) as well as telnet. We were rejecting them because
20090 they didn't come with the expected whitespace at the end of the
20091 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
20092 - Report a real bootstrap problem to the controller on router
20093 identity mismatch. Previously we just said "foo", which probably
20094 made a lot of sense at the time. Fixes bug 4169; bugfix on
20096 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
20097 option is set to 0 (which Vidalia version 0.2.16 now does when
20098 a SAVECONF attempt fails), perform other actions that SIGHUP
20099 usually causes (like reopening the logs). Fixes bug 5095; bugfix
20101 - Correctly handle checking the permissions on the parent
20102 directory of a control socket in the root directory. Bug found
20103 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
20105 - End AUTHCHALLENGE error messages (in the control protocol) with
20106 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
20108 o Minor bugfixes (network reading/writing):
20109 - Disable writing on marked-for-close connections when they are
20110 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
20111 bug 5263; bugfix on 0.0.2pre13, where we first added a special
20112 case for flushing marked connections.
20113 - Make sure that there are no unhandled pending TLS errors before
20114 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
20115 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
20116 Bugfix on 0.1.0.5-rc; fixes bug 4528.
20117 - Detect SSL handshake even when the initial attempt to write the
20118 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
20119 - If the client fails to set a reasonable set of ciphersuites
20120 during its v2 handshake renegotiation, allow the renegotiation to
20121 continue nevertheless (i.e. send all the required certificates).
20122 Fixes bug 4591; bugfix on 0.2.0.20-rc.
20124 o Minor bugfixes (other):
20125 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
20126 resource exhaustion, so that clients can adjust their load to
20127 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
20128 started using END_STREAM_REASON_RESOURCELIMIT.
20129 - Don't check for whether the address we're using for outbound
20130 connections has changed until after the outbound connection has
20131 completed. On Windows, getsockname() doesn't succeed until the
20132 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
20133 - Don't hold a Windows file handle open for every file mapping;
20134 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
20136 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
20137 bugfix on 0.2.1.10-alpha.
20138 - If we fail to write a microdescriptor to the disk cache, do not
20139 continue replacing the old microdescriptor file. Fixes bug 2954;
20140 bugfix on 0.2.2.6-alpha.
20142 o Minor bugfixes (log messages, path selection):
20143 - Downgrade "set buildtimeout to low value" messages to "info"
20144 severity; they were never an actual problem, there was never
20145 anything reasonable to do about them, and they tended to spam logs
20146 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
20147 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
20148 more information to it, so that we can track it down in case it
20149 returns again. Mitigates bug 5235.
20150 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
20151 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
20152 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
20153 - Issue a log message if a guard completes less than 40% of your
20154 circuits. Threshold is configurable by torrc option
20155 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
20156 additional, off-by-default code to disable guards which fail too
20157 many circuits. Addresses ticket 5458.
20159 o Minor bugfixes (log messages, client):
20160 - Downgrade "Got a certificate, but we already have it" log messages
20161 from warning to info, except when we're a dirauth. Fixes bug 5238;
20162 bugfix on 0.2.1.7-alpha.
20163 - Fix the log message describing how we work around discovering
20164 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
20165 4837; bugfix on 0.2.2.9-alpha.
20166 - When logging about a disallowed .exit name, do not also call it
20167 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
20168 - Fix a log message suggesting that people contact a non-existent
20169 email address. Fixes bug 3448.
20170 - Rephrase the log message emitted if the TestSocks check is
20171 successful. Patch from Fabian Keil; fixes bug 4094.
20172 - Log (at debug level) whenever a circuit's purpose is changed.
20173 - Log SSL state transitions at log level DEBUG, log domain
20174 HANDSHAKE. This can be useful for debugging censorship events.
20175 Implements ticket 3264.
20176 - We now log which torrc file we're using on startup. Implements
20178 - Rate-limit log messages when asked to connect anonymously to
20179 a private address. When these hit, they tended to hit fast and
20180 often. Also, don't bother trying to connect to addresses that we
20181 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
20182 reply makes us think we have been lied to, even when the address the
20183 client tried to connect to was "localhost." Resolves ticket 2822.
20185 o Minor bugfixes (log messages, non-client):
20186 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
20187 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
20188 - Don't log that we have "decided to publish new relay descriptor"
20189 unless we are actually publishing a descriptor. Fixes bug 3942;
20190 bugfix on 0.2.2.28-beta.
20191 - Log which authority we're missing votes from when we go to fetch
20192 them from the other auths.
20193 - Replace "Sending publish request" log messages with "Launching
20194 upload", so that they no longer confusingly imply that we're
20195 sending something to a directory we might not even be connected
20196 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
20197 - Warn when Tor is configured to use accounting in a way that can
20198 link a hidden service to some other hidden service or public
20199 address. Resolves ticket 6490.
20200 - Fix a minor formatting issue in one of tor-gencert's error messages.
20204 - Update to the latest version of the tinytest unit testing framework.
20205 This includes a couple of bugfixes that can be relevant for
20206 running forked unit tests on Windows, and removes all reserved
20208 - Avoid a false positive in the util/threads unit test by increasing
20209 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
20210 - Make it possible to set the TestingTorNetwork configuration
20211 option using AlternateDirAuthority and AlternateBridgeAuthority
20212 as an alternative to setting DirServer. Addresses ticket 6377.
20213 - Add a unit test for the environment_variable_names_equal() function.
20214 - A wide variety of new unit tests by Esteban Manchado Velázquez.
20215 - Numerous new unit tests for functions in util.c and address.c by
20217 - The long-disabled benchmark tests are now split into their own
20218 ./src/test/bench binary.
20219 - The benchmark tests can now use more accurate timers than
20220 gettimeofday() when such timers are available.
20221 - Use tt_assert(), not tor_assert(), for checking for test failures.
20222 This makes the unit tests more able to go on in the event that
20225 o Build improvements:
20226 - Use the dead_strip option when building Tor on OS X. This reduces
20227 binary size by almost 19% when linking openssl and libevent
20228 statically, which we do for Tor Browser Bundle.
20229 - Provide a better error message about possible OSX Asciidoc failure
20230 reasons. Fixes bug 6436.
20231 - Detect attempts to build Tor on (as yet hypothetical) versions
20232 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
20233 fix for bug 4533. Bugfix on 0.2.2.28-beta.
20234 - On Windows, we now define the _WIN32_WINNT macros only if they
20235 are not already defined. This lets the person building Tor decide,
20236 if they want, to require a later version of Windows.
20237 - Our autogen.sh script now uses autoreconf to launch autoconf,
20238 automake, and so on. This is more robust against some of the failure
20239 modes associated with running the autotools pieces on their own.
20240 - Running "make version" now displays the version of Tor that
20241 we're about to build. Idea from katmagic; resolves issue 4400.
20242 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
20243 on 0.2.2.4-alpha; fixes bug 3427.
20244 - New --enable-static-tor configure option for building Tor as
20245 statically as possible. Idea, general hackery and thoughts from
20246 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
20248 - Limited, experimental support for building with nmake and MSVC.
20250 o Build requirements:
20251 - Building Tor with bufferevent support now requires Libevent
20252 2.0.13-stable or later. Previous versions of Libevent had bugs in
20253 SSL-related bufferevents and related issues that would make Tor
20254 work badly with bufferevents. Requiring 2.0.13-stable also allows
20255 Tor with bufferevents to take advantage of Libevent APIs
20256 introduced after 2.0.8-rc.
20257 - Our build system requires automake 1.6 or later to create the
20258 Makefile.in files. Previously, you could have used 1.4.
20259 This only affects developers and people building Tor from git;
20260 people who build Tor from the source distribution without changing
20261 the Makefile.am files should be fine.
20262 - Detect when we try to build on a platform that doesn't define
20263 AF_UNSPEC to 0. We don't work there, so refuse to compile.
20265 o Build fixes (compile/link):
20266 - Format more doubles with %f, not %lf. Patch from grarpamp to make
20267 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
20269 - When building with --enable-static-tor on OpenBSD, do not
20270 erroneously attempt to link -lrt. Fixes bug 5103.
20271 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
20272 that IPv6 stuff will compile on MSVC, and compilation issues
20273 will be easier to track down. Fixes bug 5861.
20274 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
20275 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
20276 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
20277 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
20279 o Build fixes (other):
20280 - Use the _WIN32 macro throughout our code to detect Windows.
20281 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
20283 - Properly handle the case where the build-tree is not the same
20284 as the source tree when generating src/common/common_sha1.i,
20285 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
20286 bugfix on 0.2.0.1-alpha.
20287 - During configure, search for library containing cos function as
20288 libm lives in libcore on some platforms (BeOS/Haiku). Linking
20289 against libm was hard-coded before. Fixes the first part of bug
20290 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
20292 - Prevent a false positive from the check-spaces script, by disabling
20293 the "whitespace between function name and (" check for functions
20296 o Packaging (RPM) changes:
20297 - Update our default RPM spec files to work with mock and rpmbuild
20298 on RHEL/Fedora. They have an updated set of dependencies and
20299 conflicts, a fix for an ancient typo when creating the "_tor"
20300 user, and better instructions. Thanks to Ondrej Mikle for the
20301 patch series. Fixes bug 6043.
20302 - On OpenSUSE, create the /var/run/tor directory on startup if it
20303 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
20305 o Code refactoring (safety):
20306 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
20307 10 lines. Also, don't nest them. Doing so in the past has
20308 led to hard-to-debug code. The new style is to use the
20309 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
20310 - Use macros to indicate OpenSSL versions, so we don't need to worry
20311 about accidental hexadecimal bit shifts.
20312 - Use tor_sscanf() in place of scanf() in more places through the
20313 code. This makes us a little more locale-independent, and
20314 should help shut up code-analysis tools that can't tell
20315 a safe sscanf string from a dangerous one.
20316 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
20317 - Use the smartlist_add_asprintf() alias more consistently.
20319 o Code refactoring (consolidate):
20320 - A major revision to our internal node-selecting and listing logic.
20321 Tor already had at least two major ways to look at the question of
20322 "which Tor servers do we know about": a list of router descriptors,
20323 and a list of entries in the current consensus. With
20324 microdescriptors, we're adding a third. Having so many systems
20325 without an abstraction layer over them was hurting the codebase.
20326 Now, we have a new "node_t" abstraction that presents a consistent
20327 interface to a client's view of a Tor node, and holds (nearly) all
20328 of the mutable state formerly in routerinfo_t and routerstatus_t.
20329 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
20330 Libevent's notion of cached time when possible.
20331 - Remove duplicate code for invoking getrlimit() from control.c.
20332 - Use OpenSSL's built-in SSL_state_string_long() instead of our
20333 own homebrewed ssl_state_to_string() replacement. Patch from
20334 Emile Snyder. Fixes bug 4653.
20335 - Change the symmetric cipher interface so that creating and
20336 initializing a stream cipher are no longer separate functions.
20338 o Code refactoring (separate):
20339 - Make a new "entry connection" struct as an internal subtype of "edge
20340 connection", to simplify the code and make exit connections smaller.
20341 - Split connection_about_to_close() into separate functions for each
20343 - Rewrite the listener-selection logic so that parsing which ports
20344 we want to listen on is now separate from binding to the ports
20347 o Code refactoring (name changes):
20348 - Rename a handful of old identifiers, mostly related to crypto
20349 structures and crypto functions. By convention, our "create an
20350 object" functions are called "type_new()", our "free an object"
20351 functions are called "type_free()", and our types indicate that
20352 they are types only with a final "_t". But a handful of older
20353 types and functions broke these rules, with function names like
20354 "type_create" or "subsystem_op_type", or with type names like
20356 - Rename Tor functions that turn strings into addresses, so that
20357 "parse" indicates that no hostname resolution occurs, and
20358 "lookup" indicates that hostname resolution may occur. This
20359 should help prevent mistakes in the future. Fixes bug 3512.
20360 - Use the name "CERTS" consistently to refer to the new cell type;
20361 we were calling it CERT in some places and CERTS in others.
20362 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
20363 invalid value, rather than just -1.
20364 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
20365 can pick them up when the tests aren't disabled. Bugfix on
20366 0.2.2.4-alpha which introduced tinytest.
20368 o Code refactoring (other):
20369 - Defensively refactor rend_mid_rendezvous() so that protocol
20370 violations and length checks happen in the beginning. Fixes
20372 - Remove the pure attribute from all functions that used it
20373 previously. In many cases we assigned it incorrectly, because the
20374 functions might assert or call impure functions, and we don't have
20375 evidence that keeping the pure attribute is worthwhile. Implements
20376 changes suggested in ticket 4421.
20377 - Move the replay-detection cache for the RSA-encrypted parts of
20378 INTRODUCE2 cells to the introduction point data structures.
20379 Previously, we would use one replay-detection cache per hidden
20380 service. Required by fix for bug 3460.
20381 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
20382 no longer link against Libevent: they never used it, but
20383 our library structure used to force them to link it.
20385 o Removed features and files:
20386 - Remove all internal support for unpadded RSA. We never used it, and
20387 it would be a bad idea to start.
20388 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
20390 - Remove some redundant #include directives throughout the code.
20391 Patch from Andrea Gelmini.
20392 - Remove some old code to remember statistics about which descriptors
20393 we've served as a directory mirror. The feature wasn't used and
20394 is outdated now that microdescriptors are around.
20395 - Remove some old code to work around even older versions of Tor that
20396 used forked processes to handle DNS requests. Such versions of Tor
20397 are no longer in use as relays.
20398 - The "torify" script no longer supports the "tsocks" socksifier
20399 tool, since tsocks doesn't support DNS and UDP right for Tor.
20400 Everyone should be using torsocks instead. Fixes bugs 3530 and
20401 5180. Based on a patch by "ugh".
20402 - Remove the torrc.bridge file: we don't use it for anything, and
20403 it had become badly desynchronized from torrc.sample. Resolves
20407 - Begin a doc/state-contents.txt file to explain the contents of
20408 the Tor state file. Fixes bug 2987.
20409 - Clarify the documentation for the Alternate*Authority options.
20411 - Document the --defaults-torrc option, and the new semantics for
20412 overriding, extending, and clearing lists of options. Closes
20414 - Add missing man page documentation for consensus and microdesc
20415 files. Resolves ticket 6732.
20416 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
20418 o Documentation fixes:
20419 - Improve the manual's documentation for the NT Service command-line
20420 options. Addresses ticket 3964.
20421 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
20422 - Document the changes to the ORPort and DirPort options, and the
20423 fact that {OR/Dir}ListenAddress is now unnecessary (and
20424 therefore deprecated). Resolves ticket 5597.
20425 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
20426 - Clarify that hidden services are TCP only. Fixes bug 6024.
20429 Changes in version 0.2.2.39 - 2012-09-11
20430 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
20434 - Fix an assertion failure in tor_timegm() that could be triggered
20435 by a badly formatted directory object. Bug found by fuzzing with
20436 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
20437 - Do not crash when comparing an address with port value 0 to an
20438 address policy. This bug could have been used to cause a remote
20439 assertion failure by or against directory authorities, or to
20440 allow some applications to crash clients. Fixes bug 6690; bugfix
20444 Changes in version 0.2.2.38 - 2012-08-12
20445 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
20446 attack that could in theory leak path information.
20449 - Avoid an uninitialized memory read when reading a vote or consensus
20450 document that has an unrecognized flavor name. This read could
20451 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
20452 - Try to leak less information about what relays a client is
20453 choosing to a side-channel attacker. Previously, a Tor client would
20454 stop iterating through the list of available relays as soon as it
20455 had chosen one, thus finishing a little earlier when it picked
20456 a router earlier in the list. If an attacker can recover this
20457 timing information (nontrivial but not proven to be impossible),
20458 they could learn some coarse-grained information about which relays
20459 a client was picking (middle nodes in particular are likelier to
20460 be affected than exits). The timing attack might be mitigated by
20461 other factors (see bug 6537 for some discussion), but it's best
20462 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
20465 Changes in version 0.2.2.37 - 2012-06-06
20466 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
20467 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
20471 - Work around a bug in OpenSSL that broke renegotiation with TLS
20472 1.1 and TLS 1.2. Without this workaround, all attempts to speak
20473 the v2 Tor connection protocol when both sides were using OpenSSL
20474 1.0.1 would fail. Resolves ticket 6033.
20475 - When waiting for a client to renegotiate, don't allow it to add
20476 any bytes to the input buffer. This fixes a potential DoS issue.
20477 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
20478 - Fix an edge case where if we fetch or publish a hidden service
20479 descriptor, we might build a 4-hop circuit and then use that circuit
20480 for exiting afterwards -- even if the new last hop doesn't obey our
20481 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
20484 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
20485 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
20488 - Tell GCC and Clang to check for any errors in format strings passed
20489 to the tor_v*(print|scan)f functions.
20492 Changes in version 0.2.2.36 - 2012-05-24
20493 Tor 0.2.2.36 updates the addresses for two of the eight directory
20494 authorities, fixes some potential anonymity and security issues,
20495 and fixes several crash bugs.
20497 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
20498 known flaws, and nobody should be using them. You should upgrade. If
20499 you're using a Linux or BSD and its packages are obsolete, stop using
20500 those packages and upgrade anyway.
20502 o Directory authority changes:
20503 - Change IP address for maatuska (v3 directory authority).
20504 - Change IP address for ides (v3 directory authority), and rename
20508 - When building or running with any version of OpenSSL earlier
20509 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
20510 versions have a bug (CVE-2011-4576) in which their block cipher
20511 padding includes uninitialized data, potentially leaking sensitive
20512 information to any peer with whom they make a SSLv3 connection. Tor
20513 does not use SSL v3 by default, but a hostile client or server
20514 could force an SSLv3 connection in order to gain information that
20515 they shouldn't have been able to get. The best solution here is to
20516 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
20517 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
20518 to make sure that the bug can't happen.
20519 - Never use a bridge or a controller-supplied node as an exit, even
20520 if its exit policy allows it. Found by wanoskarnet. Fixes bug
20521 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
20522 and 0.2.0.3-alpha (for bridge-purpose descriptors).
20523 - Only build circuits if we have a sufficient threshold of the total
20524 descriptors that are marked in the consensus with the "Exit"
20525 flag. This mitigates an attack proposed by wanoskarnet, in which
20526 all of a client's bridges collude to restrict the exit nodes that
20527 the client knows about. Fixes bug 5343.
20528 - Provide controllers with a safer way to implement the cookie
20529 authentication mechanism. With the old method, if another locally
20530 running program could convince a controller that it was the Tor
20531 process, then that program could trick the controller into telling
20532 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
20533 authentication method uses a challenge-response approach to prevent
20534 this attack. Fixes bug 5185; implements proposal 193.
20537 - Avoid logging uninitialized data when unable to decode a hidden
20538 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
20539 - Avoid a client-side assertion failure when receiving an INTRODUCE2
20540 cell on a general purpose circuit. Fixes bug 5644; bugfix on
20542 - Fix builds when the path to sed, openssl, or sha1sum contains
20543 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
20545 - Correct our replacements for the timeradd() and timersub() functions
20546 on platforms that lack them (for example, Windows). The timersub()
20547 function is used when expiring circuits, while timeradd() is
20548 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
20549 bugfix on 0.2.2.24-alpha.
20550 - Fix the SOCKET_OK test that we use to tell when socket
20551 creation fails so that it works on Win64. Fixes part of bug 4533;
20552 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
20555 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
20556 Fixes bug 5346; bugfix on 0.0.8pre3.
20557 - Make our number-parsing functions always treat too-large values
20558 as an error, even when those values exceed the width of the
20559 underlying type. Previously, if the caller provided these
20560 functions with minima or maxima set to the extreme values of the
20561 underlying integer type, these functions would return those
20562 values on overflow rather than treating overflow as an error.
20563 Fixes part of bug 5786; bugfix on 0.0.9.
20564 - Older Linux kernels erroneously respond to strange nmap behavior
20565 by having accept() return successfully with a zero-length
20566 socket. When this happens, just close the connection. Previously,
20567 we would try harder to learn the remote address: but there was
20568 no such remote address to learn, and our method for trying to
20569 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
20570 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
20571 - Correct parsing of certain date types in parse_http_time().
20572 Without this patch, If-Modified-Since would behave
20573 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
20574 Esteban Manchado Velázques.
20575 - Change the BridgePassword feature (part of the "bridge community"
20576 design, which is not yet implemented) to use a time-independent
20577 comparison. The old behavior might have allowed an adversary
20578 to use timing to guess the BridgePassword value. Fixes bug 5543;
20579 bugfix on 0.2.0.14-alpha.
20580 - Detect and reject certain misformed escape sequences in
20581 configuration values. Previously, these values would cause us
20582 to crash if received in a torrc file or over an authenticated
20583 control port. Bug found by Esteban Manchado Velázquez, and
20584 independently by Robert Connolly from Matta Consulting who further
20585 noted that it allows a post-authentication heap overflow. Patch
20586 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
20587 bugfix on 0.2.0.16-alpha.
20588 - Fix a compile warning when using the --enable-openbsd-malloc
20589 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
20590 - During configure, detect when we're building with clang version
20591 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
20592 CFLAGS. clang doesn't support them yet.
20593 - When sending an HTTP/1.1 proxy request, include a Host header.
20594 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
20595 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
20596 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
20597 - If we hit the error case where routerlist_insert() replaces an
20598 existing (old) server descriptor, make sure to remove that
20599 server descriptor from the old_routers list. Fix related to bug
20600 1776. Bugfix on 0.2.2.18-alpha.
20602 o Minor bugfixes (documentation and log messages):
20603 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
20604 Fixes bug 4856; bugfix on Tor 0.0.6.
20605 - Update "ClientOnly" man page entry to explain that there isn't
20606 really any point to messing with it. Resolves ticket 5005.
20607 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
20608 directory authority option (introduced in Tor 0.2.2.34).
20609 - Downgrade the "We're missing a certificate" message from notice
20610 to info: people kept mistaking it for a real problem, whereas it
20611 is seldom the problem even when we are failing to bootstrap. Fixes
20612 bug 5067; bugfix on 0.2.0.10-alpha.
20613 - Correctly spell "connect" in a log message on failure to create a
20614 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
20615 - Clarify the behavior of MaxCircuitDirtiness with hidden service
20616 circuits. Fixes issue 5259.
20619 - Directory authorities now reject versions of Tor older than
20620 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
20621 inclusive. These versions accounted for only a small fraction of
20622 the Tor network, and have numerous known security issues. Resolves
20624 - Update to the May 1 2012 Maxmind GeoLite Country database.
20627 - When sending or relaying a RELAY_EARLY cell, we used to convert
20628 it to a RELAY cell if the connection was using the v1 link
20629 protocol. This was a workaround for older versions of Tor, which
20630 didn't handle RELAY_EARLY cells properly. Now that all supported
20631 versions can handle RELAY_EARLY cells, and now that we're enforcing
20632 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
20633 remove this workaround. Addresses bug 4786.
20636 Changes in version 0.2.2.35 - 2011-12-16
20637 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
20638 buffers code. Absolutely everybody should upgrade.
20640 The bug relied on an incorrect calculation when making data continuous
20641 in one of our IO buffers, if the first chunk of the buffer was
20642 misaligned by just the wrong amount. The miscalculation would allow an
20643 attacker to overflow a piece of heap-allocated memory. To mount this
20644 attack, the attacker would need to either open a SOCKS connection to
20645 Tor's SocksPort (usually restricted to localhost), or target a Tor
20646 instance configured to make its connections through a SOCKS proxy
20647 (which Tor does not do by default).
20649 Good security practice requires that all heap-overflow bugs should be
20650 presumed to be exploitable until proven otherwise, so we are treating
20651 this as a potential code execution attack. Please upgrade immediately!
20652 This bug does not affect bufferevents-based builds of Tor. Special
20653 thanks to "Vektor" for reporting this issue to us!
20655 Tor 0.2.2.35 also fixes several bugs in previous versions, including
20656 crash bugs for unusual configurations, and a long-term bug that
20657 would prevent Tor from starting on Windows machines with draconian
20660 With this release, we remind everyone that 0.2.0.x has reached its
20661 formal end-of-life. Those Tor versions have many known flaws, and
20662 nobody should be using them. You should upgrade -- ideally to the
20663 0.2.2.x series. If you're using a Linux or BSD and its packages are
20664 obsolete, stop using those packages and upgrade anyway.
20666 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
20667 longer receive support after some time in early 2012.
20670 - Fix a heap overflow bug that could occur when trying to pull
20671 data into the first chunk of a buffer, when that chunk had
20672 already had some data drained from it. Fixes CVE-2011-2778;
20673 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20674 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
20675 that it doesn't attempt to allocate a socketpair. This could cause
20676 some problems on Windows systems with overzealous firewalls. Fix for
20677 bug 4457; workaround for Libevent versions 2.0.1-alpha through
20679 - If we mark an OR connection for close based on a cell we process,
20680 don't process any further cells on it. We already avoid further
20681 reads on marked-for-close connections, but now we also discard the
20682 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
20683 which was the first version where we might mark a connection for
20684 close based on processing a cell on it.
20685 - Correctly sanity-check that we don't underflow on a memory
20686 allocation (and then assert) for hidden service introduction
20687 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20688 bugfix on 0.2.1.5-alpha.
20689 - Fix a memory leak when we check whether a hidden service
20690 descriptor has any usable introduction points left. Fixes bug
20691 4424. Bugfix on 0.2.2.25-alpha.
20692 - Don't crash when we're running as a relay and don't have a GeoIP
20693 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
20694 we've had in the 0.2.3.x branch already.
20695 - When running as a client, do not print a misleading (and plain
20696 wrong) log message that we're collecting "directory request"
20697 statistics: clients don't collect statistics. Also don't create a
20698 useless (because empty) stats file in the stats/ directory. Fixes
20699 bug 4353; bugfix on 0.2.2.34.
20702 - Detect failure to initialize Libevent. This fix provides better
20703 detection for future instances of bug 4457.
20704 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
20705 function. This was eating up hideously large amounts of time on some
20706 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
20707 - Resolve an integer overflow bug in smartlist_ensure_capacity().
20708 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
20710 - Don't warn about unused log_mutex in log.c when building with
20711 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
20712 0.1.0.6-rc which introduced --disable-threads.
20713 - When configuring, starting, or stopping an NT service, stop
20714 immediately after the service configuration attempt has succeeded
20715 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
20716 - When sending a NETINFO cell, include the original address
20717 received for the other side, not its canonical address. Found
20718 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
20719 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
20720 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
20721 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
20722 occurred when a client tried to fetch a descriptor for a bridge
20723 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
20724 - Backport fixes for a pair of compilation warnings on Windows.
20725 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
20726 - If we had ever tried to call tor_addr_to_str on an address of
20727 unknown type, we would have done a strdup on an uninitialized
20728 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
20729 Reported by "troll_un".
20730 - Correctly detect and handle transient lookup failures from
20731 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
20732 Reported by "troll_un".
20733 - Fix null-pointer access that could occur if TLS allocation failed.
20734 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
20735 - Use tor_socket_t type for listener argument to accept(). Fixes bug
20736 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
20739 - Add two new config options for directory authorities:
20740 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
20741 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
20742 that is always sufficient to satisfy the bandwidth requirement for
20743 the Guard flag. Now it will be easier for researchers to simulate
20744 Tor networks with different values. Resolves ticket 4484.
20745 - When Tor ignores a hidden service specified in its configuration,
20746 include the hidden service's directory in the warning message.
20747 Previously, we would only tell the user that some hidden service
20748 was ignored. Bugfix on 0.0.6; fixes bug 4426.
20749 - Update to the December 6 2011 Maxmind GeoLite Country database.
20751 o Packaging changes:
20752 - Make it easier to automate expert package builds on Windows,
20753 by removing an absolute path from makensis.exe command.
20756 Changes in version 0.2.1.32 - 2011-12-16
20757 Tor 0.2.1.32 backports important security and privacy fixes for
20758 oldstable. This release is intended only for package maintainers and
20759 others who cannot use the 0.2.2 stable series. All others should be
20760 using Tor 0.2.2.x or newer.
20762 The Tor 0.2.1.x series will reach formal end-of-life some time in
20763 early 2012; we will stop releasing patches for it then.
20765 o Major bugfixes (also included in 0.2.2.x):
20766 - Correctly sanity-check that we don't underflow on a memory
20767 allocation (and then assert) for hidden service introduction
20768 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20769 bugfix on 0.2.1.5-alpha.
20770 - Fix a heap overflow bug that could occur when trying to pull
20771 data into the first chunk of a buffer, when that chunk had
20772 already had some data drained from it. Fixes CVE-2011-2778;
20773 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20776 - Update to the December 6 2011 Maxmind GeoLite Country database.
20779 Changes in version 0.2.2.34 - 2011-10-26
20780 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
20781 can deanonymize Tor users. Everybody should upgrade.
20783 The attack relies on four components: 1) Clients reuse their TLS cert
20784 when talking to different relays, so relays can recognize a user by
20785 the identity key in her cert. 2) An attacker who knows the client's
20786 identity key can probe each guard relay to see if that identity key
20787 is connected to that guard relay right now. 3) A variety of active
20788 attacks in the literature (starting from "Low-Cost Traffic Analysis
20789 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
20790 discover the guard relays that a Tor user visiting the website is using.
20791 4) Clients typically pick three guards at random, so the set of guards
20792 for a given user could well be a unique fingerprint for her. This
20793 release fixes components #1 and #2, which is enough to block the attack;
20794 the other two remain as open research problems. Special thanks to
20795 "frosty_un" for reporting the issue to us!
20797 Clients should upgrade so they are no longer recognizable by the TLS
20798 certs they present. Relays should upgrade so they no longer allow a
20799 remote attacker to probe them to test whether unpatched clients are
20800 currently connected to them.
20802 This release also fixes several vulnerabilities that allow an attacker
20803 to enumerate bridge relays. Some bridge enumeration attacks still
20804 remain; see for example proposal 188.
20806 o Privacy/anonymity fixes (clients):
20807 - Clients and bridges no longer send TLS certificate chains on
20808 outgoing OR connections. Previously, each client or bridge would
20809 use the same cert chain for all outgoing OR connections until
20810 its IP address changes, which allowed any relay that the client
20811 or bridge contacted to determine which entry guards it is using.
20812 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20813 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20814 no longer considers that connection as suitable for satisfying a
20815 circuit EXTEND request. Now relays can protect clients from the
20816 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20817 - Directory authorities no longer assign the Guard flag to relays
20818 that haven't upgraded to the above "refuse EXTEND requests
20819 to client connections" fix. Now directory authorities can
20820 protect clients from the CVE-2011-2768 issue even if neither
20821 the clients nor the relays have upgraded yet. There's a new
20822 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
20823 to let us transition smoothly, else tomorrow there would be no
20826 o Privacy/anonymity fixes (bridge enumeration):
20827 - Bridge relays now do their directory fetches inside Tor TLS
20828 connections, like all the other clients do, rather than connecting
20829 directly to the DirPort like public relays do. Removes another
20830 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
20831 - Bridges relays now build circuits for themselves in a more similar
20832 way to how clients build them. Removes another avenue for
20833 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
20834 when bridges were introduced.
20835 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20836 that they initiated. Relays could distinguish incoming bridge
20837 connections from client connections, creating another avenue for
20838 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20839 Found by "frosty_un".
20842 - Fix a crash bug when changing node restrictions while a DNS lookup
20843 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
20845 - Don't launch a useless circuit after failing to use one of a
20846 hidden service's introduction points. Previously, we would
20847 launch a new introduction circuit, but not set the hidden service
20848 which that circuit was intended to connect to, so it would never
20849 actually be used. A different piece of code would then create a
20850 new introduction circuit correctly. Bug reported by katmagic and
20851 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
20854 - Change an integer overflow check in the OpenBSD_Malloc code so
20855 that GCC is less likely to eliminate it as impossible. Patch
20856 from Mansour Moufid. Fixes bug 4059.
20857 - When a hidden service turns an extra service-side introduction
20858 circuit into a general-purpose circuit, free the rend_data and
20859 intro_key fields first, so we won't leak memory if the circuit
20860 is cannibalized for use as another service-side introduction
20861 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
20862 - Bridges now skip DNS self-tests, to act a little more stealthily.
20863 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
20864 bridges. Patch by "warms0x".
20865 - Fix internal bug-checking logic that was supposed to catch
20866 failures in digest generation so that it will fail more robustly
20867 if we ask for a nonexistent algorithm. Found by Coverity Scan.
20868 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
20869 - Report any failure in init_keys() calls launched because our
20870 IP address has changed. Spotted by Coverity Scan. Bugfix on
20871 0.1.1.4-alpha; fixes CID 484.
20873 o Minor bugfixes (log messages and documentation):
20874 - Remove a confusing dollar sign from the example fingerprint in the
20875 man page, and also make the example fingerprint a valid one. Fixes
20876 bug 4309; bugfix on 0.2.1.3-alpha.
20877 - The next version of Windows will be called Windows 8, and it has
20878 a major version of 6, minor version of 2. Correctly identify that
20879 version instead of calling it "Very recent version". Resolves
20880 ticket 4153; reported by funkstar.
20881 - Downgrade log messages about circuit timeout calibration from
20882 "notice" to "info": they don't require or suggest any human
20883 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
20884 bugfix on 0.2.2.14-alpha.
20887 - Turn on directory request statistics by default and include them in
20888 extra-info descriptors. Don't break if we have no GeoIP database.
20889 Backported from 0.2.3.1-alpha; implements ticket 3951.
20890 - Update to the October 4 2011 Maxmind GeoLite Country database.
20893 Changes in version 0.2.1.31 - 2011-10-26
20894 Tor 0.2.1.31 backports important security and privacy fixes for
20895 oldstable. This release is intended only for package maintainers and
20896 others who cannot use the 0.2.2 stable series. All others should be
20897 using Tor 0.2.2.x or newer.
20899 o Security fixes (also included in 0.2.2.x):
20900 - Replace all potentially sensitive memory comparison operations
20901 with versions whose runtime does not depend on the data being
20902 compared. This will help resist a class of attacks where an
20903 adversary can use variations in timing information to learn
20904 sensitive data. Fix for one case of bug 3122. (Safe memcmp
20905 implementation by Robert Ransom based partially on code by DJB.)
20906 - Fix an assert in parsing router descriptors containing IPv6
20907 addresses. This one took down the directory authorities when
20908 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
20910 o Privacy/anonymity fixes (also included in 0.2.2.x):
20911 - Clients and bridges no longer send TLS certificate chains on
20912 outgoing OR connections. Previously, each client or bridge would
20913 use the same cert chain for all outgoing OR connections until
20914 its IP address changes, which allowed any relay that the client
20915 or bridge contacted to determine which entry guards it is using.
20916 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20917 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20918 no longer considers that connection as suitable for satisfying a
20919 circuit EXTEND request. Now relays can protect clients from the
20920 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20921 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20922 that they initiated. Relays could distinguish incoming bridge
20923 connections from client connections, creating another avenue for
20924 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20925 Found by "frosty_un".
20926 - When receiving a hidden service descriptor, check that it is for
20927 the hidden service we wanted. Previously, Tor would store any
20928 hidden service descriptors that a directory gave it, whether it
20929 wanted them or not. This wouldn't have let an attacker impersonate
20930 a hidden service, but it did let directories pre-seed a client
20931 with descriptors that it didn't want. Bugfix on 0.0.6.
20932 - Avoid linkability based on cached hidden service descriptors: forget
20933 all hidden service descriptors cached as a client when processing a
20934 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
20935 - Make the bridge directory authority refuse to answer directory
20936 requests for "all" descriptors. It used to include bridge
20937 descriptors in its answer, which was a major information leak.
20938 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
20939 - Don't attach new streams to old rendezvous circuits after SIGNAL
20940 NEWNYM. Previously, we would keep using an existing rendezvous
20941 circuit if it remained open (i.e. if it were kept open by a
20942 long-lived stream, or if a new stream were attached to it before
20943 Tor could notice that it was old and no longer in use). Bugfix on
20944 0.1.1.15-rc; fixes bug 3375.
20946 o Minor bugfixes (also included in 0.2.2.x):
20947 - When we restart our relay, we might get a successful connection
20948 from the outside before we've started our reachability tests,
20949 triggering a warning: "ORPort found reachable, but I have no
20950 routerinfo yet. Failing to inform controller of success." This
20951 bug was harmless unless Tor is running under a controller
20952 like Vidalia, in which case the controller would never get a
20953 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
20955 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
20956 enabled. Fixes bug 1526.
20957 - Remove undocumented option "-F" from tor-resolve: it hasn't done
20958 anything since 0.2.1.16-rc.
20959 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
20960 None of the cases where we did this before were wrong, but by making
20961 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
20962 - Fix a rare crash bug that could occur when a client was configured
20963 with a large number of bridges. Fixes bug 2629; bugfix on
20964 0.2.1.2-alpha. Bugfix by trac user "shitlei".
20965 - Correct the warning displayed when a rendezvous descriptor exceeds
20966 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
20968 - Fix an uncommon assertion failure when running with DNSPort under
20969 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
20970 - When warning about missing zlib development packages during compile,
20971 give the correct package names. Bugfix on 0.2.0.1-alpha.
20972 - Require that introduction point keys and onion keys have public
20973 exponent 65537. Bugfix on 0.2.0.10-alpha.
20974 - Do not crash when our configuration file becomes unreadable, for
20975 example due to a permissions change, between when we start up
20976 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
20978 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
20980 - Always NUL-terminate the sun_path field of a sockaddr_un before
20981 passing it to the kernel. (Not a security issue: kernels are
20982 smart enough to reject bad sockaddr_uns.) Found by Coverity;
20983 CID #428. Bugfix on Tor 0.2.0.3-alpha.
20984 - Don't stack-allocate the list of supplementary GIDs when we're
20985 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
20986 could take up to 256K, which is way too much stack. Found by
20987 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
20989 o Minor bugfixes (only in 0.2.1.x):
20990 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
20991 rely on them. Bugfix on 0.2.1.30.
20992 - Use git revisions instead of svn revisions when generating our
20993 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
20995 o Minor features (also included in 0.2.2.x):
20996 - Adjust the expiration time on our SSL session certificates to
20997 better match SSL certs seen in the wild. Resolves ticket 4014.
20998 - Allow nameservers with IPv6 address. Resolves bug 2574.
20999 - Update to the October 4 2011 Maxmind GeoLite Country database.
21002 Changes in version 0.2.2.33 - 2011-09-13
21003 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
21004 TLS handshake that makes relays and bridges that run this new version
21005 reachable from Iran again.
21008 - Avoid an assertion failure when reloading a configuration with
21009 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
21010 3923; bugfix on 0.2.2.25-alpha.
21012 o Minor features (security):
21013 - Check for replays of the public-key encrypted portion of an
21014 INTRODUCE1 cell, in addition to the current check for replays of
21015 the g^x value. This prevents a possible class of active attacks
21016 by an attacker who controls both an introduction point and a
21017 rendezvous point, and who uses the malleability of AES-CTR to
21018 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
21019 that these attacks are infeasible (requiring the attacker to send
21020 on the order of zettabytes of altered cells in a short interval),
21021 but we'd rather block them off in case there are any classes of
21022 this attack that we missed. Reported by Willem Pinckaers.
21025 - Adjust the expiration time on our SSL session certificates to
21026 better match SSL certs seen in the wild. Resolves ticket 4014.
21027 - Change the default required uptime for a relay to be accepted as
21028 a HSDir (hidden service directory) from 24 hours to 25 hours.
21029 Improves on 0.2.0.10-alpha; resolves ticket 2649.
21030 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
21031 authorities to abstain from voting on assignment of the HSDir
21032 consensus flag. Related to bug 2649.
21033 - Update to the September 6 2011 Maxmind GeoLite Country database.
21035 o Minor bugfixes (documentation and log messages):
21036 - Correct the man page to explain that HashedControlPassword and
21037 CookieAuthentication can both be set, in which case either method
21038 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
21039 when we decided to allow these config options to both be set. Issue
21040 raised by bug 3898.
21041 - Demote the 'replay detected' log message emitted when a hidden
21042 service receives the same Diffie-Hellman public key in two different
21043 INTRODUCE2 cells to info level. A normal Tor client can cause that
21044 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
21045 fixes part of bug 2442.
21046 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
21047 level. There is nothing that a hidden service's operator can do
21048 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
21050 - Clarify a log message specifying the characters permitted in
21051 HiddenServiceAuthorizeClient client names. Previously, the log
21052 message said that "[A-Za-z0-9+-_]" were permitted; that could have
21053 given the impression that every ASCII character between "+" and "_"
21054 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
21057 - Provide a substitute implementation of lround() for MSVC, which
21058 apparently lacks it. Patch from Gisle Vanem.
21059 - Clean up some code issues that prevented Tor from building on older
21060 BSDs. Fixes bug 3894; reported by "grarpamp".
21061 - Search for a platform-specific version of "ar" when cross-compiling.
21062 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
21065 Changes in version 0.2.2.32 - 2011-08-27
21066 The Tor 0.2.2 release series is dedicated to the memory of Andreas
21067 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
21068 a founder of the PETS community, a leader in our field, a mentor,
21069 and a friend. He left us with these words: "I had the possibility
21070 to contribute to this world that is not as it should be. I hope I
21071 could help in some areas to make the world a better place, and that
21072 I could also encourage other people to be engaged in improving the
21073 world. Please, stay engaged. This world needs you, your love, your
21074 initiative -- now I cannot be part of that anymore."
21076 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
21077 ready. More than two years in the making, this release features improved
21078 client performance and hidden service reliability, better compatibility
21079 for Android, correct behavior for bridges that listen on more than
21080 one address, more extensible and flexible directory object handling,
21081 better reporting of network statistics, improved code security, and
21082 many many other features and bugfixes.
21084 o Major features (client performance):
21085 - When choosing which cells to relay first, relays now favor circuits
21086 that have been quiet recently, to provide lower latency for
21087 low-volume circuits. By default, relays enable or disable this
21088 feature based on a setting in the consensus. They can override
21089 this default by using the new "CircuitPriorityHalflife" config
21090 option. Design and code by Ian Goldberg, Can Tang, and Chris
21092 - Directory authorities now compute consensus weightings that instruct
21093 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
21094 and no flag. Clients use these weightings to distribute network load
21095 more evenly across these different relay types. The weightings are
21096 in the consensus so we can change them globally in the future. Extra
21097 thanks to "outofwords" for finding some nasty security bugs in
21098 the first implementation of this feature.
21100 o Major features (client performance, circuit build timeout):
21101 - Tor now tracks how long it takes to build client-side circuits
21102 over time, and adapts its timeout to local network performance.
21103 Since a circuit that takes a long time to build will also provide
21104 bad performance, we get significant latency improvements by
21105 discarding the slowest 20% of circuits. Specifically, Tor creates
21106 circuits more aggressively than usual until it has enough data
21107 points for a good timeout estimate. Implements proposal 151.
21108 - Circuit build timeout constants can be controlled by consensus
21109 parameters. We set good defaults for these parameters based on
21110 experimentation on broadband and simulated high-latency links.
21111 - Circuit build time learning can be disabled via consensus parameter
21112 or by the client via a LearnCircuitBuildTimeout config option. We
21113 also automatically disable circuit build time calculation if either
21114 AuthoritativeDirectory is set, or if we fail to write our state
21115 file. Implements ticket 1296.
21117 o Major features (relays use their capacity better):
21118 - Set SO_REUSEADDR socket option on all sockets, not just
21119 listeners. This should help busy exit nodes avoid running out of
21120 useable ports just because all the ports have been used in the
21121 near past. Resolves issue 2850.
21122 - Relays now save observed peak bandwidth throughput rates to their
21123 state file (along with total usage, which was already saved),
21124 so that they can determine their correct estimated bandwidth on
21125 restart. Resolves bug 1863, where Tor relays would reset their
21126 estimated bandwidth to 0 after restarting.
21127 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
21128 should give us approximately 40-50% more Guard-flagged nodes,
21129 improving the anonymity the Tor network can provide and also
21130 decreasing the dropoff in throughput that relays experience when
21131 they first get the Guard flag.
21132 - Directory authorities now take changes in router IP address and
21133 ORPort into account when determining router stability. Previously,
21134 if a router changed its IP or ORPort, the authorities would not
21135 treat it as having any downtime for the purposes of stability
21136 calculation, whereas clients would experience downtime since the
21137 change would take a while to propagate to them. Resolves issue 1035.
21138 - New AccelName and AccelDir options add support for dynamic OpenSSL
21139 hardware crypto acceleration engines.
21141 o Major features (relays control their load better):
21142 - Exit relays now try harder to block exit attempts from unknown
21143 relays, to make it harder for people to use them as one-hop proxies
21144 a la tortunnel. Controlled by the refuseunknownexits consensus
21145 parameter (currently enabled), or you can override it on your
21146 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
21147 based on a variant of proposal 163.
21148 - Add separate per-conn write limiting to go with the per-conn read
21149 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
21150 but never per-conn write limits.
21151 - New consensus params "bwconnrate" and "bwconnburst" to let us
21152 rate-limit client connections as they enter the network. It's
21153 controlled in the consensus so we can turn it on and off for
21154 experiments. It's starting out off. Based on proposal 163.
21156 o Major features (controllers):
21157 - Export GeoIP information on bridge usage to controllers even if we
21158 have not yet been running for 24 hours. Now Vidalia bridge operators
21159 can get more accurate and immediate feedback about their
21160 contributions to the network.
21161 - Add an __OwningControllerProcess configuration option and a
21162 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
21163 that when it exits, Tor will shut down. Implements feature 3049.
21165 o Major features (directory authorities):
21166 - Directory authorities now create, vote on, and serve multiple
21167 parallel formats of directory data as part of their voting process.
21168 Partially implements Proposal 162: "Publish the consensus in
21170 - Directory authorities now agree on and publish small summaries
21171 of router information that clients can use in place of regular
21172 server descriptors. This transition will allow Tor 0.2.3 clients
21173 to use far less bandwidth for downloading information about the
21174 network. Begins the implementation of Proposal 158: "Clients
21175 download consensus + microdescriptors".
21176 - The directory voting system is now extensible to use multiple hash
21177 algorithms for signatures and resource selection. Newer formats
21178 are signed with SHA256, with a possibility for moving to a better
21179 hash algorithm in the future.
21180 - Directory authorities can now vote on arbitrary integer values as
21181 part of the consensus process. This is designed to help set
21182 network-wide parameters. Implements proposal 167.
21184 o Major features and bugfixes (node selection):
21185 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
21186 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
21187 options. Previously, we had been ambiguous in describing what
21188 counted as an "exit" node, and what operations exactly "StrictNodes
21189 0" would permit. This created confusion when people saw nodes built
21190 through unexpected circuits, and made it hard to tell real bugs from
21191 surprises. Now the intended behavior is:
21192 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
21193 a node that delivers user traffic outside the Tor network.
21194 . "Entry", in the context of EntryNodes, means a node used as the
21195 first hop of a multihop circuit. It doesn't include direct
21196 connections to directory servers.
21197 . "ExcludeNodes" applies to all nodes.
21198 . "StrictNodes" changes the behavior of ExcludeNodes only. When
21199 StrictNodes is set, Tor should avoid all nodes listed in
21200 ExcludeNodes, even when it will make user requests fail. When
21201 StrictNodes is *not* set, then Tor should follow ExcludeNodes
21202 whenever it can, except when it must use an excluded node to
21203 perform self-tests, connect to a hidden service, provide a
21204 hidden service, fulfill a .exit request, upload directory
21205 information, or fetch directory information.
21206 Collectively, the changes to implement the behavior fix bug 1090.
21207 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
21208 change during a config reload, mark and discard all our origin
21209 circuits. This fix should address edge cases where we change the
21210 config options and but then choose a circuit that we created before
21212 - Make EntryNodes config option much more aggressive even when
21213 StrictNodes is not set. Before it would prepend your requested
21214 entrynodes to your list of guard nodes, but feel free to use others
21215 after that. Now it chooses only from your EntryNodes if any of
21216 those are available, and only falls back to others if a) they're
21217 all down and b) StrictNodes is not set.
21218 - Now we refresh your entry guards from EntryNodes at each consensus
21219 fetch -- rather than just at startup and then they slowly rot as
21220 the network changes.
21221 - Add support for the country code "{??}" in torrc options like
21222 ExcludeNodes, to indicate all routers of unknown country. Closes
21224 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
21225 a node is listed in both, it's treated as excluded.
21226 - ExcludeNodes now applies to directory nodes -- as a preference if
21227 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
21228 Don't exclude all the directory authorities and set StrictNodes to 1
21229 unless you really want your Tor to break.
21230 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
21231 - ExcludeExitNodes now overrides .exit requests.
21232 - We don't use bridges listed in ExcludeNodes.
21233 - When StrictNodes is 1:
21234 . We now apply ExcludeNodes to hidden service introduction points
21235 and to rendezvous points selected by hidden service users. This
21236 can make your hidden service less reliable: use it with caution!
21237 . If we have used ExcludeNodes on ourself, do not try relay
21238 reachability self-tests.
21239 . If we have excluded all the directory authorities, we will not
21240 even try to upload our descriptor if we're a relay.
21241 . Do not honor .exit requests to an excluded node.
21242 - When the set of permitted nodes changes, we now remove any mappings
21243 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
21245 - We never cannibalize a circuit that had excluded nodes on it, even
21246 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
21247 - Improve log messages related to excluded nodes.
21249 o Major features (misc):
21250 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
21251 to help Tor build correctly for Android phones.
21252 - The options SocksPort, ControlPort, and so on now all accept a
21253 value "auto" that opens a socket on an OS-selected port. A
21254 new ControlPortWriteToFile option tells Tor to write its
21255 actual control port or ports to a chosen file. If the option
21256 ControlPortFileGroupReadable is set, the file is created as
21257 group-readable. Now users can run two Tor clients on the same
21258 system without needing to manually mess with parameters. Resolves
21259 part of ticket 3076.
21260 - Tor now supports tunneling all of its outgoing connections over
21261 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
21262 configuration options. Code by Christopher Davis.
21264 o Code security improvements:
21265 - Replace all potentially sensitive memory comparison operations
21266 with versions whose runtime does not depend on the data being
21267 compared. This will help resist a class of attacks where an
21268 adversary can use variations in timing information to learn
21269 sensitive data. Fix for one case of bug 3122. (Safe memcmp
21270 implementation by Robert Ransom based partially on code by DJB.)
21271 - Enable Address Space Layout Randomization (ASLR) and Data Execution
21272 Prevention (DEP) by default on Windows to make it harder for
21273 attackers to exploit vulnerabilities. Patch from John Brooks.
21274 - New "--enable-gcc-hardening" ./configure flag (off by default)
21275 to turn on gcc compile time hardening options. It ensures
21276 that signed ints have defined behavior (-fwrapv), enables
21277 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
21278 with canaries (-fstack-protector-all), turns on ASLR protection if
21279 supported by the kernel (-fPIE, -pie), and adds additional security
21280 related warnings. Verified to work on Mac OS X and Debian Lenny.
21281 - New "--enable-linker-hardening" ./configure flag (off by default)
21282 to turn on ELF specific hardening features (relro, now). This does
21283 not work with Mac OS X or any other non-ELF binary format.
21284 - Always search the Windows system directory for system DLLs, and
21285 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
21286 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
21287 current and future memory pages via mlockall(). On supported
21288 platforms (modern Linux and probably BSD but not Windows or OS X),
21289 this should effectively disable any and all attempts to page out
21290 memory. This option requires that you start your Tor as root --
21291 if you use DisableAllSwap, please consider using the User option
21292 to properly reduce the privileges of your Tor.
21294 o Major bugfixes (crashes):
21295 - Fix crash bug on platforms where gmtime and localtime can return
21296 NULL. Windows 7 users were running into this one. Fixes part of bug
21297 2077. Bugfix on all versions of Tor. Found by boboper.
21298 - Introduce minimum/maximum values that clients will believe
21299 from the consensus. Now we'll have a better chance to avoid crashes
21300 or worse when a consensus param has a weird value.
21301 - Fix a rare crash bug that could occur when a client was configured
21302 with a large number of bridges. Fixes bug 2629; bugfix on
21303 0.2.1.2-alpha. Bugfix by trac user "shitlei".
21304 - Do not crash when our configuration file becomes unreadable, for
21305 example due to a permissions change, between when we start up
21306 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
21308 - If we're in the pathological case where there's no exit bandwidth
21309 but there is non-exit bandwidth, or no guard bandwidth but there
21310 is non-guard bandwidth, don't crash during path selection. Bugfix
21312 - Fix a crash bug when trying to initialize the evdns module in
21313 Libevent 2. Bugfix on 0.2.1.16-rc.
21315 o Major bugfixes (stability):
21316 - Fix an assert in parsing router descriptors containing IPv6
21317 addresses. This one took down the directory authorities when
21318 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
21319 - Fix an uncommon assertion failure when running with DNSPort under
21320 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
21321 - Treat an unset $HOME like an empty $HOME rather than triggering an
21322 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
21323 - More gracefully handle corrupt state files, removing asserts
21324 in favor of saving a backup and resetting state.
21325 - Instead of giving an assertion failure on an internal mismatch
21326 on estimated freelist size, just log a BUG warning and try later.
21327 Mitigates but does not fix bug 1125.
21328 - Fix an assert that got triggered when using the TestingTorNetwork
21329 configuration option and then issuing a GETINFO config-text control
21330 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
21331 - If the cached cert file is unparseable, warn but don't exit.
21333 o Privacy fixes (relays/bridges):
21334 - Don't list Windows capabilities in relay descriptors. We never made
21335 use of them, and maybe it's a bad idea to publish them. Bugfix
21337 - If the Nickname configuration option isn't given, Tor would pick a
21338 nickname based on the local hostname as the nickname for a relay.
21339 Because nicknames are not very important in today's Tor and the
21340 "Unnamed" nickname has been implemented, this is now problematic
21341 behavior: It leaks information about the hostname without being
21342 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
21343 introduced the Unnamed nickname. Reported by tagnaq.
21344 - Maintain separate TLS contexts and certificates for incoming and
21345 outgoing connections in bridge relays. Previously we would use the
21346 same TLS contexts and certs for incoming and outgoing connections.
21347 Bugfix on 0.2.0.3-alpha; addresses bug 988.
21348 - Maintain separate identity keys for incoming and outgoing TLS
21349 contexts in bridge relays. Previously we would use the same
21350 identity keys for incoming and outgoing TLS contexts. Bugfix on
21351 0.2.0.3-alpha; addresses the other half of bug 988.
21352 - Make the bridge directory authority refuse to answer directory
21353 requests for "all descriptors". It used to include bridge
21354 descriptors in its answer, which was a major information leak.
21355 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
21357 o Privacy fixes (clients):
21358 - When receiving a hidden service descriptor, check that it is for
21359 the hidden service we wanted. Previously, Tor would store any
21360 hidden service descriptors that a directory gave it, whether it
21361 wanted them or not. This wouldn't have let an attacker impersonate
21362 a hidden service, but it did let directories pre-seed a client
21363 with descriptors that it didn't want. Bugfix on 0.0.6.
21364 - Start the process of disabling ".exit" address notation, since it
21365 can be used for a variety of esoteric application-level attacks
21366 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
21368 - Reject attempts at the client side to open connections to private
21369 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
21370 a randomly chosen exit node. Attempts to do so are always
21371 ill-defined, generally prevented by exit policies, and usually
21372 in error. This will also help to detect loops in transparent
21373 proxy configurations. You can disable this feature by setting
21374 "ClientRejectInternalAddresses 0" in your torrc.
21375 - Log a notice when we get a new control connection. Now it's easier
21376 for security-conscious users to recognize when a local application
21377 is knocking on their controller door. Suggested by bug 1196.
21379 o Privacy fixes (newnym):
21380 - Avoid linkability based on cached hidden service descriptors: forget
21381 all hidden service descriptors cached as a client when processing a
21382 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
21383 - On SIGHUP, do not clear out all TrackHostExits mappings, client
21384 DNS cache entries, and virtual address mappings: that's what
21385 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
21386 - Don't attach new streams to old rendezvous circuits after SIGNAL
21387 NEWNYM. Previously, we would keep using an existing rendezvous
21388 circuit if it remained open (i.e. if it were kept open by a
21389 long-lived stream, or if a new stream were attached to it before
21390 Tor could notice that it was old and no longer in use). Bugfix on
21391 0.1.1.15-rc; fixes bug 3375.
21393 o Major bugfixes (relay bandwidth accounting):
21394 - Fix a bug that could break accounting on 64-bit systems with large
21395 time_t values, making them hibernate for impossibly long intervals.
21396 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
21397 - Fix a bug in bandwidth accounting that could make us use twice
21398 the intended bandwidth when our interval start changes due to
21399 daylight saving time. Now we tolerate skew in stored vs computed
21400 interval starts: if the start of the period changes by no more than
21401 50% of the period's duration, we remember bytes that we transferred
21402 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
21404 o Major bugfixes (bridges):
21405 - Bridges now use "reject *:*" as their default exit policy. Bugfix
21406 on 0.2.0.3-alpha. Fixes bug 1113.
21407 - If you configure your bridge with a known identity fingerprint,
21408 and the bridge authority is unreachable (as it is in at least
21409 one country now), fall back to directly requesting the descriptor
21410 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
21412 - Fix a bug where bridge users who configure the non-canonical
21413 address of a bridge automatically switch to its canonical
21414 address. If a bridge listens at more than one address, it
21415 should be able to advertise those addresses independently and
21416 any non-blocked addresses should continue to work. Bugfix on Tor
21417 0.2.0.3-alpha. Fixes bug 2510.
21418 - If you configure Tor to use bridge A, and then quit and
21419 configure Tor to use bridge B instead (or if you change Tor
21420 to use bridge B via the controller), it would happily continue
21421 to use bridge A if it's still reachable. While this behavior is
21422 a feature if your goal is connectivity, in some scenarios it's a
21423 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
21424 - When the controller configures a new bridge, don't wait 10 to 60
21425 seconds before trying to fetch its descriptor. Bugfix on
21426 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
21428 o Major bugfixes (directory authorities):
21429 - Many relays have been falling out of the consensus lately because
21430 not enough authorities know about their descriptor for them to get
21431 a majority of votes. When we deprecated the v2 directory protocol,
21432 we got rid of the only way that v3 authorities can hear from each
21433 other about other descriptors. Now authorities examine every v3
21434 vote for new descriptors, and fetch them from that authority. Bugfix
21436 - Authorities could be tricked into giving out the Exit flag to relays
21437 that didn't allow exiting to any ports. This bug could screw
21438 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
21439 1238. Bug discovered by Martin Kowalczyk.
21440 - If all authorities restart at once right before a consensus vote,
21441 nobody will vote about "Running", and clients will get a consensus
21442 with no usable relays. Instead, authorities refuse to build a
21443 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
21445 o Major bugfixes (stream-level fairness):
21446 - When receiving a circuit-level SENDME for a blocked circuit, try
21447 to package cells fairly from all the streams that had previously
21448 been blocked on that circuit. Previously, we had started with the
21449 oldest stream, and allowed each stream to potentially exhaust
21450 the circuit's package window. This gave older streams on any
21451 given circuit priority over newer ones. Fixes bug 1937. Detected
21452 originally by Camilo Viecco. This bug was introduced before the
21453 first Tor release, in svn commit r152: it is the new winner of
21454 the longest-lived bug prize.
21455 - Fix a stream fairness bug that would cause newer streams on a given
21456 circuit to get preference when reading bytes from the origin or
21457 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
21458 introduced before the first Tor release, in svn revision r152.
21459 - When the exit relay got a circuit-level sendme cell, it started
21460 reading on the exit streams, even if had 500 cells queued in the
21461 circuit queue already, so the circuit queue just grew and grew in
21462 some cases. We fix this by not re-enabling reading on receipt of a
21463 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
21464 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
21466 - Newly created streams were allowed to read cells onto circuits,
21467 even if the circuit's cell queue was blocked and waiting to drain.
21468 This created potential unfairness, as older streams would be
21469 blocked, but newer streams would gladly fill the queue completely.
21470 We add code to detect this situation and prevent any stream from
21471 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
21474 o Major bugfixes (hidden services):
21475 - Apply circuit timeouts to opened hidden-service-related circuits
21476 based on the correct start time. Previously, we would apply the
21477 circuit build timeout based on time since the circuit's creation;
21478 it was supposed to be applied based on time since the circuit
21479 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
21480 - Improve hidden service robustness: When we find that we have
21481 extended a hidden service's introduction circuit to a relay not
21482 listed as an introduction point in the HS descriptor we currently
21483 have, retry with an introduction point from the current
21484 descriptor. Previously we would just give up. Fixes bugs 1024 and
21485 1930; bugfix on 0.2.0.10-alpha.
21486 - Directory authorities now use data collected from their own
21487 uptime observations when choosing whether to assign the HSDir flag
21488 to relays, instead of trusting the uptime value the relay reports in
21489 its descriptor. This change helps prevent an attack where a small
21490 set of nodes with frequently-changing identity keys can blackhole
21491 a hidden service. (Only authorities need upgrade; others will be
21492 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
21493 - Stop assigning the HSDir flag to relays that disable their
21494 DirPort (and thus will refuse to answer directory requests). This
21495 fix should dramatically improve the reachability of hidden services:
21496 hidden services and hidden service clients pick six HSDir relays
21497 to store and retrieve the hidden service descriptor, and currently
21498 about half of the HSDir relays will refuse to work. Bugfix on
21499 0.2.0.10-alpha; fixes part of bug 1693.
21501 o Major bugfixes (misc):
21502 - Clients now stop trying to use an exit node associated with a given
21503 destination by TrackHostExits if they fail to reach that exit node.
21504 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
21505 - Fix a regression that caused Tor to rebind its ports if it receives
21506 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
21507 - Remove an extra pair of quotation marks around the error
21508 message in control-port STATUS_GENERAL BUG events. Bugfix on
21509 0.1.2.6-alpha; fixes bug 3732.
21511 o Minor features (relays):
21512 - Ensure that no empty [dirreq-](read|write)-history lines are added
21513 to an extrainfo document. Implements ticket 2497.
21514 - When bandwidth accounting is enabled, be more generous with how
21515 much bandwidth we'll use up before entering "soft hibernation".
21516 Previously, we'd refuse new connections and circuits once we'd
21517 used up 95% of our allotment. Now, we use up 95% of our allotment,
21518 AND make sure that we have no more than 500MB (or 3 hours of
21519 expected traffic, whichever is lower) remaining before we enter
21521 - Relays now log the reason for publishing a new relay descriptor,
21522 so we have a better chance of hunting down instances of bug 1810.
21523 Resolves ticket 3252.
21524 - Log a little more clearly about the times at which we're no longer
21525 accepting new connections (e.g. due to hibernating). Resolves
21527 - When AllowSingleHopExits is set, print a warning to explain to the
21528 relay operator why most clients are avoiding her relay.
21529 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
21530 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
21531 clients are already deprecated because of security bugs.
21533 o Minor features (network statistics):
21534 - Directory mirrors that set "DirReqStatistics 1" write statistics
21535 about directory requests to disk every 24 hours. As compared to the
21536 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
21537 improvements: 1) stats are written to disk exactly every 24 hours;
21538 2) estimated shares of v2 and v3 requests are determined as mean
21539 values, not at the end of a measurement period; 3) unresolved
21540 requests are listed with country code '??'; 4) directories also
21541 measure download times.
21542 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
21543 number of exit streams and transferred bytes per port to disk every
21545 - Relays that set "CellStatistics 1" write statistics on how long
21546 cells spend in their circuit queues to disk every 24 hours.
21547 - Entry nodes that set "EntryStatistics 1" write statistics on the
21548 rough number and origins of connecting clients to disk every 24
21550 - Relays that write any of the above statistics to disk and set
21551 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
21552 their extra-info documents. Implements proposal 166.
21554 o Minor features (GeoIP and statistics):
21555 - Provide a log message stating which geoip file we're parsing
21556 instead of just stating that we're parsing the geoip file.
21557 Implements ticket 2432.
21558 - Make sure every relay writes a state file at least every 12 hours.
21559 Previously, a relay could go for weeks without writing its state
21560 file, and on a crash could lose its bandwidth history, capacity
21561 estimates, client country statistics, and so on. Addresses bug 3012.
21562 - Relays report the number of bytes spent on answering directory
21563 requests in extra-info descriptors similar to {read,write}-history.
21564 Implements enhancement 1790.
21565 - Report only the top 10 ports in exit-port stats in order not to
21566 exceed the maximum extra-info descriptor length of 50 KB. Implements
21568 - If writing the state file to disk fails, wait up to an hour before
21569 retrying again, rather than trying again each second. Fixes bug
21570 2346; bugfix on Tor 0.1.1.3-alpha.
21571 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
21572 when we switch from being a public relay to a bridge. Otherwise
21573 there will still be clients that see the relay in their consensus,
21574 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
21576 - Update to the August 2 2011 Maxmind GeoLite Country database.
21578 o Minor features (clients):
21579 - When expiring circuits, use microsecond timers rather than
21580 one-second timers. This can avoid an unpleasant situation where a
21581 circuit is launched near the end of one second and expired right
21582 near the beginning of the next, and prevent fluctuations in circuit
21584 - If we've configured EntryNodes and our network goes away and/or all
21585 our entrynodes get marked down, optimistically retry them all when
21586 a new socks application request appears. Fixes bug 1882.
21587 - Always perform router selections using weighted relay bandwidth,
21588 even if we don't need a high capacity circuit at the time. Non-fast
21589 circuits now only differ from fast ones in that they can use relays
21590 not marked with the Fast flag. This "feature" could turn out to
21591 be a horrible bug; we should investigate more before it goes into
21593 - When we run out of directory information such that we can't build
21594 circuits, but then get enough that we can build circuits, log when
21595 we actually construct a circuit, so the user has a better chance of
21596 knowing what's going on. Fixes bug 1362.
21597 - Log SSL state transitions at debug level during handshake, and
21598 include SSL states in error messages. This may help debug future
21599 SSL handshake issues.
21601 o Minor features (directory authorities):
21602 - When a router changes IP address or port, authorities now launch
21603 a new reachability test for it. Implements ticket 1899.
21604 - Directory authorities now reject relays running any versions of
21605 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
21606 known bugs that keep RELAY_EARLY cells from working on rendezvous
21607 circuits. Followup to fix for bug 2081.
21608 - Directory authorities now reject relays running any version of Tor
21609 older than 0.2.0.26-rc. That version is the earliest that fetches
21610 current directory information correctly. Fixes bug 2156.
21611 - Directory authorities now do an immediate reachability check as soon
21612 as they hear about a new relay. This change should slightly reduce
21613 the time between setting up a relay and getting listed as running
21614 in the consensus. It should also improve the time between setting
21615 up a bridge and seeing use by bridge users.
21616 - Directory authorities no longer launch a TLS connection to every
21617 relay as they startup. Now that we have 2k+ descriptors cached,
21618 the resulting network hiccup is becoming a burden. Besides,
21619 authorities already avoid voting about Running for the first half
21620 hour of their uptime.
21621 - Directory authorities now log the source of a rejected POSTed v3
21622 networkstatus vote, so we can track failures better.
21623 - Backport code from 0.2.3.x that allows directory authorities to
21624 clean their microdescriptor caches. Needed to resolve bug 2230.
21626 o Minor features (hidden services):
21627 - Use computed circuit-build timeouts to decide when to launch
21628 parallel introduction circuits for hidden services. (Previously,
21629 we would retry after 15 seconds.)
21630 - Don't allow v0 hidden service authorities to act as clients.
21631 Required by fix for bug 3000.
21632 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
21633 by fix for bug 3000.
21634 - Make hidden services work better in private Tor networks by not
21635 requiring any uptime to join the hidden service descriptor
21636 DHT. Implements ticket 2088.
21637 - Log (at info level) when purging pieces of hidden-service-client
21638 state because of SIGNAL NEWNYM.
21640 o Minor features (controller interface):
21641 - New "GETINFO net/listeners/(type)" controller command to return
21642 a list of addresses and ports that are bound for listeners for a
21643 given connection type. This is useful when the user has configured
21644 "SocksPort auto" and the controller needs to know which port got
21645 chosen. Resolves another part of ticket 3076.
21646 - Have the controller interface give a more useful message than
21647 "Internal Error" in response to failed GETINFO requests.
21648 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
21649 event, to give information on the current rate of circuit timeouts
21650 over our stored history.
21651 - The 'EXTENDCIRCUIT' control port command can now be used with
21652 a circ id of 0 and no path. This feature will cause Tor to build
21653 a new 'fast' general purpose circuit using its own path selection
21655 - Added a BUILDTIMEOUT_SET controller event to describe changes
21656 to the circuit build timeout.
21657 - New controller command "getinfo config-text". It returns the
21658 contents that Tor would write if you send it a SAVECONF command,
21659 so the controller can write the file to disk itself.
21661 o Minor features (controller protocol):
21662 - Add a new ControlSocketsGroupWritable configuration option: when
21663 it is turned on, ControlSockets are group-writeable by the default
21664 group of the current user. Patch by Jérémy Bobbio; implements
21666 - Tor now refuses to create a ControlSocket in a directory that is
21667 world-readable (or group-readable if ControlSocketsGroupWritable
21668 is 0). This is necessary because some operating systems do not
21669 enforce permissions on an AF_UNIX sockets. Permissions on the
21670 directory holding the socket, however, seems to work everywhere.
21671 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
21672 not. This would lead to a cookie that is still not group readable.
21673 Closes bug 1843. Suggested by katmagic.
21674 - Future-proof the controller protocol a bit by ignoring keyword
21675 arguments we do not recognize.
21677 o Minor features (more useful logging):
21678 - Revise most log messages that refer to nodes by nickname to
21679 instead use the "$key=nickname at address" format. This should be
21680 more useful, especially since nicknames are less and less likely
21681 to be unique. Resolves ticket 3045.
21682 - When an HTTPS proxy reports "403 Forbidden", we now explain
21683 what it means rather than calling it an unexpected status code.
21684 Closes bug 2503. Patch from Michael Yakubovich.
21685 - Rate-limit a warning about failures to download v2 networkstatus
21686 documents. Resolves part of bug 1352.
21687 - Rate-limit the "your application is giving Tor only an IP address"
21688 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
21689 - Rate-limit "Failed to hand off onionskin" warnings.
21690 - When logging a rate-limited warning, we now mention how many messages
21691 got suppressed since the last warning.
21692 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
21693 2 no signature, 4 required" messages about consensus signatures
21694 easier to read, and make sure they get logged at the same severity
21695 as the messages explaining which keys are which. Fixes bug 1290.
21696 - Don't warn when we have a consensus that we can't verify because
21697 of missing certificates, unless those certificates are ones
21698 that we have been trying and failing to download. Fixes bug 1145.
21700 o Minor features (log domains):
21701 - Add documentation for configuring logging at different severities in
21702 different log domains. We've had this feature since 0.2.1.1-alpha,
21703 but for some reason it never made it into the manpage. Fixes
21705 - Make it simpler to specify "All log domains except for A and B".
21706 Previously you needed to say "[*,~A,~B]". Now you can just say
21708 - Add a "LogMessageDomains 1" option to include the domains of log
21709 messages along with the messages. Without this, there's no way
21710 to use log domains without reading the source or doing a lot
21712 - Add a new "Handshake" log domain for activities that happen
21713 during the TLS handshake.
21715 o Minor features (build process):
21716 - Make compilation with clang possible when using
21717 "--enable-gcc-warnings" by removing two warning options that clang
21718 hasn't implemented yet and by fixing a few warnings. Resolves
21720 - Detect platforms that brokenly use a signed size_t, and refuse to
21721 build there. Found and analyzed by doorss and rransom.
21722 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
21724 - Add support for statically linking zlib by specifying
21725 "--enable-static-zlib", to go with our support for statically
21726 linking openssl and libevent. Resolves bug 1358.
21727 - Instead of adding the svn revision to the Tor version string, report
21728 the git commit (when we're building from a git checkout).
21729 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
21731 - New --digests command-line switch to output the digests of the
21732 source files Tor was built with.
21733 - Generate our manpage and HTML documentation using Asciidoc. This
21734 change should make it easier to maintain the documentation, and
21735 produce nicer HTML. The build process fails if asciidoc cannot
21736 be found and building with asciidoc isn't disabled (via the
21737 "--disable-asciidoc" argument to ./configure. Skipping the manpage
21738 speeds up the build considerably.
21740 o Minor features (options / torrc):
21741 - Warn when the same option is provided more than once in a torrc
21742 file, on the command line, or in a single SETCONF statement, and
21743 the option is one that only accepts a single line. Closes bug 1384.
21744 - Warn when the user configures two HiddenServiceDir lines that point
21745 to the same directory. Bugfix on 0.0.6 (the version introducing
21746 HiddenServiceDir); fixes bug 3289.
21747 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
21748 do individual connection-level rate limiting of clients. The torrc
21749 config options with the same names trump the consensus params, if
21750 both are present. Replaces the old "bwconnrate" and "bwconnburst"
21751 consensus params which were broken from 0.2.2.7-alpha through
21752 0.2.2.14-alpha. Closes bug 1947.
21753 - New config option "WarnUnsafeSocks 0" disables the warning that
21754 occurs whenever Tor receives a socks handshake using a version of
21755 the socks protocol that can only provide an IP address (rather
21756 than a hostname). Setups that do DNS locally over Tor are fine,
21757 and we shouldn't spam the logs in that case.
21758 - New config option "CircuitStreamTimeout" to override our internal
21759 timeout schedule for how many seconds until we detach a stream from
21760 a circuit and try a new circuit. If your network is particularly
21761 slow, you might want to set this to a number like 60.
21762 - New options for SafeLogging to allow scrubbing only log messages
21763 generated while acting as a relay. Specify "SafeLogging relay" if
21764 you want to ensure that only messages known to originate from
21765 client use of the Tor process will be logged unsafely.
21766 - Time and memory units in the configuration file can now be set to
21767 fractional units. For example, "2.5 GB" is now a valid value for
21769 - Support line continuations in the torrc config file. If a line
21770 ends with a single backslash character, the newline is ignored, and
21771 the configuration value is treated as continuing on the next line.
21774 o Minor features (unit tests):
21775 - Revise our unit tests to use the "tinytest" framework, so we
21776 can run tests in their own processes, have smarter setup/teardown
21777 code, and so on. The unit test code has moved to its own
21778 subdirectory, and has been split into multiple modules.
21779 - Add a unit test for cross-platform directory-listing code.
21780 - Add some forgotten return value checks during unit tests. Found
21782 - Use GetTempDir to find the proper temporary directory location on
21783 Windows when generating temporary files for the unit tests. Patch
21786 o Minor features (misc):
21787 - The "torify" script now uses torsocks where available.
21788 - Make Libevent log messages get delivered to controllers later,
21789 and not from inside the Libevent log handler. This prevents unsafe
21790 reentrant Libevent calls while still letting the log messages
21792 - Certain Tor clients (such as those behind check.torproject.org) may
21793 want to fetch the consensus in an extra early manner. To enable this
21794 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
21795 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
21796 as only certain clients who must have this information sooner should
21798 - Expand homedirs passed to tor-checkkey. This should silence a
21799 coverity complaint about passing a user-supplied string into
21800 open() without checking it.
21801 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
21802 used on bridges, and it makes bridge scanning somewhat easier.
21803 - Create the /var/run/tor directory on startup on OpenSUSE if it is
21804 not already created. Patch from Andreas Stieger. Fixes bug 2573.
21806 o Minor bugfixes (relays):
21807 - When a relay decides that its DNS is too broken for it to serve
21808 as an exit server, it advertised itself as a non-exit, but
21809 continued to act as an exit. This could create accidental
21810 partitioning opportunities for users. Instead, if a relay is
21811 going to advertise reject *:* as its exit policy, it should
21812 really act with exit policy "reject *:*". Fixes bug 2366.
21813 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
21814 - Publish a router descriptor even if generating an extra-info
21815 descriptor fails. Previously we would not publish a router
21816 descriptor without an extra-info descriptor; this can cause fast
21817 exit relays collecting exit-port statistics to drop from the
21818 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
21819 - When we're trying to guess whether we know our IP address as
21820 a relay, we would log various ways that we failed to guess
21821 our address, but never log that we ended up guessing it
21822 successfully. Now add a log line to help confused and anxious
21823 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
21824 - For bandwidth accounting, calculate our expected bandwidth rate
21825 based on the time during which we were active and not in
21826 soft-hibernation during the last interval. Previously, we were
21827 also considering the time spent in soft-hibernation. If this
21828 was a long time, we would wind up underestimating our bandwidth
21829 by a lot, and skewing our wakeup time towards the start of the
21830 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
21831 - Demote a confusing TLS warning that relay operators might get when
21832 someone tries to talk to their ORPort. It is not the operator's
21833 fault, nor can they do anything about it. Fixes bug 1364; bugfix
21835 - Change "Application request when we're believed to be offline."
21836 notice to "Application request when we haven't used client
21837 functionality lately.", to clarify that it's not an error. Bugfix
21838 on 0.0.9.3; fixes bug 1222.
21840 o Minor bugfixes (bridges):
21841 - When a client starts or stops using bridges, never use a circuit
21842 that was built before the configuration change. This behavior could
21843 put at risk a user who uses bridges to ensure that her traffic
21844 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
21846 - Do not reset the bridge descriptor download status every time we
21847 re-parse our configuration or get a configuration change. Fixes
21848 bug 3019; bugfix on 0.2.0.3-alpha.
21849 - Users couldn't configure a regular relay to be their bridge. It
21850 didn't work because when Tor fetched the bridge descriptor, it found
21851 that it already had it, and didn't realize that the purpose of the
21852 descriptor had changed. Now we replace routers with a purpose other
21853 than bridge with bridge descriptors when fetching them. Bugfix on
21854 0.1.1.9-alpha. Fixes bug 1776.
21855 - In the special case where you configure a public exit relay as your
21856 bridge, Tor would be willing to use that exit relay as the last
21857 hop in your circuit as well. Now we fail that circuit instead.
21858 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
21860 o Minor bugfixes (clients):
21861 - We now ask the other side of a stream (the client or the exit)
21862 for more data on that stream when the amount of queued data on
21863 that stream dips low enough. Previously, we wouldn't ask the
21864 other side for more data until either it sent us more data (which
21865 it wasn't supposed to do if it had exhausted its window!) or we
21866 had completely flushed all our queued data. This flow control fix
21867 should improve throughput. Fixes bug 2756; bugfix on the earliest
21868 released versions of Tor (svn commit r152).
21869 - When a client finds that an origin circuit has run out of 16-bit
21870 stream IDs, we now mark it as unusable for new streams. Previously,
21871 we would try to close the entire circuit. Bugfix on 0.0.6.
21872 - Make it explicit that we don't cannibalize one-hop circuits. This
21873 happens in the wild, but doesn't turn out to be a problem because
21874 we fortunately don't use those circuits. Many thanks to outofwords
21875 for the initial analysis and to swissknife who confirmed that
21876 two-hop circuits are actually created.
21877 - Resolve an edge case in path weighting that could make us misweight
21878 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
21879 - Make the DNSPort option work with libevent 2.x. Don't alter the
21880 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
21882 o Minor bugfixes (directory authorities):
21883 - Make directory authorities more accurate at recording when
21884 relays that have failed several reachability tests became
21885 unreachable, so we can provide more accuracy at assigning Stable,
21886 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
21887 - Directory authorities are now more robust to hops back in time
21888 when calculating router stability. Previously, if a run of uptime
21889 or downtime appeared to be negative, the calculation could give
21890 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
21892 - Directory authorities will now attempt to download consensuses
21893 if their own efforts to make a live consensus have failed. This
21894 change means authorities that restart will fetch a valid
21895 consensus, and it means authorities that didn't agree with the
21896 current consensus will still fetch and serve it if it has enough
21897 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
21898 - Never vote for a server as "Running" if we have a descriptor for
21899 it claiming to be hibernating, and that descriptor was published
21900 more recently than our last contact with the server. Bugfix on
21901 0.2.0.3-alpha; fixes bug 911.
21902 - Directory authorities no longer change their opinion of, or vote on,
21903 whether a router is Running, unless they have themselves been
21904 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
21907 o Minor bugfixes (hidden services):
21908 - Log malformed requests for rendezvous descriptors as protocol
21909 warnings, not warnings. Also, use a more informative log message
21910 in case someone sees it at log level warning without prior
21911 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
21912 - Accept hidden service descriptors if we think we might be a hidden
21913 service directory, regardless of what our consensus says. This
21914 helps robustness, since clients and hidden services can sometimes
21915 have a more up-to-date view of the network consensus than we do,
21916 and if they think that the directory authorities list us a HSDir,
21917 we might actually be one. Related to bug 2732; bugfix on
21919 - Correct the warning displayed when a rendezvous descriptor exceeds
21920 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
21922 - Clients and hidden services now use HSDir-flagged relays for hidden
21923 service descriptor downloads and uploads even if the relays have no
21924 DirPort set and the client has disabled TunnelDirConns. This will
21925 eventually allow us to give the HSDir flag to relays with no
21926 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
21927 - Only limit the lengths of single HS descriptors, even when multiple
21928 HS descriptors are published to an HSDir relay in a single POST
21929 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
21931 o Minor bugfixes (controllers):
21932 - Allow GETINFO fingerprint to return a fingerprint even when
21933 we have not yet built a router descriptor. Fixes bug 3577;
21934 bugfix on 0.2.0.1-alpha.
21935 - Send a SUCCEEDED stream event to the controller when a reverse
21936 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
21937 discovered by katmagic.
21938 - Remove a trailing asterisk from "exit-policy/default" in the
21939 output of the control port command "GETINFO info/names". Bugfix
21941 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
21942 2917. Bugfix on 0.1.1.1-alpha.
21943 - When we restart our relay, we might get a successful connection
21944 from the outside before we've started our reachability tests,
21945 triggering a warning: "ORPort found reachable, but I have no
21946 routerinfo yet. Failing to inform controller of success." This
21947 bug was harmless unless Tor is running under a controller
21948 like Vidalia, in which case the controller would never get a
21949 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
21951 - When a controller changes TrackHostExits, remove mappings for
21952 hosts that should no longer have their exits tracked. Bugfix on
21954 - When a controller changes VirtualAddrNetwork, remove any mappings
21955 for hosts that were automapped to the old network. Bugfix on
21957 - When a controller changes one of the AutomapHosts* options, remove
21958 any mappings for hosts that should no longer be automapped. Bugfix
21960 - Fix an off-by-one error in calculating some controller command
21961 argument lengths. Fortunately, this mistake is harmless since
21962 the controller code does redundant NUL termination too. Found by
21963 boboper. Bugfix on 0.1.1.1-alpha.
21964 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
21965 would return "551 Internal error" rather than "552 Unrecognized key
21966 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
21967 - Don't spam the controller with events when we have no file
21968 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
21969 for log messages was already solved from bug 748.)
21970 - Emit a GUARD DROPPED controller event for a case we missed.
21971 - Ensure DNS requests launched by "RESOLVE" commands from the
21972 controller respect the __LeaveStreamsUnattached setconf options. The
21973 same goes for requests launched via DNSPort or transparent
21974 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
21976 o Minor bugfixes (config options):
21977 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
21978 Change the limit to 512 characters by removing base64 newlines.
21979 Fixes bug 2752. Fix by Michael Yakubovich.
21980 - Complain if PublishServerDescriptor is given multiple arguments that
21981 include 0 or 1. This configuration will be rejected in the future.
21982 Bugfix on 0.2.0.1-alpha; closes bug 1107.
21983 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
21984 Bugfix on 0.2.0.13-alpha; closes bug 928.
21986 o Minor bugfixes (log subsystem fixes):
21987 - When unable to format an address as a string, report its value
21988 as "???" rather than reusing the last formatted address. Bugfix
21990 - Be more consistent in our treatment of file system paths. "~" should
21991 get expanded to the user's home directory in the Log config option.
21992 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
21993 feature for the -f and --DataDirectory options.
21995 o Minor bugfixes (memory management):
21996 - Don't stack-allocate the list of supplementary GIDs when we're
21997 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
21998 could take up to 256K, which is way too much stack. Found by
21999 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
22000 - Save a couple bytes in memory allocation every time we escape
22001 certain characters in a string. Patch from Florian Zumbiehl.
22003 o Minor bugfixes (protocol correctness):
22004 - When checking for 1024-bit keys, check for 1024 bits, not 128
22005 bytes. This allows Tor to correctly discard keys of length 1017
22006 through 1023. Bugfix on 0.0.9pre5.
22007 - Require that introduction point keys and onion handshake keys
22008 have a public exponent of 65537. Starts to fix bug 3207; bugfix
22010 - Handle SOCKS messages longer than 128 bytes long correctly, rather
22011 than waiting forever for them to finish. Fixes bug 2330; bugfix
22012 on 0.2.0.16-alpha. Found by doorss.
22013 - Never relay a cell for a circuit we have already destroyed.
22014 Between marking a circuit as closeable and finally closing it,
22015 it may have been possible for a few queued cells to get relayed,
22016 even though they would have been immediately dropped by the next
22017 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
22018 - Never queue a cell for a circuit that's already been marked
22020 - Fix a spec conformance issue: the network-status-version token
22021 must be the first token in a v3 consensus or vote. Discovered by
22022 "parakeep". Bugfix on 0.2.0.3-alpha.
22023 - A networkstatus vote must contain exactly one signature. Spec
22024 conformance issue. Bugfix on 0.2.0.3-alpha.
22025 - When asked about a DNS record type we don't support via a
22026 client DNSPort, reply with NOTIMPL rather than an empty
22027 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
22028 - Make more fields in the controller protocol case-insensitive, since
22029 control-spec.txt said they were.
22031 o Minor bugfixes (log messages):
22032 - Fix a log message that said "bits" while displaying a value in
22033 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
22035 - Downgrade "no current certificates known for authority" message from
22036 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
22037 - Correctly describe errors that occur when generating a TLS object.
22038 Previously we would attribute them to a failure while generating a
22039 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
22041 - Fix an instance where a Tor directory mirror might accidentally
22042 log the IP address of a misbehaving Tor client. Bugfix on
22044 - Stop logging at severity 'warn' when some other Tor client tries
22045 to establish a circuit with us using weak DH keys. It's a protocol
22046 violation, but that doesn't mean ordinary users need to hear about
22047 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
22048 - If your relay can't keep up with the number of incoming create
22049 cells, it would log one warning per failure into your logs. Limit
22050 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
22052 o Minor bugfixes (build fixes):
22053 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
22054 - When warning about missing zlib development packages during compile,
22055 give the correct package names. Bugfix on 0.2.0.1-alpha.
22056 - Fix warnings that newer versions of autoconf produce during
22057 ./autogen.sh. These warnings appear to be harmless in our case,
22058 but they were extremely verbose. Fixes bug 2020.
22059 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
22062 o Minor bugfixes (portability):
22063 - Write several files in text mode, on OSes that distinguish text
22064 mode from binary mode (namely, Windows). These files are:
22065 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
22066 that collect those statistics; 'client_keys' and 'hostname' for
22067 hidden services that use authentication; and (in the tor-gencert
22068 utility) newly generated identity and signing keys. Previously,
22069 we wouldn't specify text mode or binary mode, leading to an
22070 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
22071 the DirRecordUsageByCountry option which would have triggered
22072 the assertion failure was added), although this assertion failure
22073 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
22074 - Selectively disable deprecation warnings on OS X because Lion
22075 started deprecating the shipped copy of openssl. Fixes bug 3643.
22076 - Use a wide type to hold sockets when built for 64-bit Windows.
22078 - Fix an issue that prevented static linking of libevent on
22079 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
22080 where we introduced the "--with-static-libevent" configure option.
22081 - Fix a bug with our locking implementation on Windows that couldn't
22082 correctly detect when a file was already locked. Fixes bug 2504,
22083 bugfix on 0.2.1.6-alpha.
22084 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
22086 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
22087 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
22090 o Minor bugfixes (code correctness):
22091 - Always NUL-terminate the sun_path field of a sockaddr_un before
22092 passing it to the kernel. (Not a security issue: kernels are
22093 smart enough to reject bad sockaddr_uns.) Found by Coverity;
22094 CID #428. Bugfix on Tor 0.2.0.3-alpha.
22095 - Make connection_printf_to_buf()'s behavior sane. Its callers
22096 expect it to emit a CRLF iff the format string ends with CRLF;
22097 it actually emitted a CRLF iff (a) the format string ended with
22098 CRLF or (b) the resulting string was over 1023 characters long or
22099 (c) the format string did not end with CRLF *and* the resulting
22100 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
22101 fixes part of bug 3407.
22102 - Make send_control_event_impl()'s behavior sane. Its callers
22103 expect it to always emit a CRLF at the end of the string; it
22104 might have emitted extra control characters as well. Bugfix on
22105 0.1.1.9-alpha; fixes another part of bug 3407.
22106 - Make crypto_rand_int() check the value of its input correctly.
22107 Previously, it accepted values up to UINT_MAX, but could return a
22108 negative number if given a value above INT_MAX+1. Found by George
22109 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
22110 - Fix a potential null-pointer dereference while computing a
22111 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
22113 - If we fail to compute the identity digest of a v3 legacy keypair,
22114 warn, and don't use a buffer-full of junk instead. Bugfix on
22115 0.2.1.1-alpha; fixes bug 3106.
22116 - Resolve an untriggerable issue in smartlist_string_num_isin(),
22117 where if the function had ever in the future been used to check
22118 for the presence of a too-large number, it would have given an
22119 incorrect result. (Fortunately, we only used it for 16-bit
22120 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
22121 - Be more careful about reporting the correct error from a failed
22122 connect() system call. Under some circumstances, it was possible to
22123 look at an incorrect value for errno when sending the end reason.
22124 Bugfix on 0.1.0.1-rc.
22125 - Correctly handle an "impossible" overflow cases in connection byte
22126 counting, where we write or read more than 4GB on an edge connection
22127 in a single second. Bugfix on 0.1.2.8-beta.
22128 - Avoid a double mark-for-free warning when failing to attach a
22129 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
22131 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
22132 found by "cypherpunks". This bug was introduced before the first
22133 Tor release, in svn commit r110.
22134 - Fix a bug in bandwidth history state parsing that could have been
22135 triggered if a future version of Tor ever changed the timing
22136 granularity at which bandwidth history is measured. Bugfix on
22137 Tor 0.1.1.11-alpha.
22138 - Add assertions to check for overflow in arguments to
22139 base32_encode() and base32_decode(); fix a signed-unsigned
22140 comparison there too. These bugs are not actually reachable in Tor,
22141 but it's good to prevent future errors too. Found by doorss.
22142 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
22144 - Set target port in get_interface_address6() correctly. Bugfix
22145 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
22146 - Fix an impossible-to-actually-trigger buffer overflow in relay
22147 descriptor generation. Bugfix on 0.1.0.15.
22148 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
22150 o Minor bugfixes (code improvements):
22151 - After we free an internal connection structure, overwrite it
22152 with a different memory value than we use for overwriting a freed
22153 internal circuit structure. Should help with debugging. Suggested
22155 - If OpenSSL fails to make a duplicate of a private or public key, log
22156 an error message and try to exit cleanly. May help with debugging
22157 if bug 1209 ever remanifests.
22158 - Some options used different conventions for uppercasing of acronyms
22159 when comparing manpage and source. Fix those in favor of the
22160 manpage, as it makes sense to capitalize acronyms.
22161 - Take a first step towards making or.h smaller by splitting out
22162 function definitions for all source files in src/or/. Leave
22163 structures and defines in or.h for now.
22164 - Remove a few dead assignments during router parsing. Found by
22166 - Don't use 1-bit wide signed bit fields. Found by coverity.
22167 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
22168 None of the cases where we did this before were wrong, but by making
22169 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
22170 - The memarea code now uses a sentinel value at the end of each area
22171 to make sure nothing writes beyond the end of an area. This might
22172 help debug some conceivable causes of bug 930.
22173 - Always treat failure to allocate an RSA key as an unrecoverable
22175 - Add some more defensive programming for architectures that can't
22176 handle unaligned integer accesses. We don't know of any actual bugs
22177 right now, but that's the best time to fix them. Fixes bug 1943.
22179 o Minor bugfixes (misc):
22180 - Fix a rare bug in rend_fn unit tests: we would fail a test when
22181 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
22182 on 0.2.0.10-alpha; fixes bug 1808.
22183 - Where available, use Libevent 2.0's periodic timers so that our
22184 once-per-second cleanup code gets called even more closely to
22185 once per second than it would otherwise. Fixes bug 943.
22186 - Ignore OutboundBindAddress when connecting to localhost.
22187 Connections to localhost need to come _from_ localhost, or else
22188 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
22190 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
22192 - If any of the v3 certs we download are unparseable, we should
22193 actually notice the failure so we don't retry indefinitely. Bugfix
22194 on 0.2.0.x; reported by "rotator".
22195 - When Tor fails to parse a descriptor of any kind, dump it to disk.
22196 Might help diagnosing bug 1051.
22197 - Make our 'torify' script more portable; if we have only one of
22198 'torsocks' or 'tsocks' installed, don't complain to the user;
22199 and explain our warning about tsocks better.
22200 - Fix some urls in the exit notice file and make it XHTML1.1 strict
22201 compliant. Based on a patch from Christian Kujau.
22203 o Documentation changes:
22204 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
22205 - Resolve all doxygen warnings except those for missing documentation.
22207 - Add doxygen documentation for more functions, fields, and types.
22208 - Convert the HACKING file to asciidoc, and add a few new sections
22209 to it, explaining how we use Git, how we make changelogs, and
22210 what should go in a patch.
22211 - Document the default socks host and port (127.0.0.1:9050) for
22213 - Removed some unnecessary files from the source distribution. The
22214 AUTHORS file has now been merged into the people page on the
22215 website. The roadmaps and design doc can now be found in the
22216 projects directory in svn.
22218 o Deprecated and removed features (config):
22219 - Remove the torrc.complete file. It hasn't been kept up to date
22220 and users will have better luck checking out the manpage.
22221 - Remove the HSAuthorityRecordStats option that version 0 hidden
22222 service authorities could use to track statistics of overall v0
22223 hidden service usage.
22224 - Remove the obsolete "NoPublish" option; it has been flagged
22225 as obsolete and has produced a warning since 0.1.1.18-rc.
22226 - Caches no longer download and serve v2 networkstatus documents
22227 unless FetchV2Networkstatus flag is set: these documents haven't
22228 haven't been used by clients or relays since 0.2.0.x. Resolves
22231 o Deprecated and removed features (controller):
22232 - The controller no longer accepts the old obsolete "addr-mappings/"
22233 or "unregistered-servers-" GETINFO values.
22234 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
22235 always on; using them is necessary for correct forward-compatible
22238 o Deprecated and removed features (misc):
22239 - Hidden services no longer publish version 0 descriptors, and clients
22240 do not request or use version 0 descriptors. However, the old hidden
22241 service authorities still accept and serve version 0 descriptors
22242 when contacted by older hidden services/clients.
22243 - Remove undocumented option "-F" from tor-resolve: it hasn't done
22244 anything since 0.2.1.16-rc.
22245 - Remove everything related to building the expert bundle for OS X.
22246 It has confused many users, doesn't work right on OS X 10.6,
22247 and is hard to get rid of once installed. Resolves bug 1274.
22248 - Remove support for .noconnect style addresses. Nobody was using
22249 them, and they provided another avenue for detecting Tor users
22250 via application-level web tricks.
22251 - When we fixed bug 1038 we had to put in a restriction not to send
22252 RELAY_EARLY cells on rend circuits. This was necessary as long
22253 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
22254 active. Now remove this obsolete check. Resolves bug 2081.
22255 - Remove workaround code to handle directory responses from servers
22256 that had bug 539 (they would send HTTP status 503 responses _and_
22257 send a body too). Since only server versions before
22258 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
22259 keep the workaround in place.
22260 - Remove the old 'fuzzy time' logic. It was supposed to be used for
22261 handling calculations where we have a known amount of clock skew and
22262 an allowed amount of unknown skew. But we only used it in three
22263 places, and we never adjusted the known/unknown skew values. This is
22264 still something we might want to do someday, but if we do, we'll
22265 want to do it differently.
22266 - Remove the "--enable-iphone" option to ./configure. According to
22267 reports from Marco Bonetti, Tor builds fine without any special
22268 tweaking on recent iPhone SDK versions.
22271 Changes in version 0.2.1.30 - 2011-02-23
22272 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
22273 change is a slight tweak to Tor's TLS handshake that makes relays
22274 and bridges that run this new version reachable from Iran again.
22275 We don't expect this tweak will win the arms race long-term, but it
22276 buys us time until we roll out a better solution.
22279 - Stop sending a CLOCK_SKEW controller status event whenever
22280 we fetch directory information from a relay that has a wrong clock.
22281 Instead, only inform the controller when it's a trusted authority
22282 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
22283 the rest of bug 1074.
22284 - Fix a bounds-checking error that could allow an attacker to
22285 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
22286 Found by "piebeer".
22287 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
22288 Tor would ignore their RelayBandwidthBurst setting,
22289 potentially using more bandwidth than expected. Bugfix on
22290 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
22291 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
22292 hidserv" in her torrc. The 'hidserv' argument never controlled
22293 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
22296 - Adjust our TLS Diffie-Hellman parameters to match those used by
22298 - Update to the February 1 2011 Maxmind GeoLite Country database.
22301 - Check for and reject overly long directory certificates and
22302 directory tokens before they have a chance to hit any assertions.
22303 Bugfix on 0.2.1.28. Found by "doorss".
22304 - Bring the logic that gathers routerinfos and assesses the
22305 acceptability of circuits into line. This prevents a Tor OP from
22306 getting locked in a cycle of choosing its local OR as an exit for a
22307 path (due to a .exit request) and then rejecting the circuit because
22308 its OR is not listed yet. It also prevents Tor clients from using an
22309 OR running in the same instance as an exit (due to a .exit request)
22310 if the OR does not meet the same requirements expected of an OR
22311 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
22313 o Packaging changes:
22314 - Stop shipping the Tor specs files and development proposal documents
22315 in the tarball. They are now in a separate git repository at
22316 git://git.torproject.org/torspec.git
22317 - Do not include Git version tags as though they are SVN tags when
22318 generating a tarball from inside a repository that has switched
22319 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
22322 Changes in version 0.2.1.29 - 2011-01-15
22323 Tor 0.2.1.29 continues our recent code security audit work. The main
22324 fix resolves a remote heap overflow vulnerability that can allow remote
22325 code execution. Other fixes address a variety of assert and crash bugs,
22326 most of which we think are hard to exploit remotely.
22328 o Major bugfixes (security):
22329 - Fix a heap overflow bug where an adversary could cause heap
22330 corruption. This bug probably allows remote code execution
22331 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
22333 - Prevent a denial-of-service attack by disallowing any
22334 zlib-compressed data whose compression factor is implausibly
22335 high. Fixes part of bug 2324; reported by "doorss".
22336 - Zero out a few more keys in memory before freeing them. Fixes
22337 bug 2384 and part of bug 2385. These key instances found by
22338 "cypherpunks", based on Andrew Case's report about being able
22339 to find sensitive data in Tor's memory space if you have enough
22340 permissions. Bugfix on 0.0.2pre9.
22342 o Major bugfixes (crashes):
22343 - Prevent calls to Libevent from inside Libevent log handlers.
22344 This had potential to cause a nasty set of crashes, especially
22345 if running Libevent with debug logging enabled, and running
22346 Tor with a controller watching for low-severity log messages.
22347 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
22348 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
22349 underflow errors there too. Fixes the other part of bug 2324.
22350 - Fix a bug where we would assert if we ever had a
22351 cached-descriptors.new file (or another file read directly into
22352 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
22353 on 0.2.1.25. Found by doorss.
22354 - Fix some potential asserts and parsing issues with grossly
22355 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
22358 o Minor bugfixes (other):
22359 - Fix a bug with handling misformed replies to reverse DNS lookup
22360 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
22361 bug reported by doorss.
22362 - Fix compilation on mingw when a pthreads compatibility library
22363 has been installed. (We don't want to use it, so we shouldn't
22364 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
22365 - Fix a bug where we would declare that we had run out of virtual
22366 addresses when the address space was only half-exhausted. Bugfix
22368 - Correctly handle the case where AutomapHostsOnResolve is set but
22369 no virtual addresses are available. Fixes bug 2328; bugfix on
22370 0.1.2.1-alpha. Bug found by doorss.
22371 - Correctly handle wrapping around when we run out of virtual
22372 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
22375 - Update to the January 1 2011 Maxmind GeoLite Country database.
22376 - Introduce output size checks on all of our decryption functions.
22379 - Tor does not build packages correctly with Automake 1.6 and earlier;
22380 added a check to Makefile.am to make sure that we're building with
22381 Automake 1.7 or later.
22382 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
22383 because we built it with a too-old version of automake. Thus that
22384 release broke ./configure --enable-openbsd-malloc, which is popular
22385 among really fast exit relays on Linux.
22388 Changes in version 0.2.1.28 - 2010-12-17
22389 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
22390 exploitable bugs. We also took this opportunity to change the IP address
22391 for one of our directory authorities, and to update the geoip database
22395 - Fix a remotely exploitable bug that could be used to crash instances
22396 of Tor remotely by overflowing on the heap. Remote-code execution
22397 hasn't been confirmed, but can't be ruled out. Everyone should
22398 upgrade. Bugfix on the 0.1.1 series and later.
22400 o Directory authority changes:
22401 - Change IP address and ports for gabelmoo (v3 directory authority).
22404 - Update to the December 1 2010 Maxmind GeoLite Country database.
22407 Changes in version 0.2.1.27 - 2010-11-23
22408 Yet another OpenSSL security patch broke its compatibility with Tor:
22409 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
22410 also took this opportunity to fix several crash bugs, integrate a new
22411 directory authority, and update the bundled GeoIP database.
22414 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
22415 No longer set the tlsext_host_name extension on server SSL objects;
22416 but continue to set it on client SSL objects. Our goal in setting
22417 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
22418 bugfix on 0.2.1.1-alpha.
22419 - Do not log messages to the controller while shrinking buffer
22420 freelists. Doing so would sometimes make the controller connection
22421 try to allocate a buffer chunk, which would mess up the internals
22422 of the freelist and cause an assertion failure. Fixes bug 1125;
22423 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
22424 - Learn our external IP address when we're a relay or bridge, even if
22425 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
22426 where we introduced bridge relays that don't need to publish to
22427 be useful. Fixes bug 2050.
22428 - Do even more to reject (and not just ignore) annotations on
22429 router descriptors received anywhere but from the cache. Previously
22430 we would ignore such annotations at first, but cache them to disk
22431 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
22432 - When you're using bridges and your network goes away and your
22433 bridges get marked as down, recover when you attempt a new socks
22434 connection (if the network is back), rather than waiting up to an
22435 hour to try fetching new descriptors for your bridges. Bugfix on
22436 0.2.0.3-alpha; fixes bug 1981.
22439 - Move to the November 2010 Maxmind GeoLite country db (rather
22440 than the June 2009 ip-to-country GeoIP db) for our statistics that
22441 count how many users relays are seeing from each country. Now we'll
22442 have more accurate data, especially for many African countries.
22444 o New directory authorities:
22445 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
22449 - Fix an assertion failure that could occur in directory caches or
22450 bridge users when using a very short voting interval on a testing
22451 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
22453 - Enforce multiplicity rules when parsing annotations. Bugfix on
22454 0.2.0.8-alpha. Found by piebeer.
22455 - Allow handshaking OR connections to take a full KeepalivePeriod
22456 seconds to handshake. Previously, we would close them after
22457 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
22458 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
22460 - When building with --enable-gcc-warnings on OpenBSD, disable
22461 warnings in system headers. This makes --enable-gcc-warnings
22462 pass on OpenBSD 4.8.
22465 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
22466 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
22467 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
22468 Servers can start sending this code when enough clients recognize
22469 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
22470 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
22471 Patch from mingw-san.
22474 - Remove the old debian/ directory from the main Tor distribution.
22475 The official Tor-for-debian git repository lives at the URL
22476 https://git.torproject.org/debian/tor.git
22477 - Stop shipping the old doc/website/ directory in the tarball. We
22478 changed the website format in late 2010, and what we shipped in
22479 0.2.1.26 really wasn't that useful anyway.
22482 Changes in version 0.2.1.26 - 2010-05-02
22483 Tor 0.2.1.26 addresses the recent connection and memory overload
22484 problems we've been seeing on relays, especially relays with their
22485 DirPort open. If your relay has been crashing, or you turned it off
22486 because it used too many resources, give this release a try.
22488 This release also fixes yet another instance of broken OpenSSL libraries
22489 that was causing some relays to drop out of the consensus.
22492 - Teach relays to defend themselves from connection overload. Relays
22493 now close idle circuits early if it looks like they were intended
22494 for directory fetches. Relays are also more aggressive about closing
22495 TLS connections that have no circuits on them. Such circuits are
22496 unlikely to be re-used, and tens of thousands of them were piling
22497 up at the fast relays, causing the relays to run out of sockets
22498 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
22499 their directory fetches over TLS).
22500 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
22501 that claim to be earlier than 0.9.8m, but which have in reality
22502 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
22503 behavior. Possible fix for some cases of bug 1346.
22504 - Directory mirrors were fetching relay descriptors only from v2
22505 directory authorities, rather than v3 authorities like they should.
22506 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
22507 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
22510 - Finally get rid of the deprecated and now harmful notion of "clique
22511 mode", where directory authorities maintain TLS connections to
22515 - In the util/threads test, no longer free the test_mutex before all
22516 worker threads have finished. Bugfix on 0.2.1.6-alpha.
22517 - The master thread could starve the worker threads quite badly on
22518 certain systems, causing them to run only partially in the allowed
22519 window. This resulted in test failures. Now the master thread sleeps
22520 occasionally for a few microseconds while the two worker-threads
22521 compete for the mutex. Bugfix on 0.2.0.1-alpha.
22524 Changes in version 0.2.1.25 - 2010-03-16
22525 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
22526 prevent relays from guessing their IP address correctly. It also fixes
22527 several minor potential security bugs.
22530 - Fix a regression from our patch for bug 1244 that caused relays
22531 to guess their IP address incorrectly if they didn't set Address
22532 in their torrc and/or their address fails to resolve. Bugfix on
22533 0.2.1.23; fixes bug 1269.
22534 - When freeing a session key, zero it out completely. We only zeroed
22535 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
22536 patched by ekir. Fixes bug 1254.
22539 - Fix a dereference-then-NULL-check sequence when publishing
22540 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
22542 - Fix another dereference-then-NULL-check sequence. Bugfix on
22543 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
22544 - Make sure we treat potentially not NUL-terminated strings correctly.
22545 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
22548 Changes in version 0.2.1.24 - 2010-02-21
22549 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
22553 - Work correctly out-of-the-box with even more vendor-patched versions
22554 of OpenSSL. In particular, make it so Debian and OS X don't need
22555 customized patches to run/build.
22558 Changes in version 0.2.1.23 - 2010-02-13
22559 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
22560 again on the latest OS X, and updates the location of a directory
22563 o Major bugfixes (performance):
22564 - We were selecting our guards uniformly at random, and then weighting
22565 which of our guards we'd use uniformly at random. This imbalance
22566 meant that Tor clients were severely limited on throughput (and
22567 probably latency too) by the first hop in their circuit. Now we
22568 select guards weighted by currently advertised bandwidth. We also
22569 automatically discard guards picked using the old algorithm. Fixes
22570 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
22573 - Make Tor work again on the latest OS X: when deciding whether to
22574 use strange flags to turn TLS renegotiation on, detect the OpenSSL
22575 version at run-time, not compile time. We need to do this because
22576 Apple doesn't update its dev-tools headers when it updates its
22577 libraries in a security patch.
22578 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
22579 that could happen on 32-bit platforms with 64-bit time_t. Also fix
22580 a memory leak when requesting a hidden service descriptor we've
22581 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
22585 - Refactor resolve_my_address() to not use gethostbyname() anymore.
22586 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
22589 - Avoid a mad rush at the beginning of each month when each client
22590 rotates half of its guards. Instead we spread the rotation out
22591 throughout the month, but we still avoid leaving a precise timestamp
22592 in the state file about when we first picked the guard. Improves
22593 over the behavior introduced in 0.1.2.17.
22596 Changes in version 0.2.1.22 - 2010-01-19
22597 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
22598 authorities -- it would tell you its whole history of bridge descriptors
22599 if you make the right directory request. This stable update also
22600 rotates two of the seven v3 directory authority keys and locations.
22602 o Directory authority changes:
22603 - Rotate keys (both v3 identity and relay identity) for moria1
22607 - Stop bridge directory authorities from answering dbg-stability.txt
22608 directory queries, which would let people fetch a list of all
22609 bridge identities they track. Bugfix on 0.2.1.6-alpha.
22612 Changes in version 0.2.1.21 - 2009-12-21
22613 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
22614 library. If you use Tor on Linux / Unix and you're getting SSL
22615 renegotiation errors, upgrading should help. We also recommend an
22616 upgrade if you're an exit relay.
22619 - Work around a security feature in OpenSSL 0.9.8l that prevents our
22620 handshake from working unless we explicitly tell OpenSSL that we
22621 are using SSL renegotiation safely. We are, of course, but OpenSSL
22622 0.9.8l won't work unless we say we are.
22623 - Avoid crashing if the client is trying to upload many bytes and the
22624 circuit gets torn down at the same time, or if the flip side
22625 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
22628 - Do not refuse to learn about authority certs and v2 networkstatus
22629 documents that are older than the latest consensus. This bug might
22630 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
22631 Spotted and fixed by xmux.
22632 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
22633 trigger platform-specific option misparsing case found by Coverity
22635 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
22636 trigger assert. Fixes bug 1173.
22639 Changes in version 0.2.1.20 - 2009-10-15
22640 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
22641 services at once, prepares for more performance improvements, and
22642 fixes a bunch of smaller bugs.
22644 The Windows and OS X bundles also include a more recent Vidalia,
22645 and switch from Privoxy to Polipo.
22647 The OS X installers are now drag and drop. It's best to un-install
22648 Tor/Vidalia and then install this new bundle, rather than upgrade. If
22649 you want to upgrade, you'll need to update the paths for Tor and Polipo
22650 in the Vidalia Settings window.
22653 - Send circuit or stream sendme cells when our window has decreased
22654 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
22655 by Karsten when testing the "reduce circuit window" performance
22656 patch. Bugfix on the 54th commit on Tor -- from July 2002,
22657 before the release of Tor 0.0.0. This is the new winner of the
22659 - Fix a remotely triggerable memory leak when a consensus document
22660 contains more than one signature from the same voter. Bugfix on
22662 - Avoid segfault in rare cases when finishing an introduction circuit
22663 as a client and finding out that we don't have an introduction key
22664 for it. Fixes bug 1073. Reported by Aaron Swartz.
22667 - Tor now reads the "circwindow" parameter out of the consensus,
22668 and uses that value for its circuit package window rather than the
22669 default of 1000 cells. Begins the implementation of proposal 168.
22671 o New directory authorities:
22672 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
22674 - Move moria1 and tonga to alternate IP addresses.
22677 - Fix a signed/unsigned compile warning in 0.2.1.19.
22678 - Fix possible segmentation fault on directory authorities. Bugfix on
22680 - Fix an extremely rare infinite recursion bug that could occur if
22681 we tried to log a message after shutting down the log subsystem.
22682 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
22683 - Fix an obscure bug where hidden services on 64-bit big-endian
22684 systems might mis-read the timestamp in v3 introduce cells, and
22685 refuse to connect back to the client. Discovered by "rotor".
22686 Bugfix on 0.2.1.6-alpha.
22687 - We were triggering a CLOCK_SKEW controller status event whenever
22688 we connect via the v2 connection protocol to any relay that has
22689 a wrong clock. Instead, we should only inform the controller when
22690 it's a trusted authority that claims our clock is wrong. Bugfix
22691 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
22692 - We were telling the controller about CHECKING_REACHABILITY and
22693 REACHABILITY_FAILED status events whenever we launch a testing
22694 circuit or notice that one has failed. Instead, only tell the
22695 controller when we want to inform the user of overall success or
22696 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
22698 - Don't warn when we're using a circuit that ends with a node
22699 excluded in ExcludeExitNodes, but the circuit is not used to access
22700 the outside world. This should help fix bug 1090. Bugfix on
22702 - Work around a small memory leak in some versions of OpenSSL that
22703 stopped the memory used by the hostname TLS extension from being
22707 - Add a "getinfo status/accepted-server-descriptor" controller
22708 command, which is the recommended way for controllers to learn
22709 whether our server descriptor has been successfully received by at
22710 least on directory authority. Un-recommend good-server-descriptor
22711 getinfo and status events until we have a better design for them.
22714 Changes in version 0.2.1.19 - 2009-07-28
22715 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
22719 - Make accessing hidden services on 0.2.1.x work right again.
22720 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
22721 part of patch provided by "optimist".
22724 - When a relay/bridge is writing out its identity key fingerprint to
22725 the "fingerprint" file and to its logs, write it without spaces. Now
22726 it will look like the fingerprints in our bridges documentation,
22727 and confuse fewer users.
22730 - Relays no longer publish a new server descriptor if they change
22731 their MaxAdvertisedBandwidth config option but it doesn't end up
22732 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
22733 fixes bug 1026. Patch from Sebastian.
22734 - Avoid leaking memory every time we get a create cell but we have
22735 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
22736 fixes bug 1034. Reported by BarkerJr.
22739 Changes in version 0.2.1.18 - 2009-07-24
22740 Tor 0.2.1.18 lays the foundations for performance improvements,
22741 adds status events to help users diagnose bootstrap problems, adds
22742 optional authentication/authorization for hidden services, fixes a
22743 variety of potential anonymity problems, and includes a huge pile of
22744 other features and bug fixes.
22746 o Major features (clients):
22747 - Start sending "bootstrap phase" status events to the controller,
22748 so it can keep the user informed of progress fetching directory
22749 information and establishing circuits. Also inform the controller
22750 if we think we're stuck at a particular bootstrap phase. Implements
22752 - Clients replace entry guards that were chosen more than a few months
22753 ago. This change should significantly improve client performance,
22754 especially once more people upgrade, since relays that have been
22755 a guard for a long time are currently overloaded.
22756 - Network status consensus documents and votes now contain bandwidth
22757 information for each relay. Clients use the bandwidth values
22758 in the consensus, rather than the bandwidth values in each
22759 relay descriptor. This approach opens the door to more accurate
22760 bandwidth estimates once the directory authorities start doing
22761 active measurements. Implements part of proposal 141.
22763 o Major features (relays):
22764 - Disable and refactor some debugging checks that forced a linear scan
22765 over the whole server-side DNS cache. These accounted for over 50%
22766 of CPU time on a relatively busy exit node's gprof profile. Also,
22767 disable some debugging checks that appeared in exit node profile
22768 data. Found by Jacob.
22769 - New DirPortFrontPage option that takes an html file and publishes
22770 it as "/" on the DirPort. Now relay operators can provide a
22771 disclaimer without needing to set up a separate webserver. There's
22772 a sample disclaimer in contrib/tor-exit-notice.html.
22774 o Major features (hidden services):
22775 - Make it possible to build hidden services that only certain clients
22776 are allowed to connect to. This is enforced at several points,
22777 so that unauthorized clients are unable to send INTRODUCE cells
22778 to the service, or even (depending on the type of authentication)
22779 to learn introduction points. This feature raises the bar for
22780 certain kinds of active attacks against hidden services. Design
22781 and code by Karsten Loesing. Implements proposal 121.
22782 - Relays now store and serve v2 hidden service descriptors by default,
22783 i.e., the new default value for HidServDirectoryV2 is 1. This is
22784 the last step in proposal 114, which aims to make hidden service
22785 lookups more reliable.
22787 o Major features (path selection):
22788 - ExitNodes and Exclude*Nodes config options now allow you to restrict
22789 by country code ("{US}") or IP address or address pattern
22790 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
22791 refinement to decide what config options should take priority if
22792 you ask to both use a particular node and exclude it.
22794 o Major features (misc):
22795 - When building a consensus, do not include routers that are down.
22796 This cuts down 30% to 40% on consensus size. Implements proposal
22798 - New TestingTorNetwork config option to allow adjustment of
22799 previously constant values that could slow bootstrapping. Implements
22800 proposal 135. Patch from Karsten.
22801 - Convert many internal address representations to optionally hold
22802 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
22803 elements. Make resolver code handle nameservers located at IPv6
22805 - More work on making our TLS handshake blend in: modify the list
22806 of ciphers advertised by OpenSSL in client mode to even more
22807 closely resemble a common web browser. We cheat a little so that
22808 we can advertise ciphers that the locally installed OpenSSL doesn't
22810 - Use the TLS1 hostname extension to more closely resemble browser
22813 o Security fixes (anonymity/entropy):
22814 - Never use a connection with a mismatched address to extend a
22815 circuit, unless that connection is canonical. A canonical
22816 connection is one whose address is authenticated by the router's
22817 identity key, either in a NETINFO cell or in a router descriptor.
22818 - Implement most of proposal 110: The first K cells to be sent
22819 along a circuit are marked as special "early" cells; only K "early"
22820 cells will be allowed. Once this code is universal, we can block
22821 certain kinds of denial-of-service attack by requiring that EXTEND
22822 commands must be sent using an "early" cell.
22823 - Resume using OpenSSL's RAND_poll() for better (and more portable)
22824 cross-platform entropy collection again. We used to use it, then
22825 stopped using it because of a bug that could crash systems that
22826 called RAND_poll when they had a lot of fds open. It looks like the
22827 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
22828 at startup, and to call RAND_poll() when we reseed later only if
22829 we have a non-buggy OpenSSL version.
22830 - When the client is choosing entry guards, now it selects at most
22831 one guard from a given relay family. Otherwise we could end up with
22832 all of our entry points into the network run by the same operator.
22833 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
22834 - Do not use or believe expired v3 authority certificates. Patch
22835 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
22836 - Drop begin cells to a hidden service if they come from the middle
22837 of a circuit. Patch from lark.
22838 - When we erroneously receive two EXTEND cells for the same circuit
22839 ID on the same connection, drop the second. Patch from lark.
22840 - Authorities now vote for the Stable flag for any router whose
22841 weighted MTBF is at least 5 days, regardless of the mean MTBF.
22842 - Clients now never report any stream end reason except 'MISC'.
22843 Implements proposal 148.
22845 o Major bugfixes (crashes):
22846 - Parse dates and IPv4 addresses in a locale- and libc-independent
22847 manner, to avoid platform-dependent behavior on malformed input.
22848 - Fix a crash that occurs on exit nodes when a nameserver request
22849 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
22850 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
22852 - Do not assume that a stack-allocated character array will be
22853 64-bit aligned on platforms that demand that uint64_t access is
22854 aligned. Possible fix for bug 604.
22855 - Resolve a very rare crash bug that could occur when the user forced
22856 a nameserver reconfiguration during the middle of a nameserver
22857 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
22858 - Avoid a "0 divided by 0" calculation when calculating router uptime
22859 at directory authorities. Bugfix on 0.2.0.8-alpha.
22860 - Fix an assertion bug in parsing policy-related options; possible fix
22862 - Rate-limit too-many-sockets messages: when they happen, they happen
22863 a lot and end up filling up the disk. Resolves bug 748.
22864 - Fix a race condition that could cause crashes or memory corruption
22865 when running as a server with a controller listening for log
22867 - Avoid crashing when we have a policy specified in a DirPolicy or
22868 SocksPolicy or ReachableAddresses option with ports set on it,
22869 and we re-load the policy. May fix bug 996.
22870 - Fix an assertion failure on 64-bit platforms when we allocated
22871 memory right up to the end of a memarea, then realigned the memory
22872 one step beyond the end. Fixes a possible cause of bug 930.
22873 - Protect the count of open sockets with a mutex, so we can't
22874 corrupt it when two threads are closing or opening sockets at once.
22875 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
22877 o Major bugfixes (clients):
22878 - Discard router descriptors as we load them if they are more than
22879 five days old. Otherwise if Tor is off for a long time and then
22880 starts with cached descriptors, it will try to use the onion keys
22881 in those obsolete descriptors when building circuits. Fixes bug 887.
22882 - When we choose to abandon a new entry guard because we think our
22883 older ones might be better, close any circuits pending on that
22884 new entry guard connection. This fix should make us recover much
22885 faster when our network is down and then comes back. Bugfix on
22886 0.1.2.8-beta; found by lodger.
22887 - When Tor clients restart after 1-5 days, they discard all their
22888 cached descriptors as too old, but they still use the cached
22889 consensus document. This approach is good for robustness, but
22890 bad for performance: since they don't know any bandwidths, they
22891 end up choosing at random rather than weighting their choice by
22892 speed. Fixed by the above feature of putting bandwidths in the
22895 o Major bugfixes (relays):
22896 - Relays were falling out of the networkstatus consensus for
22897 part of a day if they changed their local config but the
22898 authorities discarded their new descriptor as "not sufficiently
22899 different". Now directory authorities accept a descriptor as changed
22900 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
22901 patch by Sebastian.
22902 - Ensure that two circuits can never exist on the same connection
22903 with the same circuit ID, even if one is marked for close. This
22904 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
22905 - Directory authorities were neglecting to mark relays down in their
22906 internal histories if the relays fall off the routerlist without
22907 ever being found unreachable. So there were relays in the histories
22908 that haven't been seen for eight months, and are listed as being
22909 up for eight months. This wreaked havoc on the "median wfu" and
22910 "median mtbf" calculations, in turn making Guard and Stable flags
22911 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
22914 o Major bugfixes (hidden services):
22915 - When establishing a hidden service, introduction points that
22916 originate from cannibalized circuits were completely ignored
22917 and not included in rendezvous service descriptors. This might
22918 have been another reason for delay in making a hidden service
22919 available. Bugfix from long ago (0.0.9.x?)
22921 o Major bugfixes (memory and resource management):
22922 - Fixed some memory leaks -- some quite frequent, some almost
22923 impossible to trigger -- based on results from Coverity.
22924 - Speed up parsing and cut down on memory fragmentation by using
22925 stack-style allocations for parsing directory objects. Previously,
22926 this accounted for over 40% of allocations from within Tor's code
22927 on a typical directory cache.
22928 - Use a Bloom filter rather than a digest-based set to track which
22929 descriptors we need to keep around when we're cleaning out old
22930 router descriptors. This speeds up the computation significantly,
22931 and may reduce fragmentation.
22933 o New/changed config options:
22934 - Now NodeFamily and MyFamily config options allow spaces in
22935 identity fingerprints, so it's easier to paste them in.
22936 Suggested by Lucky Green.
22937 - Allow ports 465 and 587 in the default exit policy again. We had
22938 rejected them in 0.1.0.15, because back in 2005 they were commonly
22939 misconfigured and ended up as spam targets. We hear they are better
22940 locked down these days.
22941 - Make TrackHostExit mappings expire a while after their last use, not
22942 after their creation. Patch from Robert Hogan.
22943 - Add an ExcludeExitNodes option so users can list a set of nodes
22944 that should be be excluded from the exit node position, but
22945 allowed elsewhere. Implements proposal 151.
22946 - New --hush command-line option similar to --quiet. While --quiet
22947 disables all logging to the console on startup, --hush limits the
22948 output to messages of warning and error severity.
22949 - New configure/torrc options (--enable-geoip-stats,
22950 DirRecordUsageByCountry) to record how many IPs we've served
22951 directory info to in each country code, how many status documents
22952 total we've sent to each country code, and what share of the total
22953 directory requests we should expect to see.
22954 - Make outbound DNS packets respect the OutboundBindAddress setting.
22955 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
22956 - Allow separate log levels to be configured for different logging
22957 domains. For example, this allows one to log all notices, warnings,
22958 or errors, plus all memory management messages of level debug or
22959 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
22960 - Update to the "June 3 2009" ip-to-country file.
22962 o Minor features (relays):
22963 - Raise the minimum rate limiting to be a relay from 20000 bytes
22964 to 20480 bytes (aka 20KB/s), to match our documentation. Also
22965 update directory authorities so they always assign the Fast flag
22966 to relays with 20KB/s of capacity. Now people running relays won't
22967 suddenly find themselves not seeing any use, if the network gets
22969 - If we're a relay and we change our IP address, be more verbose
22970 about the reason that made us change. Should help track down
22971 further bugs for relays on dynamic IP addresses.
22972 - Exit servers can now answer resolve requests for ip6.arpa addresses.
22973 - Implement most of Proposal 152: allow specialized servers to permit
22974 single-hop circuits, and clients to use those servers to build
22975 single-hop circuits when using a specialized controller. Patch
22976 from Josh Albrecht. Resolves feature request 768.
22977 - When relays do their initial bandwidth measurement, don't limit
22978 to just our entry guards for the test circuits. Otherwise we tend
22979 to have multiple test circuits going through a single entry guard,
22980 which makes our bandwidth test less accurate. Fixes part of bug 654;
22981 patch contributed by Josh Albrecht.
22983 o Minor features (directory authorities):
22984 - Try not to open more than one descriptor-downloading connection
22985 to an authority at once. This should reduce load on directory
22986 authorities. Fixes bug 366.
22987 - Add cross-certification to newly generated certificates, so that
22988 a signing key is enough information to look up a certificate. Start
22989 serving certificates by <identity digest, signing key digest>
22990 pairs. Implements proposal 157.
22991 - When a directory authority downloads a descriptor that it then
22992 immediately rejects, do not retry downloading it right away. Should
22993 save some bandwidth on authorities. Fix for bug 888. Patch by
22995 - Directory authorities now serve a /tor/dbg-stability.txt URL to
22996 help debug WFU and MTBF calculations.
22997 - In directory authorities' approved-routers files, allow
22998 fingerprints with or without space.
23000 o Minor features (directory mirrors):
23001 - When a download gets us zero good descriptors, do not notify
23002 Tor that new directory information has arrived.
23003 - Servers support a new URL scheme for consensus downloads that
23004 allows the client to specify which authorities are trusted.
23005 The server then only sends the consensus if the client will trust
23006 it. Otherwise a 404 error is sent back. Clients use this
23007 new scheme when the server supports it (meaning it's running
23008 0.2.1.1-alpha or later). Implements proposal 134.
23010 o Minor features (bridges):
23011 - If the bridge config line doesn't specify a port, assume 443.
23012 This makes bridge lines a bit smaller and easier for users to
23014 - If we're using bridges and our network goes away, be more willing
23015 to forgive our bridges and try again when we get an application
23018 o Minor features (hidden services):
23019 - When the client launches an introduction circuit, retry with a
23020 new circuit after 30 seconds rather than 60 seconds.
23021 - Launch a second client-side introduction circuit in parallel
23022 after a delay of 15 seconds (based on work by Christian Wilms).
23023 - Hidden services start out building five intro circuits rather
23024 than three, and when the first three finish they publish a service
23025 descriptor using those. Now we publish our service descriptor much
23026 faster after restart.
23027 - Drop the requirement to have an open dir port for storing and
23028 serving v2 hidden service descriptors.
23030 o Minor features (build and packaging):
23031 - On Linux, use the prctl call to re-enable core dumps when the User
23033 - Try to make sure that the version of Libevent we're running with
23034 is binary-compatible with the one we built with. May address bug
23036 - Add a new --enable-local-appdata configuration switch to change
23037 the default location of the datadir on win32 from APPDATA to
23038 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
23039 entirely. Patch from coderman.
23040 - Build correctly against versions of OpenSSL 0.9.8 or later that
23041 are built without support for deprecated functions.
23042 - On platforms with a maximum syslog string length, truncate syslog
23043 messages to that length ourselves, rather than relying on the
23044 system to do it for us.
23045 - Automatically detect MacOSX versions earlier than 10.4.0, and
23046 disable kqueue from inside Tor when running with these versions.
23047 We previously did this from the startup script, but that was no
23048 help to people who didn't use the startup script. Resolves bug 863.
23049 - Build correctly when configured to build outside the main source
23050 path. Patch from Michael Gold.
23051 - Disable GCC's strict alias optimization by default, to avoid the
23052 likelihood of its introducing subtle bugs whenever our code violates
23053 the letter of C99's alias rules.
23054 - Change the contrib/tor.logrotate script so it makes the new
23055 logs as "_tor:_tor" rather than the default, which is generally
23056 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
23057 - Change our header file guard macros to be less likely to conflict
23058 with system headers. Adam Langley noticed that we were conflicting
23059 with log.h on Android.
23060 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
23061 and stop using a warning that had become unfixably verbose under
23063 - Use a lockfile to make sure that two Tor processes are not
23064 simultaneously running with the same datadir.
23065 - Allow OpenSSL to use dynamic locks if it wants.
23066 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
23068 o Minor features (controllers):
23069 - When generating circuit events with verbose nicknames for
23070 controllers, try harder to look up nicknames for routers on a
23071 circuit. (Previously, we would look in the router descriptors we had
23072 for nicknames, but not in the consensus.) Partial fix for bug 941.
23073 - New controller event NEWCONSENSUS that lists the networkstatus
23074 lines for every recommended relay. Now controllers like Torflow
23075 can keep up-to-date on which relays they should be using.
23076 - New controller event "clients_seen" to report a geoip-based summary
23077 of which countries we've seen clients from recently. Now controllers
23078 like Vidalia can show bridge operators that they're actually making
23080 - Add a 'getinfo status/clients-seen' controller command, in case
23081 controllers want to hear clients_seen events but connect late.
23082 - New CONSENSUS_ARRIVED event to note when a new consensus has
23083 been fetched and validated.
23084 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
23085 controllers to prevent SIGHUP from reloading the configuration.
23087 - Return circuit purposes in response to GETINFO circuit-status.
23089 - Serve the latest v3 networkstatus consensus via the control
23090 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
23091 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
23092 controller can query our current bootstrap state in case it attaches
23093 partway through and wants to catch up.
23094 - Provide circuit purposes along with circuit events to the controller.
23096 o Minor features (tools):
23097 - Do not have tor-resolve automatically refuse all .onion addresses;
23098 if AutomapHostsOnResolve is set in your torrc, this will work fine.
23099 - Add a -p option to tor-resolve for specifying the SOCKS port: some
23100 people find host:port too confusing.
23101 - Print the SOCKS5 error message string as well as the error code
23102 when a tor-resolve request fails. Patch from Jacob.
23104 o Minor bugfixes (memory and resource management):
23105 - Clients no longer cache certificates for authorities they do not
23106 recognize. Bugfix on 0.2.0.9-alpha.
23107 - Do not use C's stdio library for writing to log files. This will
23108 improve logging performance by a minute amount, and will stop
23109 leaking fds when our disk is full. Fixes bug 861.
23110 - Stop erroneous use of O_APPEND in cases where we did not in fact
23111 want to re-seek to the end of a file before every last write().
23112 - Fix a small alignment and memory-wasting bug on buffer chunks.
23114 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
23115 to avoid unused RAM in buffer chunks and memory pools.
23116 - Reduce the default smartlist size from 32 to 16; it turns out that
23117 most smartlists hold around 8-12 elements tops.
23118 - Make dumpstats() log the fullness and size of openssl-internal
23120 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
23121 patch to their OpenSSL, turn it on to save memory on servers. This
23122 patch will (with any luck) get included in a mainline distribution
23124 - Fix a memory leak when v3 directory authorities load their keys
23125 and cert from disk. Bugfix on 0.2.0.1-alpha.
23126 - Stop using malloc_usable_size() to use more area than we had
23127 actually allocated: it was safe, but made valgrind really unhappy.
23128 - Make the assert_circuit_ok() function work correctly on circuits that
23129 have already been marked for close.
23130 - Fix uninitialized size field for memory area allocation: may improve
23131 memory performance during directory parsing.
23133 o Minor bugfixes (clients):
23134 - Stop reloading the router list from disk for no reason when we
23135 run out of reachable directory mirrors. Once upon a time reloading
23136 it would set the 'is_running' flag back to 1 for them. It hasn't
23137 done that for a long time.
23138 - When we had picked an exit node for a connection, but marked it as
23139 "optional", and it turned out we had no onion key for the exit,
23140 stop wanting that exit and try again. This situation may not
23141 be possible now, but will probably become feasible with proposal
23142 158. Spotted by rovv. Fixes another case of bug 752.
23143 - Fix a bug in address parsing that was preventing bridges or hidden
23144 service targets from being at IPv6 addresses.
23145 - Do not remove routers as too old if we do not have any consensus
23146 document. Bugfix on 0.2.0.7-alpha.
23147 - When an exit relay resolves a stream address to a local IP address,
23148 do not just keep retrying that same exit relay over and
23149 over. Instead, just close the stream. Addresses bug 872. Bugfix
23150 on 0.2.0.32. Patch from rovv.
23151 - Made Tor a little less aggressive about deleting expired
23152 certificates. Partial fix for bug 854.
23153 - Treat duplicate certificate fetches as failures, so that we do
23154 not try to re-fetch an expired certificate over and over and over.
23155 - Do not say we're fetching a certificate when we'll in fact skip it
23156 because of a pending download.
23157 - If we have correct permissions on $datadir, we complain to stdout
23158 and fail to start. But dangerous permissions on
23159 $datadir/cached-status/ would cause us to open a log and complain
23160 there. Now complain to stdout and fail to start in both cases. Fixes
23161 bug 820, reported by seeess.
23163 o Minor bugfixes (bridges):
23164 - When we made bridge authorities stop serving bridge descriptors over
23165 unencrypted links, we also broke DirPort reachability testing for
23166 bridges. So bridges with a non-zero DirPort were printing spurious
23167 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
23168 - Don't allow a bridge to publish its router descriptor to a
23169 non-bridge directory authority. Fixes part of bug 932.
23170 - When we change to or from being a bridge, reset our counts of
23171 client usage by country. Fixes bug 932.
23173 o Minor bugfixes (relays):
23174 - Log correct error messages for DNS-related network errors on
23176 - Actually return -1 in the error case for read_bandwidth_usage().
23177 Harmless bug, since we currently don't care about the return value
23178 anywhere. Bugfix on 0.2.0.9-alpha.
23179 - Provide a more useful log message if bug 977 (related to buffer
23180 freelists) ever reappears, and do not crash right away.
23181 - We were already rejecting relay begin cells with destination port
23182 of 0. Now also reject extend cells with destination port or address
23183 of 0. Suggested by lark.
23184 - When we can't transmit a DNS request due to a network error, retry
23185 it after a while, and eventually transmit a failing response to
23186 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
23187 - Solve a bug that kept hardware crypto acceleration from getting
23188 enabled when accounting was turned on. Fixes bug 907. Bugfix on
23190 - When a canonical connection appears later in our internal list
23191 than a noncanonical one for a given OR ID, always use the
23192 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
23194 - Avoid some nasty corner cases in the logic for marking connections
23195 as too old or obsolete or noncanonical for circuits. Partial
23197 - Fix another interesting corner-case of bug 891 spotted by rovv:
23198 Previously, if two hosts had different amounts of clock drift, and
23199 one of them created a new connection with just the wrong timing,
23200 the other might decide to deprecate the new connection erroneously.
23201 Bugfix on 0.1.1.13-alpha.
23202 - If one win32 nameserver fails to get added, continue adding the
23203 rest, and don't automatically fail.
23204 - Fix a bug where an unreachable relay would establish enough
23205 reachability testing circuits to do a bandwidth test -- if
23206 we already have a connection to the middle hop of the testing
23207 circuit, then it could establish the last hop by using the existing
23208 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
23209 circuits no longer use entry guards in 0.2.1.3-alpha.
23211 o Minor bugfixes (directory authorities):
23212 - Limit uploaded directory documents to be 16M rather than 500K.
23213 The directory authorities were refusing v3 consensus votes from
23214 other authorities, since the votes are now 504K. Fixes bug 959;
23215 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
23216 - Directory authorities should never send a 503 "busy" response to
23217 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
23219 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
23220 headers. Bugfix on 0.2.0.10-alpha.
23222 o Minor bugfixes (hidden services):
23223 - When we can't find an intro key for a v2 hidden service descriptor,
23224 fall back to the v0 hidden service descriptor and log a bug message.
23225 Workaround for bug 1024.
23226 - In very rare situations new hidden service descriptors were
23227 published earlier than 30 seconds after the last change to the
23228 service. (We currently think that a hidden service descriptor
23229 that's been stable for 30 seconds is worth publishing.)
23230 - If a hidden service sends us an END cell, do not consider
23231 retrying the connection; just close it. Patch from rovv.
23232 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
23233 service directories if they have no advertised dir port. Bugfix
23236 o Minor bugfixes (tools):
23237 - In the torify(1) manpage, mention that tsocks will leak your
23240 o Minor bugfixes (controllers):
23241 - If the controller claimed responsibility for a stream, but that
23242 stream never finished making its connection, it would live
23243 forever in circuit_wait state. Now we close it after SocksTimeout
23244 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
23245 - Make DNS resolved controller events into "CLOSED", not
23246 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
23248 - The control port would close the connection before flushing long
23249 replies, such as the network consensus, if a QUIT command was issued
23250 before the reply had completed. Now, the control port flushes all
23251 pending replies before closing the connection. Also fix a spurious
23252 warning when a QUIT command is issued after a malformed or rejected
23253 AUTHENTICATE command, but before the connection was closed. Patch
23254 by Marcus Griep. Fixes bugs 1015 and 1016.
23255 - Fix a bug that made stream bandwidth get misreported to the
23258 o Deprecated and removed features:
23259 - The old "tor --version --version" command, which would print out
23260 the subversion "Id" of most of the source files, is now removed. It
23261 turned out to be less useful than we'd expected, and harder to
23263 - RedirectExits has been removed. It was deprecated since
23265 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
23266 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
23267 - Cell pools are now always enabled; --disable-cell-pools is ignored.
23268 - Directory mirrors no longer fetch the v1 directory or
23269 running-routers files. They are obsolete, and nobody asks for them
23270 anymore. This is the first step to making v1 authorities obsolete.
23271 - Take out the TestVia config option, since it was a workaround for
23272 a bug that was fixed in Tor 0.1.1.21.
23273 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
23274 HiddenServiceExcludeNodes as obsolete: they never worked properly,
23275 and nobody seems to be using them. Fixes bug 754. Bugfix on
23276 0.1.0.1-rc. Patch from Christian Wilms.
23277 - Remove all backward-compatibility code for relays running
23278 versions of Tor so old that they no longer work at all on the
23281 o Code simplifications and refactoring:
23282 - Tool-assisted documentation cleanup. Nearly every function or
23283 static variable in Tor should have its own documentation now.
23284 - Rename the confusing or_is_obsolete field to the more appropriate
23285 is_bad_for_new_circs, and move it to or_connection_t where it
23287 - Move edge-only flags from connection_t to edge_connection_t: not
23288 only is this better coding, but on machines of plausible alignment,
23289 it should save 4-8 bytes per connection_t. "Every little bit helps."
23290 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
23291 for consistency; keep old option working for backward compatibility.
23292 - Simplify the code for finding connections to use for a circuit.
23293 - Revise the connection_new functions so that a more typesafe variant
23294 exists. This will work better with Coverity, and let us find any
23295 actual mistakes we're making here.
23296 - Refactor unit testing logic so that dmalloc can be used sensibly
23297 with unit tests to check for memory leaks.
23298 - Move all hidden-service related fields from connection and circuit
23299 structure to substructures: this way they won't eat so much memory.
23300 - Squeeze 2-5% out of client performance (according to oprofile) by
23301 improving the implementation of some policy-manipulation functions.
23302 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
23303 be more efficient. Formerly it was quadratic in the number of
23304 servers; now it should be linear. Fixes bug 509.
23305 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
23306 and n_conn_id_digest fields into a separate structure that's
23307 only needed when the circuit has not yet attached to an n_conn.
23308 - Optimize out calls to time(NULL) that occur for every IO operation,
23309 or for every cell. On systems like Windows where time() is a
23310 slow syscall, this fix will be slightly helpful.
23313 Changes in version 0.2.0.35 - 2009-06-24
23315 - Avoid crashing in the presence of certain malformed descriptors.
23316 Found by lark, and by automated fuzzing.
23317 - Fix an edge case where a malicious exit relay could convince a
23318 controller that the client's DNS question resolves to an internal IP
23319 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
23322 - Finally fix the bug where dynamic-IP relays disappear when their
23323 IP address changes: directory mirrors were mistakenly telling
23324 them their old address if they asked via begin_dir, so they
23325 never got an accurate answer about their new address, so they
23326 just vanished after a day. For belt-and-suspenders, relays that
23327 don't set Address in their config now avoid using begin_dir for
23328 all direct connections. Should fix bugs 827, 883, and 900.
23329 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
23330 that would occur on some exit nodes when DNS failures and timeouts
23331 occurred in certain patterns. Fix for bug 957.
23334 - When starting with a cache over a few days old, do not leak
23335 memory for the obsolete router descriptors in it. Bugfix on
23336 0.2.0.33; fixes bug 672.
23337 - Hidden service clients didn't use a cached service descriptor that
23338 was older than 15 minutes, but wouldn't fetch a new one either,
23339 because there was already one in the cache. Now, fetch a v2
23340 descriptor unless the same descriptor was added to the cache within
23341 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
23344 Changes in version 0.2.0.34 - 2009-02-08
23345 Tor 0.2.0.34 features several more security-related fixes. You should
23346 upgrade, especially if you run an exit relay (remote crash) or a
23347 directory authority (remote infinite loop), or you're on an older
23348 (pre-XP) or not-recently-patched Windows (remote exploit).
23350 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
23351 have many known flaws, and nobody should be using them. You should
23352 upgrade. If you're using a Linux or BSD and its packages are obsolete,
23353 stop using those packages and upgrade anyway.
23356 - Fix an infinite-loop bug on handling corrupt votes under certain
23357 circumstances. Bugfix on 0.2.0.8-alpha.
23358 - Fix a temporary DoS vulnerability that could be performed by
23359 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
23360 - Avoid a potential crash on exit nodes when processing malformed
23361 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
23362 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
23363 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
23366 - Fix compilation on systems where time_t is a 64-bit integer.
23367 Patch from Matthias Drochner.
23368 - Don't consider expiring already-closed client connections. Fixes
23369 bug 893. Bugfix on 0.0.2pre20.
23372 Changes in version 0.2.0.33 - 2009-01-21
23373 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
23374 useful to users. It also finally fixes a bug where a relay or client
23375 that's been off for many days would take a long time to bootstrap.
23377 This update also fixes an important security-related bug reported by
23378 Ilja van Sprundel. You should upgrade. (We'll send out more details
23379 about the bug once people have had some time to upgrade.)
23382 - Fix a heap-corruption bug that may be remotely triggerable on
23383 some platforms. Reported by Ilja van Sprundel.
23386 - When a stream at an exit relay is in state "resolving" or
23387 "connecting" and it receives an "end" relay cell, the exit relay
23388 would silently ignore the end cell and not close the stream. If
23389 the client never closes the circuit, then the exit relay never
23390 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
23391 reported by "wood".
23392 - When sending CREATED cells back for a given circuit, use a 64-bit
23393 connection ID to find the right connection, rather than an addr:port
23394 combination. Now that we can have multiple OR connections between
23395 the same ORs, it is no longer possible to use addr:port to uniquely
23396 identify a connection.
23397 - Bridge relays that had DirPort set to 0 would stop fetching
23398 descriptors shortly after startup, and then briefly resume
23399 after a new bandwidth test and/or after publishing a new bridge
23400 descriptor. Bridge users that try to bootstrap from them would
23401 get a recent networkstatus but would get descriptors from up to
23402 18 hours earlier, meaning most of the descriptors were obsolete
23403 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
23404 - Prevent bridge relays from serving their 'extrainfo' document
23405 to anybody who asks, now that extrainfo docs include potentially
23406 sensitive aggregated client geoip summaries. Bugfix on
23408 - If the cached networkstatus consensus is more than five days old,
23409 discard it rather than trying to use it. In theory it could be
23410 useful because it lists alternate directory mirrors, but in practice
23411 it just means we spend many minutes trying directory mirrors that
23412 are long gone from the network. Also discard router descriptors as
23413 we load them if they are more than five days old, since the onion
23414 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
23417 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
23418 could make gcc generate non-functional binary search code. Bugfix
23420 - Build correctly on platforms without socklen_t.
23421 - Compile without warnings on solaris.
23422 - Avoid potential crash on internal error during signature collection.
23423 Fixes bug 864. Patch from rovv.
23424 - Correct handling of possible malformed authority signing key
23425 certificates with internal signature types. Fixes bug 880.
23426 Bugfix on 0.2.0.3-alpha.
23427 - Fix a hard-to-trigger resource leak when logging credential status.
23429 - When we can't initialize DNS because the network is down, do not
23430 automatically stop Tor from starting. Instead, we retry failed
23431 dns_init() every 10 minutes, and change the exit policy to reject
23432 *:* until one succeeds. Fixes bug 691.
23433 - Use 64 bits instead of 32 bits for connection identifiers used with
23434 the controller protocol, to greatly reduce risk of identifier reuse.
23435 - When we're choosing an exit node for a circuit, and we have
23436 no pending streams, choose a good general exit rather than one that
23437 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
23438 - Fix another case of assuming, when a specific exit is requested,
23439 that we know more than the user about what hosts it allows.
23440 Fixes one case of bug 752. Patch from rovv.
23441 - Clip the MaxCircuitDirtiness config option to a minimum of 10
23442 seconds. Warn the user if lower values are given in the
23443 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
23444 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
23445 user if lower values are given in the configuration. Bugfix on
23446 0.1.1.17-rc. Patch by Sebastian.
23447 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
23448 the cache because we already had a v0 descriptor with the same ID.
23449 Bugfix on 0.2.0.18-alpha.
23450 - Fix a race condition when freeing keys shared between main thread
23451 and CPU workers that could result in a memory leak. Bugfix on
23452 0.1.0.1-rc. Fixes bug 889.
23453 - Send a valid END cell back when a client tries to connect to a
23454 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
23455 840. Patch from rovv.
23456 - Check which hops rendezvous stream cells are associated with to
23457 prevent possible guess-the-streamid injection attacks from
23458 intermediate hops. Fixes another case of bug 446. Based on patch
23460 - If a broken client asks a non-exit router to connect somewhere,
23461 do not even do the DNS lookup before rejecting the connection.
23462 Fixes another case of bug 619. Patch from rovv.
23463 - When a relay gets a create cell it can't decrypt (e.g. because it's
23464 using the wrong onion key), we were dropping it and letting the
23465 client time out. Now actually answer with a destroy cell. Fixes
23466 bug 904. Bugfix on 0.0.2pre8.
23468 o Minor bugfixes (hidden services):
23469 - Do not throw away existing introduction points on SIGHUP. Bugfix on
23470 0.0.6pre1. Patch by Karsten. Fixes bug 874.
23473 - Report the case where all signatures in a detached set are rejected
23474 differently than the case where there is an error handling the
23476 - When we realize that another process has modified our cached
23477 descriptors, print out a more useful error message rather than
23478 triggering an assertion. Fixes bug 885. Patch from Karsten.
23479 - Implement the 0x20 hack to better resist DNS poisoning: set the
23480 case on outgoing DNS requests randomly, and reject responses that do
23481 not match the case correctly. This logic can be disabled with the
23482 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
23483 of servers that do not reliably preserve case in replies. See
23484 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
23486 - Check DNS replies for more matching fields to better resist DNS
23488 - Never use OpenSSL compression: it wastes RAM and CPU trying to
23489 compress cells, which are basically all encrypted, compressed, or
23493 Changes in version 0.2.0.32 - 2008-11-20
23494 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
23495 packages (and maybe other packages) noticed by Theo de Raadt, fixes
23496 a smaller security flaw that might allow an attacker to access local
23497 services, further improves hidden service performance, and fixes a
23498 variety of other issues.
23501 - The "User" and "Group" config options did not clear the
23502 supplementary group entries for the Tor process. The "User" option
23503 is now more robust, and we now set the groups to the specified
23504 user's primary group. The "Group" option is now ignored. For more
23505 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
23506 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
23507 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
23508 - The "ClientDNSRejectInternalAddresses" config option wasn't being
23509 consistently obeyed: if an exit relay refuses a stream because its
23510 exit policy doesn't allow it, we would remember what IP address
23511 the relay said the destination address resolves to, even if it's
23512 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
23515 - Fix a DOS opportunity during the voting signature collection process
23516 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
23518 o Major bugfixes (hidden services):
23519 - When fetching v0 and v2 rendezvous service descriptors in parallel,
23520 we were failing the whole hidden service request when the v0
23521 descriptor fetch fails, even if the v2 fetch is still pending and
23522 might succeed. Similarly, if the last v2 fetch fails, we were
23523 failing the whole hidden service request even if a v0 fetch is
23524 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
23525 - When extending a circuit to a hidden service directory to upload a
23526 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
23527 requests failed, because the router descriptor has not been
23528 downloaded yet. In these cases, do not attempt to upload the
23529 rendezvous descriptor, but wait until the router descriptor is
23530 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
23531 descriptor from a hidden service directory for which the router
23532 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
23536 - Fix several infrequent memory leaks spotted by Coverity.
23537 - When testing for libevent functions, set the LDFLAGS variable
23538 correctly. Found by Riastradh.
23539 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
23540 bootstrapping with tunneled directory connections. Bugfix on
23541 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
23542 - When asked to connect to A.B.exit:80, if we don't know the IP for A
23543 and we know that server B rejects most-but-not all connections to
23544 port 80, we would previously reject the connection. Now, we assume
23545 the user knows what they were asking for. Fixes bug 752. Bugfix
23546 on 0.0.9rc5. Diagnosed by BarkerJr.
23547 - If we overrun our per-second write limits a little, count this as
23548 having used up our write allocation for the second, and choke
23549 outgoing directory writes. Previously, we had only counted this when
23550 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
23551 Bugfix on 0.2.0.x (??).
23552 - Remove the old v2 directory authority 'lefkada' from the default
23553 list. It has been gone for many months.
23554 - Stop doing unaligned memory access that generated bus errors on
23555 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
23556 - Make USR2 log-level switch take effect immediately. Bugfix on
23559 o Minor bugfixes (controller):
23560 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
23561 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
23564 Changes in version 0.2.0.31 - 2008-09-03
23565 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
23566 a big bug we're seeing where in rare cases traffic from one Tor stream
23567 gets mixed into another stream, and fixes a variety of smaller issues.
23570 - Make sure that two circuits can never exist on the same connection
23571 with the same circuit ID, even if one is marked for close. This
23572 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
23573 - Relays now reject risky extend cells: if the extend cell includes
23574 a digest of all zeroes, or asks to extend back to the relay that
23575 sent the extend cell, tear down the circuit. Ideas suggested
23577 - If not enough of our entry guards are available so we add a new
23578 one, we might use the new one even if it overlapped with the
23579 current circuit's exit relay (or its family). Anonymity bugfix
23580 pointed out by rovv.
23583 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
23584 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
23585 - Correctly detect the presence of the linux/netfilter_ipv4.h header
23586 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
23587 - Pick size of default geoip filename string correctly on windows.
23588 Fixes bug 806. Bugfix on 0.2.0.30.
23589 - Make the autoconf script accept the obsolete --with-ssl-dir
23590 option as an alias for the actually-working --with-openssl-dir
23591 option. Fix the help documentation to recommend --with-openssl-dir.
23592 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
23593 - When using the TransPort option on OpenBSD, and using the User
23594 option to change UID and drop privileges, make sure to open
23595 /dev/pf before dropping privileges. Fixes bug 782. Patch from
23596 Christopher Davis. Bugfix on 0.1.2.1-alpha.
23597 - Try to attach connections immediately upon receiving a RENDEZVOUS2
23598 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
23599 on the client side when connecting to a hidden service. Bugfix
23600 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
23601 - When closing an application-side connection because its circuit is
23602 getting torn down, generate the stream event correctly. Bugfix on
23603 0.1.2.x. Anonymous patch.
23606 Changes in version 0.2.0.30 - 2008-07-15
23607 This new stable release switches to a more efficient directory
23608 distribution design, adds features to make connections to the Tor
23609 network harder to block, allows Tor to act as a DNS proxy, adds separate
23610 rate limiting for relayed traffic to make it easier for clients to
23611 become relays, fixes a variety of potential anonymity problems, and
23612 includes the usual huge pile of other features and bug fixes.
23614 o New v3 directory design:
23615 - Tor now uses a new way to learn about and distribute information
23616 about the network: the directory authorities vote on a common
23617 network status document rather than each publishing their own
23618 opinion. Now clients and caches download only one networkstatus
23619 document to bootstrap, rather than downloading one for each
23620 authority. Clients only download router descriptors listed in
23621 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
23623 - Set up moria1, tor26, and dizum as v3 directory authorities
23624 in addition to being v2 authorities. Also add three new ones:
23625 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
23626 dannenberg (run by CCC).
23627 - Switch to multi-level keys for directory authorities: now their
23628 long-term identity key can be kept offline, and they periodically
23629 generate a new signing key. Clients fetch the "key certificates"
23630 to keep up to date on the right keys. Add a standalone tool
23631 "tor-gencert" to generate key certificates. Implements proposal 103.
23632 - Add a new V3AuthUseLegacyKey config option to make it easier for
23633 v3 authorities to change their identity keys if another bug like
23634 Debian's OpenSSL RNG flaw appears.
23635 - Authorities and caches fetch the v2 networkstatus documents
23636 less often, now that v3 is recommended.
23638 o Make Tor connections stand out less on the wire:
23639 - Use an improved TLS handshake designed by Steven Murdoch in proposal
23640 124, as revised in proposal 130. The new handshake is meant to
23641 be harder for censors to fingerprint, and it adds the ability
23642 to detect certain kinds of man-in-the-middle traffic analysis
23643 attacks. The new handshake format includes version negotiation for
23644 OR connections as described in proposal 105, which will allow us
23645 to improve Tor's link protocol more safely in the future.
23646 - Enable encrypted directory connections by default for non-relays,
23647 so censor tools that block Tor directory connections based on their
23648 plaintext patterns will no longer work. This means Tor works in
23649 certain censored countries by default again.
23650 - Stop including recognizeable strings in the commonname part of
23651 Tor's x509 certificates.
23653 o Implement bridge relays:
23654 - Bridge relays (or "bridges" for short) are Tor relays that aren't
23655 listed in the main Tor directory. Since there is no complete public
23656 list of them, even an ISP that is filtering connections to all the
23657 known Tor relays probably won't be able to block all the bridges.
23658 See doc/design-paper/blocking.pdf and proposal 125 for details.
23659 - New config option BridgeRelay that specifies you want to be a
23660 bridge relay rather than a normal relay. When BridgeRelay is set
23661 to 1, then a) you cache dir info even if your DirPort ins't on,
23662 and b) the default for PublishServerDescriptor is now "bridge"
23663 rather than "v2,v3".
23664 - New config option "UseBridges 1" for clients that want to use bridge
23665 relays instead of ordinary entry guards. Clients then specify
23666 bridge relays by adding "Bridge" lines to their config file. Users
23667 can learn about a bridge relay either manually through word of
23668 mouth, or by one of our rate-limited mechanisms for giving out
23669 bridge addresses without letting an attacker easily enumerate them
23670 all. See https://www.torproject.org/bridges for details.
23671 - Bridge relays behave like clients with respect to time intervals
23672 for downloading new v3 consensus documents -- otherwise they
23673 stand out. Bridge users now wait until the end of the interval,
23674 so their bridge relay will be sure to have a new consensus document.
23676 o Implement bridge directory authorities:
23677 - Bridge authorities are like normal directory authorities, except
23678 they don't serve a list of known bridges. Therefore users that know
23679 a bridge's fingerprint can fetch a relay descriptor for that bridge,
23680 including fetching updates e.g. if the bridge changes IP address,
23681 yet an attacker can't just fetch a list of all the bridges.
23682 - Set up Tonga as the default bridge directory authority.
23683 - Bridge authorities refuse to serve bridge descriptors or other
23684 bridge information over unencrypted connections (that is, when
23685 responding to direct DirPort requests rather than begin_dir cells.)
23686 - Bridge directory authorities do reachability testing on the
23687 bridges they know. They provide router status summaries to the
23688 controller via "getinfo ns/purpose/bridge", and also dump summaries
23689 to a file periodically, so we can keep internal stats about which
23690 bridges are functioning.
23691 - If bridge users set the UpdateBridgesFromAuthority config option,
23692 but the digest they ask for is a 404 on the bridge authority,
23693 they fall back to contacting the bridge directly.
23694 - Bridges always use begin_dir to publish their server descriptor to
23695 the bridge authority using an anonymous encrypted tunnel.
23696 - Early work on a "bridge community" design: if bridge authorities set
23697 the BridgePassword config option, they will serve a snapshot of
23698 known bridge routerstatuses from their DirPort to anybody who
23699 knows that password. Unset by default.
23700 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
23701 report sanitized aggregated summaries in their extra-info documents
23702 privately to the bridge authority, listing which countries are
23703 able to reach them. We hope this mechanism will let us learn when
23704 certain countries start trying to block bridges.
23705 - Bridge authorities write bridge descriptors to disk, so they can
23706 reload them after a reboot. They can also export the descriptors
23707 to other programs, so we can distribute them to blocked users via
23708 the BridgeDB interface, e.g. via https://bridges.torproject.org/
23709 and bridges@torproject.org.
23711 o Tor can be a DNS proxy:
23712 - The new client-side DNS proxy feature replaces the need for
23713 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
23714 for DNS requests on port 9999, use the Tor network to resolve them
23715 anonymously, and send the reply back like a regular DNS server.
23716 The code still only implements a subset of DNS.
23717 - Add a new AutomapHostsOnResolve option: when it is enabled, any
23718 resolve request for hosts matching a given pattern causes Tor to
23719 generate an internal virtual address mapping for that host. This
23720 allows DNSPort to work sensibly with hidden service users. By
23721 default, .exit and .onion addresses are remapped; the list of
23722 patterns can be reconfigured with AutomapHostsSuffixes.
23723 - Add an "-F" option to tor-resolve to force a resolve for a .onion
23724 address. Thanks to the AutomapHostsOnResolve option, this is no
23725 longer a completely silly thing to do.
23727 o Major features (relay usability):
23728 - New config options RelayBandwidthRate and RelayBandwidthBurst:
23729 a separate set of token buckets for relayed traffic. Right now
23730 relayed traffic is defined as answers to directory requests, and
23731 OR connections that don't have any local circuits on them. See
23732 proposal 111 for details.
23733 - Create listener connections before we setuid to the configured
23734 User and Group. Now non-Windows users can choose port values
23735 under 1024, start Tor as root, and have Tor bind those ports
23736 before it changes to another UID. (Windows users could already
23738 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
23739 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
23740 on "vserver" accounts. Patch from coderman.
23742 o Major features (directory authorities):
23743 - Directory authorities track weighted fractional uptime and weighted
23744 mean-time-between failures for relays. WFU is suitable for deciding
23745 whether a node is "usually up", while MTBF is suitable for deciding
23746 whether a node is "likely to stay up." We need both, because
23747 "usually up" is a good requirement for guards, while "likely to
23748 stay up" is a good requirement for long-lived connections.
23749 - Directory authorities use a new formula for selecting which relays
23750 to advertise as Guards: they must be in the top 7/8 in terms of
23751 how long we have known about them, and above the median of those
23752 nodes in terms of weighted fractional uptime.
23753 - Directory authorities use a new formula for selecting which relays
23754 to advertise as Stable: when we have 4 or more days of data, use
23755 median measured MTBF rather than median declared uptime. Implements
23757 - Directory authorities accept and serve "extra info" documents for
23758 routers. Routers now publish their bandwidth-history lines in the
23759 extra-info docs rather than the main descriptor. This step saves
23760 60% (!) on compressed router descriptor downloads. Servers upload
23761 extra-info docs to any authority that accepts them; directory
23762 authorities now allow multiple router descriptors and/or extra
23763 info documents to be uploaded in a single go. Authorities, and
23764 caches that have been configured to download extra-info documents,
23765 download them as needed. Implements proposal 104.
23766 - Authorities now list relays who have the same nickname as
23767 a different named relay, but list them with a new flag:
23768 "Unnamed". Now we can make use of relays that happen to pick the
23769 same nickname as a server that registered two years ago and then
23770 disappeared. Implements proposal 122.
23771 - Store routers in a file called cached-descriptors instead of in
23772 cached-routers. Initialize cached-descriptors from cached-routers
23773 if the old format is around. The new format allows us to store
23774 annotations along with descriptors, to record the time we received
23775 each descriptor, its source, and its purpose: currently one of
23776 general, controller, or bridge.
23778 o Major features (other):
23779 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
23780 Tor can warn and/or refuse connections to ports commonly used with
23781 vulnerable-plaintext protocols. Currently we warn on ports 23,
23782 109, 110, and 143, but we don't reject any. Based on proposal 129
23783 by Kevin Bauer and Damon McCoy.
23784 - Integrate Karsten Loesing's Google Summer of Code project to publish
23785 hidden service descriptors on a set of redundant relays that are a
23786 function of the hidden service address. Now we don't have to rely
23787 on three central hidden service authorities for publishing and
23788 fetching every hidden service descriptor. Implements proposal 114.
23789 - Allow tunnelled directory connections to ask for an encrypted
23790 "begin_dir" connection or an anonymized "uses a full Tor circuit"
23791 connection independently. Now we can make anonymized begin_dir
23792 connections for (e.g.) more secure hidden service posting and
23795 o Major bugfixes (crashes and assert failures):
23796 - Stop imposing an arbitrary maximum on the number of file descriptors
23797 used for busy servers. Bug reported by Olaf Selke; patch from
23799 - Avoid possible failures when generating a directory with routers
23800 with over-long versions strings, or too many flags set.
23801 - Fix a rare assert error when we're closing one of our threads:
23802 use a mutex to protect the list of logs, so we never write to the
23803 list as it's being freed. Fixes the very rare bug 575, which is
23804 kind of the revenge of bug 222.
23805 - Avoid segfault in the case where a badly behaved v2 versioning
23806 directory sends a signed networkstatus with missing client-versions.
23807 - When we hit an EOF on a log (probably because we're shutting down),
23808 don't try to remove the log from the list: just mark it as
23809 unusable. (Bulletproofs against bug 222.)
23811 o Major bugfixes (code security fixes):
23812 - Detect size overflow in zlib code. Reported by Justin Ferguson and
23814 - Rewrite directory tokenization code to never run off the end of
23815 a string. Fixes bug 455. Patch from croup.
23816 - Be more paranoid about overwriting sensitive memory on free(),
23817 as a defensive programming tactic to ensure forward secrecy.
23819 o Major bugfixes (anonymity fixes):
23820 - Reject requests for reverse-dns lookup of names that are in
23821 a private address space. Patch from lodger.
23822 - Never report that we've used more bandwidth than we're willing to
23823 relay: it leaks how much non-relay traffic we're using. Resolves
23825 - As a client, do not believe any server that tells us that an
23826 address maps to an internal address space.
23827 - Warn about unsafe ControlPort configurations.
23828 - Directory authorities now call routers Fast if their bandwidth is
23829 at least 100KB/s, and consider their bandwidth adequate to be a
23830 Guard if it is at least 250KB/s, no matter the medians. This fix
23831 complements proposal 107.
23832 - Directory authorities now never mark more than 2 servers per IP as
23833 Valid and Running (or 5 on addresses shared by authorities).
23834 Implements proposal 109, by Kevin Bauer and Damon McCoy.
23835 - If we're a relay, avoid picking ourselves as an introduction point,
23836 a rendezvous point, or as the final hop for internal circuits. Bug
23837 reported by taranis and lodger.
23838 - Exit relays that are used as a client can now reach themselves
23839 using the .exit notation, rather than just launching an infinite
23840 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
23841 - Fix a bug where, when we were choosing the 'end stream reason' to
23842 put in our relay end cell that we send to the exit relay, Tor
23843 clients on Windows were sometimes sending the wrong 'reason'. The
23844 anonymity problem is that exit relays may be able to guess whether
23845 the client is running Windows, thus helping partition the anonymity
23846 set. Down the road we should stop sending reasons to exit relays,
23847 or otherwise prevent future versions of this bug.
23848 - Only update guard status (usable / not usable) once we have
23849 enough directory information. This was causing us to discard all our
23850 guards on startup if we hadn't been running for a few weeks. Fixes
23852 - When our directory information has been expired for a while, stop
23853 being willing to build circuits using it. Fixes bug 401.
23855 o Major bugfixes (peace of mind for relay operators)
23856 - Non-exit relays no longer answer "resolve" relay cells, so they
23857 can't be induced to do arbitrary DNS requests. (Tor clients already
23858 avoid using non-exit relays for resolve cells, but now servers
23859 enforce this too.) Fixes bug 619. Patch from lodger.
23860 - When we setconf ClientOnly to 1, close any current OR and Dir
23861 listeners. Reported by mwenge.
23863 o Major bugfixes (other):
23864 - If we only ever used Tor for hidden service lookups or posts, we
23865 would stop building circuits and start refusing connections after
23866 24 hours, since we falsely believed that Tor was dormant. Reported
23868 - Add a new __HashedControlSessionPassword option for controllers
23869 to use for one-off session password hashes that shouldn't get
23870 saved to disk by SAVECONF --- Vidalia users were accumulating a
23871 pile of HashedControlPassword lines in their torrc files, one for
23872 each time they had restarted Tor and then clicked Save. Make Tor
23873 automatically convert "HashedControlPassword" to this new option but
23874 only when it's given on the command line. Partial fix for bug 586.
23875 - Patch from "Andrew S. Lists" to catch when we contact a directory
23876 mirror at IP address X and he says we look like we're coming from
23877 IP address X. Otherwise this would screw up our address detection.
23878 - Reject uploaded descriptors and extrainfo documents if they're
23879 huge. Otherwise we'll cache them all over the network and it'll
23880 clog everything up. Suggested by Aljosha Judmayer.
23881 - When a hidden service was trying to establish an introduction point,
23882 and Tor *did* manage to reuse one of the preemptively built
23883 circuits, it didn't correctly remember which one it used,
23884 so it asked for another one soon after, until there were no
23885 more preemptive circuits, at which point it launched one from
23886 scratch. Bugfix on 0.0.9.x.
23888 o Rate limiting and load balancing improvements:
23889 - When we add data to a write buffer in response to the data on that
23890 write buffer getting low because of a flush, do not consider the
23891 newly added data as a candidate for immediate flushing, but rather
23892 make it wait until the next round of writing. Otherwise, we flush
23893 and refill recursively, and a single greedy TLS connection can
23894 eat all of our bandwidth.
23895 - When counting the number of bytes written on a TLS connection,
23896 look at the BIO actually used for writing to the network, not
23897 at the BIO used (sometimes) to buffer data for the network.
23898 Looking at different BIOs could result in write counts on the
23899 order of ULONG_MAX. Fixes bug 614.
23900 - If we change our MaxAdvertisedBandwidth and then reload torrc,
23901 Tor won't realize it should publish a new relay descriptor. Fixes
23902 bug 688, reported by mfr.
23903 - Avoid using too little bandwidth when our clock skips a few seconds.
23904 - Choose which bridge to use proportional to its advertised bandwidth,
23905 rather than uniformly at random. This should speed up Tor for
23906 bridge users. Also do this for people who set StrictEntryNodes.
23908 o Bootstrapping faster and building circuits more intelligently:
23909 - Fix bug 660 that was preventing us from knowing that we should
23910 preemptively build circuits to handle expected directory requests.
23911 - When we're checking if we have enough dir info for each relay
23912 to begin establishing circuits, make sure that we actually have
23913 the descriptor listed in the consensus, not just any descriptor.
23914 - Correctly notify one-hop connections when a circuit build has
23915 failed. Possible fix for bug 669. Found by lodger.
23916 - Clients now hold circuitless TLS connections open for 1.5 times
23917 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
23918 rebuild a new circuit over them within that timeframe. Previously,
23919 they held them open only for KeepalivePeriod (5 minutes).
23921 o Performance improvements (memory):
23922 - Add OpenBSD malloc code from "phk" as an optional malloc
23923 replacement on Linux: some glibc libraries do very poorly with
23924 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
23925 ./configure to get the replacement malloc code.
23926 - Switch our old ring buffer implementation for one more like that
23927 used by free Unix kernels. The wasted space in a buffer with 1mb
23928 of data will now be more like 8k than 1mb. The new implementation
23929 also avoids realloc();realloc(); patterns that can contribute to
23930 memory fragmentation.
23931 - Change the way that Tor buffers data that it is waiting to write.
23932 Instead of queueing data cells in an enormous ring buffer for each
23933 client->OR or OR->OR connection, we now queue cells on a separate
23934 queue for each circuit. This lets us use less slack memory, and
23935 will eventually let us be smarter about prioritizing different kinds
23937 - Reference-count and share copies of address policy entries; only 5%
23938 of them were actually distinct.
23939 - Tune parameters for cell pool allocation to minimize amount of
23941 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
23942 for every single inactive connection_t. Free items from the
23943 4k/16k-buffer free lists when they haven't been used for a while.
23944 - Make memory debugging information describe more about history
23945 of cell allocation, so we can help reduce our memory use.
23946 - Be even more aggressive about releasing RAM from small
23947 empty buffers. Thanks to our free-list code, this shouldn't be too
23948 performance-intensive.
23949 - Log malloc statistics from mallinfo() on platforms where it exists.
23950 - Use memory pools to allocate cells with better speed and memory
23951 efficiency, especially on platforms where malloc() is inefficient.
23952 - Add a --with-tcmalloc option to the configure script to link
23953 against tcmalloc (if present). Does not yet search for non-system
23956 o Performance improvements (socket management):
23957 - Count the number of open sockets separately from the number of
23958 active connection_t objects. This will let us avoid underusing
23959 our allocated connection limit.
23960 - We no longer use socket pairs to link an edge connection to an
23961 anonymous directory connection or a DirPort test connection.
23962 Instead, we track the link internally and transfer the data
23963 in-process. This saves two sockets per "linked" connection (at the
23964 client and at the server), and avoids the nasty Windows socketpair()
23966 - We were leaking a file descriptor if Tor started with a zero-length
23967 cached-descriptors file. Patch by "freddy77".
23969 o Performance improvements (CPU use):
23970 - Never walk through the list of logs if we know that no log target
23971 is interested in a given message.
23972 - Call routerlist_remove_old_routers() much less often. This should
23973 speed startup, especially on directory caches.
23974 - Base64 decoding was actually showing up on our profile when parsing
23975 the initial descriptor file; switch to an in-process all-at-once
23976 implementation that's about 3.5x times faster than calling out to
23978 - Use a slightly simpler string hashing algorithm (copying Python's
23979 instead of Java's) and optimize our digest hashing algorithm to take
23980 advantage of 64-bit platforms and to remove some possibly-costly
23982 - When implementing AES counter mode, update only the portions of the
23983 counter buffer that need to change, and don't keep separate
23984 network-order and host-order counters on big-endian hosts (where
23985 they are the same).
23986 - Add an in-place version of aes_crypt() so that we can avoid doing a
23987 needless memcpy() call on each cell payload.
23988 - Use Critical Sections rather than Mutexes for synchronizing threads
23989 on win32; Mutexes are heavier-weight, and designed for synchronizing
23992 o Performance improvements (bandwidth use):
23993 - Don't try to launch new descriptor downloads quite so often when we
23994 already have enough directory information to build circuits.
23995 - Version 1 directories are no longer generated in full. Instead,
23996 authorities generate and serve "stub" v1 directories that list
23997 no servers. This will stop Tor versions 0.1.0.x and earlier from
23998 working, but (for security reasons) nobody should be running those
24000 - Avoid going directly to the directory authorities even if you're a
24001 relay, if you haven't found yourself reachable yet or if you've
24002 decided not to advertise your dirport yet. Addresses bug 556.
24003 - If we've gone 12 hours since our last bandwidth check, and we
24004 estimate we have less than 50KB bandwidth capacity but we could
24005 handle more, do another bandwidth test.
24006 - Support "If-Modified-Since" when answering HTTP requests for
24007 directories, running-routers documents, and v2 and v3 networkstatus
24008 documents. (There's no need to support it for router descriptors,
24009 since those are downloaded by descriptor digest.)
24010 - Stop fetching directory info so aggressively if your DirPort is
24011 on but your ORPort is off; stop fetching v2 dir info entirely.
24012 You can override these choices with the new FetchDirInfoEarly
24015 o Changed config option behavior (features):
24016 - Configuration files now accept C-style strings as values. This
24017 helps encode characters not allowed in the current configuration
24018 file format, such as newline or #. Addresses bug 557.
24019 - Add hidden services and DNSPorts to the list of things that make
24020 Tor accept that it has running ports. Change starting Tor with no
24021 ports from a fatal error to a warning; we might change it back if
24022 this turns out to confuse anybody. Fixes bug 579.
24023 - Make PublishServerDescriptor default to 1, so the default doesn't
24024 have to change as we invent new directory protocol versions.
24025 - Allow people to say PreferTunnelledDirConns rather than
24026 PreferTunneledDirConns, for those alternate-spellers out there.
24027 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
24028 accommodate the growing number of servers that use the default
24029 and are reaching it.
24030 - Make it possible to enable HashedControlPassword and
24031 CookieAuthentication at the same time.
24032 - When a TrackHostExits-chosen exit fails too many times in a row,
24033 stop using it. Fixes bug 437.
24035 o Changed config option behavior (bugfixes):
24036 - Do not read the configuration file when we've only been told to
24037 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
24038 based on patch from Sebastian Hahn.
24039 - Actually validate the options passed to AuthDirReject,
24040 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
24041 - Make "ClientOnly 1" config option disable directory ports too.
24042 - Don't stop fetching descriptors when FetchUselessDescriptors is
24043 set, even if we stop asking for circuits. Bug reported by tup
24045 - Servers used to decline to publish their DirPort if their
24046 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
24047 they look only at BandwidthRate and RelayBandwidthRate.
24048 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
24049 minus 1 byte: the actual maximum declared bandwidth.
24050 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
24051 - Make the NodeFamilies config option work. (Reported by
24052 lodger -- it has never actually worked, even though we added it
24054 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
24055 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
24057 o New config options:
24058 - New configuration options AuthDirMaxServersPerAddr and
24059 AuthDirMaxServersperAuthAddr to override default maximum number
24060 of servers allowed on a single IP address. This is important for
24061 running a test network on a single host.
24062 - Three new config options (AlternateDirAuthority,
24063 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
24064 user selectively replace the default directory authorities by type,
24065 rather than the all-or-nothing replacement that DirServer offers.
24066 - New config options AuthDirBadDir and AuthDirListBadDirs for
24067 authorities to mark certain relays as "bad directories" in the
24068 networkstatus documents. Also supports the "!baddir" directive in
24069 the approved-routers file.
24070 - New config option V2AuthoritativeDirectory that all v2 directory
24071 authorities must set. This lets v3 authorities choose not to serve
24072 v2 directory information.
24074 o Minor features (other):
24075 - When we're not serving v2 directory information, there is no reason
24076 to actually keep any around. Remove the obsolete files and directory
24077 on startup if they are very old and we aren't going to serve them.
24078 - When we negotiate a v2 link-layer connection (not yet implemented),
24079 accept RELAY_EARLY cells and turn them into RELAY cells if we've
24080 negotiated a v1 connection for their next step. Initial steps for
24082 - When we have no consensus, check FallbackNetworkstatusFile (defaults
24083 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
24084 we can start out knowing some directory caches. We don't ship with
24085 a fallback consensus by default though, because it was making
24086 bootstrapping take too long while we tried many down relays.
24087 - Authorities send back an X-Descriptor-Not-New header in response to
24088 an accepted-but-discarded descriptor upload. Partially implements
24090 - If we find a cached-routers file that's been sitting around for more
24091 than 28 days unmodified, then most likely it's a leftover from
24092 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
24094 - When we (as a cache) download a descriptor because it was listed
24095 in a consensus, remember when the consensus was supposed to expire,
24096 and don't expire the descriptor until then.
24097 - Optionally (if built with -DEXPORTMALLINFO) export the output
24098 of mallinfo via http, as tor/mallinfo.txt. Only accessible
24100 - Tag every guard node in our state file with the version that
24101 we believe added it, or with our own version if we add it. This way,
24102 if a user temporarily runs an old version of Tor and then switches
24103 back to a new one, she doesn't automatically lose her guards.
24104 - When somebody requests a list of statuses or servers, and we have
24105 none of those, return a 404 rather than an empty 200.
24106 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
24108 - Add an HSAuthorityRecordStats option that hidden service authorities
24109 can use to track statistics of overall hidden service usage without
24110 logging information that would be as useful to an attacker.
24111 - Allow multiple HiddenServicePort directives with the same virtual
24112 port; when they occur, the user is sent round-robin to one
24113 of the target ports chosen at random. Partially fixes bug 393 by
24114 adding limited ad-hoc round-robining.
24115 - Revamp file-writing logic so we don't need to have the entire
24116 contents of a file in memory at once before we write to disk. Tor,
24119 o Minor bugfixes (other):
24120 - Alter the code that tries to recover from unhandled write
24121 errors, to not try to flush onto a socket that's given us
24123 - Directory mirrors no longer include a guess at the client's IP
24124 address if the connection appears to be coming from the same /24
24125 network; it was producing too many wrong guesses.
24126 - If we're trying to flush the last bytes on a connection (for
24127 example, when answering a directory request), reset the
24128 time-to-give-up timeout every time we manage to write something
24130 - Reject router descriptors with out-of-range bandwidthcapacity or
24131 bandwidthburst values.
24132 - If we can't expand our list of entry guards (e.g. because we're
24133 using bridges or we have StrictEntryNodes set), don't mark relays
24134 down when they fail a directory request. Otherwise we're too quick
24135 to mark all our entry points down.
24136 - Authorities no longer send back "400 you're unreachable please fix
24137 it" errors to Tor servers that aren't online all the time. We're
24138 supposed to tolerate these servers now.
24139 - Let directory authorities startup even when they can't generate
24140 a descriptor immediately, e.g. because they don't know their
24142 - Correctly enforce that elements of directory objects do not appear
24143 more often than they are allowed to appear.
24144 - Stop allowing hibernating servers to be "stable" or "fast".
24145 - On Windows, we were preventing other processes from reading
24146 cached-routers while Tor was running. (Reported by janbar)
24147 - Check return values from pthread_mutex functions.
24148 - When opening /dev/null in finish_daemonize(), do not pass the
24149 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
24150 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
24152 o Controller features:
24153 - The GETCONF command now escapes and quotes configuration values
24154 that don't otherwise fit into the torrc file.
24155 - The SETCONF command now handles quoted values correctly.
24156 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
24157 ask about source, timestamp of arrival, purpose, etc. We need
24158 something like this to help Vidalia not do GeoIP lookups on bridge
24160 - Allow multiple HashedControlPassword config lines, to support
24161 multiple controller passwords.
24162 - Accept LF instead of CRLF on controller, since some software has a
24163 hard time generating real Internet newlines.
24164 - Add GETINFO values for the server status events
24165 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
24167 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
24168 GETINFO for Torstat to use until it can switch to using extrainfos.
24169 - New config option CookieAuthFile to choose a new location for the
24170 cookie authentication file, and config option
24171 CookieAuthFileGroupReadable to make it group-readable.
24172 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
24173 match requests to applications. Patch from Robert Hogan.
24174 - Add a RESOLVE command to launch hostname lookups. Original patch
24176 - Add GETINFO status/enough-dir-info to let controllers tell whether
24177 Tor has downloaded sufficient directory information. Patch from Tup.
24178 - You can now use the ControlSocket option to tell Tor to listen for
24179 controller connections on Unix domain sockets on systems that
24180 support them. Patch from Peter Palfrader.
24181 - New "GETINFO address-mappings/*" command to get address mappings
24182 with expiry information. "addr-mappings/*" is now deprecated.
24184 - Add a new config option __DisablePredictedCircuits designed for
24185 use by the controller, when we don't want Tor to build any circuits
24187 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
24188 so we can exit from the middle of the circuit.
24189 - Implement "getinfo status/circuit-established".
24190 - Implement "getinfo status/version/..." so a controller can tell
24191 whether the current version is recommended, and whether any versions
24192 are good, and how many authorities agree. Patch from "shibz".
24193 - Controllers should now specify cache=no or cache=yes when using
24194 the +POSTDESCRIPTOR command.
24195 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
24196 Robert Hogan. Fixes the first part of bug 681.
24197 - When reporting clock skew, and we know that the clock is _at least
24198 as skewed_ as some value, but we don't know the actual value,
24199 report the value as a "minimum skew."
24201 o Controller bugfixes:
24202 - Generate "STATUS_SERVER" events rather than misspelled
24203 "STATUS_SEVER" events. Caught by mwenge.
24204 - Reject controller commands over 1MB in length, so rogue
24205 processes can't run us out of memory.
24206 - Change the behavior of "getinfo status/good-server-descriptor"
24207 so it doesn't return failure when any authority disappears.
24208 - Send NAMESERVER_STATUS messages for a single failed nameserver
24210 - When the DANGEROUS_VERSION controller status event told us we're
24211 running an obsolete version, it used the string "OLD" to describe
24212 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
24213 "OBSOLETE" in both cases.
24214 - Respond to INT and TERM SIGNAL commands before we execute the
24215 signal, in case the signal shuts us down. We had a patch in
24216 0.1.2.1-alpha that tried to do this by queueing the response on
24217 the connection's buffer before shutting down, but that really
24218 isn't the same thing at all. Bug located by Matt Edman.
24219 - Provide DNS expiry times in GMT, not in local time. For backward
24220 compatibility, ADDRMAP events only provide GMT expiry in an extended
24221 field. "GETINFO address-mappings" always does the right thing.
24222 - Use CRLF line endings properly in NS events.
24223 - Make 'getinfo fingerprint' return a 551 error if we're not a
24224 server, so we match what the control spec claims we do. Reported
24226 - Fix a typo in an error message when extendcircuit fails that
24227 caused us to not follow the \r\n-based delimiter protocol. Reported
24229 - When tunneling an encrypted directory connection, and its first
24230 circuit fails, do not leave it unattached and ask the controller
24231 to deal. Fixes the second part of bug 681.
24232 - Treat some 403 responses from directory servers as INFO rather than
24233 WARN-severity events.
24235 o Portability / building / compiling:
24236 - When building with --enable-gcc-warnings, check for whether Apple's
24237 warning "-Wshorten-64-to-32" is available.
24238 - Support compilation to target iPhone; patch from cjacker huang.
24239 To build for iPhone, pass the --enable-iphone option to configure.
24240 - Port Tor to build and run correctly on Windows CE systems, using
24241 the wcecompat library. Contributed by Valerio Lupi.
24242 - Detect non-ASCII platforms (if any still exist) and refuse to
24243 build there: some of our code assumes that 'A' is 65 and so on.
24244 - Clear up some MIPSPro compiler warnings.
24245 - Make autoconf search for libevent, openssl, and zlib consistently.
24246 - Update deprecated macros in configure.in.
24247 - When warning about missing headers, tell the user to let us
24248 know if the compile succeeds anyway, so we can downgrade the
24250 - Include the current subversion revision as part of the version
24251 string: either fetch it directly if we're in an SVN checkout, do
24252 some magic to guess it if we're in an SVK checkout, or use
24253 the last-detected version if we're building from a .tar.gz.
24254 Use this version consistently in log messages.
24255 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
24256 - Read resolv.conf files correctly on platforms where read() returns
24257 partial results on small file reads.
24258 - Build without verbose warnings even on gcc 4.2 and 4.3.
24259 - On Windows, correctly detect errors when listing the contents of
24260 a directory. Fix from lodger.
24261 - Run 'make test' as part of 'make dist', so we stop releasing so
24262 many development snapshots that fail their unit tests.
24263 - Add support to detect Libevent versions in the 1.4.x series
24265 - Add command-line arguments to unit-test executable so that we can
24266 invoke any chosen test from the command line rather than having
24267 to run the whole test suite at once; and so that we can turn on
24268 logging for the unit tests.
24269 - Do not automatically run configure from autogen.sh. This
24270 non-standard behavior tended to annoy people who have built other
24272 - Fix a macro/CPP interaction that was confusing some compilers:
24273 some GCCs don't like #if/#endif pairs inside macro arguments.
24275 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
24276 Fixes bug 704; fix from Steven Murdoch.
24277 - Correctly detect transparent proxy support on Linux hosts that
24278 require in.h to be included before netfilter_ipv4.h. Patch
24281 o Logging improvements:
24282 - When we haven't had any application requests lately, don't bother
24283 logging that we have expired a bunch of descriptors.
24284 - When attempting to open a logfile fails, tell us why.
24285 - Only log guard node status when guard node status has changed.
24286 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
24287 make "INFO" 75% less verbose.
24288 - When SafeLogging is disabled, log addresses along with all TLS
24290 - Report TLS "zero return" case as a "clean close" and "IO error"
24291 as a "close". Stop calling closes "unexpected closes": existing
24292 Tors don't use SSL_close(), so having a connection close without
24293 the TLS shutdown handshake is hardly unexpected.
24294 - When we receive a consensus from the future, warn about skew.
24295 - Make "not enough dir info yet" warnings describe *why* Tor feels
24296 it doesn't have enough directory info yet.
24297 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
24298 consumers. (We already do this on HUP.)
24299 - Give more descriptive well-formedness errors for out-of-range
24300 hidden service descriptor/protocol versions.
24301 - Stop recommending that every server operator send mail to tor-ops.
24302 Resolves bug 597. Bugfix on 0.1.2.x.
24303 - Improve skew reporting: try to give the user a better log message
24304 about how skewed they are, and how much this matters.
24305 - New --quiet command-line option to suppress the default console log.
24306 Good in combination with --hash-password.
24307 - Don't complain that "your server has not managed to confirm that its
24308 ports are reachable" if we haven't been able to build any circuits
24310 - Detect the reason for failing to mmap a descriptor file we just
24311 wrote, and give a more useful log message. Fixes bug 533.
24312 - Always prepend "Bug: " to any log message about a bug.
24313 - When dumping memory usage, list bytes used in buffer memory
24315 - When running with dmalloc, dump more stats on hup and on exit.
24316 - Put a platform string (e.g. "Linux i686") in the startup log
24317 message, so when people paste just their logs, we know if it's
24318 OpenBSD or Windows or what.
24319 - When logging memory usage, break down memory used in buffers by
24321 - When we are reporting the DirServer line we just parsed, we were
24322 logging the second stanza of the key fingerprint, not the first.
24323 - Even though Windows is equally happy with / and \ as path separators,
24324 try to use \ consistently on Windows and / consistently on Unix: it
24325 makes the log messages nicer.
24326 - On OSX, stop warning the user that kqueue support in libevent is
24327 "experimental", since it seems to have worked fine for ages.
24329 o Contributed scripts and tools:
24330 - Update linux-tor-prio.sh script to allow QoS based on the uid of
24331 the Tor process. Patch from Marco Bonetti with tweaks from Mike
24333 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
24334 Unix users an easy way to script their Tor process (e.g. by
24335 adjusting bandwidth based on the time of the day).
24336 - In the exitlist script, only consider the most recently published
24337 server descriptor for each server. Also, when the user requests
24338 a list of servers that _reject_ connections to a given address,
24339 explicitly exclude the IPs that also have servers that accept
24340 connections to that address. Resolves bug 405.
24341 - Include a new contrib/tor-exit-notice.html file that exit relay
24342 operators can put on their website to help reduce abuse queries.
24344 o Newly deprecated features:
24345 - The status/version/num-versioning and status/version/num-concurring
24346 GETINFO controller options are no longer useful in the v3 directory
24347 protocol: treat them as deprecated, and warn when they're used.
24348 - The RedirectExits config option is now deprecated.
24350 o Removed features:
24351 - Drop the old code to choke directory connections when the
24352 corresponding OR connections got full: thanks to the cell queue
24353 feature, OR conns don't get full any more.
24354 - Remove the old "dns worker" server DNS code: it hasn't been default
24355 since 0.1.2.2-alpha, and all the servers are using the new
24357 - Remove the code to generate the oldest (v1) directory format.
24358 - Remove support for the old bw_accounting file: we've been storing
24359 bandwidth accounting information in the state file since
24360 0.1.2.5-alpha. This may result in bandwidth accounting errors
24361 if you try to upgrade from 0.1.1.x or earlier, or if you try to
24362 downgrade to 0.1.1.x or earlier.
24363 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
24364 it, it had no AES, and it hasn't seen any security patches since
24366 - Stop overloading the circuit_t.onionskin field for both "onionskin
24367 from a CREATE cell that we are waiting for a cpuworker to be
24368 assigned" and "onionskin from an EXTEND cell that we are going to
24369 send to an OR as soon as we are connected". Might help with bug 600.
24370 - Remove the tor_strpartition() function: its logic was confused,
24371 and it was only used for one thing that could be implemented far
24373 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
24374 and TorControl.py, as they use the old v0 controller protocol,
24375 and are obsoleted by TorFlow anyway.
24376 - Drop support for v1 rendezvous descriptors, since we never used
24377 them anyway, and the code has probably rotted by now. Based on
24378 patch from Karsten Loesing.
24379 - Stop allowing address masks that do not correspond to bit prefixes.
24380 We have warned about these for a really long time; now it's time
24381 to reject them. (Patch from croup.)
24382 - Remove an optimization in the AES counter-mode code that assumed
24383 that the counter never exceeded 2^68. When the counter can be set
24384 arbitrarily as an IV (as it is by Karsten's new hidden services
24385 code), this assumption no longer holds.
24386 - Disable the SETROUTERPURPOSE controller command: it is now
24390 Changes in version 0.1.2.19 - 2008-01-17
24391 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
24392 exit policy a little bit more conservative so it's safer to run an
24393 exit relay on a home system, and fixes a variety of smaller issues.
24396 - Exit policies now reject connections that are addressed to a
24397 relay's public (external) IP address too, unless
24398 ExitPolicyRejectPrivate is turned off. We do this because too
24399 many relays are running nearby to services that trust them based
24400 on network address.
24403 - When the clock jumps forward a lot, do not allow the bandwidth
24404 buckets to become negative. Fixes bug 544.
24405 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
24406 on every successful resolve. Reported by Mike Perry.
24407 - Purge old entries from the "rephist" database and the hidden
24408 service descriptor database even when DirPort is zero.
24409 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
24410 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
24411 crashing or mis-answering these requests.
24412 - When we decide to send a 503 response to a request for servers, do
24413 not then also send the server descriptors: this defeats the whole
24414 purpose. Fixes bug 539.
24417 - Changing the ExitPolicyRejectPrivate setting should cause us to
24418 rebuild our server descriptor.
24419 - Fix handling of hex nicknames when answering controller requests for
24420 networkstatus by name, or when deciding whether to warn about
24421 unknown routers in a config option. (Patch from mwenge.)
24422 - Fix a couple of hard-to-trigger autoconf problems that could result
24423 in really weird results on platforms whose sys/types.h files define
24424 nonstandard integer types.
24425 - Don't try to create the datadir when running --verify-config or
24426 --hash-password. Resolves bug 540.
24427 - If we were having problems getting a particular descriptor from the
24428 directory caches, and then we learned about a new descriptor for
24429 that router, we weren't resetting our failure count. Reported
24431 - Although we fixed bug 539 (where servers would send HTTP status 503
24432 responses _and_ send a body too), there are still servers out there
24433 that haven't upgraded. Therefore, make clients parse such bodies
24434 when they receive them.
24435 - Run correctly on systems where rlim_t is larger than unsigned long.
24436 This includes some 64-bit systems.
24437 - Run correctly on platforms (like some versions of OS X 10.5) where
24438 the real limit for number of open files is OPEN_FILES, not rlim_max
24439 from getrlimit(RLIMIT_NOFILES).
24440 - Avoid a spurious free on base64 failure.
24441 - Avoid segfaults on certain complex invocations of
24442 router_get_by_hexdigest().
24443 - Fix rare bug on REDIRECTSTREAM control command when called with no
24444 port set: it could erroneously report an error when none had
24448 Changes in version 0.1.2.18 - 2007-10-28
24449 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
24450 hidden service introduction that were causing huge delays, and a big
24451 bug that was causing some servers to disappear from the network status
24452 lists for a few hours each day.
24454 o Major bugfixes (crashes):
24455 - If a connection is shut down abruptly because of something that
24456 happened inside connection_flushed_some(), do not call
24457 connection_finished_flushing(). Should fix bug 451:
24458 "connection_stop_writing: Assertion conn->write_event failed"
24459 Bugfix on 0.1.2.7-alpha.
24460 - Fix possible segfaults in functions called from
24461 rend_process_relay_cell().
24463 o Major bugfixes (hidden services):
24464 - Hidden services were choosing introduction points uniquely by
24465 hexdigest, but when constructing the hidden service descriptor
24466 they merely wrote the (potentially ambiguous) nickname.
24467 - Clients now use the v2 intro format for hidden service
24468 connections: they specify their chosen rendezvous point by identity
24469 digest rather than by (potentially ambiguous) nickname. These
24470 changes could speed up hidden service connections dramatically.
24472 o Major bugfixes (other):
24473 - Stop publishing a new server descriptor just because we get a
24474 HUP signal. This led (in a roundabout way) to some servers getting
24475 dropped from the networkstatus lists for a few hours each day.
24476 - When looking for a circuit to cannibalize, consider family as well
24477 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
24478 circuit cannibalization).
24479 - When a router wasn't listed in a new networkstatus, we were leaving
24480 the flags for that router alone -- meaning it remained Named,
24481 Running, etc -- even though absence from the networkstatus means
24482 that it shouldn't be considered to exist at all anymore. Now we
24483 clear all the flags for routers that fall out of the networkstatus
24484 consensus. Fixes bug 529.
24487 - Don't try to access (or alter) the state file when running
24488 --list-fingerprint or --verify-config or --hash-password. Resolves
24490 - When generating information telling us how to extend to a given
24491 router, do not try to include the nickname if it is
24492 absent. Resolves bug 467.
24493 - Fix a user-triggerable segfault in expand_filename(). (There isn't
24494 a way to trigger this remotely.)
24495 - When sending a status event to the controller telling it that an
24496 OR address is reachable, set the port correctly. (Previously we
24497 were reporting the dir port.)
24498 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
24499 command. Bugfix on 0.1.2.17.
24500 - When loading bandwidth history, do not believe any information in
24501 the future. Fixes bug 434.
24502 - When loading entry guard information, do not believe any information
24504 - When we have our clock set far in the future and generate an
24505 onion key, then re-set our clock to be correct, we should not stop
24506 the onion key from getting rotated.
24507 - On some platforms, accept() can return a broken address. Detect
24508 this more quietly, and deal accordingly. Fixes bug 483.
24509 - It's not actually an error to find a non-pending entry in the DNS
24510 cache when canceling a pending resolve. Don't log unless stuff
24511 is fishy. Resolves bug 463.
24512 - Don't reset trusted dir server list when we set a configuration
24513 option. Patch from Robert Hogan.
24516 Changes in version 0.1.2.17 - 2007-08-30
24517 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
24518 X bundles. Vidalia 0.0.14 makes authentication required for the
24519 ControlPort in the default configuration, which addresses important
24520 security risks. Everybody who uses Vidalia (or another controller)
24523 In addition, this Tor update fixes major load balancing problems with
24524 path selection, which should speed things up a lot once many people
24527 o Major bugfixes (security):
24528 - We removed support for the old (v0) control protocol. It has been
24529 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
24530 become more of a headache than it's worth.
24532 o Major bugfixes (load balancing):
24533 - When choosing nodes for non-guard positions, weight guards
24534 proportionally less, since they already have enough load. Patch
24536 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
24537 will allow fast Tor servers to get more attention.
24538 - When we're upgrading from an old Tor version, forget our current
24539 guards and pick new ones according to the new weightings. These
24540 three load balancing patches could raise effective network capacity
24541 by a factor of four. Thanks to Mike Perry for measurements.
24543 o Major bugfixes (stream expiration):
24544 - Expire not-yet-successful application streams in all cases if
24545 they've been around longer than SocksTimeout. Right now there are
24546 some cases where the stream will live forever, demanding a new
24547 circuit every 15 seconds. Fixes bug 454; reported by lodger.
24549 o Minor features (controller):
24550 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
24551 is valid before any authentication has been received. It tells
24552 a controller what kind of authentication is expected, and what
24553 protocol is spoken. Implements proposal 119.
24555 o Minor bugfixes (performance):
24556 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
24557 greatly speeding up loading cached-routers from disk on startup.
24558 - Disable sentinel-based debugging for buffer code: we squashed all
24559 the bugs that this was supposed to detect a long time ago, and now
24560 its only effect is to change our buffer sizes from nice powers of
24561 two (which platform mallocs tend to like) to values slightly over
24562 powers of two (which make some platform mallocs sad).
24564 o Minor bugfixes (misc):
24565 - If exit bandwidth ever exceeds one third of total bandwidth, then
24566 use the correct formula to weight exit nodes when choosing paths.
24567 Based on patch from Mike Perry.
24568 - Choose perfectly fairly among routers when choosing by bandwidth and
24569 weighting by fraction of bandwidth provided by exits. Previously, we
24570 would choose with only approximate fairness, and correct ourselves
24571 if we ran off the end of the list.
24572 - If we require CookieAuthentication but we fail to write the
24573 cookie file, we would warn but not exit, and end up in a state
24574 where no controller could authenticate. Now we exit.
24575 - If we require CookieAuthentication, stop generating a new cookie
24576 every time we change any piece of our config.
24577 - Refuse to start with certain directory authority keys, and
24578 encourage people using them to stop.
24579 - Terminate multi-line control events properly. Original patch
24581 - Fix a minor memory leak when we fail to find enough suitable
24582 servers to choose a circuit.
24583 - Stop leaking part of the descriptor when we run into a particularly
24584 unparseable piece of it.
24587 Changes in version 0.1.2.16 - 2007-08-01
24588 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
24589 remote attacker in certain situations to rewrite the user's torrc
24590 configuration file. This can completely compromise anonymity of users
24591 in most configurations, including those running the Vidalia bundles,
24592 TorK, etc. Or worse.
24594 o Major security fixes:
24595 - Close immediately after missing authentication on control port;
24596 do not allow multiple authentication attempts.
24599 Changes in version 0.1.2.15 - 2007-07-17
24600 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
24601 problems, fixes compilation on BSD, and fixes a variety of other
24602 bugs. Everybody should upgrade.
24604 o Major bugfixes (compilation):
24605 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
24607 o Major bugfixes (crashes):
24608 - Try even harder not to dereference the first character after
24609 an mmap(). Reported by lodger.
24610 - Fix a crash bug in directory authorities when we re-number the
24611 routerlist while inserting a new router.
24612 - When the cached-routers file is an even multiple of the page size,
24613 don't run off the end and crash. (Fixes bug 455; based on idea
24615 - Fix eventdns.c behavior on Solaris: It is critical to include
24616 orconfig.h _before_ sys/types.h, so that we can get the expected
24617 definition of _FILE_OFFSET_BITS.
24619 o Major bugfixes (security):
24620 - Fix a possible buffer overrun when using BSD natd support. Bug
24622 - When sending destroy cells from a circuit's origin, don't include
24623 the reason for tearing down the circuit. The spec says we didn't,
24624 and now we actually don't. Reported by lodger.
24625 - Keep streamids from different exits on a circuit separate. This
24626 bug may have allowed other routers on a given circuit to inject
24627 cells into streams. Reported by lodger; fixes bug 446.
24628 - If there's a never-before-connected-to guard node in our list,
24629 never choose any guards past it. This way we don't expand our
24630 guard list unless we need to.
24632 o Minor bugfixes (guard nodes):
24633 - Weight guard selection by bandwidth, so that low-bandwidth nodes
24634 don't get overused as guards.
24636 o Minor bugfixes (directory):
24637 - Correctly count the number of authorities that recommend each
24638 version. Previously, we were under-counting by 1.
24639 - Fix a potential crash bug when we load many server descriptors at
24640 once and some of them make others of them obsolete. Fixes bug 458.
24642 o Minor bugfixes (hidden services):
24643 - Stop tearing down the whole circuit when the user asks for a
24644 connection to a port that the hidden service didn't configure.
24647 o Minor bugfixes (misc):
24648 - On Windows, we were preventing other processes from reading
24649 cached-routers while Tor was running. Reported by janbar.
24650 - Fix a possible (but very unlikely) bug in picking routers by
24651 bandwidth. Add a log message to confirm that it is in fact
24652 unlikely. Patch from lodger.
24653 - Backport a couple of memory leak fixes.
24654 - Backport miscellaneous cosmetic bugfixes.
24657 Changes in version 0.1.2.14 - 2007-05-25
24658 Tor 0.1.2.14 changes the addresses of two directory authorities (this
24659 change especially affects those who serve or use hidden services),
24660 and fixes several other crash- and security-related bugs.
24662 o Directory authority changes:
24663 - Two directory authorities (moria1 and moria2) just moved to new
24664 IP addresses. This change will particularly affect those who serve
24665 or use hidden services.
24667 o Major bugfixes (crashes):
24668 - If a directory server runs out of space in the connection table
24669 as it's processing a begin_dir request, it will free the exit stream
24670 but leave it attached to the circuit, leading to unpredictable
24671 behavior. (Reported by seeess, fixes bug 425.)
24672 - Fix a bug in dirserv_remove_invalid() that would cause authorities
24673 to corrupt memory under some really unlikely scenarios.
24674 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
24675 - Avoid segfaults when reading from mmaped descriptor file. (Reported
24678 o Major bugfixes (security):
24679 - When choosing an entry guard for a circuit, avoid using guards
24680 that are in the same family as the chosen exit -- not just guards
24681 that are exactly the chosen exit. (Reported by lodger.)
24683 o Major bugfixes (resource management):
24684 - If a directory authority is down, skip it when deciding where to get
24685 networkstatus objects or descriptors. Otherwise we keep asking
24686 every 10 seconds forever. Fixes bug 384.
24687 - Count it as a failure if we fetch a valid network-status but we
24688 don't want to keep it. Otherwise we'll keep fetching it and keep
24689 not wanting to keep it. Fixes part of bug 422.
24690 - If all of our dirservers have given us bad or no networkstatuses
24691 lately, then stop hammering them once per minute even when we
24692 think they're failed. Fixes another part of bug 422.
24695 - Actually set the purpose correctly for descriptors inserted with
24696 purpose=controller.
24697 - When we have k non-v2 authorities in our DirServer config,
24698 we ignored the last k authorities in the list when updating our
24700 - Correctly back-off from requesting router descriptors that we are
24701 having a hard time downloading.
24702 - Read resolv.conf files correctly on platforms where read() returns
24703 partial results on small file reads.
24704 - Don't rebuild the entire router store every time we get 32K of
24705 routers: rebuild it when the journal gets very large, or when
24706 the gaps in the store get very large.
24709 - When routers publish SVN revisions in their router descriptors,
24710 authorities now include those versions correctly in networkstatus
24712 - Warn when using a version of libevent before 1.3b to run a server on
24713 OSX or BSD: these versions interact badly with userspace threads.
24716 Changes in version 0.1.2.13 - 2007-04-24
24717 This release features some major anonymity fixes, such as safer path
24718 selection; better client performance; faster bootstrapping, better
24719 address detection, and better DNS support for servers; write limiting as
24720 well as read limiting to make servers easier to run; and a huge pile of
24721 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
24723 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
24724 of the Freenode IRC network, remembering his patience and vision for
24725 free speech on the Internet.
24727 o Major features, client performance:
24728 - Weight directory requests by advertised bandwidth. Now we can
24729 let servers enable write limiting but still allow most clients to
24730 succeed at their directory requests. (We still ignore weights when
24731 choosing a directory authority; I hope this is a feature.)
24732 - Stop overloading exit nodes -- avoid choosing them for entry or
24733 middle hops when the total bandwidth available from non-exit nodes
24734 is much higher than the total bandwidth available from exit nodes.
24735 - Rather than waiting a fixed amount of time between retrying
24736 application connections, we wait only 10 seconds for the first,
24737 10 seconds for the second, and 15 seconds for each retry after
24738 that. Hopefully this will improve the expected user experience.
24739 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
24740 to open a stream fails; now we do in more cases. This should
24741 make clients able to find a good exit faster in some cases, since
24742 unhandleable requests will now get an error rather than timing out.
24744 o Major features, client functionality:
24745 - Implement BEGIN_DIR cells, so we can connect to a directory
24746 server via TLS to do encrypted directory requests rather than
24747 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
24748 config options if you like. For now, this feature only works if
24749 you already have a descriptor for the destination dirserver.
24750 - Add support for transparent application connections: this basically
24751 bundles the functionality of trans-proxy-tor into the Tor
24752 mainline. Now hosts with compliant pf/netfilter implementations
24753 can redirect TCP connections straight to Tor without diverting
24754 through SOCKS. (Based on patch from tup.)
24755 - Add support for using natd; this allows FreeBSDs earlier than
24756 5.1.2 to have ipfw send connections through Tor without using
24757 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
24759 o Major features, servers:
24760 - Setting up a dyndns name for your server is now optional: servers
24761 with no hostname or IP address will learn their IP address by
24762 asking the directory authorities. This code only kicks in when you
24763 would normally have exited with a "no address" error. Nothing's
24764 authenticated, so use with care.
24765 - Directory servers now spool server descriptors, v1 directories,
24766 and v2 networkstatus objects to buffers as needed rather than en
24767 masse. They also mmap the cached-routers files. These steps save
24769 - Stop requiring clients to have well-formed certificates, and stop
24770 checking nicknames in certificates. (Clients have certificates so
24771 that they can look like Tor servers, but in the future we might want
24772 to allow them to look like regular TLS clients instead. Nicknames
24773 in certificates serve no purpose other than making our protocol
24774 easier to recognize on the wire.) Implements proposal 106.
24776 o Improvements on DNS support:
24777 - Add "eventdns" asynchronous dns library originally based on code
24778 from Adam Langley. Now we can discard the old rickety dnsworker
24779 concept, and support a wider variety of DNS functions. Allows
24780 multithreaded builds on NetBSD and OpenBSD again.
24781 - Add server-side support for "reverse" DNS lookups (using PTR
24782 records so clients can determine the canonical hostname for a given
24783 IPv4 address). Only supported by servers using eventdns; servers
24784 now announce in their descriptors if they don't support eventdns.
24785 - Workaround for name servers (like Earthlink's) that hijack failing
24786 DNS requests and replace the no-such-server answer with a "helpful"
24787 redirect to an advertising-driven search portal. Also work around
24788 DNS hijackers who "helpfully" decline to hijack known-invalid
24789 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
24790 lets you turn it off.
24791 - Servers now check for the case when common DNS requests are going to
24792 wildcarded addresses (i.e. all getting the same answer), and change
24793 their exit policy to reject *:* if it's happening.
24794 - When asked to resolve a hostname, don't use non-exit servers unless
24795 requested to do so. This allows servers with broken DNS to be
24796 useful to the network.
24797 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
24798 useless IPv6 DNS resolves.
24799 - Specify and implement client-side SOCKS5 interface for reverse DNS
24800 lookups (see doc/socks-extensions.txt). Also cache them.
24801 - When we change nameservers or IP addresses, reset and re-launch
24802 our tests for DNS hijacking.
24804 o Improvements on reachability testing:
24805 - Servers send out a burst of long-range padding cells once they've
24806 established that they're reachable. Spread them over 4 circuits,
24807 so hopefully a few will be fast. This exercises bandwidth and
24808 bootstraps them into the directory more quickly.
24809 - When we find our DirPort to be reachable, publish a new descriptor
24810 so we'll tell the world (reported by pnx).
24811 - Directory authorities now only decide that routers are reachable
24812 if their identity keys are as expected.
24813 - Do DirPort reachability tests less often, since a single test
24814 chews through many circuits before giving up.
24815 - Avoid some false positives during reachability testing: don't try
24816 to test via a server that's on the same /24 network as us.
24817 - Start publishing one minute or so after we find our ORPort
24818 to be reachable. This will help reduce the number of descriptors
24819 we have for ourselves floating around, since it's quite likely
24820 other things (e.g. DirPort) will change during that minute too.
24821 - Routers no longer try to rebuild long-term connections to directory
24822 authorities, and directory authorities no longer try to rebuild
24823 long-term connections to all servers. We still don't hang up
24824 connections in these two cases though -- we need to look at it
24825 more carefully to avoid flapping, and we likely need to wait til
24826 0.1.1.x is obsolete.
24828 o Improvements on rate limiting:
24829 - Enable write limiting as well as read limiting. Now we sacrifice
24830 capacity if we're pushing out lots of directory traffic, rather
24831 than overrunning the user's intended bandwidth limits.
24832 - Include TLS overhead when counting bandwidth usage; previously, we
24833 would count only the bytes sent over TLS, but not the bytes used
24835 - Servers decline directory requests much more aggressively when
24836 they're low on bandwidth. Otherwise they end up queueing more and
24837 more directory responses, which can't be good for latency.
24838 - But never refuse directory requests from local addresses.
24839 - Be willing to read or write on local connections (e.g. controller
24840 connections) even when the global rate limiting buckets are empty.
24841 - Flush local controller connection buffers periodically as we're
24842 writing to them, so we avoid queueing 4+ megabytes of data before
24844 - Revise and clean up the torrc.sample that we ship with; add
24845 a section for BandwidthRate and BandwidthBurst.
24847 o Major features, NT services:
24848 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
24849 command-line flag so that admins can override the default by saying
24850 "tor --service install --user "SomeUser"". This will not affect
24851 existing installed services. Also, warn the user that the service
24852 will look for its configuration file in the service user's
24853 %appdata% directory. (We can't do the "hardwire the user's appdata
24854 directory" trick any more, since we may not have read access to that
24856 - Support running the Tor service with a torrc not in the same
24857 directory as tor.exe and default to using the torrc located in
24858 the %appdata%\Tor\ of the user who installed the service. Patch
24860 - Add an --ignore-missing-torrc command-line option so that we can
24861 get the "use sensible defaults if the configuration file doesn't
24862 exist" behavior even when specifying a torrc location on the
24864 - When stopping an NT service, wait up to 10 sec for it to actually
24865 stop. (Patch from Matt Edman; resolves bug 295.)
24867 o Directory authority improvements:
24868 - Stop letting hibernating or obsolete servers affect uptime and
24870 - Stop listing hibernating servers in the v1 directory.
24871 - Authorities no longer recommend exits as guards if this would shift
24872 too much load to the exit nodes.
24873 - Authorities now specify server versions in networkstatus. This adds
24874 about 2% to the size of compressed networkstatus docs, and allows
24875 clients to tell which servers support BEGIN_DIR and which don't.
24876 The implementation is forward-compatible with a proposed future
24877 protocol version scheme not tied to Tor versions.
24878 - DirServer configuration lines now have an orport= option so
24879 clients can open encrypted tunnels to the authorities without
24880 having downloaded their descriptors yet. Enabled for moria1,
24881 moria2, tor26, and lefkada now in the default configuration.
24882 - Add a BadDirectory flag to network status docs so that authorities
24883 can (eventually) tell clients about caches they believe to be
24884 broken. Not used yet.
24885 - Allow authorities to list nodes as bad exits in their
24886 approved-routers file by fingerprint or by address. If most
24887 authorities set a BadExit flag for a server, clients don't think
24888 of it as a general-purpose exit. Clients only consider authorities
24889 that advertise themselves as listing bad exits.
24890 - Patch from Steve Hildrey: Generate network status correctly on
24891 non-versioning dirservers.
24892 - Have directory authorities allow larger amounts of drift in uptime
24893 without replacing the server descriptor: previously, a server that
24894 restarted every 30 minutes could have 48 "interesting" descriptors
24896 - Reserve the nickname "Unnamed" for routers that can't pick
24897 a hostname: any router can call itself Unnamed; directory
24898 authorities will never allocate Unnamed to any particular router;
24899 clients won't believe that any router is the canonical Unnamed.
24901 o Directory mirrors and clients:
24902 - Discard any v1 directory info that's over 1 month old (for
24903 directories) or over 1 week old (for running-routers lists).
24904 - Clients track responses with status 503 from dirservers. After a
24905 dirserver has given us a 503, we try not to use it until an hour has
24906 gone by, or until we have no dirservers that haven't given us a 503.
24907 - When we get a 503 from a directory, and we're not a server, we no
24908 longer count the failure against the total number of failures
24909 allowed for the object we're trying to download.
24910 - Prepare for servers to publish descriptors less often: never
24911 discard a descriptor simply for being too old until either it is
24912 recommended by no authorities, or until we get a better one for
24913 the same router. Make caches consider retaining old recommended
24914 routers for even longer.
24915 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
24916 headers for content, so that we can work better in the presence of
24917 caching HTTP proxies.
24918 - Stop fetching descriptors if you're not a dir mirror and you
24919 haven't tried to establish any circuits lately. (This currently
24920 causes some dangerous behavior, because when you start up again
24921 you'll use your ancient server descriptors.)
24923 o Major fixes, crashes:
24924 - Stop crashing when the controller asks us to resetconf more than
24925 one config option at once. (Vidalia 0.0.11 does this.)
24926 - Fix a longstanding obscure crash bug that could occur when we run
24927 out of DNS worker processes, if we're not using eventdns. (Resolves
24929 - Fix an assert that could trigger if a controller quickly set then
24930 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
24931 - Avoid crash when telling controller about stream-status and a
24932 stream is detached.
24933 - Avoid sending junk to controllers or segfaulting when a controller
24934 uses EVENT_NEW_DESC with verbose nicknames.
24935 - Stop triggering asserts if the controller tries to extend hidden
24936 service circuits (reported by mwenge).
24937 - If we start a server with ClientOnly 1, then set ClientOnly to 0
24938 and hup, stop triggering an assert based on an empty onion_key.
24939 - Mask out all signals in sub-threads; only the libevent signal
24940 handler should be processing them. This should prevent some crashes
24941 on some machines using pthreads. (Patch from coderman.)
24942 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
24944 o Major fixes, anonymity/security:
24945 - Automatically avoid picking more than one node from the same
24946 /16 network when constructing a circuit. Add an
24947 "EnforceDistinctSubnets" option to let people disable it if they
24948 want to operate private test networks on a single subnet.
24949 - When generating bandwidth history, round down to the nearest
24950 1k. When storing accounting data, round up to the nearest 1k.
24951 - When we're running as a server, remember when we last rotated onion
24952 keys, so that we will rotate keys once they're a week old even if
24953 we never stay up for a week ourselves.
24954 - If a client asked for a server by name, and there's a named server
24955 in our network-status but we don't have its descriptor yet, we
24956 could return an unnamed server instead.
24957 - Reject (most) attempts to use Tor circuits with length one. (If
24958 many people start using Tor as a one-hop proxy, exit nodes become
24959 a more attractive target for compromise.)
24960 - Just because your DirPort is open doesn't mean people should be
24961 able to remotely teach you about hidden service descriptors. Now
24962 only accept rendezvous posts if you've got HSAuthoritativeDir set.
24963 - Fix a potential race condition in the rpm installer. Found by
24965 - Do not log IPs with TLS failures for incoming TLS
24966 connections. (Fixes bug 382.)
24968 o Major fixes, other:
24969 - If our system clock jumps back in time, don't publish a negative
24970 uptime in the descriptor.
24971 - When we start during an accounting interval before it's time to wake
24972 up, remember to wake up at the correct time. (May fix bug 342.)
24973 - Previously, we would cache up to 16 old networkstatus documents
24974 indefinitely, if they came from nontrusted authorities. Now we
24975 discard them if they are more than 10 days old.
24976 - When we have a state file we cannot parse, tell the user and
24977 move it aside. Now we avoid situations where the user starts
24978 Tor in 1904, Tor writes a state file with that timestamp in it,
24979 the user fixes her clock, and Tor refuses to start.
24980 - Publish a new descriptor after we hup/reload. This is important
24981 if our config has changed such that we'll want to start advertising
24982 our DirPort now, etc.
24983 - If we are using an exit enclave and we can't connect, e.g. because
24984 its webserver is misconfigured to not listen on localhost, then
24985 back off and try connecting from somewhere else before we fail.
24987 o New config options or behaviors:
24988 - When EntryNodes are configured, rebuild the guard list to contain,
24989 in order: the EntryNodes that were guards before; the rest of the
24990 EntryNodes; the nodes that were guards before.
24991 - Do not warn when individual nodes in the configuration's EntryNodes,
24992 ExitNodes, etc are down: warn only when all possible nodes
24993 are down. (Fixes bug 348.)
24994 - Put a lower-bound on MaxAdvertisedBandwidth.
24995 - Start using the state file to store bandwidth accounting data:
24996 the bw_accounting file is now obsolete. We'll keep generating it
24997 for a while for people who are still using 0.1.2.4-alpha.
24998 - Try to batch changes to the state file so that we do as few
24999 disk writes as possible while still storing important things in
25001 - The state file and the bw_accounting file get saved less often when
25002 the AvoidDiskWrites config option is set.
25003 - Make PIDFile work on Windows.
25004 - Add internal descriptions for a bunch of configuration options:
25005 accessible via controller interface and in comments in saved
25007 - Reject *:563 (NNTPS) in the default exit policy. We already reject
25008 NNTP by default, so this seems like a sensible addition.
25009 - Clients now reject hostnames with invalid characters. This should
25010 avoid some inadvertent info leaks. Add an option
25011 AllowNonRFC953Hostnames to disable this behavior, in case somebody
25012 is running a private network with hosts called @, !, and #.
25013 - Check for addresses with invalid characters at the exit as well,
25014 and warn less verbosely when they fail. You can override this by
25015 setting ServerDNSAllowNonRFC953Addresses to 1.
25016 - Remove some options that have been deprecated since at least
25017 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
25018 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
25019 to set log options. Mark PathlenCoinWeight as obsolete.
25020 - Stop accepting certain malformed ports in configured exit policies.
25021 - When the user uses bad syntax in the Log config line, stop
25022 suggesting other bad syntax as a replacement.
25023 - Add new config option "ResolvConf" to let the server operator
25024 choose an alternate resolve.conf file when using eventdns.
25025 - If one of our entry guards is on the ExcludeNodes list, or the
25026 directory authorities don't think it's a good guard, treat it as
25027 if it were unlisted: stop using it as a guard, and throw it off
25028 the guards list if it stays that way for a long time.
25029 - Allow directory authorities to be marked separately as authorities
25030 for the v1 directory protocol, the v2 directory protocol, and
25031 as hidden service directories, to make it easier to retire old
25032 authorities. V1 authorities should set "HSAuthoritativeDir 1"
25033 to continue being hidden service authorities too.
25034 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
25035 - Make TrackExitHosts case-insensitive, and fix the behavior of
25036 ".suffix" TrackExitHosts items to avoid matching in the middle of
25038 - New DirPort behavior: if you have your dirport set, you download
25039 descriptors aggressively like a directory mirror, whether or not
25040 your ORPort is set.
25043 - Create a new file ReleaseNotes which was the old ChangeLog. The
25044 new ChangeLog file now includes the notes for all development
25046 - Add a new address-spec.txt document to describe our special-case
25047 addresses: .exit, .onion, and .noconnnect.
25048 - Fork the v1 directory protocol into its own spec document,
25049 and mark dir-spec.txt as the currently correct (v2) spec.
25051 o Packaging, porting, and contrib
25052 - "tor --verify-config" now exits with -1(255) or 0 depending on
25053 whether the config options are bad or good.
25054 - The Debian package now uses --verify-config when (re)starting,
25055 to distinguish configuration errors from other errors.
25056 - Adapt a patch from goodell to let the contrib/exitlist script
25057 take arguments rather than require direct editing.
25058 - Prevent the contrib/exitlist script from printing the same
25059 result more than once.
25060 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
25061 - In the hidden service example in torrc.sample, stop recommending
25062 esoteric and discouraged hidden service options.
25063 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
25064 values before failing, and always enables eventdns.
25065 - Try to detect Windows correctly when cross-compiling.
25066 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
25067 Try to fix this in configure.in by checking for most functions
25068 before we check for libevent.
25069 - Update RPMs to require libevent 1.2.
25070 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
25071 or later. Log when we are doing this, so we can diagnose it when
25072 it fails. (Also, recommend libevent 1.1b for kqueue and
25073 win32 methods; deprecate libevent 1.0b harder; make libevent
25074 recommendation system saner.)
25075 - Build with recent (1.3+) libevents on platforms that do not
25076 define the nonstandard types "u_int8_t" and friends.
25077 - Remove architecture from OS X builds. The official builds are
25078 now universal binaries.
25079 - Run correctly on OS X platforms with case-sensitive filesystems.
25080 - Correctly set maximum connection limit on Cygwin. (This time
25082 - Start compiling on MinGW on Windows (patches from Mike Chiussi
25084 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
25085 - Finally fix the openssl warnings from newer gccs that believe that
25086 ignoring a return value is okay, but casting a return value and
25087 then ignoring it is a sign of madness.
25088 - On architectures where sizeof(int)>4, still clamp declarable
25089 bandwidth to INT32_MAX.
25091 o Minor features, controller:
25092 - Warn the user when an application uses the obsolete binary v0
25093 control protocol. We're planning to remove support for it during
25094 the next development series, so it's good to give people some
25096 - Add STREAM_BW events to report per-entry-stream bandwidth
25097 use. (Patch from Robert Hogan.)
25098 - Rate-limit SIGNEWNYM signals in response to controllers that
25099 impolitely generate them for every single stream. (Patch from
25100 mwenge; closes bug 394.)
25101 - Add a REMAP status to stream events to note that a stream's
25102 address has changed because of a cached address or a MapAddress
25104 - Make REMAP stream events have a SOURCE (cache or exit), and
25105 make them generated in every case where we get a successful
25106 connected or resolved cell.
25107 - Track reasons for OR connection failure; make these reasons
25108 available via the controller interface. (Patch from Mike Perry.)
25109 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
25110 can learn when clients are sending malformed hostnames to Tor.
25111 - Specify and implement some of the controller status events.
25112 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
25113 - Reimplement GETINFO so that info/names stays in sync with the
25115 - Implement "GETINFO fingerprint".
25116 - Implement "SETEVENTS GUARD" so controllers can get updates on
25117 entry guard status as it changes.
25118 - Make all connections to addresses of the form ".noconnect"
25119 immediately get closed. This lets application/controller combos
25120 successfully test whether they're talking to the same Tor by
25121 watching for STREAM events.
25122 - Add a REASON field to CIRC events; for backward compatibility, this
25123 field is sent only to controllers that have enabled the extended
25124 event format. Also, add additional reason codes to explain why
25125 a given circuit has been destroyed or truncated. (Patches from
25127 - Add a REMOTE_REASON field to extended CIRC events to tell the
25128 controller why a remote OR told us to close a circuit.
25129 - Stream events also now have REASON and REMOTE_REASON fields,
25130 working much like those for circuit events.
25131 - There's now a GETINFO ns/... field so that controllers can ask Tor
25132 about the current status of a router.
25133 - A new event type "NS" to inform a controller when our opinion of
25134 a router's status has changed.
25135 - Add a GETINFO events/names and GETINFO features/names so controllers
25136 can tell which events and features are supported.
25137 - A new CLEARDNSCACHE signal to allow controllers to clear the
25138 client-side DNS cache without expiring circuits.
25139 - Fix CIRC controller events so that controllers can learn the
25140 identity digests of non-Named servers used in circuit paths.
25141 - Let controllers ask for more useful identifiers for servers. Instead
25142 of learning identity digests for un-Named servers and nicknames
25143 for Named servers, the new identifiers include digest, nickname,
25144 and indication of Named status. Off by default; see control-spec.txt
25145 for more information.
25146 - Add a "getinfo address" controller command so it can display Tor's
25147 best guess to the user.
25148 - New controller event to alert the controller when our server
25149 descriptor has changed.
25150 - Give more meaningful errors on controller authentication failure.
25151 - Export the default exit policy via the control port, so controllers
25152 don't need to guess what it is / will be later.
25154 o Minor bugfixes, controller:
25155 - When creating a circuit via the controller, send a 'launched'
25156 event when we're done, so we follow the spec better.
25157 - Correct the control spec to match how the code actually responds
25158 to 'getinfo addr-mappings/*'. Reported by daejees.
25159 - The control spec described a GUARDS event, but the code
25160 implemented a GUARD event. Standardize on GUARD, but let people
25161 ask for GUARDS too. Reported by daejees.
25162 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
25163 clear the corresponding on_circuit variable, and remember later
25164 that we don't need to send a redundant CLOSED event. (Resolves part
25166 - Report events where a resolve succeeded or where we got a socks
25167 protocol error correctly, rather than calling both of them
25169 - Change reported stream target addresses to IP consistently when
25170 we finally get the IP from an exit node.
25171 - Send log messages to the controller even if they happen to be very
25173 - Flush ERR-level controller status events just like we currently
25174 flush ERR-level log events, so that a Tor shutdown doesn't prevent
25175 the controller from learning about current events.
25176 - Report the circuit number correctly in STREAM CLOSED events. Bug
25177 reported by Mike Perry.
25178 - Do not report bizarre values for results of accounting GETINFOs
25179 when the last second's write or read exceeds the allotted bandwidth.
25180 - Report "unrecognized key" rather than an empty string when the
25181 controller tries to fetch a networkstatus that doesn't exist.
25182 - When the controller does a "GETINFO network-status", tell it
25183 about even those routers whose descriptors are very old, and use
25184 long nicknames where appropriate.
25185 - Fix handling of verbose nicknames with ORCONN controller events:
25186 make them show up exactly when requested, rather than exactly when
25188 - Controller signals now work on non-Unix platforms that don't define
25189 SIGUSR1 and SIGUSR2 the way we expect.
25190 - Respond to SIGNAL command before we execute the signal, in case
25191 the signal shuts us down. Suggested by Karsten Loesing.
25192 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
25194 o Minor features, code performance:
25195 - Major performance improvement on inserting descriptors: change
25196 algorithm from O(n^2) to O(n).
25197 - Do not rotate onion key immediately after setting it for the first
25199 - Call router_have_min_dir_info half as often. (This is showing up in
25200 some profiles, but not others.)
25201 - When using GCC, make log_debug never get called at all, and its
25202 arguments never get evaluated, when no debug logs are configured.
25203 (This is showing up in some profiles, but not others.)
25204 - Statistics dumped by -USR2 now include a breakdown of public key
25205 operations, for profiling.
25206 - Make the common memory allocation path faster on machines where
25207 malloc(0) returns a pointer.
25208 - Split circuit_t into origin_circuit_t and or_circuit_t, and
25209 split connection_t into edge, or, dir, control, and base structs.
25210 These will save quite a bit of memory on busy servers, and they'll
25211 also help us track down bugs in the code and bugs in the spec.
25212 - Use OpenSSL's AES implementation on platforms where it's faster.
25213 This could save us as much as 10% CPU usage.
25215 o Minor features, descriptors and descriptor handling:
25216 - Avoid duplicate entries on MyFamily line in server descriptor.
25217 - When Tor receives a router descriptor that it asked for, but
25218 no longer wants (because it has received fresh networkstatuses
25219 in the meantime), do not warn the user. Cache the descriptor if
25220 we're a cache; drop it if we aren't.
25221 - Servers no longer ever list themselves in their "family" line,
25222 even if configured to do so. This makes it easier to configure
25223 family lists conveniently.
25225 o Minor fixes, confusing/misleading log messages:
25226 - Display correct results when reporting which versions are
25227 recommended, and how recommended they are. (Resolves bug 383.)
25228 - Inform the server operator when we decide not to advertise a
25229 DirPort due to AccountingMax enabled or a low BandwidthRate.
25230 - Only include function names in log messages for info/debug messages.
25231 For notice/warn/err, the content of the message should be clear on
25232 its own, and printing the function name only confuses users.
25233 - Remove even more protocol-related warnings from Tor server logs,
25234 such as bad TLS handshakes and malformed begin cells.
25235 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
25236 when the IP address is mapped through MapAddress to a hostname.
25237 - Fix misleading log messages: an entry guard that is "unlisted",
25238 as well as not known to be "down" (because we've never heard
25239 of it), is not therefore "up".
25241 o Minor fixes, old/obsolete behavior:
25242 - Start assuming we can use a create_fast cell if we don't know
25243 what version a router is running.
25244 - We no longer look for identity and onion keys in "identity.key" and
25245 "onion.key" -- these were replaced by secret_id_key and
25246 secret_onion_key in 0.0.8pre1.
25247 - We no longer require unrecognized directory entries to be
25249 - Drop compatibility with obsolete Tors that permit create cells
25250 to have the wrong circ_id_type.
25251 - Remove code to special-case "-cvs" ending, since it has not
25252 actually mattered since 0.0.9.
25253 - Don't re-write the fingerprint file every restart, unless it has
25256 o Minor fixes, misc client-side behavior:
25257 - Always remove expired routers and networkstatus docs before checking
25258 whether we have enough information to build circuits. (Fixes
25260 - When computing clock skew from directory HTTP headers, consider what
25261 time it was when we finished asking for the directory, not what
25263 - Make our socks5 handling more robust to broken socks clients:
25264 throw out everything waiting on the buffer in between socks
25265 handshake phases, since they can't possibly (so the theory
25266 goes) have predicted what we plan to respond to them.
25267 - Expire socks connections if they spend too long waiting for the
25268 handshake to finish. Previously we would let them sit around for
25269 days, if the connecting application didn't close them either.
25270 - And if the socks handshake hasn't started, don't send a
25271 "DNS resolve socks failed" handshake reply; just close it.
25272 - If the user asks to use invalid exit nodes, be willing to use
25274 - Track unreachable entry guards correctly: don't conflate
25275 'unreachable by us right now' with 'listed as down by the directory
25276 authorities'. With the old code, if a guard was unreachable by us
25277 but listed as running, it would clog our guard list forever.
25278 - Behave correctly in case we ever have a network with more than
25279 2GB/s total advertised capacity.
25280 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
25281 - Fix a memory leak when we ask for "all" networkstatuses and we
25282 get one we don't recognize.
25285 Changes in version 0.1.1.26 - 2006-12-14
25286 o Security bugfixes:
25287 - Stop sending the HttpProxyAuthenticator string to directory
25288 servers when directory connections are tunnelled through Tor.
25289 - Clients no longer store bandwidth history in the state file.
25290 - Do not log introduction points for hidden services if SafeLogging
25294 - Fix an assert failure when a directory authority sets
25295 AuthDirRejectUnlisted and then receives a descriptor from an
25296 unlisted router (reported by seeess).
25299 Changes in version 0.1.1.25 - 2006-11-04
25301 - When a client asks us to resolve (rather than connect to)
25302 an address, and we have a cached answer, give them the cached
25303 answer. Previously, we would give them no answer at all.
25304 - We were building exactly the wrong circuits when we predict
25305 hidden service requirements, meaning Tor would have to build all
25306 its circuits on demand.
25307 - If none of our live entry guards have a high uptime, but we
25308 require a guard with a high uptime, try adding a new guard before
25309 we give up on the requirement. This patch should make long-lived
25310 connections more stable on average.
25311 - When testing reachability of our DirPort, don't launch new
25312 tests when there's already one in progress -- unreachable
25313 servers were stacking up dozens of testing streams.
25315 o Security bugfixes:
25316 - When the user sends a NEWNYM signal, clear the client-side DNS
25317 cache too. Otherwise we continue to act on previous information.
25320 - Avoid a memory corruption bug when creating a hash table for
25322 - Avoid possibility of controller-triggered crash when misusing
25323 certain commands from a v0 controller on platforms that do not
25324 handle printf("%s",NULL) gracefully.
25325 - Avoid infinite loop on unexpected controller input.
25326 - Don't log spurious warnings when we see a circuit close reason we
25327 don't recognize; it's probably just from a newer version of Tor.
25328 - Add Vidalia to the OS X uninstaller script, so when we uninstall
25329 Tor/Privoxy we also uninstall Vidalia.
25332 Changes in version 0.1.1.24 - 2006-09-29
25334 - Allow really slow clients to not hang up five minutes into their
25335 directory downloads (suggested by Adam J. Richter).
25336 - Fix major performance regression from 0.1.0.x: instead of checking
25337 whether we have enough directory information every time we want to
25338 do something, only check when the directory information has changed.
25339 This should improve client CPU usage by 25-50%.
25340 - Don't crash if, after a server has been running for a while,
25341 it can't resolve its hostname.
25342 - When a client asks us to resolve (not connect to) an address,
25343 and we have a cached answer, give them the cached answer.
25344 Previously, we would give them no answer at all.
25347 - Allow Tor to start when RunAsDaemon is set but no logs are set.
25348 - Don't crash when the controller receives a third argument to an
25349 "extendcircuit" request.
25350 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
25351 response; fix error code when "getinfo dir/status/" fails.
25352 - Fix configure.in to not produce broken configure files with
25353 more recent versions of autoconf. Thanks to Clint for his auto*
25355 - Fix security bug on NetBSD that could allow someone to force
25356 uninitialized RAM to be sent to a server's DNS resolver. This
25357 only affects NetBSD and other platforms that do not bounds-check
25359 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
25360 methods: these are known to be buggy.
25361 - If we're a directory mirror and we ask for "all" network status
25362 documents, we would discard status documents from authorities
25363 we don't recognize.
25366 Changes in version 0.1.1.23 - 2006-07-30
25368 - Fast Tor servers, especially exit nodes, were triggering asserts
25369 due to a bug in handling the list of pending DNS resolves. Some
25370 bugs still remain here; we're hunting them.
25371 - Entry guards could crash clients by sending unexpected input.
25372 - More fixes on reachability testing: if you find yourself reachable,
25373 then don't ever make any client requests (so you stop predicting
25374 circuits), then hup or have your clock jump, then later your IP
25375 changes, you won't think circuits are working, so you won't try to
25376 test reachability, so you won't publish.
25379 - Avoid a crash if the controller does a resetconf firewallports
25380 and then a setconf fascistfirewall=1.
25381 - Avoid an integer underflow when the dir authority decides whether
25382 a router is stable: we might wrongly label it stable, and compute
25383 a slightly wrong median stability, when a descriptor is published
25385 - Fix a place where we might trigger an assert if we can't build our
25386 own server descriptor yet.
25389 Changes in version 0.1.1.22 - 2006-07-05
25391 - Fix a big bug that was causing servers to not find themselves
25392 reachable if they changed IP addresses. Since only 0.1.1.22+
25393 servers can do reachability testing correctly, now we automatically
25394 make sure to test via one of these.
25395 - Fix to allow clients and mirrors to learn directory info from
25396 descriptor downloads that get cut off partway through.
25397 - Directory authorities had a bug in deciding if a newly published
25398 descriptor was novel enough to make everybody want a copy -- a few
25399 servers seem to be publishing new descriptors many times a minute.
25401 - Fix a rare bug that was causing some servers to complain about
25402 "closing wedged cpuworkers" and skip some circuit create requests.
25403 - Make the Exit flag in directory status documents actually work.
25406 Changes in version 0.1.1.21 - 2006-06-10
25407 o Crash and assert fixes from 0.1.1.20:
25408 - Fix a rare crash on Tor servers that have enabled hibernation.
25409 - Fix a seg fault on startup for Tor networks that use only one
25410 directory authority.
25411 - Fix an assert from a race condition that occurs on Tor servers
25412 while exiting, where various threads are trying to log that they're
25413 exiting, and delete the logs, at the same time.
25414 - Make our unit tests pass again on certain obscure platforms.
25417 - Add support for building SUSE RPM packages.
25418 - Speed up initial bootstrapping for clients: if we are making our
25419 first ever connection to any entry guard, then don't mark it down
25421 - When only one Tor server in the network is labelled as a guard,
25422 and we've already picked him, we would cycle endlessly picking him
25423 again, being unhappy about it, etc. Now we specifically exclude
25424 current guards when picking a new guard.
25425 - Servers send create cells more reliably after the TLS connection
25426 is established: we were sometimes forgetting to send half of them
25427 when we had more than one pending.
25428 - If we get a create cell that asks us to extend somewhere, but the
25429 Tor server there doesn't match the expected digest, we now send
25430 a destroy cell back, rather than silently doing nothing.
25431 - Make options->RedirectExit work again.
25432 - Make cookie authentication for the controller work again.
25433 - Stop being picky about unusual characters in the arguments to
25434 mapaddress. It's none of our business.
25435 - Add a new config option "TestVia" that lets you specify preferred
25436 middle hops to use for test circuits. Perhaps this will let me
25437 debug the reachability problems better.
25439 o Log / documentation fixes:
25440 - If we're a server and some peer has a broken TLS certificate, don't
25441 log about it unless ProtocolWarnings is set, i.e., we want to hear
25442 about protocol violations by others.
25443 - Fix spelling of VirtualAddrNetwork in man page.
25444 - Add a better explanation at the top of the autogenerated torrc file
25445 about what happened to our old torrc.
25448 Changes in version 0.1.1.20 - 2006-05-23
25449 o Crash and assert fixes from 0.1.0.17:
25450 - Fix assert bug in close_logs() on exit: when we close and delete
25451 logs, remove them all from the global "logfiles" list.
25452 - Fix an assert error when we're out of space in the connection_list
25453 and we try to post a hidden service descriptor (reported by Peter
25455 - Fix a rare assert error when we've tried all intro points for
25456 a hidden service and we try fetching the service descriptor again:
25457 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
25458 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
25459 out and refuse the setconf if it would fail.
25460 - If you specify a relative torrc path and you set RunAsDaemon in
25461 your torrc, then it chdir()'s to the new directory. If you then
25462 HUP, it tries to load the new torrc location, fails, and exits.
25463 The fix: no longer allow a relative path to torrc when using -f.
25464 - Check for integer overflows in more places, when adding elements
25465 to smartlists. This could possibly prevent a buffer overflow
25466 on malicious huge inputs.
25468 o Security fixes, major:
25469 - When we're printing strings from the network, don't try to print
25470 non-printable characters. Now we're safer against shell escape
25471 sequence exploits, and also against attacks to fool users into
25472 misreading their logs.
25473 - Implement entry guards: automatically choose a handful of entry
25474 nodes and stick with them for all circuits. Only pick new guards
25475 when the ones you have are unsuitable, and if the old guards
25476 become suitable again, switch back. This will increase security
25477 dramatically against certain end-point attacks. The EntryNodes
25478 config option now provides some hints about which entry guards you
25479 want to use most; and StrictEntryNodes means to only use those.
25480 Fixes CVE-2006-0414.
25481 - Implement exit enclaves: if we know an IP address for the
25482 destination, and there's a running Tor server at that address
25483 which allows exit to the destination, then extend the circuit to
25484 that exit first. This provides end-to-end encryption and end-to-end
25485 authentication. Also, if the user wants a .exit address or enclave,
25486 use 4 hops rather than 3, and cannibalize a general circ for it
25488 - Obey our firewall options more faithfully:
25489 . If we can't get to a dirserver directly, try going via Tor.
25490 . Don't ever try to connect (as a client) to a place our
25491 firewall options forbid.
25492 . If we specify a proxy and also firewall options, obey the
25493 firewall options even when we're using the proxy: some proxies
25494 can only proxy to certain destinations.
25495 - Make clients regenerate their keys when their IP address changes.
25496 - For the OS X package's modified privoxy config file, comment
25497 out the "logfile" line so we don't log everything passed
25499 - Our TLS handshakes were generating a single public/private
25500 keypair for the TLS context, rather than making a new one for
25501 each new connection. Oops. (But we were still rotating them
25502 periodically, so it's not so bad.)
25503 - When we were cannibalizing a circuit with a particular exit
25504 node in mind, we weren't checking to see if that exit node was
25505 already present earlier in the circuit. Now we are.
25506 - Require server descriptors to list IPv4 addresses -- hostnames
25507 are no longer allowed. This also fixes potential vulnerabilities
25508 to servers providing hostnames as their address and then
25509 preferentially resolving them so they can partition users.
25510 - Our logic to decide if the OR we connected to was the right guy
25511 was brittle and maybe open to a mitm for invalid routers.
25513 o Security fixes, minor:
25514 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
25515 Ian Goldberg can prove things about our handshake protocol more
25517 - Make directory authorities generate a separate "guard" flag to
25518 mean "would make a good entry guard". Clients now honor the
25519 is_guard flag rather than looking at is_fast or is_stable.
25520 - Try to list MyFamily elements by key, not by nickname, and warn
25521 if we've not heard of a server.
25522 - Start using RAND_bytes rather than RAND_pseudo_bytes from
25523 OpenSSL. Also, reseed our entropy every hour, not just at
25524 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
25525 - Refuse server descriptors where the fingerprint line doesn't match
25526 the included identity key. Tor doesn't care, but other apps (and
25527 humans) might actually be trusting the fingerprint line.
25528 - We used to kill the circuit when we receive a relay command we
25529 don't recognize. Now we just drop that cell.
25530 - Fix a bug found by Lasse Overlier: when we were making internal
25531 circuits (intended to be cannibalized later for rendezvous and
25532 introduction circuits), we were picking them so that they had
25533 useful exit nodes. There was no need for this, and it actually
25534 aids some statistical attacks.
25535 - Start treating internal circuits and exit circuits separately.
25536 It's important to keep them separate because internal circuits
25537 have their last hops picked like middle hops, rather than like
25538 exit hops. So exiting on them will break the user's expectations.
25539 - Fix a possible way to DoS dirservers.
25540 - When the client asked for a rendezvous port that the hidden
25541 service didn't want to provide, we were sending an IP address
25542 back along with the end cell. Fortunately, it was zero. But stop
25545 o Packaging improvements:
25546 - Implement --with-libevent-dir option to ./configure. Improve
25547 search techniques to find libevent, and use those for openssl too.
25548 - Fix a couple of bugs in OpenSSL detection. Deal better when
25549 there are multiple SSLs installed with different versions.
25550 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
25551 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
25553 - Make unit tests (and other invocations that aren't the real Tor)
25554 run without launching listeners, creating subdirectories, and so on.
25555 - The OS X installer was adding a symlink for tor_resolve but
25556 the binary was called tor-resolve (reported by Thomas Hardly).
25557 - Now we can target arch and OS in rpm builds (contributed by
25558 Phobos). Also make the resulting dist-rpm filename match the
25560 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
25561 if you log to syslog and want something other than LOG_DAEMON.
25562 - Fix the torify (tsocks) config file to not use Tor for localhost
25564 - Start shipping socks-extensions.txt, tor-doc-unix.html,
25565 tor-doc-server.html, and stylesheet.css in the tarball.
25566 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
25567 They are useless now.
25568 - Add Peter Palfrader's contributed check-tor script. It lets you
25569 easily check whether a given server (referenced by nickname)
25570 is reachable by you.
25571 - Add BSD-style contributed startup script "rc.subr" from Peter
25574 o Directory improvements -- new directory protocol:
25575 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
25576 - Authorities and caches publish individual descriptors (by
25577 digest, by fingerprint, by "all", and by "tell me yours").
25578 - Clients don't download or use the old directory anymore. Now they
25579 download network-statuses from the directory authorities, and
25580 fetch individual server descriptors as needed from mirrors.
25581 - Clients don't download descriptors of non-running servers.
25582 - Download descriptors by digest, not by fingerprint. Caches try to
25583 download all listed digests from authorities; clients try to
25584 download "best" digests from caches. This avoids partitioning
25585 and isolating attacks better.
25586 - Only upload a new server descriptor when options change, 18
25587 hours have passed, uptime is reset, or bandwidth changes a lot.
25588 - Directory authorities silently throw away new descriptors that
25589 haven't changed much if the timestamps are similar. We do this to
25590 tolerate older Tor servers that upload a new descriptor every 15
25591 minutes. (It seemed like a good idea at the time.)
25592 - Clients choose directory servers from the network status lists,
25593 not from their internal list of router descriptors. Now they can
25594 go to caches directly rather than needing to go to authorities
25595 to bootstrap the first set of descriptors.
25596 - When picking a random directory, prefer non-authorities if any
25598 - Add a new flag to network-status indicating whether the server
25599 can answer v2 directory requests too.
25600 - Directory mirrors now cache up to 16 unrecognized network-status
25601 docs, so new directory authorities will be cached too.
25602 - Stop parsing, storing, or using running-routers output (but
25603 mirrors still cache and serve it).
25604 - Clients consider a threshold of "versioning" directory authorities
25605 before deciding whether to warn the user that he's obsolete.
25606 - Authorities publish separate sorted lists of recommended versions
25607 for clients and for servers.
25608 - Change DirServers config line to note which dirs are v1 authorities.
25609 - Put nicknames on the DirServer line, so we can refer to them
25610 without requiring all our users to memorize their IP addresses.
25611 - Remove option when getting directory cache to see whether they
25612 support running-routers; they all do now. Replace it with one
25613 to see whether caches support v2 stuff.
25614 - Stop listing down or invalid nodes in the v1 directory. This
25615 reduces its bulk by about 1/3, and reduces load on mirrors.
25616 - Mirrors no longer cache the v1 directory as often.
25617 - If we as a directory mirror don't know of any v1 directory
25618 authorities, then don't try to cache any v1 directories.
25620 o Other directory improvements:
25621 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
25622 fifth authoritative directory servers.
25623 - Directory authorities no longer require an open connection from
25624 a server to consider him "reachable". We need this change because
25625 when we add new directory authorities, old servers won't know not
25626 to hang up on them.
25627 - Dir authorities now do their own external reachability testing
25628 of each server, and only list as running the ones they found to
25629 be reachable. We also send back warnings to the server's logs if
25630 it uploads a descriptor that we already believe is unreachable.
25631 - Spread the directory authorities' reachability testing over the
25632 entire testing interval, so we don't try to do 500 TLS's at once
25634 - Make the "stable" router flag in network-status be the median of
25635 the uptimes of running valid servers, and make clients pay
25636 attention to the network-status flags. Thus the cutoff adapts
25637 to the stability of the network as a whole, making IRC, IM, etc
25638 connections more reliable.
25639 - Make the v2 dir's "Fast" flag based on relative capacity, just
25640 like "Stable" is based on median uptime. Name everything in the
25641 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
25642 - Retry directory requests if we fail to get an answer we like
25643 from a given dirserver (we were retrying before, but only if
25644 we fail to connect).
25645 - Return a robots.txt on our dirport to discourage google indexing.
25647 o Controller protocol improvements:
25648 - Revised controller protocol (version 1) that uses ascii rather
25649 than binary: tor/doc/control-spec.txt. Add supporting libraries
25650 in python and java and c# so you can use the controller from your
25651 applications without caring how our protocol works.
25652 - Allow the DEBUG controller event to work again. Mark certain log
25653 entries as "don't tell this to controllers", so we avoid cycles.
25654 - New controller function "getinfo accounting", to ask how
25655 many bytes we've used in this time period.
25656 - Add a "resetconf" command so you can set config options like
25657 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
25658 a config option in the torrc with no value, then it clears it
25659 entirely (rather than setting it to its default).
25660 - Add a "getinfo config-file" to tell us where torrc is. Also
25661 expose guard nodes, config options/names.
25662 - Add a "quit" command (when when using the controller manually).
25663 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
25664 stop using any currently-dirty circuits for new streams, so we
25665 don't link new actions to old actions. This also occurs on HUP
25666 or "signal reload".
25667 - If we would close a stream early (e.g. it asks for a .exit that
25668 we know would refuse it) but the LeaveStreamsUnattached config
25669 option is set by the controller, then don't close it.
25670 - Add a new controller event type "authdir_newdescs" that allows
25671 controllers to get all server descriptors that were uploaded to
25672 a router in its role as directory authority.
25673 - New controller option "getinfo desc/all-recent" to fetch the
25674 latest server descriptor for every router that Tor knows about.
25675 - Fix the controller's "attachstream 0" command to treat conn like
25676 it just connected, doing address remapping, handling .exit and
25677 .onion idioms, and so on. Now we're more uniform in making sure
25678 that the controller hears about new and closing connections.
25679 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
25680 the controller. Also, rotate dns and cpu workers if the controller
25681 changes options that will affect them; and initialize the dns
25682 worker cache tree whether or not we start out as a server.
25683 - Add a new circuit purpose 'controller' to let the controller ask
25684 for a circuit that Tor won't try to use. Extend the "extendcircuit"
25685 controller command to let you specify the purpose if you're starting
25686 a new circuit. Add a new "setcircuitpurpose" controller command to
25687 let you change a circuit's purpose after it's been created.
25688 - Let the controller ask for "getinfo dir/server/foo" so it can ask
25689 directly rather than connecting to the dir port. "getinfo
25690 dir/status/foo" also works, but currently only if your DirPort
25692 - Let the controller tell us about certain router descriptors
25693 that it doesn't want Tor to use in circuits. Implement
25694 "setrouterpurpose" and modify "+postdescriptor" to do this.
25695 - If the controller's *setconf commands fail, collect an error
25696 message in a string and hand it back to the controller -- don't
25697 just tell them to go read their logs.
25699 o Scalability, resource management, and performance:
25700 - Fix a major load balance bug: we were round-robin reading in 16 KB
25701 chunks, and servers with bandwidthrate of 20 KB, while downloading
25702 a 600 KB directory, would starve their other connections. Now we
25703 try to be a bit more fair.
25704 - Be more conservative about whether to advertise our DirPort.
25705 The main change is to not advertise if we're running at capacity
25706 and either a) we could hibernate ever or b) our capacity is low
25707 and we're using a default DirPort.
25708 - We weren't cannibalizing circuits correctly for
25709 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
25710 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
25711 build those from scratch. This should make hidden services faster.
25712 - Predict required circuits better, with an eye toward making hidden
25713 services faster on the service end.
25714 - Compress exit policies even more: look for duplicate lines and
25716 - Generate 18.0.0.0/8 address policy format in descs when we can;
25717 warn when the mask is not reducible to a bit-prefix.
25718 - There used to be two ways to specify your listening ports in a
25719 server descriptor: on the "router" line and with a separate "ports"
25720 line. Remove support for the "ports" line.
25721 - Reduce memory requirements in our structs by changing the order
25722 of fields. Replace balanced trees with hash tables. Inline
25723 bottleneck smartlist functions. Add a "Map from digest to void*"
25724 abstraction so we can do less hex encoding/decoding, and use it
25725 in router_get_by_digest(). Many other CPU and memory improvements.
25726 - Allow tor_gzip_uncompress to extract as much as possible from
25727 truncated compressed data. Try to extract as many
25728 descriptors as possible from truncated http responses (when
25729 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
25730 - Make circ->onionskin a pointer, not a static array. moria2 was using
25731 125000 circuit_t's after it had been up for a few weeks, which
25732 translates to 20+ megs of wasted space.
25733 - The private half of our EDH handshake keys are now chosen out
25734 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
25735 - Stop doing the complex voodoo overkill checking for insecure
25736 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
25737 - Do round-robin writes for TLS of at most 16 kB per write. This
25738 might be more fair on loaded Tor servers.
25739 - Do not use unaligned memory access on alpha, mips, or mipsel.
25740 It *works*, but is very slow, so we treat them as if it doesn't.
25742 o Other bugfixes and improvements:
25743 - Start storing useful information to $DATADIR/state, so we can
25744 remember things across invocations of Tor. Retain unrecognized
25745 lines so we can be forward-compatible, and write a TorVersion line
25746 so we can be backward-compatible.
25747 - If ORPort is set, Address is not explicitly set, and our hostname
25748 resolves to a private IP address, try to use an interface address
25749 if it has a public address. Now Windows machines that think of
25750 themselves as localhost can guess their address.
25751 - Regenerate our local descriptor if it's dirty and we try to use
25752 it locally (e.g. if it changes during reachability detection).
25753 This was causing some Tor servers to keep publishing the same
25754 initial descriptor forever.
25755 - Tor servers with dynamic IP addresses were needing to wait 18
25756 hours before they could start doing reachability testing using
25757 the new IP address and ports. This is because they were using
25758 the internal descriptor to learn what to test, yet they were only
25759 rebuilding the descriptor once they decided they were reachable.
25760 - It turns out we couldn't bootstrap a network since we added
25761 reachability detection in 0.1.0.1-rc. Good thing the Tor network
25762 has never gone down. Add an AssumeReachable config option to let
25763 servers and authorities bootstrap. When we're trying to build a
25764 high-uptime or high-bandwidth circuit but there aren't enough
25765 suitable servers, try being less picky rather than simply failing.
25766 - Newly bootstrapped Tor networks couldn't establish hidden service
25767 circuits until they had nodes with high uptime. Be more tolerant.
25768 - Really busy servers were keeping enough circuits open on stable
25769 connections that they were wrapping around the circuit_id
25770 space. (It's only two bytes.) This exposed a bug where we would
25771 feel free to reuse a circuit_id even if it still exists but has
25772 been marked for close. Try to fix this bug. Some bug remains.
25773 - When we fail to bind or listen on an incoming or outgoing
25774 socket, we now close it before refusing, rather than just
25775 leaking it. (Thanks to Peter Palfrader for finding.)
25776 - Fix a file descriptor leak in start_daemon().
25777 - On Windows, you can't always reopen a port right after you've
25778 closed it. So change retry_listeners() to only close and re-open
25779 ports that have changed.
25780 - Workaround a problem with some http proxies that refuse GET
25781 requests that specify "Content-Length: 0". Reported by Adrian.
25782 - Recover better from TCP connections to Tor servers that are
25783 broken but don't tell you (it happens!); and rotate TLS
25784 connections once a week.
25785 - Fix a scary-looking but apparently harmless bug where circuits
25786 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
25787 servers, and never switch to state CIRCUIT_STATE_OPEN.
25788 - Check for even more Windows version flags when writing the platform
25789 string in server descriptors, and note any we don't recognize.
25790 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
25791 get a better idea of why their circuits failed. Not used yet.
25792 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
25793 We don't use them yet, but maybe one day our DNS resolver will be
25794 able to discover them.
25795 - Let people type "tor --install" as well as "tor -install" when they
25796 want to make it an NT service.
25797 - Looks like we were never delivering deflated (i.e. compressed)
25798 running-routers lists, even when asked. Oops.
25799 - We were leaking some memory every time the client changed IPs.
25800 - Clean up more of the OpenSSL memory when exiting, so we can detect
25801 memory leaks better.
25802 - Never call free() on tor_malloc()d memory. This will help us
25803 use dmalloc to detect memory leaks.
25804 - Some Tor servers process billions of cells per day. These
25805 statistics are now uint64_t's.
25806 - Check [X-]Forwarded-For headers in HTTP requests when generating
25807 log messages. This lets people run dirservers (and caches) behind
25808 Apache but still know which IP addresses are causing warnings.
25809 - Fix minor integer overflow in calculating when we expect to use up
25810 our bandwidth allocation before hibernating.
25811 - Lower the minimum required number of file descriptors to 1000,
25812 so we can have some overhead for Valgrind on Linux, where the
25813 default ulimit -n is 1024.
25814 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
25815 and its existence is confusing some users.
25817 o Config option fixes:
25818 - Add a new config option ExitPolicyRejectPrivate which defaults
25819 to on. Now all exit policies will begin with rejecting private
25820 addresses, unless the server operator explicitly turns it off.
25821 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
25822 - Add new ReachableORAddresses and ReachableDirAddresses options
25823 that understand address policies. FascistFirewall is now a synonym
25824 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
25825 - Start calling it FooListenAddress rather than FooBindAddress,
25826 since few of our users know what it means to bind an address
25828 - If the user gave Tor an odd number of command-line arguments,
25829 we were silently ignoring the last one. Now we complain and fail.
25830 This wins the oldest-bug prize -- this bug has been present since
25831 November 2002, as released in Tor 0.0.0.
25832 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
25833 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
25834 it would silently ignore the 6668.
25835 - If we get a linelist or linelist_s config option from the torrc,
25836 e.g. ExitPolicy, and it has no value, warn and skip rather than
25837 silently resetting it to its default.
25838 - Setconf was appending items to linelists, not clearing them.
25839 - Add MyFamily to torrc.sample in the server section, so operators
25840 will be more likely to learn that it exists.
25841 - Make ContactInfo mandatory for authoritative directory servers.
25842 - MaxConn has been obsolete for a while now. Document the ConnLimit
25843 config option, which is a *minimum* number of file descriptors
25844 that must be available else Tor refuses to start.
25845 - Get rid of IgnoreVersion undocumented config option, and make us
25846 only warn, never exit, when we're running an obsolete version.
25847 - Make MonthlyAccountingStart config option truly obsolete now.
25848 - Correct the man page entry on TrackHostExitsExpire.
25849 - Let directory authorities start even if they don't specify an
25850 Address config option.
25851 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
25852 reflect the updated flags in our v2 dir protocol.
25854 o Config option features:
25855 - Add a new config option FastFirstHopPK (on by default) so clients
25856 do a trivial crypto handshake for their first hop, since TLS has
25857 already taken care of confidentiality and authentication.
25858 - Let the user set ControlListenAddress in the torrc. This can be
25859 dangerous, but there are some cases (like a secured LAN) where it
25861 - New config options to help controllers: FetchServerDescriptors
25862 and FetchHidServDescriptors for whether to fetch server
25863 info and hidserv info or let the controller do it, and
25864 PublishServerDescriptor and PublishHidServDescriptors.
25865 - Also let the controller set the __AllDirActionsPrivate config
25866 option if you want all directory fetches/publishes to happen via
25867 Tor (it assumes your controller bootstraps your circuits).
25868 - Add "HardwareAccel" config option: support for crypto hardware
25869 accelerators via OpenSSL. Off by default, until we find somebody
25870 smart who can test it for us. (It appears to produce seg faults
25871 in at least some cases.)
25872 - New config option "AuthDirRejectUnlisted" for directory authorities
25873 as a panic button: if we get flooded with unusable servers we can
25874 revert to only listing servers in the approved-routers file.
25875 - Directory authorities can now reject/invalidate by key and IP,
25876 with the config options "AuthDirInvalid" and "AuthDirReject", or
25877 by marking a fingerprint as "!reject" or "!invalid" (as its
25878 nickname) in the approved-routers file. This is useful since
25879 currently we automatically list servers as running and usable
25880 even if we know they're jerks.
25881 - Add a new config option TestSocks so people can see whether their
25882 applications are using socks4, socks4a, socks5-with-ip, or
25883 socks5-with-fqdn. This way they don't have to keep mucking
25884 with tcpdump and wondering if something got cached somewhere.
25885 - Add "private:*" as an alias in configuration for policies. Now
25886 you can simplify your exit policy rather than needing to list
25887 every single internal or nonroutable network space.
25888 - Accept "private:*" in routerdesc exit policies; not generated yet
25889 because older Tors do not understand it.
25890 - Add configuration option "V1AuthoritativeDirectory 1" which
25891 moria1, moria2, and tor26 have set.
25892 - Implement an option, VirtualAddrMask, to set which addresses
25893 get handed out in response to mapaddress requests. This works
25894 around a bug in tsocks where 127.0.0.0/8 is never socksified.
25895 - Add a new config option FetchUselessDescriptors, off by default,
25896 for when you plan to run "exitlist" on your client and you want
25897 to know about even the non-running descriptors.
25898 - SocksTimeout: How long do we let a socks connection wait
25899 unattached before we fail it?
25900 - CircuitBuildTimeout: Cull non-open circuits that were born
25901 at least this many seconds ago.
25902 - CircuitIdleTimeout: Cull open clean circuits that were born
25903 at least this many seconds ago.
25904 - New config option SafeSocks to reject all application connections
25905 using unsafe socks protocols. Defaults to off.
25907 o Improved and clearer log messages:
25908 - Reduce clutter in server logs. We're going to try to make
25909 them actually usable now. New config option ProtocolWarnings that
25910 lets you hear about how _other Tors_ are breaking the protocol. Off
25912 - Divide log messages into logging domains. Once we put some sort
25913 of interface on this, it will let people looking at more verbose
25914 log levels specify the topics they want to hear more about.
25915 - Log server fingerprint on startup, so new server operators don't
25916 have to go hunting around their filesystem for it.
25917 - Provide dire warnings to any users who set DirServer manually;
25918 move it out of torrc.sample and into torrc.complete.
25919 - Make the log message less scary when all the dirservers are
25920 temporarily unreachable.
25921 - When tor_socketpair() fails in Windows, give a reasonable
25922 Windows-style errno back.
25923 - Improve tor_gettimeofday() granularity on windows.
25924 - We were printing the number of idle dns workers incorrectly when
25926 - Handle duplicate lines in approved-routers files without warning.
25927 - We were whining about using socks4 or socks5-with-local-lookup
25928 even when it's an IP address in the "virtual" range we designed
25929 exactly for this case.
25930 - Check for named servers when looking them up by nickname;
25931 warn when we're calling a non-named server by its nickname;
25932 don't warn twice about the same name.
25933 - Downgrade the dirserver log messages when whining about
25935 - Correct "your server is reachable" log entries to indicate that
25936 it was self-testing that told us so.
25937 - If we're trying to be a Tor server and running Windows 95/98/ME
25938 as a server, explain that we'll likely crash.
25939 - Provide a more useful warn message when our onion queue gets full:
25940 the CPU is too slow or the exit policy is too liberal.
25941 - Don't warn when we receive a 503 from a dirserver/cache -- this
25942 will pave the way for them being able to refuse if they're busy.
25943 - When we fail to bind a listener, try to provide a more useful
25944 log message: e.g., "Is Tor already running?"
25945 - Only start testing reachability once we've established a
25946 circuit. This will make startup on dir authorities less noisy.
25947 - Don't try to upload hidden service descriptors until we have
25948 established a circuit.
25949 - Tor didn't warn when it failed to open a log file.
25950 - Warn when listening on a public address for socks. We suspect a
25951 lot of people are setting themselves up as open socks proxies,
25952 and they have no idea that jerks on the Internet are using them,
25953 since they simply proxy the traffic into the Tor network.
25954 - Give a useful message when people run Tor as the wrong user,
25955 rather than telling them to start chowning random directories.
25956 - Fix a harmless bug that was causing Tor servers to log
25957 "Got an end because of misc error, but we're not an AP. Closing."
25958 - Fix wrong log message when you add a "HiddenServiceNodes" config
25959 line without any HiddenServiceDir line (reported by Chris Thomas).
25960 - Directory authorities now stop whining so loudly about bad
25961 descriptors that they fetch from other dirservers. So when there's
25962 a log complaint, it's for sure from a freshly uploaded descriptor.
25963 - When logging via syslog, include the pid whenever we provide
25964 a log entry. Suggested by Todd Fries.
25965 - When we're shutting down and we do something like try to post a
25966 server descriptor or rendezvous descriptor, don't complain that
25967 we seem to be unreachable. Of course we are, we're shutting down.
25968 - Change log line for unreachability to explicitly suggest /etc/hosts
25969 as the culprit. Also make it clearer what IP address and ports we're
25970 testing for reachability.
25971 - Put quotes around user-supplied strings when logging so users are
25972 more likely to realize if they add bad characters (like quotes)
25974 - NT service patch from Matt Edman to improve error messages on Win32.
25977 Changes in version 0.1.0.17 - 2006-02-17
25978 o Crash bugfixes on 0.1.0.x:
25979 - When servers with a non-zero DirPort came out of hibernation,
25980 sometimes they would trigger an assert.
25982 o Other important bugfixes:
25983 - On platforms that don't have getrlimit (like Windows), we were
25984 artificially constraining ourselves to a max of 1024
25985 connections. Now just assume that we can handle as many as 15000
25986 connections. Hopefully this won't cause other problems.
25988 o Backported features:
25989 - When we're a server, a client asks for an old-style directory,
25990 and our write bucket is empty, don't give it to him. This way
25991 small servers can continue to serve the directory *sometimes*,
25992 without getting overloaded.
25993 - Whenever you get a 503 in response to a directory fetch, try
25994 once more. This will become important once servers start sending
25995 503's whenever they feel busy.
25996 - Fetch a new directory every 120 minutes, not every 40 minutes.
25997 Now that we have hundreds of thousands of users running the old
25998 directory algorithm, it's starting to hurt a lot.
25999 - Bump up the period for forcing a hidden service descriptor upload
26000 from 20 minutes to 1 hour.
26003 Changes in version 0.1.0.16 - 2006-01-02
26004 o Crash bugfixes on 0.1.0.x:
26005 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
26006 corrupting the heap, losing FDs, or crashing when we need to resize
26007 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
26008 - It turns out sparc64 platforms crash on unaligned memory access
26009 too -- so detect and avoid this.
26010 - Handle truncated compressed data correctly (by detecting it and
26012 - Fix possible-but-unlikely free(NULL) in control.c.
26013 - When we were closing connections, there was a rare case that
26014 stomped on memory, triggering seg faults and asserts.
26015 - Avoid potential infinite recursion when building a descriptor. (We
26016 don't know that it ever happened, but better to fix it anyway.)
26017 - We were neglecting to unlink marked circuits from soon-to-close OR
26018 connections, which caused some rare scribbling on freed memory.
26019 - Fix a memory stomping race bug when closing the joining point of two
26020 rendezvous circuits.
26021 - Fix an assert in time parsing found by Steven Murdoch.
26023 o Other bugfixes on 0.1.0.x:
26024 - When we're doing reachability testing, provide more useful log
26025 messages so the operator knows what to expect.
26026 - Do not check whether DirPort is reachable when we are suppressing
26027 advertising it because of hibernation.
26028 - When building with -static or on Solaris, we sometimes needed -ldl.
26029 - One of the dirservers (tor26) changed its IP address.
26030 - When we're deciding whether a stream has enough circuits around
26031 that can handle it, count the freshly dirty ones and not the ones
26032 that are so dirty they won't be able to handle it.
26033 - When we're expiring old circuits, we had a logic error that caused
26034 us to close new rendezvous circuits rather than old ones.
26035 - Give a more helpful log message when you try to change ORPort via
26036 the controller: you should upgrade Tor if you want that to work.
26037 - We were failing to parse Tor versions that start with "Tor ".
26038 - Tolerate faulty streams better: when a stream fails for reason
26039 exitpolicy, stop assuming that the router is lying about his exit
26040 policy. When a stream fails for reason misc, allow it to retry just
26041 as if it was resolvefailed. When a stream has failed three times,
26042 reset its failure count so we can try again and get all three tries.
26045 Changes in version 0.1.0.15 - 2005-09-23
26046 o Bugfixes on 0.1.0.x:
26047 - Reject ports 465 and 587 (spam targets) in default exit policy.
26048 - Don't crash when we don't have any spare file descriptors and we
26049 try to spawn a dns or cpu worker.
26050 - Get rid of IgnoreVersion undocumented config option, and make us
26051 only warn, never exit, when we're running an obsolete version.
26052 - Don't try to print a null string when your server finds itself to
26053 be unreachable and the Address config option is empty.
26054 - Make the numbers in read-history and write-history into uint64s,
26055 so they don't overflow and publish negatives in the descriptor.
26056 - Fix a minor memory leak in smartlist_string_remove().
26057 - We were only allowing ourselves to upload a server descriptor at
26058 most every 20 minutes, even if it changed earlier than that.
26059 - Clean up log entries that pointed to old URLs.
26062 Changes in version 0.1.0.14 - 2005-08-08
26063 o Bugfixes on 0.1.0.x:
26064 - Fix the other half of the bug with crypto handshakes
26066 - Fix an assert trigger if you send a 'signal term' via the
26067 controller when it's listening for 'event info' messages.
26070 Changes in version 0.1.0.13 - 2005-08-04
26071 o Bugfixes on 0.1.0.x:
26072 - Fix a critical bug in the security of our crypto handshakes.
26073 - Fix a size_t underflow in smartlist_join_strings2() that made
26074 it do bad things when you hand it an empty smartlist.
26075 - Fix Windows installer to ship Tor license (thanks to Aphex for
26076 pointing out this oversight) and put a link to the doc directory
26078 - Explicitly set no-unaligned-access for sparc: it turns out the
26079 new gcc's let you compile broken code, but that doesn't make it
26083 Changes in version 0.1.0.12 - 2005-07-18
26084 o New directory servers:
26085 - tor26 has changed IP address.
26087 o Bugfixes on 0.1.0.x:
26088 - Fix a possible double-free in tor_gzip_uncompress().
26089 - When --disable-threads is set, do not search for or link against
26090 pthreads libraries.
26091 - Don't trigger an assert if an authoritative directory server
26092 claims its dirport is 0.
26093 - Fix bug with removing Tor as an NT service: some people were
26094 getting "The service did not return an error." Thanks to Matt
26098 Changes in version 0.1.0.11 - 2005-06-30
26099 o Bugfixes on 0.1.0.x:
26100 - Fix major security bug: servers were disregarding their
26101 exit policies if clients behaved unexpectedly.
26102 - Make OS X init script check for missing argument, so we don't
26103 confuse users who invoke it incorrectly.
26104 - Fix a seg fault in "tor --hash-password foo".
26105 - The MAPADDRESS control command was broken.
26108 Changes in version 0.1.0.10 - 2005-06-14
26110 - Make NT services work and start on startup on Win32 (based on
26111 patch by Matt Edman). See the FAQ entry for details.
26112 - Make 'platform' string in descriptor more accurate for Win32
26113 servers, so it's not just "unknown platform".
26114 - REUSEADDR on normal platforms means you can rebind to the port
26115 right after somebody else has let it go. But REUSEADDR on Win32
26116 means you can bind to the port _even when somebody else already
26117 has it bound_! So, don't do that on Win32.
26118 - Clean up the log messages when starting on Win32 with no config
26120 - Allow seeding the RNG on Win32 even when you're not running as
26121 Administrator. If seeding the RNG on Win32 fails, quit.
26123 o Assert / crash bugs:
26124 - Refuse relay cells that claim to have a length larger than the
26125 maximum allowed. This prevents a potential attack that could read
26126 arbitrary memory (e.g. keys) from an exit server's process
26128 - If unofficial Tor clients connect and send weird TLS certs, our
26129 Tor server triggers an assert. Stop asserting, and start handling
26130 TLS errors better in other situations too.
26131 - Fix a race condition that can trigger an assert when we have a
26132 pending create cell and an OR connection attempt fails.
26135 - Use pthreads for worker processes rather than forking. This was
26136 forced because when we forked, we ended up wasting a lot of
26137 duplicate ram over time.
26138 - Also switch to foo_r versions of some library calls to allow
26139 reentry and threadsafeness.
26140 - Implement --disable-threads configure option. Disable threads on
26141 netbsd and openbsd by default, because they have no reentrant
26142 resolver functions (!), and on solaris since it has other
26144 - Fix possible bug on threading platforms (e.g. win32) which was
26145 leaking a file descriptor whenever a cpuworker or dnsworker died.
26146 - Fix a minor memory leak when somebody establishes an introduction
26147 point at your Tor server.
26148 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
26150 - Add ./configure --with-dmalloc option, to track memory leaks.
26151 - And try to free all memory on closing, so we can detect what
26154 o Protocol correctness:
26155 - When we've connected to an OR and handshaked but didn't like
26156 the result, we were closing the conn without sending destroy
26157 cells back for pending circuits. Now send those destroys.
26158 - Start sending 'truncated' cells back rather than destroy cells
26159 if the circuit closes in front of you. This means we won't have
26160 to abandon partially built circuits.
26161 - Handle changed router status correctly when dirserver reloads
26162 fingerprint file. We used to be dropping all unverified descriptors
26163 right then. The bug was hidden because we would immediately
26164 fetch a directory from another dirserver, which would include the
26165 descriptors we just dropped.
26166 - Revise tor-spec to add more/better stream end reasons.
26167 - Revise all calls to connection_edge_end to avoid sending 'misc',
26168 and to take errno into account where possible.
26169 - Client now retries when streams end early for 'hibernating' or
26170 'resource limit' reasons, rather than failing them.
26171 - Try to be more zealous about calling connection_edge_end when
26172 things go bad with edge conns in connection.c.
26174 o Robustness improvements:
26175 - Better handling for heterogeneous / unreliable nodes:
26176 - Annotate circuits with whether they aim to contain high uptime
26177 nodes and/or high capacity nodes. When building circuits, choose
26179 - This means that every single node in an intro rend circuit,
26180 not just the last one, will have a minimum uptime.
26181 - New config option LongLivedPorts to indicate application streams
26182 that will want high uptime circuits.
26183 - Servers reset uptime when a dir fetch entirely fails. This
26184 hopefully reflects stability of the server's network connectivity.
26185 - If somebody starts his tor server in Jan 2004 and then fixes his
26186 clock, don't make his published uptime be a year.
26187 - Reset published uptime when we wake up from hibernation.
26188 - Introduce a notion of 'internal' circs, which are chosen without
26189 regard to the exit policy of the last hop. Intro and rendezvous
26190 circs must be internal circs, to avoid leaking information. Resolve
26191 and connect streams can use internal circs if they want.
26192 - New circuit pooling algorithm: keep track of what destination ports
26193 we've used recently (start out assuming we'll want to use 80), and
26194 make sure to have enough circs around to satisfy these ports. Also
26195 make sure to have 2 internal circs around if we've required internal
26196 circs lately (and with high uptime if we've seen that lately too).
26197 - Turn addr_policy_compare from a tristate to a quadstate; this should
26198 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
26199 for google.com" problem.
26200 - When a client asks us for a dir mirror and we don't have one,
26201 launch an attempt to get a fresh one.
26202 - First cut at support for "create-fast" cells. Clients can use
26203 these when extending to their first hop, since the TLS already
26204 provides forward secrecy and authentication. Not enabled on
26207 o Reachability testing.
26208 - Your Tor server will automatically try to see if its ORPort and
26209 DirPort are reachable from the outside, and it won't upload its
26210 descriptor until it decides at least ORPort is reachable (when
26211 DirPort is not yet found reachable, publish it as zero).
26212 - When building testing circs for ORPort testing, use only
26213 high-bandwidth nodes, so fewer circuits fail.
26214 - Notice when our IP changes, and reset stats/uptime/reachability.
26215 - Authdirservers don't do ORPort reachability detection, since
26216 they're in clique mode, so it will be rare to find a server not
26217 already connected to them.
26218 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
26222 - Now we allow two unverified servers with the same nickname
26223 but different keys. But if a nickname is verified, only that
26224 nickname+key are allowed.
26225 - If you're an authdirserver connecting to an address:port,
26226 and it's not the OR you were expecting, forget about that
26227 descriptor. If he *was* the one you were expecting, then forget
26228 about all other descriptors for that address:port.
26229 - Allow servers to publish descriptors from 12 hours in the future.
26230 Corollary: only whine about clock skew from the dirserver if
26231 he's a trusted dirserver (since now even verified servers could
26232 have quite wrong clocks).
26233 - Require servers that use the default dirservers to have public IP
26234 addresses. We have too many servers that are configured with private
26235 IPs and their admins never notice the log entries complaining that
26236 their descriptors are being rejected.
26238 o Efficiency improvements:
26239 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
26240 and /dev/poll), and hopefully work better on Windows too.
26241 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
26242 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
26243 - Find libevent even if it's hiding in /usr/local/ and your
26244 CFLAGS and LDFLAGS don't tell you to look there.
26245 - Be able to link with libevent as a shared library (the default
26246 after 1.0d), even if it's hiding in /usr/local/lib and even
26247 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
26248 assuming you're running gcc. Otherwise fail and give a useful
26250 - Switch to a new buffer management algorithm, which tries to avoid
26251 reallocing and copying quite as much. In first tests it looks like
26252 it uses *more* memory on average, but less cpu.
26253 - Switch our internal buffers implementation to use a ring buffer,
26254 to hopefully improve performance for fast servers a lot.
26255 - Reenable the part of the code that tries to flush as soon as an
26256 OR outbuf has a full TLS record available. Perhaps this will make
26257 OR outbufs not grow as huge except in rare cases, thus saving lots
26258 of CPU time plus memory.
26259 - Improve performance for dirservers: stop re-parsing the whole
26260 directory every time you regenerate it.
26261 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
26262 it much faster to look up a circuit for each relay cell.
26263 - Remove most calls to assert_all_pending_dns_resolves_ok(),
26264 since they're eating our cpu on exit nodes.
26265 - Stop wasting time doing a case insensitive comparison for every
26266 dns name every time we do any lookup. Canonicalize the names to
26267 lowercase when you first see them.
26270 - Handle unavailable hidden services better. Handle slow or busy
26271 hidden services better.
26272 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
26273 circ as necessary, if there are any completed ones lying around
26274 when we try to launch one.
26275 - Make hidden services try to establish a rendezvous for 30 seconds
26276 after fetching the descriptor, rather than for n (where n=3)
26277 attempts to build a circuit.
26278 - Adjust maximum skew and age for rendezvous descriptors: let skew
26279 be 48 hours rather than 90 minutes.
26280 - Reject malformed .onion addresses rather then passing them on as
26281 normal web requests.
26284 - More Tor controller support. See
26285 http://tor.eff.org/doc/control-spec.txt for all the new features,
26286 including signals to emulate unix signals from any platform;
26287 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
26288 closestream; closecircuit; etc.
26289 - Encode hashed controller passwords in hex instead of base64,
26290 to make it easier to write controllers.
26291 - Revise control spec and implementation to allow all log messages to
26292 be sent to controller with their severities intact (suggested by
26293 Matt Edman). Disable debug-level logs while delivering a debug-level
26294 log to the controller, to prevent loop. Update TorControl to handle
26295 new log event types.
26297 o New config options/defaults:
26298 - Begin scrubbing sensitive strings from logs by default. Turn off
26299 the config option SafeLogging if you need to do debugging.
26300 - New exit policy: accept most low-numbered ports, rather than
26301 rejecting most low-numbered ports.
26302 - Put a note in the torrc about abuse potential with the default
26304 - Add support for CONNECTing through https proxies, with "HttpsProxy"
26306 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
26307 based on patch from Adam Langley (basic auth only).
26308 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
26309 the fast servers that have been joining lately. (Clients are now
26310 willing to load balance over up to 2 MB of advertised bandwidth
26312 - New config option MaxAdvertisedBandwidth which lets you advertise
26313 a low bandwidthrate (to not attract as many circuits) while still
26314 allowing a higher bandwidthrate in reality.
26315 - Require BandwidthRate to be at least 20kB/s for servers.
26316 - Add a NoPublish config option, so you can be a server (e.g. for
26317 testing running Tor servers in other Tor networks) without
26318 publishing your descriptor to the primary dirservers.
26319 - Add a new AddressMap config directive to rewrite incoming socks
26320 addresses. This lets you, for example, declare an implicit
26321 required exit node for certain sites.
26322 - Add a new TrackHostExits config directive to trigger addressmaps
26323 for certain incoming socks addresses -- for sites that break when
26324 your exit keeps changing (based on patch from Mike Perry).
26325 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
26326 which describes how often we retry making new circuits if current
26327 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
26328 how long we're willing to make use of an already-dirty circuit.
26329 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
26330 a config option "ShutdownWaitLength" (when using kill -INT on
26332 - Fix an edge case in parsing config options: if they say "--"
26333 on the commandline, it's not a config option (thanks weasel).
26334 - New config option DirAllowPrivateAddresses for authdirservers.
26335 Now by default they refuse router descriptors that have non-IP or
26336 private-IP addresses.
26337 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
26338 smart" default value: low for servers and high for clients.
26339 - Some people were putting "Address " in their torrc, and they had
26340 a buggy resolver that resolved " " to 0.0.0.0. Oops.
26341 - If DataDir is ~/.tor, and that expands to /.tor, then default to
26342 LOCALSTATEDIR/tor instead.
26343 - Implement --verify-config command-line option to check if your torrc
26344 is valid without actually launching Tor.
26346 o Logging improvements:
26347 - When dirservers refuse a server descriptor, we now log its
26348 contactinfo, platform, and the poster's IP address.
26349 - Only warn once per nickname from add_nickname_list_to_smartlist()
26350 per failure, so an entrynode or exitnode choice that's down won't
26352 - When we're connecting to an OR and he's got a different nickname/key
26353 than we were expecting, only complain loudly if we're an OP or a
26354 dirserver. Complaining loudly to the OR admins just confuses them.
26355 - Whine at you if you're a server and you don't set your contactinfo.
26356 - Warn when exit policy implicitly allows local addresses.
26357 - Give a better warning when some other server advertises an
26358 ORPort that is actually an apache running ssl.
26359 - If we get an incredibly skewed timestamp from a dirserver mirror
26360 that isn't a verified OR, don't warn -- it's probably him that's
26362 - When a dirserver causes you to give a warn, mention which dirserver
26364 - Initialize libevent later in the startup process, so the logs are
26365 already established by the time we start logging libevent warns.
26366 - Use correct errno on win32 if libevent fails.
26367 - Check and warn about known-bad/slow libevent versions.
26368 - Stop warning about sigpipes in the logs. We're going to
26369 pretend that getting these occasionally is normal and fine.
26371 o New contrib scripts:
26372 - New experimental script tor/contrib/exitlist: a simple python
26373 script to parse directories and find Tor nodes that exit to listed
26375 - New experimental script tor/contrib/ExerciseServer.py (needs more
26376 work) that uses the controller interface to build circuits and
26377 fetch pages over them. This will help us bootstrap servers that
26378 have lots of capacity but haven't noticed it yet.
26379 - New experimental script tor/contrib/PathDemo.py (needs more work)
26380 that uses the controller interface to let you choose whole paths
26382 "<hostname>.<path,separated by dots>.<length of path>.path"
26383 - New contributed script "privoxy-tor-toggle" to toggle whether
26384 Privoxy uses Tor. Seems to be configured for Debian by default.
26385 - Have torctl.in/tor.sh.in check for location of su binary (needed
26389 - chdir() to your datadirectory at the *end* of the daemonize process,
26390 not the beginning. This was a problem because the first time you
26391 run tor, if your datadir isn't there, and you have runasdaemon set
26392 to 1, it will try to chdir to it before it tries to create it. Oops.
26393 - Fix several double-mark-for-close bugs, e.g. where we were finding
26394 a conn for a cell even if that conn is already marked for close.
26395 - Stop most cases of hanging up on a socks connection without sending
26397 - Fix a bug in the RPM package: set home directory for _tor to
26398 something more reasonable when first installing.
26399 - Stop putting nodename in the Platform string in server descriptors.
26400 It doesn't actually help, and it is confusing/upsetting some people.
26401 - When using preferred entry or exit nodes, ignore whether the
26402 circuit wants uptime or capacity. They asked for the nodes, they
26404 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
26405 artificially capped at 500kB.
26406 - Cache local dns resolves correctly even when they're .exit
26408 - If we're hibernating and we get a SIGINT, exit immediately.
26409 - tor-resolve requests were ignoring .exit if there was a working circuit
26410 they could use instead.
26411 - Pay more attention to the ClientOnly config option.
26412 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
26413 installer screens; and don't put stuff into StartupItems unless
26414 the user asks you to.
26417 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
26418 rather than just rejecting it.
26419 - If our clock jumps forward by 100 seconds or more, assume something
26420 has gone wrong with our network and abandon all not-yet-used circs.
26421 - When an application is using socks5, give him the whole variety of
26422 potential socks5 responses (connect refused, host unreachable, etc),
26423 rather than just "success" or "failure".
26424 - A more sane version numbering system. See
26425 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
26426 - Change version parsing logic: a version is "obsolete" if it is not
26427 recommended and (1) there is a newer recommended version in the
26428 same series, or (2) there are no recommended versions in the same
26429 series, but there are some recommended versions in a newer series.
26430 A version is "new" if it is newer than any recommended version in
26432 - Report HTTP reasons to client when getting a response from directory
26433 servers -- so you can actually know what went wrong.
26434 - Reject odd-looking addresses at the client (e.g. addresses that
26435 contain a colon), rather than having the server drop them because
26437 - Stop publishing socksport in the directory, since it's not
26438 actually meant to be public. For compatibility, publish a 0 there
26440 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
26441 cookies to disk and doesn't log each web request to disk. (Thanks
26442 to Brett Carrington for pointing this out.)
26443 - Add OSX uninstall instructions. An actual uninstall script will
26445 - Add "opt hibernating 1" to server descriptor to make it clearer
26446 whether the server is hibernating.
26449 Changes in version 0.0.9.10 - 2005-06-16
26450 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
26451 - Refuse relay cells that claim to have a length larger than the
26452 maximum allowed. This prevents a potential attack that could read
26453 arbitrary memory (e.g. keys) from an exit server's process
26457 Changes in version 0.0.9.9 - 2005-04-23
26458 o Bugfixes on 0.0.9.x:
26459 - If unofficial Tor clients connect and send weird TLS certs, our
26460 Tor server triggers an assert. This release contains a minimal
26461 backport from the broader fix that we put into 0.1.0.4-rc.
26464 Changes in version 0.0.9.8 - 2005-04-07
26465 o Bugfixes on 0.0.9.x:
26466 - We have a bug that I haven't found yet. Sometimes, very rarely,
26467 cpuworkers get stuck in the 'busy' state, even though the cpuworker
26468 thinks of itself as idle. This meant that no new circuits ever got
26469 established. Here's a workaround to kill any cpuworker that's been
26470 busy for more than 100 seconds.
26473 Changes in version 0.0.9.7 - 2005-04-01
26474 o Bugfixes on 0.0.9.x:
26475 - Fix another race crash bug (thanks to Glenn Fink for reporting).
26476 - Compare identity to identity, not to nickname, when extending to
26477 a router not already in the directory. This was preventing us from
26478 extending to unknown routers. Oops.
26479 - Make sure to create OS X Tor user in <500 range, so we aren't
26480 creating actual system users.
26481 - Note where connection-that-hasn't-sent-end was marked, and fix
26482 a few really loud instances of this harmless bug (it's fixed more
26486 Changes in version 0.0.9.6 - 2005-03-24
26487 o Bugfixes on 0.0.9.x (crashes and asserts):
26488 - Add new end stream reasons to maintenance branch. Fix bug where
26489 reason (8) could trigger an assert. Prevent bug from recurring.
26490 - Apparently win32 stat wants paths to not end with a slash.
26491 - Fix assert triggers in assert_cpath_layer_ok(), where we were
26492 blowing away the circuit that conn->cpath_layer points to, then
26493 checking to see if the circ is well-formed. Backport check to make
26494 sure we dont use the cpath on a closed connection.
26495 - Prevent circuit_resume_edge_reading_helper() from trying to package
26496 inbufs for marked-for-close streams.
26497 - Don't crash on hup if your options->address has become unresolvable.
26498 - Some systems (like OS X) sometimes accept() a connection and tell
26499 you the remote host is 0.0.0.0:0. If this happens, due to some
26500 other mis-features, we get confused; so refuse the conn for now.
26502 o Bugfixes on 0.0.9.x (other):
26503 - Fix harmless but scary "Unrecognized content encoding" warn message.
26504 - Add new stream error reason: TORPROTOCOL reason means "you are not
26505 speaking a version of Tor I understand; say bye-bye to your stream."
26506 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
26507 into the future, now that we are more tolerant of skew. This
26508 resolves a bug where a Tor server would refuse to cache a directory
26509 because all the directories it gets are too far in the future;
26510 yet the Tor server never logs any complaints about clock skew.
26511 - Mac packaging magic: make man pages useable, and do not overwrite
26512 existing torrc files.
26513 - Make OS X log happily to /var/log/tor/tor.log
26516 Changes in version 0.0.9.5 - 2005-02-22
26517 o Bugfixes on 0.0.9.x:
26518 - Fix an assert race at exit nodes when resolve requests fail.
26519 - Stop picking unverified dir mirrors--it only leads to misery.
26520 - Patch from Matt Edman to make NT services work better. Service
26521 support is still not compiled into the executable by default.
26522 - Patch from Dmitri Bely so the Tor service runs better under
26523 the win32 SYSTEM account.
26524 - Make tor-resolve actually work (?) on Win32.
26525 - Fix a sign bug when getrlimit claims to have 4+ billion
26526 file descriptors available.
26527 - Stop refusing to start when bandwidthburst == bandwidthrate.
26528 - When create cells have been on the onion queue more than five
26529 seconds, just send back a destroy and take them off the list.
26532 Changes in version 0.0.9.4 - 2005-02-03
26533 o Bugfixes on 0.0.9:
26534 - Fix an assert bug that took down most of our servers: when
26535 a server claims to have 1 GB of bandwidthburst, don't
26537 - Don't crash as badly if we have spawned the max allowed number
26538 of dnsworkers, or we're out of file descriptors.
26539 - Block more file-sharing ports in the default exit policy.
26540 - MaxConn is now automatically set to the hard limit of max
26541 file descriptors we're allowed (ulimit -n), minus a few for
26543 - Give a clearer message when servers need to raise their
26544 ulimit -n when they start running out of file descriptors.
26545 - SGI Compatibility patches from Jan Schaumann.
26546 - Tolerate a corrupt cached directory better.
26547 - When a dirserver hasn't approved your server, list which one.
26548 - Go into soft hibernation after 95% of the bandwidth is used,
26549 not 99%. This is especially important for daily hibernators who
26550 have a small accounting max. Hopefully it will result in fewer
26551 cut connections when the hard hibernation starts.
26552 - Load-balance better when using servers that claim more than
26553 800kB/s of capacity.
26554 - Make NT services work (experimental, only used if compiled in).
26557 Changes in version 0.0.9.3 - 2005-01-21
26558 o Bugfixes on 0.0.9:
26559 - Backport the cpu use fixes from main branch, so busy servers won't
26560 need as much processor time.
26561 - Work better when we go offline and then come back, or when we
26562 run Tor at boot before the network is up. We do this by
26563 optimistically trying to fetch a new directory whenever an
26564 application request comes in and we think we're offline -- the
26565 human is hopefully a good measure of when the network is back.
26566 - Backport some minimal hidserv bugfixes: keep rend circuits open as
26567 long as you keep using them; actually publish hidserv descriptors
26568 shortly after they change, rather than waiting 20-40 minutes.
26569 - Enable Mac startup script by default.
26570 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
26571 - When you update AllowUnverifiedNodes or FirewallPorts via the
26572 controller's setconf feature, we were always appending, never
26574 - When you update HiddenServiceDir via setconf, it was screwing up
26575 the order of reading the lines, making it fail.
26576 - Do not rewrite a cached directory back to the cache; otherwise we
26577 will think it is recent and not fetch a newer one on startup.
26578 - Workaround for webservers that lie about Content-Encoding: Tor
26579 now tries to autodetect compressed directories and compression
26580 itself. This lets us Proxypass dir fetches through apache.
26583 Changes in version 0.0.9.2 - 2005-01-04
26584 o Bugfixes on 0.0.9 (crashes and asserts):
26585 - Fix an assert on startup when the disk is full and you're logging
26587 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
26588 style address, then we'd crash.
26589 - Fix an assert trigger when the running-routers string we get from
26590 a dirserver is broken.
26591 - Make worker threads start and run on win32. Now win32 servers
26593 - Bandaid (not actually fix, but now it doesn't crash) an assert
26594 where the dns worker dies mysteriously and the main Tor process
26595 doesn't remember anything about the address it was resolving.
26597 o Bugfixes on 0.0.9 (Win32):
26598 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
26599 name out of the warning/assert messages.
26600 - Fix a superficial "unhandled error on read" bug on win32.
26601 - The win32 installer no longer requires a click-through for our
26602 license, since our Free Software license grants rights but does not
26604 - Win32: When connecting to a dirserver fails, try another one
26605 immediately. (This was already working for non-win32 Tors.)
26606 - Stop trying to parse $HOME on win32 when hunting for default
26608 - Make tor-resolve.c work on win32 by calling network_init().
26610 o Bugfixes on 0.0.9 (other):
26611 - Make 0.0.9.x build on Solaris again.
26612 - Due to a fencepost error, we were blowing away the \n when reporting
26613 confvalue items in the controller. So asking for multiple config
26614 values at once couldn't work.
26615 - When listing circuits that are pending on an opening OR connection,
26616 if we're an OR we were listing circuits that *end* at us as
26617 being pending on every listener, dns/cpu worker, etc. Stop that.
26618 - Dirservers were failing to create 'running-routers' or 'directory'
26619 strings if we had more than some threshold of routers. Fix them so
26620 they can handle any number of routers.
26621 - Fix a superficial "Duplicate mark for close" bug.
26622 - Stop checking for clock skew for OR connections, even for servers.
26623 - Fix a fencepost error that was chopping off the last letter of any
26624 nickname that is the maximum allowed nickname length.
26625 - Update URLs in log messages so they point to the new website.
26626 - Fix a potential problem in mangling server private keys while
26627 writing to disk (not triggered yet, as far as we know).
26628 - Include the licenses for other free software we include in Tor,
26629 now that we're shipping binary distributions more regularly.
26632 Changes in version 0.0.9.1 - 2004-12-15
26633 o Bugfixes on 0.0.9:
26634 - Make hibernation actually work.
26635 - Make HashedControlPassword config option work.
26636 - When we're reporting event circuit status to a controller,
26637 don't use the stream status code.
26640 Changes in version 0.0.9 - 2004-12-12
26641 o Bugfixes on 0.0.8.1 (Crashes and asserts):
26642 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
26643 write() call will fail and we handle it there.
26644 - When we run out of disk space, or other log writing error, don't
26645 crash. Just stop logging to that log and continue.
26646 - Fix isspace() and friends so they still make Solaris happy
26647 but also so they don't trigger asserts on win32.
26648 - Fix assert failure on malformed socks4a requests.
26649 - Fix an assert bug where a hidden service provider would fail if
26650 the first hop of his rendezvous circuit was down.
26651 - Better handling of size_t vs int, so we're more robust on 64
26654 o Bugfixes on 0.0.8.1 (Win32):
26655 - Make windows sockets actually non-blocking (oops), and handle
26656 win32 socket errors better.
26657 - Fix parse_iso_time on platforms without strptime (eg win32).
26658 - win32: when being multithreaded, leave parent fdarray open.
26659 - Better handling of winsock includes on non-MSV win32 compilers.
26660 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
26662 - Make unit tests work on win32.
26664 o Bugfixes on 0.0.8.1 (Path selection and streams):
26665 - Calculate timeout for waiting for a connected cell from the time
26666 we sent the begin cell, not from the time the stream started. If
26667 it took a long time to establish the circuit, we would time out
26668 right after sending the begin cell.
26669 - Fix router_compare_addr_to_addr_policy: it was not treating a port
26670 of * as always matching, so we were picking reject *:* nodes as
26671 exit nodes too. Oops.
26672 - When read() failed on a stream, we would close it without sending
26673 back an end. So 'connection refused' would simply be ignored and
26674 the user would get no response.
26675 - Stop a sigpipe: when an 'end' cell races with eof from the app,
26676 we shouldn't hold-open-until-flush if the eof arrived first.
26677 - Let resolve conns retry/expire also, rather than sticking around
26679 - Fix more dns related bugs: send back resolve_failed and end cells
26680 more reliably when the resolve fails, rather than closing the
26681 circuit and then trying to send the cell. Also attach dummy resolve
26682 connections to a circuit *before* calling dns_resolve(), to fix
26683 a bug where cached answers would never be sent in RESOLVED cells.
26685 o Bugfixes on 0.0.8.1 (Circuits):
26686 - Finally fix a bug that's been plaguing us for a year:
26687 With high load, circuit package window was reaching 0. Whenever
26688 we got a circuit-level sendme, we were reading a lot on each
26689 socket, but only writing out a bit. So we would eventually reach
26690 eof. This would be noticed and acted on even when there were still
26691 bytes sitting in the inbuf.
26692 - Use identity comparison, not nickname comparison, to choose which
26693 half of circuit-ID-space each side gets to use. This is needed
26694 because sometimes we think of a router as a nickname, and sometimes
26695 as a hex ID, and we can't predict what the other side will do.
26697 o Bugfixes on 0.0.8.1 (Other):
26698 - Fix a whole slew of memory leaks.
26699 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
26700 - If we are using select, make sure we stay within FD_SETSIZE.
26701 - When poll() is interrupted, we shouldn't believe the revents values.
26702 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
26703 and smartlist_len, which are two major profiling offenders.
26704 - If do_hup fails, actually notice.
26705 - Flush the log file descriptor after we print "Tor opening log file",
26706 so we don't see those messages days later.
26707 - Hidden service operators now correctly handle version 1 style
26708 INTRODUCE1 cells (nobody generates them still, so not a critical
26710 - Handle more errnos from accept() without closing the listener.
26711 Some OpenBSD machines were closing their listeners because
26712 they ran out of file descriptors.
26713 - Some people had wrapped their tor client/server in a script
26714 that would restart it whenever it died. This did not play well
26715 with our "shut down if your version is obsolete" code. Now people
26716 don't fetch a new directory if their local cached version is
26718 - Make our autogen.sh work on ksh as well as bash.
26719 - Better torrc example lines for dirbindaddress and orbindaddress.
26720 - Improved bounds checking on parsed ints (e.g. config options and
26721 the ones we find in directories.)
26722 - Stop using separate defaults for no-config-file and
26723 empty-config-file. Now you have to explicitly turn off SocksPort,
26724 if you don't want it open.
26725 - We were starting to daemonize before we opened our logs, so if
26726 there were any problems opening logs, we would complain to stderr,
26727 which wouldn't work, and then mysteriously exit.
26728 - If a verified OR connects to us before he's uploaded his descriptor,
26729 or we verify him and hup but he still has the original TLS
26730 connection, then conn->nickname is still set like he's unverified.
26732 o Code security improvements, inspired by Ilja:
26733 - tor_snprintf wrapper over snprintf with consistent (though not C99)
26735 - Replace sprintf with tor_snprintf. (I think they were all safe, but
26737 - Replace strcpy/strncpy with strlcpy in more places.
26738 - Avoid strcat; use tor_snprintf or strlcat instead.
26740 o Features (circuits and streams):
26741 - New circuit building strategy: keep a list of ports that we've
26742 used in the past 6 hours, and always try to have 2 circuits open
26743 or on the way that will handle each such port. Seed us with port
26744 80 so web users won't complain that Tor is "slow to start up".
26745 - Make kill -USR1 dump more useful stats about circuits.
26746 - When warning about retrying or giving up, print the address, so
26747 the user knows which one it's talking about.
26748 - If you haven't used a clean circuit in an hour, throw it away,
26749 just to be on the safe side. (This means after 6 hours a totally
26750 unused Tor client will have no circuits open.)
26751 - Support "foo.nickname.exit" addresses, to let Alice request the
26752 address "foo" as viewed by exit node "nickname". Based on a patch
26753 from Geoff Goodell.
26754 - If your requested entry or exit node has advertised bandwidth 0,
26756 - Be more greedy about filling up relay cells -- we try reading again
26757 once we've processed the stuff we read, in case enough has arrived
26758 to fill the last cell completely.
26759 - Refuse application socks connections to port 0.
26760 - Use only 0.0.9pre1 and later servers for resolve cells.
26762 o Features (bandwidth):
26763 - Hibernation: New config option "AccountingMax" lets you
26764 set how many bytes per month (in each direction) you want to
26765 allow your server to consume. Rather than spreading those
26766 bytes out evenly over the month, we instead hibernate for some
26767 of the month and pop up at a deterministic time, work until
26768 the bytes are consumed, then hibernate again. Config option
26769 "MonthlyAccountingStart" lets you specify which day of the month
26770 your billing cycle starts on.
26771 - Implement weekly/monthly/daily accounting: now you specify your
26772 hibernation properties by
26773 AccountingMax N bytes|KB|MB|GB|TB
26774 AccountingStart day|week|month [day] HH:MM
26775 Defaults to "month 1 0:00".
26776 - Let bandwidth and interval config options be specified as 5 bytes,
26777 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
26779 o Features (directories):
26780 - New "router-status" line in directory, to better bind each verified
26781 nickname to its identity key.
26782 - Clients can ask dirservers for /dir.z to get a compressed version
26783 of the directory. Only works for servers running 0.0.9, of course.
26784 - Make clients cache directories and use them to seed their router
26785 lists at startup. This means clients have a datadir again.
26786 - Respond to content-encoding headers by trying to uncompress as
26788 - Clients and servers now fetch running-routers; cache
26789 running-routers; compress running-routers; serve compressed
26791 - Make moria2 advertise a dirport of 80, so people behind firewalls
26792 will be able to get a directory.
26793 - Http proxy support
26794 - Dirservers translate requests for http://%s:%d/x to /x
26795 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
26796 be routed through this host.
26797 - Clients ask for /tor/x rather than /x for new enough dirservers.
26798 This way we can one day coexist peacefully with apache.
26799 - Clients specify a "Host: %s%d" http header, to be compatible
26800 with more proxies, and so running squid on an exit node can work.
26801 - Protect dirservers from overzealous descriptor uploading -- wait
26802 10 seconds after directory gets dirty, before regenerating.
26804 o Features (packages and install):
26805 - Add NSI installer contributed by J Doe.
26806 - Apply NT service patch from Osamu Fujino. Still needs more work.
26807 - Commit VC6 and VC7 workspace/project files.
26808 - Commit a tor.spec for making RPM files, with help from jbash.
26809 - Add contrib/torctl.in contributed by Glenn Fink.
26810 - Make expand_filename handle ~ and ~username.
26811 - Use autoconf to enable largefile support where necessary. Use
26812 ftello where available, since ftell can fail at 2GB.
26813 - Ship src/win32/ in the tarball, so people can use it to build.
26814 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
26817 o Features (ui controller):
26818 - Control interface: a separate program can now talk to your
26819 client/server over a socket, and get/set config options, receive
26820 notifications of circuits and streams starting/finishing/dying,
26821 bandwidth used, etc. The next step is to get some GUIs working.
26822 Let us know if you want to help out. See doc/control-spec.txt .
26823 - Ship a contrib/tor-control.py as an example script to interact
26824 with the control port.
26825 - "tor --hash-password zzyxz" will output a salted password for
26826 use in authenticating to the control interface.
26827 - Implement the control-spec's SAVECONF command, to write your
26828 configuration to torrc.
26829 - Get cookie authentication for the controller closer to working.
26830 - When set_conf changes our server descriptor, upload a new copy.
26831 But don't upload it too often if there are frequent changes.
26833 o Features (config and command-line):
26834 - Deprecate unofficial config option abbreviations, and abbreviations
26835 not on the command line.
26836 - Configuration infrastructure support for warning on obsolete
26838 - Give a slightly more useful output for "tor -h".
26839 - Break DirFetchPostPeriod into:
26840 - DirFetchPeriod for fetching full directory,
26841 - StatusFetchPeriod for fetching running-routers,
26842 - DirPostPeriod for posting server descriptor,
26843 - RendPostPeriod for posting hidden service descriptors.
26844 - New log format in config:
26845 "Log minsev[-maxsev] stdout|stderr|syslog" or
26846 "Log minsev[-maxsev] file /var/foo"
26847 - DirPolicy config option, to let people reject incoming addresses
26848 from their dirserver.
26849 - "tor --list-fingerprint" will list your identity key fingerprint
26851 - Make tor --version --version dump the cvs Id of every file.
26852 - New 'MyFamily nick1,...' config option for a server to
26853 specify other servers that shouldn't be used in the same circuit
26854 with it. Only believed if nick1 also specifies us.
26855 - New 'NodeFamily nick1,nick2,...' config option for a client to
26856 specify nodes that it doesn't want to use in the same circuit.
26857 - New 'Redirectexit pattern address:port' config option for a
26858 server to redirect exit connections, e.g. to a local squid.
26859 - Add "pass" target for RedirectExit, to make it easier to break
26860 out of a sequence of RedirectExit rules.
26861 - Make the dirservers file obsolete.
26862 - Include a dir-signing-key token in directories to tell the
26863 parsing entity which key is being used to sign.
26864 - Remove the built-in bulky default dirservers string.
26865 - New config option "Dirserver %s:%d [fingerprint]", which can be
26866 repeated as many times as needed. If no dirservers specified,
26867 default to moria1,moria2,tor26.
26868 - Make 'Routerfile' config option obsolete.
26869 - Discourage people from setting their dirfetchpostperiod more often
26870 than once per minute.
26872 o Features (other):
26873 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
26874 get back to normal.)
26875 - Accept *:706 (silc) in default exit policy.
26876 - Implement new versioning format for post 0.1.
26877 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
26878 log more informatively.
26879 - Check clock skew for verified servers, but allow unverified
26880 servers and clients to have any clock skew.
26881 - Make sure the hidden service descriptors are at a random offset
26882 from each other, to hinder linkability.
26883 - Clients now generate a TLS cert too, in preparation for having
26884 them act more like real nodes.
26885 - Add a pure-C tor-resolve implementation.
26886 - Use getrlimit and friends to ensure we can reach MaxConn (currently
26887 1024) file descriptors.
26888 - Raise the max dns workers from 50 to 100.
26891 Changes in version 0.0.8.1 - 2004-10-13
26893 - Fix a seg fault that can be triggered remotely for Tor
26894 clients/servers with an open dirport.
26895 - Fix a rare assert trigger, where routerinfos for entries in
26896 our cpath would expire while we're building the path.
26897 - Fix a bug in OutboundBindAddress so it (hopefully) works.
26898 - Fix a rare seg fault for people running hidden services on
26899 intermittent connections.
26900 - Fix a bug in parsing opt keywords with objects.
26901 - Fix a stale pointer assert bug when a stream detaches and
26903 - Fix a string format vulnerability (probably not exploitable)
26904 in reporting stats locally.
26905 - Fix an assert trigger: sometimes launching circuits can fail
26906 immediately, e.g. because too many circuits have failed recently.
26907 - Fix a compile warning on 64 bit platforms.
26910 Changes in version 0.0.8 - 2004-08-25
26912 - Made our unit tests compile again on OpenBSD 3.5, and tor
26913 itself compile again on OpenBSD on a sparc64.
26914 - We were neglecting milliseconds when logging on win32, so
26915 everything appeared to happen at the beginning of each second.
26916 - Check directory signature _before_ you decide whether you're
26917 you're running an obsolete version and should exit.
26918 - Check directory signature _before_ you parse the running-routers
26919 list to decide who's running.
26920 - Check return value of fclose while writing to disk, so we don't
26921 end up with broken files when servers run out of disk space.
26922 - Port it to SunOS 5.9 / Athena
26923 - Fix two bugs in saving onion keys to disk when rotating, so
26924 hopefully we'll get fewer people using old onion keys.
26925 - Remove our mostly unused -- and broken -- hex_encode()
26926 function. Use base16_encode() instead. (Thanks to Timo Lindfors
26927 for pointing out this bug.)
26928 - Only pick and establish intro points after we've gotten a
26930 - Fix assert triggers: if the other side returns an address 0.0.0.0,
26931 don't put it into the client dns cache.
26932 - If a begin failed due to exit policy, but we believe the IP
26933 address should have been allowed, switch that router to exitpolicy
26934 reject *:* until we get our next directory.
26936 o Protocol changes:
26937 - 'Extend' relay cell payloads now include the digest of the
26938 intended next hop's identity key. Now we can verify that we're
26939 extending to the right router, and also extend to routers we
26940 hadn't heard of before.
26943 - Tor nodes can now act as relays (with an advertised ORPort)
26944 without being manually verified by the dirserver operators.
26945 - Uploaded descriptors of unverified routers are now accepted
26946 by the dirservers, and included in the directory.
26947 - Verified routers are listed by nickname in the running-routers
26948 list; unverified routers are listed as "$<fingerprint>".
26949 - We now use hash-of-identity-key in most places rather than
26950 nickname or addr:port, for improved security/flexibility.
26951 - AllowUnverifiedNodes config option to let circuits choose no-name
26952 routers in entry,middle,exit,introduction,rendezvous positions.
26953 Allow middle and rendezvous positions by default.
26954 - When picking unverified routers, skip those with low uptime and/or
26955 low bandwidth, depending on what properties you care about.
26956 - ClientOnly option for nodes that never want to become servers.
26957 - Directory caching.
26958 - "AuthoritativeDir 1" option for the official dirservers.
26959 - Now other nodes (clients and servers) will cache the latest
26960 directory they've pulled down.
26961 - They can enable their DirPort to serve it to others.
26962 - Clients will pull down a directory from any node with an open
26963 DirPort, and check the signature/timestamp correctly.
26964 - Authoritative dirservers now fetch directories from other
26965 authdirservers, to stay better synced.
26966 - Running-routers list tells who's down also, along with noting
26967 if they're verified (listed by nickname) or unverified (listed
26969 - Allow dirservers to serve running-router list separately.
26970 This isn't used yet.
26971 - You can now fetch $DIRURL/running-routers to get just the
26972 running-routers line, not the whole descriptor list. (But
26973 clients don't use this yet.)
26974 - Clients choose nodes proportional to advertised bandwidth.
26975 - Clients avoid using nodes with low uptime as introduction points.
26976 - Handle servers with dynamic IP addresses: don't just replace
26977 options->Address with the resolved one at startup, and
26978 detect our address right before we make a routerinfo each time.
26979 - 'FascistFirewall' option to pick dirservers and ORs on specific
26980 ports; plus 'FirewallPorts' config option to tell FascistFirewall
26981 which ports are open. (Defaults to 80,443)
26982 - Try other dirservers immediately if the one you try is down. This
26983 should tolerate down dirservers better now.
26984 - ORs connect-on-demand to other ORs
26985 - If you get an extend cell to an OR you're not connected to,
26986 connect, handshake, and forward the create cell.
26987 - The authoritative dirservers stay connected to everybody,
26988 and everybody stays connected to 0.0.7 servers, but otherwise
26989 clients/servers expire unused connections after 5 minutes.
26990 - When servers get a sigint, they delay 30 seconds (refusing new
26991 connections) then exit. A second sigint causes immediate exit.
26992 - File and name management:
26993 - Look for .torrc if no CONFDIR "torrc" is found.
26994 - If no datadir is defined, then choose, make, and secure ~/.tor
26996 - If torrc not found, exitpolicy reject *:*.
26997 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
26998 - If no nickname is defined, derive default from hostname.
26999 - Rename secret key files, e.g. identity.key -> secret_id_key,
27000 to discourage people from mailing their identity key to tor-ops.
27001 - Refuse to build a circuit before the directory has arrived --
27002 it won't work anyway, since you won't know the right onion keys
27004 - Parse tor version numbers so we can do an is-newer-than check
27005 rather than an is-in-the-list check.
27006 - New socks command 'resolve', to let us shim gethostbyname()
27008 - A 'tor_resolve' script to access the socks resolve functionality.
27009 - A new socks-extensions.txt doc file to describe our
27010 interpretation and extensions to the socks protocols.
27011 - Add a ContactInfo option, which gets published in descriptor.
27012 - Write tor version at the top of each log file
27013 - New docs in the tarball:
27015 - Document that you should proxy your SSL traffic too.
27016 - Log a warning if the user uses an unsafe socks variant, so people
27017 are more likely to learn about privoxy or socat.
27018 - Log a warning if you're running an unverified server, to let you
27019 know you might want to get it verified.
27020 - Change the default exit policy to reject the default edonkey,
27021 kazaa, gnutella ports.
27022 - Add replace_file() to util.[ch] to handle win32's rename().
27023 - Publish OR uptime in descriptor (and thus in directory) too.
27024 - Remember used bandwidth (both in and out), and publish 15-minute
27025 snapshots for the past day into our descriptor.
27026 - Be more aggressive about trying to make circuits when the network
27027 has changed (e.g. when you unsuspend your laptop).
27028 - Check for time skew on http headers; report date in response to
27030 - If the entrynode config line has only one node, don't pick it as
27032 - Add strict{entry|exit}nodes config options. If set to 1, then
27033 we refuse to build circuits that don't include the specified entry
27035 - OutboundBindAddress config option, to bind to a specific
27036 IP address for outgoing connect()s.
27037 - End truncated log entries (e.g. directories) with "[truncated]".
27040 Changes in version 0.0.7.3 - 2004-08-12
27041 o Stop dnsworkers from triggering an assert failure when you
27042 ask them to resolve the host "".
27045 Changes in version 0.0.7.2 - 2004-07-07
27046 o A better fix for the 0.0.0.0 problem, that will hopefully
27047 eliminate the remaining related assertion failures.
27050 Changes in version 0.0.7.1 - 2004-07-04
27051 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
27052 since internally we use 0.0.0.0 to signify "not yet resolved".
27055 Changes in version 0.0.7 - 2004-06-07
27056 o Fixes for crashes and other obnoxious bugs:
27057 - Fix an epipe bug: sometimes when directory connections failed
27058 to connect, we would give them a chance to flush before closing
27060 - When we detached from a circuit because of resolvefailed, we
27061 would immediately try the same circuit twice more, and then
27062 give up on the resolve thinking we'd tried three different
27064 - Limit the number of intro circuits we'll attempt to build for a
27065 hidden service per 15-minute period.
27066 - Check recommended-software string *early*, before actually parsing
27067 the directory. Thus we can detect an obsolete version and exit,
27068 even if the new directory format doesn't parse.
27069 o Fixes for security bugs:
27070 - Remember which nodes are dirservers when you startup, and if a
27071 random OR enables his dirport, don't automatically assume he's
27072 a trusted dirserver.
27074 - Directory connections were asking the wrong poll socket to
27075 start writing, and not asking themselves to start writing.
27076 - When we detached from a circuit because we sent a begin but
27077 didn't get a connected, we would use it again the first time;
27078 but after that we would correctly switch to a different one.
27079 - Stop warning when the first onion decrypt attempt fails; they
27080 will sometimes legitimately fail now that we rotate keys.
27081 - Override unaligned-access-ok check when $host_cpu is ia64 or
27082 arm. Apparently they allow it but the kernel whines.
27083 - Dirservers try to reconnect periodically too, in case connections
27085 - Fix some memory leaks in directory servers.
27086 - Allow backslash in Win32 filenames.
27087 - Made Tor build complain-free on FreeBSD, hopefully without
27088 breaking other BSD builds. We'll see.
27089 - Check directory signatures based on name of signer, not on whom
27090 we got the directory from. This will let us cache directories more
27092 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
27095 - Doxygen markup on all functions and global variables.
27096 - Make directory functions update routerlist, not replace it. So
27097 now directory disagreements are not so critical a problem.
27098 - Remove the upper limit on number of descriptors in a dirserver's
27099 directory (not that we were anywhere close).
27100 - Allow multiple logfiles at different severity ranges.
27101 - Allow *BindAddress to specify ":port" rather than setting *Port
27102 separately. Allow multiple instances of each BindAddress config
27103 option, so you can bind to multiple interfaces if you want.
27104 - Allow multiple exit policy lines, which are processed in order.
27105 Now we don't need that huge line with all the commas in it.
27106 - Enable accept/reject policies on SOCKS connections, so you can bind
27107 to 0.0.0.0 but still control who can use your OP.
27108 - Updated the man page to reflect these features.
27111 Changes in version 0.0.6.2 - 2004-05-16
27112 o Our integrity-checking digest was checking only the most recent cell,
27113 not the previous cells like we'd thought.
27114 Thanks to Stefan Mark for finding the flaw!
27117 Changes in version 0.0.6.1 - 2004-05-06
27118 o Fix two bugs in our AES counter-mode implementation (this affected
27119 onion-level stream encryption, but not TLS-level). It turns
27120 out we were doing something much more akin to a 16-character
27121 polyalphabetic cipher. Oops.
27122 Thanks to Stefan Mark for finding the flaw!
27123 o Retire moria3 as a directory server, and add tor26 as a directory
27127 Changes in version 0.0.6 - 2004-05-02
27129 - Hidden services and rendezvous points are implemented. Go to
27130 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
27131 hidden services. (This only works via a socks4a proxy such as
27132 Privoxy, and currently it's quite slow.)
27133 - We now rotate link (tls context) keys and onion keys.
27134 - CREATE cells now include oaep padding, so you can tell
27135 if you decrypted them correctly.
27136 - Retry stream correctly when we fail to connect because of
27137 exit-policy-reject (should try another) or can't-resolve-address.
27138 - When we hup a dirserver and we've *removed* a server from the
27139 approved-routers list, now we remove that server from the
27140 in-memory directories too.
27141 - Add bandwidthburst to server descriptor.
27142 - Directories now say which dirserver signed them.
27143 - Use a tor_assert macro that logs failed assertions too.
27144 - Since we don't support truncateds much, don't bother sending them;
27145 just close the circ.
27146 - Fetch randomness from /dev/urandom better (not via fopen/fread)
27147 - Better debugging for tls errors
27148 - Set Content-Type on the directory and hidserv descriptor.
27149 - Remove IVs from cipher code, since AES-ctr has none.
27151 - Fix an assert trigger for exit nodes that's been plaguing us since
27152 the days of 0.0.2prexx (thanks weasel!)
27153 - Fix a bug where we were closing tls connections intermittently.
27154 It turns out openssl keeps its errors around -- so if an error
27155 happens, and you don't ask about it, and then another openssl
27156 operation happens and succeeds, and you ask if there was an error,
27157 it tells you about the first error.
27158 - Fix a bug that's been lurking since 27 may 03 (!)
27159 When passing back a destroy cell, we would use the wrong circ id.
27160 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
27161 - Some versions of openssl have an SSL_pending function that erroneously
27162 returns bytes when there is a non-application record pending.
27163 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
27164 o We were using an array of length zero in a few places.
27165 o Win32's gethostbyname can't resolve an IP to an IP.
27166 o Win32's close can't close a socket.
27167 o Handle windows socket errors correctly.
27169 - check for <sys/limits.h> so we build on FreeBSD again, and
27170 <machine/limits.h> for NetBSD.
27173 Changes in version 0.0.5 - 2004-03-30
27174 o Install torrc as torrc.sample -- we no longer clobber your
27176 o Fix mangled-state bug in directory fetching (was causing sigpipes).
27177 o Only build circuits after we've fetched the directory: clients were
27178 using only the directory servers before they'd fetched a directory.
27179 This also means longer startup time; so it goes.
27180 o Fix an assert trigger where an OP would fail to handshake, and we'd
27181 expect it to have a nickname.
27182 o Work around a tsocks bug: do a socks reject when AP connection dies
27183 early, else tsocks goes into an infinite loop.
27184 o Hold socks connection open until reply is flushed (if possible)
27185 o Make exit nodes resolve IPs to IPs immediately, rather than asking
27186 the dns farm to do it.
27187 o Fix c99 aliasing warnings in rephist.c
27188 o Don't include server descriptors that are older than 24 hours in the
27190 o Give socks 'reject' replies their whole 15s to attempt to flush,
27191 rather than seeing the 60s timeout and assuming the flush had failed.
27192 o Clean automake droppings from the cvs repository
27193 o Add in a 'notice' log level for things the operator should hear
27194 but that aren't warnings
27197 Changes in version 0.0.4 - 2004-03-26
27198 o When connecting to a dirserver or OR and the network is down,
27202 Changes in version 0.0.3 - 2004-03-26
27203 o Warn and fail if server chose a nickname with illegal characters
27204 o Port to Solaris and Sparc:
27205 - include missing header fcntl.h
27206 - have autoconf find -lsocket -lnsl automatically
27207 - deal with hardware word alignment
27208 - make uname() work (solaris has a different return convention)
27209 - switch from using signal() to sigaction()
27210 o Preliminary work on reputation system:
27211 - Keep statistics on success/fail of connect attempts; they're published
27212 by kill -USR1 currently.
27213 - Add a RunTesting option to try to learn link state by creating test
27214 circuits, even when SocksPort is off.
27215 - Remove unused open circuits when there are too many.
27218 Changes in version 0.0.2 - 2004-03-19
27219 - Include strlcpy and strlcat for safer string ops
27220 - define INADDR_NONE so we compile (but still not run) on solaris
27223 Changes in version 0.0.2pre27 - 2004-03-14
27225 - Allow internal tor networks (we were rejecting internal IPs,
27226 now we allow them if they're set explicitly).
27227 - And fix a few endian issues.
27230 Changes in version 0.0.2pre26 - 2004-03-14
27232 - If a stream times out after 15s without a connected cell, don't
27233 try that circuit again: try a new one.
27234 - Retry streams at most 4 times. Then give up.
27235 - When a dirserver gets a descriptor from an unknown router, it
27236 logs its fingerprint (so the dirserver operator can choose to
27237 accept it even without mail from the server operator).
27238 - Inform unapproved servers when we reject their descriptors.
27239 - Make tor build on Windows again. It works as a client, who knows
27241 - Clearer instructions in the torrc for how to set up a server.
27242 - Be more efficient about reading fd's when our global token bucket
27243 (used for rate limiting) becomes empty.
27245 - Stop asserting that computers always go forward in time. It's
27247 - When we sent a cell (e.g. destroy) and then marked an OR connection
27248 expired, we might close it before finishing a flush if the other
27249 side isn't reading right then.
27250 - Don't allow dirservers to start if they haven't defined
27251 RecommendedVersions
27252 - We were caching transient dns failures. Oops.
27253 - Prevent servers from publishing an internal IP as their address.
27254 - Address a strcat vulnerability in circuit.c
27257 Changes in version 0.0.2pre25 - 2004-03-04
27259 - Put the OR's IP in its router descriptor, not its fqdn. That way
27260 we'll stop being stalled by gethostbyname for nodes with flaky dns,
27263 - If the user typed in an address that didn't resolve, the server
27267 Changes in version 0.0.2pre24 - 2004-03-03
27269 - Fix an assertion failure in dns.c, where we were trying to dequeue
27270 a pending dns resolve even if it wasn't pending
27271 - Fix a spurious socks5 warning about still trying to write after the
27272 connection is finished.
27273 - Hold certain marked_for_close connections open until they're finished
27274 flushing, rather than losing bytes by closing them too early.
27275 - Correctly report the reason for ending a stream
27276 - Remove some duplicate calls to connection_mark_for_close
27277 - Put switch_id and start_daemon earlier in the boot sequence, so it
27278 will actually try to chdir() to options.DataDirectory
27279 - Make 'make test' exit(1) if a test fails; fix some unit tests
27280 - Make tor fail when you use a config option it doesn't know about,
27281 rather than warn and continue.
27282 - Make --version work
27283 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
27286 Changes in version 0.0.2pre23 - 2004-02-29
27288 - Print a statement when the first circ is finished, so the user
27289 knows it's working.
27290 - If a relay cell is unrecognized at the end of the circuit,
27291 send back a destroy. (So attacks to mutate cells are more
27293 - New config option 'excludenodes' to avoid certain nodes for circuits.
27294 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
27295 so you can collect coredumps there.
27297 - Fix a bug in tls flushing where sometimes data got wedged and
27298 didn't flush until more data got sent. Hopefully this bug was
27299 a big factor in the random delays we were seeing.
27300 - Make 'connected' cells include the resolved IP, so the client
27301 dns cache actually gets populated.
27302 - Disallow changing from ORPort=0 to ORPort>0 on hup.
27303 - When we time-out on a stream and detach from the circuit, send an
27304 end cell down it first.
27305 - Only warn about an unknown router (in exitnodes, entrynodes,
27306 excludenodes) after we've fetched a directory.
27309 Changes in version 0.0.2pre22 - 2004-02-26
27311 - Servers publish less revealing uname information in descriptors.
27312 - More memory tracking and assertions, to crash more usefully when
27314 - If the default torrc isn't there, just use some default defaults.
27315 Plus provide an internal dirservers file if they don't have one.
27316 - When the user tries to use Tor as an http proxy, give them an http
27317 501 failure explaining that we're a socks proxy.
27318 - Dump a new router.desc on hup, to help confused people who change
27319 their exit policies and then wonder why router.desc doesn't reflect
27321 - Clean up the generic tor.sh init script that we ship with.
27323 - If the exit stream is pending on the resolve, and a destroy arrives,
27324 then the stream wasn't getting removed from the pending list. I
27325 think this was the one causing recent server crashes.
27326 - Use a more robust poll on OSX 10.3, since their poll is flaky.
27327 - When it couldn't resolve any dirservers, it was useless from then on.
27328 Now it reloads the RouterFile (or default dirservers) if it has no
27330 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
27331 many users don't even *have* a /usr/local/sbin/.
27334 Changes in version 0.0.2pre21 - 2004-02-18
27336 - There's a ChangeLog file that actually reflects the changelog.
27337 - There's a 'torify' wrapper script, with an accompanying
27338 tor-tsocks.conf, that simplifies the process of using tsocks for
27339 tor. It even has a man page.
27340 - The tor binary gets installed to sbin rather than bin now.
27341 - Retry streams where the connected cell hasn't arrived in 15 seconds
27342 - Clean up exit policy handling -- get the default out of the torrc,
27343 so we can update it without forcing each server operator to fix
27345 - Allow imaps and pop3s in default exit policy
27347 - Prevent picking middleman nodes as the last node in the circuit
27350 Changes in version 0.0.2pre20 - 2004-01-30
27352 - We now have a deb package, and it's in debian unstable. Go to
27353 it, apt-getters. :)
27354 - I've split the TotalBandwidth option into BandwidthRate (how many
27355 bytes per second you want to allow, long-term) and
27356 BandwidthBurst (how many bytes you will allow at once before the cap
27357 kicks in). This better token bucket approach lets you, say, set
27358 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
27359 performance while not exceeding your monthly bandwidth quota.
27360 - Push out a tls record's worth of data once you've got it, rather
27361 than waiting until you've read everything waiting to be read. This
27362 may improve performance by pipelining better. We'll see.
27363 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
27364 from failed circuits (if they haven't been connected yet) and attach
27366 - Expire old streams that haven't managed to connect. Some day we'll
27367 have them reattach to new circuits instead.
27370 - Fix several memory leaks that were causing servers to become bloated
27372 - Fix a few very rare assert triggers. A few more remain.
27373 - Setuid to User _before_ complaining about running as root.
27376 Changes in version 0.0.2pre19 - 2004-01-07
27378 - Fix deadlock condition in dns farm. We were telling a child to die by
27379 closing the parent's file descriptor to him. But newer children were
27380 inheriting the open file descriptor from the parent, and since they
27381 weren't closing it, the socket never closed, so the child never read
27382 eof, so he never knew to exit. Similarly, dns workers were holding
27383 open other sockets, leading to all sorts of chaos.
27384 - New cleaner daemon() code for forking and backgrounding.
27385 - If you log to a file, it now prints an entry at the top of the
27386 logfile so you know it's working.
27387 - The onionskin challenge length was 30 bytes longer than necessary.
27388 - Started to patch up the spec so it's not quite so out of date.
27391 Changes in version 0.0.2pre18 - 2004-01-02
27393 - Fix endian issues with the 'integrity' field in the relay header.
27394 - Fix a potential bug where connections in state
27395 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
27398 Changes in version 0.0.2pre17 - 2003-12-30
27400 - Made --debuglogfile (or any second log file, actually) work.
27401 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
27402 adversary could force us into an infinite loop.
27405 - Each onionskin handshake now includes a hash of the computed key,
27406 to prove the server's identity and help perfect forward secrecy.
27407 - Changed cell size from 256 to 512 bytes (working toward compatibility
27409 - Changed cell length to 2 bytes, and moved it to the relay header.
27410 - Implemented end-to-end integrity checking for the payloads of
27412 - Separated streamid from 'recognized' (otherwise circuits will get
27413 messed up when we try to have streams exit from the middle). We
27414 use the integrity-checking to confirm that a cell is addressed to
27416 - Randomize the initial circid and streamid values, so an adversary who
27417 breaks into a node can't learn how many circuits or streams have
27421 Changes in version 0.0.2pre16 - 2003-12-14
27423 - Fixed a bug that made HUP trigger an assert
27424 - Fixed a bug where a circuit that immediately failed wasn't being
27425 counted as a failed circuit in counting retries.
27428 - Now we close the circuit when we get a truncated cell: otherwise we're
27429 open to an anonymity attack where a bad node in the path truncates
27430 the circuit and then we open streams at him.
27431 - Add port ranges to exit policies
27432 - Add a conservative default exit policy
27433 - Warn if you're running tor as root
27434 - on HUP, retry OR connections and close/rebind listeners
27435 - options.EntryNodes: try these nodes first when picking the first node
27436 - options.ExitNodes: if your best choices happen to include any of
27437 your preferred exit nodes, you choose among just those preferred
27439 - options.ExcludedNodes: nodes that are never picked in path building
27442 Changes in version 0.0.2pre15 - 2003-12-03
27443 o Robustness and bugfixes:
27444 - Sometimes clients would cache incorrect DNS resolves, which would
27445 really screw things up.
27446 - An OP that goes offline would slowly leak all its sockets and stop
27448 - A wide variety of bugfixes in exit node selection, exit policy
27449 handling, and processing pending streams when a new circuit is
27451 - Pick nodes for a path only from those the directory says are up
27452 - Choose randomly from all running dirservers, not always the first one
27453 - Increase allowed http header size for directory fetch.
27454 - Stop writing to stderr (if we're daemonized it will be closed).
27455 - Enable -g always, so cores will be more useful to me.
27456 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
27459 - Wrote a man page. It lists commonly used options.
27462 - Change default loglevel to warn.
27463 - Make PidFile default to null rather than littering in your CWD.
27464 - OnionRouter config option is now obsolete. Instead it just checks
27466 - Moved to a single unified torrc file for both clients and servers.
27469 Changes in version 0.0.2pre14 - 2003-11-29
27470 o Robustness and bugfixes:
27471 - Force the admin to make the DataDirectory himself
27472 - to get ownership/permissions right
27473 - so clients no longer make a DataDirectory and then never use it
27474 - fix bug where a client who was offline for 45 minutes would never
27475 pull down a directory again
27476 - fix (or at least hide really well) the dns assert bug that was
27477 causing server crashes
27478 - warnings and improved robustness wrt clockskew for certs
27479 - use the native daemon(3) to daemonize, when available
27480 - exit if bind() fails
27481 - exit if neither socksport nor orport is defined
27482 - include our own tor_timegm (Win32 doesn't have its own)
27483 - bugfix for win32 with lots of connections
27484 - fix minor bias in PRNG
27485 - make dirserver more robust to corrupt cached directory
27488 - Wrote the design document (woo)
27490 o Circuit building and exit policies:
27491 - Circuits no longer try to use nodes that the directory has told them
27493 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
27494 bitcounts (18.0.0.0/8).
27495 - Make AP connections standby for a circuit if no suitable circuit
27496 exists, rather than failing
27497 - Circuits choose exit node based on addr/port, exit policies, and
27498 which AP connections are standing by
27499 - Bump min pathlen from 2 to 3
27500 - Relay end cells have a payload to describe why the stream ended.
27501 - If the stream failed because of exit policy, try again with a new
27503 - Clients have a dns cache to remember resolved addresses.
27504 - Notice more quickly when we have no working circuits
27507 - APPort is now called SocksPort
27508 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
27510 - RecommendedVersions is now a config variable rather than
27511 hardcoded (for dirservers)
27512 - Reloads config on HUP
27513 - Usage info on -h or --help
27514 - If you set User and Group config vars, it'll setu/gid to them.
27516 Changes in version 0.0.2pre13 - 2003-10-19
27517 o General stability:
27518 - SSL_write no longer fails when it returns WANTWRITE and the number
27519 of bytes in the buf has changed by the next SSL_write call.
27520 - Fix segfault fetching directory when network is down
27521 - Fix a variety of minor memory leaks
27522 - Dirservers reload the fingerprints file on HUP, so I don't have
27523 to take down the network when I approve a new router
27524 - Default server config file has explicit Address line to specify fqdn
27527 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
27528 - Make listener connections not ever alloc bufs
27530 o Autoconf improvements:
27531 - don't clobber an external CFLAGS in ./configure
27532 - Make install now works
27533 - create var/lib/tor on make install
27534 - autocreate a tor.sh initscript to help distribs
27535 - autocreate the torrc and sample-server-torrc with correct paths
27537 o Log files and Daemonizing now work:
27538 - If --DebugLogFile is specified, log to it at -l debug
27539 - If --LogFile is specified, use it instead of commandline
27540 - If --RunAsDaemon is set, tor forks and backgrounds on startup