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.6.8 - 2021-10-26
6 This version fixes several bugs from earlier versions of Tor. One
7 highlight is a fix on how we track DNS timeouts to report general
10 o Major bugfixes (relay, overload state):
11 - Relays report the general overload state for DNS timeout errors
12 only if X% of all DNS queries over Y seconds are errors. Before
13 that, it only took 1 timeout to report the overload state which
14 was just too low of a threshold. The X and Y values are 1% and 10
15 minutes respectively but they are also controlled by consensus
16 parameters. Fixes bug 40491; bugfix on 0.4.6.1-alpha.
18 o Minor features (fallbackdir):
19 - Regenerate fallback directories for October 2021. Closes
22 o Minor features (testing):
23 - On a testing network, relays can now use the
24 TestingMinTimeToReportBandwidth option to change the smallest
25 amount of time over which they're willing to report their observed
26 maximum bandwidth. Previously, this was fixed at 1 day. For
27 safety, values under 2 hours are only supported on testing
28 networks. Part of a fix for ticket 40337.
29 - Relays on testing networks no longer rate-limit how frequently
30 they are willing to report new bandwidth measurements. Part of a
32 - Relays on testing networks now report their observed bandwidths
33 immediately from startup. Previously, they waited until they had
34 been running for a full day. Closes ticket 40337.
36 o Minor bugfix (onion service):
37 - Do not flag an HSDir as non-running in case the descriptor upload
38 or fetch fails. An onion service closes pending directory
39 connections before uploading a new descriptor which can thus lead
40 to wrongly flagging many relays and thus affecting circuit building
41 path selection. Fixes bug 40434; bugfix on 0.2.0.13-alpha.
42 - Improve logging when a bad HS version is given. Fixes bug 40476;
43 bugfix on 0.4.6.1-alpha.
45 o Minor bugfix (CI, onion service):
46 - Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500;
47 bugfix on 0.3.2.1-alpha.
49 o Minor bugfixes (compatibility):
50 - Fix compatibility with the most recent Libevent versions, which no
51 longer have an evdns_set_random_bytes() function. Because this
52 function has been a no-op since Libevent 2.0.4-alpha, it is safe
53 for us to just stop calling it. Fixes bug 40371; bugfix
56 o Minor bugfixes (onion service, TROVE-2021-008):
57 - Only log v2 access attempts once total, in order to not pollute
58 the logs with warnings and to avoid recording the times on disk
59 when v2 access was attempted. Note that the onion address was
60 _never_ logged. This counts as a Low-severity security issue.
61 Fixes bug 40474; bugfix on 0.4.5.8.
64 Changes in version 0.4.5.11 - 2021-10-26
65 The major change in this version is that v2 onion services are now
66 disabled at the client, service, and relay: any Tor nodes running this
67 version and onward will stop supporting v2 onion services. This is the
68 last step in the long deprecation process of v2 onion services.
69 Everyone running an earlier version, whether as a client, a relay, or
70 an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11,
73 o Major feature (onion service v2):
74 - See https://blog.torproject.org/v2-deprecation-timeline for
75 details on how to transition from v2 to v3.
76 - The control port commands HSFETCH and HSPOST no longer allow
77 version 2, and it is no longer possible to create a v2 service
79 - Tor no longer allows creating v2 services, or connecting as a
80 client to a v2 service. Relays will decline to be a v2 HSDir or
81 introduction point. This effectively disables onion service
82 version 2 Tor-wide. Closes ticket 40476.
84 o Minor features (bridge, backport from 0.4.6.8):
85 - We now announce the URL to Tor's new bridge status at
86 https://bridges.torproject.org/ when Tor is configured to run as a
87 bridge relay. Closes ticket 30477.
89 o Minor features (fallbackdir):
90 - Regenerate fallback directories for October 2021. Closes
93 o Minor features (logging, diagnostic, backport from 0.4.6.5):
94 - Log decompression failures at a higher severity level, since they
95 can help provide missing context for other warning messages. We
96 rate-limit these messages, to avoid flooding the logs if they
97 begin to occur frequently. Closes ticket 40175.
99 o Minor features (testing, backport from 0.4.6.8):
100 - On a testing network, relays can now use the
101 TestingMinTimeToReportBandwidth option to change the smallest
102 amount of time over which they're willing to report their observed
103 maximum bandwidth. Previously, this was fixed at 1 day. For
104 safety, values under 2 hours are only supported on testing
105 networks. Part of a fix for ticket 40337.
106 - Relays on testing networks no longer rate-limit how frequently
107 they are willing to report new bandwidth measurements. Part of a
108 fix for ticket 40337.
109 - Relays on testing networks now report their observed bandwidths
110 immediately from startup. Previously, they waited until they had
111 been running for a full day. Closes ticket 40337.
113 o Minor bugfix (CI, onion service):
114 - Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500;
115 bugfix on 0.3.2.1-alpha.
117 o Minor bugfix (onion service, backport from 0.4.6.8):
118 - Do not flag an HSDir as non-running in case the descriptor upload
119 or fetch fails. An onion service closes pending directory
120 connections before uploading a new descriptor which can thus lead
121 to wrongly flagging many relays and thus affecting circuit building
122 path selection. Fixes bug 40434; bugfix on 0.2.0.13-alpha.
124 o Minor bugfixes (compatibility, backport from 0.4.6.8):
125 - Fix compatibility with the most recent Libevent versions, which no
126 longer have an evdns_set_random_bytes() function. Because this
127 function has been a no-op since Libevent 2.0.4-alpha, it is safe
128 for us to just stop calling it. Fixes bug 40371; bugfix
131 o Minor bugfixes (consensus handling, backport from 0.4.6.4-rc):
132 - Avoid a set of bugs that could be caused by inconsistently
133 preferring an out-of-date consensus stored in a stale directory
134 cache over a more recent one stored on disk as the latest
135 consensus. Fixes bug 40375; bugfix on 0.3.1.1-alpha.
137 o Minor bugfixes (onion service, TROVE-2021-008, backport from 0.4.6.8):
138 - Only log v2 access attempts once total, in order to not pollute
139 the logs with warnings and to avoid recording the times on disk
140 when v2 access was attempted. Note that the onion address was
141 _never_ logged. This counts as a Low-severity security issue.
142 Fixes bug 40474; bugfix on 0.4.5.8.
145 Changes in version 0.3.5.17 - 2021-10-26
146 The major change in this version is that v2 onion services are now
147 disabled at the client, service, and relay: any Tor nodes running this
148 version and onward will stop supporting v2 onion services. This is the
149 last step in the long deprecation process of v2 onion services.
150 Everyone running an earlier version, whether as a client, a relay, or
151 an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11,
154 o Major feature (onion service v2, backport from 0.4.5.11):
155 - See https://blog.torproject.org/v2-deprecation-timeline for
156 details on how to transition from v2 to v3.
157 - The control port commands HSFETCH and HSPOST no longer allow
158 version 2, and it is no longer possible to create a v2 service
160 - Tor no longer allows creating v2 services, or connecting as a
161 client to a v2 service. Relays will decline to be a v2 HSDir or
162 introduction point. This effectively disables onion service
163 version 2 Tor-wide. Closes ticket 40476.
165 o Minor features (bridge, backport from 0.4.6.8):
166 - We now announce the URL to Tor's new bridge status at
167 https://bridges.torproject.org/ when Tor is configured to run as a
168 bridge relay. Closes ticket 30477.
170 o Minor features (fallbackdir):
171 - Regenerate fallback directories for October 2021. Closes
174 o Minor bugfixes (compatibility, backport from 0.4.6.8):
175 - Fix compatibility with the most recent Libevent versions, which no
176 longer have an evdns_set_random_bytes() function. Because this
177 function has been a no-op since Libevent 2.0.4-alpha, it is safe
178 for us to just stop calling it. Fixes bug 40371; bugfix
182 Changes in version 0.4.6.7 - 2021-08-16
183 This version fixes several bugs from earlier versions of Tor, including one
184 that could lead to a denial-of-service attack. Everyone running an earlier
185 version, whether as a client, a relay, or an onion service, should upgrade
186 to Tor 0.3.5.16, 0.4.5.10, or 0.4.6.7.
188 o Major bugfixes (cryptography, security):
189 - Resolve an assertion failure caused by a behavior mismatch between our
190 batch-signature verification code and our single-signature verification
191 code. This assertion failure could be triggered remotely, leading to a
192 denial of service attack. We fix this issue by disabling batch
193 verification. Fixes bug 40078; bugfix on 0.2.6.1-alpha. This issue is
194 also tracked as TROVE-2021-007 and CVE-2021-38385. Found by Henry de
197 o Minor feature (fallbackdir):
198 - Regenerate fallback directories list. Close ticket 40447.
200 o Minor features (geoip data):
201 - Update the geoip files to match the IPFire Location Database,
202 as retrieved on 2021/08/12.
204 o Minor bugfix (crypto):
205 - Disable the unused batch verification feature of ed25519-donna. Fixes
206 bug 40078; bugfix on 0.2.6.1-alpha. Found by Henry de Valence.
208 o Minor bugfixes (onion service):
209 - Send back the extended SOCKS error 0xF6 (Onion Service Invalid Address)
210 for a v2 onion address. Fixes bug 40421; bugfix on 0.4.6.2-alpha.
212 o Minor bugfix (CI, onion service):
213 - Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500;
214 bugfix on 0.3.2.1-alpha.
216 o Minor bugfixes (relay):
217 - Reduce the compression level for data streaming from HIGH to LOW in
218 order to reduce CPU load on the directory relays. Fixes bug 40301;
219 bugfix on 0.3.5.1-alpha.
221 o Minor bugfixes (timekeeping):
222 - Calculate the time of day correctly on systems where the time_t
223 type includes leap seconds. (This is not the case on most
224 operating systems, but on those where it occurs, our tor_timegm
225 function did not correctly invert the system's gmtime function,
226 which could result in assertion failures when calculating
227 voting schedules.) Fixes bug 40383; bugfix on 0.2.0.3-alpha.
230 Changes in version 0.4.5.10 - 2021-08-16
231 This version fixes several bugs from earlier versions of Tor, including one
232 that could lead to a denial-of-service attack. Everyone running an earlier
233 version, whether as a client, a relay, or an onion service, should upgrade
234 to Tor 0.3.5.16, 0.4.5.10, or 0.4.6.7.
236 o Major bugfixes (cryptography, security):
237 - Resolve an assertion failure caused by a behavior mismatch between our
238 batch-signature verification code and our single-signature verification
239 code. This assertion failure could be triggered remotely, leading to a
240 denial of service attack. We fix this issue by disabling batch
241 verification. Fixes bug 40078; bugfix on 0.2.6.1-alpha. This issue is
242 also tracked as TROVE-2021-007 and CVE-2021-38385. Found by Henry de
245 o Minor feature (fallbackdir):
246 - Regenerate fallback directories list. Close ticket 40447.
248 o Minor features (geoip data):
249 - Update the geoip files to match the IPFire Location Database,
250 as retrieved on 2021/08/12.
252 o Minor features (testing):
253 - Enable the deterministic RNG for unit tests that covers the address set
254 bloomfilter-based API's. Fixes bug 40419; bugfix on 0.3.3.2-alpha.
256 o Minor bugfix (crypto):
257 - Disable the unused batch verification feature of ed25519-donna. Fixes
258 bug 40078; bugfix on 0.2.6.1-alpha. Found by Henry de Valence.
260 o Minor bugfixes (relay, backport from 0.4.6.x):
261 - Reduce the compression level for data streaming from HIGH to LOW. Fixes
262 bug 40301; bugfix on 0.3.5.1-alpha.
264 o Minor bugfixes (timekeeping, backport from 0.4.6.x):
265 - Calculate the time of day correctly on systems where the time_t
266 type includes leap seconds. (This is not the case on most
267 operating systems, but on those where it occurs, our tor_timegm
268 function did not correctly invert the system's gmtime function,
269 which could result in assertion failures when calculating
270 voting schedules.) Fixes bug 40383; bugfix on 0.2.0.3-alpha.
272 o Minor bugfixes (warnings, portability, backport from 0.4.6.x):
273 - Suppress a strict-prototype warning when building with some versions
274 of NSS. Fixes bug 40409; bugfix on 0.3.5.1-alpha.
277 Changes in version 0.3.5.16 - 2021-08-16
278 This version fixes several bugs from earlier versions of Tor, including one
279 that could lead to a denial-of-service attack. Everyone running an earlier
280 version, whether as a client, a relay, or an onion service, should upgrade
281 to Tor 0.3.5.16, 0.4.5.10, or 0.4.6.7.
283 o Major bugfixes (cryptography, security):
284 - Resolve an assertion failure caused by a behavior mismatch between our
285 batch-signature verification code and our single-signature verification
286 code. This assertion failure could be triggered remotely, leading to a
287 denial of service attack. We fix this issue by disabling batch
288 verification. Fixes bug 40078; bugfix on 0.2.6.1-alpha. This issue is
289 also tracked as TROVE-2021-007 and CVE-2021-38385. Found by Henry de
292 o Minor feature (fallbackdir):
293 - Regenerate fallback directories list. Close ticket 40447.
295 o Minor features (geoip data):
296 - Update the geoip files to match the IPFire Location Database,
297 as retrieved on 2021/08/12.
299 o Minor bugfix (crypto):
300 - Disable the unused batch verification feature of ed25519-donna. Fixes
301 bug 40078; bugfix on 0.2.6.1-alpha. Found by Henry de Valence.
303 o Minor bugfixes (relay, backport from 0.4.6.x):
304 - Reduce the compression level for data streaming from HIGH to LOW. Fixes
305 bug 40301; bugfix on 0.3.5.1-alpha.
308 Changes in version 0.4.6.6 - 2021-06-30
309 Tor 0.4.6.6 makes several small fixes on 0.4.6.5, including one that
310 allows Tor to build correctly on older versions of GCC. You should
311 upgrade to this version if you were having trouble building Tor
312 0.4.6.5; otherwise, there is probably no need.
314 o Minor bugfixes (compilation):
315 - Fix a compilation error when trying to build Tor with a compiler
316 that does not support const variables in static initializers.
317 Fixes bug 40410; bugfix on 0.4.6.5.
318 - Suppress a strict-prototype warning when building with some
319 versions of NSS. Fixes bug 40409; bugfix on 0.3.5.1-alpha.
321 o Minor bugfixes (testing):
322 - Enable the deterministic RNG for unit tests that covers the
323 address set bloomfilter-based API's. Fixes bug 40419; bugfix
327 Changes in version 0.4.6.5 - 2021-06-14
328 Tor 0.4.6.5 is the first stable release in its series. The 0.4.6.x
329 series includes numerous features and bugfixes, including a significant
330 improvement to our circuit timeout algorithm that should improve
331 observed client performance, and a way for relays to report when they are
334 This release also includes security fixes for several security issues,
335 including a denial-of-service attack against onion service clients,
336 and another denial-of-service attack against relays. Everybody should
337 upgrade to one of 0.3.5.15, 0.4.4.9, 0.4.5.9, or 0.4.6.5.
339 Below are the changes since 0.4.5.8. For a list of changes since
340 0.4.6.4-rc, see the ChangeLog file.
342 o Major bugfixes (security):
343 - Don't allow relays to spoof RELAY_END or RELAY_RESOLVED cell on
344 half-closed streams. Previously, clients failed to validate which
345 hop sent these cells: this would allow a relay on a circuit to end
346 a stream that wasn't actually built with it. Fixes bug 40389;
347 bugfix on 0.3.5.1-alpha. This issue is also tracked as TROVE-2021-
348 003 and CVE-2021-34548.
350 o Major bugfixes (security, defense-in-depth):
351 - Detect more failure conditions from the OpenSSL RNG code.
352 Previously, we would detect errors from a missing RNG
353 implementation, but not failures from the RNG code itself.
354 Fortunately, it appears those failures do not happen in practice
355 when Tor is using OpenSSL's default RNG implementation. Fixes bug
356 40390; bugfix on 0.2.8.1-alpha. This issue is also tracked as
357 TROVE-2021-004. Reported by Jann Horn at Google's Project Zero.
359 o Major bugfixes (security, denial of service):
360 - Resist a hashtable-based CPU denial-of-service attack against
361 relays. Previously we used a naive unkeyed hash function to look
362 up circuits in a circuitmux object. An attacker could exploit this
363 to construct circuits with chosen circuit IDs, to create
364 collisions and make the hash table inefficient. Now we use a
365 SipHash construction here instead. Fixes bug 40391; bugfix on
366 0.2.4.4-alpha. This issue is also tracked as TROVE-2021-005 and
367 CVE-2021-34549. Reported by Jann Horn from Google's Project Zero.
368 - Fix an out-of-bounds memory access in v3 onion service descriptor
369 parsing. An attacker could exploit this bug by crafting an onion
370 service descriptor that would crash any client that tried to visit
371 it. Fixes bug 40392; bugfix on 0.3.0.1-alpha. This issue is also
372 tracked as TROVE-2021-006 and CVE-2021-34550. Reported by Sergei
373 Glazunov from Google's Project Zero.
375 o Major features (control port, onion services):
376 - Add controller support for creating version 3 onion services with
377 client authorization. Previously, only v2 onion services could be
378 created with client authorization. Closes ticket 40084. Patch by
381 o Major features (directory authority):
382 - When voting on a relay with a Sybil-like appearance, add the Sybil
383 flag when clearing out the other flags. This lets a relay operator
384 know why their relay hasn't been included in the consensus. Closes
385 ticket 40255. Patch by Neel Chauhan.
387 o Major features (metrics):
388 - Relays now report how overloaded they are in their extrainfo
389 documents. This information is controlled with the
390 OverloadStatistics torrc option, and it will be used to improve
391 decisions about the network's load balancing. Implements proposal
392 328; closes ticket 40222.
394 o Major features (relay, denial of service):
395 - Add a new DoS subsystem feature to control the rate of client
396 connections for relays. Closes ticket 40253.
398 o Major features (statistics):
399 - Relays now publish statistics about the number of v3 onion
400 services and volume of v3 onion service traffic, in the same
401 manner they already do for v2 onions. Closes ticket 23126.
403 o Major bugfixes (circuit build timeout):
404 - Improve the accuracy of our circuit build timeout calculation for
405 60%, 70%, and 80% build rates for various guard choices. We now
406 use a maximum likelihood estimator for Pareto parameters of the
407 circuit build time distribution, instead of a "right-censored
408 estimator". This causes clients to ignore circuits that never
409 finish building in their timeout calculations. Previously, clients
410 were counting such unfinished circuits as having the highest
411 possible build time value, when in reality these circuits most
412 likely just contain relays that are offline. We also now wait a
413 bit longer to let circuits complete for measurement purposes,
414 lower the minimum possible effective timeout from 1.5 seconds to
415 10ms, and increase the resolution of the circuit build time
416 histogram from 50ms bin widths to 10ms bin widths. Additionally,
417 we alter our estimate Xm by taking the maximum of the top 10 most
418 common build time values of the 10ms histogram, and compute Xm as
419 the average of these. Fixes bug 40168; bugfix on 0.2.2.14-alpha.
420 - Remove max_time calculation and associated warning from circuit
421 build timeout 'alpha' parameter estimation, as this is no longer
422 needed by our new estimator from 40168. Fixes bug 34088; bugfix
425 o Major bugfixes (signing key):
426 - In the tor-gencert utility, give an informative error message if
427 the passphrase given in `--create-identity-key` is too short.
428 Fixes bug 40189; bugfix on 0.2.0.1-alpha. Patch by Neel Chauhan.
430 o Minor features (bridge):
431 - We now announce the URL to Tor's new bridge status at
432 https://bridges.torproject.org/ when Tor is configured to run as a
433 bridge relay. Closes ticket 30477.
435 o Minor features (build system):
436 - New "make lsp" command to auto generate the compile_commands.json
437 file used by the ccls server. The "bear" program is needed for
438 this. Closes ticket 40227.
440 o Minor features (client):
441 - Clients now check whether their streams are attempting to re-enter
442 the Tor network (i.e. to send Tor traffic over Tor), and close
443 them preemptively if they think exit relays will refuse them for
444 this reason. See ticket 2667 for details. Closes ticket 40271.
446 o Minor features (command line):
447 - Add long format name "--torrc-file" equivalent to the existing
448 command-line option "-f". Closes ticket 40324. Patch by
451 o Minor features (command-line interface):
452 - Add build informations to `tor --version` in order to ease
453 reproducible builds. Closes ticket 32102.
454 - When parsing command-line flags that take an optional argument,
455 treat the argument as absent if it would start with a '-'
456 character. Arguments in that form are not intelligible for any of
457 our optional-argument flags. Closes ticket 40223.
458 - Allow a relay operator to list the ed25519 keys on the command
459 line by adding the `rsa` and `ed25519` arguments to the
460 --list-fingerprint flag to show the respective RSA and ed25519
461 relay fingerprint. Closes ticket 33632. Patch by Neel Chauhan.
463 o Minor features (compatibility):
464 - Remove an assertion function related to TLS renegotiation. It was
465 used nowhere outside the unit tests, and it was breaking
466 compilation with recent alpha releases of OpenSSL 3.0.0. Closes
469 o Minor features (control port, stream handling):
470 - Add the stream ID to the event line in the ADDRMAP control event.
471 Closes ticket 40249. Patch by Neel Chauhan.
473 o Minor features (dormant mode):
474 - Add a new 'DormantTimeoutEnabled' option to allow coarse-grained
475 control over whether the client ever becomes dormant from
476 inactivity. Most people won't need this. Closes ticket 40228.
477 - Add a new 'DormantTimeoutEnabled' option for coarse-grained
478 control over whether the client can become dormant from
479 inactivity. Most people won't need this. Closes ticket 40228.
481 o Minor features (geoip data):
482 - Update the geoip files to match the IPFire Location Database, as
483 retrieved on 2021/06/10.
485 o Minor features (logging):
486 - Edit heartbeat log messages so that more of them begin with the
487 string "Heartbeat: ". Closes ticket 40322; patch
489 - Change the DoS subsystem heartbeat line format to be more clear on
490 what has been detected/rejected, and which option is disabled (if
491 any). Closes ticket 40308.
492 - In src/core/mainloop/mainloop.c and src/core/mainloop/connection.c,
493 put brackets around IPv6 addresses in log messages. Closes ticket
494 40232. Patch by Neel Chauhan.
496 o Minor features (logging, diagnostic):
497 - Log decompression failures at a higher severity level, since they
498 can help provide missing context for other warning messages. We
499 rate-limit these messages, to avoid flooding the logs if they
500 begin to occur frequently. Closes ticket 40175.
502 o Minor features (onion services):
503 - Add a warning message when trying to connect to (no longer
504 supported) v2 onion services. Closes ticket 40373.
506 o Minor features (performance, windows):
507 - Use SRWLocks to implement locking on Windows. Replaces the
508 "critical section" locking implementation with the faster
509 SRWLocks, available since Windows Vista. Closes ticket 17927.
510 Patch by Daniel Pinto.
512 o Minor features (protocol, proxy support, defense in depth):
513 - Close HAProxy connections if they somehow manage to send us data
514 before we start reading. Closes another case of ticket 40017.
516 o Minor features (tests, portability):
517 - Port the hs_build_address.py test script to work with recent
518 versions of python. Closes ticket 40213. Patch from
521 o Minor features (vote document):
522 - Add a "stats" line to directory authority votes, to report various
523 statistics that authorities compute about the relays. This will
524 help us diagnose the network better. Closes ticket 40314.
526 o Minor bugfixes (build):
527 - The configure script now shows whether or not lzma and zstd have
528 been used, not just if the enable flag was passed in. Fixes bug
529 40236; bugfix on 0.4.3.1-alpha.
531 o Minor bugfixes (compatibility):
532 - Fix a failure in the test cases when running on the "hppa"
533 architecture, along with a related test that might fail on other
534 architectures in the future. Fixes bug 40274; bugfix
537 o Minor bugfixes (compilation):
538 - Fix a compilation warning about unused functions when building
539 with a libc that lacks the GLOB_ALTDIRFUNC constant. Fixes bug
540 40354; bugfix on 0.4.5.1-alpha. Patch by Daniel Pinto.
542 o Minor bugfixes (consensus handling):
543 - Avoid a set of bugs that could be caused by inconsistently
544 preferring an out-of-date consensus stored in a stale directory
545 cache over a more recent one stored on disk as the latest
546 consensus. Fixes bug 40375; bugfix on 0.3.1.1-alpha.
548 o Minor bugfixes (control, sandbox):
549 - Allow the control command SAVECONF to succeed when the seccomp
550 sandbox is enabled, and make SAVECONF keep only one backup file to
551 simplify implementation. Previously SAVECONF allowed a large
552 number of backup files, which made it incompatible with the
553 sandbox. Fixes bug 40317; bugfix on 0.2.5.4-alpha. Patch by
556 o Minor bugfixes (directory authorities, voting):
557 - Add a new consensus method (31) to support any future changes that
558 authorities decide to make to the value of bwweightscale or
559 maxunmeasuredbw. Previously, there was a bug that prevented the
560 authorities from parsing these consensus parameters correctly under
561 most circumstances. Fixes bug 19011; bugfix on 0.2.2.10-alpha.
563 o Minor bugfixes (ipv6):
564 - Allow non-SOCKSPorts to disable IPv4, IPv6, and PreferIPv4. Some
565 rare configurations might break, but in this case you can disable
566 NoIPv4Traffic and NoIPv6Traffic as needed. Fixes bug 33607; bugfix
567 on 0.4.1.1-alpha. Patch by Neel Chauhan.
569 o Minor bugfixes (key generation):
570 - Do not require a valid torrc when using the `--keygen` argument to
571 generate a signing key. This allows us to generate keys on systems
572 or users which may not run Tor. Fixes bug 40235; bugfix on
573 0.2.7.2-alpha. Patch by Neel Chauhan.
575 o Minor bugfixes (logging, relay):
576 - Emit a warning if an Address is found to be internal and tor can't
577 use it. Fixes bug 40290; bugfix on 0.4.5.1-alpha.
579 o Minor bugfixes (metrics port):
580 - Fix a bug that made tor try to re-bind() on an already open
581 MetricsPort every 60 seconds. Fixes bug 40370; bugfix
584 o Minor bugfixes (onion services, logging):
585 - Downgrade the severity of a few rendezvous circuit-related
586 warnings from warning to info. Fixes bug 40207; bugfix on
587 0.3.2.1-alpha. Patch by Neel Chauhan.
589 o Minor bugfixes (relay):
590 - Reduce the compression level for data streaming from HIGH to LOW.
591 This should reduce the CPU and memory burden for directory caches.
592 Fixes bug 40301; bugfix on 0.3.5.1-alpha.
594 o Minor bugfixes (testing, BSD):
595 - Fix pattern-matching errors when patterns expand to invalid paths
596 on BSD systems. Fixes bug 40318; bugfix on 0.4.5.1-alpha. Patch by
599 o Code simplification and refactoring:
600 - Remove the orconn_ext_or_id_map structure and related functions.
601 (Nothing outside of unit tests used them.) Closes ticket 33383.
602 Patch by Neel Chauhan.
605 - Remove unneeded code for parsing private keys in directory
606 documents. This code was only used for client authentication in v2
607 onion services, which are now unsupported. Closes ticket 40374.
608 - As of this release, Tor no longer supports the old v2 onion
609 services. They were deprecated last July for security, and support
610 will be removed entirely later this year. We strongly encourage
611 everybody to migrate to v3 onion services. For more information,
612 see https://blog.torproject.org/v2-deprecation-timeline . Closes
613 ticket 40266. (NOTE: We accidentally released an earlier version
614 of the 0.4.6.1-alpha changelog without this entry. Sorry for
617 o Code simplification and refactoring (metrics, DoS):
618 - Move the DoS subsystem into the subsys manager, including its
619 configuration options. Closes ticket 40261.
621 o Documentation (manual):
622 - Move the ServerTransport* options to the "SERVER OPTIONS" section.
624 - Indicate that the HiddenServiceStatistics option also applies to
625 bridges. Closes ticket 40346.
626 - Move the description of BridgeRecordUsageByCountry to the section
627 "STATISTICS OPTIONS". Closes ticket 40323.
629 o Removed features (relay):
630 - Because DirPorts are only used on authorities, relays no longer
631 advertise them. Similarly, self-testing for DirPorts has been
632 disabled, since an unreachable DirPort is no reason for a relay
633 not to advertise itself. (Configuring a DirPort will still work,
634 for now.) Closes ticket 40282.
637 Changes in version 0.4.5.9 - 2021-06-14
638 Tor 0.4.5.9 fixes several security issues, including a
639 denial-of-service attack against onion service clients, and another
640 denial-of-service attack against relays. Everybody should upgrade to
641 one of 0.3.5.15, 0.4.4.9, 0.4.5.9, or 0.4.6.5.
643 o Major bugfixes (security, backport from 0.4.6.5):
644 - Don't allow relays to spoof RELAY_END or RELAY_RESOLVED cell on
645 half-closed streams. Previously, clients failed to validate which
646 hop sent these cells: this would allow a relay on a circuit to end
647 a stream that wasn't actually built with it. Fixes bug 40389;
648 bugfix on 0.3.5.1-alpha. This issue is also tracked as TROVE-2021-
649 003 and CVE-2021-34548.
651 o Major bugfixes (security, defense-in-depth, backport from 0.4.6.5):
652 - Detect more failure conditions from the OpenSSL RNG code.
653 Previously, we would detect errors from a missing RNG
654 implementation, but not failures from the RNG code itself.
655 Fortunately, it appears those failures do not happen in practice
656 when Tor is using OpenSSL's default RNG implementation. Fixes bug
657 40390; bugfix on 0.2.8.1-alpha. This issue is also tracked as
658 TROVE-2021-004. Reported by Jann Horn at Google's Project Zero.
660 o Major bugfixes (security, denial of service, backport from 0.4.6.5):
661 - Resist a hashtable-based CPU denial-of-service attack against
662 relays. Previously we used a naive unkeyed hash function to look
663 up circuits in a circuitmux object. An attacker could exploit this
664 to construct circuits with chosen circuit IDs, to create
665 collisions and make the hash table inefficient. Now we use a
666 SipHash construction here instead. Fixes bug 40391; bugfix on
667 0.2.4.4-alpha. This issue is also tracked as TROVE-2021-005 and
668 CVE-2021-34549. Reported by Jann Horn from Google's Project Zero.
669 - Fix an out-of-bounds memory access in v3 onion service descriptor
670 parsing. An attacker could exploit this bug by crafting an onion
671 service descriptor that would crash any client that tried to visit
672 it. Fixes bug 40392; bugfix on 0.3.0.1-alpha. This issue is also
673 tracked as TROVE-2021-006 and CVE-2021-34550. Reported by Sergei
674 Glazunov from Google's Project Zero.
676 o Minor features (compatibility, backport from 0.4.6.4-rc):
677 - Remove an assertion function related to TLS renegotiation. It was
678 used nowhere outside the unit tests, and it was breaking
679 compilation with recent alpha releases of OpenSSL 3.0.0. Closes
682 o Minor features (geoip data):
683 - Update the geoip files to match the IPFire Location Database, as
684 retrieved on 2021/06/10.
686 o Minor bugfixes (control, sandbox, backport from 0.4.6.4-rc):
687 - Allow the control command SAVECONF to succeed when the seccomp
688 sandbox is enabled, and make SAVECONF keep only one backup file to
689 simplify implementation. Previously SAVECONF allowed a large
690 number of backup files, which made it incompatible with the
691 sandbox. Fixes bug 40317; bugfix on 0.2.5.4-alpha. Patch by
694 o Minor bugfixes (metrics port, backport from 0.4.6.4-rc):
695 - Fix a bug that made tor try to re-bind() on an already open
696 MetricsPort every 60 seconds. Fixes bug 40370; bugfix
700 Changes in version 0.4.4.9 - 2021-06-14
701 Tor 0.4.4.9 fixes several security issues, including a
702 denial-of-service attack against onion service clients, and another
703 denial-of-service attack against relays. Everybody should upgrade to
704 one of 0.3.5.15, 0.4.4.9, 0.4.5.9, or 0.4.6.5.
706 Note that the scheduled end-of-life date for the Tor 0.4.4.x series is
707 June 15. This is therefore the last release in its series. Everybody
708 still running 0.4.4.x should plan to upgrade to 0.4.5.x or later.
710 o Major bugfixes (security, backport from 0.4.6.5):
711 - Don't allow relays to spoof RELAY_END or RELAY_RESOLVED cell on
712 half-closed streams. Previously, clients failed to validate which
713 hop sent these cells: this would allow a relay on a circuit to end
714 a stream that wasn't actually built with it. Fixes bug 40389;
715 bugfix on 0.3.5.1-alpha. This issue is also tracked as TROVE-2021-
716 003 and CVE-2021-34548.
718 o Major bugfixes (security, defense-in-depth, backport from 0.4.6.5):
719 - Detect more failure conditions from the OpenSSL RNG code.
720 Previously, we would detect errors from a missing RNG
721 implementation, but not failures from the RNG code itself.
722 Fortunately, it appears those failures do not happen in practice
723 when Tor is using OpenSSL's default RNG implementation. Fixes bug
724 40390; bugfix on 0.2.8.1-alpha. This issue is also tracked as
725 TROVE-2021-004. Reported by Jann Horn at Google's Project Zero.
727 o Major bugfixes (security, denial of service, backport from 0.4.6.5):
728 - Resist a hashtable-based CPU denial-of-service attack against
729 relays. Previously we used a naive unkeyed hash function to look
730 up circuits in a circuitmux object. An attacker could exploit this
731 to construct circuits with chosen circuit IDs, to create
732 collisions and make the hash table inefficient. Now we use a
733 SipHash construction here instead. Fixes bug 40391; bugfix on
734 0.2.4.4-alpha. This issue is also tracked as TROVE-2021-005 and
735 CVE-2021-34549. Reported by Jann Horn from Google's Project Zero.
736 - Fix an out-of-bounds memory access in v3 onion service descriptor
737 parsing. An attacker could exploit this bug by crafting an onion
738 service descriptor that would crash any client that tried to visit
739 it. Fixes bug 40392; bugfix on 0.3.0.1-alpha. This issue is also
740 tracked as TROVE-2021-006 and CVE-2021-34550. Reported by Sergei
741 Glazunov from Google's Project Zero.
743 o Minor features (compatibility, backport from 0.4.6.4-rc):
744 - Remove an assertion function related to TLS renegotiation. It was
745 used nowhere outside the unit tests, and it was breaking
746 compilation with recent alpha releases of OpenSSL 3.0.0. Closes
749 o Minor features (fallback directory list, backport from 0.4.6.2-alpha):
750 - Regenerate the list of fallback directories to contain a new set
751 of 200 relays. Closes ticket 40265.
753 o Minor features (geoip data):
754 - Update the geoip files to match the IPFire Location Database, as
755 retrieved on 2021/06/10.
757 o Minor bugfixes (channel, DoS, backport from 0.4.6.2-alpha):
758 - Fix a non-fatal BUG() message due to a too-early free of a string,
759 when listing a client connection from the DoS defenses subsystem.
760 Fixes bug 40345; bugfix on 0.4.3.4-rc.
762 o Minor bugfixes (compiler warnings, backport from 0.4.6.3-rc):
763 - Fix an indentation problem that led to a warning from GCC 11.1.1.
764 Fixes bug 40380; bugfix on 0.3.0.1-alpha.
767 Changes in version 0.3.5.15 - 2021-06-14
768 Tor 0.3.5.15 fixes several security issues, including a
769 denial-of-service attack against onion service clients, and another
770 denial-of-service attack against relays. Everybody should upgrade to
771 one of 0.3.5.15, 0.4.4.9, 0.4.5.9, or 0.4.6.5.
773 o Major bugfixes (security, backport from 0.4.6.5):
774 - Don't allow relays to spoof RELAY_END or RELAY_RESOLVED cell on
775 half-closed streams. Previously, clients failed to validate which
776 hop sent these cells: this would allow a relay on a circuit to end
777 a stream that wasn't actually built with it. Fixes bug 40389;
778 bugfix on 0.3.5.1-alpha. This issue is also tracked as TROVE-2021-
779 003 and CVE-2021-34548.
781 o Major bugfixes (security, defense-in-depth, backport from 0.4.6.5):
782 - Detect more failure conditions from the OpenSSL RNG code.
783 Previously, we would detect errors from a missing RNG
784 implementation, but not failures from the RNG code itself.
785 Fortunately, it appears those failures do not happen in practice
786 when Tor is using OpenSSL's default RNG implementation. Fixes bug
787 40390; bugfix on 0.2.8.1-alpha. This issue is also tracked as
788 TROVE-2021-004. Reported by Jann Horn at Google's Project Zero.
790 o Major bugfixes (security, denial of service, backport from 0.4.6.5):
791 - Resist a hashtable-based CPU denial-of-service attack against
792 relays. Previously we used a naive unkeyed hash function to look
793 up circuits in a circuitmux object. An attacker could exploit this
794 to construct circuits with chosen circuit IDs, to create
795 collisions and make the hash table inefficient. Now we use a
796 SipHash construction here instead. Fixes bug 40391; bugfix on
797 0.2.4.4-alpha. This issue is also tracked as TROVE-2021-005 and
798 CVE-2021-34549. Reported by Jann Horn from Google's Project Zero.
799 - Fix an out-of-bounds memory access in v3 onion service descriptor
800 parsing. An attacker could exploit this bug by crafting an onion
801 service descriptor that would crash any client that tried to visit
802 it. Fixes bug 40392; bugfix on 0.3.0.1-alpha. This issue is also
803 tracked as TROVE-2021-006 and CVE-2021-34550. Reported by Sergei
804 Glazunov from Google's Project Zero.
806 o Minor bugfixes (compiler warnings, backport from 0.4.6.3-rc):
807 - Fix an indentation problem that led to a warning from GCC 11.1.1.
808 Fixes bug 40380; bugfix on 0.3.0.1-alpha.
810 o Minor features (compatibility, backport from 0.4.6.4-rc):
811 - Remove an assertion function related to TLS renegotiation. It was
812 used nowhere outside the unit tests, and it was breaking
813 compilation with recent alpha releases of OpenSSL 3.0.0. Closes
816 o Minor features (fallback directory list, backport from 0.4.6.2-alpha):
817 - Regenerate the list of fallback directories to contain a new set
818 of 200 relays. Closes ticket 40265.
820 o Minor features (geoip data):
821 - Update the geoip files to match the IPFire Location Database, as
822 retrieved on 2021/06/10.
825 Changes in version 0.4.5.8 - 2021-05-10
826 Tor 0.4.5.8 fixes several bugs in earlier version, backporting fixes
827 from the 0.4.6.x series.
829 o Minor features (compatibility, Linux seccomp sandbox, backport from 0.4.6.3-rc):
830 - Add a workaround to enable the Linux sandbox to work correctly
831 with Glibc 2.33. This version of Glibc has started using the
832 fstatat() system call, which previously our sandbox did not allow.
833 Closes ticket 40382; see the ticket for a discussion of trade-offs.
835 o Minor features (compilation, backport from 0.4.6.3-rc):
836 - Make the autoconf script build correctly with autoconf versions
837 2.70 and later. Closes part of ticket 40335.
839 o Minor features (fallback directory list, backport from 0.4.6.2-alpha):
840 - Regenerate the list of fallback directories to contain a new set
841 of 200 relays. Closes ticket 40265.
843 o Minor features (geoip data):
844 - Update the geoip files to match the IPFire Location Database, as
845 retrieved on 2021/05/07.
847 o Minor features (onion services):
848 - Add warning message when connecting to now deprecated v2 onion
849 services. As announced, Tor 0.4.5.x is the last series that will
850 support v2 onions. Closes ticket 40373.
852 o Minor bugfixes (bridge, pluggable transport, backport from 0.4.6.2-alpha):
853 - Fix a regression that made it impossible start Tor using a bridge
854 line with a transport name and no fingerprint. Fixes bug 40360;
855 bugfix on 0.4.5.4-rc.
857 o Minor bugfixes (build, cross-compilation, backport from 0.4.6.3-rc):
858 - Allow a custom "ar" for cross-compilation. Our previous build
859 script had used the $AR environment variable in most places, but
860 it missed one. Fixes bug 40369; bugfix on 0.4.5.1-alpha.
862 o Minor bugfixes (channel, DoS, backport from 0.4.6.2-alpha):
863 - Fix a non-fatal BUG() message due to a too-early free of a string,
864 when listing a client connection from the DoS defenses subsystem.
865 Fixes bug 40345; bugfix on 0.4.3.4-rc.
867 o Minor bugfixes (compiler warnings, backport from 0.4.6.3-rc):
868 - Fix an indentation problem that led to a warning from GCC 11.1.1.
869 Fixes bug 40380; bugfix on 0.3.0.1-alpha.
871 o Minor bugfixes (controller, backport from 0.4.6.1-alpha):
872 - Fix a "BUG" warning that would appear when a controller chooses
873 the first hop for a circuit, and that circuit completes. Fixes bug
874 40285; bugfix on 0.3.2.1-alpha.
876 o Minor bugfixes (onion service, client, memory leak, backport from 0.4.6.3-rc):
877 - Fix a bug where an expired cached descriptor could get overwritten
878 with a new one without freeing it, leading to a memory leak. Fixes
879 bug 40356; bugfix on 0.3.5.1-alpha.
881 o Minor bugfixes (testing, BSD, backport from 0.4.6.2-alpha):
882 - Fix pattern-matching errors when patterns expand to invalid paths
883 on BSD systems. Fixes bug 40318; bugfix on 0.4.5.1-alpha. Patch by
887 Changes in version 0.3.5.14 - 2021-03-16
888 Tor 0.3.5.14 backports fixes for two important denial-of-service bugs
889 in earlier versions of Tor.
891 One of these vulnerabilities (TROVE-2021-001) would allow an attacker
892 who can send directory data to a Tor instance to force that Tor
893 instance to consume huge amounts of CPU. This is easiest to exploit
894 against authorities, since anybody can upload to them, but directory
895 caches could also exploit this vulnerability against relays or clients
896 when they download. The other vulnerability (TROVE-2021-002) only
897 affects directory authorities, and would allow an attacker to remotely
898 crash the authority with an assertion failure. Patches have already
899 been provided to the authority operators, to help ensure
902 We recommend that everybody upgrade to one of the releases that fixes
903 these issues (0.3.5.14, 0.4.4.8, or 0.4.5.7) as they become available
906 This release also updates our GeoIP data source, and fixes a
909 o Major bugfixes (security, denial of service, backport from 0.4.5.7):
910 - Disable the dump_desc() function that we used to dump unparseable
911 information to disk. It was called incorrectly in several places,
912 in a way that could lead to excessive CPU usage. Fixes bug 40286;
913 bugfix on 0.2.2.1-alpha. This bug is also tracked as TROVE-2021-
914 001 and CVE-2021-28089.
915 - Fix a bug in appending detached signatures to a pending consensus
916 document that could be used to crash a directory authority. Fixes
917 bug 40316; bugfix on 0.2.2.6-alpha. Tracked as TROVE-2021-002
920 o Minor features (geoip data, backport from 0.4.5.7):
921 - We have switched geoip data sources. Previously we shipped IP-to-
922 country mappings from Maxmind's GeoLite2, but in 2019 they changed
923 their licensing terms, so we were unable to update them after that
924 point. We now ship geoip files based on the IPFire Location
925 Database instead. (See https://location.ipfire.org/ for more
926 information). This release updates our geoip files to match the
927 IPFire Location Database as retrieved on 2021/03/12. Closes
930 o Removed features (mallinfo deprecated, backport from 0.4.5.7):
931 - Remove mallinfo() usage entirely. Libc 2.33+ now deprecates it.
935 Changes in version 0.4.4.8 - 2021-03-16
936 Tor 0.4.4.8 backports fixes for two important denial-of-service bugs
937 in earlier versions of Tor.
939 One of these vulnerabilities (TROVE-2021-001) would allow an attacker
940 who can send directory data to a Tor instance to force that Tor
941 instance to consume huge amounts of CPU. This is easiest to exploit
942 against authorities, since anybody can upload to them, but directory
943 caches could also exploit this vulnerability against relays or clients
944 when they download. The other vulnerability (TROVE-2021-002) only
945 affects directory authorities, and would allow an attacker to remotely
946 crash the authority with an assertion failure. Patches have already
947 been provided to the authority operators, to help ensure
950 We recommend that everybody upgrade to one of the releases that fixes
951 these issues (0.3.5.14, 0.4.4.8, or 0.4.5.7) as they become available
954 This release also updates our GeoIP data source, and fixes a
957 o Major bugfixes (security, denial of service, backport from 0.4.5.7):
958 - Disable the dump_desc() function that we used to dump unparseable
959 information to disk. It was called incorrectly in several places,
960 in a way that could lead to excessive CPU usage. Fixes bug 40286;
961 bugfix on 0.2.2.1-alpha. This bug is also tracked as TROVE-2021-
962 001 and CVE-2021-28089.
963 - Fix a bug in appending detached signatures to a pending consensus
964 document that could be used to crash a directory authority. Fixes
965 bug 40316; bugfix on 0.2.2.6-alpha. Tracked as TROVE-2021-002
968 o Minor features (geoip data, backport from 0.4.5.7):
969 - We have switched geoip data sources. Previously we shipped IP-to-
970 country mappings from Maxmind's GeoLite2, but in 2019 they changed
971 their licensing terms, so we were unable to update them after that
972 point. We now ship geoip files based on the IPFire Location
973 Database instead. (See https://location.ipfire.org/ for more
974 information). This release updates our geoip files to match the
975 IPFire Location Database as retrieved on 2021/03/12. Closes
978 o Removed features (mallinfo deprecated, backport from 0.4.5.7):
979 - Remove mallinfo() usage entirely. Libc 2.33+ now deprecates it.
983 Changes in version 0.4.5.7 - 2021-03-16
984 Tor 0.4.5.7 fixes two important denial-of-service bugs in earlier
987 One of these vulnerabilities (TROVE-2021-001) would allow an attacker
988 who can send directory data to a Tor instance to force that Tor
989 instance to consume huge amounts of CPU. This is easiest to exploit
990 against authorities, since anybody can upload to them, but directory
991 caches could also exploit this vulnerability against relays or clients
992 when they download. The other vulnerability (TROVE-2021-002) only
993 affects directory authorities, and would allow an attacker to remotely
994 crash the authority with an assertion failure. Patches have already
995 been provided to the authority operators, to help ensure
998 We recommend that everybody upgrade to one of the releases that fixes
999 these issues (0.3.5.14, 0.4.4.8, or 0.4.5.7) as they become available
1002 This release also updates our GeoIP data source, and fixes a few
1003 smaller bugs in earlier releases.
1005 o Major bugfixes (security, denial of service):
1006 - Disable the dump_desc() function that we used to dump unparseable
1007 information to disk. It was called incorrectly in several places,
1008 in a way that could lead to excessive CPU usage. Fixes bug 40286;
1009 bugfix on 0.2.2.1-alpha. This bug is also tracked as TROVE-2021-
1010 001 and CVE-2021-28089.
1011 - Fix a bug in appending detached signatures to a pending consensus
1012 document that could be used to crash a directory authority. Fixes
1013 bug 40316; bugfix on 0.2.2.6-alpha. Tracked as TROVE-2021-002
1016 o Minor features (geoip data):
1017 - We have switched geoip data sources. Previously we shipped IP-to-
1018 country mappings from Maxmind's GeoLite2, but in 2019 they changed
1019 their licensing terms, so we were unable to update them after that
1020 point. We now ship geoip files based on the IPFire Location
1021 Database instead. (See https://location.ipfire.org/ for more
1022 information). This release updates our geoip files to match the
1023 IPFire Location Database as retrieved on 2021/03/12. Closes
1026 o Minor bugfixes (directory authority):
1027 - Now that exit relays don't allow exit connections to directory
1028 authority DirPorts (to prevent network reentry), disable
1029 authorities' reachability self test on the DirPort. Fixes bug
1030 40287; bugfix on 0.4.5.5-rc.
1032 o Minor bugfixes (documentation):
1033 - Fix a formatting error in the documentation for
1034 VirtualAddrNetworkIPv6. Fixes bug 40256; bugfix on 0.2.9.4-alpha.
1036 o Minor bugfixes (Linux, relay):
1037 - Fix a bug in determining total available system memory that would
1038 have been triggered if the format of Linux's /proc/meminfo file
1039 had ever changed to include "MemTotal:" in the middle of a line.
1040 Fixes bug 40315; bugfix on 0.2.5.4-alpha.
1042 o Minor bugfixes (metrics port):
1043 - Fix a BUG() warning on the MetricsPort for an internal missing
1044 handler. Fixes bug 40295; bugfix on 0.4.5.1-alpha.
1046 o Minor bugfixes (onion service):
1047 - Remove a harmless BUG() warning when reloading tor configured with
1048 onion services. Fixes bug 40334; bugfix on 0.4.5.1-alpha.
1050 o Minor bugfixes (portability):
1051 - Fix a non-portable usage of "==" with "test" in the configure
1052 script. Fixes bug 40298; bugfix on 0.4.5.1-alpha.
1054 o Minor bugfixes (relay):
1055 - Remove a spammy log notice falsely claiming that the IPv4/v6
1056 address was missing. Fixes bug 40300; bugfix on 0.4.5.1-alpha.
1057 - Do not query the address cache early in the boot process when
1058 deciding if a relay needs to fetch early directory information
1059 from an authority. This bug resulted in a relay falsely believing
1060 it didn't have an address and thus triggering an authority fetch
1061 at each boot. Related to our fix for 40300.
1063 o Removed features (mallinfo deprecated):
1064 - Remove mallinfo() usage entirely. Libc 2.33+ now deprecates it.
1065 Closes ticket 40309.
1068 Changes in version 0.4.5.6 - 2021-02-15
1069 The Tor 0.4.5.x release series is dedicated to the memory of Karsten
1070 Loesing (1979-2020), Tor developer, cypherpunk, husband, and father.
1071 Karsten is best known for creating the Tor metrics portal and leading
1072 the metrics team, but he was involved in Tor from the early days. For
1073 example, while he was still a student he invented and implemented the
1074 v2 onion service directory design, and he also served as an ambassador
1075 to the many German researchers working in the anonymity field. We
1076 loved him and respected him for his patience, his consistency, and his
1077 welcoming approach to growing our community.
1079 This release series introduces significant improvements in relay IPv6
1080 address discovery, a new "MetricsPort" mechanism for relay operators
1081 to measure performance, LTTng support, build system improvements to
1082 help when using Tor as a static library, and significant bugfixes
1083 related to Windows relay performance. It also includes numerous
1084 smaller features and bugfixes.
1086 Below are the changes since 0.4.4.7. For a list of changes since
1087 0.4.5.5-rc, see the ChangeLog file.
1089 o Major features (build):
1090 - When building Tor, first link all object files into a single
1091 static library. This may help with embedding Tor in other
1092 programs. Note that most Tor functions do not constitute a part of
1093 a stable or supported API: only those functions in tor_api.h
1094 should be used if embedding Tor. Closes ticket 40127.
1096 o Major features (metrics):
1097 - Introduce a new MetricsPort which exposes, through an HTTP
1098 interface, a series of metrics that tor collects at runtime. At
1099 the moment, the only supported output format is Prometheus data
1100 model. Closes ticket 40063. See the manual page for more
1101 information and security considerations.
1103 o Major features (relay, IPv6):
1104 - The torrc option Address now supports IPv6. This unifies our
1105 address discovery interface to support IPv4, IPv6, and hostnames.
1106 Closes ticket 33233.
1107 - Launch IPv4 and IPv6 ORPort self-test circuits on relays and
1108 bridges. Closes ticket 33222.
1109 - Relays now automatically bind on IPv6 for their ORPort, unless
1110 specified otherwise with the IPv4Only flag. Closes ticket 33246.
1111 - When a relay with IPv6 support is told to open a connection to
1112 another relay, and the extend cell lists both IPv4 and IPv6
1113 addresses, the first relay now picks randomly which address to
1114 use. Closes ticket 33220.
1115 - Relays now track their IPv6 ORPort reachability separately from
1116 the reachability of their IPv4 ORPort. They will not publish a
1117 descriptor unless _both_ ports appear to be externally reachable.
1118 Closes ticket 34067.
1120 o Major features (tracing):
1121 - Add event-tracing library support for USDT and LTTng-UST, and a
1122 few tracepoints in the circuit subsystem. More will come
1123 incrementally. This feature is compiled out by default: it needs
1124 to be enabled at configure time. See documentation in
1125 doc/HACKING/Tracing.md. Closes ticket 32910.
1127 o Major bugfixes (directory cache, performance, windows):
1128 - Limit the number of items in the consensus diff cache to 64 on
1129 Windows. We hope this will mitigate an issue where Windows relay
1130 operators reported Tor using 100% CPU, while we investigate better
1131 solutions. Fixes bug 24857; bugfix on 0.3.1.1-alpha.
1133 o Major bugfixes (relay, windows):
1134 - Fix a bug in our implementation of condition variables on Windows.
1135 Previously, a relay on Windows would use 100% CPU after running
1136 for some time. Because of this change, Tor now require Windows
1137 Vista or later to build and run. Fixes bug 30187; bugfix on
1138 0.2.6.3-alpha. (This bug became more serious in 0.3.1.1-alpha with
1139 the introduction of consensus diffs.) Patch by Daniel Pinto.
1141 o Major bugfixes (TLS, buffer):
1142 - When attempting to read N bytes on a TLS connection, really try to
1143 read all N bytes. Previously, Tor would stop reading after the
1144 first TLS record, which can be smaller than the N bytes requested,
1145 and not check for more data until the next mainloop event. Fixes
1146 bug 40006; bugfix on 0.1.0.5-rc.
1148 o Minor features (address discovery):
1149 - If no Address statements are found, relays now prioritize guessing
1150 their address by looking at the local interface instead of the
1151 local hostname. If the interface address can't be found, the local
1152 hostname is used. Closes ticket 33238.
1154 o Minor features (admin tools):
1155 - Add a new --format argument to -key-expiration option to allow
1156 specifying the time format of the expiration date. Adds Unix
1157 timestamp format support. Patch by Daniel Pinto. Closes
1160 o Minor features (authority, logging):
1161 - Log more information for directory authority operators during the
1162 consensus voting process, and while processing relay descriptors.
1163 Closes ticket 40245.
1165 o Minor features (bootstrap reporting):
1166 - When reporting bootstrapping status on a relay, do not consider
1167 connections that have never been the target of an origin circuit.
1168 Previously, all connection failures were treated as potential
1169 bootstrapping failures, including connections that had been opened
1170 because of client requests. Closes ticket 25061.
1172 o Minor features (build):
1173 - When running the configure script, try to detect version
1174 mismatches between the OpenSSL headers and libraries, and suggest
1175 that the user should try "--with-openssl-dir". Closes 40138.
1176 - If the configure script has given any warnings, remind the user
1177 about them at the end of the script. Related to 40138.
1179 o Minor features (configuration):
1180 - Allow using wildcards (* and ?) with the %include option on
1181 configuration files. Closes ticket 25140. Patch by Daniel Pinto.
1182 - Allow the configuration options EntryNodes, ExcludeNodes,
1183 ExcludeExitNodes, ExitNodes, MiddleNodes, HSLayer2Nodes and
1184 HSLayer3Nodes to be specified multiple times. Closes ticket 28361.
1185 Patch by Daniel Pinto.
1187 o Minor features (control port):
1188 - Add a DROPTIMEOUTS command to drop circuit build timeout history
1189 and reset the current timeout. Closes ticket 40002.
1190 - When a stream enters the AP_CONN_STATE_CONTROLLER_WAIT status,
1191 send a control port event. Closes ticket 32190. Patch by
1193 - Introduce GETINFO "stats/ntor/{assigned/requested}" and
1194 "stats/tap/{assigned/requested}" to get the NTor and TAP circuit
1195 onion handshake counts respectively. Closes ticket 28279. Patch by
1198 o Minor features (control port, IPv6):
1199 - Tor relays now try to report to the controller when they are
1200 launching an IPv6 self-test. Closes ticket 34068.
1201 - Introduce "GETINFO address/v4" and "GETINFO address/v6" in the
1202 control port to fetch the Tor host's respective IPv4 or IPv6
1203 address. We keep "GETINFO address" for backwards-compatibility.
1204 Closes ticket 40039. Patch by Neel Chauhan.
1206 o Minor features (directory authorities):
1207 - Add a new consensus method 30 that removes the unnecessary "="
1208 padding from ntor-onion-key. Closes ticket 7869. Patch by
1210 - Directory authorities now reject descriptors from relays running
1211 Tor versions from the obsolete 0.4.1 series. Resolves ticket
1212 34357. Patch by Neel Chauhan.
1213 - The AssumeReachable option no longer stops directory authorities
1214 from checking whether other relays are running. A new
1215 AuthDirTestReachability option can be used to disable these
1216 checks. Closes ticket 34445.
1217 - When looking for possible Sybil attacks, also consider IPv6
1218 addresses. Two routers are considered to have "the same" address
1219 by this metric if they are in the same /64 network. Patch from
1220 Maurice Pibouin. Closes ticket 7193.
1222 o Minor features (directory authorities, IPv6):
1223 - Make authorities add their IPv6 ORPort (if any) to the trusted
1224 servers list. Authorities previously added only their IPv4
1225 addresses. Closes ticket 32822.
1227 o Minor features (documentation):
1228 - Mention the "!badexit" directive that can appear in an authority's
1229 approved-routers file, and update the description of the
1230 "!invalid" directive. Closes ticket 40188.
1232 o Minor features (ed25519, relay):
1233 - Save a relay's base64-encoded ed25519 identity key to the data
1234 directory in a file named fingerprint-ed25519. Closes ticket
1235 30642. Patch by Neel Chauhan.
1237 o Minor features (heartbeat):
1238 - Include the total number of inbound and outbound IPv4 and IPv6
1239 connections in the heartbeat message. Closes ticket 29113.
1241 o Minor features (IPv6, ExcludeNodes):
1242 - Handle IPv6 addresses in ExcludeNodes; previously they were
1243 ignored. Closes ticket 34065. Patch by Neel Chauhan.
1245 o Minor features (logging):
1246 - Add the running glibc version to the log, and the compiled glibc
1247 version to the library list returned when using --library-versions.
1248 Patch from Daniel Pinto. Closes ticket 40047.
1249 - Consider an HTTP 301 response to be an error (like a 404) when
1250 processing a directory response. Closes ticket 40053.
1251 - Log directory fetch statistics as a single line. Closes
1253 - Provide more complete descriptions of our connections when logging
1254 about them. Closes ticket 40041.
1255 - When describing a relay in the logs, we now include its ed25519
1256 identity. Closes ticket 22668.
1258 o Minor features (onion services):
1259 - Only overwrite an onion service's existing hostname file if its
1260 contents are wrong. This enables read-only onion-service
1261 directories. Resolves ticket 40062. Patch by Neel Chauhan.
1263 o Minor features (pluggable transports):
1264 - Add an OutboundBindAddressPT option to allow users to specify
1265 which IPv4 and IPv6 address pluggable transports should use for
1266 outgoing IP packets. Tor does not have a way to enforce that the
1267 pluggable transport honors this option, so each pluggable transport
1268 needs to implement support on its own. Closes ticket 5304.
1270 o Minor features (protocol, proxy support, defense in depth):
1271 - Respond more deliberately to misbehaving proxies that leave
1272 leftover data on their connections, so as to make Tor even less
1273 likely to allow the proxies to pass their data off as having come
1274 from a relay. Closes ticket 40017.
1276 o Minor features (relay address tracking):
1277 - We now store relay addresses for OR connections in a more logical
1278 way. Previously we would sometimes overwrite the actual address of
1279 a connection with a "canonical address", and then store the "real
1280 address" elsewhere to remember it. We now track the "canonical
1281 address" elsewhere for the cases where we need it, and leave the
1282 connection's address alone. Closes ticket 33898.
1284 o Minor features (relay):
1285 - If a relay is unable to discover its address, attempt to learn it
1286 from the NETINFO cell. Closes ticket 40022.
1287 - Log immediately when launching a relay self-check. Previously we
1288 would try to log before launching checks, or approximately when we
1289 intended to launch checks, but this tended to be error-prone.
1290 Closes ticket 34137.
1292 o Minor features (relay, address discovery):
1293 - If Address option is not found in torrc, attempt to learn our
1294 address with the configured ORPort address if any. Closes
1297 o Minor features (relay, IPv6):
1298 - Add an AssumeReachableIPv6 option to disable self-checking IPv6
1299 reachability. Closes part of ticket 33224.
1300 - Add new "assume-reachable" and "assume-reachable-ipv6" consensus
1301 parameters to be used in an emergency to tell relays that they
1302 should publish even if they cannot complete their ORPort self-
1303 checks. Closes ticket 34064 and part of 33224.
1304 - Allow relays to send IPv6-only extend cells. Closes ticket 33222.
1305 - Declare support for the Relay=3 subprotocol version. Closes
1307 - When launching IPv6 ORPort self-test circuits, make sure that the
1308 second-last hop can initiate an IPv6 extend. Closes ticket 33222.
1310 o Minor features (safety):
1311 - Log a warning at startup if Tor is built with compile-time options
1312 that are likely to make it less stable or reliable. Closes
1315 o Minor features (specification update):
1316 - Several fields in microdescriptors, router descriptors, and
1317 consensus documents that were formerly optional are now required.
1318 Implements proposal 315; closes ticket 40132.
1320 o Minor features (state management):
1321 - When loading the state file, remove entries from the statefile
1322 that have been obsolete for a long time. Ordinarily Tor preserves
1323 unrecognized entries in order to keep forward-compatibility, but
1324 these entries have not actually been used in any release since
1325 before 0.3.5.x. Closes ticket 40137.
1327 o Minor features (statistics, ipv6):
1328 - Relays now publish IPv6-specific counts of single-direction versus
1329 bidirectional relay connections. Closes ticket 33264.
1330 - Relays now publish their IPv6 read and write statistics over time,
1331 if statistics are enabled. Closes ticket 33263.
1333 o Minor features (subprotocol versions):
1334 - Use the new limitations on subprotocol versions due to proposal
1335 318 to simplify our implementation. Part of ticket 40133.
1337 o Minor features (testing configuration):
1338 - The TestingTorNetwork option no longer implicitly sets
1339 AssumeReachable to 1. This change allows us to test relays' self-
1340 testing mechanisms, and to test authorities' relay-testing
1341 functionality. Closes ticket 34446.
1343 o Minor features (testing):
1344 - Added unit tests for channel_matches_target_addr_for_extend().
1345 Closes Ticket 33919. Patch by MrSquanchee.
1347 o Minor bugfixes (circuit padding):
1348 - When circpad_send_padding_cell_for_callback is called,
1349 `is_padding_timer_scheduled` flag was not reset. Now it is set to
1350 0 at the top of that function. Fixes bug 32671; bugfix
1352 - Add a per-circuit padding machine instance counter, so we can
1353 differentiate between shutdown requests for old machines on a
1354 circuit. Fixes bug 30992; bugfix on 0.4.1.1-alpha.
1355 - Add the ability to keep circuit padding machines if they match a
1356 set of circuit states or purposes. This allows us to have machines
1357 that start up under some conditions but don't shut down under
1358 others. We now use this mask to avoid starting up introduction
1359 circuit padding again after the machines have already completed.
1360 Fixes bug 32040; bugfix on 0.4.1.1-alpha.
1362 o Minor bugfixes (circuit, handshake):
1363 - In the v3 handshaking code, use connection_or_change_state() to
1364 change the state. Previously, we changed the state directly, but
1365 this did not pass the state change to the pubsub or channel
1366 objects, potentially leading to bugs. Fixes bug 32880; bugfix on
1367 0.2.3.6-alpha. Patch by Neel Chauhan.
1369 o Minor bugfixes (compilation):
1370 - Change the linker flag ordering in our library search code so that
1371 it works for compilers that need the libraries to be listed in the
1372 right order. Fixes bug 33624; bugfix on 0.1.1.0-alpha.
1373 - Fix the "--enable-static-tor" switch to properly set the "-static"
1374 compile option onto the tor binary only. Fixes bug 40111; bugfix
1377 o Minor bugfixes (configuration):
1378 - Exit Tor on a misconfiguration when the Bridge line is configured
1379 to use a transport but no corresponding ClientTransportPlugin can
1380 be found. Prior to this fix, Tor would attempt to connect to the
1381 bridge directly without using the transport, making it easier for
1382 adversaries to notice the bridge. Fixes bug 25528; bugfix
1385 o Minor bugfixes (control port):
1386 - Make sure we send the SOCKS request address in relay begin cells
1387 when a stream is attached with the purpose
1388 CIRCUIT_PURPOSE_CONTROLLER. Fixes bug 33124; bugfix on 0.0.5.
1389 Patch by Neel Chauhan.
1391 o Minor bugfixes (crash, relay, signing key):
1392 - Avoid assertion failures when we run Tor from the command line
1393 with `--key-expiration sign`, but an ORPort is not set. Fixes bug
1394 40015; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
1396 o Minor bugfixes (logging):
1397 - Avoid a spurious log message about missing subprotocol versions,
1398 when the consensus that we're reading from is older than the
1399 current release. Previously we had made this message nonfatal, but
1400 in practice, it is never relevant when the consensus is older than
1401 the current release. Fixes bug 40281; bugfix on 0.4.0.1-alpha.
1402 - Remove trailing whitespace from control event log messages. Fixes
1403 bug 32178; bugfix on 0.1.1.1-alpha. Based on a patch by
1405 - Turn warning-level log message about SENDME failure into a debug-
1406 level message. (This event can happen naturally, and is no reason
1407 for concern). Fixes bug 40142; bugfix on 0.4.1.1-alpha.
1408 - When logging a rate-limited message about how many messages have
1409 been suppressed in the last N seconds, give an accurate value for
1410 N, rounded up to the nearest minute. Previously we would report
1411 the size of the rate-limiting interval, regardless of when the
1412 messages started to occur. Fixes bug 19431; bugfix
1415 o Minor bugfixes (onion services):
1416 - Avoid a non-fatal assertion in certain edge-cases when
1417 establishing a circuit to an onion service. Fixes bug 32666;
1418 bugfix on 0.3.0.3-alpha.
1420 o Minor bugfixes (rust, protocol versions):
1421 - Declare support for the onion service introduction point denial of
1422 service extensions when building with Rust. Fixes bug 34248;
1423 bugfix on 0.4.2.1-alpha.
1424 - Make Rust protocol version support checks consistent with the
1425 undocumented error behavior of the corresponding C code. Fixes bug
1426 34251; bugfix on 0.3.3.5-rc.
1428 o Minor bugfixes (self-testing):
1429 - When receiving an incoming circuit, only accept it as evidence
1430 that we are reachable if the declared address of its channel is
1431 the same address we think that we have. Otherwise, it could be
1432 evidence that we're reachable on some other address. Fixes bug
1433 20165; bugfix on 0.1.0.1-rc.
1435 o Minor bugfixes (spec conformance):
1436 - Use the correct key type when generating signing->link
1437 certificates. Fixes bug 40124; bugfix on 0.2.7.2-alpha.
1439 o Minor bugfixes (subprotocol versions):
1440 - Consistently reject extra commas, instead of only rejecting
1441 leading commas. Fixes bug 27194; bugfix on 0.2.9.4-alpha.
1442 - In summarize_protover_flags(), treat empty strings the same as
1443 NULL. This prevents protocols_known from being set. Previously, we
1444 treated empty strings as normal strings, which led to
1445 protocols_known being set. Fixes bug 34232; bugfix on
1446 0.3.3.2-alpha. Patch by Neel Chauhan.
1448 o Code simplification and refactoring:
1449 - Add and use a set of functions to perform down-casts on constant
1450 connection and channel pointers. Closes ticket 40046.
1451 - Refactor our code that logs descriptions of connections, channels,
1452 and the peers on them, to use a single call path. This change
1453 enables us to refactor the data types that they use, and eliminates
1454 many confusing usages of those types. Closes ticket 40041.
1455 - Refactor some common node selection code into a single function.
1456 Closes ticket 34200.
1457 - Remove the now-redundant 'outbuf_flushlen' field from our
1458 connection type. It was previously used for an older version of
1459 our rate-limiting logic. Closes ticket 33097.
1460 - Rename "fascist_firewall_*" identifiers to "reachable_addr_*"
1461 instead, for consistency with other code. Closes ticket 18106.
1462 - Rename functions about "advertised" ports which are not in fact
1463 guaranteed to return the ports that have been advertised. Closes
1465 - Split implementation of several command line options from
1466 options_init_from_torrc into smaller isolated functions. Patch by
1467 Daniel Pinto. Closes ticket 40102.
1468 - When an extend cell is missing an IPv4 or IPv6 address, fill in
1469 the address from the extend info. This is similar to what was done
1470 in ticket 33633 for ed25519 keys. Closes ticket 33816. Patch by
1473 o Deprecated features:
1474 - The "non-builtin" argument to the "--dump-config" command is now
1475 deprecated. When it works, it behaves the same as "short", which
1476 you should use instead. Closes ticket 33398.
1479 - Replace URLs from our old bugtracker so that they refer to the new
1480 bugtracker and wiki. Closes ticket 40101.
1483 - We no longer ship or build a "tor.service" file for use with
1484 systemd. No distribution included this script unmodified, and we
1485 don't have the expertise ourselves to maintain this in a way that
1486 all the various systemd-based distributions can use. Closes
1488 - We no longer ship support for the Android logging API. Modern
1489 versions of Android can use the syslog API instead. Closes
1491 - The "optimistic data" feature is now always on; there is no longer
1492 an option to disable it from the torrc file or from the consensus
1493 directory. Closes part of 40139.
1494 - The "usecreatefast" network parameter is now removed; there is no
1495 longer an option for authorities to turn it off. Closes part
1499 - Add unit tests for bandwidth statistics manipulation functions.
1500 Closes ticket 33812. Patch by MrSquanchee.
1502 o Code simplification and refactoring (autoconf):
1503 - Remove autoconf checks for unused funcs and headers. Closes ticket
1504 31699; Patch by @bduszel
1506 o Code simplification and refactoring (maintainer scripts):
1507 - Disable by default the pre-commit hook. Use the environment
1508 variable TOR_EXTRA_PRE_COMMIT_CHECKS in order to run it.
1509 Furthermore, stop running practracker in the pre-commit hook and
1510 make check-local. Closes ticket 40019.
1512 o Code simplification and refactoring (relay address):
1513 - Most of IPv4 representation was using "uint32_t". It has now been
1514 moved to use the internal "tor_addr_t" interface instead. This is
1515 so we can properly integrate IPv6 along IPv4 with common
1516 interfaces. Closes ticket 40043.
1518 o Documentation (manual page):
1519 - Move them from doc/ to doc/man/. Closes ticket 40044.
1520 - Describe the status of the "Sandbox" option more accurately. It is
1521 no longer "experimental", but it _is_ dependent on kernel and libc
1522 versions. Closes ticket 23378.
1524 o Documentation (tracing):
1525 - Document in depth the circuit subsystem trace events in the new
1526 doc/tracing/EventsCircuit.md. Closes ticket 40036.
1528 o Removed features (controller):
1529 - Remove the "GETINFO network-status" controller command. It has
1530 been deprecated since 0.3.1.1-alpha. Closes ticket 22473.
1533 Changes in version 0.4.4.7 - 2021-02-03
1534 Tor 0.4.4.7 backports numerous bugfixes from later releases,
1535 including one that made v3 onion services more susceptible to
1536 denial-of-service attacks, and a feature that makes some kinds of
1537 DoS attacks harder to perform.
1539 o Major bugfixes (onion service v3, backport from 0.4.5.3-rc):
1540 - Stop requiring a live consensus for v3 clients and services, and
1541 allow a "reasonably live" consensus instead. This allows v3 onion
1542 services to work even if the authorities fail to generate a
1543 consensus for more than 2 hours in a row. Fixes bug 40237; bugfix
1546 o Major feature (exit, backport from 0.4.5.5-rc):
1547 - Re-entry into the network is now denied at the Exit level to all
1548 relays' ORPorts and authorities' ORPorts and DirPorts. This change
1549 should help mitgate a set of denial-of-service attacks. Closes
1552 o Minor feature (build system, backport from 0.4.5.4-rc):
1553 - New "make lsp" command to generate the compile_commands.json file
1554 used by the ccls language server. The "bear" program is needed for
1555 this. Closes ticket 40227.
1557 o Minor features (compilation, backport from 0.4.5.2-rc):
1558 - Disable deprecation warnings when building with OpenSSL 3.0.0 or
1559 later. There are a number of APIs newly deprecated in OpenSSL
1560 3.0.0 that Tor still requires. (A later version of Tor will try to
1561 stop depending on these APIs.) Closes ticket 40165.
1563 o Minor features (crypto, backport from 0.4.5.3-rc):
1564 - Fix undefined behavior on our Keccak library. The bug only
1565 appeared on platforms with 32-byte CPU cache lines (e.g. armv5tel)
1566 and would result in wrong digests. Fixes bug 40210; bugfix on
1567 0.2.8.1-alpha. Thanks to Bernhard Übelacker, Arnd Bergmann and
1568 weasel for diagnosing this.
1570 o Minor bugfixes (compatibility, backport from 0.4.5.1-rc):
1571 - Strip '\r' characters when reading text files on Unix platforms.
1572 This should resolve an issue where a relay operator migrates a
1573 relay from Windows to Unix, but does not change the line ending of
1574 Tor's various state files to match the platform, and the CRLF line
1575 endings from Windows end up leaking into other files such as the
1576 extra-info document. Fixes bug 33781; bugfix on 0.0.9pre5.
1578 o Minor bugfixes (compilation, backport from 0.4.5.3-rc):
1579 - Fix a compilation warning about unreachable fallthrough
1580 annotations when building with "--enable-all-bugs-are-fatal" on
1581 some compilers. Fixes bug 40241; bugfix on 0.3.5.4-alpha.
1583 o Minor bugfixes (SOCKS5, backport from 0.4.5.3-rc):
1584 - Handle partial SOCKS5 messages correctly. Previously, our code
1585 would send an incorrect error message if it got a SOCKS5 request
1586 that wasn't complete. Fixes bug 40190; bugfix on 0.3.5.1-alpha.
1588 o Minor bugfixes (testing, backport from 0.4.5.2-alpha):
1589 - Fix the `config/parse_tcp_proxy_line` test so that it works
1590 correctly on systems where the DNS provider hijacks invalid
1591 queries. Fixes part of bug 40179; bugfix on 0.4.3.1-alpha.
1592 - Fix our Python reference-implementation for the v3 onion service
1593 handshake so that it works correctly with the version of hashlib
1594 provided by Python 3.9. Fixes part of bug 40179; bugfix
1596 - Fix the `tortls/openssl/log_one_error` test to work with OpenSSL
1597 3.0.0. Fixes bug 40170; bugfix on 0.2.8.1-alpha.
1600 Changes in version 0.4.3.8 - 2021-02-03
1601 Tor 0.4.3.8 backports numerous bugfixes from later releases,
1602 including one that made v3 onion services more susceptible to
1603 denial-of-service attacks, and a feature that makes some kinds of
1604 DoS attacks harder to perform.
1606 Note that this is, in all likelihood, the last release of Tor 0.4.3.x,
1607 which will reach end-of-life on 15 Feb 2021.
1609 o Major bugfixes (onion service v3, backport from 0.4.5.3-rc):
1610 - Stop requiring a live consensus for v3 clients and services, and
1611 allow a "reasonably live" consensus instead. This allows v3 onion
1612 services to work even if the authorities fail to generate a
1613 consensus for more than 2 hours in a row. Fixes bug 40237; bugfix
1616 o Major bugfixes (stats, onion services, backport from 0.4.4.5):
1617 - Fix a bug where we were undercounting the Tor network's total
1618 onion service traffic, by ignoring any traffic originating from
1619 clients. Now we count traffic from both clients and services.
1620 Fixes bug 40117; bugfix on 0.2.6.2-alpha.
1622 o Major feature (exit, backport from 0.4.5.5-rc):
1623 - Re-entry into the network is now denied at the Exit level to all
1624 relays' ORPorts and authorities' ORPorts and DirPorts. This change
1625 should help mitgate a set of denial-of-service attacks. Closes
1628 o Minor feature (build system, backport from 0.4.5.4-rc):
1629 - New "make lsp" command to generate the compile_commands.json file
1630 used by the ccls language server. The "bear" program is needed for
1631 this. Closes ticket 40227.
1633 o Minor features (compilation, backport from 0.4.5.2-rc):
1634 - Disable deprecation warnings when building with OpenSSL 3.0.0 or
1635 later. There are a number of APIs newly deprecated in OpenSSL
1636 3.0.0 that Tor still requires. (A later version of Tor will try to
1637 stop depending on these APIs.) Closes ticket 40165.
1639 o Minor features (crypto, backport from 0.4.5.3-rc):
1640 - Fix undefined behavior on our Keccak library. The bug only
1641 appeared on platforms with 32-byte CPU cache lines (e.g. armv5tel)
1642 and would result in wrong digests. Fixes bug 40210; bugfix on
1643 0.2.8.1-alpha. Thanks to Bernhard Übelacker, Arnd Bergmann and
1644 weasel for diagnosing this.
1646 o Minor bugfixes (compatibility, backport from 0.4.5.1-rc):
1647 - Strip '\r' characters when reading text files on Unix platforms.
1648 This should resolve an issue where a relay operator migrates a
1649 relay from Windows to Unix, but does not change the line ending of
1650 Tor's various state files to match the platform, and the CRLF line
1651 endings from Windows end up leaking into other files such as the
1652 extra-info document. Fixes bug 33781; bugfix on 0.0.9pre5.
1654 o Minor bugfixes (compilation, backport from 0.4.5.1-rc):
1655 - Resolve a compilation warning that could occur in
1656 test_connection.c. Fixes bug 40113; bugfix on 0.2.9.3-alpha.
1658 o Minor bugfixes (compilation, backport from 0.4.5.3-rc):
1659 - Fix a compilation warning about unreachable fallthrough
1660 annotations when building with "--enable-all-bugs-are-fatal" on
1661 some compilers. Fixes bug 40241; bugfix on 0.3.5.4-alpha.
1663 o Minor bugfixes (SOCKS5, backport from 0.4.5.3-rc):
1664 - Handle partial SOCKS5 messages correctly. Previously, our code
1665 would send an incorrect error message if it got a SOCKS5 request
1666 that wasn't complete. Fixes bug 40190; bugfix on 0.3.5.1-alpha.
1668 o Minor bugfixes (testing, backport from 0.4.5.2-alpha):
1669 - Fix the `config/parse_tcp_proxy_line` test so that it works
1670 correctly on systems where the DNS provider hijacks invalid
1671 queries. Fixes part of bug 40179; bugfix on 0.4.3.1-alpha.
1672 - Fix our Python reference-implementation for the v3 onion service
1673 handshake so that it works correctly with the version of hashlib
1674 provided by Python 3.9. Fixes part of bug 40179; bugfix
1676 - Fix the `tortls/openssl/log_one_error` test to work with OpenSSL
1677 3.0.0. Fixes bug 40170; bugfix on 0.2.8.1-alpha.
1680 Changes in version 0.3.5.13 - 2020-02-03
1681 Tor 0.3.5.13 backports numerous bugfixes from later releases,
1682 including one that made v3 onion services more susceptible to
1683 denial-of-service attacks, and a feature that makes some kinds of
1684 DoS attacks harder to perform.
1686 o Major bugfixes (onion service v3, backport from 0.4.5.3-rc):
1687 - Stop requiring a live consensus for v3 clients and services, and
1688 allow a "reasonably live" consensus instead. This allows v3 onion
1689 services to work even if the authorities fail to generate a
1690 consensus for more than 2 hours in a row. Fixes bug 40237; bugfix
1693 o Major bugfixes (stats, onion services, backport from 0.4.4.5):
1694 - Fix a bug where we were undercounting the Tor network's total
1695 onion service traffic, by ignoring any traffic originating from
1696 clients. Now we count traffic from both clients and services.
1697 Fixes bug 40117; bugfix on 0.2.6.2-alpha.
1699 o Major feature (exit, backport from 0.4.5.5-rc):
1700 - Re-entry into the network is now denied at the Exit level to all
1701 relays' ORPorts and authorities' ORPorts and DirPorts. This change
1702 should help mitgate a set of denial-of-service attacks. Closes
1705 o Minor feature (build system, backport from 0.4.5.4-rc):
1706 - New "make lsp" command to generate the compile_commands.json file
1707 used by the ccls language server. The "bear" program is needed for
1708 this. Closes ticket 40227.
1710 o Minor features (compilation, backport from 0.4.5.2-rc):
1711 - Disable deprecation warnings when building with OpenSSL 3.0.0 or
1712 later. There are a number of APIs newly deprecated in OpenSSL
1713 3.0.0 that Tor still requires. (A later version of Tor will try to
1714 stop depending on these APIs.) Closes ticket 40165.
1716 o Minor features (crypto, backport from 0.4.5.3-rc):
1717 - Fix undefined behavior on our Keccak library. The bug only
1718 appeared on platforms with 32-byte CPU cache lines (e.g. armv5tel)
1719 and would result in wrong digests. Fixes bug 40210; bugfix on
1720 0.2.8.1-alpha. Thanks to Bernhard Übelacker, Arnd Bergmann and
1721 weasel for diagnosing this.
1723 o Minor bugfixes (compatibility, backport from 0.4.5.1-rc):
1724 - Strip '\r' characters when reading text files on Unix platforms.
1725 This should resolve an issue where a relay operator migrates a
1726 relay from Windows to Unix, but does not change the line ending of
1727 Tor's various state files to match the platform, and the CRLF line
1728 endings from Windows end up leaking into other files such as the
1729 extra-info document. Fixes bug 33781; bugfix on 0.0.9pre5.
1731 o Minor bugfixes (compilation, backport from 0.4.5.1-rc):
1732 - Resolve a compilation warning that could occur in
1733 test_connection.c. Fixes bug 40113; bugfix on 0.2.9.3-alpha.
1735 o Minor bugfixes (compilation, backport from 0.4.5.3-rc):
1736 - Fix a compilation warning about unreachable fallthrough
1737 annotations when building with "--enable-all-bugs-are-fatal" on
1738 some compilers. Fixes bug 40241; bugfix on 0.3.5.4-alpha.
1740 o Minor bugfixes (SOCKS5, backport from 0.4.5.3-rc):
1741 - Handle partial SOCKS5 messages correctly. Previously, our code
1742 would send an incorrect error message if it got a SOCKS5 request
1743 that wasn't complete. Fixes bug 40190; bugfix on 0.3.5.1-alpha.
1745 o Minor bugfixes (testing, backport from 0.4.5.2-alpha):
1746 - Fix our Python reference-implementation for the v3 onion service
1747 handshake so that it works correctly with the version of hashlib
1748 provided by Python 3.9. Fixes part of bug 40179; bugfix
1750 - Fix the `tortls/openssl/log_one_error` test to work with OpenSSL
1751 3.0.0. Fixes bug 40170; bugfix on 0.2.8.1-alpha.
1754 Changes in version 0.4.4.6 - 2020-11-12
1755 Tor 0.4.4.6 is the second stable release in the 0.4.4.x series. It
1756 backports fixes from later releases, including a fix for TROVE-2020-
1757 005, a security issue that could be used, under certain cases, by an
1758 adversary to observe traffic patterns on a limited number of circuits
1759 intended for a different relay.
1761 o Major bugfixes (security, backport from 0.4.5.1-alpha):
1762 - When completing a channel, relays now check more thoroughly to
1763 make sure that it matches any pending circuits before attaching
1764 those circuits. Previously, address correctness and Ed25519
1765 identities were not checked in this case, but only when extending
1766 circuits on an existing channel. Fixes bug 40080; bugfix on
1767 0.2.7.2-alpha. Resolves TROVE-2020-005.
1769 o Minor features (directory authorities, backport from 0.4.5.1-alpha):
1770 - Authorities now list a different set of protocols as required and
1771 recommended. These lists have been chosen so that only truly
1772 recommended and/or required protocols are included, and so that
1773 clients using 0.2.9 or later will continue to work (even though
1774 they are not supported), whereas only relays running 0.3.5 or
1775 later will meet the requirements. Closes ticket 40162.
1776 - Make it possible to specify multiple ConsensusParams torrc lines.
1777 Now directory authority operators can for example put the main
1778 ConsensusParams config in one torrc file and then add to it from a
1779 different torrc file. Closes ticket 40164.
1781 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
1782 - Tor no longer allows subprotocol versions larger than 63.
1783 Previously version numbers up to UINT32_MAX were allowed, which
1784 significantly complicated our code. Implements proposal 318;
1785 closes ticket 40133.
1787 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
1788 - Fix a rendezvous cache unit test that was triggering an underflow
1789 on the global rend cache allocation. Fixes bug 40125; bugfix
1791 - Fix another rendezvous cache unit test that was triggering an
1792 underflow on the global rend cache allocation. Fixes bug 40126;
1793 bugfix on 0.2.8.1-alpha.
1795 o Minor bugfixes (compilation, backport from 0.4.5.1-alpha):
1796 - Fix compiler warnings that would occur when building with
1797 "--enable-all-bugs-are-fatal" and "--disable-module-relay" at the
1798 same time. Fixes bug 40129; bugfix on 0.4.4.1-alpha.
1799 - Resolve a compilation warning that could occur in
1800 test_connection.c. Fixes bug 40113; bugfix on 0.2.9.3-alpha.
1802 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
1803 - Remove a debug logging statement that uselessly spammed the logs.
1804 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
1806 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
1807 - Avoid a fatal assert() when failing to create a listener
1808 connection for an address that was in use. Fixes bug 40073; bugfix
1811 o Minor bugfixes (v2 onion services, backport from 0.4.5.1-alpha):
1812 - For HSFETCH commands on v2 onion services addresses, check the
1813 length of bytes decoded, not the base32 length. Fixes bug 34400;
1814 bugfix on 0.4.1.1-alpha. Patch by Neel Chauhan.
1817 Changes in version 0.4.3.7 - 2020-11-12
1818 Tor 0.4.3.7 backports several bugfixes from later releases. It
1819 includes a fix for TROVE-2020-005, a security issue that could be
1820 used, under certain cases, by an adversary to observe traffic patterns
1821 on a limited number of circuits intended for a different relay.
1823 Please be aware that support for the 0.4.3.x series will end on 15
1824 February 2021. Please upgrade to 0.4.4.x or 0.4.5.x before then, or
1825 downgrade to 0.3.5.x, which will be supported until at least 1
1828 o Major features (fallback directory list, backport form 0.4.4.3-alpha):
1829 - Replace the 148 fallback directories originally included in Tor
1830 0.4.1.4-rc (of which around 105 are still functional) with a list
1831 of 144 fallbacks generated in July 2020. Closes ticket 40061.
1833 o Major bugfixes (security, backport from 0.4.5.1-alpha):
1834 - When completing a channel, relays now check more thoroughly to
1835 make sure that it matches any pending circuits before attaching
1836 those circuits. Previously, address correctness and Ed25519
1837 identities were not checked in this case, but only when extending
1838 circuits on an existing channel. Fixes bug 40080; bugfix on
1839 0.2.7.2-alpha. Resolves TROVE-2020-005.
1841 o Major bugfixes (NSS, backport from 0.4.4.3-alpha):
1842 - When running with NSS enabled, make sure that NSS knows to expect
1843 nonblocking sockets. Previously, we set our TCP sockets as
1844 nonblocking, but did not tell NSS, which in turn could lead to
1845 unexpected blocking behavior. Fixes bug 40035; bugfix
1848 o Minor features (security, backport from 0.4.4.4-rc):
1849 - Channels using obsolete versions of the Tor link protocol are no
1850 longer allowed to circumvent address-canonicity checks. (This is
1851 only a minor issue, since such channels have no way to set ed25519
1852 keys, and therefore should always be rejected for circuits that
1853 specify ed25519 identities.) Closes ticket 40081.
1855 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
1856 - Tor no longer allows subprotocol versions larger than 63.
1857 Previously version numbers up to UINT32_MAX were allowed, which
1858 significantly complicated our code. Implements proposal 318;
1859 closes ticket 40133.
1861 o Minor features (tests, backport from 0.4.4.5):
1862 - Our "make check" target now runs the unit tests in 8 parallel
1863 chunks. Doing this speeds up hardened CI builds by more than a
1864 factor of two. Closes ticket 40098.
1866 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
1867 - Fix a rendezvous cache unit test that was triggering an underflow
1868 on the global rend cache allocation. Fixes bug 40125; bugfix
1870 - Fix another rendezvous cache unit test that was triggering an
1871 underflow on the global rend cache allocation. Fixes bug 40126;
1872 bugfix on 0.2.8.1-alpha.
1874 o Minor bugfixes (correctness, buffers, backport from 0.4.4.4-rc):
1875 - Fix a correctness bug that could cause an assertion failure if we
1876 ever tried using the buf_move_all() function with an empty input
1877 buffer. As far as we know, no released versions of Tor do this.
1878 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
1880 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
1881 - Remove a debug logging statement that uselessly spammed the logs.
1882 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
1884 o Minor bugfixes (rate limiting, bridges, pluggable transports, backport from 0.4.4.4-rc):
1885 - On a bridge, treat all connections from an ExtORPort as remote by
1886 default for the purposes of rate-limiting. Previously, bridges
1887 would treat the connection as local unless they explicitly
1888 received a "USERADDR" command. ExtORPort connections still count
1889 as local if there is a USERADDR command with an explicit local
1890 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
1892 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
1893 - Avoid a fatal assert() when failing to create a listener
1894 connection for an address that was in use. Fixes bug 40073; bugfix
1897 o Minor bugfixes (relay, usability, backport from 0.4.4.3-alpha):
1898 - Adjust the rules for when to warn about having too many
1899 connections to other relays. Previously we'd tolerate up to 1.5
1900 connections per relay on average. Now we tolerate more connections
1901 for directory authorities, and raise the number of total
1902 connections we need to see before we warn. Fixes bug 33880; bugfix
1905 o Minor bugfixes (tests, 0.4.4.5):
1906 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
1907 on its own. Previously, it would exit with an error. Fixes bug
1908 40099; bugfix on 0.2.8.1-alpha.
1910 o Minor bugfixes (v2 onion services, backport from 0.4.5.1-alpha):
1911 - For HSFETCH commands on v2 onion services addresses, check the
1912 length of bytes decoded, not the base32 length. Fixes bug 34400;
1913 bugfix on 0.4.1.1-alpha. Patch by Neel Chauhan.
1915 o Minor bugfixes (windows, backport from 0.4.4.4-rc):
1916 - Fix a bug that prevented Tor from starting if its log file grew
1917 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
1919 o Deprecated features (onion service v2, backport form 0.4.4.2-alpha):
1920 - Add a deprecation warning for version 2 onion services. Closes
1923 o Removed features (backport from 0.4.4.3-alpha):
1924 - Our "check-local" test target no longer tries to use the
1925 Coccinelle semantic patching tool parse all the C files. While it
1926 is a good idea to try to make sure Coccinelle works on our C
1927 before we run a Coccinelle patch, doing so on every test run has
1928 proven to be disruptive. You can still run this tool manually with
1929 "make check-cocci". Closes ticket 40030. ticket 40030.
1932 Changes in version 0.3.5.12 - 2020-11-12
1933 Tor 0.4.3.7 backports several bugfixes from later releases. It
1934 includes a fix for TROVE-2020-005, a security issue that could be
1935 used, under certain cases, by an adversary to observe traffic patterns
1936 on a limited number of circuits intended for a different relay.
1938 o Major features (fallback directory list, backport form 0.4.4.3-alpha):
1939 - Replace the 148 fallback directories originally included in Tor
1940 0.4.1.4-rc (of which around 105 are still functional) with a list
1941 of 144 fallbacks generated in July 2020. Closes ticket 40061.
1943 o Major bugfixes (security, backport from 0.4.5.1-alpha):
1944 - When completing a channel, relays now check more thoroughly to
1945 make sure that it matches any pending circuits before attaching
1946 those circuits. Previously, address correctness and Ed25519
1947 identities were not checked in this case, but only when extending
1948 circuits on an existing channel. Fixes bug 40080; bugfix on
1949 0.2.7.2-alpha. Resolves TROVE-2020-005.
1951 o Major bugfixes (NSS, backport from 0.4.4.3-alpha):
1952 - When running with NSS enabled, make sure that NSS knows to expect
1953 nonblocking sockets. Previously, we set our TCP sockets as
1954 nonblocking, but did not tell NSS, which in turn could lead to
1955 unexpected blocking behavior. Fixes bug 40035; bugfix
1958 o Minor features (security, backport from 0.4.4.4-rc):
1959 - Channels using obsolete versions of the Tor link protocol are no
1960 longer allowed to circumvent address-canonicity checks. (This is
1961 only a minor issue, since such channels have no way to set ed25519
1962 keys, and therefore should always be rejected for circuits that
1963 specify ed25519 identities.) Closes ticket 40081.
1965 o Minor features (debugging, directory system):
1966 - Don't crash when we find a non-guard with a guard-fraction value
1967 set. Instead, log a bug warning, in an attempt to figure out how
1968 this happened. Diagnostic for ticket 32868.
1970 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
1971 - Tor no longer allows subprotocol versions larger than 63.
1972 Previously version numbers up to UINT32_MAX were allowed, which
1973 significantly complicated our code. Implements proposal 318;
1974 closes ticket 40133.
1976 o Minor features (tests, backport from 0.4.4.5):
1977 - Our "make check" target now runs the unit tests in 8 parallel
1978 chunks. Doing this speeds up hardened CI builds by more than a
1979 factor of two. Closes ticket 40098.
1981 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
1982 - Fix a rendezvous cache unit test that was triggering an underflow
1983 on the global rend cache allocation. Fixes bug 40125; bugfix
1985 - Fix another rendezvous cache unit test that was triggering an
1986 underflow on the global rend cache allocation. Fixes bug 40126;
1987 bugfix on 0.2.8.1-alpha.
1989 o Minor bugfixes (correctness, buffers, backport from 0.4.4.4-rc):
1990 - Fix a correctness bug that could cause an assertion failure if we
1991 ever tried using the buf_move_all() function with an empty input
1992 buffer. As far as we know, no released versions of Tor do this.
1993 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
1995 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
1996 - Remove a debug logging statement that uselessly spammed the logs.
1997 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
1999 o Minor bugfixes (rate limiting, bridges, pluggable transports, backport from 0.4.4.4-rc):
2000 - On a bridge, treat all connections from an ExtORPort as remote by
2001 default for the purposes of rate-limiting. Previously, bridges
2002 would treat the connection as local unless they explicitly
2003 received a "USERADDR" command. ExtORPort connections still count
2004 as local if there is a USERADDR command with an explicit local
2005 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
2007 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
2008 - Avoid a fatal assert() when failing to create a listener
2009 connection for an address that was in use. Fixes bug 40073; bugfix
2012 o Minor bugfixes (relay, usability, backport from 0.4.4.3-alpha):
2013 - Adjust the rules for when to warn about having too many
2014 connections to other relays. Previously we'd tolerate up to 1.5
2015 connections per relay on average. Now we tolerate more connections
2016 for directory authorities, and raise the number of total
2017 connections we need to see before we warn. Fixes bug 33880; bugfix
2020 o Minor bugfixes (relays, backport from 0.4.4.1-alpha):
2021 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
2022 descriptors, when the IPv6 port was configured as "auto". Fixes
2023 bug 32588; bugfix on 0.2.3.9-alpha.
2025 o Minor bugfixes (tests, 0.4.4.5):
2026 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
2027 on its own. Previously, it would exit with an error. Fixes bug
2028 40099; bugfix on 0.2.8.1-alpha.
2030 o Minor bugfixes (windows, backport from 0.4.4.4-rc):
2031 - Fix a bug that prevented Tor from starting if its log file grew
2032 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
2034 o Deprecated features (onion service v2, backport form 0.4.4.2-alpha):
2035 - Add a deprecation warning for version 2 onion services. Closes
2038 Changes in version 0.4.4.5 - 2020-09-15
2039 Tor 0.4.4.5 is the first stable release in the 0.4.4.x series. This
2040 series improves our guard selection algorithms, adds v3 onion balance
2041 support, improves the amount of code that can be disabled when running
2042 without relay support, and includes numerous small bugfixes and
2043 enhancements. It also lays the ground for some IPv6 features that
2044 we'll be developing more in the next (0.4.5) series.
2046 Per our support policy, we support each stable release series for nine
2047 months after its first stable release, or three months after the first
2048 stable release of the next series: whichever is longer. This means
2049 that 0.4.4.x will be supported until around June 2021--or later, if
2050 0.4.5.x is later than anticipated.
2052 Note also that support for 0.4.2.x has just ended; support for 0.4.3
2053 will continue until Feb 15, 2021. We still plan to continue supporting
2054 0.3.5.x, our long-term stable series, until Feb 2022.
2056 Below are the changes since 0.4.3.6-rc. For a complete list of changes
2057 since 0.4.4.4-rc, see the ChangeLog file.
2059 o Major features (Proposal 310, performance + security):
2060 - Implements Proposal 310, "Bandaid on guard selection". Proposal
2061 310 solves load-balancing issues with older versions of the guard
2062 selection algorithm, and improves its security. Under this new
2063 algorithm, a newly selected guard never becomes Primary unless all
2064 previously sampled guards are unreachable. Implements
2065 recommendation from 32088. (Proposal 310 is linked to the CLAPS
2066 project researching optimal client location-aware path selections.
2067 This project is a collaboration between the UCLouvain Crypto Group,
2068 the U.S. Naval Research Laboratory, and Princeton University.)
2070 o Major features (fallback directory list):
2071 - Replace the 148 fallback directories originally included in Tor
2072 0.4.1.4-rc (of which around 105 are still functional) with a list
2073 of 144 fallbacks generated in July 2020. Closes ticket 40061.
2075 o Major features (IPv6, relay):
2076 - Consider IPv6-only EXTEND2 cells valid on relays. Log a protocol
2077 warning if the IPv4 or IPv6 address is an internal address, and
2078 internal addresses are not allowed. But continue to use the other
2079 address, if it is valid. Closes ticket 33817.
2080 - If a relay can extend over IPv4 and IPv6, and both addresses are
2081 provided, it chooses between them uniformly at random. Closes
2083 - Re-use existing IPv6 connections for circuit extends. Closes
2085 - Relays may extend circuits over IPv6, if the relay has an IPv6
2086 ORPort, and the client supplies the other relay's IPv6 ORPort in
2087 the EXTEND2 cell. IPv6 extends will be used by the relay IPv6
2088 ORPort self-tests in 33222. Closes ticket 33817.
2090 o Major features (v3 onion services):
2091 - Allow v3 onion services to act as OnionBalance backend instances,
2092 by using the HiddenServiceOnionBalanceInstance torrc option.
2093 Closes ticket 32709.
2095 o Major bugfixes (NSS):
2096 - When running with NSS enabled, make sure that NSS knows to expect
2097 nonblocking sockets. Previously, we set our TCP sockets as
2098 nonblocking, but did not tell NSS, which in turn could lead to
2099 unexpected blocking behavior. Fixes bug 40035; bugfix
2102 o Major bugfixes (onion services, DoS):
2103 - Correct handling of parameters for the onion service DoS defense.
2104 Previously, the consensus parameters for the onion service DoS
2105 defenses were overwriting the parameters set by the service
2106 operator using HiddenServiceEnableIntroDoSDefense. Fixes bug
2107 40109; bugfix on 0.4.2.1-alpha.
2109 o Major bugfixes (stats, onion services):
2110 - Fix a bug where we were undercounting the Tor network's total
2111 onion service traffic, by ignoring any traffic originating from
2112 clients. Now we count traffic from both clients and services.
2113 Fixes bug 40117; bugfix on 0.2.6.2-alpha.
2115 o Minor features (security):
2116 - Channels using obsolete versions of the Tor link protocol are no
2117 longer allowed to circumvent address-canonicity checks. (This is
2118 only a minor issue, since such channels have no way to set ed25519
2119 keys, and therefore should always be rejected for circuits that
2120 specify ed25519 identities.) Closes ticket 40081.
2122 o Minor features (bootstrap reporting):
2123 - Report more detailed reasons for bootstrap failure when the
2124 failure happens due to a TLS error. Previously we would just call
2125 these errors "MISC" when they happened during read, and "DONE"
2126 when they happened during any other TLS operation. Closes
2129 o Minor features (client-only compilation):
2130 - Disable more code related to the ext_orport protocol when
2131 compiling without support for relay mode. Closes ticket 33368.
2132 - Disable more of our self-testing code when support for relay mode
2133 is disabled. Closes ticket 33370.
2134 - Most server-side DNS code is now disabled when building without
2135 support for relay mode. Closes ticket 33366.
2137 o Minor features (code safety):
2138 - Check for failures of tor_inet_ntop() and tor_inet_ntoa()
2139 functions in DNS and IP address processing code, and adjust
2140 codepaths to make them less likely to crash entire Tor instances.
2141 Resolves issue 33788.
2143 o Minor features (continuous integration):
2144 - Run unit-test and integration test (Stem, Chutney) jobs with
2145 ALL_BUGS_ARE_FATAL macro being enabled on Travis and Appveyor.
2146 Resolves ticket 32143.
2148 o Minor features (control port):
2149 - If a ClientName was specified in ONION_CLIENT_AUTH_ADD for an
2150 onion service, display it when we use ONION_CLIENT_AUTH_VIEW.
2151 Closes ticket 40089. Patch by Neel Chauhan.
2152 - Return a descriptive error message from the 'GETINFO status/fresh-
2153 relay-descs' command on the control port. Previously, we returned
2154 a generic error of "Error generating descriptor". Closes ticket
2155 32873. Patch by Neel Chauhan.
2157 o Minor features (defense in depth):
2158 - Wipe more data from connection address fields before returning
2159 them to the memory heap. Closes ticket 6198.
2161 o Minor features (denial-of-service memory limiter):
2162 - Allow the user to configure even lower values for the
2163 MaxMemInQueues parameter. Relays now enforce a minimum of 64 MB,
2164 when previously the minimum was 256 MB. On clients, there is no
2165 minimum. Relays and clients will both warn if the value is set so
2166 low that Tor is likely to stop working. Closes ticket 24308.
2168 o Minor features (developer tooling):
2169 - Add a script to help check the alphabetical ordering of option
2170 names in the manual page. Closes ticket 33339.
2171 - Refrain from listing all .a files that are generated by the Tor
2172 build in .gitignore. Add a single wildcard *.a entry that covers
2173 all of them for present and future. Closes ticket 33642.
2174 - Add a script ("git-install-tools.sh") to install git hooks and
2175 helper scripts. Closes ticket 33451.
2177 o Minor features (directory authority):
2178 - Authorities now recommend the protocol versions that are supported
2179 by Tor 0.3.5 and later. (Earlier versions of Tor have been
2180 deprecated since January of this year.) This recommendation will
2181 cause older clients and relays to give a warning on startup, or
2182 when they download a consensus directory. Closes ticket 32696.
2184 o Minor features (directory authority, shared random):
2185 - Refactor more authority-only parts of the shared-random scheduling
2186 code to reside in the dirauth module, and to be disabled when
2187 compiling with --disable-module-dirauth. Closes ticket 33436.
2189 o Minor features (directory):
2190 - Remember the number of bytes we have downloaded for each directory
2191 purpose while bootstrapping, and while fully bootstrapped. Log
2192 this information as part of the heartbeat message. Closes
2195 o Minor features (entry guards):
2196 - Reinstate support for GUARD NEW/UP/DOWN control port events.
2197 Closes ticket 40001.
2199 o Minor features (IPv6 support):
2200 - Adds IPv6 support to tor_addr_is_valid(). Adds tests for the above
2201 changes and tor_addr_is_null(). Closes ticket 33679. Patch
2203 - Allow clients and relays to send dual-stack and IPv6-only EXTEND2
2204 cells. Parse dual-stack and IPv6-only EXTEND2 cells on relays.
2205 Closes ticket 33901.
2207 o Minor features (linux seccomp2 sandbox, portability):
2208 - Allow Tor to build on platforms where it doesn't know how to
2209 report which syscall caused the linux seccomp2 sandbox to fail.
2210 This change should make the sandbox code more portable to less
2211 common Linux architectures. Closes ticket 34382.
2212 - Permit the unlinkat() syscall, which some Libc implementations use
2213 to implement unlink(). Closes ticket 33346.
2215 o Minor features (logging):
2216 - When trying to find our own address, add debug-level logging to
2217 report the sources of candidate addresses. Closes ticket 32888.
2219 o Minor features (onion service client, SOCKS5):
2220 - Add 3 new SocksPort ExtendedErrors (F2, F3, F7) that reports back
2221 new type of onion service connection failures. The semantics of
2222 these error codes are documented in proposal 309. Closes
2225 o Minor features (onion service v3):
2226 - If a service cannot upload its descriptor(s), log why at INFO
2227 level. Closes ticket 33400; bugfix on 0.3.2.1-alpha.
2229 o Minor features (python scripts):
2230 - Stop assuming that /usr/bin/python exists. Instead of using a
2231 hardcoded path in scripts that still use Python 2, use
2232 /usr/bin/env, similarly to the scripts that use Python 3. Fixes
2233 bug 33192; bugfix on 0.4.2.
2235 o Minor features (testing, architecture):
2236 - Our test scripts now double-check that subsystem initialization
2237 order is consistent with the inter-module dependencies established
2238 by our .may_include files. Implements ticket 31634.
2239 - Initialize all subsystems at the beginning of our unit test
2240 harness, to avoid crashes due to uninitialized subsystems. Follow-
2241 up from ticket 33316.
2242 - Our "make check" target now runs the unit tests in 8 parallel
2243 chunks. Doing this speeds up hardened CI builds by more than a
2244 factor of two. Closes ticket 40098.
2246 o Minor features (v3 onion services):
2247 - Add v3 onion service status to the dumpstats() call which is
2248 triggered by a SIGUSR1 signal. Previously, we only did v2 onion
2249 services. Closes ticket 24844. Patch by Neel Chauhan.
2251 o Minor features (windows):
2252 - Add support for console control signals like Ctrl+C in Windows.
2253 Closes ticket 34211. Patch from Damon Harris (TheDcoder).
2255 o Minor bugfixes (control port, onion service):
2256 - Consistently use 'address' in "Invalid v3 address" response to
2257 ONION_CLIENT_AUTH commands. Previously, we would sometimes say
2258 'addr'. Fixes bug 40005; bugfix on 0.4.3.1-alpha.
2260 o Minor bugfixes (correctness, buffers):
2261 - Fix a correctness bug that could cause an assertion failure if we
2262 ever tried using the buf_move_all() function with an empty input
2263 buffer. As far as we know, no released versions of Tor do this.
2264 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
2266 o Minor bugfixes (directory authorities):
2267 - Directory authorities now reject votes that arrive too late. In
2268 particular, once an authority has started fetching missing votes,
2269 it no longer accepts new votes posted by other authorities. This
2270 change helps prevent a consensus split, where only some authorities
2271 have the late vote. Fixes bug 4631; bugfix on 0.2.0.5-alpha.
2273 o Minor bugfixes (git scripts):
2274 - Stop executing the checked-out pre-commit hook from the pre-push
2275 hook. Instead, execute the copy in the user's git directory. Fixes
2276 bug 33284; bugfix on 0.4.1.1-alpha.
2278 o Minor bugfixes (initialization):
2279 - Initialize the subsystems in our code in an order more closely
2280 corresponding to their dependencies, so that every system is
2281 initialized before the ones that (theoretically) depend on it.
2282 Fixes bug 33316; bugfix on 0.4.0.1-alpha.
2284 o Minor bugfixes (IPv4, relay):
2285 - Check for invalid zero IPv4 addresses and ports when sending and
2286 receiving extend cells. Fixes bug 33900; bugfix on 0.2.4.8-alpha.
2288 o Minor bugfixes (IPv6, relay):
2289 - Consider IPv6 addresses when checking if a connection is
2290 canonical. In 17604, relays assumed that a remote relay could
2291 consider an IPv6 connection canonical, but did not set the
2292 canonical flag on their side of the connection. Fixes bug 33899;
2293 bugfix on 0.3.1.1-alpha.
2294 - Log IPv6 addresses on connections where this relay is the
2295 responder. Previously, responding relays would replace the remote
2296 IPv6 address with the IPv4 address from the consensus. Fixes bug
2297 33899; bugfix on 0.3.1.1-alpha.
2299 o Minor bugfixes (linux seccomp2 sandbox):
2300 - Fix a regression on sandboxing rules for the openat() syscall. The
2301 fix for bug 25440 fixed the problem on systems with glibc >= 2.27
2302 but broke with versions of glibc. We now choose a rule based on
2303 the glibc version. Patch from Daniel Pinto. Fixes bug 27315;
2305 - Makes the seccomp sandbox allow the correct syscall for opendir
2306 according to the running glibc version. This fixes crashes when
2307 reloading torrc with sandbox enabled when running on glibc 2.15 to
2308 2.21 and 2.26. Patch from Daniel Pinto. Fixes bug 40020; bugfix
2311 o Minor bugfixes (logging, testing):
2312 - Make all of tor's assertion macros support the ALL_BUGS_ARE_FATAL
2313 and DISABLE_ASSERTS_IN_UNIT_TESTS debugging modes. (IF_BUG_ONCE()
2314 used to log a non-fatal warning, regardless of the debugging
2315 mode.) Fixes bug 33917; bugfix on 0.2.9.1-alpha.
2316 - Remove surprising empty line in the INFO-level log about circuit
2317 build timeout. Fixes bug 33531; bugfix on 0.3.3.1-alpha.
2319 o Minor bugfixes (mainloop):
2320 - Better guard against growing a buffer past its maximum 2GB in
2321 size. Fixes bug 33131; bugfix on 0.3.0.4-rc.
2323 o Minor bugfixes (onion service v3 client):
2324 - Remove a BUG() warning that could occur naturally. Fixes bug
2325 34087; bugfix on 0.3.2.1-alpha.
2327 o Minor bugfixes (onion service, logging):
2328 - Fix a typo in a log message PublishHidServDescriptors is set to 0.
2329 Fixes bug 33779; bugfix on 0.3.2.1-alpha.
2331 o Minor bugfixes (onion services v3):
2332 - Avoid a non-fatal assertion failure in certain edge-cases when
2333 opening an intro circuit as a client. Fixes bug 34084; bugfix
2336 o Minor bugfixes (protocol versions):
2337 - Sort tor's supported protocol version lists, as recommended by the
2338 tor directory specification. Fixes bug 33285; bugfix
2341 o Minor bugfixes (rate limiting, bridges, pluggable transports):
2342 - On a bridge, treat all connections from an ExtORPort as remote by
2343 default for the purposes of rate-limiting. Previously, bridges
2344 would treat the connection as local unless they explicitly
2345 received a "USERADDR" command. ExtORPort connections still count
2346 as local if there is a USERADDR command with an explicit local
2347 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
2349 o Minor bugfixes (refactoring):
2350 - Lift circuit_build_times_disabled() out of the
2351 circuit_expire_building() loop, to save CPU time when there are
2352 many circuits open. Fixes bug 33977; bugfix on 0.3.5.9.
2354 o Minor bugfixes (relay, self-testing):
2355 - When starting up as a relay, if we haven't been able to verify
2356 that we're reachable, only launch reachability tests at most once
2357 a minute. Previously, we had been launching tests up to once a
2358 second, which was needlessly noisy. Fixes bug 40083; bugfix
2361 o Minor bugfixes (relay, usability):
2362 - Adjust the rules for when to warn about having too many
2363 connections to other relays. Previously we'd tolerate up to 1.5
2364 connections per relay on average. Now we tolerate more connections
2365 for directory authorities, and raise the number of total
2366 connections we need to see before we warn. Fixes bug 33880; bugfix
2369 o Minor bugfixes (SOCKS, onion service client):
2370 - Detect v3 onion service addresses of the wrong length when
2371 returning the F6 ExtendedErrors code. Fixes bug 33873; bugfix
2374 o Minor bugfixes (tests):
2375 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
2376 on its own. Previously, it would exit with an error. Fixes bug
2377 40099; bugfix on 0.2.8.1-alpha.
2379 o Minor bugfixes (v3 onion services):
2380 - Remove a BUG() warning that could trigger in certain unlikely
2381 edge-cases. Fixes bug 34086; bugfix on 0.3.2.1-alpha.
2382 - Remove a BUG() that was causing a stacktrace when a descriptor
2383 changed at an unexpected time. Fixes bug 28992; bugfix
2386 o Minor bugfixes (windows):
2387 - Fix a bug that prevented Tor from starting if its log file grew
2388 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
2390 o Code simplification and refactoring:
2391 - Define and use a new constant TOR_ADDRPORT_BUF_LEN which is like
2392 TOR_ADDR_BUF_LEN but includes enough space for an IP address,
2393 brackets, separating colon, and port number. Closes ticket 33956.
2394 Patch by Neel Chauhan.
2395 - Merge the orconn and ocirc events into the "core" subsystem, which
2396 manages or connections and origin circuits. Previously they were
2397 isolated in subsystems of their own.
2398 - Move LOG_PROTOCOL_WARN to app/config. Resolves a dependency
2399 inversion. Closes ticket 33633.
2400 - Move the circuit extend code to the relay module. Split the
2401 circuit extend function into smaller functions. Closes
2403 - Rewrite port_parse_config() to use the default port flags from
2404 port_cfg_new(). Closes ticket 32994. Patch by MrSquanchee.
2405 - Updated comments in 'scheduler.c' to reflect old code changes, and
2406 simplified the scheduler channel state change code. Closes
2408 - Refactor configuration parsing to use the new config subsystem
2409 code. Closes ticket 33014.
2410 - Move a series of functions related to address resolving into their
2411 own files. Closes ticket 33789.
2414 - Replace most http:// URLs in our code and documentation with
2415 https:// URLs. (We have left unchanged the code in src/ext/, and
2416 the text in LICENSE.) Closes ticket 31812. Patch from Jeremy Rand.
2417 - Document the limitations of using %include on config files with
2418 seccomp sandbox enabled. Fixes documentation bug 34133; bugfix on
2419 0.3.1.1-alpha. Patch by Daniel Pinto.
2422 - Our "check-local" test target no longer tries to use the
2423 Coccinelle semantic patching tool parse all the C files. While it
2424 is a good idea to try to make sure Coccinelle works on our C
2425 before we run a Coccinelle patch, doing so on every test run has
2426 proven to be disruptive. You can still run this tool manually with
2427 "make check-cocci". Closes ticket 40030.
2428 - Remove the ClientAutoIPv6ORPort option. This option attempted to
2429 randomly choose between IPv4 and IPv6 for client connections, and
2430 wasn't a true implementation of Happy Eyeballs. Often, this option
2431 failed on IPv4-only or IPv6-only connections. Closes ticket 32905.
2432 Patch by Neel Chauhan.
2433 - Stop shipping contrib/dist/rc.subr file, as it is not being used
2434 on FreeBSD anymore. Closes issue 31576.
2437 - Add a basic IPv6 test to "make test-network". This test only runs
2438 when the local machine has an IPv6 stack. Closes ticket 33300.
2439 - Add test-network-ipv4 and test-network-ipv6 jobs to the Makefile.
2440 These jobs run the IPv4-only and dual-stack chutney flavours from
2441 test-network-all. Closes ticket 33280.
2442 - Remove a redundant distcheck job. Closes ticket 33194.
2443 - Run the test-network-ipv6 Makefile target in the Travis CI IPv6
2444 chutney job. This job runs on macOS, so it's a bit slow. Closes
2446 - Sort the Travis jobs in order of speed. Putting the slowest jobs
2447 first takes full advantage of Travis job concurrency. Closes
2449 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
2450 previously configured to fast_finish (which requires
2451 allow_failure), to speed up the build. Closes ticket 33195.
2452 - Test v3 onion services to tor's mixed IPv4 chutney network. And
2453 add a mixed IPv6 chutney network. These networks are used in the
2454 test-network-all, test-network-ipv4, and test-network-ipv6 make
2455 targets. Closes ticket 33334.
2456 - Use the "bridges+hs-v23" chutney network flavour in "make test-
2457 network". This test requires a recent version of chutney (mid-
2458 February 2020). Closes ticket 28208.
2459 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
2460 tool to produce detailed diagnostic output. Closes ticket 32792.
2462 o Deprecated features (onion service v2):
2463 - Add a deprecation warning for version 2 onion services. Closes
2466 o Documentation (manual page):
2467 - Add cross reference links and a table of contents to the HTML tor
2468 manual page. Closes ticket 33369. Work by Swati Thacker as part of
2469 Google Season of Docs.
2470 - Alphabetize the Denial of Service Mitigation Options, Directory
2471 Authority Server Options, Hidden Service Options, and Testing
2472 Network Options sections of the tor(1) manual page. Closes ticket
2473 33275. Work by Swati Thacker as part of Google Season of Docs.
2474 - Refrain from mentioning nicknames in manpage section for MyFamily
2475 torrc option. Resolves issue 33417.
2476 - Updated the options set by TestingTorNetwork in the manual page.
2477 Closes ticket 33778.
2480 Changes in version 0.3.5.11 - 2020-07-09
2481 Tor 0.3.5.11 backports fixes from later tor releases, including several
2482 usability, portability, and reliability fixes.
2484 This release also fixes TROVE-2020-001, a medium-severity denial of
2485 service vulnerability affecting all versions of Tor when compiled with
2486 the NSS encryption library. (This is not the default configuration.)
2487 Using this vulnerability, an attacker could cause an affected Tor
2488 instance to crash remotely. This issue is also tracked as CVE-2020-
2489 15572. Anybody running a version of Tor built with the NSS library
2490 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
2493 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
2494 - Fix a crash due to an out-of-bound memory access when Tor is
2495 compiled with NSS support. Fixes bug 33119; bugfix on
2496 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
2499 o Major bugfixes (DoS defenses, bridges, pluggable transport, backport from 0.4.3.4-rc):
2500 - Fix a bug that was preventing DoS defenses from running on bridges
2501 with a pluggable transport. Previously, the DoS subsystem was not
2502 given the transport name of the client connection, thus failed to
2503 find the GeoIP cache entry for that client address. Fixes bug
2504 33491; bugfix on 0.3.3.2-alpha.
2506 o Minor features (testing, backport from 0.4.3.4-rc):
2507 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
2508 variable to specify a list of space-separated test cases that
2509 should not be executed. We will use this to disable certain tests
2510 that are failing on Appveyor because of mismatched OpenSSL
2511 libraries. Part of ticket 33643.
2513 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
2514 - Use the correct 64-bit printf format when compiling with MINGW on
2515 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
2517 o Minor bugfix (relay, configuration, backport from 0.4.3.3-alpha):
2518 - Warn if the ContactInfo field is not set, and tell the relay
2519 operator that not having a ContactInfo field set might cause their
2520 relay to get rejected in the future. Fixes bug 33361; bugfix
2523 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
2524 - Resume use of preemptively-built circuits when UseEntryGuards is set
2525 to 0. We accidentally disabled this feature with that config
2526 setting, leading to slower load times. Fixes bug 34303; bugfix
2529 o Minor bugfixes (compiler compatibility, backport from 0.4.3.5):
2530 - Avoid compiler warnings from Clang 10 related to the use of GCC-
2531 style "/* falls through */" comments. Both Clang and GCC allow
2532 __attribute__((fallthrough)) instead, so that's what we're using
2533 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
2535 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
2536 - Fix a compiler warning on platforms with 32-bit time_t values.
2537 Fixes bug 40028; bugfix on 0.3.2.8-rc.
2539 o Minor bugfixes (embedded Tor, backport from 0.4.3.1-alpha):
2540 - When starting Tor any time after the first time in a process,
2541 register the thread in which it is running as the main thread.
2542 Previously, we only did this on Windows, which could lead to bugs
2543 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
2546 o Minor bugfixes (key portability, backport from 0.4.3.4-rc):
2547 - When reading PEM-encoded key data, tolerate CRLF line-endings even
2548 if we are not running on Windows. Previously, non-Windows hosts
2549 would reject these line-endings in certain positions, making
2550 certain key files hard to move from one host to another. Fixes bug
2551 33032; bugfix on 0.3.5.1-alpha.
2553 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
2554 - Downgrade a noisy log message that could occur naturally when
2555 receiving an extrainfo document that we no longer want. Fixes bug
2556 16016; bugfix on 0.2.6.3-alpha.
2558 o Minor bugfixes (onion service v3, client, backport from 0.4.3.3-alpha):
2559 - Remove a BUG() warning that would cause a stack trace if an onion
2560 service descriptor was freed while we were waiting for a
2561 rendezvous circuit to complete. Fixes bug 28992; bugfix
2564 o Testing (CI, backport from 0.4.3.4-rc):
2565 - In our Appveyor Windows CI, copy required DLLs to test and app
2566 directories, before running tor's tests. This ensures that tor.exe
2567 and test*.exe use the correct version of each DLL. This fix is not
2568 required, but we hope it will avoid DLL search issues in future.
2569 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
2570 - On Appveyor, skip the crypto/openssl_version test, which is
2571 failing because of a mismatched library installation. Fix
2575 Changes in version 0.4.2.8 - 2020-07-09
2576 Tor 0.4.2.8 backports various fixes from later releases, including
2577 several that affect usability and portability.
2579 This release also fixes TROVE-2020-001, a medium-severity denial of
2580 service vulnerability affecting all versions of Tor when compiled with
2581 the NSS encryption library. (This is not the default configuration.)
2582 Using this vulnerability, an attacker could cause an affected Tor
2583 instance to crash remotely. This issue is also tracked as CVE-2020-
2584 15572. Anybody running a version of Tor built with the NSS library
2585 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
2588 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
2589 - Fix a crash due to an out-of-bound memory access when Tor is
2590 compiled with NSS support. Fixes bug 33119; bugfix on
2591 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
2594 o Major bugfixes (DoS defenses, bridges, pluggable transport, backport from 0.4.3.4-rc):
2595 - Fix a bug that was preventing DoS defenses from running on bridges
2596 with a pluggable transport. Previously, the DoS subsystem was not
2597 given the transport name of the client connection, thus failed to
2598 find the GeoIP cache entry for that client address. Fixes bug
2599 33491; bugfix on 0.3.3.2-alpha.
2601 o Minor feature (sendme, flow control, backport form 0.4.3.4-rc):
2602 - Default to sending SENDME version 1 cells. (Clients are already
2603 sending these, because of a consensus parameter telling them to do
2604 so: this change only affects what clients would do if the
2605 consensus didn't contain a recommendation.) Closes ticket 33623.
2607 o Minor features (diagnostic, backport from 0.4.3.3-alpha):
2608 - Improve assertions and add some memory-poisoning code to try to
2609 track down possible causes of a rare crash (32564) in the EWMA
2610 code. Closes ticket 33290.
2612 o Minor features (testing, backport from 0.4.3.4-rc):
2613 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
2614 variable to specify a list of space-separated test cases that
2615 should not be executed. We will use this to disable certain tests
2616 that are failing on Appveyor because of mismatched OpenSSL
2617 libraries. Part of ticket 33643.
2619 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
2620 - Use the correct 64-bit printf format when compiling with MINGW on
2621 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
2623 o Minor bugfix (relay, configuration, backport from 0.4.3.3-alpha):
2624 - Warn if the ContactInfo field is not set, and tell the relay
2625 operator that not having a ContactInfo field set might cause their
2626 relay to get rejected in the future. Fixes bug 33361; bugfix
2629 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
2630 - Resume use of preemptively-built circuits when UseEntryGuards is set
2631 to 0. We accidentally disabled this feature with that config
2632 setting, leading to slower load times. Fixes bug 34303; bugfix
2635 o Minor bugfixes (compiler compatibility, backport from 0.4.3.5):
2636 - Avoid compiler warnings from Clang 10 related to the use of GCC-
2637 style "/* falls through */" comments. Both Clang and GCC allow
2638 __attribute__((fallthrough)) instead, so that's what we're using
2639 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
2640 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
2643 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
2644 - Fix a compiler warning on platforms with 32-bit time_t values.
2645 Fixes bug 40028; bugfix on 0.3.2.8-rc.
2647 o Minor bugfixes (controller protocol, backport from 0.4.3.2-alpha):
2648 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
2649 report them as SIGNAL events. Previously we would log a bug
2650 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
2652 o Minor bugfixes (embedded Tor, backport from 0.4.3.1-alpha):
2653 - When starting Tor any time after the first time in a process,
2654 register the thread in which it is running as the main thread.
2655 Previously, we only did this on Windows, which could lead to bugs
2656 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
2659 o Minor bugfixes (key portability, backport from 0.4.3.4-rc):
2660 - When reading PEM-encoded key data, tolerate CRLF line-endings even
2661 if we are not running on Windows. Previously, non-Windows hosts
2662 would reject these line-endings in certain positions, making
2663 certain key files hard to move from one host to another. Fixes bug
2664 33032; bugfix on 0.3.5.1-alpha.
2666 o Minor bugfixes (logging, backport from 0.4.3.2-rc):
2667 - When logging a bug, do not say "Future instances of this warning
2668 will be silenced" unless we are actually going to silence them.
2669 Previously we would say this whenever a BUG() check failed in the
2670 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
2672 o Minor bugfixes (logging, backport from 0.4.3.4-rc):
2673 - Flush stderr, stdout, and file logs during shutdown, if supported
2674 by the OS. This change helps make sure that any final logs are
2675 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
2677 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
2678 - Downgrade a noisy log message that could occur naturally when
2679 receiving an extrainfo document that we no longer want. Fixes bug
2680 16016; bugfix on 0.2.6.3-alpha.
2682 o Minor bugfixes (onion service v3, client, backport from 0.4.3.3-alpha):
2683 - Remove a BUG() warning that would cause a stack trace if an onion
2684 service descriptor was freed while we were waiting for a
2685 rendezvous circuit to complete. Fixes bug 28992; bugfix
2688 o Testing (CI, backport from 0.4.3.4-rc):
2689 - In our Appveyor Windows CI, copy required DLLs to test and app
2690 directories, before running tor's tests. This ensures that tor.exe
2691 and test*.exe use the correct version of each DLL. This fix is not
2692 required, but we hope it will avoid DLL search issues in future.
2693 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
2694 - On Appveyor, skip the crypto/openssl_version test, which is
2695 failing because of a mismatched library installation. Fix
2699 Changes in version 0.4.3.6 - 2020-07-09
2700 Tor 0.4.3.6 backports several bugfixes from later releases, including
2701 some affecting usability.
2703 This release also fixes TROVE-2020-001, a medium-severity denial of
2704 service vulnerability affecting all versions of Tor when compiled with
2705 the NSS encryption library. (This is not the default configuration.)
2706 Using this vulnerability, an attacker could cause an affected Tor
2707 instance to crash remotely. This issue is also tracked as CVE-2020-
2708 15572. Anybody running a version of Tor built with the NSS library
2709 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
2712 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
2713 - Fix a crash due to an out-of-bound memory access when Tor is
2714 compiled with NSS support. Fixes bug 33119; bugfix on
2715 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
2718 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
2719 - Use the correct 64-bit printf format when compiling with MINGW on
2720 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
2722 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
2723 - Resume use of preemptively-built circuits when UseEntryGuards is set
2724 to 0. We accidentally disabled this feature with that config
2725 setting, leading to slower load times. Fixes bug 34303; bugfix
2728 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
2729 - Fix a compiler warning on platforms with 32-bit time_t values.
2730 Fixes bug 40028; bugfix on 0.3.2.8-rc.
2732 o Minor bugfixes (linux seccomp sandbox, nss, backport from 0.4.4.1-alpha):
2733 - Fix a startup crash when tor is compiled with --enable-nss and
2734 sandbox support is enabled. Fixes bug 34130; bugfix on
2735 0.3.5.1-alpha. Patch by Daniel Pinto.
2737 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
2738 - Downgrade a noisy log message that could occur naturally when
2739 receiving an extrainfo document that we no longer want. Fixes bug
2740 16016; bugfix on 0.2.6.3-alpha.
2742 o Minor bugfixes (manual page, backport from 0.4.4.1-alpha):
2743 - Update the man page to reflect that MinUptimeHidServDirectoryV2
2744 defaults to 96 hours. Fixes bug 34299; bugfix on 0.2.6.3-alpha.
2746 o Minor bugfixes (onion service v3, backport from 0.4.4.1-alpha):
2747 - Prevent an assert() that would occur when cleaning the client
2748 descriptor cache, and attempting to close circuits for a non-
2749 decrypted descriptor (lacking client authorization). Fixes bug
2750 33458; bugfix on 0.4.2.1-alpha.
2752 o Minor bugfixes (portability, backport from 0.4.4.1-alpha):
2753 - Fix a portability error in the configure script, where we were
2754 using "==" instead of "=". Fixes bug 34233; bugfix on 0.4.3.5.
2756 o Minor bugfixes (relays, backport from 0.4.4.1-alpha):
2757 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
2758 descriptors, when the IPv6 port was configured as "auto". Fixes
2759 bug 32588; bugfix on 0.2.3.9-alpha.
2761 o Documentation (backport from 0.4.4.1-alpha):
2762 - Fix several doxygen warnings related to imbalanced groups. Closes
2766 Changes in version 0.4.3.5 - 2020-05-15
2767 Tor 0.4.3.5 is the first stable release in the 0.4.3.x series. This
2768 series adds support for building without relay code enabled, and
2769 implements functionality needed for OnionBalance with v3 onion
2770 services. It includes significant refactoring of our configuration and
2771 controller functionality, and fixes numerous smaller bugs and
2774 Per our support policy, we support each stable release series for nine
2775 months after its first stable release, or three months after the first
2776 stable release of the next series: whichever is longer. This means
2777 that 0.4.3.x will be supported until around February 2021--later, if
2778 0.4.4.x is later than anticipated.
2780 Note also that support for 0.4.1.x is about to end on May 20 of this
2781 year; 0.4.2.x will be supported until September 15. We still plan to
2782 continue supporting 0.3.5.x, our long-term stable series, until
2785 Below are the changes since 0.4.2.6. For a list of only the changes
2786 since 0.4.3.4-rc, see the ChangeLog file.
2788 o New system requirements:
2789 - When building Tor, you now need to have Python 3 in order to run
2790 the integration tests. (Python 2 is officially unsupported
2791 upstream, as of 1 Jan 2020.) Closes ticket 32608.
2793 o Major features (build system):
2794 - The relay code can now be disabled using the --disable-module-relay
2795 configure option. When this option is set, we also disable the
2796 dirauth module. Closes ticket 32123.
2797 - When Tor is compiled --disable-module-relay, we also omit the code
2798 used to act as a directory cache. Closes ticket 32487.
2800 o Major features (directory authority, ed25519):
2801 - Add support for banning a relay's ed25519 keys in the approved-
2802 routers file. This will help us migrate away from RSA keys in the
2803 future. Previously, only RSA keys could be banned in approved-
2804 routers. Resolves ticket 22029. Patch by Neel Chauhan.
2806 o Major features (onion services):
2807 - New control port commands to manage client-side onion service
2808 authorization credentials. The ONION_CLIENT_AUTH_ADD command adds
2809 a credential, ONION_CLIENT_AUTH_REMOVE deletes a credential, and
2810 ONION_CLIENT_AUTH_VIEW lists the credentials. Closes ticket 30381.
2811 - Introduce a new SocksPort flag, ExtendedErrors, to support more
2812 detailed error codes in information for applications that support
2813 them. Closes ticket 30382; implements proposal 304.
2815 o Major features (proxy):
2816 - In addition to its current supported proxy types (HTTP CONNECT,
2817 SOCKS4, and SOCKS5), Tor can now make its OR connections through a
2818 HAProxy server. A new torrc option was added to specify the
2819 address/port of the server: TCPProxy <protocol> <host>:<port>.
2820 Currently the only supported protocol for the option is haproxy.
2821 Closes ticket 31518. Patch done by Suphanat Chunhapanya (haxxpop).
2823 o Major bugfixes (security, denial-of-service):
2824 - Fix a denial-of-service bug that could be used by anyone to
2825 consume a bunch of CPU on any Tor relay or authority, or by
2826 directories to consume a bunch of CPU on clients or hidden
2827 services. Because of the potential for CPU consumption to
2828 introduce observable timing patterns, we are treating this as a
2829 high-severity security issue. Fixes bug 33119; bugfix on
2830 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
2831 as TROVE-2020-002 and CVE-2020-10592.
2833 o Major bugfixes (circuit padding, memory leak):
2834 - Avoid a remotely triggered memory leak in the case that a circuit
2835 padding machine is somehow negotiated twice on the same circuit.
2836 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
2837 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
2839 o Major bugfixes (directory authority):
2840 - Directory authorities will now send a 503 (not enough bandwidth)
2841 code to clients when under bandwidth pressure. Known relays and
2842 other authorities will always be answered regardless of the
2843 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
2845 o Major bugfixes (DoS defenses, bridges, pluggable transport):
2846 - Fix a bug that was preventing DoS defenses from running on bridges
2847 with a pluggable transport. Previously, the DoS subsystem was not
2848 given the transport name of the client connection, thus failed to
2849 find the GeoIP cache entry for that client address. Fixes bug
2850 33491; bugfix on 0.3.3.2-alpha.
2852 o Major bugfixes (networking):
2853 - Correctly handle IPv6 addresses in SOCKS5 RESOLVE_PTR requests,
2854 and accept strings as well as binary addresses. Fixes bug 32315;
2855 bugfix on 0.3.5.1-alpha.
2857 o Major bugfixes (onion service):
2858 - Report HS circuit failure back into the HS subsystem so we take
2859 appropriate action with regards to the client introduction point
2860 failure cache. This improves reachability of onion services, since
2861 now clients notice failing introduction circuits properly. Fixes
2862 bug 32020; bugfix on 0.3.2.1-alpha.
2864 o Minor feature (heartbeat, onion service):
2865 - Add the DoS INTRODUCE2 defenses counter to the heartbeat DoS
2866 message. Closes ticket 31371.
2868 o Minor feature (sendme, flow control):
2869 - Default to sending SENDME version 1 cells. (Clients are already
2870 sending these, because of a consensus parameter telling them to do
2871 so: this change only affects what clients would do if the
2872 consensus didn't contain a recommendation.) Closes ticket 33623.
2874 o Minor features (best practices tracker):
2875 - Practracker now supports a --regen-overbroad option to regenerate
2876 the exceptions file, but only to revise exceptions to be _less_
2877 tolerant of best-practices violations. Closes ticket 32372.
2879 o Minor features (configuration validation):
2880 - Configuration validation can now be done by per-module callbacks,
2881 rather than a global validation function. This will let us reduce
2882 the size of config.c and some of its more cumbersome functions.
2883 Closes ticket 31241.
2885 o Minor features (configuration):
2886 - If a configured hardware crypto accelerator in AccelName is
2887 prefixed with "!", Tor now exits when it cannot be found. Closes
2889 - We now use flag-driven logic to warn about obsolete configuration
2890 fields, so that we can include their names. In 0.4.2, we used a
2891 special type, which prevented us from generating good warnings.
2892 Implements ticket 32404.
2894 o Minor features (configure, build system):
2895 - Output a list of enabled/disabled features at the end of the
2896 configure process in a pleasing way. Closes ticket 31373.
2898 o Minor features (continuous integration):
2899 - Run Doxygen Makefile target on Travis, so we can learn about
2900 regressions in our internal documentation. Closes ticket 32455.
2901 - Stop allowing failures on the Travis CI stem tests job. It looks
2902 like all the stem hangs we were seeing before are now fixed.
2903 Closes ticket 33075.
2905 o Minor features (controller):
2906 - Add stream isolation data to STREAM event. Closes ticket 19859.
2907 - Implement a new GETINFO command to fetch microdescriptor
2908 consensus. Closes ticket 31684.
2910 o Minor features (debugging, directory system):
2911 - Don't crash when we find a non-guard with a guard-fraction value
2912 set. Instead, log a bug warning, in an attempt to figure out how
2913 this happened. Diagnostic for ticket 32868.
2915 o Minor features (defense in depth):
2916 - Add additional checks around tor_vasprintf() usage, in case the
2917 function returns an error. Patch by Tobias Stoeckmann. Fixes
2920 o Minor features (developer tools):
2921 - Remove the 0.2.9.x series branches from git scripts (git-merge-
2922 forward.sh, git-pull-all.sh, git-push-all.sh, git-setup-dirs.sh).
2923 Closes ticket 32772.
2924 - Add a check_cocci_parse.sh script that checks that new code is
2925 parseable by Coccinelle. Add an exceptions file for unparseable
2926 files, and run the script from travis CI. Closes ticket 31919.
2927 - Call the check_cocci_parse.sh script from a 'check-cocci' Makefile
2928 target. Closes ticket 31919.
2929 - Add a rename_c_identifiers.py tool to rename a bunch of C
2930 identifiers at once, and generate a well-formed commit message
2931 describing the change. This should help with refactoring. Closes
2933 - Add some scripts in "scripts/coccinelle" to invoke the Coccinelle
2934 semantic patching tool with the correct flags. These flags are
2935 fairly easy to forget, and these scripts should help us use
2936 Coccinelle more effectively in the future. Closes ticket 31705.
2938 o Minor features (diagnostic):
2939 - Improve assertions and add some memory-poisoning code to try to
2940 track down possible causes of a rare crash (32564) in the EWMA
2941 code. Closes ticket 33290.
2943 o Minor features (directory authorities):
2944 - Directory authorities now reject descriptors from relays running
2945 Tor versions from the 0.2.9 and 0.4.0 series. The 0.3.5 series is
2946 still allowed. Resolves ticket 32672. Patch by Neel Chauhan.
2948 o Minor features (Doxygen):
2949 - Update Doxygen configuration file to a more recent template (from
2950 1.8.15). Closes ticket 32110.
2951 - "make doxygen" now works with out-of-tree builds. Closes
2953 - Make sure that doxygen outputs documentation for all of our C
2954 files. Previously, some were missing @file declarations, causing
2955 them to be ignored. Closes ticket 32307.
2956 - Our "make doxygen" target now respects --enable-fatal-warnings by
2957 default, and does not warn about items that are missing
2958 documentation. To warn about missing documentation, run configure
2959 with the "--enable-missing-doc-warnings" flag: doing so suspends
2960 fatal warnings for doxygen. Closes ticket 32385.
2962 o Minor features (git scripts):
2963 - Add TOR_EXTRA_CLONE_ARGS to git-setup-dirs.sh for git clone
2964 customisation. Closes ticket 32347.
2965 - Add git-setup-dirs.sh, which sets up an upstream git repository
2966 and worktrees for tor maintainers. Closes ticket 29603.
2967 - Add TOR_EXTRA_REMOTE_* to git-setup-dirs.sh for a custom extra
2968 remote. Closes ticket 32347.
2969 - Call the check_cocci_parse.sh script from the git commit and push
2970 hooks. Closes ticket 31919.
2971 - Make git-push-all.sh skip unchanged branches when pushing to
2972 upstream. The script already skipped unchanged test branches.
2973 Closes ticket 32216.
2974 - Make git-setup-dirs.sh create a master symlink in the worktree
2975 directory. Closes ticket 32347.
2976 - Skip unmodified source files when doing some existing git hook
2977 checks. Related to ticket 31919.
2979 o Minor features (IPv6, client):
2980 - Make Tor clients tell dual-stack exits that they prefer IPv6
2981 connections. This change is equivalent to setting the PreferIPv6
2982 flag on SOCKSPorts (and most other listener ports). Tor Browser
2983 has been setting this flag for some time, and we want to remove a
2984 client distinguisher at exits. Closes ticket 32637.
2986 o Minor features (portability, android):
2987 - When building for Android, disable some tests that depend on $HOME
2988 and/or pwdb, which Android doesn't have. Closes ticket 32825.
2989 Patch from Hans-Christoph Steiner.
2991 o Minor features (relay modularity):
2992 - Split the relay and server pluggable transport config code into
2993 separate files in the relay module. Disable this code when the
2994 relay module is disabled. Closes part of ticket 32213.
2995 - When the relay module is disabled, reject attempts to set the
2996 ORPort, DirPort, DirCache, BridgeRelay, ExtORPort, or
2997 ServerTransport* options, rather than ignoring the values of these
2998 options. Closes part of ticket 32213.
2999 - When the relay module is disabled, change the default config so
3000 that DirCache is 0, and ClientOnly is 1. Closes ticket 32410.
3002 o Minor features (release tools):
3003 - Port our ChangeLog formatting and sorting tools to Python 3.
3004 Closes ticket 32704.
3006 o Minor features (testing):
3007 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
3008 variable to specify a list of space-separated test cases that
3009 should not be executed. We will use this to disable certain tests
3010 that are failing on Appveyor because of mismatched OpenSSL
3011 libraries. Part of ticket 33643.
3012 - Detect some common failure cases for test_parseconf.sh in
3013 src/test/conf_failures. Closes ticket 32451.
3014 - Allow test_parseconf.sh to test expected log outputs for successful
3015 configs, as well as failed configs. Closes ticket 32451.
3016 - The test_parseconf.sh script now supports result variants for any
3017 combination of the optional libraries lzma, nss, and zstd. Closes
3019 - When running the unit tests on Android, create temporary files in
3020 a subdirectory of /data/local/tmp. Closes ticket 32172. Based on a
3021 patch from Hans-Christoph Steiner.
3023 o Minor features (usability):
3024 - Include more information when failing to parse a configuration
3025 value. This should make it easier to tell what's going wrong when
3026 a configuration file doesn't parse. Closes ticket 33460.
3028 o Minor bugfix (relay, configuration):
3029 - Warn if the ContactInfo field is not set, and tell the relay
3030 operator that not having a ContactInfo field set might cause their
3031 relay to get rejected in the future. Fixes bug 33361; bugfix
3034 o Minor bugfixes (bridges):
3035 - Lowercase the configured value of BridgeDistribution before adding
3036 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
3038 o Minor bugfixes (build system):
3039 - Fix "make autostyle" for out-of-tree builds. Fixes bug 32370;
3040 bugfix on 0.4.1.2-alpha.
3042 o Minor bugfixes (compiler compatibility):
3043 - Avoid compiler warnings from Clang 10 related to the use of GCC-
3044 style "/* falls through */" comments. Both Clang and GCC allow
3045 __attribute__((fallthrough)) instead, so that's what we're using
3046 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
3047 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
3050 o Minor bugfixes (configuration handling):
3051 - Make control_event_conf_changed() take in a config_line_t instead
3052 of a smartlist of alternating key/value entries. Fixes bug 31531;
3053 bugfix on 0.2.3.3-alpha. Patch by Neel Chauhan.
3054 - Check for multiplication overflow when parsing memory units inside
3055 configuration. Fixes bug 30920; bugfix on 0.0.9rc1.
3056 - When dumping the configuration, stop adding a trailing space after
3057 the option name when there is no option value. This issue only
3058 affects options that accept an empty value or list. (Most options
3059 reject empty values, or delete the entire line from the dumped
3060 options.) Fixes bug 32352; bugfix on 0.0.9pre6.
3061 - Avoid changing the user's value of HardwareAccel as stored by
3062 SAVECONF, when AccelName is set but HardwareAccel is not. Fixes
3063 bug 32382; bugfix on 0.2.2.1-alpha.
3064 - When creating a KeyDirectory with the same location as the
3065 DataDirectory (not recommended), respect the DataDirectory's
3066 group-readable setting if one has not been set for the
3067 KeyDirectory. Fixes bug 27992; bugfix on 0.3.3.1-alpha.
3069 o Minor bugfixes (continuous integration):
3070 - Remove the buggy and unused mirroring job. Fixes bug 33213; bugfix
3073 o Minor bugfixes (controller protocol):
3074 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
3075 report them as SIGNAL events. Previously we would log a bug
3076 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
3078 o Minor bugfixes (controller):
3079 - In routerstatus_has_changed(), check all the fields that are
3080 output over the control port. Fixes bug 20218; bugfix
3083 o Minor bugfixes (developer tools):
3084 - Allow paths starting with ./ in scripts/add_c_file.py. Fixes bug
3085 31336; bugfix on 0.4.1.2-alpha.
3087 o Minor bugfixes (dirauth module):
3088 - Split the dirauth config code into a separate file in the dirauth
3089 module. Disable this code when the dirauth module is disabled.
3090 Closes ticket 32213.
3091 - When the dirauth module is disabled, reject attempts to set the
3092 AuthoritativeDir option, rather than ignoring the value of the
3093 option. Fixes bug 32213; bugfix on 0.3.4.1-alpha.
3095 o Minor bugfixes (embedded Tor):
3096 - When starting Tor any time after the first time in a process,
3097 register the thread in which it is running as the main thread.
3098 Previously, we only did this on Windows, which could lead to bugs
3099 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
3102 o Minor bugfixes (git scripts):
3103 - Avoid sleeping before the last push in git-push-all.sh. Closes
3105 - Forward all unrecognised arguments in git-push-all.sh to git push.
3106 Closes ticket 32216.
3108 o Minor bugfixes (key portability):
3109 - When reading PEM-encoded key data, tolerate CRLF line-endings even
3110 if we are not running on Windows. Previously, non-Windows hosts
3111 would reject these line-endings in certain positions, making
3112 certain key files hard to move from one host to another. Fixes bug
3113 33032; bugfix on 0.3.5.1-alpha.
3115 o Minor bugfixes (logging):
3116 - Stop truncating IPv6 addresses and ports in channel and connection
3117 logs. Fixes bug 33918; bugfix on 0.2.4.4-alpha.
3118 - Flush stderr, stdout, and file logs during shutdown, if supported
3119 by the OS. This change helps make sure that any final logs are
3120 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
3121 - Stop closing stderr and stdout during shutdown. Closing these file
3122 descriptors can hide sanitiser logs. Fixes bug 33087; bugfix
3124 - If we encounter a bug when flushing a buffer to a TLS connection,
3125 only log the bug once per invocation of the Tor process.
3126 Previously we would log with every occurrence, which could cause
3127 us to run out of disk space. Fixes bug 33093; bugfix
3129 - When logging a bug, do not say "Future instances of this warning
3130 will be silenced" unless we are actually going to silence them.
3131 Previously we would say this whenever a BUG() check failed in the
3132 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
3134 o Minor bugfixes (onion services v2):
3135 - Move a series of v2 onion service warnings to protocol-warning
3136 level because they can all be triggered remotely by a malformed
3137 request. Fixes bug 32706; bugfix on 0.1.1.14-alpha.
3138 - When sending the INTRO cell for a v2 Onion Service, look at the
3139 failure cache alongside timeout values to check if the intro point
3140 is marked as failed. Previously, we only looked at the relay
3141 timeout values. Fixes bug 25568; bugfix on 0.2.7.3-rc. Patch by
3144 o Minor bugfixes (onion services v3):
3145 - Remove a BUG() warning that would cause a stack trace if an onion
3146 service descriptor was freed while we were waiting for a
3147 rendezvous circuit to complete. Fixes bug 28992; bugfix
3149 - Relax severity of a log message that can appear naturally when
3150 decoding onion service descriptors as a relay. Also add some
3151 diagnostics to debug any future bugs in that area. Fixes bug
3152 31669; bugfix on 0.3.0.1-alpha.
3153 - Fix an assertion failure that could result from a corrupted
3154 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
3155 bugfix on 0.3.3.1-alpha. This issue is also tracked
3157 - Properly handle the client rendezvous circuit timeout. Previously
3158 Tor would sometimes timeout a rendezvous circuit awaiting the
3159 introduction ACK, and find itself unable to re-establish all
3160 circuits because the rendezvous circuit timed out too early. Fixes
3161 bug 32021; bugfix on 0.3.2.1-alpha.
3163 o Minor bugfixes (onion services):
3164 - Do not rely on a "circuit established" flag for intro circuits but
3165 instead always query the HS circuit map. This is to avoid sync
3166 issue with that flag and the map. Fixes bug 32094; bugfix
3169 o Minor bugfixes (onion services, all):
3170 - In cancel_descriptor_fetches(), use
3171 connection_list_by_type_purpose() instead of
3172 connection_list_by_type_state(). Fixes bug 32639; bugfix on
3173 0.3.2.1-alpha. Patch by Neel Chauhan.
3175 o Minor bugfixes (pluggable transports):
3176 - When receiving a message on standard error from a pluggable
3177 transport, log it at info level, rather than as a warning. Fixes
3178 bug 33005; bugfix on 0.4.0.1-alpha.
3180 o Minor bugfixes (rust, build):
3181 - Fix a syntax warning given by newer versions of Rust that was
3182 creating problems for our continuous integration. Fixes bug 33212;
3183 bugfix on 0.3.5.1-alpha.
3185 o Minor bugfixes (scripts):
3186 - Fix update_versions.py for out-of-tree builds. Fixes bug 32371;
3187 bugfix on 0.4.0.1-alpha.
3189 o Minor bugfixes (testing):
3190 - Use the same code to find the tor binary in all of our test
3191 scripts. This change makes sure we are always using the coverage
3192 binary when coverage is enabled. Fixes bug 32368; bugfix
3194 - Stop ignoring "tor --dump-config" errors in test_parseconf.sh.
3195 Fixes bug 32468; bugfix on 0.4.2.1-alpha.
3196 - Our option-validation tests no longer depend on specially
3197 configured non-default, non-passing sets of options. Previously,
3198 the tests had been written to assume that options would _not_ be
3199 set to their defaults, which led to needless complexity and
3200 verbosity. Fixes bug 32175; bugfix on 0.2.8.1-alpha.
3202 o Minor bugfixes (TLS bug handling):
3203 - When encountering a bug in buf_read_from_tls(), return a "MISC"
3204 error code rather than "WANTWRITE". This change might help avoid
3205 some CPU-wasting loops if the bug is ever triggered. Bug reported
3206 by opara. Fixes bug 32673; bugfix on 0.3.0.4-alpha.
3208 o Deprecated features:
3209 - Deprecate the ClientAutoIPv6ORPort option. This option was not
3210 true "Happy Eyeballs", and often failed on connections that
3211 weren't reliably dual-stack. Closes ticket 32942. Patch by
3215 - Provide a quickstart guide for a Circuit Padding Framework, and
3216 documentation for researchers to implement and study circuit
3217 padding machines. Closes ticket 28804.
3218 - Add documentation in 'HelpfulTools.md' to describe how to build a
3219 tag file. Closes ticket 32779.
3220 - Create a high-level description of the long-term software
3221 architecture goals. Closes ticket 32206.
3222 - Describe the --dump-config command in the manual page. Closes
3224 - Unite coding advice from this_not_that.md in torguts repo into our
3225 coding standards document. Resolves ticket 31853.
3228 - Our Doxygen configuration no longer generates LaTeX output. The
3229 reference manual produced by doing this was over 4000 pages long,
3230 and generally unusable. Closes ticket 32099.
3231 - The option "TestingEstimatedDescriptorPropagationTime" is now
3232 marked as obsolete. It has had no effect since 0.3.0.7, when
3233 clients stopped rejecting consensuses "from the future". Closes
3235 - We no longer support consensus methods before method 28; these
3236 methods were only used by authorities running versions of Tor that
3237 are now at end-of-life. In effect, this means that clients,
3238 relays, and authorities now assume that authorities will be
3239 running version 0.3.5.x or later. Closes ticket 32695.
3242 - Avoid conflicts between the fake sockets in tor's unit tests, and
3243 real file descriptors. Resolves issues running unit tests with
3244 GitHub Actions, where the process that embeds or launches the
3245 tests has already opened a large number of file descriptors. Fixes
3246 bug 33782; bugfix on 0.2.8.1-alpha. Found and fixed by
3248 - Add more test cases for tor's UTF-8 validation function. Also,
3249 check the arguments passed to the function for consistency. Closes
3251 - Improve test coverage for relay and dirauth config code, focusing
3252 on option validation and normalization. Closes ticket 32213.
3253 - Improve the consistency of test_parseconf.sh output, and run all
3254 the tests, even if one fails. Closes ticket 32213.
3255 - Run the practracker unit tests in the pre-commit git hook. Closes
3258 o Code simplification and refactoring (channel):
3259 - Channel layer had a variable length cell handler that was not used
3260 and thus removed. Closes ticket 32892.
3262 o Code simplification and refactoring (configuration):
3263 - Immutability is now implemented as a flag on individual
3264 configuration options rather than as part of the option-transition
3265 checking code. Closes ticket 32344.
3266 - Instead of keeping a list of configuration options to check for
3267 relative paths, check all the options whose type is "FILENAME".
3268 Solves part of ticket 32339.
3269 - Our default log (which ordinarily sends NOTICE-level messages to
3270 standard output) is now handled in a more logical manner.
3271 Previously, we replaced the configured log options if they were
3272 empty. Now, we interpret an empty set of log options as meaning
3273 "use the default log". Closes ticket 31999.
3274 - Remove some unused arguments from the options_validate() function,
3275 to simplify our code and tests. Closes ticket 32187.
3276 - Simplify the options_validate() code so that it looks at the
3277 default options directly, rather than taking default options as an
3278 argument. This change lets us simplify its interface. Closes
3280 - Use our new configuration architecture to move most authority-
3281 related options to the directory authority module. Closes
3283 - When parsing the command line, handle options that determine our
3284 "quiet level" and our mode of operation (e.g., --dump-config and
3285 so on) all in one table. Closes ticket 32003.
3287 o Code simplification and refactoring (controller):
3288 - Create a new abstraction for formatting control protocol reply
3289 lines based on key-value pairs. Refactor some existing control
3290 protocol code to take advantage of this. Closes ticket 30984.
3291 - Create a helper function that can fetch network status or
3292 microdesc consensuses. Closes ticket 31684.
3294 o Code simplification and refactoring (dirauth modularization):
3295 - Remove the last remaining HAVE_MODULE_DIRAUTH inside a function.
3296 Closes ticket 32163.
3297 - Replace some confusing identifiers in process_descs.c. Closes
3299 - Simplify some relay and dirauth config code. Closes ticket 32213.
3301 o Code simplification and refactoring (mainloop):
3302 - Simplify the ip_address_changed() function by removing redundant
3303 checks. Closes ticket 33091.
3305 o Code simplification and refactoring (misc):
3306 - Make all the structs we declare follow the same naming convention
3307 of ending with "_t". Closes ticket 32415.
3308 - Move and rename some configuration-related code for clarity.
3309 Closes ticket 32304.
3310 - Our include.am files are now broken up by subdirectory.
3311 Previously, src/core/include.am covered all of the subdirectories
3312 in "core", "feature", and "app". Closes ticket 32137.
3313 - Remove underused NS*() macros from test code: they make our tests
3314 more confusing, especially for code-formatting tools. Closes
3317 o Code simplification and refactoring (relay modularization):
3318 - Disable relay_periodic when the relay module is disabled. Closes
3320 - Disable relay_sys when the relay module is disabled. Closes
3323 o Code simplification and refactoring (tool support):
3324 - Add numerous missing dependencies to our include files, so that
3325 they can be included in different reasonable orders and still
3326 compile. Addresses part of ticket 32764.
3327 - Fix some parts of our code that were difficult for Coccinelle to
3328 parse. Related to ticket 31705.
3329 - Fix some small issues in our code that prevented automatic
3330 formatting tools from working. Addresses part of ticket 32764.
3332 o Documentation (manpage):
3333 - Alphabetize the Server and Directory server sections of the tor
3334 manpage. Also split Statistics options into their own section of
3335 the manpage. Closes ticket 33188. Work by Swati Thacker as part of
3336 Google Season of Docs.
3337 - Document the __OwningControllerProcess torrc option and specify
3338 its polling interval. Resolves issue 32971.
3339 - Split "Circuit Timeout" options and "Node Selection" options into
3340 their own sections of the tor manpage. Closes tickets 32928 and
3341 32929. Work by Swati Thacker as part of Google Season of Docs.
3342 - Alphabetize the Client Options section of the tor manpage. Closes
3344 - Alphabetize the General Options section of the tor manpage. Closes
3346 - In the tor(1) manpage, reword and improve formatting of the
3347 COMMAND-LINE OPTIONS and DESCRIPTION sections. Closes ticket
3348 32277. Based on work by Swati Thacker as part of Google Season
3350 - In the tor(1) manpage, reword and improve formatting of the FILES,
3351 SEE ALSO, and BUGS sections. Closes ticket 32176. Based on work by
3352 Swati Thacker as part of Google Season of Docs.
3354 o Testing (Appveyor CI):
3355 - In our Appveyor Windows CI, copy required DLLs to test and app
3356 directories, before running tor's tests. This ensures that tor.exe
3357 and test*.exe use the correct version of each DLL. This fix is not
3358 required, but we hope it will avoid DLL search issues in future.
3359 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
3360 - On Appveyor, skip the crypto/openssl_version test, which is
3361 failing because of a mismatched library installation. Fix
3364 o Testing (circuit, EWMA):
3365 - Add unit tests for circuitmux and EWMA subsystems. Closes
3368 o Testing (Travis CI):
3369 - Remove a redundant distcheck job. Closes ticket 33194.
3370 - Sort the Travis jobs in order of speed: putting the slowest jobs
3371 first takes full advantage of Travis job concurrency. Closes
3373 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
3374 previously configured to fast_finish (which requires
3375 allow_failure), to speed up the build. Closes ticket 33195.
3376 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
3377 tool to produce detailed diagnostic output. Closes ticket 32792.
3380 Changes in version 0.4.2.7 - 2020-03-18
3381 This is the third stable release in the 0.4.2.x series. It backports
3382 numerous fixes from later releases, including a fix for TROVE-2020-
3383 002, a major denial-of-service vulnerability that affected all
3384 released Tor instances since 0.2.1.5-alpha. Using this vulnerability,
3385 an attacker could cause Tor instances to consume a huge amount of CPU,
3386 disrupting their operations for several seconds or minutes. This
3387 attack could be launched by anybody against a relay, or by a directory
3388 cache against any client that had connected to it. The attacker could
3389 launch this attack as much as they wanted, thereby disrupting service
3390 or creating patterns that could aid in traffic analysis. This issue
3391 was found by OSS-Fuzz, and is also tracked as CVE-2020-10592.
3393 We do not have reason to believe that this attack is currently being
3394 exploited in the wild, but nonetheless we advise everyone to upgrade
3395 as soon as packages are available.
3397 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
3398 - Fix a denial-of-service bug that could be used by anyone to
3399 consume a bunch of CPU on any Tor relay or authority, or by
3400 directories to consume a bunch of CPU on clients or hidden
3401 services. Because of the potential for CPU consumption to
3402 introduce observable timing patterns, we are treating this as a
3403 high-severity security issue. Fixes bug 33119; bugfix on
3404 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
3405 as TROVE-2020-002 and CVE-2020-10592.
3407 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
3408 - Avoid a remotely triggered memory leak in the case that a circuit
3409 padding machine is somehow negotiated twice on the same circuit.
3410 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
3411 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
3413 o Major bugfixes (directory authority, backport from 0.4.3.3-alpha):
3414 - Directory authorities will now send a 503 (not enough bandwidth)
3415 code to clients when under bandwidth pressure. Known relays and
3416 other authorities will always be answered regardless of the
3417 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
3419 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
3420 - Stop allowing failures on the Travis CI stem tests job. It looks
3421 like all the stem hangs we were seeing before are now fixed.
3422 Closes ticket 33075.
3424 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
3425 - Lowercase the configured value of BridgeDistribution before adding
3426 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
3428 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
3429 - If we encounter a bug when flushing a buffer to a TLS connection,
3430 only log the bug once per invocation of the Tor process.
3431 Previously we would log with every occurrence, which could cause
3432 us to run out of disk space. Fixes bug 33093; bugfix
3435 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
3436 - Fix an assertion failure that could result from a corrupted
3437 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
3438 bugfix on 0.3.3.1-alpha. This issue is also tracked
3441 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
3442 - Fix a syntax warning given by newer versions of Rust that was
3443 creating problems for our continuous integration. Fixes bug 33212;
3444 bugfix on 0.3.5.1-alpha.
3446 o Testing (Travis CI, backport from 0.4.3.3-alpha):
3447 - Remove a redundant distcheck job. Closes ticket 33194.
3448 - Sort the Travis jobs in order of speed: putting the slowest jobs
3449 first takes full advantage of Travis job concurrency. Closes
3451 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
3452 previously configured to fast_finish (which requires
3453 allow_failure), to speed up the build. Closes ticket 33195.
3454 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
3455 tool to produce detailed diagnostic output. Closes ticket 32792.
3458 Changes in version 0.4.1.9 - 2020-03-18
3459 Tor 0.4.1.9 backports important fixes from later Tor releases,
3460 including a fix for TROVE-2020-002, a major denial-of-service
3461 vulnerability that affected all released Tor instances since
3462 0.2.1.5-alpha. Using this vulnerability, an attacker could cause Tor
3463 instances to consume a huge amount of CPU, disrupting their operations
3464 for several seconds or minutes. This attack could be launched by
3465 anybody against a relay, or by a directory cache against any client
3466 that had connected to it. The attacker could launch this attack as
3467 much as they wanted, thereby disrupting service or creating patterns
3468 that could aid in traffic analysis. This issue was found by OSS-Fuzz,
3469 and is also tracked as CVE-2020-10592.
3471 We do not have reason to believe that this attack is currently being
3472 exploited in the wild, but nonetheless we advise everyone to upgrade
3473 as soon as packages are available.
3475 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
3476 - Fix a denial-of-service bug that could be used by anyone to
3477 consume a bunch of CPU on any Tor relay or authority, or by
3478 directories to consume a bunch of CPU on clients or hidden
3479 services. Because of the potential for CPU consumption to
3480 introduce observable timing patterns, we are treating this as a
3481 high-severity security issue. Fixes bug 33119; bugfix on
3482 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
3483 as TROVE-2020-002 and CVE-2020-10592.
3485 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
3486 - Avoid a remotely triggered memory leak in the case that a circuit
3487 padding machine is somehow negotiated twice on the same circuit.
3488 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
3489 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
3491 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
3492 - Lowercase the configured value of BridgeDistribution before adding
3493 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
3495 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
3496 - If we encounter a bug when flushing a buffer to a TLS connection,
3497 only log the bug once per invocation of the Tor process.
3498 Previously we would log with every occurrence, which could cause
3499 us to run out of disk space. Fixes bug 33093; bugfix
3502 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
3503 - Fix an assertion failure that could result from a corrupted
3504 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
3505 bugfix on 0.3.3.1-alpha. This issue is also tracked
3508 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
3509 - Fix a syntax warning given by newer versions of Rust that was
3510 creating problems for our continuous integration. Fixes bug 33212;
3511 bugfix on 0.3.5.1-alpha.
3513 o Testing (Travis CI, backport from 0.4.3.3-alpha):
3514 - Remove a redundant distcheck job. Closes ticket 33194.
3515 - Sort the Travis jobs in order of speed: putting the slowest jobs
3516 first takes full advantage of Travis job concurrency. Closes
3518 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
3519 previously configured to fast_finish (which requires
3520 allow_failure), to speed up the build. Closes ticket 33195.
3521 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
3522 tool to produce detailed diagnostic output. Closes ticket 32792.
3525 Changes in version 0.3.5.10 - 2020-03-18
3526 Tor 0.3.5.10 backports many fixes from later Tor releases, including a
3527 fix for TROVE-2020-002, a major denial-of-service vulnerability that
3528 affected all released Tor instances since 0.2.1.5-alpha. Using this
3529 vulnerability, an attacker could cause Tor instances to consume a huge
3530 amount of CPU, disrupting their operations for several seconds or
3531 minutes. This attack could be launched by anybody against a relay, or
3532 by a directory cache against any client that had connected to it. The
3533 attacker could launch this attack as much as they wanted, thereby
3534 disrupting service or creating patterns that could aid in traffic
3535 analysis. This issue was found by OSS-Fuzz, and is also tracked
3538 We do not have reason to believe that this attack is currently being
3539 exploited in the wild, but nonetheless we advise everyone to upgrade
3540 as soon as packages are available.
3542 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
3543 - Fix a denial-of-service bug that could be used by anyone to
3544 consume a bunch of CPU on any Tor relay or authority, or by
3545 directories to consume a bunch of CPU on clients or hidden
3546 services. Because of the potential for CPU consumption to
3547 introduce observable timing patterns, we are treating this as a
3548 high-severity security issue. Fixes bug 33119; bugfix on
3549 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
3550 as TROVE-2020-002 and CVE-2020-10592.
3552 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
3553 - Correct how we use libseccomp. Particularly, stop assuming that
3554 rules are applied in a particular order or that more rules are
3555 processed after the first match. Neither is the case! In
3556 libseccomp <2.4.0 this lead to some rules having no effect.
3557 libseccomp 2.4.0 changed how rules are generated, leading to a
3558 different ordering, which in turn led to a fatal crash during
3559 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
3562 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
3563 - Stop allowing failures on the Travis CI stem tests job. It looks
3564 like all the stem hangs we were seeing before are now fixed.
3565 Closes ticket 33075.
3567 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
3568 - Lowercase the configured value of BridgeDistribution before adding
3569 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
3571 o Minor bugfixes (crash, backport from 0.4.2.4-rc):
3572 - When running Tor with an option like --verify-config or
3573 --dump-config that does not start the event loop, avoid crashing
3574 if we try to exit early because of an error. Fixes bug 32407;
3575 bugfix on 0.3.3.1-alpha.
3577 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
3578 - If we encounter a bug when flushing a buffer to a TLS connection,
3579 only log the bug once per invocation of the Tor process.
3580 Previously we would log with every occurrence, which could cause
3581 us to run out of disk space. Fixes bug 33093; bugfix
3584 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
3585 - Fix an assertion failure that could result from a corrupted
3586 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
3587 bugfix on 0.3.3.1-alpha. This issue is also tracked
3590 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
3591 - Fix a syntax warning given by newer versions of Rust that was
3592 creating problems for our continuous integration. Fixes bug 33212;
3593 bugfix on 0.3.5.1-alpha.
3595 o Testing (backport from 0.4.3.1-alpha):
3596 - Re-enable the Travis CI macOS Chutney build, but don't let it
3597 prevent the Travis job from finishing. (The Travis macOS jobs are
3598 slow, so we don't want to have it delay the whole CI process.)
3599 Closes ticket 32629.
3600 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
3601 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
3602 fix the sandbox errors in 32722. Closes ticket 32240.
3604 o Testing (continuous integration, backport from 0.4.3.1-alpha):
3605 - Use zstd in our Travis Linux builds. Closes ticket 32242.
3607 o Testing (Travis CI, backport from 0.4.3.3-alpha):
3608 - Remove a redundant distcheck job. Closes ticket 33194.
3609 - Sort the Travis jobs in order of speed: putting the slowest jobs
3610 first takes full advantage of Travis job concurrency. Closes
3612 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
3613 previously configured to fast_finish (which requires
3614 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
3615 tool to produce detailed diagnostic output. Closes ticket 32792.
3618 Changes in version 0.4.2.6 - 2020-01-30
3619 This is the second stable release in the 0.4.2.x series. It backports
3620 several bugfixes from 0.4.3.1-alpha, including some that had affected
3621 the Linux seccomp2 sandbox or Windows services. If you're running with
3622 one of those configurations, you'll probably want to upgrade;
3623 otherwise, you should be fine with 0.4.2.5.
3625 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
3626 - Correct how we use libseccomp. Particularly, stop assuming that
3627 rules are applied in a particular order or that more rules are
3628 processed after the first match. Neither is the case! In
3629 libseccomp <2.4.0 this led to some rules having no effect.
3630 libseccomp 2.4.0 changed how rules are generated, leading to a
3631 different ordering, which in turn led to a fatal crash during
3632 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
3634 - Fix crash when reloading logging configuration while the
3635 experimental sandbox is enabled. Fixes bug 32841; bugfix on
3636 0.4.1.7. Patch by Peter Gerber.
3638 o Minor bugfixes (correctness checks, backport from 0.4.3.1-alpha):
3639 - Use GCC/Clang's printf-checking feature to make sure that
3640 tor_assertf() arguments are correctly typed. Fixes bug 32765;
3641 bugfix on 0.4.1.1-alpha.
3643 o Minor bugfixes (logging, crash, backport from 0.4.3.1-alpha):
3644 - Avoid a possible crash when trying to log a (fatal) assertion
3645 failure about mismatched magic numbers in configuration objects.
3646 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
3648 o Minor bugfixes (testing, backport from 0.4.3.1-alpha):
3649 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
3650 test_practracker.sh script. Doing so caused a test failure. Fixes
3651 bug 32705; bugfix on 0.4.2.1-alpha.
3652 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
3653 skipping practracker checks. Fixes bug 32705; bugfix
3656 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
3657 - Initialize the publish/subscribe system when running as a windows
3658 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
3660 o Testing (backport from 0.4.3.1-alpha):
3661 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
3662 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
3663 fix the sandbox errors in 32722. Closes ticket 32240.
3664 - Re-enable the Travis CI macOS Chutney build, but don't let it
3665 prevent the Travis job from finishing. (The Travis macOS jobs are
3666 slow, so we don't want to have it delay the whole CI process.)
3667 Closes ticket 32629.
3669 o Testing (continuous integration, backport from 0.4.3.1-alpha):
3670 - Use zstd in our Travis Linux builds. Closes ticket 32242.
3673 Changes in version 0.4.1.8 - 2020-01-30
3674 This release backports several bugfixes from later release series,
3675 including some that had affected the Linux seccomp2 sandbox or Windows
3676 services. If you're running with one of those configurations, you'll
3677 probably want to upgrade; otherwise, you should be fine with your
3678 current version of 0.4.1.x.
3680 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
3681 - Correct how we use libseccomp. Particularly, stop assuming that
3682 rules are applied in a particular order or that more rules are
3683 processed after the first match. Neither is the case! In
3684 libseccomp <2.4.0 this led to some rules having no effect.
3685 libseccomp 2.4.0 changed how rules are generated, leading to a
3686 different ordering, which in turn led to a fatal crash during
3687 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
3689 - Fix crash when reloading logging configuration while the
3690 experimental sandbox is enabled. Fixes bug 32841; bugfix on
3691 0.4.1.7. Patch by Peter Gerber.
3693 o Minor bugfixes (crash, backport form 0.4.2.4-rc):
3694 - When running Tor with an option like --verify-config or
3695 --dump-config that does not start the event loop, avoid crashing
3696 if we try to exit early because of an error. Fixes bug 32407;
3697 bugfix on 0.3.3.1-alpha.
3699 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
3700 - Initialize the publish/subscribe system when running as a windows
3701 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
3703 o Testing (backport from 0.4.3.1-alpha):
3704 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
3705 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
3706 fix the sandbox errors in 32722. Closes ticket 32240.
3707 - Re-enable the Travis CI macOS Chutney build, but don't let it
3708 prevent the Travis job from finishing. (The Travis macOS jobs are
3709 slow, so we don't want to have it delay the whole CI process.)
3710 Closes ticket 32629.
3712 o Testing (continuous integration, backport from 0.4.3.1-alpha):
3713 - Use zstd in our Travis Linux builds. Closes ticket 32242.
3716 Changes in version 0.4.2.5 - 2019-12-09
3717 This is the first stable release in the 0.4.2.x series. This series
3718 improves reliability and stability, and includes several stability and
3719 correctness improvements for onion services. It also fixes many smaller
3720 bugs present in previous series.
3722 Per our support policy, we will support the 0.4.2.x series for nine
3723 months, or until three months after the release of a stable 0.4.3.x:
3724 whichever is longer. If you need longer-term support, please stick
3725 with 0.3.5.x, which will we plan to support until Feb 2022.
3727 Below are the changes since 0.4.1.4-rc. For a complete list of only
3728 the changes since 0.4.2.4-rc, see the ChangeLog file.
3730 o Major features (directory authorities):
3731 - Directory authorities now reject relays running all currently
3732 deprecated release series. The currently supported release series
3733 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
3735 o Major features (onion service v3, denial of service):
3736 - Add onion service introduction denial of service defenses. Intro
3737 points can now rate-limit client introduction requests, using
3738 parameters that can be sent by the service within the
3739 ESTABLISH_INTRO cell. If the cell extension for this is not used,
3740 the intro point will honor the consensus parameters. Closes
3743 o Major bugfixes (circuit build, guard):
3744 - When considering upgrading circuits from "waiting for guard" to
3745 "open", always ignore circuits that are marked for close.
3746 Previously we could end up in the situation where a subsystem is
3747 notified of a circuit opening, but the circuit is still marked for
3748 close, leading to undesirable behavior. Fixes bug 30871; bugfix
3751 o Major bugfixes (crash, Linux, Android):
3752 - Tolerate systems (including some Android installations) where
3753 madvise and MADV_DONTDUMP are available at build-time, but not at
3754 run time. Previously, these systems would notice a failed syscall
3755 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
3756 - Tolerate systems (including some Linux installations) where
3757 madvise and/or MADV_DONTFORK are available at build-time, but not
3758 at run time. Previously, these systems would notice a failed
3759 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
3761 o Major bugfixes (embedded Tor):
3762 - Avoid a possible crash when restarting Tor in embedded mode and
3763 enabling a different set of publish/subscribe messages. Fixes bug
3764 31898; bugfix on 0.4.1.1-alpha.
3766 o Major bugfixes (relay):
3767 - Relays now respect their AccountingMax bandwidth again. When
3768 relays entered "soft" hibernation (which typically starts when
3769 we've hit 90% of our AccountingMax), we had stopped checking
3770 whether we should enter hard hibernation. Soft hibernation refuses
3771 new connections and new circuits, but the existing circuits can
3772 continue, meaning that relays could have exceeded their configured
3773 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
3775 o Major bugfixes (torrc parsing):
3776 - Stop ignoring torrc options after an %include directive, when the
3777 included directory ends with a file that does not contain any
3778 config options (but does contain comments or whitespace). Fixes
3779 bug 31408; bugfix on 0.3.1.1-alpha.
3781 o Major bugfixes (v3 onion services):
3782 - Onion services now always use the exact number of intro points
3783 configured with the HiddenServiceNumIntroductionPoints option (or
3784 fewer if nodes are excluded). Before, a service could sometimes
3785 pick more intro points than configured. Fixes bug 31548; bugfix
3788 o Minor feature (onion services, control port):
3789 - The ADD_ONION command's keyword "BEST" now defaults to ED25519-V3
3790 (v3) onion services. Previously it defaulted to RSA1024 (v2).
3791 Closes ticket 29669.
3793 o Minor features (auto-formatting scripts):
3794 - When annotating C macros, never generate a line that our check-
3795 spaces script would reject. Closes ticket 31759.
3796 - When annotating C macros, try to remove cases of double-negation.
3797 Closes ticket 31779.
3799 o Minor features (best practices tracker):
3800 - Our best-practices tracker now integrates with our include-checker
3801 tool to keep track of how many layering violations we have not yet
3802 fixed. We hope to reduce this number over time to improve Tor's
3803 modularity. Closes ticket 31176.
3804 - Add a TOR_PRACTRACKER_OPTIONS variable for passing arguments to
3805 practracker from the environment. We may want this for continuous
3806 integration. Closes ticket 31309.
3807 - Give a warning rather than an error when a practracker exception
3808 is violated by a small amount, add a --list-overbroad option to
3809 practracker that lists exceptions that are stricter than they need
3810 to be, and provide an environment variable for disabling
3811 practracker. Closes ticket 30752.
3812 - Our best-practices tracker now looks at headers as well as C
3813 files. Closes ticket 31175.
3815 o Minor features (build system):
3816 - Make pkg-config use --prefix when cross-compiling, if
3817 PKG_CONFIG_PATH is not set. Closes ticket 32191.
3818 - Add --disable-manpage and --disable-html-manual options to
3819 configure script. This will enable shortening build times by not
3820 building documentation. Resolves issue 19381.
3822 o Minor features (compilation):
3823 - Log a more useful error message when we are compiling and one of
3824 the compile-time hardening options we have selected can be linked
3825 but not executed. Closes ticket 27530.
3827 o Minor features (configuration):
3828 - The configuration code has been extended to allow splitting
3829 configuration data across multiple objects. Previously, all
3830 configuration data needed to be kept in a single object, which
3831 tended to become bloated. Closes ticket 31240.
3833 o Minor features (continuous integration):
3834 - When building on Appveyor and Travis, pass the "-k" flag to make,
3835 so that we are informed of all compilation failures, not just the
3836 first one or two. Closes ticket 31372.
3837 - When running CI builds on Travis, put some random data in
3838 ~/.torrc, to make sure no tests are reading the Tor configuration
3839 file from its default location. Resolves issue 30102.
3841 o Minor features (debugging):
3842 - Log a nonfatal assertion failure if we encounter a configuration
3843 line whose command is "CLEAR" but which has a nonempty value. This
3844 should be impossible, according to the rules of our configuration
3845 line parsing. Closes ticket 31529.
3847 o Minor features (geoip):
3848 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
3849 Country database. Closes ticket 32685.
3851 o Minor features (git hooks):
3852 - Our pre-commit git hook now checks for a special file before
3853 running practracker, so that practracker only runs on branches
3854 that are based on master. Since the pre-push hook calls the pre-
3855 commit hook, practracker will also only run before pushes of
3856 branches based on master. Closes ticket 30979.
3858 o Minor features (git scripts):
3859 - Add a "--" command-line argument, to separate git-push-all.sh
3860 script arguments from arguments that are passed through to git
3861 push. Closes ticket 31314.
3862 - Add a -r <remote-name> argument to git-push-all.sh, so the script
3863 can push test branches to a personal remote. Closes ticket 31314.
3864 - Add a -t <test-branch-prefix> argument to git-merge-forward.sh and
3865 git-push-all.sh, which makes these scripts create, merge forward,
3866 and push test branches. Closes ticket 31314.
3867 - Add a -u argument to git-merge-forward.sh, so that the script can
3868 re-use existing test branches after a merge failure and fix.
3869 Closes ticket 31314.
3870 - Add a TOR_GIT_PUSH env var, which sets the default git push
3871 command and arguments for git-push-all.sh. Closes ticket 31314.
3872 - Add a TOR_PUSH_DELAY variable to git-push-all.sh, which makes the
3873 script push master and maint branches with a delay between each
3874 branch. These delays trigger the CI jobs in a set order, which
3875 should show the most likely failures first. Also make pushes
3876 atomic by default, and make the script pass any command-line
3877 arguments to git push. Closes ticket 29879.
3878 - Call the shellcheck script from the pre-commit hook. Closes
3880 - Skip pushing test branches that are the same as a remote
3881 maint/release/master branch in git-push-all.sh by default. Add a
3882 -s argument, so git-push-all.sh can push all test branches. Closes
3885 o Minor features (IPv6, logging):
3886 - Log IPv6 addresses as well as IPv4 addresses when describing
3887 routerinfos, routerstatuses, and nodes. Closes ticket 21003.
3889 o Minor features (maintenance scripts):
3890 - Add a Coccinelle script to detect bugs caused by incrementing or
3891 decrementing a variable inside a call to log_debug(). Since
3892 log_debug() is a macro whose arguments are conditionally
3893 evaluated, it is usually an error to do this. One such bug was
3894 30628, in which SENDME cells were miscounted by a decrement
3895 operator inside a log_debug() call. Closes ticket 30743.
3897 o Minor features (onion service v3):
3898 - Do not allow single hop clients to fetch or post an HS descriptor
3899 from an HSDir. Closes ticket 24964.
3901 o Minor features (onion service):
3902 - Disallow single-hop clients at the introduction point. We've
3903 removed Tor2web support a while back and single-hop rendezvous
3904 attempts are blocked at the relays. This change should remove load
3905 off the network from spammy clients. Close ticket 24963.
3907 o Minor features (onion services v3):
3908 - Assist users who try to setup v2 client authorization in v3 onion
3909 services by pointing them to the right documentation. Closes
3912 o Minor features (stem tests):
3913 - Change "make test-stem" so it only runs the stem tests that use
3914 tor. This change makes test-stem faster and more reliable. Closes
3917 o Minor features (testing):
3918 - When running tests that attempt to look up hostnames, replace the
3919 libc name lookup functions with ones that do not actually touch
3920 the network. This way, the tests complete more quickly in the
3921 presence of a slow or missing DNS resolver. Closes ticket 31841.
3922 - Add a script to invoke "tor --dump-config" and "tor
3923 --verify-config" with various configuration options, and see
3924 whether tor's resulting configuration or error messages are what
3925 we expect. Use it for integration testing of our +Option and
3926 /Option flags. Closes ticket 31637.
3927 - Improve test coverage for our existing configuration parsing and
3928 management API. Closes ticket 30893.
3929 - Add integration tests to make sure that practracker gives the
3930 outputs we expect. Closes ticket 31477.
3931 - The practracker self-tests are now run as part of the Tor test
3932 suite. Closes ticket 31304.
3934 o Minor features (testing, continuous integration):
3935 - Disable all but one Travis CI macOS build, to mitigate slow
3936 scheduling of Travis macOS jobs. Closes ticket 32177.
3937 - Run the chutney IPv6 networks as part of Travis CI. Closes
3939 - Simplify the Travis CI build matrix, and optimise for build time.
3940 Closes ticket 31859.
3941 - Use Windows Server 2019 instead of Windows Server 2016 in our
3942 Appveyor builds. Closes ticket 32086.
3944 o Minor features (token bucket):
3945 - Implement a generic token bucket that uses a single counter, for
3946 use in anti-DoS onion service work. Closes ticket 30687.
3948 o Minor bugfixes (Appveyor continuous integration):
3949 - Avoid spurious errors when Appveyor CI fails before the install
3950 step. Fixes bug 31884; bugfix on 0.3.4.2-alpha.
3952 o Minor bugfixes (best practices tracker):
3953 - Fix a few issues in the best-practices script, including tests,
3954 tab tolerance, error reporting, and directory-exclusion logic.
3955 Fixes bug 29746; bugfix on 0.4.1.1-alpha.
3956 - When running check-best-practices, only consider files in the src
3957 subdirectory. Previously we had recursively considered all
3958 subdirectories, which made us get confused by the temporary
3959 directories made by "make distcheck". Fixes bug 31578; bugfix
3962 o Minor bugfixes (build system):
3963 - Interpret "--disable-module-dirauth=no" correctly. Fixes bug
3964 32124; bugfix on 0.3.4.1-alpha.
3965 - Interpret "--with-tcmalloc=no" correctly. Fixes bug 32124; bugfix
3967 - Stop failing when jemalloc is requested, but tcmalloc is not
3968 found. Fixes bug 32124; bugfix on 0.3.5.1-alpha.
3969 - When pkg-config is not installed, or a library that depends on
3970 pkg-config is not found, tell the user what to do to fix the
3971 problem. Fixes bug 31922; bugfix on 0.3.1.1-alpha.
3972 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
3973 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
3975 o Minor bugfixes (chutney, makefiles, documentation):
3976 - "make test-network-all" now shows the warnings from each test-
3977 network.sh run on the console, so developers see new warnings
3978 early. We've also improved the documentation for this feature, and
3979 renamed a Makefile variable so the code is self-documenting. Fixes
3980 bug 30455; bugfix on 0.3.0.4-rc.
3982 o Minor bugfixes (client, onion service v3):
3983 - Fix a BUG() assertion that occurs within a very small race window
3984 between when a client intro circuit opens and when its descriptor
3985 gets cleaned up from the cache. The circuit is now closed early,
3986 which will trigger a re-fetch of the descriptor and continue the
3987 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
3989 o Minor bugfixes (code quality):
3990 - Fix "make check-includes" so it runs correctly on out-of-tree
3991 builds. Fixes bug 31335; bugfix on 0.3.5.1-alpha.
3993 o Minor bugfixes (compilation):
3994 - Add more stub functions to fix compilation on Android with link-
3995 time optimization when --disable-module-dirauth is used.
3996 Previously, these compilation settings would make the compiler
3997 look for functions that didn't exist. Fixes bug 31552; bugfix
3999 - Suppress spurious float-conversion warnings from GCC when calling
4000 floating-point classifier functions on FreeBSD. Fixes part of bug
4001 31687; bugfix on 0.3.1.5-alpha.
4003 o Minor bugfixes (configuration):
4004 - Invalid floating-point values in the configuration file are now
4005 treated as errors in the configuration. Previously, they were
4006 ignored and treated as zero. Fixes bug 31475; bugfix on 0.0.1.
4008 o Minor bugfixes (connections):
4009 - Avoid trying to read data from closed connections, which can cause
4010 needless loops in Libevent and infinite loops in Shadow. Fixes bug
4011 30344; bugfix on 0.1.1.1-alpha.
4013 o Minor bugfixes (controller protocol):
4014 - Fix the MAPADDRESS controller command to accept one or more
4015 arguments. Previously, it required two or more arguments, and
4016 ignored the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
4018 o Minor bugfixes (coverity):
4019 - Add an assertion when parsing a BEGIN cell so that coverity can be
4020 sure that we are not about to dereference a NULL address. Fixes
4021 bug 31026; bugfix on 0.2.4.7-alpha. This is CID 1447296.
4022 - In our siphash implementation, when building for coverity, use
4023 memcpy in place of a switch statement, so that coverity can tell
4024 we are not accessing out-of-bounds memory. Fixes bug 31025; bugfix
4025 on 0.2.8.1-alpha. This is tracked as CID 1447293 and 1447295.
4026 - Fix several coverity warnings from our unit tests. Fixes bug
4027 31030; bugfix on 0.2.4.1-alpha, 0.3.2.1-alpha, and 0.4.0.1-alpha.
4029 o Minor bugfixes (crash):
4030 - When running Tor with an option like --verify-config or
4031 --dump-config that does not start the event loop, avoid crashing
4032 if we try to exit early because of an error. Fixes bug 32407;
4033 bugfix on 0.3.3.1-alpha.
4035 o Minor bugfixes (developer tooling):
4036 - Only log git script changes in the post-merge script when the
4037 merge was to the master branch. Fixes bug 31040; bugfix
4040 o Minor bugfixes (directory authorities):
4041 - Return a distinct status when formatting annotations fails. Fixes
4042 bug 30780; bugfix on 0.2.0.8-alpha.
4044 o Minor bugfixes (error handling):
4045 - Always lock the backtrace buffer before it is used. Fixes bug
4046 31734; bugfix on 0.2.5.3-alpha.
4047 - On abort, try harder to flush the output buffers of log messages.
4048 On some platforms (macOS), log messages could be discarded when
4049 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
4050 - Report the tor version whenever an assertion fails. Previously, we
4051 only reported the Tor version on some crashes, and some non-fatal
4052 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
4053 - When tor aborts due to an error, close log file descriptors before
4054 aborting. Closing the logs makes some OSes flush log file buffers,
4055 rather than deleting buffered log lines. Fixes bug 31594; bugfix
4058 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6):
4059 - When extracting an IPv6 address from a PF-based proxy, verify that
4060 we are actually configured to receive an IPv6 address, and log an
4061 internal error if not. Fixes part of bug 31687; bugfix
4064 o Minor bugfixes (git hooks):
4065 - Remove a duplicate call to practracker from the pre-push hook. The
4066 pre-push hook already calls the pre-commit hook, which calls
4067 practracker. Fixes bug 31462; bugfix on 0.4.1.1-alpha.
4069 o Minor bugfixes (git scripts):
4070 - Stop hard-coding the bash path in the git scripts. Some OSes don't
4071 have bash in /usr/bin, others have an ancient bash at this path.
4072 Fixes bug 30840; bugfix on 0.4.0.1-alpha.
4073 - Stop hard-coding the tor master branch name and worktree path in
4074 the git scripts. Fixes bug 30841; bugfix on 0.4.0.1-alpha.
4075 - Allow git-push-all.sh to be run from any directory. Previously,
4076 the script only worked if run from an upstream worktree directory.
4077 Closes ticket 31678.
4079 o Minor bugfixes (guards):
4080 - When tor is missing descriptors for some primary entry guards,
4081 make the log message less alarming. It's normal for descriptors to
4082 expire, as long as tor fetches new ones soon after. Fixes bug
4083 31657; bugfix on 0.3.3.1-alpha.
4085 o Minor bugfixes (ipv6):
4086 - Check for private IPv6 addresses alongside their IPv4 equivalents
4087 when authorities check descriptors. Previously, we only checked
4088 for private IPv4 addresses. Fixes bug 31088; bugfix on
4089 0.2.3.21-rc. Patch by Neel Chauhan.
4090 - When parsing microdescriptors, we should check the IPv6 exit
4091 policy alongside IPv4. Previously, we checked both exit policies
4092 for only router info structures, while microdescriptors were
4093 IPv4-only. Fixes bug 27284; bugfix on 0.2.3.1-alpha. Patch by
4096 o Minor bugfixes (logging):
4097 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
4098 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
4099 - Disable backtrace signal handlers when shutting down tor. Fixes
4100 bug 31614; bugfix on 0.2.5.2-alpha.
4101 - Rate-limit our the logging message about the obsolete .exit
4102 notation. Previously, there was no limit on this warning, which
4103 could potentially be triggered many times by a hostile website.
4104 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
4105 - When initialising log domain masks, only set known log domains.
4106 Fixes bug 31854; bugfix on 0.2.1.1-alpha.
4107 - Change log level of message "Hash of session info was not as
4108 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
4110 - Fix a code issue that would have broken our parsing of log domains
4111 as soon as we had 33 of them. Fortunately, we still only have 29.
4112 Fixes bug 31451; bugfix on 0.4.1.4-rc.
4114 o Minor bugfixes (logging, protocol violations):
4115 - Do not log a nonfatal assertion failure when receiving a VERSIONS
4116 cell on a connection using the obsolete v1 link protocol. Log a
4117 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
4119 o Minor bugfixes (mainloop, periodic events, in-process API):
4120 - Reset the periodic events' "enabled" flag when Tor is shut down
4121 cleanly. Previously, this flag was left on, which caused periodic
4122 events not to be re-enabled when Tor was relaunched in-process
4123 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
4126 o Minor bugfixes (memory management):
4127 - Stop leaking a small amount of memory in nt_service_install(), in
4128 unreachable code. Fixes bug 30799; bugfix on 0.2.0.7-alpha. Patch
4131 o Minor bugfixes (modules):
4132 - Explain what the optional Directory Authority module is, and what
4133 happens when it is disabled. Fixes bug 31825; bugfix
4136 o Minor bugfixes (multithreading):
4137 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
4138 31736; bugfix on 0.0.7.
4140 o Minor bugfixes (networking, IP addresses):
4141 - When parsing addresses via Tor's internal DNS lookup API, reject
4142 IPv4 addresses in square brackets, and accept IPv6 addresses in
4143 square brackets. This change completes the work started in 23082,
4144 making address parsing consistent between tor's internal DNS
4145 lookup and address parsing APIs. Fixes bug 30721; bugfix
4147 - When parsing addresses via Tor's internal address:port parsing and
4148 DNS lookup APIs, require IPv6 addresses with ports to have square
4149 brackets. But allow IPv6 addresses without ports, whether or not
4150 they have square brackets. Fixes bug 30721; bugfix
4153 o Minor bugfixes (onion service v3):
4154 - When purging the client descriptor cache, close any introduction
4155 point circuits associated with purged cache entries. This avoids
4156 picking those circuits later when connecting to the same
4157 introduction points. Fixes bug 30921; bugfix on 0.3.2.1-alpha.
4159 o Minor bugfixes (onion services):
4160 - In the hs_ident_circuit_t data structure, remove the unused field
4161 circuit_type and the respective argument in hs_ident_circuit_new().
4162 This field was set by clients (for introduction) and services (for
4163 introduction and rendezvous) but was never used afterwards. Fixes
4164 bug 31490; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
4166 o Minor bugfixes (operator tools):
4167 - Make tor-print-ed-signing-cert(1) print certificate expiration
4168 date in RFC 1123 and UNIX timestamp formats, to make output
4169 machine readable. Fixes bug 31012; bugfix on 0.3.5.1-alpha.
4171 o Minor bugfixes (process management):
4172 - Remove overly strict assertions that triggered when a pluggable
4173 transport failed to launch. Fixes bug 31091; bugfix
4175 - Remove an assertion in the Unix process backend. This assertion
4176 would trigger when we failed to find the executable for a child
4177 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
4179 o Minor bugfixes (relay):
4180 - Avoid crashing when starting with a corrupt keys directory where
4181 the old ntor key and the new ntor key are identical. Fixes bug
4182 30916; bugfix on 0.2.4.8-alpha.
4184 o Minor bugfixes (rust):
4185 - Correctly exclude a redundant rust build job in Travis. Fixes bug
4186 31463; bugfix on 0.3.5.4-alpha.
4187 - Raise the minimum rustc version to 1.31.0, as checked by configure
4188 and CI. Fixes bug 31442; bugfix on 0.3.5.4-alpha.
4190 o Minor bugfixes (sendme, code structure):
4191 - Rename the trunnel SENDME file definition from sendme.trunnel to
4192 sendme_cell.trunnel to avoid having twice sendme.{c|h} in the
4193 repository. Fixes bug 30769; bugfix on 0.4.1.1-alpha.
4195 o Minor bugfixes (statistics):
4196 - Stop removing the ed25519 signature if the extra info file is too
4197 big. If the signature data was removed, but the keyword was kept,
4198 this could result in an unparseable extra info file. Fixes bug
4199 30958; bugfix on 0.2.7.2-alpha.
4201 o Minor bugfixes (subsystems):
4202 - Make the subsystem init order match the subsystem module
4203 dependencies. Call windows process security APIs as early as
4204 possible. Initialize logging before network and time, so that
4205 network and time can use logging. Fixes bug 31615; bugfix
4208 o Minor bugfixes (testing):
4209 - Avoid intermittent test failures due to a test that had relied on
4210 inconsistent timing sources. Fixes bug 31995; bugfix
4212 - When testing port rebinding, don't busy-wait for tor to log.
4213 Instead, actually sleep for a short time before polling again.
4214 Also improve the formatting of control commands and log messages.
4215 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
4216 - Teach the util/socketpair_ersatz test to work correctly when we
4217 have no network stack configured. Fixes bug 30804; bugfix
4220 o Minor bugfixes (tests, SunOS):
4221 - Avoid a map_anon_nofork test failure due to a signed/unsigned
4222 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
4224 o Minor bugfixes (tls, logging):
4225 - Log bugs about the TLS read buffer's length only once, rather than
4226 filling the logs with similar warnings. Fixes bug 31939; bugfix
4229 o Minor bugfixes (v2 single onion services):
4230 - Always retry v2 single onion service intro and rend circuits with
4231 a 3-hop path. Previously, v2 single onion services used a 3-hop
4232 path when rendezvous circuits were retried after a remote or
4233 delayed failure, but a 1-hop path for immediate retries. Fixes bug
4234 23818; bugfix on 0.2.9.3-alpha.
4236 o Minor bugfixes (v3 onion services):
4237 - When cleaning up intro circuits for a v3 onion service, don't
4238 remove circuits that have an established or pending circuit, even
4239 if they ran out of retries. This way, we don't remove a circuit on
4240 its last retry. Fixes bug 31652; bugfix on 0.3.2.1-alpha.
4242 o Minor bugfixes (v3 single onion services):
4243 - Always retry v3 single onion service intro and rend circuits with
4244 a 3-hop path. Previously, v3 single onion services used a 3-hop
4245 path when rend circuits were retried after a remote or delayed
4246 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
4247 bugfix on 0.3.2.1-alpha.
4248 - Make v3 single onion services fall back to a 3-hop intro, when all
4249 intro points are unreachable via a 1-hop path. Previously, v3
4250 single onion services failed when all intro nodes were unreachable
4251 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
4253 o Code simplification and refactoring:
4254 - Refactor connection_control_process_inbuf() to reduce the size of
4255 a practracker exception. Closes ticket 31840.
4256 - Refactor the microdescs_parse_from_string() function into smaller
4257 pieces, for better comprehensibility. Closes ticket 31675.
4258 - Use SEVERITY_MASK_IDX() to find the LOG_* mask indexes in the unit
4259 tests and fuzzers, rather than using hard-coded values. Closes
4261 - Interface for function `decrypt_desc_layer` cleaned up. Closes
4265 - Correct the description of "GuardLifetime". Fixes bug 31189;
4266 bugfix on 0.3.0.1-alpha.
4267 - Make clear in the man page, in both the bandwidth section and the
4268 AccountingMax section, that Tor counts in powers of two, not
4269 powers of ten: 1 GByte is 1024*1024*1024 bytes, not one billion
4270 bytes. Resolves ticket 32106.
4271 - Document the signal-safe logging behaviour in the tor man page.
4272 Also add some comments to the relevant functions. Closes
4274 - Explain why we can't destroy the backtrace buffer mutex. Explain
4275 why we don't need to destroy the log mutex. Closes ticket 31736.
4276 - The Tor source code repository now includes a (somewhat dated)
4277 description of Tor's modular architecture, in doc/HACKING/design.
4278 This is based on the old "tor-guts.git" repository, which we are
4279 adopting and superseding. Closes ticket 31849.
4280 - Improve documentation in circuit padding subsystem. Patch by
4281 Tobias Pulls. Closes ticket 31113.
4282 - Include an example usage for IPv6 ORPort in our sample torrc.
4283 Closes ticket 31320; patch from Ali Raheem.
4284 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
4285 notice.html so that operators no longer have to host it
4286 themselves. Closes ticket 31089.
4289 - No longer include recommended package digests in votes as detailed
4290 in proposal 301. The RecommendedPackages torrc option is
4291 deprecated and will no longer have any effect. "package" lines
4292 will still be considered when computing consensuses for consensus
4293 methods that include them. (This change has no effect on the list
4294 of recommended Tor versions, which is still in use.) Closes
4296 - Remove torctl.in from contrib/dist directory. Resolves
4300 - Require C99 standards-conforming code in Travis CI, but allow GNU
4301 gcc extensions. Also activates clang's -Wtypedef-redefinition
4302 warnings. Build some jobs with -std=gnu99, and some jobs without.
4303 Closes ticket 32500.
4304 - Run shellcheck for all non-third-party shell scripts that are
4305 shipped with Tor. Closes ticket 29533.
4306 - When checking shell scripts, ignore any user-created directories.
4307 Closes ticket 30967.
4309 o Code simplification and refactoring (config handling):
4310 - Extract our variable manipulation code from confparse.c to a new
4311 lower-level typedvar.h module. Closes ticket 30864.
4312 - Lower another layer of object management from confparse.c to a
4313 more general tool. Now typed structure members are accessible via
4314 an abstract type. Implements ticket 30914.
4315 - Move our backend logic for working with configuration and state
4316 files into a lower-level library, since it no longer depends on
4317 any tor-specific functionality. Closes ticket 31626.
4318 - Numerous simplifications in configuration-handling logic: remove
4319 duplicated macro definitions, replace magical names with flags,
4320 and refactor "TestingTorNetwork" to use the same default-option
4321 logic as the rest of Tor. Closes ticket 30935.
4322 - Replace our ad-hoc set of flags for configuration variables and
4323 configuration variable types with fine-grained orthogonal flags
4324 corresponding to the actual behavior we want. Closes ticket 31625.
4326 o Code simplification and refactoring (misc):
4327 - Eliminate some uses of lower-level control reply abstractions,
4328 primarily in the onion_helper functions. Closes ticket 30889.
4329 - Rework bootstrap tracking to use the new publish-subscribe
4330 subsystem. Closes ticket 29976.
4331 - Rewrite format_node_description() and router_get_verbose_nickname()
4332 to use strlcpy() and strlcat(). The previous implementation used
4333 memcpy() and pointer arithmetic, which was error-prone. Closes
4334 ticket 31545. This is CID 1452819.
4335 - Split extrainfo_dump_to_string() into smaller functions. Closes
4337 - Use the ptrdiff_t type consistently for expressing variable
4338 offsets and pointer differences. Previously we incorrectly (but
4339 harmlessly) used int and sometimes off_t for these cases. Closes
4341 - Use the subsystems mechanism to manage the main event loop code.
4342 Closes ticket 30806.
4343 - Various simplifications and minor improvements to the circuit
4344 padding machines. Patch by Tobias Pulls. Closes tickets 31112
4347 o Documentation (hard-coded directories):
4348 - Improve the documentation for the DirAuthority and FallbackDir
4349 torrc options. Closes ticket 30955.
4351 o Documentation (tor.1 man page):
4352 - Fix typo in tor.1 man page: the option is "--help", not "-help".
4353 Fixes bug 31008; bugfix on 0.2.2.9-alpha.
4355 o Testing (continuous integration):
4356 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
4357 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
4358 until we can fix some Bionic permissions issues (see ticket
4359 32240). Related to ticket 31919.
4360 - Install the mingw OpenSSL package in Appveyor. This makes sure
4361 that the OpenSSL headers and libraries match in Tor's Appveyor
4362 builds. (This bug was triggered by an Appveyor image update.)
4363 Fixes bug 32449; bugfix on 0.3.5.6-rc.
4364 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
4367 Changes in version 0.4.1.7 - 2019-12-09
4368 This release backports several bugfixes to improve stability and
4369 correctness. Anyone experiencing build problems or crashes with 0.4.1.6,
4370 including all relays relying on AccountingMax, should upgrade.
4372 o Major features (directory authorities, backport from 0.4.2.2-alpha):
4373 - Directory authorities now reject relays running all currently
4374 deprecated release series. The currently supported release series
4375 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
4377 o Major bugfixes (embedded Tor, backport from 0.4.2.2-alpha):
4378 - Avoid a possible crash when restarting Tor in embedded mode and
4379 enabling a different set of publish/subscribe messages. Fixes bug
4380 31898; bugfix on 0.4.1.1-alpha.
4382 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
4383 - Relays now respect their AccountingMax bandwidth again. When
4384 relays entered "soft" hibernation (which typically starts when
4385 we've hit 90% of our AccountingMax), we had stopped checking
4386 whether we should enter hard hibernation. Soft hibernation refuses
4387 new connections and new circuits, but the existing circuits can
4388 continue, meaning that relays could have exceeded their configured
4389 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
4391 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
4392 - Stop ignoring torrc options after an %include directive, when the
4393 included directory ends with a file that does not contain any
4394 config options (but does contain comments or whitespace). Fixes
4395 bug 31408; bugfix on 0.3.1.1-alpha.
4397 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
4398 - Onion services now always use the exact number of intro points
4399 configured with the HiddenServiceNumIntroductionPoints option (or
4400 fewer if nodes are excluded). Before, a service could sometimes
4401 pick more intro points than configured. Fixes bug 31548; bugfix
4404 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
4405 - When building on Appveyor and Travis, pass the "-k" flag to make,
4406 so that we are informed of all compilation failures, not just the
4407 first one or two. Closes ticket 31372.
4409 o Minor features (geoip, backport from 0.4.2.5):
4410 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
4411 Country database. Closes ticket 32685.
4413 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
4414 - Avoid spurious errors when Appveyor CI fails before the install step.
4415 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
4417 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
4418 - Fix a BUG() assertion that occurs within a very small race window
4419 between when a client intro circuit opens and when its descriptor
4420 gets cleaned up from the cache. The circuit is now closed early,
4421 which will trigger a re-fetch of the descriptor and continue the
4422 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
4424 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
4425 - Avoid trying to read data from closed connections, which can cause
4426 needless loops in Libevent and infinite loops in Shadow. Fixes bug
4427 30344; bugfix on 0.1.1.1-alpha.
4429 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
4430 - On abort, try harder to flush the output buffers of log messages.
4431 On some platforms (macOS), log messages could be discarded when
4432 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
4433 - Report the tor version whenever an assertion fails. Previously, we
4434 only reported the Tor version on some crashes, and some non-fatal
4435 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
4436 - When tor aborts due to an error, close log file descriptors before
4437 aborting. Closing the logs makes some OSes flush log file buffers,
4438 rather than deleting buffered log lines. Fixes bug 31594; bugfix
4441 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
4442 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
4443 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
4444 - Disable backtrace signal handlers when shutting down tor. Fixes
4445 bug 31614; bugfix on 0.2.5.2-alpha.
4446 - Rate-limit our the logging message about the obsolete .exit
4447 notation. Previously, there was no limit on this warning, which
4448 could potentially be triggered many times by a hostile website.
4449 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
4451 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
4452 - Do not log a nonfatal assertion failure when receiving a VERSIONS
4453 cell on a connection using the obsolete v1 link protocol. Log a
4454 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
4456 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
4457 - Reset the periodic events' "enabled" flag when Tor is shut down
4458 cleanly. Previously, this flag was left on, which caused periodic
4459 events not to be re-enabled when Tor was relaunched in-process
4460 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
4463 o Minor bugfixes (multithreading, backport from 0.4.2.2-alpha):
4464 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
4465 31736; bugfix on 0.0.7.
4467 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
4468 - Remove overly strict assertions that triggered when a pluggable
4469 transport failed to launch. Fixes bug 31091; bugfix
4471 - Remove an assertion in the Unix process backend. This assertion
4472 would trigger when we failed to find the executable for a child
4473 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
4475 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
4476 - Avoid crashing when starting with a corrupt keys directory where
4477 the old ntor key and the new ntor key are identical. Fixes bug
4478 30916; bugfix on 0.2.4.8-alpha.
4480 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
4481 - When testing port rebinding, don't busy-wait for tor to log.
4482 Instead, actually sleep for a short time before polling again.
4483 Also improve the formatting of control commands and log messages.
4484 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
4486 o Minor bugfixes (tests, SunOS, backport from 0.4.2.2-alpha):
4487 - Avoid a map_anon_nofork test failure due to a signed/unsigned
4488 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
4490 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
4491 - Log bugs about the TLS read buffer's length only once, rather than
4492 filling the logs with similar warnings. Fixes bug 31939; bugfix
4495 o Documentation (backport from 0.4.2.2-alpha):
4496 - Explain why we can't destroy the backtrace buffer mutex. Explain
4497 why we don't need to destroy the log mutex. Closes ticket 31736.
4499 o Testing (continuous integration, backport from 0.4.2.3-alpha):
4500 - Disable all but one Travis CI macOS build, to mitigate slow
4501 scheduling of Travis macOS jobs. Closes ticket 32177.
4502 - Run the chutney IPv6 networks as part of Travis CI. Closes
4504 - Simplify the Travis CI build matrix, and optimise for build time.
4505 Closes ticket 31859.
4506 - Use Windows Server 2019 instead of Windows Server 2016 in our
4507 Appveyor builds. Closes ticket 32086.
4509 o Testing (continuous integration, backport from 0.4.2.4-rc):
4510 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
4511 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
4512 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
4513 until we can fix some Bionic permissions issues (see ticket
4514 32240). Related to ticket 31919.
4515 - Install the mingw OpenSSL package in Appveyor. This makes sure
4516 that the OpenSSL headers and libraries match in Tor's Appveyor
4517 builds. (This bug was triggered by an Appveyor image update.)
4518 Fixes bug 32449; bugfix on 0.3.5.6-rc.
4520 o Testing (continuous integration, backport from 0.4.2.5):
4521 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
4522 extensions. Also activates clang's -Wtypedef-redefinition warnings.
4523 Build some jobs with -std=gnu99, and some jobs without.
4524 Closes ticket 32500.
4527 Changes in version 0.4.0.6 - 2019-12-09
4528 This is the second stable release in the 0.4.0.x series. This release
4529 backports several bugfixes to improve stability and correctness. Anyone
4530 experiencing build problems or crashes with 0.4.0.5, including all relays
4531 relying on AccountingMax, should upgrade.
4533 Note that, per our support policy, support for the 0.4.0.x series will end
4534 on 2 Feb 2020. Anyone still running 0.4.0.x should plan to upgrade to the
4535 latest stable release, or downgrade to 0.3.5.x, which will get long-term
4536 support until 1 Feb 2022.
4538 o Directory authority changes (backport from 0.4.1.5):
4539 - The directory authority "dizum" has a new IP address. Closes
4542 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
4543 - Consider our directory information to have changed when our list
4544 of bridges changes. Previously, Tor would not re-compute the
4545 status of its directory information when bridges changed, and
4546 therefore would not realize that it was no longer able to build
4547 circuits. Fixes part of bug 29875.
4548 - Do not count previously configured working bridges towards our
4549 total of working bridges. Previously, when Tor's list of bridges
4550 changed, it would think that the old bridges were still usable,
4551 and delay fetching router descriptors for the new ones. Fixes part
4552 of bug 29875; bugfix on 0.3.0.1-alpha.
4554 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
4555 - When considering upgrading circuits from "waiting for guard" to
4556 "open", always ignore circuits that are marked for close. Otherwise,
4557 we can end up in the situation where a subsystem is notified that
4558 a closing circuit has just opened, leading to undesirable
4559 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
4561 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
4562 - Properly clean up the introduction point map when circuits change
4563 purpose from onion service circuits to pathbias, measurement, or
4564 other circuit types. This should fix some service-side instances
4565 of introduction point failure. Fixes bug 29034; bugfix
4568 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
4569 - Fix an unreachable bug in which an introduction point could try to
4570 send an INTRODUCE_ACK with a status code that Trunnel would refuse
4571 to encode, leading the relay to assert(). We've consolidated the
4572 ABI values into Trunnel now. Fixes bug 30454; bugfix
4574 - Clients can now handle unknown status codes from INTRODUCE_ACK
4575 cells. (The NACK behavior will stay the same.) This will allow us
4576 to extend status codes in the future without breaking the normal
4577 client behavior. Fixes another part of bug 30454; bugfix
4580 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
4581 - Relays now respect their AccountingMax bandwidth again. When
4582 relays entered "soft" hibernation (which typically starts when
4583 we've hit 90% of our AccountingMax), we had stopped checking
4584 whether we should enter hard hibernation. Soft hibernation refuses
4585 new connections and new circuits, but the existing circuits can
4586 continue, meaning that relays could have exceeded their configured
4587 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
4589 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
4590 - Stop ignoring torrc options after an %include directive, when the
4591 included directory ends with a file that does not contain any
4592 config options (but does contain comments or whitespace). Fixes
4593 bug 31408; bugfix on 0.3.1.1-alpha.
4595 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
4596 - Onion services now always use the exact number of intro points
4597 configured with the HiddenServiceNumIntroductionPoints option (or
4598 fewer if nodes are excluded). Before, a service could sometimes
4599 pick more intro points than configured. Fixes bug 31548; bugfix
4602 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
4603 - Add a "--list-modules" command to print a list of which compile-
4604 time modules are enabled. Closes ticket 30452.
4606 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
4607 - Remove sudo configuration lines from .travis.yml as they are no
4608 longer needed with current Travis build environment. Resolves
4611 o Minor features (continuous integration, backport from 0.4.1.4-rc):
4612 - Our Travis configuration now uses Chutney to run some network
4613 integration tests automatically. Closes ticket 29280.
4615 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
4616 - When building on Appveyor and Travis, pass the "-k" flag to make,
4617 so that we are informed of all compilation failures, not just the
4618 first one or two. Closes ticket 31372.
4620 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
4621 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
4622 in December 2018 (of which ~122 were still functional), with a
4623 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
4624 in June 2019. Closes ticket 28795.
4626 o Minor features (geoip, backport from 0.4.2.5):
4627 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
4628 Country database. Closes ticket 32685.
4630 o Minor features (stem tests, backport from 0.4.2.1-alpha):
4631 - Change "make test-stem" so it only runs the stem tests that use
4632 tor. This change makes test-stem faster and more reliable. Closes
4635 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
4636 - Avoid spurious errors when Appveyor CI fails before the install step.
4637 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
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 (circuit isolation, backport from 0.4.1.3-alpha):
4644 - Fix a logic error that prevented the SessionGroup sub-option from
4645 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
4647 o Minor bugfixes (circuit padding, backport from 0.4.1.4-rc):
4648 - On relays, properly check that a padding machine is absent before
4649 logging a warning about it being absent. Fixes bug 30649; bugfix
4652 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
4653 - Fix a BUG() assertion that occurs within a very small race window
4654 between when a client intro circuit opens and when its descriptor
4655 gets cleaned up from the cache. The circuit is now closed early,
4656 which will trigger a re-fetch of the descriptor and continue the
4657 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
4659 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
4660 - Don't believe clock skew results from NETINFO cells that appear to
4661 arrive before we sent the VERSIONS cells they are responding to.
4662 Previously, we would accept them up to 3 minutes "in the past".
4663 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
4665 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
4666 - Fix a compilation warning on Windows about casting a function
4667 pointer for GetTickCount64(). Fixes bug 31374; bugfix
4670 o Minor bugfixes (compilation, backport from 0.4.1.5):
4671 - Avoid using labs() on time_t, which can cause compilation warnings
4672 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
4674 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
4675 - Suppress spurious float-conversion warnings from GCC when calling
4676 floating-point classifier functions on FreeBSD. Fixes part of bug
4677 31687; bugfix on 0.3.1.5-alpha.
4679 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
4680 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
4681 due to missing declarations of abort(), and prevent other such
4682 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
4684 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
4685 - Fix a bug that prevented us from supporting SOCKS5 proxies that
4686 want authentication along with configured (but unused!)
4687 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
4689 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
4690 - Avoid trying to read data from closed connections, which can cause
4691 needless loops in Libevent and infinite loops in Shadow. Fixes bug
4692 30344; bugfix on 0.1.1.1-alpha.
4694 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
4695 - Allow the test-stem job to fail in Travis, because it sometimes
4696 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
4697 - Skip test_rebind on macOS in Travis, because it is unreliable on
4698 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
4699 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
4700 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
4702 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
4703 - Avoid a set of possible code paths that could try to use freed
4704 memory in routerlist_free() while Tor was exiting. Fixes bug
4705 31003; bugfix on 0.1.2.2-alpha.
4707 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
4708 - Stop crashing after parsing an unknown descriptor purpose
4709 annotation. We think this bug can only be triggered by modifying a
4710 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
4712 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
4713 - Move the "bandwidth-file-headers" line in directory authority
4714 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
4717 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
4718 - On abort, try harder to flush the output buffers of log messages.
4719 On some platforms (macOS), log messages could be discarded when
4720 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
4721 - Report the tor version whenever an assertion fails. Previously, we
4722 only reported the Tor version on some crashes, and some non-fatal
4723 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
4725 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
4726 - When extracting an IPv6 address from a PF-based proxy, verify that
4727 we are actually configured to receive an IPv6 address, and log an
4728 internal error if not. Fixes part of bug 31687; bugfix
4731 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
4732 - When tor is missing descriptors for some primary entry guards,
4733 make the log message less alarming. It's normal for descriptors to
4734 expire, as long as tor fetches new ones soon after. Fixes bug
4735 31657; bugfix on 0.3.3.1-alpha.
4737 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
4738 - Do not log a warning when running with an OpenSSL version other
4739 than the one Tor was compiled with, if the two versions should be
4740 compatible. Previously, we would warn whenever the version was
4741 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
4743 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
4744 - Change log level of message "Hash of session info was not as
4745 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
4748 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
4749 - Rate-limit our the logging message about the obsolete .exit
4750 notation. Previously, there was no limit on this warning, which
4751 could potentially be triggered many times by a hostile website.
4752 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
4754 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
4755 - Do not log a nonfatal assertion failure when receiving a VERSIONS
4756 cell on a connection using the obsolete v1 link protocol. Log a
4757 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
4759 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
4760 - Reset the periodic events' "enabled" flag when Tor is shut down
4761 cleanly. Previously, this flag was left on, which caused periodic
4762 events not to be re-enabled when Tor was relaunched in-process
4763 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
4766 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
4767 - Avoid a minor memory leak that could occur on relays when failing
4768 to create a "keys" directory. Fixes bug 30148; bugfix
4771 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
4772 - Fix a trivial memory leak when parsing an invalid value
4773 from a download schedule in the configuration. Fixes bug
4774 30894; bugfix on 0.3.4.1-alpha.
4776 o Minor bugfixes (NetBSD, backport from 0.4.1.2-alpha):
4777 - Fix usage of minherit() on NetBSD and other platforms that define
4778 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
4779 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
4781 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
4782 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
4783 implemenation) when failing to load an onion service client
4784 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
4786 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
4787 - When purging the DNS cache because of an out-of-memory condition,
4788 try purging just the older entries at first. Previously, we would
4789 always purge the whole thing. Fixes bug 29617; bugfix
4792 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
4793 - Avoid crashing in our tor_vasprintf() implementation on systems
4794 that define neither vasprintf() nor _vscprintf(). (This bug has
4795 been here long enough that we question whether people are running
4796 Tor on such systems, but we're applying the fix out of caution.)
4797 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
4800 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
4801 - Remove overly strict assertions that triggered when a pluggable
4802 transport failed to launch. Fixes bug 31091; bugfix
4804 - Remove an assertion in the Unix process backend. This assertion
4805 would trigger when we failed to find the executable for a child
4806 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
4808 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
4809 - Avoid crashing when starting with a corrupt keys directory where
4810 the old ntor key and the new ntor key are identical. Fixes bug
4811 30916; bugfix on 0.2.4.8-alpha.
4813 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
4814 - Correctly exclude a redundant rust build job in Travis. Fixes bug
4815 31463; bugfix on 0.3.5.4-alpha.
4817 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
4818 - When testing port rebinding, don't busy-wait for tor to log.
4819 Instead, actually sleep for a short time before polling again.
4820 Also improve the formatting of control commands and log messages.
4821 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
4823 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
4824 - Log bugs about the TLS read buffer's length only once, rather than
4825 filling the logs with similar warnings. Fixes bug 31939; bugfix
4828 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
4829 - Always retry v2 single onion service intro and rend circuits with
4830 a 3-hop path. Previously, v2 single onion services used a 3-hop
4831 path when rendezvous circuits were retried after a remote or
4832 delayed failure, but a 1-hop path for immediate retries. Fixes bug
4833 23818; bugfix on 0.2.9.3-alpha.
4834 - Make v3 single onion services fall back to a 3-hop intro, when all
4835 intro points are unreachable via a 1-hop path. Previously, v3
4836 single onion services failed when all intro nodes were unreachable
4837 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
4839 o Documentation (backport from 0.4.2.1-alpha):
4840 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
4841 notice.html so that operators no longer have to host it
4842 themselves. Closes ticket 31089.
4844 o Testing (backport from 0.4.1.2-alpha):
4845 - Specify torrc paths (with empty files) when launching tor in
4846 integration tests; refrain from reading user and system torrcs.
4847 Resolves issue 29702.
4849 o Testing (continuous integration, backport from 0.4.1.1-alpha):
4850 - In Travis, show stem's tor log after failure. Closes ticket 30234.
4852 o Testing (continuous integration, backport from 0.4.1.5):
4853 - In Travis, make stem log a controller trace to the console, and
4854 tail stem's tor log after failure. Closes ticket 30591.
4855 - In Travis, only run the stem tests that use a tor binary. Closes
4858 o Testing (continuous integration, backport from 0.4.2.3-alpha):
4859 - Disable all but one Travis CI macOS build, to mitigate slow
4860 scheduling of Travis macOS jobs. Closes ticket 32177.
4861 - Run the chutney IPv6 networks as part of Travis CI. Closes
4863 - Simplify the Travis CI build matrix, and optimise for build time.
4864 Closes ticket 31859.
4865 - Use Windows Server 2019 instead of Windows Server 2016 in our
4866 Appveyor builds. Closes ticket 32086.
4868 o Testing (continuous integration, backport from 0.4.2.4-rc):
4869 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
4870 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
4871 until we can fix some Bionic permissions issues (see ticket
4872 32240). Related to ticket 31919.
4873 - Install the mingw OpenSSL package in Appveyor. This makes sure
4874 that the OpenSSL headers and libraries match in Tor's Appveyor
4875 builds. (This bug was triggered by an Appveyor image update.)
4876 Fixes bug 32449; bugfix on 0.3.5.6-rc.
4877 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
4879 o Testing (continuous integration, backport from 0.4.2.5):
4880 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
4881 extensions. Also activates clang's -Wtypedef-redefinition warnings.
4882 Build some jobs with -std=gnu99, and some jobs without.
4883 Closes ticket 32500.
4886 Changes in version 0.3.5.9 - 2019-12-09
4887 Tor 0.3.5.9 backports serveral fixes from later releases, including
4888 several that affect bridge users, relay stability, onion services,
4891 o Directory authority changes (backport from 0.4.1.5):
4892 - The directory authority "dizum" has a new IP address. Closes
4895 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
4896 - Consider our directory information to have changed when our list
4897 of bridges changes. Previously, Tor would not re-compute the
4898 status of its directory information when bridges changed, and
4899 therefore would not realize that it was no longer able to build
4900 circuits. Fixes part of bug 29875.
4901 - Do not count previously configured working bridges towards our
4902 total of working bridges. Previously, when Tor's list of bridges
4903 changed, it would think that the old bridges were still usable,
4904 and delay fetching router descriptors for the new ones. Fixes part
4905 of bug 29875; bugfix on 0.3.0.1-alpha.
4907 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
4908 - When considering upgrading circuits from "waiting for guard" to
4909 "open", always ignore circuits that are marked for close. Otherwise,
4910 we can end up in the situation where a subsystem is notified that
4911 a closing circuit has just opened, leading to undesirable
4912 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
4914 o Major bugfixes (NSS, relay, backport from 0.4.0.4-rc):
4915 - When running with NSS, disable TLS 1.2 ciphersuites that use
4916 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
4917 these ciphersuites don't work -- which caused relays to fail to
4918 handshake with one another when these ciphersuites were enabled.
4919 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
4921 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
4922 - Properly clean up the introduction point map when circuits change
4923 purpose from onion service circuits to pathbias, measurement, or
4924 other circuit types. This should fix some service-side instances
4925 of introduction point failure. Fixes bug 29034; bugfix
4928 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
4929 - Fix an unreachable bug in which an introduction point could try to
4930 send an INTRODUCE_ACK with a status code that Trunnel would refuse
4931 to encode, leading the relay to assert(). We've consolidated the
4932 ABI values into Trunnel now. Fixes bug 30454; bugfix
4934 - Clients can now handle unknown status codes from INTRODUCE_ACK
4935 cells. (The NACK behavior will stay the same.) This will allow us
4936 to extend status codes in the future without breaking the normal
4937 client behavior. Fixes another part of bug 30454; bugfix
4940 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
4941 - Stop ignoring torrc options after an %include directive, when the
4942 included directory ends with a file that does not contain any
4943 config options (but does contain comments or whitespace). Fixes
4944 bug 31408; bugfix on 0.3.1.1-alpha.
4946 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
4947 - Onion services now always use the exact number of intro points
4948 configured with the HiddenServiceNumIntroductionPoints option (or
4949 fewer if nodes are excluded). Before, a service could sometimes
4950 pick more intro points than configured. Fixes bug 31548; bugfix
4953 o Minor features (address selection, backport from 0.4.0.3-alpha):
4954 - Treat the subnet 100.64.0.0/10 as public for some purposes;
4955 private for others. This subnet is the RFC 6598 (Carrier Grade
4956 NAT) IP range, and is deployed by many ISPs as an alternative to
4957 RFC 1918 that does not break existing internal networks. Tor now
4958 blocks SOCKS and control ports on these addresses and warns users
4959 if client ports or ExtORPorts are listening on a RFC 6598 address.
4960 Closes ticket 28525. Patch by Neel Chauhan.
4962 o Minor features (bandwidth authority, backport from 0.4.0.4-rc):
4963 - Make bandwidth authorities ignore relays that are reported in the
4964 bandwidth file with the flag "vote=0". This change allows us to
4965 report unmeasured relays for diagnostic reasons without including
4966 their bandwidth in the bandwidth authorities' vote. Closes
4969 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
4970 - Add a "--list-modules" command to print a list of which compile-
4971 time modules are enabled. Closes ticket 30452.
4973 o Minor features (continuous integration, backport from 0.4.0.4-rc):
4974 - On Travis Rust builds, cleanup Rust registry and refrain from
4975 caching the "target/" directory to speed up builds. Resolves
4978 o Minor features (continuous integration, backport from 0.4.0.5):
4979 - In Travis, tell timelimit to use stem's backtrace signals, and
4980 launch python directly from timelimit, so python receives the
4981 signals from timelimit, rather than make. Closes ticket 30117.
4983 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
4984 - Remove sudo configuration lines from .travis.yml as they are no
4985 longer needed with current Travis build environment. Resolves
4988 o Minor features (continuous integration, backport from 0.4.1.4-rc):
4989 - Our Travis configuration now uses Chutney to run some network
4990 integration tests automatically. Closes ticket 29280.
4992 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
4993 - When building on Appveyor and Travis, pass the "-k" flag to make,
4994 so that we are informed of all compilation failures, not just the
4995 first one or two. Closes ticket 31372.
4997 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
4998 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
4999 in December 2018 (of which ~122 were still functional), with a
5000 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
5001 in June 2019. Closes ticket 28795.
5003 o Minor features (geoip, backport from 0.4.2.5):
5004 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
5005 Country database. Closes ticket 32685.
5007 o Minor features (NSS, diagnostic, backport from 0.4.0.4-rc):
5008 - Try to log an error from NSS (if there is any) and a more useful
5009 description of our situation if we are using NSS and a call to
5010 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
5012 o Minor features (stem tests, backport from 0.4.2.1-alpha):
5013 - Change "make test-stem" so it only runs the stem tests that use
5014 tor. This change makes test-stem faster and more reliable. Closes
5017 o Minor bugfixes (security, backport from 0.4.0.4-rc):
5018 - Verify in more places that we are not about to create a buffer
5019 with more than INT_MAX bytes, to avoid possible OOB access in the
5020 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
5021 fixed by Tobias Stoeckmann.
5022 - Fix a potential double free bug when reading huge bandwidth files.
5023 The issue is not exploitable in the current Tor network because
5024 the vulnerable code is only reached when directory authorities
5025 read bandwidth files, but bandwidth files come from a trusted
5026 source (usually the authorities themselves). Furthermore, the
5027 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
5028 which are not used by any of the current authorities. Fixes bug
5029 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
5032 o Minor bugfix (continuous integration, backport from 0.4.0.4-rc):
5033 - Reset coverage state on disk after Travis CI has finished. This
5034 should prevent future coverage merge errors from causing the test
5035 suite for the "process" subsystem to fail. The process subsystem
5036 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
5038 - Terminate test-stem if it takes more than 9.5 minutes to run.
5039 (Travis terminates the job after 10 minutes of no output.)
5040 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
5042 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
5043 - Avoid spurious errors when Appveyor CI fails before the install step.
5044 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
5046 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
5047 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
5048 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
5050 o Minor bugfixes (C correctness, backport from 0.4.0.4-rc):
5051 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
5052 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
5055 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
5056 - Fix a logic error that prevented the SessionGroup sub-option from
5057 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
5059 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
5060 - Fix a BUG() assertion that occurs within a very small race window
5061 between when a client intro circuit opens and when its descriptor
5062 gets cleaned up from the cache. The circuit is now closed early,
5063 which will trigger a re-fetch of the descriptor and continue the
5064 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
5066 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
5067 - Don't believe clock skew results from NETINFO cells that appear to
5068 arrive before we sent the VERSIONS cells they are responding to.
5069 Previously, we would accept them up to 3 minutes "in the past".
5070 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
5072 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
5073 - Fix a compilation warning on Windows about casting a function
5074 pointer for GetTickCount64(). Fixes bug 31374; bugfix
5077 o Minor bugfixes (compilation, backport from 0.4.0.2-alpha):
5078 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
5079 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
5081 o Minor bugfixes (compilation, backport from 0.4.1.5):
5082 - Avoid using labs() on time_t, which can cause compilation warnings
5083 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
5085 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
5086 - Suppress spurious float-conversion warnings from GCC when calling
5087 floating-point classifier functions on FreeBSD. Fixes part of bug
5088 31687; bugfix on 0.3.1.5-alpha.
5090 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
5091 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
5092 due to missing declarations of abort(), and prevent other such
5093 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
5095 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
5096 - Fix a bug that prevented us from supporting SOCKS5 proxies that
5097 want authentication along with configured (but unused!)
5098 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
5100 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
5101 - Avoid trying to read data from closed connections, which can cause
5102 needless loops in Libevent and infinite loops in Shadow. Fixes bug
5103 30344; bugfix on 0.1.1.1-alpha.
5105 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
5106 - Allow the test-stem job to fail in Travis, because it sometimes
5107 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
5108 - Skip test_rebind on macOS in Travis, because it is unreliable on
5109 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
5110 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
5111 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
5113 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
5114 - Avoid a set of possible code paths that could try to use freed
5115 memory in routerlist_free() while Tor was exiting. Fixes bug
5116 31003; bugfix on 0.1.2.2-alpha.
5118 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
5119 - Stop crashing after parsing an unknown descriptor purpose
5120 annotation. We think this bug can only be triggered by modifying a
5121 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
5123 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
5124 - Move the "bandwidth-file-headers" line in directory authority
5125 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
5128 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
5129 - On abort, try harder to flush the output buffers of log messages.
5130 On some platforms (macOS), log messages could be discarded when
5131 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
5132 - Report the tor version whenever an assertion fails. Previously, we
5133 only reported the Tor version on some crashes, and some non-fatal
5134 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
5136 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
5137 - When extracting an IPv6 address from a PF-based proxy, verify that
5138 we are actually configured to receive an IPv6 address, and log an
5139 internal error if not. Fixes part of bug 31687; bugfix
5142 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
5143 - When tor is missing descriptors for some primary entry guards,
5144 make the log message less alarming. It's normal for descriptors to
5145 expire, as long as tor fetches new ones soon after. Fixes bug
5146 31657; bugfix on 0.3.3.1-alpha.
5148 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
5149 - Avoid logging that we are relaxing a circuit timeout when that
5150 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
5152 o Minor bugfixes (logging, backport from 0.4.0.3-alpha):
5153 - Correct a misleading error message when IPv4Only or IPv6Only is
5154 used but the resolved address can not be interpreted as an address
5155 of the specified IP version. Fixes bug 13221; bugfix on
5156 0.2.3.9-alpha. Patch from Kris Katterjohn.
5157 - Log the correct port number for listening sockets when "auto" is
5158 used to let Tor pick the port number. Previously, port 0 was
5159 logged instead of the actual port number. Fixes bug 29144; bugfix
5160 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
5161 - Stop logging a BUG() warning when Tor is waiting for exit
5162 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
5164 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
5165 - Do not log a warning when running with an OpenSSL version other
5166 than the one Tor was compiled with, if the two versions should be
5167 compatible. Previously, we would warn whenever the version was
5168 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
5170 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
5171 - Change log level of message "Hash of session info was not as
5172 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
5175 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
5176 - Rate-limit our the logging message about the obsolete .exit
5177 notation. Previously, there was no limit on this warning, which
5178 could potentially be triggered many times by a hostile website.
5179 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
5181 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
5182 - Do not log a nonfatal assertion failure when receiving a VERSIONS
5183 cell on a connection using the obsolete v1 link protocol. Log a
5184 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
5186 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
5187 - Reset the periodic events' "enabled" flag when Tor is shut down
5188 cleanly. Previously, this flag was left on, which caused periodic
5189 events not to be re-enabled when Tor was relaunched in-process
5190 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
5193 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
5194 - Avoid a minor memory leak that could occur on relays when failing
5195 to create a "keys" directory. Fixes bug 30148; bugfix
5198 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
5199 - Fix a trivial memory leak when parsing an invalid value
5200 from a download schedule in the configuration. Fixes bug
5201 30894; bugfix on 0.3.4.1-alpha.
5203 o Minor bugfixes (memory management, backport from 0.4.0.3-alpha):
5204 - Refactor the shared random state's memory management so that it
5205 actually takes ownership of the shared random value pointers.
5206 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
5208 o Minor bugfixes (memory management, testing, backport from 0.4.0.3-alpha):
5209 - Stop leaking parts of the shared random state in the shared-random
5210 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
5212 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
5213 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
5214 implemenation) when failing to load an onion service client
5215 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
5217 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
5218 - When purging the DNS cache because of an out-of-memory condition,
5219 try purging just the older entries at first. Previously, we would
5220 always purge the whole thing. Fixes bug 29617; bugfix
5223 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
5224 - Avoid crashing in our tor_vasprintf() implementation on systems
5225 that define neither vasprintf() nor _vscprintf(). (This bug has
5226 been here long enough that we question whether people are running
5227 Tor on such systems, but we're applying the fix out of caution.)
5228 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
5231 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
5232 - Avoid crashing when starting with a corrupt keys directory where
5233 the old ntor key and the new ntor key are identical. Fixes bug
5234 30916; bugfix on 0.2.4.8-alpha.
5236 o Minor bugfixes (rust, backport from 0.4.0.5):
5237 - Abort on panic in all build profiles, instead of potentially
5238 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
5240 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
5241 - Correctly exclude a redundant rust build job in Travis. Fixes bug
5242 31463; bugfix on 0.3.5.4-alpha.
5244 o Minor bugfixes (single onion services, backport from 0.4.0.3-alpha):
5245 - Allow connections to single onion services to remain idle without
5246 being disconnected. Previously, relays acting as rendezvous points
5247 for single onion services were mistakenly closing idle rendezvous
5248 circuits after 60 seconds, thinking that they were unused
5249 directory-fetching circuits that had served their purpose. Fixes
5250 bug 29665; bugfix on 0.2.1.26.
5252 o Minor bugfixes (stats, backport from 0.4.0.3-alpha):
5253 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
5254 relay and bridge extra-info documents. Fixes bug 29017; bugfix
5257 o Minor bugfixes (testing, backport from 0.4.0.3-alpha):
5258 - Downgrade some LOG_ERR messages in the address/* tests to
5259 warnings. The LOG_ERR messages were occurring when we had no
5260 configured network. We were failing the unit tests, because we
5261 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
5262 29530; bugfix on 0.3.5.8.
5263 - Fix our gcov wrapper script to look for object files at the
5264 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
5266 o Minor bugfixes (testing, backport from 0.4.0.4-rc):
5267 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
5268 recent test-network.sh to use new chutney features in CI. Fixes
5269 bug 29703; bugfix on 0.2.9.1-alpha.
5270 - Fix a test failure on Windows caused by an unexpected "BUG"
5271 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
5274 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
5275 - When testing port rebinding, don't busy-wait for tor to log.
5276 Instead, actually sleep for a short time before polling again.
5277 Also improve the formatting of control commands and log messages.
5278 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
5280 o Minor bugfixes (TLS protocol, backport form 0.4.0.4-rc):
5281 - When classifying a client's selection of TLS ciphers, if the
5282 client ciphers are not yet available, do not cache the result.
5283 Previously, we had cached the unavailability of the cipher list
5284 and never looked again, which in turn led us to assume that the
5285 client only supported the ancient V1 link protocol. This, in turn,
5286 was causing Stem integration tests to stall in some cases. Fixes
5287 bug 30021; bugfix on 0.2.4.8-alpha.
5289 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
5290 - Log bugs about the TLS read buffer's length only once, rather than
5291 filling the logs with similar warnings. Fixes bug 31939; bugfix
5294 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
5295 - Always retry v2 single onion service intro and rend circuits with
5296 a 3-hop path. Previously, v2 single onion services used a 3-hop
5297 path when rendezvous circuits were retried after a remote or
5298 delayed failure, but a 1-hop path for immediate retries. Fixes bug
5299 23818; bugfix on 0.2.9.3-alpha.
5300 - Make v3 single onion services fall back to a 3-hop intro, when all
5301 intro points are unreachable via a 1-hop path. Previously, v3
5302 single onion services failed when all intro nodes were unreachable
5303 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
5305 o Minor bugfixes (Windows, CI, backport from 0.4.0.3-alpha):
5306 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
5307 Windows Server 2012 R2 job. The remaining 2 jobs still provide
5308 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
5309 fast_finish, so failed jobs terminate the build immediately. Fixes
5310 bug 29601; bugfix on 0.3.5.4-alpha.
5312 o Documentation (backport from 0.4.2.1-alpha):
5313 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
5314 notice.html so that operators no longer have to host it
5315 themselves. Closes ticket 31089.
5317 o Testing (backport from 0.4.1.2-alpha):
5318 - Specify torrc paths (with empty files) when launching tor in
5319 integration tests; refrain from reading user and system torrcs.
5320 Resolves issue 29702.
5322 o Testing (continuous integration, backport from 0.4.1.1-alpha):
5323 - In Travis, show stem's tor log after failure. Closes ticket 30234.
5325 o Testing (continuous integration, backport from 0.4.1.5):
5326 - In Travis, make stem log a controller trace to the console, and
5327 tail stem's tor log after failure. Closes ticket 30591.
5328 - In Travis, only run the stem tests that use a tor binary. Closes
5331 o Testing (continuous integration, backport from 0.4.2.3-alpha):
5332 - Disable all but one Travis CI macOS build, to mitigate slow
5333 scheduling of Travis macOS jobs. Closes ticket 32177.
5334 - Run the chutney IPv6 networks as part of Travis CI. Closes
5336 - Simplify the Travis CI build matrix, and optimise for build time.
5337 Closes ticket 31859.
5338 - Use Windows Server 2019 instead of Windows Server 2016 in our
5339 Appveyor builds. Closes ticket 32086.
5341 o Testing (continuous integration, backport from 0.4.2.4-rc):
5342 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
5343 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
5344 until we can fix some Bionic permissions issues (see ticket
5345 32240). Related to ticket 31919.
5346 - Install the mingw OpenSSL package in Appveyor. This makes sure
5347 that the OpenSSL headers and libraries match in Tor's Appveyor
5348 builds. (This bug was triggered by an Appveyor image update.)
5349 Fixes bug 32449; bugfix on 0.3.5.6-rc.
5350 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
5352 o Testing (continuous integration, backport from 0.4.2.5):
5353 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
5354 extensions. Also activates clang's -Wtypedef-redefinition warnings.
5355 Build some jobs with -std=gnu99, and some jobs without.
5356 Closes ticket 32500.
5359 Changes in version 0.4.1.6 - 2019-09-19
5360 This release backports several bugfixes to improve stability and
5361 correctness. Anyone experiencing build problems or crashes with 0.4.1.5,
5362 or experiencing reliability issues with single onion services, should
5365 o Major bugfixes (crash, Linux, Android, backport from 0.4.2.1-alpha):
5366 - Tolerate systems (including some Android installations) where
5367 madvise and MADV_DONTDUMP are available at build-time, but not at
5368 run time. Previously, these systems would notice a failed syscall
5369 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
5370 - Tolerate systems (including some Linux installations) where
5371 madvise and/or MADV_DONTFORK are available at build-time, but not
5372 at run time. Previously, these systems would notice a failed
5373 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
5375 o Minor features (stem tests, backport from 0.4.2.1-alpha):
5376 - Change "make test-stem" so it only runs the stem tests that use
5377 tor. This change makes test-stem faster and more reliable. Closes
5380 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
5381 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
5382 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
5384 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
5385 - Add more stub functions to fix compilation on Android with link-
5386 time optimization when --disable-module-dirauth is used.
5387 Previously, these compilation settings would make the compiler
5388 look for functions that didn't exist. Fixes bug 31552; bugfix
5390 - Suppress spurious float-conversion warnings from GCC when calling
5391 floating-point classifier functions on FreeBSD. Fixes part of bug
5392 31687; bugfix on 0.3.1.5-alpha.
5394 o Minor bugfixes (controller protocol):
5395 - Fix the MAPADDRESS controller command to accept one or more
5396 arguments. Previously, it required two or more arguments, and ignored
5397 the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
5399 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
5400 - When extracting an IPv6 address from a PF-based proxy, verify that
5401 we are actually configured to receive an IPv6 address, and log an
5402 internal error if not. Fixes part of bug 31687; bugfix
5405 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
5406 - When tor is missing descriptors for some primary entry guards,
5407 make the log message less alarming. It's normal for descriptors to
5408 expire, as long as tor fetches new ones soon after. Fixes bug
5409 31657; bugfix on 0.3.3.1-alpha.
5411 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
5412 - Change log level of message "Hash of session info was not as
5413 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
5416 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
5417 - Correctly exclude a redundant rust build job in Travis. Fixes bug
5418 31463; bugfix on 0.3.5.4-alpha.
5420 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
5421 - Always retry v2 single onion service intro and rend circuits with
5422 a 3-hop path. Previously, v2 single onion services used a 3-hop
5423 path when rendezvous circuits were retried after a remote or
5424 delayed failure, but a 1-hop path for immediate retries. Fixes bug
5425 23818; bugfix on 0.2.9.3-alpha.
5427 o Minor bugfixes (v3 single onion services, backport from 0.4.2.1-alpha):
5428 - Always retry v3 single onion service intro and rend circuits with
5429 a 3-hop path. Previously, v3 single onion services used a 3-hop
5430 path when rend circuits were retried after a remote or delayed
5431 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
5432 bugfix on 0.3.2.1-alpha.
5433 - Make v3 single onion services fall back to a 3-hop intro, when all
5434 intro points are unreachable via a 1-hop path. Previously, v3
5435 single onion services failed when all intro nodes were unreachable
5436 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
5438 o Documentation (backport from 0.4.2.1-alpha):
5439 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
5440 notice.html so that operators no longer have to host it
5441 themselves. Closes ticket 31089.
5444 Changes in version 0.4.1.5 - 2019-08-20
5445 This is the first stable release in the 0.4.1.x series. This series
5446 adds experimental circuit-level padding, authenticated SENDME cells to
5447 defend against certain attacks, and several performance improvements
5448 to save on CPU consumption. It fixes bugs in bootstrapping and v3
5449 onion services. It also includes numerous smaller features and
5450 bugfixes on earlier versions.
5452 Per our support policy, we will support the 0.4.1.x series for nine
5453 months, or until three months after the release of a stable 0.4.2.x:
5454 whichever is longer. If you need longer-term support, please stick
5455 with 0.3.5.x, which will we plan to support until Feb 2022.
5457 Below are the changes since 0.4.0.5. For a list of only the changes
5458 since 0.4.1.4-rc, see the ChangeLog file.
5460 o Directory authority changes:
5461 - The directory authority "dizum" has a new IP address. Closes
5464 o Major features (circuit padding):
5465 - Onion service clients now add padding cells at the start of their
5466 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
5467 look more like general purpose Exit traffic. The overhead for this
5468 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
5469 extra upstream cell and 10 downstream cells for INTRODUCE
5470 circuits. This feature is only enabled when also supported by the
5471 circuit's middle node. (Clients may specify fixed middle nodes
5472 with the MiddleNodes option, and may force-disable this feature
5473 with the CircuitPadding option.) Closes ticket 28634.
5475 o Major features (code organization):
5476 - Tor now includes a generic publish-subscribe message-passing
5477 subsystem that we can use to organize intermodule dependencies. We
5478 hope to use this to reduce dependencies between modules that don't
5479 need to be related, and to generally simplify our codebase. Closes
5482 o Major features (controller protocol):
5483 - Controller commands are now parsed using a generalized parsing
5484 subsystem. Previously, each controller command was responsible for
5485 parsing its own input, which led to strange inconsistencies.
5486 Closes ticket 30091.
5488 o Major features (flow control):
5489 - Implement authenticated SENDMEs as detailed in proposal 289. A
5490 SENDME cell now includes the digest of the traffic that it
5491 acknowledges, so that once an end point receives the SENDME, it
5492 can confirm the other side's knowledge of the previous cells that
5493 were sent, and prevent certain types of denial-of-service attacks.
5494 This behavior is controlled by two new consensus parameters: see
5495 the proposal for more details. Fixes ticket 26288.
5497 o Major features (performance):
5498 - Our node selection algorithm now excludes nodes in linear time.
5499 Previously, the algorithm was quadratic, which could slow down
5500 heavily used onion services. Closes ticket 30307.
5502 o Major features (performance, RNG):
5503 - Tor now constructs a fast secure pseudorandom number generator for
5504 each thread, to use when performance is critical. This PRNG is
5505 based on AES-CTR, using a buffering construction similar to
5506 libottery and the (newer) OpenBSD arc4random() code. It
5507 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
5508 small outputs. Although we believe it to be cryptographically
5509 strong, we are only using it when necessary for performance.
5510 Implements tickets 29023 and 29536.
5512 o Major bugfixes (bridges):
5513 - Consider our directory information to have changed when our list
5514 of bridges changes. Previously, Tor would not re-compute the
5515 status of its directory information when bridges changed, and
5516 therefore would not realize that it was no longer able to build
5517 circuits. Fixes part of bug 29875.
5518 - Do not count previously configured working bridges towards our
5519 total of working bridges. Previously, when Tor's list of bridges
5520 changed, it would think that the old bridges were still usable,
5521 and delay fetching router descriptors for the new ones. Fixes part
5522 of bug 29875; bugfix on 0.3.0.1-alpha.
5524 o Major bugfixes (circuit build, guard):
5525 - On relays, properly check that a padding machine is absent before
5526 logging a warning about it being absent. Fixes bug 30649; bugfix
5528 - When considering upgrading circuits from "waiting for guard" to
5529 "open", always ignore circuits that are marked for close. Otherwise,
5530 we can end up in the situation where a subsystem is notified that
5531 a closing circuit has just opened, leading to undesirable
5532 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
5534 o Major bugfixes (onion service reachability):
5535 - Properly clean up the introduction point map when circuits change
5536 purpose from onion service circuits to pathbias, measurement, or
5537 other circuit types. This should fix some service-side instances
5538 of introduction point failure. Fixes bug 29034; bugfix
5541 o Major bugfixes (onion service v3):
5542 - Fix an unreachable bug in which an introduction point could try to
5543 send an INTRODUCE_ACK with a status code that Trunnel would refuse
5544 to encode, leading the relay to assert(). We've consolidated the
5545 ABI values into Trunnel now. Fixes bug 30454; bugfix
5547 - Clients can now handle unknown status codes from INTRODUCE_ACK
5548 cells. (The NACK behavior will stay the same.) This will allow us
5549 to extend status codes in the future without breaking the normal
5550 client behavior. Fixes another part of bug 30454; bugfix
5553 o Minor features (authenticated SENDME):
5554 - Ensure that there is enough randomness on every circuit to prevent
5555 an attacker from successfully predicting the hashes they will need
5556 to include in authenticated SENDME cells. At a random interval, if
5557 we have not sent randomness already, we now leave some extra space
5558 at the end of a cell that we can fill with random bytes. Closes
5561 o Minor features (circuit padding logging):
5562 - Demote noisy client-side warn logs about circuit padding to protocol
5563 warnings. Add additional log messages and circuit ID fields to help
5564 with bug 30992 and any other future issues.
5566 o Minor features (circuit padding):
5567 - We now use a fast PRNG when scheduling circuit padding. Part of
5569 - Allow the padding machine designer to pick the edges of their
5570 histogram instead of trying to compute them automatically using an
5571 exponential formula. Resolves some undefined behavior in the case
5572 of small histograms and allows greater flexibility on machine
5573 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
5574 - Allow circuit padding machines to hold a circuit open until they
5575 are done padding it. Closes ticket 28780.
5577 o Minor features (compile-time modules):
5578 - Add a "--list-modules" command to print a list of which compile-
5579 time modules are enabled. Closes ticket 30452.
5581 o Minor features (continuous integration):
5582 - Our Travis configuration now uses Chutney to run some network
5583 integration tests automatically. Closes ticket 29280.
5584 - When running coverage builds on Travis, we now set
5585 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
5587 - Remove sudo configuration lines from .travis.yml as they are no
5588 longer needed with current Travis build environment. Resolves
5590 - In Travis, show stem's tor log after failure. Closes ticket 30234.
5592 o Minor features (controller):
5593 - Add onion service version 3 support to the HSFETCH command.
5594 Previously, only version 2 onion services were supported. Closes
5595 ticket 25417. Patch by Neel Chauhan.
5597 o Minor features (debugging):
5598 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
5599 logging of additional information during assert failure. Now we
5600 can use format strings to include information for trouble
5601 shooting. Resolves ticket 29662.
5603 o Minor features (defense in depth):
5604 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
5605 case a bug causes them to be used later. Closes ticket 30176.
5606 Patch from Tobias Stoeckmann.
5607 - Tor now uses a cryptographically strong PRNG even for decisions
5608 that we do not believe are security-sensitive. Previously, for
5609 performance reasons, we had used a trivially predictable linear
5610 congruential generator algorithm for certain load-balancing and
5611 statistical sampling decisions. Now we use our fast RNG in those
5612 cases. Closes ticket 29542.
5614 o Minor features (developer tools):
5615 - Tor's "practracker" test script now checks for files and functions
5616 that seem too long and complicated. Existing overlong functions
5617 and files are accepted for now, but should eventually be
5618 refactored. Closes ticket 29221.
5619 - Add some scripts used for git maintenance to scripts/git. Closes
5621 - Call practracker from pre-push and pre-commit git hooks to let
5622 developers know if they made any code style violations. Closes
5624 - Add a script to check that each header has a well-formed and
5625 unique guard macro. Closes ticket 29756.
5627 o Minor features (fallback directory list):
5628 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
5629 in December 2018 (of which ~122 were still functional), with a
5630 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
5631 in June 2019. Closes ticket 28795.
5633 o Minor features (geoip):
5634 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
5635 Country database. Closes ticket 30852.
5636 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
5637 Country database. Closes ticket 30522.
5639 o Minor features (HTTP tunnel):
5640 - Return an informative web page when the HTTPTunnelPort is used as
5641 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
5643 o Minor features (IPv6, v3 onion services):
5644 - Make v3 onion services put IPv6 addresses in service descriptors.
5645 Before this change, service descriptors only contained IPv4
5646 addresses. Implements 26992.
5648 o Minor features (logging):
5649 - Give a more useful assertion failure message if we think we have
5650 minherit() but we fail to make a region non-inheritable. Give a
5651 compile-time warning if our support for minherit() is incomplete.
5652 Closes ticket 30686.
5654 o Minor features (maintenance):
5655 - Add a new "make autostyle" target that developers can use to apply
5656 all automatic Tor style and consistency conversions to the
5657 codebase. Closes ticket 30539.
5659 o Minor features (modularity):
5660 - The "--disable-module-dirauth" compile-time option now disables
5661 even more dirauth-only code. Closes ticket 30345.
5663 o Minor features (performance):
5664 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
5665 1.1.1 and later), since they tend to be faster than tiny-keccak.
5666 Closes ticket 28837.
5668 o Minor features (testing):
5669 - The circuitpadding tests now use a reproducible RNG implementation,
5670 so that if a test fails, we can learn why. Part of ticket 28878.
5671 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
5672 to set the RNG seed for tests that use a reproducible RNG. Part of
5674 - When running tests in coverage mode, take additional care to make
5675 our coverage deterministic, so that we can accurately track
5676 changes in code coverage. Closes ticket 30519.
5677 - Tor's unit test code now contains helper functions to replace the
5678 PRNG with a deterministic or reproducible version for testing.
5679 Previously, various tests implemented this in various ways.
5680 Implements ticket 29732.
5681 - We now have a script, cov-test-determinism.sh, to identify places
5682 where our unit test coverage has become nondeterministic. Closes
5684 - Check that representative subsets of values of `int` and `unsigned
5685 int` can be represented by `void *`. Resolves issue 29537.
5687 o Minor bugfixes (bridge authority):
5688 - Bridge authorities now set bridges as running or non-running when
5689 about to dump their status to a file. Previously, they set bridges
5690 as running in response to a GETINFO command, but those shouldn't
5691 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
5692 Patch by Neel Chauhan.
5694 o Minor bugfixes (channel padding statistics):
5695 - Channel padding write totals and padding-enabled totals are now
5696 counted properly in relay extrainfo descriptors. Fixes bug 29231;
5697 bugfix on 0.3.1.1-alpha.
5699 o Minor bugfixes (circuit isolation):
5700 - Fix a logic error that prevented the SessionGroup sub-option from
5701 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
5703 o Minor bugfixes (circuit padding):
5704 - Add a "CircuitPadding" torrc option to disable circuit padding.
5705 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
5706 - Allow circuit padding machines to specify that they do not
5707 contribute much overhead, and provide consensus flags and torrc
5708 options to force clients to only use these low overhead machines.
5709 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
5710 - Provide a consensus parameter to fully disable circuit padding, to
5711 be used in emergency network overload situations. Fixes bug 30173;
5712 bugfix on 0.4.0.1-alpha.
5713 - The circuit padding subsystem will no longer schedule padding if
5714 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
5715 - Inspect a circuit-level cell queue before sending padding, to
5716 avoid sending padding while too much data is already queued. Fixes
5717 bug 29204; bugfix on 0.4.0.1-alpha.
5718 - Avoid calling monotime_absolute_usec() in circuit padding machines
5719 that do not use token removal or circuit RTT estimation. Fixes bug
5720 29085; bugfix on 0.4.0.1-alpha.
5722 o Minor bugfixes (clock skew detection):
5723 - Don't believe clock skew results from NETINFO cells that appear to
5724 arrive before we sent the VERSIONS cells they are responding to.
5725 Previously, we would accept them up to 3 minutes "in the past".
5726 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
5728 o Minor bugfixes (compatibility, standards compliance):
5729 - Fix a bug that would invoke undefined behavior on certain
5730 operating systems when trying to asprintf() a string exactly
5731 INT_MAX bytes long. We don't believe this is exploitable, but it's
5732 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
5733 Found and fixed by Tobias Stoeckmann.
5735 o Minor bugfixes (compilation warning):
5736 - Fix a compilation warning on Windows about casting a function
5737 pointer for GetTickCount64(). Fixes bug 31374; bugfix on
5740 o Minor bugfixes (compilation):
5741 - Avoid using labs() on time_t, which can cause compilation warnings
5742 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
5744 o Minor bugfixes (compilation, unusual configurations):
5745 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
5746 due to missing declarations of abort(), and prevent other such
5747 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
5749 o Minor bugfixes (configuration, proxies):
5750 - Fix a bug that prevented us from supporting SOCKS5 proxies that
5751 want authentication along with configured (but unused!)
5752 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
5754 o Minor bugfixes (continuous integration):
5755 - Allow the test-stem job to fail in Travis, because it sometimes
5756 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
5757 - Skip test_rebind on macOS in Travis, because it is unreliable on
5758 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
5759 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
5760 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
5762 o Minor bugfixes (controller protocol):
5763 - Teach the controller parser to distinguish an object preceded by
5764 an argument list from one without. Previously, it couldn't
5765 distinguish an argument list from the first line of a multiline
5766 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
5768 o Minor bugfixes (crash on exit):
5769 - Avoid a set of possible code paths that could try to use freed
5770 memory in routerlist_free() while Tor was exiting. Fixes bug
5771 31003; bugfix on 0.1.2.2-alpha.
5773 o Minor bugfixes (developer tooling):
5774 - Fix pre-push hook to allow fixup and squash commits when pushing
5775 to non-upstream git remote. Fixes bug 30286; bugfix
5778 o Minor bugfixes (directory authorities):
5779 - Stop crashing after parsing an unknown descriptor purpose
5780 annotation. We think this bug can only be triggered by modifying a
5781 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
5782 - Move the "bandwidth-file-headers" line in directory authority
5783 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
5785 - Directory authorities with IPv6 support now always mark themselves
5786 as reachable via IPv6. Fixes bug 24338; bugfix on 0.2.4.1-alpha.
5787 Patch by Neel Chauhan.
5789 o Minor bugfixes (documentation):
5790 - Improve the documentation for using MapAddress with ".exit". Fixes
5791 bug 30109; bugfix on 0.1.0.1-rc.
5792 - Improve the monotonic time module and function documentation to
5793 explain what "monotonic" actually means, and document some results
5794 that have surprised people. Fixes bug 29640; bugfix
5796 - Use proper formatting when providing an example on quoting options
5797 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
5799 o Minor bugfixes (logging):
5800 - Do not log a warning when running with an OpenSSL version other
5801 than the one Tor was compiled with, if the two versions should be
5802 compatible. Previously, we would warn whenever the version was
5803 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
5804 - Warn operators when the MyFamily option is set but ContactInfo is
5805 missing, as the latter should be set too. Fixes bug 25110; bugfix
5808 o Minor bugfixes (memory leaks):
5809 - Avoid a minor memory leak that could occur on relays when failing
5810 to create a "keys" directory. Fixes bug 30148; bugfix
5812 - Fix a trivial memory leak when parsing an invalid value from a
5813 download schedule in the configuration. Fixes bug 30894; bugfix
5816 o Minor bugfixes (NetBSD):
5817 - Fix usage of minherit() on NetBSD and other platforms that define
5818 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
5819 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
5821 o Minor bugfixes (onion services):
5822 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
5823 implemenation) when failing to load an onion service client
5824 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
5825 - When refusing to launch a controller's HSFETCH request because of
5826 rate-limiting, respond to the controller with a new response,
5827 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
5828 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
5830 - When relaunching a circuit to a rendezvous service, mark the
5831 circuit as needing high-uptime routers as appropriate. Fixes bug
5832 17357; bugfix on 0.1.0.1-rc. Patch by Neel Chauhan.
5833 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
5834 (IPv6 support for v3 onion services is still incomplete: see
5835 ticket 23493 for details.) Fixes bug 23588; bugfix on
5836 0.3.2.1-alpha. Patch by Neel Chauhan.
5838 o Minor bugfixes (onion services, performance):
5839 - When building circuits to onion services, call tor_addr_parse()
5840 less often. Previously, we called tor_addr_parse() in
5841 circuit_is_acceptable() even if its output wasn't used. This
5842 change should improve performance when building circuits. Fixes
5843 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
5845 o Minor bugfixes (out-of-memory handler):
5846 - When purging the DNS cache because of an out-of-memory condition,
5847 try purging just the older entries at first. Previously, we would
5848 always purge the whole thing. Fixes bug 29617; bugfix
5851 o Minor bugfixes (performance):
5852 - When checking whether a node is a bridge, use a fast check to make
5853 sure that its identity is set. Previously, we used a constant-time
5854 check, which is not necessary in this case. Fixes bug 30308;
5855 bugfix on 0.3.5.1-alpha.
5857 o Minor bugfixes (pluggable transports):
5858 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
5859 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
5861 o Minor bugfixes (portability):
5862 - Avoid crashing in our tor_vasprintf() implementation on systems
5863 that define neither vasprintf() nor _vscprintf(). (This bug has
5864 been here long enough that we question whether people are running
5865 Tor on such systems, but we're applying the fix out of caution.)
5866 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
5869 o Minor bugfixes (probability distributions):
5870 - Refactor and improve parts of the probability distribution code
5871 that made Coverity complain. Fixes bug 29805; bugfix
5874 o Minor bugfixes (python):
5875 - Stop assuming that /usr/bin/python3 exists. For scripts that work
5876 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
5877 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
5879 o Minor bugfixes (relay):
5880 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
5881 is auto, act as if ExitRelay is 1. Previously, we would ignore
5882 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
5883 0.3.5.1-alpha. Patch by Neel Chauhan.
5885 o Minor bugfixes (static analysis):
5886 - Fix several spurious Coverity warnings about the unit tests, to
5887 lower our chances of missing real warnings in the future. Fixes
5888 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
5890 o Minor bugfixes (stats):
5891 - When ExtraInfoStatistics is 0, stop including bandwidth usage
5892 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
5893 bridge statistics by country in extra-info documents. Fixes bug
5894 29018; bugfix on 0.2.4.1-alpha.
5896 o Minor bugfixes (testing):
5897 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
5898 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
5899 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
5900 - Fix some incorrect code in the v3 onion service unit tests. Fixes
5901 bug 29243; bugfix on 0.3.2.1-alpha.
5902 - In the "routerkeys/*" tests, check the return values of mkdir()
5903 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
5904 Found by Coverity as CID 1444254.
5905 - Split test_utils_general() into several smaller test functions.
5906 This makes it easier to perform resource deallocation on assert
5907 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
5908 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
5910 o Minor bugfixes (tor-resolve):
5911 - Fix a memory leak in tor-resolve that could happen if Tor gave it
5912 a malformed SOCKS response. (Memory leaks in tor-resolve don't
5913 actually matter, but it's good to fix them anyway.) Fixes bug
5914 30151; bugfix on 0.4.0.1-alpha.
5916 o Code simplification and refactoring:
5917 - Abstract out the low-level formatting of replies on the control
5918 port. Implements ticket 30007.
5919 - Add several assertions in an attempt to fix some Coverity
5920 warnings. Closes ticket 30149.
5921 - Introduce a connection_dir_buf_add() helper function that checks
5922 for compress_state of dir_connection_t and automatically writes a
5923 string to directory connection with or without compression.
5924 Resolves issue 28816.
5925 - Make the base32_decode() API return the number of bytes written,
5926 for consistency with base64_decode(). Closes ticket 28913.
5927 - Move most relay-only periodic events out of mainloop.c into the
5928 relay subsystem. Closes ticket 30414.
5929 - Refactor and encapsulate parts of the codebase that manipulate
5930 crypt_path_t objects. Resolves issue 30236.
5931 - Refactor several places in our code that Coverity incorrectly
5932 believed might have memory leaks. Closes ticket 30147.
5933 - Remove redundant return values in crypto_format, and the
5934 associated return value checks elsewhere in the code. Make the
5935 implementations in crypto_format consistent, and remove redundant
5936 code. Resolves ticket 29660.
5937 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
5938 it is not a constant-time function. Closes ticket 30309.
5939 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
5940 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
5941 bugfix on 0.3.2.1-alpha.
5942 - Simplify v3 onion service link specifier handling code. Fixes bug
5943 23576; bugfix on 0.3.2.1-alpha.
5944 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
5945 code. Resolves ticket 29108.
5946 - Split control.c into several submodules, in preparation for
5947 distributing its current responsibilities throughout the codebase.
5948 Closes ticket 29894.
5949 - Start to move responsibility for knowing about periodic events to
5950 the appropriate subsystems, so that the mainloop doesn't need to
5951 know all the periodic events in the rest of the codebase.
5952 Implements tickets 30293 and 30294.
5955 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
5956 Closes ticket 30630.
5957 - Document how to find git commits and tags for bug fixes in
5958 CodingStandards.md. Update some file documentation. Closes
5962 - Remove the linux-tor-prio.sh script from contrib/operator-tools
5963 directory. Resolves issue 29434.
5964 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
5965 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
5969 - Specify torrc paths (with empty files) when launching tor in
5970 integration tests; refrain from reading user and system torrcs.
5971 Resolves issue 29702.
5973 o Code simplification and refactoring (shell scripts):
5974 - Clean up many of our shell scripts to fix shellcheck warnings.
5975 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
5976 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
5977 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
5978 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
5979 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
5980 nagios-check-tor-authority-cert (ticket 29071),
5981 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
5982 (ticket 29060), test_key_expiration.sh (ticket 30002),
5983 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
5986 o Testing (chutney):
5987 - In "make test-network-all", test IPv6-only v3 single onion
5988 services, using the chutney network single-onion-v23-ipv6-md.
5989 Closes ticket 27251.
5991 o Testing (continuous integration):
5992 - In Travis, make stem log a controller trace to the console, and tail
5993 stem's tor log after failure. Closes ticket 30591.
5994 - In Travis, only run the stem tests that use a tor binary.
5995 Closes ticket 30694.
5998 Changes in version 0.4.0.5 - 2019-05-02
5999 This is the first stable release in the 0.4.0.x series. It contains
6000 improvements for power management and bootstrap reporting, as well as
6001 preliminary backend support for circuit padding to prevent some kinds
6002 of traffic analysis. It also continues our work in refactoring Tor for
6003 long-term maintainability.
6005 Per our support policy, we will support the 0.4.0.x series for nine
6006 months, or until three months after the release of a stable 0.4.1.x:
6007 whichever is longer. If you need longer-term support, please stick
6008 with 0.3.5.x, which will we plan to support until Feb 2022.
6010 Below are the changes since 0.3.5.7. For a complete list of changes
6011 since 0.4.0.4-rc, see the ChangeLog file.
6013 o Major features (battery management, client, dormant mode):
6014 - When Tor is running as a client, and it is unused for a long time,
6015 it can now enter a "dormant" state. When Tor is dormant, it avoids
6016 network and CPU activity until it is reawoken either by a user
6017 request or by a controller command. For more information, see the
6018 configuration options starting with "Dormant". Implements tickets
6020 - The client's memory of whether it is "dormant", and how long it
6021 has spent idle, persists across invocations. Implements
6023 - There is a DormantOnFirstStartup option that integrators can use
6024 if they expect that in many cases, Tor will be installed but
6027 o Major features (bootstrap reporting):
6028 - When reporting bootstrap progress, report the first connection
6029 uniformly, regardless of whether it's a connection for building
6030 application circuits. This allows finer-grained reporting of early
6031 progress than previously possible, with the improvements of ticket
6032 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
6033 - When reporting bootstrap progress, treat connecting to a proxy or
6034 pluggable transport as separate from having successfully used that
6035 proxy or pluggable transport to connect to a relay. Closes tickets
6038 o Major features (circuit padding):
6039 - Implement preliminary support for the circuit padding portion of
6040 Proposal 254. The implementation supports Adaptive Padding (aka
6041 WTF-PAD) state machines for use between experimental clients and
6042 relays. Support is also provided for APE-style state machines that
6043 use probability distributions instead of histograms to specify
6044 inter-packet delay. At the moment, Tor does not provide any
6045 padding state machines that are used in normal operation: for now,
6046 this feature exists solely for experimentation. Closes
6049 o Major features (refactoring):
6050 - Tor now uses an explicit list of its own subsystems when
6051 initializing and shutting down. Previously, these systems were
6052 managed implicitly in various places throughout the codebase.
6053 (There may still be some subsystems using the old system.) Closes
6056 o Major bugfixes (cell scheduler, KIST, security):
6057 - Make KIST consider the outbuf length when computing what it can
6058 put in the outbuf. Previously, KIST acted as though the outbuf
6059 were empty, which could lead to the outbuf becoming too full. It
6060 is possible that an attacker could exploit this bug to cause a Tor
6061 client or relay to run out of memory and crash. Fixes bug 29168;
6062 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
6063 TROVE-2019-001 and CVE-2019-8955.
6065 o Major bugfixes (networking):
6066 - Gracefully handle empty username/password fields in SOCKS5
6067 username/password auth message and allow SOCKS5 handshake to
6068 continue. Previously, we had rejected these handshakes, breaking
6069 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
6071 o Major bugfixes (NSS, relay):
6072 - When running with NSS, disable TLS 1.2 ciphersuites that use
6073 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
6074 these ciphersuites don't work -- which caused relays to fail to
6075 handshake with one another when these ciphersuites were enabled.
6076 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
6078 o Major bugfixes (windows, startup):
6079 - When reading a consensus file from disk, detect whether it was
6080 written in text mode, and re-read it in text mode if so. Always
6081 write consensus files in binary mode so that we can map them into
6082 memory later. Previously, we had written in text mode, which
6083 confused us when we tried to map the file on windows. Fixes bug
6084 28614; bugfix on 0.4.0.1-alpha.
6086 o Minor features (address selection):
6087 - Treat the subnet 100.64.0.0/10 as public for some purposes;
6088 private for others. This subnet is the RFC 6598 (Carrier Grade
6089 NAT) IP range, and is deployed by many ISPs as an alternative to
6090 RFC 1918 that does not break existing internal networks. Tor now
6091 blocks SOCKS and control ports on these addresses and warns users
6092 if client ports or ExtORPorts are listening on a RFC 6598 address.
6093 Closes ticket 28525. Patch by Neel Chauhan.
6095 o Minor features (bandwidth authority):
6096 - Make bandwidth authorities ignore relays that are reported in the
6097 bandwidth file with the flag "vote=0". This change allows us to
6098 report unmeasured relays for diagnostic reasons without including
6099 their bandwidth in the bandwidth authorities' vote. Closes
6101 - When a directory authority is using a bandwidth file to obtain the
6102 bandwidth values that will be included in the next vote, serve
6103 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
6106 o Minor features (bootstrap reporting):
6107 - When reporting bootstrap progress, stop distinguishing between
6108 situations where only internal paths are available and situations
6109 where external paths are available. Previously, Tor would often
6110 erroneously report that it had only internal paths. Closes
6113 o Minor features (compilation):
6114 - Compile correctly when OpenSSL is built with engine support
6115 disabled, or with deprecated APIs disabled. Closes ticket 29026.
6116 Patches from "Mangix".
6118 o Minor features (continuous integration):
6119 - On Travis Rust builds, cleanup Rust registry and refrain from
6120 caching the "target/" directory to speed up builds. Resolves
6122 - Log Python version during each Travis CI job. Resolves
6124 - In Travis, tell timelimit to use stem's backtrace signals, and
6125 launch python directly from timelimit, so python receives the
6126 signals from timelimit, rather than make. Closes ticket 30117.
6128 o Minor features (controller):
6129 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
6130 Implements ticket 28843.
6132 o Minor features (developer tooling):
6133 - Check that bugfix versions in changes files look like Tor versions
6134 from the versions spec. Warn when bugfixes claim to be on a future
6135 release. Closes ticket 27761.
6136 - Provide a git pre-commit hook that disallows committing if we have
6137 any failures in our code and changelog formatting checks. It is
6138 now available in scripts/maint/pre-commit.git-hook. Implements
6140 - Provide a git hook script to prevent "fixup!" and "squash!"
6141 commits from ending up in the master branch, as scripts/main/pre-
6142 push.git-hook. Closes ticket 27993.
6144 o Minor features (diagnostic):
6145 - Add more diagnostic log messages in an attempt to solve the issue
6146 of NUL bytes appearing in a microdescriptor cache. Related to
6149 o Minor features (directory authority):
6150 - When a directory authority is using a bandwidth file to obtain
6151 bandwidth values, include the digest of that file in the vote.
6152 Closes ticket 26698.
6153 - Directory authorities support a new consensus algorithm, under
6154 which the family lines in microdescriptors are encoded in a
6155 canonical form. This change makes family lines more compressible
6156 in transit, and on the client. Closes ticket 28266; implements
6159 o Minor features (directory authority, relay):
6160 - Authorities now vote on a "StaleDesc" flag to indicate that a
6161 relay's descriptor is so old that the relay should upload again
6162 soon. Relays treat this flag as a signal to upload a new
6163 descriptor. This flag will eventually let us remove the
6164 'published' date from routerstatus entries, and make our consensus
6165 diffs much smaller. Closes ticket 26770; implements proposal 293.
6167 o Minor features (dormant mode):
6168 - Add a DormantCanceledByStartup option to tell Tor that it should
6169 treat a startup event as cancelling any previous dormant state.
6170 Integrators should use this option with caution: it should only be
6171 used if Tor is being started because of something that the user
6172 did, and not if Tor is being automatically started in the
6173 background. Closes ticket 29357.
6175 o Minor features (fallback directory mirrors):
6176 - Update the fallback whitelist based on operator opt-ins and opt-
6177 outs. Closes ticket 24805, patch by Phoul.
6179 o Minor features (FreeBSD):
6180 - On FreeBSD-based systems, warn relay operators if the
6181 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
6182 Closes ticket 28518.
6184 o Minor features (geoip):
6185 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
6186 Country database. Closes ticket 29992.
6188 o Minor features (HTTP standards compliance):
6189 - Stop sending the header "Content-type: application/octet-stream"
6190 along with transparently compressed documents: this confused
6191 browsers. Closes ticket 28100.
6193 o Minor features (IPv6):
6194 - We add an option ClientAutoIPv6ORPort, to make clients randomly
6195 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
6196 every time a node is loaded from a new consensus or bridge config.
6197 We expect that this option will enable clients to bootstrap more
6198 quickly without having to determine whether they support IPv4,
6199 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
6200 - When using addrs_in_same_network_family(), avoid choosing circuit
6201 paths that pass through the same IPv6 subnet more than once.
6202 Previously, we only checked IPv4 subnets. Closes ticket 24393.
6203 Patch by Neel Chauhan.
6205 o Minor features (log messages):
6206 - Improve log message in v3 onion services that could print out
6207 negative revision counters. Closes ticket 27707. Patch
6210 o Minor features (memory usage):
6211 - Save memory by storing microdescriptor family lists with a more
6212 compact representation. Closes ticket 27359.
6213 - Tor clients now use mmap() to read consensus files from disk, so
6214 that they no longer need keep the full text of a consensus in
6215 memory when parsing it or applying a diff. Closes ticket 27244.
6217 o Minor features (NSS, diagnostic):
6218 - Try to log an error from NSS (if there is any) and a more useful
6219 description of our situation if we are using NSS and a call to
6220 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
6222 o Minor features (parsing):
6223 - Directory authorities now validate that router descriptors and
6224 ExtraInfo documents are in a valid subset of UTF-8, and reject
6225 them if they are not. Closes ticket 27367.
6227 o Minor features (performance):
6228 - Cache the results of summarize_protocol_flags(), so that we don't
6229 have to parse the same protocol-versions string over and over.
6230 This should save us a huge number of malloc calls on startup, and
6231 may reduce memory fragmentation with some allocators. Closes
6233 - Remove a needless memset() call from get_token_arguments, thereby
6234 speeding up the tokenization of directory objects by about 20%.
6235 Closes ticket 28852.
6236 - Replace parse_short_policy() with a faster implementation, to
6237 improve microdescriptor parsing time. Closes ticket 28853.
6238 - Speed up directory parsing a little by avoiding use of the non-
6239 inlined strcmp_len() function. Closes ticket 28856.
6240 - Speed up microdescriptor parsing by about 30%, to help improve
6241 startup time. Closes ticket 28839.
6243 o Minor features (pluggable transports):
6244 - Add support for emitting STATUS updates to Tor's control port from
6245 a pluggable transport process. Closes ticket 28846.
6246 - Add support for logging to Tor's logging subsystem from a
6247 pluggable transport process. Closes ticket 28180.
6249 o Minor features (process management):
6250 - Add a new process API for handling child processes. This new API
6251 allows Tor to have bi-directional communication with child
6252 processes on both Unix and Windows. Closes ticket 28179.
6253 - Use the subsystem manager to initialize and shut down the process
6254 module. Closes ticket 28847.
6256 o Minor features (relay):
6257 - When listing relay families, list them in canonical form including
6258 the relay's own identity, and try to give a more useful set of
6259 warnings. Part of ticket 28266 and proposal 298.
6261 o Minor features (required protocols):
6262 - Before exiting because of a missing required protocol, Tor will
6263 now check the publication time of the consensus, and not exit
6264 unless the consensus is newer than the Tor program's own release
6265 date. Previously, Tor would not check the consensus publication
6266 time, and so might exit because of a missing protocol that might
6267 no longer be required in a current consensus. Implements proposal
6268 297; closes ticket 27735.
6270 o Minor features (testing):
6271 - Treat all unexpected ERR and BUG messages as test failures. Closes
6273 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
6274 networks. Closes ticket 28840. Patch by Rob Jansen.
6275 - Use the approx_time() function when setting the "Expires" header
6276 in directory replies, to make them more testable. Needed for
6279 o Minor bugfixes (security):
6280 - Fix a potential double free bug when reading huge bandwidth files.
6281 The issue is not exploitable in the current Tor network because
6282 the vulnerable code is only reached when directory authorities
6283 read bandwidth files, but bandwidth files come from a trusted
6284 source (usually the authorities themselves). Furthermore, the
6285 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
6286 which are not used by any of the current authorities. Fixes bug
6287 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
6289 - Verify in more places that we are not about to create a buffer
6290 with more than INT_MAX bytes, to avoid possible OOB access in the
6291 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
6292 fixed by Tobias Stoeckmann.
6294 o Minor bugfix (continuous integration):
6295 - Reset coverage state on disk after Travis CI has finished. This
6296 should prevent future coverage merge errors from causing the test
6297 suite for the "process" subsystem to fail. The process subsystem
6298 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
6300 - Terminate test-stem if it takes more than 9.5 minutes to run.
6301 (Travis terminates the job after 10 minutes of no output.)
6302 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
6304 o Minor bugfixes (build, compatibility, rust):
6305 - Update Cargo.lock file to match the version made by the latest
6306 version of Rust, so that "make distcheck" will pass again. Fixes
6307 bug 29244; bugfix on 0.3.3.4-alpha.
6309 o Minor bugfixes (C correctness):
6310 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
6311 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
6314 o Minor bugfixes (client, clock skew):
6315 - Bootstrap successfully even when Tor's clock is behind the clocks
6316 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
6317 - Select guards even if the consensus has expired, as long as the
6318 consensus is still reasonably live. Fixes bug 24661; bugfix
6321 o Minor bugfixes (compilation):
6322 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
6323 29169; bugfix on 0.4.0.1-alpha.
6324 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
6325 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
6326 - Compile correctly on OpenBSD; previously, we were missing some
6327 headers required in order to detect it properly. Fixes bug 28938;
6328 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
6330 o Minor bugfixes (directory clients):
6331 - Mark outdated dirservers when Tor only has a reasonably live
6332 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
6334 o Minor bugfixes (directory mirrors):
6335 - Even when a directory mirror's clock is behind the clocks on the
6336 authorities, we now allow the mirror to serve "future"
6337 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
6339 o Minor bugfixes (DNS):
6340 - Gracefully handle an empty or absent resolve.conf file by falling
6341 back to using "localhost" as a DNS server (and hoping it works).
6342 Previously, we would just stop running as an exit. Fixes bug
6343 21900; bugfix on 0.2.1.10-alpha.
6345 o Minor bugfixes (documentation):
6346 - Describe the contents of the v3 onion service client authorization
6347 files correctly: They hold public keys, not private keys. Fixes
6348 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
6350 o Minor bugfixes (guards):
6351 - In count_acceptable_nodes(), the minimum number is now one bridge
6352 or guard node, and two non-guard nodes for a circuit. Previously,
6353 we had added up the sum of all nodes with a descriptor, but that
6354 could cause us to build failing circuits when we had either too
6355 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
6356 0.2.3.1-alpha. Patch by Neel Chauhan.
6358 o Minor bugfixes (IPv6):
6359 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
6360 IPv6 socket was bound using an address family of AF_INET instead
6361 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
6364 o Minor bugfixes (linux seccomp sandbox):
6365 - Fix startup crash when experimental sandbox support is enabled.
6366 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
6368 o Minor bugfixes (logging):
6369 - Correct a misleading error message when IPv4Only or IPv6Only is
6370 used but the resolved address can not be interpreted as an address
6371 of the specified IP version. Fixes bug 13221; bugfix on
6372 0.2.3.9-alpha. Patch from Kris Katterjohn.
6373 - Log the correct port number for listening sockets when "auto" is
6374 used to let Tor pick the port number. Previously, port 0 was
6375 logged instead of the actual port number. Fixes bug 29144; bugfix
6376 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
6377 - Stop logging a BUG() warning when Tor is waiting for exit
6378 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
6379 - Avoid logging that we are relaxing a circuit timeout when that
6380 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
6381 - Log more information at "warning" level when unable to read a
6382 private key; log more information at "info" level when unable to
6383 read a public key. We had warnings here before, but they were lost
6384 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
6385 - Rework rep_hist_log_link_protocol_counts() to iterate through all
6386 link protocol versions when logging incoming/outgoing connection
6387 counts. Tor no longer skips version 5, and we won't have to
6388 remember to update this function when new link protocol version is
6389 developed. Fixes bug 28920; bugfix on 0.2.6.10.
6391 o Minor bugfixes (memory management):
6392 - Refactor the shared random state's memory management so that it
6393 actually takes ownership of the shared random value pointers.
6394 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
6395 - Stop leaking parts of the shared random state in the shared-random
6396 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
6398 o Minor bugfixes (misc):
6399 - The amount of total available physical memory is now determined
6400 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
6401 when it is defined and a 64-bit variant is not available. Fixes
6402 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
6404 o Minor bugfixes (networking):
6405 - Introduce additional checks into tor_addr_parse() to reject
6406 certain incorrect inputs that previously were not detected. Fixes
6407 bug 23082; bugfix on 0.2.0.10-alpha.
6409 o Minor bugfixes (onion service v3, client):
6410 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
6411 connection waiting for a descriptor that we actually have in the
6412 cache. It turns out that this can actually happen, though it is
6413 rare. Now, tor will recover and retry the descriptor. Fixes bug
6414 28669; bugfix on 0.3.2.4-alpha.
6416 o Minor bugfixes (onion services):
6417 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
6418 than one private key for a hidden service. Fixes bug 29040; bugfix
6420 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
6421 "debug" level. Tor used to log it as a warning, which caused very
6422 long log lines to appear for some users. Fixes bug 29135; bugfix
6424 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
6425 as a warning. Instead, log it as a protocol warning, because there
6426 is nothing that relay operators can do to fix it. Fixes bug 29029;
6427 bugfix on 0.2.5.7-rc.
6429 o Minor bugfixes (periodic events):
6430 - Refrain from calling routerlist_remove_old_routers() from
6431 check_descriptor_callback(). Instead, create a new hourly periodic
6432 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
6434 o Minor bugfixes (pluggable transports):
6435 - Make sure that data is continously read from standard output and
6436 standard error pipes of a pluggable transport child-process, to
6437 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
6438 bugfix on 0.2.3.6-alpha.
6440 o Minor bugfixes (rust):
6441 - Abort on panic in all build profiles, instead of potentially
6442 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
6444 o Minor bugfixes (scheduler):
6445 - When re-adding channels to the pending list, check the correct
6446 channel's sched_heap_idx. This issue has had no effect in mainline
6447 Tor, but could have led to bugs down the road in improved versions
6448 of our circuit scheduling code. Fixes bug 29508; bugfix
6451 o Minor bugfixes (shellcheck):
6452 - Look for scripts in their correct locations during "make
6453 shellcheck". Previously we had looked in the wrong place during
6454 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
6456 o Minor bugfixes (single onion services):
6457 - Allow connections to single onion services to remain idle without
6458 being disconnected. Previously, relays acting as rendezvous points
6459 for single onion services were mistakenly closing idle rendezvous
6460 circuits after 60 seconds, thinking that they were unused
6461 directory-fetching circuits that had served their purpose. Fixes
6462 bug 29665; bugfix on 0.2.1.26.
6464 o Minor bugfixes (stats):
6465 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
6466 relay and bridge extra-info documents. Fixes bug 29017; bugfix
6469 o Minor bugfixes (testing):
6470 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
6471 recent test-network.sh to use new chutney features in CI. Fixes
6472 bug 29703; bugfix on 0.2.9.1-alpha.
6473 - Fix a test failure on Windows caused by an unexpected "BUG"
6474 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
6476 - Downgrade some LOG_ERR messages in the address/* tests to
6477 warnings. The LOG_ERR messages were occurring when we had no
6478 configured network. We were failing the unit tests, because we
6479 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
6480 29530; bugfix on 0.3.5.8.
6481 - Fix our gcov wrapper script to look for object files at the
6482 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
6483 - Decrease the false positive rate of stochastic probability
6484 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
6485 - Fix intermittent failures on an adaptive padding test. Fixes one
6486 case of bug 29122; bugfix on 0.4.0.1-alpha.
6487 - Disable an unstable circuit-padding test that was failing
6488 intermittently because of an ill-defined small histogram. Such
6489 histograms will be allowed again after 29298 is implemented. Fixes
6490 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
6491 - Detect and suppress "bug" warnings from the util/time test on
6492 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
6493 - Do not log an error-level message if we fail to find an IPv6
6494 network interface from the unit tests. Fixes bug 29160; bugfix
6496 - Instead of relying on hs_free_all() to clean up all onion service
6497 objects in test_build_descriptors(), we now deallocate them one by
6498 one. This lets Coverity know that we are not leaking memory there
6499 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
6500 - Check the time in the "Expires" header using approx_time(). Fixes
6501 bug 30001; bugfix on 0.4.0.4-rc.
6503 o Minor bugfixes (TLS protocol):
6504 - When classifying a client's selection of TLS ciphers, if the
6505 client ciphers are not yet available, do not cache the result.
6506 Previously, we had cached the unavailability of the cipher list
6507 and never looked again, which in turn led us to assume that the
6508 client only supported the ancient V1 link protocol. This, in turn,
6509 was causing Stem integration tests to stall in some cases. Fixes
6510 bug 30021; bugfix on 0.2.4.8-alpha.
6512 o Minor bugfixes (UI):
6513 - Lower log level of unlink() errors during bootstrap. Fixes bug
6514 29930; bugfix on 0.4.0.1-alpha.
6516 o Minor bugfixes (usability):
6517 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
6518 Some users took this phrasing to mean that the mentioned guard was
6519 under their control or responsibility, which it is not. Fixes bug
6520 28895; bugfix on Tor 0.3.0.1-alpha.
6522 o Minor bugfixes (Windows, CI):
6523 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
6524 Windows Server 2012 R2 job. The remaining 2 jobs still provide
6525 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
6526 fast_finish, so failed jobs terminate the build immediately. Fixes
6527 bug 29601; bugfix on 0.3.5.4-alpha.
6529 o Code simplification and refactoring:
6530 - Introduce a connection_dir_buf_add() helper function that detects
6531 whether compression is in use, and adds a string accordingly.
6532 Resolves issue 28816.
6533 - Refactor handle_get_next_bandwidth() to use
6534 connection_dir_buf_add(). Implements ticket 29897.
6535 - Reimplement NETINFO cell parsing and generation to rely on
6536 trunnel-generated wire format handling code. Closes ticket 27325.
6537 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
6539 - Rework SOCKS wire format handling to rely on trunnel-generated
6540 parsing/generation code. Resolves ticket 27620.
6541 - Split out bootstrap progress reporting from control.c into a
6542 separate file. Part of ticket 27402.
6543 - The .may_include files that we use to describe our directory-by-
6544 directory dependency structure now describe a noncircular
6545 dependency graph over the directories that they cover. Our
6546 checkIncludes.py tool now enforces this noncircularity. Closes
6550 - Clarify that Tor performs stream isolation among *Port listeners
6551 by default. Resolves issue 29121.
6552 - In the manpage entry describing MapAddress torrc setting, use
6553 example IP addresses from ranges specified for use in documentation
6554 by RFC 5737. Resolves issue 28623.
6555 - Mention that you cannot add a new onion service if Tor is already
6556 running with Sandbox enabled. Closes ticket 28560.
6557 - Improve ControlPort documentation. Mention that it accepts
6558 address:port pairs, and can be used multiple times. Closes
6560 - Document the exact output of "tor --version". Closes ticket 28889.
6563 - Remove the old check-tor script. Resolves issue 29072.
6564 - Stop responding to the 'GETINFO status/version/num-concurring' and
6565 'GETINFO status/version/num-versioning' control port commands, as
6566 those were deprecated back in 0.2.0.30. Also stop listing them in
6567 output of 'GETINFO info/names'. Resolves ticket 28757.
6568 - The scripts used to generate and maintain the list of fallback
6569 directories have been extracted into a new "fallback-scripts"
6570 repository. Closes ticket 27914.
6573 - Run shellcheck for scripts in the in scripts/ directory. Closes
6575 - Add unit tests for tokenize_string() and get_next_token()
6576 functions. Resolves ticket 27625.
6578 o Code simplification and refactoring (onion service v3):
6579 - Consolidate the authorized client descriptor cookie computation
6580 code from client and service into one function. Closes
6583 o Code simplification and refactoring (shell scripts):
6584 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
6586 - Fix issues that shellcheck found in chutney-git-bisect.sh.
6587 Resolves ticket 28006.
6588 - Fix issues that shellcheck found in updateRustDependencies.sh.
6589 Resolves ticket 28012.
6590 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
6591 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
6592 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
6593 - Fix shellcheck warnings in scripts/test/coverage. Resolves
6597 Changes in version 0.3.5.8 - 2019-02-21
6598 Tor 0.3.5.8 backports several fixes from later releases, including fixes
6599 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
6602 It also includes a fix for a medium-severity security bug affecting Tor
6603 0.3.2.1-alpha and later. All Tor instances running an affected release
6604 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
6606 o Major bugfixes (cell scheduler, KIST, security):
6607 - Make KIST consider the outbuf length when computing what it can
6608 put in the outbuf. Previously, KIST acted as though the outbuf
6609 were empty, which could lead to the outbuf becoming too full. It
6610 is possible that an attacker could exploit this bug to cause a Tor
6611 client or relay to run out of memory and crash. Fixes bug 29168;
6612 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
6613 TROVE-2019-001 and CVE-2019-8955.
6615 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
6616 - Gracefully handle empty username/password fields in SOCKS5
6617 username/password auth messsage and allow SOCKS5 handshake to
6618 continue. Previously, we had rejected these handshakes, breaking
6619 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
6621 o Minor features (compilation, backport from 0.4.0.2-alpha):
6622 - Compile correctly when OpenSSL is built with engine support
6623 disabled, or with deprecated APIs disabled. Closes ticket 29026.
6624 Patches from "Mangix".
6626 o Minor features (geoip):
6627 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
6628 Country database. Closes ticket 29478.
6630 o Minor features (testing, backport from 0.4.0.2-alpha):
6631 - Treat all unexpected ERR and BUG messages as test failures. Closes
6634 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
6635 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
6636 connection waiting for a descriptor that we actually have in the
6637 cache. It turns out that this can actually happen, though it is
6638 rare. Now, tor will recover and retry the descriptor. Fixes bug
6639 28669; bugfix on 0.3.2.4-alpha.
6641 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
6642 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
6643 IPv6 socket was bound using an address family of AF_INET instead
6644 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
6647 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
6648 - Update Cargo.lock file to match the version made by the latest
6649 version of Rust, so that "make distcheck" will pass again. Fixes
6650 bug 29244; bugfix on 0.3.3.4-alpha.
6652 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
6653 - Select guards even if the consensus has expired, as long as the
6654 consensus is still reasonably live. Fixes bug 24661; bugfix
6657 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
6658 - Compile correctly on OpenBSD; previously, we were missing some
6659 headers required in order to detect it properly. Fixes bug 28938;
6660 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
6662 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
6663 - Describe the contents of the v3 onion service client authorization
6664 files correctly: They hold public keys, not private keys. Fixes
6665 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
6667 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
6668 - Rework rep_hist_log_link_protocol_counts() to iterate through all
6669 link protocol versions when logging incoming/outgoing connection
6670 counts. Tor no longer skips version 5, and we won't have to
6671 remember to update this function when new link protocol version is
6672 developed. Fixes bug 28920; bugfix on 0.2.6.10.
6674 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
6675 - Log more information at "warning" level when unable to read a
6676 private key; log more information at "info" level when unable to
6677 read a public key. We had warnings here before, but they were lost
6678 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
6680 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
6681 - The amount of total available physical memory is now determined
6682 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
6683 when it is defined and a 64-bit variant is not available. Fixes
6684 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
6686 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
6687 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
6688 than one private key for a hidden service. Fixes bug 29040; bugfix
6690 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
6691 "debug" level. Tor used to log it as a warning, which caused very
6692 long log lines to appear for some users. Fixes bug 29135; bugfix
6694 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
6695 as a warning. Instead, log it as a protocol warning, because there
6696 is nothing that relay operators can do to fix it. Fixes bug 29029;
6697 bugfix on 0.2.5.7-rc.
6699 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
6700 - Mark outdated dirservers when Tor only has a reasonably live
6701 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
6703 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
6704 - Detect and suppress "bug" warnings from the util/time test on
6705 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
6706 - Do not log an error-level message if we fail to find an IPv6
6707 network interface from the unit tests. Fixes bug 29160; bugfix
6710 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
6711 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
6712 Some users took this phrasing to mean that the mentioned guard was
6713 under their control or responsibility, which it is not. Fixes bug
6714 28895; bugfix on Tor 0.3.0.1-alpha.
6717 Changes in version 0.3.4.11 - 2019-02-21
6718 Tor 0.3.4.11 is the third stable release in its series. It includes
6719 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
6720 later. All Tor instances running an affected release should upgrade to
6721 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
6723 o Major bugfixes (cell scheduler, KIST, security):
6724 - Make KIST consider the outbuf length when computing what it can
6725 put in the outbuf. Previously, KIST acted as though the outbuf
6726 were empty, which could lead to the outbuf becoming too full. It
6727 is possible that an attacker could exploit this bug to cause a Tor
6728 client or relay to run out of memory and crash. Fixes bug 29168;
6729 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
6730 TROVE-2019-001 and CVE-2019-8955.
6732 o Minor features (geoip):
6733 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
6734 Country database. Closes ticket 29478.
6736 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
6737 - Update Cargo.lock file to match the version made by the latest
6738 version of Rust, so that "make distcheck" will pass again. Fixes
6739 bug 29244; bugfix on 0.3.3.4-alpha.
6741 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
6742 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
6743 as a warning. Instead, log it as a protocol warning, because there
6744 is nothing that relay operators can do to fix it. Fixes bug 29029;
6745 bugfix on 0.2.5.7-rc.
6748 Changes in version 0.3.3.12 - 2019-02-21
6749 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
6750 0.3.2.1-alpha and later. All Tor instances running an affected release
6751 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
6753 This release marks the end of support for the Tor 0.3.3.x series. We
6754 recommend that users switch to either the Tor 0.3.4 series (supported
6755 until at least 10 June 2019), or the Tor 0.3.5 series, which will
6756 receive long-term support until at least 1 Feb 2022.
6758 o Major bugfixes (cell scheduler, KIST, security):
6759 - Make KIST consider the outbuf length when computing what it can
6760 put in the outbuf. Previously, KIST acted as though the outbuf
6761 were empty, which could lead to the outbuf becoming too full. It
6762 is possible that an attacker could exploit this bug to cause a Tor
6763 client or relay to run out of memory and crash. Fixes bug 29168;
6764 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
6765 TROVE-2019-001 and CVE-2019-8955.
6767 o Minor features (geoip):
6768 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
6769 Country database. Closes ticket 29478.
6771 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
6772 - Update Cargo.lock file to match the version made by the latest
6773 version of Rust, so that "make distcheck" will pass again. Fixes
6774 bug 29244; bugfix on 0.3.3.4-alpha.
6776 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
6777 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
6778 as a warning. Instead, log it as a protocol warning, because there
6779 is nothing that relay operators can do to fix it. Fixes bug 29029;
6780 bugfix on 0.2.5.7-rc.
6783 Changes in version 0.3.3.11 - 2019-01-07
6784 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
6785 numerous fixes, including an important fix for anyone using OpenSSL
6786 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
6787 to this version, or to a later series.
6789 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
6790 We anticipate that this will be the last release of Tor 0.3.3, unless
6791 some major bug is before then. Some time between now and then, users
6792 should switch to either the Tor 0.3.4 series (supported until at least
6793 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
6794 support until at least 1 Feb 2022.
6796 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
6797 - Fix our usage of named groups when running as a TLS 1.3 client in
6798 OpenSSL 1.1.1. Previously, we only initialized EC groups when
6799 running as a relay, which caused clients to fail to negotiate TLS
6800 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
6803 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
6804 - Fix a use-after-free error that could be caused by passing Tor an
6805 impossible set of options that would fail during options_act().
6806 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
6808 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
6809 - Only run one online rust build in Travis, to reduce network
6810 errors. Skip offline rust builds on Travis for Linux gcc, because
6811 they're redundant. Implements ticket 27252.
6812 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
6813 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
6814 Linux with default settings, because all the non-default builds
6815 use gcc on Linux. Implements ticket 27252.
6817 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
6818 - Use the Travis Homebrew addon to install packages on macOS during
6819 Travis CI. The package list is the same, but the Homebrew addon
6820 does not do a `brew update` by default. Implements ticket 27738.
6822 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
6823 - Replace the 150 fallbacks originally introduced in Tor
6824 0.3.3.1-alpha in January 2018 (of which ~115 were still
6825 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
6826 removed) generated in December 2018. Closes ticket 24803.
6828 o Minor features (geoip):
6829 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
6830 Country database. Closes ticket 29012.
6832 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
6833 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
6834 key export function from handling long labels. When this bug is
6835 detected, Tor will disable TLS 1.3. We recommend upgrading to a
6836 version of OpenSSL without this bug when it becomes available.
6837 Closes ticket 28973.
6839 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
6840 - Update relay descriptor on bandwidth changes only when the uptime
6841 is smaller than 24h, in order to reduce the efficiency of guard
6842 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
6844 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
6845 - Avoid undefined behavior in an end-of-string check when parsing
6846 the BEGIN line in a directory object. Fixes bug 28202; bugfix
6849 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
6850 - Rewrite our assertion macros so that they no longer suppress the
6851 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
6853 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
6854 - Initialize a variable unconditionally in aes_new_cipher(), since
6855 some compilers cannot tell that we always initialize it before
6856 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
6858 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
6859 - Log additional info when we get a relay that shares an ed25519 ID
6860 with a different relay, instead making a BUG() warning. Fixes bug
6861 27800; bugfix on 0.3.2.1-alpha.
6863 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
6864 - When a user requests a group-readable DataDirectory, give it to
6865 them. Previously, when the DataDirectory and the CacheDirectory
6866 were the same, the default setting (0) for
6867 CacheDirectoryGroupReadable would override the setting for
6868 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
6871 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
6872 - When the onion service directory can't be created or has the wrong
6873 permissions, do not log a stack trace. Fixes bug 27335; bugfix
6876 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
6877 - Close all SOCKS request (for the same .onion) if the newly fetched
6878 descriptor is unusable. Before that, we would close only the first
6879 one leaving the other hanging and let to time out by themselves.
6880 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
6882 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
6883 - Don't warn so loudly when Tor is unable to decode an onion
6884 descriptor. This can now happen as a normal use case if a client
6885 gets a descriptor with client authorization but the client is not
6886 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
6888 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
6889 - When deleting an ephemeral onion service (DEL_ONION), do not close
6890 any rendezvous circuits in order to let the existing client
6891 connections finish by themselves or closed by the application. The
6892 HS v2 is doing that already so now we have the same behavior for
6893 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
6895 o Minor bugfixes (HTTP tunnel):
6896 - Fix a bug warning when closing an HTTP tunnel connection due to
6897 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
6900 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
6901 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
6902 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
6904 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
6905 - Ensure circuitmux queues are empty before scheduling or sending
6906 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
6908 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
6909 - Reject protocol names containing bytes other than alphanumeric
6910 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
6913 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
6914 - Compute protover votes correctly in the rust version of the
6915 protover code. Previously, the protover rewrite in 24031 allowed
6916 repeated votes from the same voter for the same protocol version
6917 to be counted multiple times in protover_compute_vote(). Fixes bug
6918 27649; bugfix on 0.3.3.5-rc.
6919 - Reject protover names that contain invalid characters. Fixes bug
6920 27687; bugfix on 0.3.3.1-alpha.
6922 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
6923 - protover_all_supported() would attempt to allocate up to 16GB on
6924 some inputs, leading to a potential memory DoS. Fixes bug 27206;
6925 bugfix on 0.3.3.5-rc.
6927 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
6928 - Fix a potential null dereference in protover_all_supported(). Add
6929 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
6930 - Return a string that can be safely freed by C code, not one
6931 created by the rust allocator, in protover_all_supported(). Fixes
6932 bug 27740; bugfix on 0.3.3.1-alpha.
6933 - Fix an API mismatch in the rust implementation of
6934 protover_compute_vote(). This bug could have caused crashes on any
6935 directory authorities running Tor with Rust (which we do not yet
6936 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
6938 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
6939 - If a unit test running in a subprocess exits abnormally or with a
6940 nonzero status code, treat the test as having failed, even if the
6941 test reported success. Without this fix, memory leaks don't cause
6942 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
6943 bugfix on 0.2.2.4-alpha.
6945 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
6946 - Treat backtrace test failures as expected on BSD-derived systems
6947 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
6948 (FreeBSD failures have been treated as expected since 18204 in
6949 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
6951 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
6952 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
6953 bugfix on 0.3.0.1-alpha.
6956 Changes in version 0.3.4.10 - 2019-01-07
6957 Tor 0.3.4.9 is the second stable release in its series; it backports
6958 numerous fixes, including an important fix for relays, and for anyone
6959 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
6962 As a reminder, the Tor 0.3.4 series will be supported until 10 June
6963 2019. Some time between now and then, users should switch to the Tor
6964 0.3.5 series, which will receive long-term support until at least 1
6967 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
6968 - Fix our usage of named groups when running as a TLS 1.3 client in
6969 OpenSSL 1.1.1. Previously, we only initialized EC groups when
6970 running as a relay, which caused clients to fail to negotiate TLS
6971 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
6974 o Major bugfixes (relay, directory, backport from 0.3.5.7):
6975 - Always reactivate linked connections in the main loop so long as
6976 any linked connection has been active. Previously, connections
6977 serving directory information wouldn't get reactivated after the
6978 first chunk of data was sent (usually 32KB), which would prevent
6979 clients from bootstrapping. Fixes bug 28912; bugfix on
6980 0.3.4.1-alpha. Patch by "cypherpunks3".
6982 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
6983 - Always show the configure and test logs, and upload them as build
6984 artifacts, when building for Windows using Appveyor CI.
6987 o Minor features (controller, backport from 0.3.5.1-alpha):
6988 - For purposes of CIRC_BW-based dropped cell detection, track half-
6989 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
6990 bias check cells to arrive without counting it as dropped until
6991 either the END arrives, or the windows are empty. Closes
6994 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
6995 - Replace the 150 fallbacks originally introduced in Tor
6996 0.3.3.1-alpha in January 2018 (of which ~115 were still
6997 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
6998 removed) generated in December 2018. Closes ticket 24803.
7000 o Minor features (geoip):
7001 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
7002 Country database. Closes ticket 28395.
7004 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
7005 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
7006 key export function from handling long labels. When this bug is
7007 detected, Tor will disable TLS 1.3. We recommend upgrading to a
7008 version of OpenSSL without this bug when it becomes available.
7009 Closes ticket 28973.
7011 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
7012 - Initialize a variable unconditionally in aes_new_cipher(), since
7013 some compilers cannot tell that we always initialize it before
7014 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
7016 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
7017 - Avoid a logging a BUG() stacktrace when closing connection held
7018 open because the write side is rate limited but not the read side.
7019 Now, the connection read side is simply shut down until Tor is
7020 able to flush the connection and close it. Fixes bug 27750; bugfix
7023 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
7024 - Manually configure the zstd compiler options, when building using
7025 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
7026 not come with a pkg-config file. Fixes bug 28454; bugfix
7028 - Stop using an external OpenSSL install, and stop installing MSYS2
7029 packages, when building using mingw on Appveyor Windows CI. Fixes
7030 bug 28399; bugfix on 0.3.4.1-alpha.
7032 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
7033 - Explicitly specify the path to the OpenSSL library and do not
7034 download OpenSSL from Pacman, but instead use the library that is
7035 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
7037 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
7038 - When a user requests a group-readable DataDirectory, give it to
7039 them. Previously, when the DataDirectory and the CacheDirectory
7040 were the same, the default setting (0) for
7041 CacheDirectoryGroupReadable would override the setting for
7042 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
7045 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
7046 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
7047 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
7049 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
7050 - Don't warn so loudly when Tor is unable to decode an onion
7051 descriptor. This can now happen as a normal use case if a client
7052 gets a descriptor with client authorization but the client is not
7053 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
7055 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
7056 - When deleting an ephemeral onion service (DEL_ONION), do not close
7057 any rendezvous circuits in order to let the existing client
7058 connections finish by themselves or closed by the application. The
7059 HS v2 is doing that already so now we have the same behavior for
7060 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
7062 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
7063 - Update relay descriptor on bandwidth changes only when the uptime
7064 is smaller than 24h, in order to reduce the efficiency of guard
7065 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
7067 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
7068 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
7069 bugfix on 0.3.0.1-alpha.
7072 Changes in version 0.3.5.7 - 2019-01-07
7073 Tor 0.3.5.7 is the first stable release in its series; it includes
7074 compilation and portability fixes, and a fix for a severe problem
7075 affecting directory caches.
7077 The Tor 0.3.5 series includes several new features and performance
7078 improvements, including client authorization for v3 onion services,
7079 cleanups to bootstrap reporting, support for improved bandwidth-
7080 measurement tools, experimental support for NSS in place of OpenSSL,
7081 and much more. It also begins a full reorganization of Tor's code
7082 layout, for improved modularity and maintainability in the future.
7083 Finally, there is the usual set of performance improvements and
7084 bugfixes that we try to do in every release series.
7086 There are a couple of changes in the 0.3.5 that may affect
7087 compatibility. First, the default version for newly created onion
7088 services is now v3. Use the HiddenServiceVersion option if you want to
7089 override this. Second, some log messages related to bootstrapping have
7090 changed; if you use stem, you may need to update to the latest version
7091 so it will recognize them.
7093 We have designated 0.3.5 as a "long-term support" (LTS) series: we
7094 will continue to patch major bugs in typical configurations of 0.3.5
7095 until at least 1 Feb 2022. (We do not plan to provide long-term
7096 support for embedding, Rust support, NSS support, running a directory
7097 authority, or unsupported platforms. For these, you will need to stick
7098 with the latest stable release.)
7100 Below are the changes since 0.3.4.9. For a complete list of changes
7101 since 0.3.5.6-rc, see the ChangeLog file.
7103 o Major features (bootstrap):
7104 - Don't report directory progress until after a connection to a
7105 relay or bridge has succeeded. Previously, we'd report 80%
7106 progress based on cached directory information when we couldn't
7107 even connect to the network. Closes ticket 27169.
7109 o Major features (new code layout):
7110 - Nearly all of Tor's source code has been moved around into more
7111 logical places. The "common" directory is now divided into a set
7112 of libraries in "lib", and files in the "or" directory have been
7113 split into "core" (logic absolutely needed for onion routing),
7114 "feature" (independent modules in Tor), and "app" (to configure
7115 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
7116 more information. Closes ticket 26481.
7118 This refactoring is not complete: although the libraries have been
7119 refactored to be acyclic, the main body of Tor is still too
7120 interconnected. We will attempt to improve this in the future.
7122 o Major features (onion services v3):
7123 - Implement onion service client authorization at the descriptor
7124 level: only authorized clients can decrypt a service's descriptor
7125 to find out how to contact it. A new torrc option was added to
7126 control this client side: ClientOnionAuthDir <path>. On the
7127 service side, if the "authorized_clients/" directory exists in the
7128 onion service directory path, client configurations are read from
7129 the files within. See the manpage for more details. Closes ticket
7130 27547. Patch done by Suphanat Chunhapanya (haxxpop).
7131 - Improve revision counter generation in next-gen onion services.
7132 Onion services can now scale by hosting multiple instances on
7133 different hosts without synchronization between them, which was
7134 previously impossible because descriptors would get rejected by
7135 HSDirs. Addresses ticket 25552.
7136 - Version 3 onion services can now use the per-service
7137 HiddenServiceExportCircuitID option to differentiate client
7138 circuits. It communicates with the service by using the HAProxy
7139 protocol to assign virtual IP addresses to inbound client
7140 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
7142 o Major features (onion services, UI change):
7143 - For a newly created onion service, the default version is now 3.
7144 Tor still supports existing version 2 services, but the operator
7145 now needs to set "HiddenServiceVersion 2" in order to create a new
7146 version 2 service. For existing services, Tor now learns the
7147 version by reading the key file. Closes ticket 27215.
7149 o Major features (portability, cryptography, experimental, TLS):
7150 - Tor now has the option to compile with the NSS library instead of
7151 OpenSSL. This feature is experimental, and we expect that bugs may
7152 remain. It is mainly intended for environments where Tor's
7153 performance is not CPU-bound, and where NSS is already known to be
7154 installed. To try it out, configure Tor with the --enable-nss
7155 flag. Closes tickets 26631, 26815, and 26816.
7157 If you are experimenting with this option and using an old cached
7158 consensus, Tor may fail to start. To solve this, delete your
7159 "cached-consensus" and "cached-microdesc-consensus" files,
7160 (if present), and restart Tor.
7162 o Major features (relay, UI change):
7163 - Relays no longer run as exits by default. If the "ExitRelay"
7164 option is auto (or unset), and no exit policy is specified with
7165 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
7166 Previously in this case, we allowed exit traffic and logged a
7167 warning message. Closes ticket 21530. Patch by Neel Chauhan.
7168 - Tor now validates that the ContactInfo config option is valid UTF-
7169 8 when parsing torrc. Closes ticket 27428.
7171 o Major bugfixes (compilation):
7172 - Fix compilation on ARM (and other less-used CPUs) when compiling
7173 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
7175 o Major bugfixes (compilation, rust):
7176 - Rust tests can now build and run successfully with the
7177 --enable-fragile-hardening option enabled. Doing this currently
7178 requires the rust beta channel; it will be possible with stable
7179 rust once Rust version 1.31 is released. Patch from Alex Crichton.
7180 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
7182 o Major bugfixes (directory authority):
7183 - Actually check that the address we get from DirAuthority
7184 configuration line is valid IPv4. Explicitly disallow DirAuthority
7185 address to be a DNS hostname. Fixes bug 26488; bugfix
7188 o Major bugfixes (embedding, main loop):
7189 - When DisableNetwork becomes set, actually disable periodic events
7190 that are already enabled. (Previously, we would refrain from
7191 enabling new ones, but we would leave the old ones turned on.)
7192 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
7194 o Major bugfixes (main loop, bootstrap):
7195 - Make sure Tor bootstraps and works properly if only the
7196 ControlPort is set. Prior to this fix, Tor would only bootstrap
7197 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
7198 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
7200 o Major bugfixes (onion service v3):
7201 - On an intro point for a version 3 onion service, stop closing
7202 introduction circuits on a NACK. This lets the client decide
7203 whether to reuse the circuit or discard it. Previously, we closed
7204 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
7205 0.3.2.1-alpha. Patch by Neel Chaunan.
7207 o Major bugfixes (OpenSSL, portability):
7208 - Fix our usage of named groups when running as a TLS 1.3 client in
7209 OpenSSL 1.1.1. Previously, we only initialized EC groups when
7210 running as a relay, which caused clients to fail to negotiate TLS
7211 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
7214 o Major bugfixes (relay bandwidth statistics):
7215 - When we close relayed circuits, report the data in the circuit
7216 queues as being written in our relay bandwidth stats. This
7217 mitigates guard discovery and other attacks that close circuits
7218 for the explicit purpose of noticing this discrepancy in
7219 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
7221 o Major bugfixes (relay):
7222 - When our write bandwidth limit is exhausted, stop writing on the
7223 connection. Previously, we had a typo in the code that would make
7224 us stop reading instead, leading to relay connections being stuck
7225 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
7227 - Always reactivate linked connections in the main loop so long as
7228 any linked connection has been active. Previously, connections
7229 serving directory information wouldn't get reactivated after the
7230 first chunk of data was sent (usually 32KB), which would prevent
7231 clients from bootstrapping. Fixes bug 28912; bugfix on
7232 0.3.4.1-alpha. Patch by "cypherpunks3".
7234 o Major bugfixes (restart-in-process):
7235 - Fix a use-after-free error that could be caused by passing Tor an
7236 impossible set of options that would fail during options_act().
7237 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
7239 o Minor features (admin tools):
7240 - Add a new --key-expiration option to print the expiration date of
7241 the signing cert in an ed25519_signing_cert file. Resolves
7244 o Minor features (build):
7245 - If you pass the "--enable-pic" option to configure, Tor will try
7246 to tell the compiler to build position-independent code suitable
7247 to link into a dynamic library. (The default remains -fPIE, for
7248 code suitable for a relocatable executable.) Closes ticket 23846.
7250 o Minor features (code correctness, testing):
7251 - Tor's build process now includes a "check-includes" make target to
7252 verify that no module of Tor relies on any headers from a higher-
7253 level module. We hope to use this feature over time to help
7254 refactor our codebase. Closes ticket 26447.
7256 o Minor features (code layout):
7257 - We have a new "lowest-level" error-handling API for use by code
7258 invoked from within the logging module. With this interface, the
7259 logging code is no longer at risk of calling into itself if a
7260 failure occurs while it is trying to log something. Closes
7263 o Minor features (compilation):
7264 - When possible, place our warning flags in a separate file, to
7265 avoid flooding verbose build logs. Closes ticket 28924.
7266 - Tor's configure script now supports a --with-malloc= option to
7267 select your malloc implementation. Supported options are
7268 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
7269 default). Addresses part of ticket 20424. Based on a patch from
7272 o Minor features (config):
7273 - The "auto" keyword in torrc is now case-insensitive. Closes
7276 o Minor features (continuous integration):
7277 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
7279 - Add new CI job to Travis configuration to run stem-based
7280 integration tests. Closes ticket 27913.
7281 - Use the Travis Homebrew addon to install packages on macOS during
7282 Travis CI. The package list is the same, but the Homebrew addon
7283 does not do a `brew update` by default. Implements ticket 27738.
7284 - Report what program produced the mysterious core file that we
7285 occasionally see on Travis CI during make distcheck. Closes
7287 - Don't do a distcheck with --disable-module-dirauth in Travis.
7288 Implements ticket 27252.
7289 - Install libcap-dev and libseccomp2-dev so these optional
7290 dependencies get tested on Travis CI. Closes ticket 26560.
7291 - Only run one online rust build in Travis, to reduce network
7292 errors. Skip offline rust builds on Travis for Linux gcc, because
7293 they're redundant. Implements ticket 27252.
7294 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
7295 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
7296 Linux with default settings, because all the non-default builds
7297 use gcc on Linux. Implements ticket 27252.
7299 o Minor features (continuous integration, Windows):
7300 - Always show the configure and test logs, and upload them as build
7301 artifacts, when building for Windows using Appveyor CI.
7303 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
7304 Appveyor's CI. Closes ticket 28318.
7306 o Minor features (controller):
7307 - Emit CIRC_BW events as soon as we detect that we processed an
7308 invalid or otherwise dropped cell on a circuit. This allows
7309 vanguards and other controllers to react more quickly to dropped
7310 cells. Closes ticket 27678.
7311 - For purposes of CIRC_BW-based dropped cell detection, track half-
7312 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
7313 bias check cells to arrive without counting it as dropped until
7314 either the END arrives, or the windows are empty. Closes
7316 - Implement a 'GETINFO md/all' controller command to enable getting
7317 all known microdescriptors. Closes ticket 8323.
7318 - The GETINFO command now support an "uptime" argument, to return
7319 Tor's uptime in seconds. Closes ticket 25132.
7321 o Minor features (denial-of-service avoidance):
7322 - Make our OOM handler aware of the DNS cache so that it doesn't
7323 fill up the memory. This check is important for our DoS mitigation
7324 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
7326 o Minor features (development):
7327 - Tor's makefile now supports running the "clippy" Rust style tool
7328 on our Rust code. Closes ticket 22156.
7330 o Minor features (directory authority):
7331 - There is no longer an artificial upper limit on the length of
7332 bandwidth lines. Closes ticket 26223.
7333 - When a bandwidth file is used to obtain the bandwidth measurements,
7334 include this bandwidth file headers in the votes. Closes
7336 - Improved support for networks with only a single authority or a
7337 single fallback directory. Patch from Gabriel Somlo. Closes
7340 o Minor features (embedding API):
7341 - The Tor controller API now supports a function to launch Tor with
7342 a preconstructed owning controller FD, so that embedding
7343 applications don't need to manage controller ports and
7344 authentication. Closes ticket 24204.
7345 - The Tor controller API now has a function that returns the name
7346 and version of the backend implementing the API. Closes
7349 o Minor features (fallback directory list):
7350 - Replace the 150 fallbacks originally introduced in Tor
7351 0.3.3.1-alpha in January 2018 (of which ~115 were still
7352 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
7353 removed) generated in December 2018. Closes ticket 24803.
7355 o Minor features (geoip):
7356 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
7357 Country database. Closes ticket 29012.
7359 o Minor features (memory management):
7360 - Get Libevent to use the same memory allocator as Tor, by calling
7361 event_set_mem_functions() during initialization. Resolves
7364 o Minor features (memory usage):
7365 - When not using them, store legacy TAP public onion keys in DER-
7366 encoded format, rather than as expanded public keys. This should
7367 save several megabytes on typical clients. Closes ticket 27246.
7369 o Minor features (OpenSSL bug workaround):
7370 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
7371 key export function from handling long labels. When this bug is
7372 detected, Tor will disable TLS 1.3. We recommend upgrading to a
7373 version of OpenSSL without this bug when it becomes available.
7374 Closes ticket 28973.
7376 o Minor features (OpenSSL):
7377 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
7378 than our own. Resolves ticket 19979.
7380 o Minor features (performance):
7381 - Remove about 96% of the work from the function that we run at
7382 startup to test our curve25519_basepoint implementation. Since
7383 this function has yet to find an actual failure, we now only run
7384 it for 8 iterations instead of 200. Based on our profile
7385 information, this change should save around 8% of our startup time
7386 on typical desktops, and may have a similar effect on other
7387 platforms. Closes ticket 28838.
7388 - Stop re-validating our hardcoded Diffie-Hellman parameters on
7389 every startup. Doing this wasted time and cycles, especially on
7390 low-powered devices. Closes ticket 28851.
7392 o Minor features (Rust, code quality):
7393 - Improve rust code quality in the rust protover implementation by
7394 making it more idiomatic. Includes changing an internal API to
7395 take &str instead of &String. Closes ticket 26492.
7397 o Minor features (testing):
7398 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
7399 chutney. Implements ticket 27211.
7401 o Minor features (tor-resolve):
7402 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
7403 Side-effect of the refactoring for ticket 26526.
7405 o Minor features (UI):
7406 - Log each included configuration file or directory as we read it,
7407 to provide more visibility about where Tor is reading from. Patch
7408 from Unto Sten; closes ticket 27186.
7409 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
7410 Closes ticket 26703.
7412 o Minor bugfixes (32-bit OSX and iOS, timing):
7413 - Fix an integer overflow bug in our optimized 32-bit millisecond-
7414 difference algorithm for 32-bit Apple platforms. Previously, it
7415 would overflow when calculating the difference between two times
7416 more than 47 days apart. Fixes part of bug 27139; bugfix
7418 - Improve the precision of our 32-bit millisecond difference
7419 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
7420 bugfix on 0.3.4.1-alpha.
7421 - Relax the tolerance on the mainloop/update_time_jumps test when
7422 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
7425 o Minor bugfixes (bootstrap):
7426 - Try harder to get descriptors in non-exit test networks, by using
7427 the mid weight for the third hop when there are no exits. Fixes
7428 bug 27237; bugfix on 0.2.6.2-alpha.
7430 o Minor bugfixes (C correctness):
7431 - Avoid casting smartlist index to int implicitly, as it may trigger
7432 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
7433 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
7434 - Use time_t for all values in
7435 predicted_ports_prediction_time_remaining(). Rework the code that
7436 computes difference between durations/timestamps. Fixes bug 27165;
7437 bugfix on 0.3.1.1-alpha.
7439 o Minor bugfixes (client, memory usage):
7440 - When not running as a directory cache, there is no need to store
7441 the text of the current consensus networkstatus in RAM.
7442 Previously, however, clients would store it anyway, at a cost of
7443 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
7446 o Minor bugfixes (client, ReachableAddresses):
7447 - Instead of adding a "reject *:*" line to ReachableAddresses when
7448 loading the configuration, add one to the policy after parsing it
7449 in parse_reachable_addresses(). This prevents extra "reject *.*"
7450 lines from accumulating on reloads. Fixes bug 20874; bugfix on
7451 0.1.1.5-alpha. Patch by Neel Chauhan.
7453 o Minor bugfixes (code quality):
7454 - Rename sandbox_getaddrinfo() and other functions to no longer
7455 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
7456 bugfix on 0.2.7.1-alpha.
7458 o Minor bugfixes (code safety):
7459 - Rewrite our assertion macros so that they no longer suppress the
7460 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
7463 o Minor bugfixes (compilation):
7464 - Initialize a variable unconditionally in aes_new_cipher(), since
7465 some compilers cannot tell that we always initialize it before
7466 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
7468 o Minor bugfixes (configuration):
7469 - Refuse to start with relative file paths and RunAsDaemon set
7470 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
7473 o Minor bugfixes (configuration, Onion Services):
7474 - In rend_service_parse_port_config(), disallow any input to remain
7475 after address-port pair was parsed. This will catch address and
7476 port being whitespace-separated by mistake of the user. Fixes bug
7477 27044; bugfix on 0.2.9.10.
7479 o Minor bugfixes (connection, relay):
7480 - Avoid a logging a BUG() stacktrace when closing connection held
7481 open because the write side is rate limited but not the read side.
7482 Now, the connection read side is simply shut down until Tor is
7483 able to flush the connection and close it. Fixes bug 27750; bugfix
7486 o Minor bugfixes (continuous integration, Windows):
7487 - Stop reinstalling identical packages in our Windows CI. Fixes bug
7488 27464; bugfix on 0.3.4.1-alpha.
7489 - Install only the necessary mingw packages during our appveyor
7490 builds. This change makes the build a little faster, and prevents
7491 a conflict with a preinstalled mingw openssl that appveyor now
7492 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
7493 - Explicitly specify the path to the OpenSSL library and do not
7494 download OpenSSL from Pacman, but instead use the library that is
7495 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
7496 - Manually configure the zstd compiler options, when building using
7497 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
7498 not come with a pkg-config file. Fixes bug 28454; bugfix
7500 - Stop using an external OpenSSL install, and stop installing MSYS2
7501 packages, when building using mingw on Appveyor Windows CI. Fixes
7502 bug 28399; bugfix on 0.3.4.1-alpha.
7504 o Minor bugfixes (controller):
7505 - Consider all routerinfo errors other than "not a server" to be
7506 transient for the purpose of "GETINFO exit-policy/*" controller
7507 request. Print stacktrace in the unlikely case of failing to
7508 recompute routerinfo digest. Fixes bug 27034; bugfix
7511 o Minor bugfixes (correctness):
7512 - Fix an unreached code path where we checked the value of
7513 "hostname" inside send_resolved_hostname_cell(). Previously, we
7514 used it before checking it; now we check it first. Fixes bug
7515 28879; bugfix on 0.1.2.7-alpha.
7517 o Minor bugfixes (directory connection shutdown):
7518 - Avoid a double-close when shutting down a stalled directory
7519 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
7521 o Minor bugfixes (directory permissions):
7522 - When a user requests a group-readable DataDirectory, give it to
7523 them. Previously, when the DataDirectory and the CacheDirectory
7524 were the same, the default setting (0) for
7525 CacheDirectoryGroupReadable would override the setting for
7526 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
7529 o Minor bugfixes (HTTP tunnel):
7530 - Fix a bug warning when closing an HTTP tunnel connection due to an
7531 HTTP request we couldn't handle. Fixes bug 26470; bugfix
7534 o Minor bugfixes (ipv6):
7535 - In addrs_in_same_network_family(), we choose the subnet size based
7536 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
7537 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
7538 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
7540 o Minor bugfixes (Linux seccomp2 sandbox):
7541 - Permit the "shutdown()" system call, which is apparently used by
7542 OpenSSL under some circumstances. Fixes bug 28183; bugfix
7545 o Minor bugfixes (logging):
7546 - Stop talking about the Named flag in log messages. Clients have
7547 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
7549 - As a precaution, do an early return from log_addr_has_changed() if
7550 Tor is running as client. Also, log a stack trace for debugging as
7551 this function should only be called when Tor runs as server. Fixes
7552 bug 26892; bugfix on 0.1.1.9-alpha.
7553 - Refrain from mentioning bug 21018 in the logs, as it is already
7554 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
7556 o Minor bugfixes (logging, documentation):
7557 - When SafeLogging is enabled, scrub IP address in
7558 channel_tls_process_netinfo_cell(). Also, add a note to manpage
7559 that scrubbing is not guaranteed on loglevels below Notice. Fixes
7560 bug 26882; bugfix on 0.2.4.10-alpha.
7562 o Minor bugfixes (memory leaks):
7563 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
7564 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
7565 - Fix a small memory leak when calling Tor with --dump-config. Fixes
7566 bug 27893; bugfix on 0.3.2.1-alpha.
7568 o Minor bugfixes (netflow padding):
7569 - Ensure circuitmux queues are empty before scheduling or sending
7570 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
7572 o Minor bugfixes (onion service v2):
7573 - Log at level "info", not "warning", in the case that we do not
7574 have a consensus when a .onion request comes in. This can happen
7575 normally while bootstrapping. Fixes bug 27040; bugfix
7578 o Minor bugfixes (onion service v3):
7579 - When deleting an ephemeral onion service (DEL_ONION), do not close
7580 any rendezvous circuits in order to let the existing client
7581 connections finish by themselves or closed by the application. The
7582 HS v2 is doing that already so now we have the same behavior for
7583 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
7584 - Build the service descriptor's signing key certificate before
7585 uploading, so we always have a fresh one: leaving no chances for
7586 it to expire service side. Fixes bug 27838; bugfix
7588 - Stop dumping a stack trace when trying to connect to an intro
7589 point without having a descriptor for it. Fixes bug 27774; bugfix
7591 - When selecting a v3 rendezvous point, don't only look at the
7592 protover, but also check whether the curve25519 onion key is
7593 present. This way we avoid picking a relay that supports the v3
7594 rendezvous but for which we don't have the microdescriptor. Fixes
7595 bug 27797; bugfix on 0.3.2.1-alpha.
7596 - Close all SOCKS request (for the same .onion) if the newly fetched
7597 descriptor is unusable. Before that, we would close only the first
7598 one leaving the other hanging and let to time out by themselves.
7599 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
7600 - When the onion service directory can't be created or has the wrong
7601 permissions, do not log a stack trace. Fixes bug 27335; bugfix
7603 - When replacing a descriptor in the client cache, make sure to
7604 close all client introduction circuits for the old descriptor, so
7605 we don't end up with unusable leftover circuits. Fixes bug 27471;
7606 bugfix on 0.3.2.1-alpha.
7608 o Minor bugfixes (OS compatibility):
7609 - Properly handle configuration changes that move a listener to/from
7610 wildcard IP address. If the first attempt to bind a socket fails,
7611 close the old listener and try binding the socket again. Fixes bug
7612 17873; bugfix on 0.0.8pre-1.
7614 o Minor bugfixes (performance)::
7615 - Rework node_is_a_configured_bridge() to no longer call
7616 node_get_all_orports(), which was performing too many memory
7617 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
7619 o Minor bugfixes (protover):
7620 - Reject protocol names containing bytes other than alphanumeric
7621 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
7624 o Minor bugfixes (protover, rust):
7625 - Reject extra commas in version strings. Fixes bug 27197; bugfix
7627 - protover_all_supported() would attempt to allocate up to 16GB on
7628 some inputs, leading to a potential memory DoS. Fixes bug 27206;
7629 bugfix on 0.3.3.5-rc.
7630 - Compute protover votes correctly in the rust version of the
7631 protover code. Previously, the protover rewrite in 24031 allowed
7632 repeated votes from the same voter for the same protocol version
7633 to be counted multiple times in protover_compute_vote(). Fixes bug
7634 27649; bugfix on 0.3.3.5-rc.
7635 - Reject protover names that contain invalid characters. Fixes bug
7636 27687; bugfix on 0.3.3.1-alpha.
7638 o Minor bugfixes (relay shutdown, systemd):
7639 - Notify systemd of ShutdownWaitLength so it can be set to longer
7640 than systemd's TimeoutStopSec. In Tor's systemd service file, set
7641 TimeoutSec to 60 seconds to allow Tor some time to shut down.
7642 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
7644 o Minor bugfixes (relay statistics):
7645 - Update relay descriptor on bandwidth changes only when the uptime
7646 is smaller than 24h, in order to reduce the efficiency of guard
7647 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
7649 o Minor bugfixes (relay):
7650 - Consider the fact that we'll be making direct connections to our
7651 entry and guard nodes when computing the fraction of nodes that
7652 have their descriptors. Also, if we are using bridges and there is
7653 at least one bridge with a full descriptor, treat the fraction of
7654 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
7655 Patch by Neel Chauhan.
7656 - Update the message logged on relays when DirCache is disabled.
7657 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
7658 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
7660 o Minor bugfixes (testing):
7661 - Stop running stem's unit tests as part of "make test-stem", but
7662 continue to run stem's unit and online tests during "make test-
7663 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
7664 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
7665 bugfix on 0.3.0.1-alpha.
7666 - Make the hs_service tests use the same time source when creating
7667 the introduction point and when testing it. Now tests work better
7668 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
7670 - Revise the "conditionvar_timeout" test so that it succeeds even on
7671 heavily loaded systems where the test threads are not scheduled
7672 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
7673 - Fix two unit tests to work when HOME environment variable is not
7674 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
7675 - If a unit test running in a subprocess exits abnormally or with a
7676 nonzero status code, treat the test as having failed, even if the
7677 test reported success. Without this fix, memory leaks don't cause
7678 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
7679 bugfix on 0.2.2.4-alpha.
7680 - When logging a version mismatch in our openssl_version tests,
7681 report the actual offending version strings. Fixes bug 26152;
7682 bugfix on 0.2.9.1-alpha.
7683 - Fix forking tests on Windows when there is a space somewhere in
7684 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
7686 o Minor bugfixes (Windows):
7687 - Correctly identify Windows 8.1, Windows 10, and Windows Server
7688 2008 and later from their NT versions. Fixes bug 28096; bugfix on
7689 0.2.2.34; reported by Keifer Bly.
7690 - On recent Windows versions, the GetVersionEx() function may report
7691 an earlier Windows version than the running OS. To avoid user
7692 confusion, add "[or later]" to Tor's version string on affected
7693 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
7695 - Remove Windows versions that were never supported by the
7696 GetVersionEx() function. Stop duplicating the latest Windows
7697 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
7698 reported by Keifer Bly.
7700 o Code simplification and refactoring:
7701 - When parsing a port configuration, make it more obvious to static
7702 analyzer tools that we always initialize the address. Closes
7704 - Divide more large Tor source files -- especially ones that span
7705 multiple areas of functionality -- into smaller parts, including
7706 onion.c and main.c. Closes ticket 26747.
7707 - Divide the "routerparse.c" module into separate modules for each
7708 group of parsed objects. Closes ticket 27924.
7709 - Move protover_rust.c to the same place protover.c was moved to.
7710 Closes ticket 27814.
7711 - Split directory.c into separate pieces for client, server, and
7712 common functionality. Closes ticket 26744.
7713 - Split the non-statistics-related parts from the rephist.c and
7714 geoip.c modules. Closes ticket 27892.
7715 - Split the router.c file into relay-only and shared components, to
7716 help with future modularization. Closes ticket 27864.
7717 - Divide the routerlist.c and dirserv.c modules into smaller parts.
7718 Closes ticket 27799.
7719 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
7720 longer needed. Closes ticket 26502.
7721 - Include paths to header files within Tor are now qualified by
7722 directory within the top-level src directory.
7723 - Many structures have been removed from the centralized "or.h"
7724 header, and moved into their own headers. This will allow us to
7725 reduce the number of places in the code that rely on each
7726 structure's contents and layout. Closes ticket 26383.
7727 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
7728 - Remove GetAdaptersAddresses_fn_t. The code that used it was
7729 removed as part of the 26481 refactor. Closes ticket 27467.
7730 - Rework Tor SOCKS server code to use Trunnel and benefit from
7731 autogenerated functions for parsing and generating SOCKS wire
7732 format. New implementation is cleaner, more maintainable and
7733 should be less prone to heartbleed-style vulnerabilities.
7734 Implements a significant fraction of ticket 3569.
7735 - Split sampled_guards_update_from_consensus() and
7736 select_entry_guard_for_circuit() into subfunctions. In
7737 entry_guards_update_primary() unite three smartlist enumerations
7738 into one and move smartlist comparison code out of the function.
7739 Closes ticket 21349.
7740 - Tor now assumes that you have standards-conformant stdint.h and
7741 inttypes.h headers when compiling. Closes ticket 26626.
7742 - Unify our bloom filter logic. Previously we had two copies of this
7743 code: one for routerlist filtering, and one for address set
7744 calculations. Closes ticket 26510.
7745 - Use the simpler strcmpstart() helper in
7746 rend_parse_v2_service_descriptor instead of strncmp(). Closes
7748 - Utility functions that can perform a DNS lookup are now wholly
7749 separated from those that can't, in separate headers and C
7750 modules. Closes ticket 26526.
7753 - In the tor-resolve(1) manpage, fix the reference to socks-
7754 extensions.txt by adding a web URL. Resolves ticket 27853.
7755 - Mention that we require Python to be 2.7 or newer for some
7756 integration tests that we ship with Tor. Resolves ticket 27677.
7757 - Copy paragraph and URL to Tor's code of conduct document from
7758 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
7759 - Remove old instructions from INSTALL document. Closes ticket 26588.
7760 - Warn users that they should not include MyFamily line(s) in their
7761 torrc when running Tor bridge. Closes ticket 26908.
7764 - Tor no longer supports building with the dmalloc library. For
7765 debugging memory issues, we suggest using gperftools or msan
7766 instead. Closes ticket 26426.
7767 - Tor no longer attempts to run on Windows environments without the
7768 GetAdaptersAddresses() function. This function has existed since
7769 Windows XP, which is itself already older than we support.
7770 - Remove Tor2web functionality for version 2 onion services. The
7771 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
7772 (This feature was never shipped in vanilla Tor and it was only
7773 possible to use this feature by building the support at compile
7774 time. Tor2webMode is not implemented for version 3 onion services.)
7775 Closes ticket 26367.
7778 - Increase logging and tag all log entries with timestamps in
7779 test_rebind.py. Provides diagnostics for issue 28229.
7781 o Code simplification and refactoring (shared random, dirauth):
7782 - Change many tor_assert() to use BUG() instead. The idea is to not
7783 crash a dirauth but rather scream loudly with a stacktrace and let
7784 it continue run. The shared random subsystem is very resilient and
7785 if anything wrong happens with it, at worst a non coherent value
7786 will be put in the vote and discarded by the other authorities.
7787 Closes ticket 19566.
7789 o Documentation (onion services):
7790 - Improve HSv3 client authorization by making some options more
7791 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
7792 - Document in the man page that changing ClientOnionAuthDir value or
7793 adding a new file in the directory will not work at runtime upon
7794 sending a HUP if Sandbox 1. Closes ticket 28128.
7795 - Note in the man page that the only real way to fully revoke an
7796 onion service v3 client authorization is by restarting the tor
7797 process. Closes ticket 28275.
7800 Changes in version 0.3.4.9 - 2018-11-02
7801 Tor 0.3.4.9 is the second stable release in its series; it backports
7802 numerous fixes, including a fix for a bandwidth management bug that
7803 was causing memory exhaustion on relays. Anyone running an earlier
7804 version of Tor 0.3.4.9 should upgrade.
7806 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
7807 - Fix compilation on ARM (and other less-used CPUs) when compiling
7808 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
7810 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
7811 - Make sure Tor bootstraps and works properly if only the
7812 ControlPort is set. Prior to this fix, Tor would only bootstrap
7813 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
7814 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
7816 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
7817 - When our write bandwidth limit is exhausted, stop writing on the
7818 connection. Previously, we had a typo in the code that would make
7819 us stop reading instead, leading to relay connections being stuck
7820 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
7823 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
7824 - Fix a use-after-free error that could be caused by passing Tor an
7825 impossible set of options that would fail during options_act().
7826 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
7828 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
7829 - Don't do a distcheck with --disable-module-dirauth in Travis.
7830 Implements ticket 27252.
7831 - Only run one online rust build in Travis, to reduce network
7832 errors. Skip offline rust builds on Travis for Linux gcc, because
7833 they're redundant. Implements ticket 27252.
7834 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
7835 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
7836 Linux with default settings, because all the non-default builds
7837 use gcc on Linux. Implements ticket 27252.
7839 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
7840 - Use the Travis Homebrew addon to install packages on macOS during
7841 Travis CI. The package list is the same, but the Homebrew addon
7842 does not do a `brew update` by default. Implements ticket 27738.
7844 o Minor features (geoip):
7845 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
7846 Country database. Closes ticket 27991.
7848 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
7849 - Fix an integer overflow bug in our optimized 32-bit millisecond-
7850 difference algorithm for 32-bit Apple platforms. Previously, it
7851 would overflow when calculating the difference between two times
7852 more than 47 days apart. Fixes part of bug 27139; bugfix
7854 - Improve the precision of our 32-bit millisecond difference
7855 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
7856 bugfix on 0.3.4.1-alpha.
7857 - Relax the tolerance on the mainloop/update_time_jumps test when
7858 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
7861 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
7862 - Avoid undefined behavior in an end-of-string check when parsing
7863 the BEGIN line in a directory object. Fixes bug 28202; bugfix
7866 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
7867 - Only install the necessary mingw packages during our appveyor
7868 builds. This change makes the build a little faster, and prevents
7869 a conflict with a preinstalled mingw openssl that appveyor now
7870 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
7872 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
7873 - Rewrite our assertion macros so that they no longer suppress the
7874 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
7876 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
7877 - Stop reinstalling identical packages in our Windows CI. Fixes bug
7878 27464; bugfix on 0.3.4.1-alpha.
7880 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
7881 - Log additional info when we get a relay that shares an ed25519 ID
7882 with a different relay, instead making a BUG() warning. Fixes bug
7883 27800; bugfix on 0.3.2.1-alpha.
7885 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
7886 - Avoid a double-close when shutting down a stalled directory
7887 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
7889 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
7890 - Fix a bug warning when closing an HTTP tunnel connection due to an
7891 HTTP request we couldn't handle. Fixes bug 26470; bugfix
7894 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
7895 - Ensure circuitmux queues are empty before scheduling or sending
7896 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
7898 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
7899 - When the onion service directory can't be created or has the wrong
7900 permissions, do not log a stack trace. Fixes bug 27335; bugfix
7903 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
7904 - Close all SOCKS request (for the same .onion) if the newly fetched
7905 descriptor is unusable. Before that, we would close only the first
7906 one leaving the other hanging and let to time out by themselves.
7907 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
7909 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
7910 - When selecting a v3 rendezvous point, don't only look at the
7911 protover, but also check whether the curve25519 onion key is
7912 present. This way we avoid picking a relay that supports the v3
7913 rendezvous but for which we don't have the microdescriptor. Fixes
7914 bug 27797; bugfix on 0.3.2.1-alpha.
7916 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
7917 - Reject protocol names containing bytes other than alphanumeric
7918 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
7921 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
7922 - Compute protover votes correctly in the rust version of the
7923 protover code. Previously, the protover rewrite in 24031 allowed
7924 repeated votes from the same voter for the same protocol version
7925 to be counted multiple times in protover_compute_vote(). Fixes bug
7926 27649; bugfix on 0.3.3.5-rc.
7927 - Reject protover names that contain invalid characters. Fixes bug
7928 27687; bugfix on 0.3.3.1-alpha.
7930 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
7931 - protover_all_supported() would attempt to allocate up to 16GB on
7932 some inputs, leading to a potential memory DoS. Fixes bug 27206;
7933 bugfix on 0.3.3.5-rc.
7935 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
7936 - Fix an API mismatch in the rust implementation of
7937 protover_compute_vote(). This bug could have caused crashes on any
7938 directory authorities running Tor with Rust (which we do not yet
7939 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
7941 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
7942 - Fix a potential null dereference in protover_all_supported(). Add
7943 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
7944 - Return a string that can be safely freed by C code, not one
7945 created by the rust allocator, in protover_all_supported(). Fixes
7946 bug 27740; bugfix on 0.3.3.1-alpha.
7948 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
7949 - If a unit test running in a subprocess exits abnormally or with a
7950 nonzero status code, treat the test as having failed, even if the
7951 test reported success. Without this fix, memory leaks don't cause
7952 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
7953 bugfix on 0.2.2.4-alpha.
7955 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
7956 - Make the hs_service tests use the same time source when creating
7957 the introduction point and when testing it. Now tests work better
7958 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
7961 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
7962 - Treat backtrace test failures as expected on BSD-derived systems
7963 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
7964 (FreeBSD failures have been treated as expected since 18204 in
7965 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
7968 Changes in version 0.2.9.17 - 2018-09-10
7969 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
7971 o Minor features (compatibility, backport from 0.3.4.8):
7972 - Tell OpenSSL to maintain backward compatibility with previous
7973 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
7974 ciphers are disabled by default. Closes ticket 27344.
7976 o Minor features (continuous integration, backport from 0.3.4.7-rc):
7977 - Enable macOS builds in our Travis CI configuration. Closes
7979 - Install libcap-dev and libseccomp2-dev so these optional
7980 dependencies get tested on Travis CI. Closes ticket 26560.
7981 - Run asciidoc during Travis CI. Implements ticket 27087.
7982 - Use ccache in our Travis CI configuration. Closes ticket 26952.
7984 o Minor features (geoip):
7985 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
7986 Country database. Closes ticket 27089.
7988 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
7989 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
7990 tell the compiler not to include the system malloc implementation.
7991 Fixes bug 20424; bugfix on 0.2.0.20-rc.
7993 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
7994 - Silence a spurious compiler warning on the GetAdaptersAddresses
7995 function pointer cast. This issue is already fixed by 26481 in
7996 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
7997 bugfix on 0.2.3.11-alpha.
7998 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
7999 supported, and always fails. Some compilers warn about the
8000 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
8003 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
8004 - Don't link or search for pthreads when building for Windows, even
8005 if we are using build environment (like mingw) that provides a
8006 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
8008 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
8009 - Skip a pair of unreliable key generation tests on Windows, until
8010 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
8011 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
8013 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
8014 - Pass the module flags to distcheck configure, and log the flags
8015 before running configure. (Backported to 0.2.9 and later as a
8016 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
8018 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
8019 - When a Travis build fails, and showing a log fails, keep trying to
8020 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
8021 - When we use echo in Travis, don't pass a --flag as the first
8022 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
8024 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
8025 - When voting for recommended versions, make sure that all of the
8026 versions are well-formed and parsable. Fixes bug 26485; bugfix
8029 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
8030 - Fix a bug in out sandboxing rules for the openat() syscall.
8031 Previously, no openat() call would be permitted, which would break
8032 filesystem operations on recent glibc versions. Fixes bug 25440;
8033 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
8035 o Minor bugfixes (onion services, backport from 0.3.4.8):
8036 - Silence a spurious compiler warning in
8037 rend_client_send_introduction(). Fixes bug 27463; bugfix
8040 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
8041 - Log a protocol warning when single onion services or Tor2web clients
8042 fail to authenticate direct connections to relays.
8043 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
8045 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
8046 - Disable core dumps in test_bt.sh, to avoid failures in "make
8047 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
8049 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
8050 - Before running make test-network-all, delete old logs and test
8051 result files, to avoid spurious failures. Fixes bug 27295; bugfix
8054 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
8055 - Our "tortls/cert_matches_key" unit test no longer relies on
8056 OpenSSL internals. Previously, it relied on unsupported OpenSSL
8057 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
8058 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
8060 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
8061 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
8062 27185; bugfix on 0.2.2.2-alpha.
8065 Changes in version 0.3.2.12 - 2018-09-10
8066 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
8068 o Minor features (compatibility, backport from 0.3.4.8):
8069 - Tell OpenSSL to maintain backward compatibility with previous
8070 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
8071 ciphers are disabled by default. Closes ticket 27344.
8073 o Minor features (continuous integration, backport from 0.3.4.7-rc):
8074 - Enable macOS builds in our Travis CI configuration. Closes
8076 - Install libcap-dev and libseccomp2-dev so these optional
8077 dependencies get tested on Travis CI. Closes ticket 26560.
8078 - Run asciidoc during Travis CI. Implements ticket 27087.
8079 - Use ccache in our Travis CI configuration. Closes ticket 26952.
8081 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
8082 - Use cargo cache in our Travis CI configuration. Closes
8085 o Minor features (controller, backport from 0.3.4.6-rc):
8086 - The control port now exposes the list of HTTPTunnelPorts and
8087 ExtOrPorts via GETINFO net/listeners/httptunnel and
8088 net/listeners/extor respectively. Closes ticket 26647.
8090 o Minor features (directory authorities, backport from 0.3.4.7-rc):
8091 - Authorities no longer vote to make the subprotocol version
8092 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
8093 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
8095 o Minor features (geoip):
8096 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
8097 Country database. Closes ticket 27089.
8099 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
8100 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
8101 tell the compiler not to include the system malloc implementation.
8102 Fixes bug 20424; bugfix on 0.2.0.20-rc.
8103 - Don't try to use a pragma to temporarily disable the
8104 -Wunused-const-variable warning if the compiler doesn't support
8105 it. Fixes bug 26785; bugfix on 0.3.2.11.
8107 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
8108 - Silence a spurious compiler warning on the GetAdaptersAddresses
8109 function pointer cast. This issue is already fixed by 26481 in
8110 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
8111 bugfix on 0.2.3.11-alpha.
8112 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
8113 supported, and always fails. Some compilers warn about the
8114 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
8117 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
8118 - Don't link or search for pthreads when building for Windows, even
8119 if we are using build environment (like mingw) that provides a
8120 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
8122 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
8123 - Skip a pair of unreliable key generation tests on Windows, until
8124 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
8125 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
8127 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
8128 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
8129 - Pass the module flags to distcheck configure, and log the flags
8130 before running configure. (Backported to 0.2.9 and later as a
8131 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
8133 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
8134 - When a Travis build fails, and showing a log fails, keep trying to
8135 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
8136 - When we use echo in Travis, don't pass a --flag as the first
8137 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
8139 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
8140 - When voting for recommended versions, make sure that all of the
8141 versions are well-formed and parsable. Fixes bug 26485; bugfix
8144 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
8145 - Fix a bug in out sandboxing rules for the openat() syscall.
8146 Previously, no openat() call would be permitted, which would break
8147 filesystem operations on recent glibc versions. Fixes bug 25440;
8148 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
8150 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
8151 - Improve the log message when connection initiators fail to
8152 authenticate direct connections to relays. Fixes bug 26927; bugfix
8155 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
8156 - Fix bug that causes services to not ever rotate their descriptors
8157 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
8160 o Minor bugfixes (onion services, backport from 0.3.4.8):
8161 - Silence a spurious compiler warning in
8162 rend_client_send_introduction(). Fixes bug 27463; bugfix
8165 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
8166 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
8168 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
8169 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
8170 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
8171 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
8173 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
8174 - Log a protocol warning when single onion services or Tor2web clients
8175 fail to authenticate direct connections to relays.
8176 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
8178 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
8179 - Disable core dumps in test_bt.sh, to avoid failures in "make
8180 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
8182 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
8183 - When running make test-network-all, use the mixed+hs-v2 network.
8184 (A previous fix to chutney removed v3 onion services from the
8185 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
8186 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
8187 - Before running make test-network-all, delete old logs and test
8188 result files, to avoid spurious failures. Fixes bug 27295; bugfix
8191 o Minor bugfixes (testing, openssl compatibility):
8192 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
8193 internals. Previously, it relied on unsupported OpenSSL behavior in
8194 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
8195 bugfix on 0.2.5.1-alpha.
8197 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
8198 - Our "tortls/cert_matches_key" unit test no longer relies on
8199 OpenSSL internals. Previously, it relied on unsupported OpenSSL
8200 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
8201 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
8203 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
8204 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
8205 27185; bugfix on 0.2.2.2-alpha.
8208 Changes in version 0.3.3.10 - 2018-09-10
8209 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
8211 o Minor features (bug workaround, backport from 0.3.4.7-rc):
8212 - Compile correctly on systems that provide the C11 stdatomic.h
8213 header, but where C11 atomic functions don't actually compile.
8214 Closes ticket 26779; workaround for Debian issue 903709.
8216 o Minor features (compatibility, backport from 0.3.4.8):
8217 - Tell OpenSSL to maintain backward compatibility with previous
8218 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
8219 ciphers are disabled by default. Closes ticket 27344.
8221 o Minor features (continuous integration, backport from 0.3.4.7-rc):
8222 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
8223 - Enable macOS builds in our Travis CI configuration. Closes
8225 - Install libcap-dev and libseccomp2-dev so these optional
8226 dependencies get tested on Travis CI. Closes ticket 26560.
8227 - Run asciidoc during Travis CI. Implements ticket 27087.
8228 - Use ccache in our Travis CI configuration. Closes ticket 26952.
8230 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
8231 - Use cargo cache in our Travis CI configuration. Closes
8234 o Minor features (controller, backport from 0.3.4.6-rc):
8235 - The control port now exposes the list of HTTPTunnelPorts and
8236 ExtOrPorts via GETINFO net/listeners/httptunnel and
8237 net/listeners/extor respectively. Closes ticket 26647.
8239 o Minor features (directory authorities, backport from 0.3.4.7-rc):
8240 - Authorities no longer vote to make the subprotocol version
8241 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
8242 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
8244 o Minor features (geoip):
8245 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
8246 Country database. Closes ticket 27089.
8248 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
8249 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
8250 tell the compiler not to include the system malloc implementation.
8251 Fixes bug 20424; bugfix on 0.2.0.20-rc.
8252 - Don't try to use a pragma to temporarily disable the
8253 -Wunused-const-variable warning if the compiler doesn't support
8254 it. Fixes bug 26785; bugfix on 0.3.2.11.
8256 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
8257 - Silence a spurious compiler warning on the GetAdaptersAddresses
8258 function pointer cast. This issue is already fixed by 26481 in
8259 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
8260 bugfix on 0.2.3.11-alpha.
8261 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
8262 supported, and always fails. Some compilers warn about the
8263 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
8266 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
8267 - Don't link or search for pthreads when building for Windows, even
8268 if we are using build environment (like mingw) that provides a
8269 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
8271 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
8272 - Skip a pair of unreliable key generation tests on Windows, until
8273 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
8274 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
8276 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
8277 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
8278 - Pass the module flags to distcheck configure, and log the flags
8279 before running configure. (Backported to 0.2.9 and later as a
8280 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
8282 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
8283 - When a Travis build fails, and showing a log fails, keep trying to
8284 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
8285 - When we use echo in Travis, don't pass a --flag as the first
8286 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
8288 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
8289 - When voting for recommended versions, make sure that all of the
8290 versions are well-formed and parsable. Fixes bug 26485; bugfix
8293 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
8294 - Always call tor_free_all() when leaving tor_run_main(). When we
8295 did not, restarting tor in-process would cause an assertion
8296 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
8298 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
8299 - Fix a bug in our sandboxing rules for the openat() syscall.
8300 Previously, no openat() call would be permitted, which would break
8301 filesystem operations on recent glibc versions. Fixes bug 25440;
8302 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
8304 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
8305 - Improve the log message when connection initiators fail to
8306 authenticate direct connections to relays. Fixes bug 26927; bugfix
8309 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
8310 - Fix bug that causes services to not ever rotate their descriptors
8311 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
8314 o Minor bugfixes (onion services, backport from 0.3.4.8):
8315 - Silence a spurious compiler warning in
8316 rend_client_send_introduction(). Fixes bug 27463; bugfix
8319 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
8320 - Work around two different bugs in the OS X 10.10 and later SDKs
8321 that would prevent us from successfully targeting earlier versions
8322 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
8324 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
8325 - Fix compilation of the unit tests on GNU/Hurd, which does not
8326 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
8329 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
8330 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
8332 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
8333 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
8334 - Protover parsing was accepting the presence of whitespace in
8335 version strings, which the C implementation would choke on, e.g.
8336 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
8337 - Protover parsing was ignoring a 2nd hyphen and everything after
8338 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
8340 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
8341 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
8342 - cd to ${abs_top_builddir}/src/rust before running cargo in
8343 src/test/test_rust.sh. This makes the working directory consistent
8344 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
8346 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
8347 - Log a protocol warning when single onion services or Tor2web clients
8348 fail to authenticate direct connections to relays.
8349 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
8351 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
8352 - Disable core dumps in test_bt.sh, to avoid failures in "make
8353 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
8355 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
8356 - When running make test-network-all, use the mixed+hs-v2 network.
8357 (A previous fix to chutney removed v3 onion services from the
8358 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
8359 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
8360 - Before running make test-network-all, delete old logs and test
8361 result files, to avoid spurious failures. Fixes bug 27295; bugfix
8364 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
8365 - Our "tortls/cert_matches_key" unit test no longer relies on
8366 OpenSSL internals. Previously, it relied on unsupported OpenSSL
8367 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
8368 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
8370 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
8371 - Stop sending ed25519 link specifiers in v3 onion service introduce
8372 cells and descriptors, when the rendezvous or introduction point
8373 doesn't support ed25519 link authentication. Fixes bug 26627;
8374 bugfix on 0.3.2.4-alpha.
8376 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
8377 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
8378 27185; bugfix on 0.2.2.2-alpha.
8381 Changes in version 0.3.4.8 - 2018-09-10
8382 Tor 0.3.4.8 is the first stable release in its series; it includes
8383 compilation and portability fixes.
8385 The Tor 0.3.4 series includes improvements for running Tor in
8386 low-power and embedded environments, which should help performance in
8387 general. We've begun work on better modularity, and included preliminary
8388 changes on the directory authority side to accommodate a new bandwidth
8389 measurement system. We've also integrated more continuous-integration
8390 systems into our development process, and made corresponding changes to
8391 Tor's testing infrastructure. Finally, we've continued to refine
8392 our anti-denial-of-service code.
8394 Below are the changes since 0.3.3.9. For a list of only the changes
8395 since 0.3.4.7-rc, see the ChangeLog file.
8397 o New system requirements:
8398 - Tor no longer tries to support old operating systems without
8399 mmap() or some local equivalent. Apparently, compilation on such
8400 systems has been broken for some time, without anybody noticing or
8401 complaining. Closes ticket 25398.
8403 o Major features (directory authority, modularization):
8404 - The directory authority subsystem has been modularized. The code
8405 is now located in src/or/dirauth/, and is compiled in by default.
8406 To disable the module, the configure option
8407 --disable-module-dirauth has been added. This module may be
8408 disabled by default in some future release. Closes ticket 25610.
8410 o Major features (main loop, CPU usage):
8411 - When Tor is disabled (via DisableNetwork or via hibernation), it
8412 no longer needs to run any per-second events. This change should
8413 make it easier for mobile applications to disable Tor while the
8414 device is sleeping, or Tor is not running. Closes ticket 26063.
8415 - Tor no longer enables all of its periodic events by default.
8416 Previously, Tor would enable all possible main loop events,
8417 regardless of whether it needed them. Furthermore, many of these
8418 events are now disabled when Tor is hibernating or DisableNetwork
8419 is set. This is a big step towards reducing client CPU usage by
8420 reducing the amount of wake-ups the daemon does. Closes tickets
8422 - The bandwidth-limitation logic has been refactored so that
8423 bandwidth calculations are performed on-demand, rather than every
8424 TokenBucketRefillInterval milliseconds. This change should improve
8425 the granularity of our bandwidth calculations, and limit the
8426 number of times that the Tor process needs to wake up when it is
8427 idle. Closes ticket 25373.
8428 - Move responsibility for many operations from a once-per-second
8429 callback to a callback that is only scheduled as needed. Moving
8430 this functionality has allowed us to disable the callback when
8431 Tor's network is disabled. Once enough items are removed from our
8432 once-per-second callback, we can eliminate it entirely to conserve
8433 CPU when idle. The functionality removed includes: closing
8434 connections, circuits, and channels (ticket 25932); consensus
8435 voting (25937); flushing log callbacks (25951); honoring delayed
8436 SIGNEWNYM requests (25949); rescanning the consensus cache
8437 (25931); saving the state file to disk (25948); warning relay
8438 operators about unreachable ports (25952); and keeping track of
8439 Tor's uptime (26009).
8441 o Minor features (accounting):
8442 - When Tor becomes dormant, it now uses a scheduled event to wake up
8443 at the right time. Previously, we would use the per-second timer
8444 to check whether to wake up, but we no longer have any per-second
8445 timers enabled when the network is disabled. Closes ticket 26064.
8447 o Minor features (bug workaround):
8448 - Compile correctly on systems that provide the C11 stdatomic.h
8449 header, but where C11 atomic functions don't actually compile.
8450 Closes ticket 26779; workaround for Debian issue 903709.
8452 o Minor features (code quality):
8453 - Add optional spell-checking for the Tor codebase, using the
8454 "misspell" program. To use this feature, run "make check-typos".
8455 Closes ticket 25024.
8457 o Minor features (compatibility):
8458 - Tell OpenSSL to maintain backward compatibility with previous
8459 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
8460 ciphers are disabled by default. Closes ticket 27344.
8461 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
8462 the no-deprecated option, and builds correctly with them. Closes
8463 tickets 19429, 19981, and 25353.
8465 o Minor features (compilation):
8466 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
8467 tell the compiler not to include the system malloc implementation.
8468 Fixes bug 20424; bugfix on 0.2.0.20-rc.
8469 - Don't try to use a pragma to temporarily disable the
8470 -Wunused-const-variable warning if the compiler doesn't support
8471 it. Fixes bug 26785; bugfix on 0.3.2.11.
8472 - When building Tor, prefer to use Python 3 over Python 2, and more
8473 recent (contemplated) versions over older ones. Closes
8476 o Minor features (compression, zstd):
8477 - When running with zstd, Tor now considers using advanced functions
8478 that the zstd maintainers have labeled as potentially unstable. To
8479 prevent breakage, Tor will only use this functionality when the
8480 runtime version of the zstd library matches the version with which
8481 Tor was compiled. Closes ticket 25162.
8483 o Minor features (configuration):
8484 - The "DownloadSchedule" options have been renamed to end with
8485 "DownloadInitialDelay". The old names are still allowed, but will
8486 produce a warning. Comma-separated lists are still permitted for
8487 these options, but all values after the first are ignored (as they
8488 have been since 0.2.9). Closes ticket 23354.
8490 o Minor features (continuous integration):
8491 - Log the compiler path and version during Appveyor builds.
8492 Implements ticket 27449.
8493 - Show config.log and test-suite.log after failed Appveyor builds.
8494 Also upload the zipped full logs as a build artifact. Implements
8496 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
8497 - Enable macOS builds in our Travis CI configuration. Closes
8499 - Install libcap-dev and libseccomp2-dev so these optional
8500 dependencies get tested on Travis CI. Closes ticket 26560.
8501 - Only post Appveyor IRC notifications when the build fails.
8502 Implements ticket 27275.
8503 - Run asciidoc during Travis CI. Implements ticket 27087.
8504 - Use ccache in our Travis CI configuration. Closes ticket 26952.
8505 - Add the necessary configuration files for continuous integration
8506 testing on Windows, via the Appveyor platform. Closes ticket
8507 25549. Patches from Marcin Cieślak and Isis Lovecruft.
8509 o Minor features (continuous integration, rust):
8510 - Use cargo cache in our Travis CI configuration. Closes
8513 o Minor features (control port):
8514 - Introduce GETINFO "current-time/{local,utc}" to return the local
8515 and UTC times respectively in ISO format. This helps a controller
8516 like Tor Browser detect a time-related error. Closes ticket 25511.
8517 Patch by Neel Chauhan.
8518 - Introduce new fields to the CIRC_BW event. There are two new
8519 fields in each of the read and written directions. The DELIVERED
8520 fields report the total valid data on the circuit, as measured by
8521 the payload sizes of verified and error-checked relay command
8522 cells. The OVERHEAD fields report the total unused bytes in each
8523 of these cells. Closes ticket 25903.
8525 o Minor features (controller):
8526 - The control port now exposes the list of HTTPTunnelPorts and
8527 ExtOrPorts via GETINFO net/listeners/httptunnel and
8528 net/listeners/extor respectively. Closes ticket 26647.
8530 o Minor features (directory authorities):
8531 - Stop warning about incomplete bw lines before the first complete
8532 bw line has been found, so that additional header lines can be
8533 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
8534 - Authorities no longer vote to make the subprotocol version
8535 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
8536 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
8538 o Minor features (directory authority):
8539 - Directory authorities now open their key-pinning files as O_SYNC,
8540 to limit their chances of accidentally writing partial lines.
8541 Closes ticket 23909.
8543 o Minor features (directory authority, forward compatibility):
8544 - Make the lines of the measured bandwidth file able to contain
8545 their entries in any order. Previously, the node_id entry needed
8546 to come first. Closes ticket 26004.
8548 o Minor features (entry guards):
8549 - Introduce a new torrc option NumPrimaryGuards for controlling the
8550 number of primary guards. Closes ticket 25843.
8552 o Minor features (geoip):
8553 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
8554 Country database. Closes ticket 27089.
8556 o Minor features (performance):
8557 - Avoid a needless call to malloc() when processing an incoming
8558 relay cell. Closes ticket 24914.
8559 - Make our timing-wheel code run a tiny bit faster on 32-bit
8560 platforms, by preferring 32-bit math to 64-bit. Closes
8562 - Avoid a needless malloc()/free() pair every time we handle an ntor
8563 handshake. Closes ticket 25150.
8565 o Minor features (Rust, portability):
8566 - Rust cross-compilation is now supported. Closes ticket 25895.
8568 o Minor features (testing):
8569 - Add a unit test for voting_schedule_get_start_of_next_interval().
8570 Closes ticket 26014, and helps make unit test coverage
8572 - A new unittests module specifically for testing the functions in
8573 the (new-ish) bridges.c module has been created with new
8574 unittests, raising the code coverage percentages. Closes 25425.
8575 - We now have improved testing for addressmap_get_virtual_address()
8576 function. This should improve our test coverage, and make our test
8577 coverage more deterministic. Closes ticket 25993.
8579 o Minor features (timekeeping, circuit scheduling):
8580 - When keeping track of how busy each circuit have been recently on
8581 a given connection, use coarse-grained monotonic timers rather
8582 than gettimeofday(). This change should marginally increase
8583 accuracy and performance. Implements part of ticket 25927.
8585 o Minor features (unit tests):
8586 - Test complete bandwidth measurements files, and test that
8587 incomplete bandwidth lines only give warnings when the end of the
8588 header has not been detected. Fixes bug 25947; bugfix
8591 o Minor bugfixes (bandwidth management):
8592 - Consider ourselves "low on write bandwidth" if we have exhausted
8593 our write bandwidth some time in the last second. This was the
8594 documented behavior before, but the actual behavior was to change
8595 this value every TokenBucketRefillInterval. Fixes bug 25828;
8596 bugfix on 0.2.3.5-alpha.
8598 o Minor bugfixes (C correctness):
8599 - Add a missing lock acquisition in the shutdown code of the control
8600 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
8601 Coverity; this is CID 1433643.
8603 o Minor bugfixes (code style):
8604 - Fixed multiple includes of transports.h in src/or/connection.c
8605 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
8606 - Remove the unused variable n_possible from the function
8607 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
8609 o Minor bugfixes (compilation):
8610 - Silence a spurious compiler warning on the GetAdaptersAddresses
8611 function pointer cast. This issue is already fixed by 26481 in
8612 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
8613 bugfix on 0.2.3.11-alpha.
8614 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
8615 supported, and always fails. Some compilers warn about the
8616 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
8618 - Fix a compilation warning on some versions of GCC when building
8619 code that calls routerinfo_get_my_routerinfo() twice, assuming
8620 that the second call will succeed if the first one did. Fixes bug
8621 26269; bugfix on 0.2.8.2-alpha.
8622 - Refrain from compiling unit testing related object files when
8623 --disable-unittests is set to configure script. Fixes bug 24891;
8624 bugfix on 0.2.5.1-alpha.
8625 - The --enable-fatal-warnings flag now affects Rust code as well.
8626 Closes ticket 26245.
8627 - Avoid a compiler warning when casting the return value of
8628 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
8629 26283; bugfix on 0.2.4.10-alpha.
8631 o Minor bugfixes (compilation, windows):
8632 - Don't link or search for pthreads when building for Windows, even
8633 if we are using build environment (like mingw) that provides a
8634 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
8636 o Minor bugfixes (continuous integration):
8637 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
8638 - Skip a pair of unreliable key generation tests on Windows, until
8639 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
8640 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
8642 o Minor bugfixes (control port):
8643 - Respond with more human-readable error messages to GETINFO exit-
8644 policy/* requests. Also, let controller know if an error is
8645 transient (response code 551) or not (response code 552). Fixes
8646 bug 25852; bugfix on 0.2.8.1-alpha.
8647 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
8648 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
8649 on 0.3.3.1-alpha. Patch by "akwizgran".
8650 - Make CIRC_BW event reflect the total of all data sent on a
8651 circuit, including padding and dropped cells. Also fix a mis-
8652 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
8653 bugfix on 0.2.5.2-alpha.
8655 o Minor bugfixes (correctness, flow control):
8656 - Upon receiving a stream-level SENDME cell, verify that our window
8657 has not grown too large. Fixes bug 26214; bugfix on svn
8660 o Minor bugfixes (directory authority):
8661 - When voting for recommended versions, make sure that all of the
8662 versions are well-formed and parsable. Fixes bug 26485; bugfix
8665 o Minor bugfixes (directory client):
8666 - When unverified-consensus is verified, rename it to cached-
8667 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
8668 - Fixed launching a certificate fetch always during the scheduled
8669 periodic consensus fetch by fetching only in those cases when
8670 consensus are waiting for certs. Fixes bug 24740; bugfix
8673 o Minor bugfixes (error reporting):
8674 - Improve tolerance for directory authorities with skewed clocks.
8675 Previously, an authority with a clock more than 60 seconds ahead
8676 could cause a client with a correct clock to warn that the
8677 client's clock was behind. Now the clocks of a majority of
8678 directory authorities have to be ahead of the client before this
8679 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
8681 o Minor bugfixes (in-process restart):
8682 - Always call tor_free_all() when leaving tor_run_main(). When we
8683 did not, restarting tor in-process would cause an assertion
8684 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
8686 o Minor bugfixes (Linux seccomp2 sandbox):
8687 - Fix a bug in our sandboxing rules for the openat() syscall.
8688 Previously, no openat() call would be permitted, which would break
8689 filesystem operations on recent glibc versions. Fixes bug 25440;
8690 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
8692 o Minor bugfixes (logging):
8693 - Improve the log message when connection initiators fail to
8694 authenticate direct connections to relays. Fixes bug 26927; bugfix
8697 o Minor bugfixes (onion services):
8698 - Silence a spurious compiler warning in
8699 rend_client_send_introduction(). Fixes bug 27463; bugfix
8701 - Fix bug that causes services to not ever rotate their descriptors
8702 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
8704 - Recompute some consensus information after detecting a clock jump,
8705 or after transitioning from a non-live consensus to a live
8706 consensus. We do this to avoid having an outdated state, and
8707 miscalculating the index for next-generation onion services. Fixes
8708 bug 24977; bugfix on 0.3.2.1-alpha.
8710 o Minor bugfixes (portability):
8711 - Fix compilation of the unit tests on GNU/Hurd, which does not
8712 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
8714 - Work around two different bugs in the OS X 10.10 and later SDKs
8715 that would prevent us from successfully targeting earlier versions
8716 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
8717 - Do not align mmap length, as it is not required by POSIX, and the
8718 getpagesize function is deprecated. Fixes bug 25399; bugfix
8721 o Minor bugfixes (portability, FreeBSD):
8722 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
8723 does not stringify on FreeBSD, so we switch to tor_asprintf().
8724 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
8726 o Minor bugfixes (relay statistics):
8727 - When a relay is collecting internal statistics about how many
8728 create cell requests it has seen of each type, accurately count
8729 the requests from relays that temporarily fall out of the
8730 consensus. (To be extra conservative, we were already ignoring
8731 requests from clients in our counts, and we continue ignoring them
8732 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
8734 o Minor bugfixes (rust):
8735 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
8737 - Protover parsing was accepting the presence of whitespace in
8738 version strings, which the C implementation would choke on, e.g.
8739 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
8740 - Protover parsing was ignoring a 2nd hyphen and everything after
8741 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
8743 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
8744 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
8745 - cd to ${abs_top_builddir}/src/rust before running cargo in
8746 src/test/test_rust.sh. This makes the working directory consistent
8747 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
8749 o Minor bugfixes (single onion services, Tor2web):
8750 - Log a protocol warning when single onion services or Tor2web
8751 clients fail to authenticate direct connections to relays. Fixes
8752 bug 26924; bugfix on 0.2.9.1-alpha.
8754 o Minor bugfixes (test coverage tools):
8755 - Update our "cov-diff" script to handle output from the latest
8756 version of gcov, and to remove extraneous timestamp information
8757 from its output. Fixes bugs 26101 and 26102; bugfix
8760 o Minor bugfixes (testing):
8761 - Disable core dumps in test_bt.sh, to avoid failures in "make
8762 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
8763 - When testing workqueue event-cancellation, make sure that we
8764 actually cancel an event, and that cancel each event with equal
8765 probability. (It was previously possible, though extremely
8766 unlikely, for our event-canceling test not to cancel any events.)
8767 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
8768 - Repeat part of the test in test_client_pick_intro() a number of
8769 times, to give it consistent coverage. Fixes bug 25996; bugfix
8771 - Remove randomness from the hs_common/responsible_hsdirs test, so
8772 that it always takes the same path through the function it tests.
8773 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
8774 - Change the behavior of the "channel/outbound" test so that it
8775 never causes a 10-second rollover for the EWMA circuitmux code.
8776 Previously, this behavior would happen randomly, and result in
8777 fluctuating test coverage. Fixes bug 25994; bugfix
8779 - Use X509_new() to allocate certificates that will be freed later
8780 with X509_free(). Previously, some parts of the unit tests had
8781 used tor_malloc_zero(), which is incorrect, and which caused test
8782 failures on Windows when they were built with extra hardening.
8783 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
8785 - While running the circuit_timeout test, fix the PRNG to a
8786 deterministic AES stream, so that the test coverage from this test
8787 will itself be deterministic. Fixes bug 25995; bugfix
8790 o Minor bugfixes (testing, bootstrap):
8791 - When calculating bootstrap progress, check exit policies and the
8792 exit flag. Previously, Tor would only check the exit flag, which
8793 caused race conditions in small and fast networks like chutney.
8794 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
8796 o Minor bugfixes (testing, chutney):
8797 - When running make test-network-all, use the mixed+hs-v2 network.
8798 (A previous fix to chutney removed v3 onion services from the
8799 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
8800 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
8801 - Before running make test-network-all, delete old logs and test
8802 result files, to avoid spurious failures. Fixes bug 27295; bugfix
8805 o Minor bugfixes (testing, openssl compatibility):
8806 - Our "tortls/cert_matches_key" unit test no longer relies on
8807 OpenSSL internals. Previously, it relied on unsupported OpenSSL
8808 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
8809 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
8811 o Minor bugfixes (v3 onion services):
8812 - Stop sending ed25519 link specifiers in v3 onion service introduce
8813 cells and descriptors, when the rendezvous or introduction point
8814 doesn't support ed25519 link authentication. Fixes bug 26627;
8815 bugfix on 0.3.2.4-alpha.
8817 o Minor bugfixes (vanguards):
8818 - Allow the last hop in a vanguard circuit to be the same as our
8819 first, to prevent the adversary from influencing guard node choice
8820 by choice of last hop. Also prevent the creation of A - B - A
8821 paths, or A - A paths, which are forbidden by relays. Fixes bug
8822 25870; bugfix on 0.3.3.1-alpha.
8824 o Minor bugfixes (Windows, compilation):
8825 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
8826 27185; bugfix on 0.2.2.2-alpha.
8828 o Code simplification and refactoring:
8829 - Remove duplicate code in parse_{c,s}method_line and bootstrap
8830 their functionalities into a single function. Fixes bug 6236;
8831 bugfix on 0.2.3.6-alpha.
8832 - We remove the PortForwarding and PortForwardingHelper options,
8833 related functions, and the port_forwarding tests. These options
8834 were used by the now-deprecated Vidalia to help ordinary users
8835 become Tor relays or bridges. Closes ticket 25409. Patch by
8837 - In order to make the OR and dir checking function in router.c less
8838 confusing we renamed some functions and
8839 consider_testing_reachability() has been split into
8840 router_should_check_reachability() and
8841 router_do_reachability_checks(). Also we improved the documentation
8842 in some functions. Closes ticket 18918.
8843 - Initial work to isolate Libevent usage to a handful of modules in
8844 our codebase, to simplify our call structure, and so that we can
8845 more easily change event loops in the future if needed. Closes
8847 - Introduce a function to call getsockname() and return tor_addr_t,
8848 to save a little complexity throughout the codebase. Closes
8850 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
8851 as hsdir_index is always present. Also, we move hsdir_index_t into
8852 or.h. Closes ticket 23094. Patch by Neel Chauhan.
8853 - Merge functions used for describing nodes and suppress the
8854 functions that do not allocate memory for the output buffer
8855 string. NODE_DESC_BUF_LEN constant and format_node_description()
8856 function cannot be used externally from router.c module anymore.
8857 Closes ticket 25432. Patch by valentecaio.
8858 - Our main loop has been simplified so that all important operations
8859 happen inside events. Previously, some operations had to happen
8860 outside the event loop, to prevent infinite sequences of event
8861 activations. Closes ticket 25374.
8862 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
8863 it in register_intro_circ() and service_intro_point_new(). This
8864 prevents the digest from being re-calculated each time. Closes
8865 ticket 23107. Patch by Neel Chauhan.
8866 - Refactor token-bucket implementations to use a common backend.
8867 Closes ticket 25766.
8868 - Remove extern declaration of stats_n_seconds_working variable from
8869 main, protecting its accesses with get_uptime() and reset_uptime()
8870 functions. Closes ticket 25081, patch by “valentecaio”.
8871 - Remove our previous logic for "cached gettimeofday()" -- our
8872 coarse monotonic timers are fast enough for this purpose, and far
8873 less error-prone. Implements part of ticket 25927.
8874 - Remove the return value for fascist_firewall_choose_address_base(),
8875 and sister functions such as fascist_firewall_choose_address_node()
8876 and fascist_firewall_choose_address_rs(). Also, while we're here,
8877 initialize the ap argument as leaving it uninitialized can pose a
8878 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
8879 - Rename two fields of connection_t struct. timestamp_lastwritten is
8880 renamed to timestamp_last_write_allowed and timestamp_lastread is
8881 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
8883 - Since Tor requires C99, remove our old workaround code for libc
8884 implementations where free(NULL) doesn't work. Closes ticket 24484.
8885 - Use our standard rate-limiting code to deal with excessive
8886 libevent failures, rather than the hand-rolled logic we had
8887 before. Closes ticket 26016.
8888 - We remove the return value of node_get_prim_orport() and
8889 node_get_prim_dirport(), and introduce node_get_prim_orport() in
8890 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
8891 check for a null address. Closes ticket 23873. Patch by
8893 - We switch to should_record_bridge_info() in
8894 geoip_note_client_seen() and options_need_geoip_info() instead of
8895 accessing the configuration values directly. Fixes bug 25290;
8896 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
8898 o Deprecated features:
8899 - As we are not recommending 0.2.5 anymore, we require relays that
8900 once had an ed25519 key associated with their RSA key to always
8901 have that key, instead of allowing them to drop back to a version
8902 that didn't support ed25519. This means they need to use a new RSA
8903 key if they want to downgrade to an older version of tor without
8904 ed25519. Closes ticket 20522.
8907 - Directory authorities will no longer support voting according to
8908 any consensus method before consensus method 25. This keeps
8909 authorities compatible with all authorities running 0.2.9.8 and
8910 later, and does not break any clients or relays. Implements ticket
8911 24378 and proposal 290.
8912 - The PortForwarding and PortForwardingHelper features have been
8913 removed. The reasoning is, given that implementations of NAT
8914 traversal protocols within common consumer grade routers are
8915 frequently buggy, and that the target audience for a NAT punching
8916 feature is a perhaps less-technically-inclined relay operator,
8917 when the helper fails to setup traversal the problems are usually
8918 deep, ugly, and very router specific, making them horrendously
8919 impossible for technical support to reliable assist with, and thus
8920 resulting in frustration all around. Unfortunately, relay
8921 operators who would like to run relays behind NATs will need to
8922 become more familiar with the port forwarding configurations on
8923 their local router. Closes 25409.
8924 - The TestingEnableTbEmptyEvent option has been removed. It was used
8925 in testing simulations to measure how often connection buckets
8926 were emptied, in order to improve our scheduling, but it has not
8927 been actively used in years. Closes ticket 25760.
8928 - The old "round-robin" circuit multiplexer (circuitmux)
8929 implementation has been removed, along with a fairly large set of
8930 code that existed to support it. It has not been the default
8931 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
8932 but it still required an unreasonable amount of memory and CPU.
8933 Closes ticket 25268.
8936 Changes in version 0.3.3.9 - 2018-07-13
8937 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
8938 bridge relays should upgrade.
8940 o Directory authority changes:
8941 - The "Bifroest" bridge authority has been retired; the new bridge
8942 authority is "Serge", and it is operated by George from the
8943 TorBSD project. Closes ticket 26771.
8946 Changes in version 0.3.2.11 - 2018-07-13
8947 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
8948 bridge relays should upgrade. We also take this opportunity to backport
8951 o Directory authority changes:
8952 - The "Bifroest" bridge authority has been retired; the new bridge
8953 authority is "Serge", and it is operated by George from the
8954 TorBSD project. Closes ticket 26771.
8956 o Directory authority changes (backport from 0.3.3.7):
8957 - Add an IPv6 address for the "dannenberg" directory authority.
8958 Closes ticket 26343.
8960 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
8961 - When directory authorities read a zero-byte bandwidth file, they
8962 would previously log a warning with the contents of an
8963 uninitialised buffer. They now log a warning about the empty file
8964 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
8966 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
8967 - Correctly detect when onion services get disabled after HUP. Fixes
8968 bug 25761; bugfix on 0.3.2.1.
8970 o Minor features (sandbox, backport from 0.3.3.4-alpha):
8971 - Explicitly permit the poll() system call when the Linux
8972 seccomp2-based sandbox is enabled: apparently, some versions of
8973 libc use poll() when calling getpwnam(). Closes ticket 25313.
8975 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
8976 - Update the Travis CI configuration to use the stable Rust channel,
8977 now that we have decided to require that. Closes ticket 25714.
8979 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
8980 - Our .travis.yml configuration now includes support for testing the
8981 results of "make distcheck". (It's not uncommon for "make check"
8982 to pass but "make distcheck" to fail.) Closes ticket 25814.
8983 - Our Travis CI configuration now integrates with the Coveralls
8984 coverage analysis tool. Closes ticket 25818.
8986 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
8987 - Add several checks to detect whether Tor relays are uploading
8988 their descriptors without specifying why they regenerated them.
8989 Diagnostic for ticket 25686.
8991 o Minor features (compilation, backport from 0.3.4.4-rc):
8992 - When building Tor, prefer to use Python 3 over Python 2, and more
8993 recent (contemplated) versions over older ones. Closes
8996 o Minor features (geoip):
8997 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
8998 Country database. Closes ticket 26674.
9000 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
9001 - Upon receiving a malformed connected cell, stop processing the
9002 cell immediately. Previously we would mark the connection for
9003 close, but continue processing the cell as if the connection were
9004 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
9006 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
9007 - Allow the nanosleep() system call, which glibc uses to implement
9008 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
9010 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
9011 - When running the hs_ntor_ref.py test, make sure only to pass
9012 strings (rather than "bytes" objects) to the Python subprocess
9013 module. Python 3 on Windows seems to require this. Fixes bug
9014 26535; bugfix on 0.3.1.1-alpha.
9015 - When running the ntor_ref.py test, make sure only to pass strings
9016 (rather than "bytes" objects) to the Python subprocess module.
9017 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
9020 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
9021 - Work around a change in OpenSSL 1.1.1 where return values that
9022 would previously indicate "no password" now indicate an empty
9023 password. Without this workaround, Tor instances running with
9024 OpenSSL 1.1.1 would accept descriptors that other Tor instances
9025 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
9027 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
9028 - Document that the PerConnBW{Rate,Burst} options will fall back to
9029 their corresponding consensus parameters only if those parameters
9030 are set. Previously we had claimed that these values would always
9031 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
9033 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
9034 - Fix a compilation warning on some versions of GCC when building
9035 code that calls routerinfo_get_my_routerinfo() twice, assuming
9036 that the second call will succeed if the first one did. Fixes bug
9037 26269; bugfix on 0.2.8.2-alpha.
9039 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
9040 - Don't consider Tor running as a client if the ControlPort is open,
9041 but no actual client ports are open. Fixes bug 26062; bugfix
9044 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
9045 - Prevent a possible out-of-bounds smartlist read in
9046 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
9048 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
9049 - Fix a very unlikely (impossible, we believe) null pointer
9050 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
9051 Coverity; this is CID 1430932.
9053 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
9054 - Fix a memory leak when a v3 onion service is configured and gets a
9055 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
9056 - When parsing the descriptor signature, look for the token plus an
9057 extra white-space at the end. This is more correct but also will
9058 allow us to support new fields that might start with "signature".
9059 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
9061 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
9062 - Relays now correctly block attempts to re-extend to the previous
9063 relay by Ed25519 identity. Previously they would warn in this
9064 case, but not actually reject the attempt. Fixes bug 26158; bugfix
9067 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
9068 - Avoid a crash when running with DirPort set but ORPort turned off.
9069 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
9071 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
9072 - Silence unused-const-variable warnings in zstd.h with some GCC
9073 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
9075 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
9076 - Avoid intermittent test failures due to a test that had relied on
9077 onion service introduction point creation finishing within 5
9078 seconds of real clock time. Fixes bug 25450; bugfix
9081 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
9082 - Fix a C99 compliance issue in our configuration script that caused
9083 compilation issues when compiling Tor with certain versions of
9084 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
9086 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
9087 - Fix a number of small memory leaks identified by coverity. Fixes
9088 bug 26467; bugfix on numerous Tor versions.
9090 o Code simplification and refactoring (backport from 0.3.3.5-rc):
9091 - Move the list of default directory authorities to its own file.
9092 Closes ticket 24854. Patch by "beastr0".
9095 Changes in version 0.2.9.16 - 2018-07-13
9096 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
9097 bridge relays should upgrade. We also take this opportunity to backport
9100 o Directory authority changes:
9101 - The "Bifroest" bridge authority has been retired; the new bridge
9102 authority is "Serge", and it is operated by George from the
9103 TorBSD project. Closes ticket 26771.
9105 o Directory authority changes (backport from 0.3.3.7):
9106 - Add an IPv6 address for the "dannenberg" directory authority.
9107 Closes ticket 26343.
9109 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
9110 - When directory authorities read a zero-byte bandwidth file, they
9111 would previously log a warning with the contents of an
9112 uninitialised buffer. They now log a warning about the empty file
9113 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
9115 o Minor features (sandbox, backport from 0.3.3.4-alpha):
9116 - Explicitly permit the poll() system call when the Linux
9117 seccomp2-based sandbox is enabled: apparently, some versions of
9118 libc use poll() when calling getpwnam(). Closes ticket 25313.
9120 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
9121 - Our .travis.yml configuration now includes support for testing the
9122 results of "make distcheck". (It's not uncommon for "make check"
9123 to pass but "make distcheck" to fail.) Closes ticket 25814.
9124 - Our Travis CI configuration now integrates with the Coveralls
9125 coverage analysis tool. Closes ticket 25818.
9127 o Minor features (compilation, backport from 0.3.4.4-rc):
9128 - When building Tor, prefer to use Python 3 over Python 2, and more
9129 recent (contemplated) versions over older ones. Closes
9132 o Minor features (geoip):
9133 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
9134 Country database. Closes ticket 26674.
9136 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
9137 - Upon receiving a malformed connected cell, stop processing the
9138 cell immediately. Previously we would mark the connection for
9139 close, but continue processing the cell as if the connection were
9140 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
9142 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
9143 - Allow the nanosleep() system call, which glibc uses to implement
9144 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
9146 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
9147 - When running the ntor_ref.py test, make sure only to pass strings
9148 (rather than "bytes" objects) to the Python subprocess module.
9149 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
9152 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
9153 - Work around a change in OpenSSL 1.1.1 where return values that
9154 would previously indicate "no password" now indicate an empty
9155 password. Without this workaround, Tor instances running with
9156 OpenSSL 1.1.1 would accept descriptors that other Tor instances
9157 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
9159 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
9160 - Fix a compilation warning on some versions of GCC when building
9161 code that calls routerinfo_get_my_routerinfo() twice, assuming
9162 that the second call will succeed if the first one did. Fixes bug
9163 26269; bugfix on 0.2.8.2-alpha.
9165 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
9166 - Don't consider Tor running as a client if the ControlPort is open,
9167 but no actual client ports are open. Fixes bug 26062; bugfix
9170 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
9171 - Prevent a possible out-of-bounds smartlist read in
9172 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
9174 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
9175 - Fix a very unlikely (impossible, we believe) null pointer
9176 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
9177 Coverity; this is CID 1430932.
9179 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
9180 - Fix a number of small memory leaks identified by coverity. Fixes
9181 bug 26467; bugfix on numerous Tor versions.
9183 o Code simplification and refactoring (backport from 0.3.3.5-rc):
9184 - Move the list of default directory authorities to its own file.
9185 Closes ticket 24854. Patch by "beastr0".
9188 Changes in version 0.3.3.8 - 2018-07-09
9189 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
9190 fixes for a memory leak affecting directory authorities.
9192 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
9193 - Stop leaking memory on directory authorities when planning to
9194 vote. This bug was crashing authorities by exhausting their
9195 memory. Fixes bug 26435; bugfix on 0.3.3.6.
9197 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
9198 - Make sure that failing tests in Rust will actually cause the build
9199 to fail: previously, they were ignored. Fixes bug 26258; bugfix
9202 o Minor features (compilation, backport from 0.3.4.4-rc):
9203 - When building Tor, prefer to use Python 3 over Python 2, and more
9204 recent (contemplated) versions over older ones. Closes
9207 o Minor features (geoip):
9208 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
9209 Country database. Closes ticket 26674.
9211 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
9212 - Add several checks to detect whether Tor relays are uploading
9213 their descriptors without specifying why they regenerated them.
9214 Diagnostic for ticket 25686.
9216 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
9217 - Don't count path selection failures as circuit build failures.
9218 This change should eliminate cases where Tor blames its guard or
9219 the network for situations like insufficient microdescriptors
9220 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
9223 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
9224 - Fix a compilation warning on some versions of GCC when building
9225 code that calls routerinfo_get_my_routerinfo() twice, assuming
9226 that the second call will succeed if the first one did. Fixes bug
9227 26269; bugfix on 0.2.8.2-alpha.
9229 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
9230 - Handle the HSADDRESS= argument to the HSPOST command properly.
9231 (Previously, this argument was misparsed and thus ignored.) Fixes
9232 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
9234 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
9235 - Fix a number of small memory leaks identified by coverity. Fixes
9236 bug 26467; bugfix on numerous Tor versions.
9238 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
9239 - Relays now correctly block attempts to re-extend to the previous
9240 relay by Ed25519 identity. Previously they would warn in this
9241 case, but not actually reject the attempt. Fixes bug 26158; bugfix
9244 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
9245 - When shutting down, Tor now clears all the flags in the control.c
9246 module. This should prevent a bug where authentication cookies are
9247 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
9249 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
9250 - When running the hs_ntor_ref.py test, make sure only to pass
9251 strings (rather than "bytes" objects) to the Python subprocess
9252 module. Python 3 on Windows seems to require this. Fixes bug
9253 26535; bugfix on 0.3.1.1-alpha.
9254 - When running the ntor_ref.py test, make sure only to pass strings
9255 (rather than "bytes" objects) to the Python subprocess module.
9256 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
9260 Changes in version 0.3.3.7 - 2018-06-12
9261 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
9262 fixes for bugs affecting compatibility and stability.
9264 o Directory authority changes:
9265 - Add an IPv6 address for the "dannenberg" directory authority.
9266 Closes ticket 26343.
9268 o Minor features (geoip):
9269 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
9270 Country database. Closes ticket 26351.
9272 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
9273 - Work around a change in OpenSSL 1.1.1 where return values that
9274 would previously indicate "no password" now indicate an empty
9275 password. Without this workaround, Tor instances running with
9276 OpenSSL 1.1.1 would accept descriptors that other Tor instances
9277 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
9279 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
9280 - Silence unused-const-variable warnings in zstd.h with some GCC
9281 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
9283 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
9284 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
9285 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
9286 miscounting the total number of circuits for these field values.)
9287 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
9289 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
9290 - Prevent a possible out-of-bounds smartlist read in
9291 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
9293 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
9294 - Only select relays when they have the descriptors we prefer to use
9295 for them. This change fixes a bug where we could select a relay
9296 because it had _some_ descriptor, but reject it later with a
9297 nonfatal assertion error because it didn't have the exact one we
9298 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
9301 Changes in version 0.3.3.6 - 2018-05-22
9302 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
9303 backports several important fixes from the 0.3.4.1-alpha.
9305 The Tor 0.3.3 series includes controller support and other
9306 improvements for v3 onion services, official support for embedding Tor
9307 within other applications, and our first non-trivial module written in
9308 the Rust programming language. (Rust is still not enabled by default
9309 when building Tor.) And as usual, there are numerous other smaller
9310 bugfixes, features, and improvements.
9312 Below are the changes since 0.3.2.10. For a list of only the changes
9313 since 0.3.3.5-rc, see the ChangeLog file.
9315 o New system requirements:
9316 - When built with Rust, Tor now depends on version 0.2.39 of the
9317 libc crate. Closes tickets 25310 and 25664.
9319 o Major features (embedding):
9320 - There is now a documented stable API for programs that need to
9321 embed Tor. See tor_api.h for full documentation and known bugs.
9322 Closes ticket 23684.
9323 - Tor now has support for restarting in the same process.
9324 Controllers that run Tor using the "tor_api.h" interface can now
9325 restart Tor after Tor has exited. This support is incomplete,
9326 however: we fixed crash bugs that prevented it from working at
9327 all, but many bugs probably remain, including a possibility of
9328 security issues. Implements ticket 24581.
9330 o Major features (IPv6, directory documents):
9331 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
9332 consensus. This information makes it easier for IPv6 clients to
9333 bootstrap and choose reachable entry guards. Implements
9335 - Add consensus method 28, which removes IPv6 ORPorts from
9336 microdescriptors. Now that the consensus contains IPv6 ORPorts,
9337 they are redundant in microdescs. This change will be used by Tor
9338 clients on 0.2.8.x and later. (That is to say, with all Tor
9339 clients that have IPv6 bootstrap and guard support.) Implements
9341 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
9342 set by different numbers of authorities. Fixes 23870
9345 o Major features (onion service v3, control port):
9346 - The control port now supports commands and events for v3 onion
9347 services. It is now possible to create ephemeral v3 services using
9348 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
9349 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
9350 DEL_ONION) have been extended to support v3 onion services. Closes
9351 ticket 20699; implements proposal 284.
9353 o Major features (onion services):
9354 - Provide torrc options to pin the second and third hops of onion
9355 service circuits to a list of nodes. The option HSLayer2Guards
9356 pins the second hop, and the option HSLayer3Guards pins the third
9357 hop. These options are for use in conjunction with experiments
9358 with "vanguards" for preventing guard enumeration attacks. Closes
9360 - When v3 onion service clients send introduce cells, they now
9361 include the IPv6 address of the rendezvous point, if it has one.
9362 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
9363 in future Tor versions, IPv6-only v3 single onion services will be
9364 able to use IPv6 addresses to connect directly to the rendezvous
9365 point. Closes ticket 23577. Patch by Neel Chauhan.
9367 o Major features (relay):
9368 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
9369 operator to use a more reasonable ("reduced") exit policy, rather
9370 than the default one. If you want to run an exit node without
9371 thinking too hard about which ports to allow, this one is for you.
9372 Closes ticket 13605. Patch from Neel Chauhan.
9374 o Major features (rust, portability, experimental):
9375 - Tor now ships with an optional implementation of one of its
9376 smaller modules (protover.c) in the Rust programming language. To
9377 try it out, install a Rust build environment, and configure Tor
9378 with "--enable-rust --enable-cargo-online-mode". This should not
9379 cause any user-visible changes, but should help us gain more
9380 experience with Rust, and plan future Rust integration work.
9381 Implementation by Chelsea Komlo. Closes ticket 22840.
9383 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
9384 - When directory authorities read a zero-byte bandwidth file, they
9385 would previously log a warning with the contents of an
9386 uninitialised buffer. They now log a warning about the empty file
9387 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
9389 o Major bugfixes (security, directory authority, denial-of-service):
9390 - Fix a bug that could have allowed an attacker to force a directory
9391 authority to use up all its RAM by passing it a maliciously
9392 crafted protocol versions string. Fixes bug 25517; bugfix on
9393 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
9395 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
9396 - Avoid a rare assertion failure in the circuit build timeout code
9397 if we fail to allow any circuits to actually complete. Fixes bug
9398 25733; bugfix on 0.2.2.2-alpha.
9400 o Major bugfixes (netflow padding):
9401 - Stop adding unneeded channel padding right after we finish
9402 flushing to a connection that has been trying to flush for many
9403 seconds. Instead, treat all partial or complete flushes as
9404 activity on the channel, which will defer the time until we need
9405 to add padding. This fix should resolve confusing and scary log
9406 messages like "Channel padding timeout scheduled 221453ms in the
9407 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
9409 o Major bugfixes (networking):
9410 - Tor will no longer reject IPv6 address strings from Tor Browser
9411 when they are passed as hostnames in SOCKS5 requests. Fixes bug
9412 25036, bugfix on Tor 0.3.1.2.
9414 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
9415 - Correctly detect when onion services get disabled after HUP. Fixes
9416 bug 25761; bugfix on 0.3.2.1.
9418 o Major bugfixes (performance, load balancing):
9419 - Directory authorities no longer vote in favor of the Guard flag
9420 for relays without directory support. Starting in Tor
9421 0.3.0.1-alpha, clients have been avoiding using such relays in the
9422 Guard position, leading to increasingly broken load balancing for
9423 the 5%-or-so of Guards that don't advertise directory support.
9424 Fixes bug 22310; bugfix on 0.3.0.6.
9426 o Major bugfixes (relay):
9427 - If we have failed to connect to a relay and received a connection
9428 refused, timeout, or similar error (at the TCP level), do not try
9429 that same address/port again for 60 seconds after the failure has
9430 occurred. Fixes bug 24767; bugfix on 0.0.6.
9432 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
9433 - Impose a limit on circuit cell queue size. The limit can be
9434 controlled by a consensus parameter. Fixes bug 25226; bugfix
9437 o Minor features (cleanup):
9438 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
9439 when it stops. Closes ticket 23271.
9441 o Minor features (compatibility, backport from 0.3.4.1-alpha):
9442 - Avoid some compilation warnings with recent versions of LibreSSL.
9443 Closes ticket 26006.
9445 o Minor features (config options):
9446 - Change the way the default value for MaxMemInQueues is calculated.
9447 We now use 40% of the hardware RAM if the system has 8 GB RAM or
9448 more. Otherwise we use the former value of 75%. Closes
9451 o Minor features (continuous integration):
9452 - Update the Travis CI configuration to use the stable Rust channel,
9453 now that we have decided to require that. Closes ticket 25714.
9455 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
9456 - Our .travis.yml configuration now includes support for testing the
9457 results of "make distcheck". (It's not uncommon for "make check"
9458 to pass but "make distcheck" to fail.) Closes ticket 25814.
9459 - Our Travis CI configuration now integrates with the Coveralls
9460 coverage analysis tool. Closes ticket 25818.
9462 o Minor features (defensive programming):
9463 - Most of the functions in Tor that free objects have been replaced
9464 with macros that free the objects and set the corresponding
9465 pointers to NULL. This change should help prevent a large class of
9466 dangling pointer bugs. Closes ticket 24337.
9467 - Where possible, the tor_free() macro now only evaluates its input
9468 once. Part of ticket 24337.
9469 - Check that microdesc ed25519 ids are non-zero in
9470 node_get_ed25519_id() before returning them. Implements ticket
9471 24001, patch by "aruna1234".
9473 o Minor features (directory authority):
9474 - When directory authorities are unable to add signatures to a
9475 pending consensus, log the reason why. Closes ticket 24849.
9477 o Minor features (embedding):
9478 - Tor can now start with a preauthenticated control connection
9479 created by the process that launched it. This feature is meant for
9480 use by programs that want to launch and manage a Tor process
9481 without allowing other programs to manage it as well. For more
9482 information, see the __OwningControllerFD option documented in
9483 control-spec.txt. Closes ticket 23900.
9484 - On most errors that would cause Tor to exit, it now tries to
9485 return from the tor_main() function, rather than calling the
9486 system exit() function. Most users won't notice a difference here,
9487 but it should be significant for programs that run Tor inside a
9488 separate thread: they should now be able to survive Tor's exit
9489 conditions rather than having Tor shut down the entire process.
9490 Closes ticket 23848.
9491 - Applications that want to embed Tor can now tell Tor not to
9492 register any of its own POSIX signal handlers, using the
9493 __DisableSignalHandlers option. Closes ticket 24588.
9495 o Minor features (fallback directory list):
9496 - Avoid selecting fallbacks that change their IP addresses too
9497 often. Select more fallbacks by ignoring the Guard flag, and
9498 allowing lower cutoffs for the Running and V2Dir flags. Also allow
9499 a lower bandwidth, and a higher number of fallbacks per operator
9500 (5% of the list). Implements ticket 24785.
9501 - Update the fallback whitelist and blacklist based on opt-ins and
9502 relay changes. Closes tickets 22321, 24678, 22527, 24135,
9505 o Minor features (fallback directory mirror configuration):
9506 - Add a nickname to each fallback in a C comment. This makes it
9507 easier for operators to find their relays, and allows stem to use
9508 nicknames to identify fallbacks. Implements ticket 24600.
9509 - Add a type and version header to the fallback directory mirror
9510 file. Also add a delimiter to the end of each fallback entry. This
9511 helps external parsers like stem and Relay Search. Implements
9513 - Add an extrainfo cache flag for each fallback in a C comment. This
9514 allows stem to use fallbacks to fetch extra-info documents, rather
9515 than using authorities. Implements ticket 22759.
9516 - Add the generateFallbackDirLine.py script for automatically
9517 generating fallback directory mirror lines from relay fingerprints.
9518 No more typos! Add the lookupFallbackDirContact.py script for
9519 automatically looking up operator contact info from relay
9520 fingerprints. Implements ticket 24706, patch by teor and atagar.
9521 - Reject any fallback directory mirror that serves an expired
9522 consensus. Implements ticket 20942, patch by "minik".
9523 - Remove commas and equals signs from external string inputs to the
9524 fallback list. This avoids format confusion attacks. Implements
9526 - Remove the "weight=10" line from fallback directory mirror
9527 entries. Ticket 24681 will maintain the current fallback weights
9528 by changing Tor's default fallback weight to 10. Implements
9530 - Stop logging excessive information about fallback netblocks.
9531 Implements ticket 24791.
9533 o Minor features (forward-compatibility):
9534 - If a relay supports some link authentication protocol that we do
9535 not recognize, then include that relay's ed25519 key when telling
9536 other relays to extend to it. Previously, we treated future
9537 versions as if they were too old to support ed25519 link
9538 authentication. Closes ticket 20895.
9540 o Minor features (geoip):
9541 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
9542 database. Closes ticket 26104.
9544 o Minor features (heartbeat):
9545 - Add onion service information to our heartbeat logs, displaying
9546 stats about the activity of configured onion services. Closes
9549 o Minor features (instrumentation, development):
9550 - Add the MainloopStats option to allow developers to get
9551 instrumentation information from the main event loop via the
9552 heartbeat messages. We hope to use this to improve Tor's behavior
9553 when it's trying to sleep. Closes ticket 24605.
9555 o Minor features (IPv6):
9556 - Make IPv6-only clients wait for microdescs for relays, even if we
9557 were previously using descriptors (or were using them as a bridge)
9558 and have a cached descriptor for them. Implements ticket 23827.
9559 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
9560 them, rather than waiting to download microdescriptors. Implements
9563 o Minor features (log messages):
9564 - Improve log message in the out-of-memory handler to include
9565 information about memory usage from the different compression
9566 backends. Closes ticket 25372.
9567 - Improve a warning message that happens when we fail to re-parse an
9568 old router because of an expired certificate. Closes ticket 20020.
9569 - Make the log more quantitative when we hit MaxMemInQueues
9570 threshold exposing some values. Closes ticket 24501.
9572 o Minor features (logging):
9573 - Clarify the log messages produced when getrandom() or a related
9574 entropy-generation mechanism gives an error. Closes ticket 25120.
9575 - Added support for the Android logging subsystem. Closes
9578 o Minor features (performance):
9579 - Support predictive circuit building for onion service circuits
9580 with multiple layers of guards. Closes ticket 23101.
9581 - Use stdatomic.h where available, rather than mutexes, to implement
9582 atomic_counter_t. Closes ticket 23953.
9584 o Minor features (performance, 32-bit):
9585 - Improve performance on 32-bit systems by avoiding 64-bit division
9586 when calculating the timestamp in milliseconds for channel padding
9587 computations. Implements ticket 24613.
9588 - Improve performance on 32-bit systems by avoiding 64-bit division
9589 when timestamping cells and buffer chunks for OOM calculations.
9590 Implements ticket 24374.
9592 o Minor features (performance, OSX, iOS):
9593 - Use the mach_approximate_time() function (when available) to
9594 implement coarse monotonic time. Having a coarse time function
9595 should avoid a large number of system calls, and improve
9596 performance slightly, especially under load. Closes ticket 24427.
9598 o Minor features (performance, windows):
9599 - Improve performance on Windows Vista and Windows 7 by adjusting
9600 TCP send window size according to the recommendation from
9601 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
9604 o Minor features (sandbox):
9605 - Explicitly permit the poll() system call when the Linux
9606 seccomp2-based sandbox is enabled: apparently, some versions of
9607 libc use poll() when calling getpwnam(). Closes ticket 25313.
9609 o Minor features (storage, configuration):
9610 - Users can store cached directory documents somewhere other than
9611 the DataDirectory by using the CacheDirectory option. Similarly,
9612 the storage location for relay's keys can be overridden with the
9613 KeyDirectory option. Closes ticket 22703.
9615 o Minor features (testing):
9616 - Add a "make test-rust" target to run the rust tests only. Closes
9619 o Minor features (testing, debugging, embedding):
9620 - For development purposes, Tor now has a mode in which it runs for
9621 a few seconds, then stops, and starts again without exiting the
9622 process. This mode is meant to help us debug various issues with
9623 ticket 23847. To use this feature, compile with
9624 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
9625 environment variable. This is expected to crash a lot, and is
9626 really meant for developers only. It will likely be removed in a
9627 future release. Implements ticket 24583.
9629 o Minor bugfixes (build, rust):
9630 - Fix output of autoconf checks to display success messages for Rust
9631 dependencies and a suitable rustc compiler version. Fixes bug
9632 24612; bugfix on 0.3.1.3-alpha.
9633 - Don't pass the --quiet option to cargo: it seems to suppress some
9634 errors, which is not what we want to do when building. Fixes bug
9635 24518; bugfix on 0.3.1.7.
9636 - Build correctly when building from outside Tor's source tree with
9637 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
9640 o Minor bugfixes (C correctness):
9641 - Fix a very unlikely (impossible, we believe) null pointer
9642 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
9643 Coverity; this is CID 1430932.
9645 o Minor bugfixes (channel, client):
9646 - Better identify client connection when reporting to the geoip
9647 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
9649 o Minor bugfixes (circuit, cannibalization):
9650 - Don't cannibalize preemptively-built circuits if we no longer
9651 recognize their first hop. This situation can happen if our Guard
9652 relay went off the consensus after the circuit was created. Fixes
9653 bug 24469; bugfix on 0.0.6.
9655 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
9656 - Don't consider Tor running as a client if the ControlPort is open,
9657 but no actual client ports are open. Fixes bug 26062; bugfix
9660 o Minor bugfixes (compilation):
9661 - Fix a C99 compliance issue in our configuration script that caused
9662 compilation issues when compiling Tor with certain versions of
9663 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
9665 o Minor bugfixes (controller):
9666 - Restore the correct operation of the RESOLVE command, which had
9667 been broken since we added the ability to enable/disable DNS on
9668 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
9669 - Avoid a (nonfatal) assertion failure when extending a one-hop
9670 circuit from the controller to become a multihop circuit. Fixes
9671 bug 24903; bugfix on 0.2.5.2-alpha.
9673 o Minor bugfixes (correctness):
9674 - Remove a nonworking, unnecessary check to see whether a circuit
9675 hop's identity digest was set when the circuit failed. Fixes bug
9676 24927; bugfix on 0.2.4.4-alpha.
9678 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
9679 - Upon receiving a malformed connected cell, stop processing the
9680 cell immediately. Previously we would mark the connection for
9681 close, but continue processing the cell as if the connection were
9682 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
9684 o Minor bugfixes (directory authorities, IPv6):
9685 - When creating a routerstatus (vote) from a routerinfo (descriptor),
9686 set the IPv6 address to the unspecified IPv6 address, and
9687 explicitly initialize the port to zero. Fixes bug 24488; bugfix
9690 o Minor bugfixes (documentation):
9691 - Document that the PerConnBW{Rate,Burst} options will fall back to
9692 their corresponding consensus parameters only if those parameters
9693 are set. Previously we had claimed that these values would always
9694 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
9696 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
9697 - Stop saying in the manual that clients cache ipv4 dns answers from
9698 exit relays. We haven't used them since 0.2.6.3-alpha, and in
9699 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
9700 we forgot to say so in the man page. Fixes bug 26052; bugfix
9703 o Minor bugfixes (exit relay DNS retries):
9704 - Re-attempt timed-out DNS queries 3 times before failure, since our
9705 timeout is 5 seconds for them, but clients wait 10-15. Also allow
9706 slightly more timeouts per resolver when an exit has multiple
9707 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
9709 o Minor bugfixes (fallback directory mirrors):
9710 - Make updateFallbackDirs.py search harder for python. (Some OSs
9711 don't put it in /usr/bin.) Fixes bug 24708; bugfix
9714 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
9715 - When hibernating, close connections normally and allow them to
9716 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
9718 - Do not attempt to launch self-reachability tests when entering
9719 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
9720 - Resolve several bugs related to descriptor fetching on bridge
9721 clients with bandwidth accounting enabled. (This combination is
9722 not recommended!) Fixes a case of bug 12062; bugfix
9724 - When hibernating, do not attempt to launch DNS checks. Fixes a
9725 case of bug 12062; bugfix on 0.1.2.2-alpha.
9726 - When hibernating, do not try to upload or download descriptors.
9727 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
9729 o Minor bugfixes (IPv6, bridges):
9730 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
9731 bugfix on 0.2.8.2-alpha.
9732 - Tor now sets IPv6 address in the routerstatus as well as in the
9733 router descriptors when updating addresses for a bridge. Closes
9734 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
9736 o Minor bugfixes (Linux seccomp2 sandbox):
9737 - When running with the sandbox enabled, reload configuration files
9738 correctly even when %include was used. Previously we would crash.
9739 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
9741 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
9742 - Allow the nanosleep() system call, which glibc uses to implement
9743 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
9745 o Minor bugfixes (logging):
9746 - Fix a (mostly harmless) race condition when invoking
9747 LOG_PROTOCOL_WARN message from a subthread while the torrc options
9748 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
9750 o Minor bugfixes (man page, SocksPort):
9751 - Remove dead code from the old "SocksSocket" option, and rename
9752 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old
9753 option still works, but is deprecated. Fixes bug 24343; bugfix
9756 o Minor bugfixes (memory leaks):
9757 - Avoid possible at-exit memory leaks related to use of Libevent's
9758 event_base_once() function. (This function tends to leak memory if
9759 the event_base is closed before the event fires.) Fixes bug 24584;
9760 bugfix on 0.2.8.1-alpha.
9761 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
9764 o Minor bugfixes (network IPv6 test):
9765 - Tor's test scripts now check if "ping -6 ::1" works when the user
9766 runs "make test-network-all". Fixes bug 24677; bugfix on
9767 0.2.9.3-alpha. Patch by "ffmancera".
9769 o Minor bugfixes (networking):
9770 - string_is_valid_hostname() will not consider IP strings to be
9771 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
9773 o Minor bugfixes (onion service v3):
9774 - Avoid an assertion failure when the next onion service descriptor
9775 rotation type is out of sync with the consensus's valid-after
9776 time. Instead, log a warning message with extra information, so we
9777 can better hunt down the cause of this assertion. Fixes bug 25306;
9778 bugfix on 0.3.2.1-alpha.
9780 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
9781 - Fix a memory leak when a v3 onion service is configured and gets a
9782 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
9783 - When parsing the descriptor signature, look for the token plus an
9784 extra white-space at the end. This is more correct but also will
9785 allow us to support new fields that might start with "signature".
9786 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
9788 o Minor bugfixes (onion services):
9789 - If we are configured to offer a single onion service, don't log
9790 long-term established one hop rendezvous points in the heartbeat.
9791 Fixes bug 25116; bugfix on 0.2.9.6-rc.
9793 o Minor bugfixes (performance):
9794 - Reduce the number of circuits that will be opened at once during
9795 the circuit build timeout phase. This is done by increasing the
9796 idle timeout to 3 minutes, and lowering the maximum number of
9797 concurrent learning circuits to 10. Fixes bug 24769; bugfix
9799 - Avoid calling protocol_list_supports_protocol() from inside tight
9800 loops when running with cached routerinfo_t objects. Instead,
9801 summarize the relevant protocols as flags in the routerinfo_t, as
9802 we do for routerstatus_t objects. This change simplifies our code
9803 a little, and saves a large amount of short-term memory allocation
9804 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
9806 o Minor bugfixes (performance, timeouts):
9807 - Consider circuits for timeout as soon as they complete a hop. This
9808 is more accurate than applying the timeout in
9809 circuit_expire_building() because that function is only called
9810 once per second, which is now too slow for typical timeouts on the
9811 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
9812 - Use onion service circuits (and other circuits longer than 3 hops)
9813 to calculate a circuit build timeout. Previously, Tor only
9814 calculated its build timeout based on circuits that planned to be
9815 exactly 3 hops long. With this change, we include measurements
9816 from all circuits at the point where they complete their third
9817 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
9819 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
9820 - Avoid a crash when running with DirPort set but ORPort turned off.
9821 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
9823 o Minor bugfixes (Rust FFI):
9824 - Fix a minor memory leak which would happen whenever the C code
9825 would call the Rust implementation of
9826 protover_get_supported_protocols(). This was due to the C version
9827 returning a static string, whereas the Rust version newly allocated
9828 a CString to pass across the FFI boundary. Consequently, the C
9829 code was not expecting to need to free() what it was given. Fixes
9830 bug 25127; bugfix on 0.3.2.1-alpha.
9832 o Minor bugfixes (spelling):
9833 - Use the "misspell" tool to detect and fix typos throughout the
9834 source code. Fixes bug 23650; bugfix on various versions of Tor.
9835 Patch from Deepesh Pathak.
9837 o Minor bugfixes (testing):
9838 - Avoid intermittent test failures due to a test that had relied on
9839 onion service introduction point creation finishing within 5
9840 seconds of real clock time. Fixes bug 25450; bugfix
9842 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
9843 bugfix on 0.2.3.1-alpha.
9845 o Minor bugfixes (unit test, monotonic time):
9846 - Increase a constant (1msec to 10msec) in the monotonic time test
9847 that makes sure the nsec/usec/msec times read are synchronized.
9848 This change was needed to accommodate slow systems like armel or
9849 when the clock_gettime() is not a VDSO on the running kernel.
9850 Fixes bug 25113; bugfix on 0.2.9.1.
9852 o Code simplification and refactoring:
9853 - Move the list of default directory authorities to its own file.
9854 Closes ticket 24854. Patch by "beastr0".
9855 - Remove the old (deterministic) directory retry logic entirely:
9856 We've used exponential backoff exclusively for some time. Closes
9858 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
9860 - Remove a series of counters used to track circuit extend attempts
9861 and connection status but that in reality we aren't using for
9862 anything other than stats logged by a SIGUSR1 signal. Closes
9864 - Remove /usr/athena from search path in configure.ac. Closes
9866 - Remove duplicate code in node_has_curve25519_onion_key() and
9867 node_get_curve25519_onion_key(), and add a check for a zero
9868 microdesc curve25519 onion key. Closes ticket 23966, patch by
9869 "aruna1234" and teor.
9870 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
9871 memory allocations with large numbers of OR connections (e.g.
9872 relays). Closes ticket 24119.
9873 - Separate the function that deletes ephemeral files when Tor
9875 - Small changes to Tor's buf_t API to make it suitable for use as a
9876 general-purpose safe string constructor. Closes ticket 22342.
9877 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
9878 avoid source code identifier confusion. Closes ticket 24467.
9879 - The tor_git_revision[] constant no longer needs to be redeclared
9880 by everything that links against the rest of Tor. Done as part of
9881 ticket 23845, to simplify our external API.
9882 - We make extend_info_from_node() use node_get_curve25519_onion_key()
9883 introduced in ticket 23577 to access the curve25519 public keys
9884 rather than accessing it directly. Closes ticket 23760. Patch by
9886 - Add a function to log channels' scheduler state changes to aid
9887 debugging efforts. Closes ticket 24531.
9890 - Improved the documentation of AccountingStart parameter. Closes
9892 - Update the documentation for "Log" to include the current list of
9893 logging domains. Closes ticket 25378.
9894 - Add documentation on how to build tor with Rust dependencies
9895 without having to be online. Closes ticket 22907; bugfix
9897 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
9898 traffic. Closes ticket 24318.
9899 - Document that OutboundBindAddress doesn't apply to DNS requests.
9900 Closes ticket 22145. Patch from Aruna Maurya.
9902 o Code simplification and refactoring (channels):
9903 - Remove the incoming and outgoing channel queues. These were never
9904 used, but still took up a step in our fast path.
9905 - The majority of the channel unit tests have been rewritten and the
9906 code coverage has now been raised to 83.6% for channel.c. Closes
9908 - Remove other dead code from the channel subsystem: All together,
9909 this cleanup has removed more than 1500 lines of code overall and
9910 adding very little except for unit test.
9912 o Code simplification and refactoring (circuit rendezvous):
9913 - Split the client-side rendezvous circuit lookup into two
9914 functions: one that returns only established circuits and another
9915 that returns all kinds of circuits. Closes ticket 23459.
9917 o Code simplification and refactoring (controller):
9918 - Make most of the variables in networkstatus_getinfo_by_purpose()
9919 const. Implements ticket 24489.
9921 o Documentation (backport from 0.3.4.1-alpha):
9922 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
9923 ticket 25857. Patch from "CTassisF".
9925 o Documentation (man page):
9926 - The HiddenServiceVersion torrc option accepts only one number:
9927 either version 2 or 3. Closes ticket 25026; bugfix
9930 o Documentation (manpage, denial of service):
9931 - Provide more detail about the denial-of-service options, by
9932 listing each mitigation and explaining how they relate. Closes
9936 Changes in version 0.3.1.10 - 2018-03-03
9937 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
9940 It includes an important security fix for a remote crash attack
9941 against directory authorities, tracked as TROVE-2018-001.
9943 This release also backports our new system for improved resistance to
9944 denial-of-service attacks against relays.
9946 This release also fixes several minor bugs and annoyances from
9949 All directory authorities should upgrade to one of the versions
9950 released today. Relays running 0.3.1.x may wish to update to one of
9951 the versions released today, for the DoS mitigations.
9953 Please note: according to our release calendar, Tor 0.3.1 will no
9954 longer be supported after 1 July 2018. If you will be running Tor
9955 after that date, you should make sure to plan to upgrade to the latest
9956 stable version, or downgrade to 0.2.9 (which will receive long-term
9959 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
9960 - Fix a protocol-list handling bug that could be used to remotely crash
9961 directory authorities with a null-pointer exception. Fixes bug 25074;
9962 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
9965 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
9966 - Give relays some defenses against the recent network overload. We
9967 start with three defenses (default parameters in parentheses).
9968 First: if a single client address makes too many concurrent
9969 connections (>100), hang up on further connections. Second: if a
9970 single client address makes circuits too quickly (more than 3 per
9971 second, with an allowed burst of 90) while also having too many
9972 connections open (3), refuse new create cells for the next while
9973 (1-2 hours). Third: if a client asks to establish a rendezvous
9974 point to you directly, ignore the request. These defenses can be
9975 manually controlled by new torrc options, but relays will also
9976 take guidance from consensus parameters, so there's no need to
9977 configure anything manually. Implements ticket 24902.
9979 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
9980 - Update the sandbox rules so that they should now work correctly
9981 with Glibc 2.26. Closes ticket 24315.
9983 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
9984 - Fix an "off by 2" error in counting rendezvous failures on the
9985 onion service side. While we thought we would stop the rendezvous
9986 attempt after one failed circuit, we were actually making three
9987 circuit attempts before giving up. Now switch to a default of 2,
9988 and allow the consensus parameter "hs_service_max_rdv_failures" to
9989 override. Fixes bug 24895; bugfix on 0.0.6.
9991 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
9992 - Add Link protocol version 5 to the supported protocols list. Fixes
9993 bug 25070; bugfix on 0.3.1.1-alpha.
9995 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
9996 - Fix a set of false positives where relays would consider
9997 connections to other relays as being client-only connections (and
9998 thus e.g. deserving different link padding schemes) if those
9999 relays fell out of the consensus briefly. Now we look only at the
10000 initial handshake and whether the connection authenticated as a
10001 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
10003 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
10004 - Make our OOM handler aware of the geoip client history cache so it
10005 doesn't fill up the memory. This check is important for IPv6 and
10006 our DoS mitigation subsystem. Closes ticket 25122.
10008 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
10009 - Change relay bandwidth reporting stats interval from 4 hours to 24
10010 hours in order to reduce the efficiency of guard discovery
10011 attacks. Fixes ticket 23856.
10013 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
10014 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
10015 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
10016 since they neither disabled TLS 1.3 nor enabled any of the
10017 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
10018 Closes ticket 24978.
10020 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
10021 - The fallback directory list has been re-generated based on the
10022 current status of the network. Tor uses fallback directories to
10023 bootstrap when it doesn't yet have up-to-date directory
10024 information. Closes ticket 24801.
10025 - Make the default DirAuthorityFallbackRate 0.1, so that clients
10026 prefer to bootstrap from fallback directory mirrors. This is a
10027 follow-up to 24679, which removed weights from the default
10028 fallbacks. Implements ticket 24681.
10030 o Minor features (geoip):
10031 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
10034 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
10035 - Use the actual observed address of an incoming relay connection,
10036 not the canonical address of the relay from its descriptor, when
10037 making decisions about how to handle the incoming connection.
10038 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
10040 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
10041 - Directory authorities, when refusing a descriptor from a rejected
10042 relay, now explicitly tell the relay (in its logs) to set a valid
10043 ContactInfo address and contact the bad-relays@ mailing list.
10044 Fixes bug 25170; bugfix on 0.2.9.1.
10046 o Minor bugfixes (address selection, backport from 0.3.2.9):
10047 - When the fascist_firewall_choose_address_ functions don't find a
10048 reachable address, set the returned address to the null address
10049 and port. This is a precautionary measure, because some callers do
10050 not check the return value. Fixes bug 24736; bugfix
10053 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
10054 - Fetch descriptors aggressively whenever we lack enough to build
10055 circuits, regardless of how many descriptors we are missing.
10056 Previously, we would delay launching the fetch when we had fewer
10057 than 15 missing descriptors, even if some of those descriptors
10058 were blocking circuits from building. Fixes bug 23985; bugfix on
10059 0.1.1.11-alpha. The effects of this bug became worse in
10060 0.3.0.3-alpha, when we began treating missing descriptors from our
10061 primary guards as a reason to delay circuits.
10062 - Don't try fetching microdescriptors from relays that have failed
10063 to deliver them in the past. Fixes bug 23817; bugfix
10066 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
10067 - Fix a signed/unsigned comparison warning introduced by our fix to
10068 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
10070 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
10071 - Avoid a crash when attempting to use the seccomp2 sandbox together
10072 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
10075 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
10076 - Fix a possible crash on malformed consensus. If a consensus had
10077 contained an unparseable protocol line, it could have made clients
10078 and relays crash with a null-pointer exception. To exploit this
10079 issue, however, an attacker would need to be able to subvert the
10080 directory authority system. Fixes bug 25251; bugfix on
10081 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
10083 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
10084 - Recover better from empty or corrupt files in the consensus cache
10085 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
10086 - When a consensus diff calculation is only partially successful,
10087 only record the successful parts as having succeeded. Partial
10088 success can happen if (for example) one compression method fails
10089 but the others succeed. Previously we misrecorded all the
10090 calculations as having succeeded, which would later cause a
10091 nonfatal assertion failure. Fixes bug 24086; bugfix
10094 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
10095 - Tor now updates its guard state when it reads a consensus
10096 regardless of whether it's missing descriptors. That makes tor use
10097 its primary guards to fetch descriptors in some edge cases where
10098 it would previously have used fallback directories. Fixes bug
10099 23862; bugfix on 0.3.0.1-alpha.
10101 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
10102 - Don't treat inability to store a cached consensus object as a bug:
10103 it can happen normally when we are out of disk space. Fixes bug
10104 24859; bugfix on 0.3.1.1-alpha.
10106 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
10107 - When queuing DESTROY cells on a channel, only queue the circuit-id
10108 and reason fields: not the entire 514-byte cell. This fix should
10109 help mitigate any bugs or attacks that fill up these queues, and
10110 free more RAM for other uses. Fixes bug 24666; bugfix
10113 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
10114 - When closing a connection via close_connection_immediately(), we
10115 mark it as "not blocked on bandwidth", to prevent later calls from
10116 trying to unblock it, and give it permission to read. This fixes a
10117 backtrace warning that can happen on relays under various
10118 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
10120 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
10121 - When selecting relays by bandwidth, avoid a rounding error that
10122 could sometimes cause load to be imbalanced incorrectly.
10123 Previously, we would always round upwards; now, we round towards
10124 the nearest integer. This had the biggest effect when a relay's
10125 weight adjustments should have given it weight 0, but it got
10126 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
10127 - When calculating the fraction of nodes that have descriptors, and
10128 all nodes in the network have zero bandwidths, count the number of
10129 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
10130 - Actually log the total bandwidth in compute_weighted_bandwidths().
10131 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
10133 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
10134 - Improve the performance of our consensus-diff application code
10135 when Tor is built with the --enable-fragile-hardening option set.
10136 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
10138 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
10139 - Don't exit the Tor process if setrlimit() fails to change the file
10140 limit (which can happen sometimes on some versions of OSX). Fixes
10141 bug 21074; bugfix on 0.0.9pre5.
10143 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
10144 - Fix a bug in the bit-counting parts of our timing-wheel code on
10145 MSVC. (Note that MSVC is still not a supported build platform, due
10146 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
10149 o Minor bugfixes (relay, partial backport):
10150 - Make the internal channel_is_client() function look at what sort
10151 of connection handshake the other side used, rather than whether
10152 the other side ever sent a create_fast cell to us. Backports part
10153 of the fixes from bugs 22805 and 24898.
10155 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
10156 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
10158 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
10159 bugfix on 0.2.9.4-alpha.
10161 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
10162 - Update the "rust dependencies" submodule to be a project-level
10163 repository, rather than a user repository. Closes ticket 25323.
10166 Changes in version 0.2.9.15 - 2018-03-03
10167 Tor 0.2.9.15 backports important security and stability bugfixes from
10168 later Tor releases.
10170 It includes an important security fix for a remote crash attack
10171 against directory authorities, tracked as TROVE-2018-001.
10173 This release also backports our new system for improved resistance to
10174 denial-of-service attacks against relays.
10176 This release also fixes several minor bugs and annoyances from
10179 All directory authorities should upgrade to one of the versions
10180 released today. Relays running 0.2.9.x may wish to update to one of
10181 the versions released today, for the DoS mitigations.
10183 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
10184 - Fix a protocol-list handling bug that could be used to remotely crash
10185 directory authorities with a null-pointer exception. Fixes bug 25074;
10186 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
10189 o Major features (denial-of-service mitigation):
10190 - Give relays some defenses against the recent network overload. We
10191 start with three defenses (default parameters in parentheses).
10192 First: if a single client address makes too many concurrent
10193 connections (>100), hang up on further connections. Second: if a
10194 single client address makes circuits too quickly (more than 3 per
10195 second, with an allowed burst of 90) while also having too many
10196 connections open (3), refuse new create cells for the next while
10197 (1-2 hours). Third: if a client asks to establish a rendezvous
10198 point to you directly, ignore the request. These defenses can be
10199 manually controlled by new torrc options, but relays will also
10200 take guidance from consensus parameters, so there's no need to
10201 configure anything manually. Implements ticket 24902.
10203 o Major bugfixes (bootstrapping):
10204 - Fetch descriptors aggressively whenever we lack enough to build
10205 circuits, regardless of how many descriptors we are missing.
10206 Previously, we would delay launching the fetch when we had fewer
10207 than 15 missing descriptors, even if some of those descriptors
10208 were blocking circuits from building. Fixes bug 23985; bugfix on
10209 0.1.1.11-alpha. The effects of this bug became worse in
10210 0.3.0.3-alpha, when we began treating missing descriptors from our
10211 primary guards as a reason to delay circuits.
10213 o Major bugfixes (onion services, retry behavior):
10214 - Fix an "off by 2" error in counting rendezvous failures on the
10215 onion service side. While we thought we would stop the rendezvous
10216 attempt after one failed circuit, we were actually making three
10217 circuit attempts before giving up. Now switch to a default of 2,
10218 and allow the consensus parameter "hs_service_max_rdv_failures" to
10219 override. Fixes bug 24895; bugfix on 0.0.6.
10221 o Minor feature (relay statistics):
10222 - Change relay bandwidth reporting stats interval from 4 hours to 24
10223 hours in order to reduce the efficiency of guard discovery
10224 attacks. Fixes ticket 23856.
10226 o Minor features (compatibility, OpenSSL):
10227 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
10228 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
10229 since they neither disabled TLS 1.3 nor enabled any of the
10230 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
10231 Closes ticket 24978.
10233 o Minor features (denial-of-service avoidance):
10234 - Make our OOM handler aware of the geoip client history cache so it
10235 doesn't fill up the memory. This check is important for IPv6 and
10236 our DoS mitigation subsystem. Closes ticket 25122.
10238 o Minor features (fallback directory mirrors):
10239 - The fallback directory list has been re-generated based on the
10240 current status of the network. Tor uses fallback directories to
10241 bootstrap when it doesn't yet have up-to-date directory
10242 information. Closes ticket 24801.
10243 - Make the default DirAuthorityFallbackRate 0.1, so that clients
10244 prefer to bootstrap from fallback directory mirrors. This is a
10245 follow-up to 24679, which removed weights from the default
10246 fallbacks. Implements ticket 24681.
10248 o Minor features (geoip):
10249 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
10252 o Minor features (linux seccomp2 sandbox):
10253 - Update the sandbox rules so that they should now work correctly
10254 with Glibc 2.26. Closes ticket 24315.
10256 o Minor bugfix (channel connection):
10257 - Use the actual observed address of an incoming relay connection,
10258 not the canonical address of the relay from its descriptor, when
10259 making decisions about how to handle the incoming connection.
10260 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
10262 o Minor bugfix (directory authority):
10263 - Directory authorities, when refusing a descriptor from a rejected
10264 relay, now explicitly tell the relay (in its logs) to set a valid
10265 ContactInfo address and contact the bad-relays@ mailing list.
10266 Fixes bug 25170; bugfix on 0.2.9.1.
10268 o Minor bugfixes (address selection):
10269 - When the fascist_firewall_choose_address_ functions don't find a
10270 reachable address, set the returned address to the null address
10271 and port. This is a precautionary measure, because some callers do
10272 not check the return value. Fixes bug 24736; bugfix
10275 o Minor bugfixes (compilation):
10276 - Fix a signed/unsigned comparison warning introduced by our fix to
10277 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
10279 o Minor bugfixes (control port, linux seccomp2 sandbox):
10280 - Avoid a crash when attempting to use the seccomp2 sandbox together
10281 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
10284 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
10285 - Fix a possible crash on malformed consensus. If a consensus had
10286 contained an unparseable protocol line, it could have made clients
10287 and relays crash with a null-pointer exception. To exploit this
10288 issue, however, an attacker would need to be able to subvert the
10289 directory authority system. Fixes bug 25251; bugfix on
10290 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
10292 o Minor bugfixes (memory usage):
10293 - When queuing DESTROY cells on a channel, only queue the circuit-id
10294 and reason fields: not the entire 514-byte cell. This fix should
10295 help mitigate any bugs or attacks that fill up these queues, and
10296 free more RAM for other uses. Fixes bug 24666; bugfix
10299 o Minor bugfixes (network layer):
10300 - When closing a connection via close_connection_immediately(), we
10301 mark it as "not blocked on bandwidth", to prevent later calls from
10302 trying to unblock it, and give it permission to read. This fixes a
10303 backtrace warning that can happen on relays under various
10304 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
10306 o Minor bugfixes (OSX):
10307 - Don't exit the Tor process if setrlimit() fails to change the file
10308 limit (which can happen sometimes on some versions of OSX). Fixes
10309 bug 21074; bugfix on 0.0.9pre5.
10311 o Minor bugfixes (path selection):
10312 - When selecting relays by bandwidth, avoid a rounding error that
10313 could sometimes cause load to be imbalanced incorrectly.
10314 Previously, we would always round upwards; now, we round towards
10315 the nearest integer. This had the biggest effect when a relay's
10316 weight adjustments should have given it weight 0, but it got
10317 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
10318 - When calculating the fraction of nodes that have descriptors, and
10319 all nodes in the network have zero bandwidths, count the number of
10320 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
10321 - Actually log the total bandwidth in compute_weighted_bandwidths().
10322 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
10324 o Minor bugfixes (portability, msvc):
10325 - Fix a bug in the bit-counting parts of our timing-wheel code on
10326 MSVC. (Note that MSVC is still not a supported build platform, due
10327 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
10330 o Minor bugfixes (relay):
10331 - Make the internal channel_is_client() function look at what sort
10332 of connection handshake the other side used, rather than whether
10333 the other side ever sent a create_fast cell to us. Backports part
10334 of the fixes from bugs 22805 and 24898.
10336 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
10337 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
10339 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
10340 bugfix on 0.2.9.4-alpha.
10343 Changes in version 0.3.2.10 - 2018-03-03
10344 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
10345 backports a number of bugfixes, including important fixes for security
10348 It includes an important security fix for a remote crash attack
10349 against directory authorities, tracked as TROVE-2018-001.
10351 Additionally, it backports a fix for a bug whose severity we have
10352 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
10353 triggered in order to crash relays with a use-after-free pattern. As
10354 such, we are now tracking that bug as TROVE-2018-002 and
10355 CVE-2018-0491, and backporting it to earlier releases. This bug
10356 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
10359 This release also backports our new system for improved resistance to
10360 denial-of-service attacks against relays.
10362 This release also fixes several minor bugs and annoyances from
10365 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
10366 today, for the fix to TROVE-2018-002. Directory authorities should
10367 also upgrade. (Relays on earlier versions might want to update too for
10368 the DoS mitigations.)
10370 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
10371 - Fix a protocol-list handling bug that could be used to remotely crash
10372 directory authorities with a null-pointer exception. Fixes bug 25074;
10373 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
10376 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
10377 - Avoid adding the same channel twice in the KIST scheduler pending
10378 list, which could lead to remote denial-of-service use-after-free
10379 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
10381 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
10382 - Give relays some defenses against the recent network overload. We
10383 start with three defenses (default parameters in parentheses).
10384 First: if a single client address makes too many concurrent
10385 connections (>100), hang up on further connections. Second: if a
10386 single client address makes circuits too quickly (more than 3 per
10387 second, with an allowed burst of 90) while also having too many
10388 connections open (3), refuse new create cells for the next while
10389 (1-2 hours). Third: if a client asks to establish a rendezvous
10390 point to you directly, ignore the request. These defenses can be
10391 manually controlled by new torrc options, but relays will also
10392 take guidance from consensus parameters, so there's no need to
10393 configure anything manually. Implements ticket 24902.
10395 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
10396 - Fix an "off by 2" error in counting rendezvous failures on the
10397 onion service side. While we thought we would stop the rendezvous
10398 attempt after one failed circuit, we were actually making three
10399 circuit attempts before giving up. Now switch to a default of 2,
10400 and allow the consensus parameter "hs_service_max_rdv_failures" to
10401 override. Fixes bug 24895; bugfix on 0.0.6.
10402 - New-style (v3) onion services now obey the "max rendezvous circuit
10403 attempts" logic. Previously they would make as many rendezvous
10404 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
10405 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
10407 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
10408 - Add Link protocol version 5 to the supported protocols list. Fixes
10409 bug 25070; bugfix on 0.3.1.1-alpha.
10411 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
10412 - Fix a set of false positives where relays would consider
10413 connections to other relays as being client-only connections (and
10414 thus e.g. deserving different link padding schemes) if those
10415 relays fell out of the consensus briefly. Now we look only at the
10416 initial handshake and whether the connection authenticated as a
10417 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
10419 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
10420 - The scheduler subsystem was failing to promptly notice changes in
10421 consensus parameters, making it harder to switch schedulers
10422 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
10424 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
10425 - Make our OOM handler aware of the geoip client history cache so it
10426 doesn't fill up the memory. This check is important for IPv6 and
10427 our DoS mitigation subsystem. Closes ticket 25122.
10429 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
10430 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
10431 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
10432 since they neither disabled TLS 1.3 nor enabled any of the
10433 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
10434 Closes ticket 24978.
10436 o Minor features (geoip):
10437 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
10440 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
10441 - When logging a failure to create an onion service's descriptor,
10442 also log what the problem with the descriptor was. Diagnostic
10445 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
10446 - Use the actual observed address of an incoming relay connection,
10447 not the canonical address of the relay from its descriptor, when
10448 making decisions about how to handle the incoming connection.
10449 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
10451 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
10452 - Fix a possible crash on malformed consensus. If a consensus had
10453 contained an unparseable protocol line, it could have made clients
10454 and relays crash with a null-pointer exception. To exploit this
10455 issue, however, an attacker would need to be able to subvert the
10456 directory authority system. Fixes bug 25251; bugfix on
10457 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
10459 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
10460 - Directory authorities, when refusing a descriptor from a rejected
10461 relay, now explicitly tell the relay (in its logs) to set a valid
10462 ContactInfo address and contact the bad-relays@ mailing list.
10463 Fixes bug 25170; bugfix on 0.2.9.1.
10465 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
10466 - When building with Rust on OSX, link against libresolv, to work
10467 around the issue at https://github.com/rust-lang/rust/issues/46797.
10468 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
10470 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
10471 - Remove a BUG() statement when a client fetches an onion descriptor
10472 that has a lower revision counter than the one in its cache. This
10473 can happen in normal circumstances due to HSDir desync. Fixes bug
10474 24976; bugfix on 0.3.2.1-alpha.
10476 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
10477 - Don't treat inability to store a cached consensus object as a bug:
10478 it can happen normally when we are out of disk space. Fixes bug
10479 24859; bugfix on 0.3.1.1-alpha.
10481 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
10482 - Improve the performance of our consensus-diff application code
10483 when Tor is built with the --enable-fragile-hardening option set.
10484 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
10486 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
10487 - Don't exit the Tor process if setrlimit() fails to change the file
10488 limit (which can happen sometimes on some versions of OSX). Fixes
10489 bug 21074; bugfix on 0.0.9pre5.
10491 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
10492 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
10494 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
10495 bugfix on 0.2.9.4-alpha.
10497 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
10498 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
10499 25005; bugfix on 0.3.2.7-rc.
10501 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
10502 - Look at the "HSRend" protocol version, not the "HSDir" protocol
10503 version, when deciding whether a consensus entry can support the
10504 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
10505 bugfix on 0.3.2.1-alpha.
10507 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
10508 - Update the "rust dependencies" submodule to be a project-level
10509 repository, rather than a user repository. Closes ticket 25323.
10511 o Documentation (backport from 0.3.3.1-alpha)
10512 - Document that operators who run more than one relay or bridge are
10513 expected to set MyFamily and ContactInfo correctly. Closes
10517 Changes in version 0.3.2.9 - 2018-01-09
10518 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
10520 The 0.3.2 series includes our long-anticipated new onion service
10521 design, with numerous security features. (For more information, see
10522 our blog post at https://blog.torproject.org/fall-harvest.) We also
10523 have a new circuit scheduler algorithm for improved performance on
10524 relays everywhere (see https://blog.torproject.org/kist-and-tell),
10525 along with many smaller features and bugfixes.
10527 Per our stable release policy, we plan to support each stable release
10528 series for at least the next nine months, or for three months after
10529 the first stable release of the next series: whichever is longer. If
10530 you need a release with long-term support, we recommend that you stay
10531 with the 0.2.9 series.
10533 Below is a list of the changes since 0.3.1.7. For a list of all
10534 changes since 0.3.2.8-rc, see the ChangeLog file.
10536 o Directory authority changes:
10537 - Add "Bastet" as a ninth directory authority to the default list.
10538 Closes ticket 23910.
10539 - The directory authority "Longclaw" has changed its IP address.
10540 Closes ticket 23592.
10541 - Remove longclaw's IPv6 address, as it will soon change. Authority
10542 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10543 3/8 directory authorities with IPv6 addresses, but there are also
10544 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10545 - Add an IPv6 address for the "bastet" directory authority. Closes
10548 o Major features (next-generation onion services):
10549 - Tor now supports the next-generation onion services protocol for
10550 clients and services! As part of this release, the core of
10551 proposal 224 has been implemented and is available for
10552 experimentation and testing by our users. This newer version of
10553 onion services ("v3") features many improvements over the legacy
10556 a) Better crypto (replaced SHA1/DH/RSA1024
10557 with SHA3/ed25519/curve25519)
10559 b) Improved directory protocol, leaking much less information to
10562 c) Improved directory protocol, with smaller surface for
10565 d) Better onion address security against impersonation.
10567 e) More extensible introduction/rendezvous protocol.
10569 f) A cleaner and more modular codebase.
10571 You can identify a next-generation onion address by its length:
10572 they are 56 characters long, as in
10573 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
10575 In the future, we will release more options and features for v3
10576 onion services, but we first need a testing period, so that the
10577 current codebase matures and becomes more robust. Planned features
10578 include: offline keys, advanced client authorization, improved
10579 guard algorithms, and statistics. For full details, see
10582 Legacy ("v2") onion services will still work for the foreseeable
10583 future, and will remain the default until this new codebase gets
10584 tested and hardened. Service operators who want to experiment with
10585 the new system can use the 'HiddenServiceVersion 3' torrc
10586 directive along with the regular onion service configuration
10587 options. For more information, see our blog post at
10588 "https://blog.torproject.org/fall-harvest". Enjoy!
10590 o Major feature (scheduler, channel):
10591 - Tor now uses new schedulers to decide which circuits should
10592 deliver cells first, in order to improve congestion at relays. The
10593 first type is called "KIST" ("Kernel Informed Socket Transport"),
10594 and is only available on Linux-like systems: it uses feedback from
10595 the kernel to prevent the kernel's TCP buffers from growing too
10596 full. The second new scheduler type is called "KISTLite": it
10597 behaves the same as KIST, but runs on systems without kernel
10598 support for inspecting TCP implementation details. The old
10599 scheduler is still available, under the name "Vanilla". To change
10600 the default scheduler preference order, use the new "Schedulers"
10601 option. (The default preference order is "KIST,KISTLite,Vanilla".)
10603 Matt Traudt implemented KIST, based on research by Rob Jansen,
10604 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
10605 more information, see the design paper at
10606 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
10607 followup implementation paper at https://arxiv.org/abs/1709.01044.
10608 Closes ticket 12541. For more information, see our blog post at
10609 "https://blog.torproject.org/kist-and-tell".
10611 o Major bugfixes (security, general):
10612 - Fix a denial of service bug where an attacker could use a
10613 malformed directory object to cause a Tor instance to pause while
10614 OpenSSL would try to read a passphrase from the terminal. (Tor
10615 instances run without a terminal, which is the case for most Tor
10616 packages, are not impacted.) Fixes bug 24246; bugfix on every
10617 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10618 Found by OSS-Fuzz as testcase 6360145429790720.
10620 o Major bugfixes (security, directory authority):
10621 - Fix a denial of service issue where an attacker could crash a
10622 directory authority using a malformed router descriptor. Fixes bug
10623 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
10626 o Major bugfixes (security, onion service v2):
10627 - Fix a use-after-free error that could crash v2 Tor onion services
10628 when they failed to open circuits while expiring introduction
10629 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
10630 also tracked as TROVE-2017-013 and CVE-2017-8823.
10631 - When checking for replays in the INTRODUCE1 cell data for a
10632 (legacy) onion service, correctly detect replays in the RSA-
10633 encrypted part of the cell. We were previously checking for
10634 replays on the entire cell, but those can be circumvented due to
10635 the malleability of Tor's legacy hybrid encryption. This fix helps
10636 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10637 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10640 o Major bugfixes (security, relay):
10641 - When running as a relay, make sure that we never build a path
10642 through ourselves, even in the case where we have somehow lost the
10643 version of our descriptor appearing in the consensus. Fixes part
10644 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
10645 as TROVE-2017-012 and CVE-2017-8822.
10646 - When running as a relay, make sure that we never choose ourselves
10647 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
10648 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
10650 o Major bugfixes (bootstrapping):
10651 - Fetch descriptors aggressively whenever we lack enough to build
10652 circuits, regardless of how many descriptors we are missing.
10653 Previously, we would delay launching the fetch when we had fewer
10654 than 15 missing descriptors, even if some of those descriptors
10655 were blocking circuits from building. Fixes bug 23985; bugfix on
10656 0.1.1.11-alpha. The effects of this bug became worse in
10657 0.3.0.3-alpha, when we began treating missing descriptors from our
10658 primary guards as a reason to delay circuits.
10659 - Don't try fetching microdescriptors from relays that have failed
10660 to deliver them in the past. Fixes bug 23817; bugfix
10663 o Major bugfixes (circuit prediction):
10664 - Fix circuit prediction logic so that a client doesn't treat a port
10665 as being "handled" by a circuit if that circuit already has
10666 isolation settings on it. This change should make Tor clients more
10667 responsive by improving their chances of having a pre-created
10668 circuit ready for use when a request arrives. Fixes bug 18859;
10669 bugfix on 0.2.3.3-alpha.
10671 o Major bugfixes (exit relays, DNS):
10672 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
10673 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
10674 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
10675 identifying and finding a workaround to this bug and to Moritz,
10676 Arthur Edelstein, and Roger for helping to track it down and
10679 o Major bugfixes (relay, crash, assertion failure):
10680 - Fix a timing-based assertion failure that could occur when the
10681 circuit out-of-memory handler freed a connection's output buffer.
10682 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10684 o Major bugfixes (usability, control port):
10685 - Report trusted clock skew indications as bootstrap errors, so
10686 controllers can more easily alert users when their clocks are
10687 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
10689 o Minor features (bridge):
10690 - Bridge relays can now set the BridgeDistribution config option to
10691 add a "bridge-distribution-request" line to their bridge
10692 descriptor, which tells BridgeDB how they'd like their bridge
10693 address to be given out. (Note that as of Oct 2017, BridgeDB does
10694 not yet implement this feature.) As a side benefit, this feature
10695 provides a way to distinguish bridge descriptors from non-bridge
10696 descriptors. Implements tickets 18329.
10697 - When handling the USERADDR command on an ExtOrPort, warn when the
10698 transports provides a USERADDR with no port. In a future version,
10699 USERADDR commands of this format may be rejected. Detects problems
10700 related to ticket 23080.
10702 o Minor features (bug detection):
10703 - Log a warning message with a stack trace for any attempt to call
10704 get_options() during option validation. This pattern has caused
10705 subtle bugs in the past. Closes ticket 22281.
10707 o Minor features (build, compilation):
10708 - The "check-changes" feature is now part of the "make check" tests;
10709 we'll use it to try to prevent misformed changes files from
10710 accumulating. Closes ticket 23564.
10711 - Tor builds should now fail if there are any mismatches between the
10712 C type representing a configuration variable and the C type the
10713 data-driven parser uses to store a value there. Previously, we
10714 needed to check these by hand, which sometimes led to mistakes.
10715 Closes ticket 23643.
10717 o Minor features (client):
10718 - You can now use Tor as a tunneled HTTP proxy: use the new
10719 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
10720 requests. Closes ticket 22407.
10721 - Add an extra check to make sure that we always use the newer guard
10722 selection code for picking our guards. Closes ticket 22779.
10723 - When downloading (micro)descriptors, don't split the list into
10724 multiple requests unless we want at least 32 descriptors.
10725 Previously, we split at 4, not 32, which led to significant
10726 overhead in HTTP request size and degradation in compression
10727 performance. Closes ticket 23220.
10728 - Improve log messages when missing descriptors for primary guards.
10729 Resolves ticket 23670.
10731 o Minor features (command line):
10732 - Add a new commandline option, --key-expiration, which prints when
10733 the current signing key is going to expire. Implements ticket
10734 17639; patch by Isis Lovecruft.
10736 o Minor features (control port):
10737 - If an application tries to use the control port as an HTTP proxy,
10738 respond with a meaningful "This is the Tor control port" message,
10739 and log the event. Closes ticket 1667. Patch from Ravi
10741 - Provide better error message for GETINFO desc/(id|name) when not
10742 fetching router descriptors. Closes ticket 5847. Patch by
10744 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
10745 whether Tor will try to download router descriptors and
10746 microdescriptors respectively. Closes ticket 22684.
10747 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
10748 so controllers can tell whether the geoip databases are loaded.
10749 Closes ticket 23237.
10750 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
10751 events. Closes ticket 19254. Patch by "DonnchaC".
10753 o Minor features (development support):
10754 - Developers can now generate a call-graph for Tor using the
10755 "calltool" python program, which post-processes object dumps. It
10756 should work okay on many Linux and OSX platforms, and might work
10757 elsewhere too. To run it, install calltool from
10758 https://gitweb.torproject.org/user/nickm/calltool.git and run
10759 "make callgraph". Closes ticket 19307.
10761 o Minor features (directory authority):
10762 - Make the "Exit" flag assignment only depend on whether the exit
10763 policy allows connections to ports 80 and 443. Previously relays
10764 would get the Exit flag if they allowed connections to one of
10765 these ports and also port 6667. Resolves ticket 23637.
10767 o Minor features (ed25519):
10768 - Add validation function to checks for torsion components in
10769 ed25519 public keys, used by prop224 client-side code. Closes
10770 ticket 22006. Math help by Ian Goldberg.
10772 o Minor features (exit relay, DNS):
10773 - Improve the clarity and safety of the log message from evdns when
10774 receiving an apparently spoofed DNS reply. Closes ticket 3056.
10776 o Minor features (fallback directory mirrors):
10777 - The fallback directory list has been re-generated based on the
10778 current status of the network. Tor uses fallback directories to
10779 bootstrap when it doesn't yet have up-to-date directory
10780 information. Closes ticket 24801.
10781 - Make the default DirAuthorityFallbackRate 0.1, so that clients
10782 prefer to bootstrap from fallback directory mirrors. This is a
10783 follow-up to 24679, which removed weights from the default
10784 fallbacks. Implements ticket 24681.
10786 o Minor features (geoip):
10787 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
10790 o Minor features (integration, hardening):
10791 - Add a new NoExec option to prevent Tor from running other
10792 programs. When this option is set to 1, Tor will never try to run
10793 another program, regardless of the settings of
10794 PortForwardingHelper, ClientTransportPlugin, or
10795 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
10796 without restarting Tor. Closes ticket 22976.
10798 o Minor features (linux seccomp2 sandbox):
10799 - Update the sandbox rules so that they should now work correctly
10800 with Glibc 2.26. Closes ticket 24315.
10802 o Minor features (logging):
10803 - Provide better warnings when the getrandom() syscall fails. Closes
10805 - Downgrade a pair of log messages that could occur when an exit's
10806 resolver gave us an unusual (but not forbidden) response. Closes
10808 - Improve the message we log when re-enabling circuit build timeouts
10809 after having received a consensus. Closes ticket 20963.
10810 - Log more circuit information whenever we are about to try to
10811 package a relay cell on a circuit with a nonexistent n_chan.
10812 Attempt to diagnose ticket 8185.
10813 - Improve info-level log identification of particular circuits, to
10814 help with debugging. Closes ticket 23645.
10815 - Improve the warning message for specifying a relay by nickname.
10816 The previous message implied that nickname registration was still
10817 part of the Tor network design, which it isn't. Closes
10819 - If the sandbox filter fails to load, suggest to the user that
10820 their kernel might not support seccomp2. Closes ticket 23090.
10822 o Minor features (onion service, circuit, logging):
10823 - Improve logging of many callsite in the circuit subsystem to print
10824 the circuit identifier(s).
10825 - Log when we cleanup an intro point from a service so we know when
10826 and for what reason it happened. Closes ticket 23604.
10828 o Minor features (portability):
10829 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
10830 (It doesn't yet work with the sandbox enabled.) Closes
10832 - Check at configure time whether uint8_t is the same type as
10833 unsigned char. Lots of existing code already makes this
10834 assumption, and there could be strict aliasing issues if the
10835 assumption is violated. Closes ticket 22410.
10837 o Minor features (relay):
10838 - When choosing which circuits can be expired as unused, consider
10839 circuits from clients even if those clients used regular CREATE
10840 cells to make them; and do not consider circuits from relays even
10841 if they were made with CREATE_FAST. Part of ticket 22805.
10842 - Reject attempts to use relative file paths when RunAsDaemon is
10843 set. Previously, Tor would accept these, but the directory-
10844 changing step of RunAsDaemon would give strange and/or confusing
10845 results. Closes ticket 22731.
10847 o Minor features (relay statistics):
10848 - Change relay bandwidth reporting stats interval from 4 hours to 24
10849 hours in order to reduce the efficiency of guard discovery
10850 attacks. Fixes ticket 23856.
10852 o Minor features (reverted deprecations):
10853 - The ClientDNSRejectInternalAddresses flag can once again be set in
10854 non-testing Tor networks, so long as they do not use the default
10855 directory authorities. This change also removes the deprecation of
10856 this flag from 0.2.9.2-alpha. Closes ticket 21031.
10858 o Minor features (robustness):
10859 - Change several fatal assertions when flushing buffers into non-
10860 fatal assertions, to prevent any recurrence of 23690.
10862 o Minor features (startup, safety):
10863 - When configured to write a PID file, Tor now exits if it is unable
10864 to do so. Previously, it would warn and continue. Closes
10867 o Minor features (static analysis):
10868 - The BUG() macro has been changed slightly so that Coverity no
10869 longer complains about dead code if the bug is impossible. Closes
10872 o Minor features (testing):
10873 - Our fuzzing tests now test the encrypted portions of v3 onion
10874 service descriptors. Implements more of 21509.
10875 - Add a unit test to make sure that our own generated platform
10876 string will be accepted by directory authorities. Closes
10878 - The default chutney network tests now include tests for the v3
10879 onion service design. Make sure you have the latest version of
10880 chutney if you want to run these. Closes ticket 22437.
10881 - Add a unit test to verify that we can parse a hardcoded v2 onion
10882 service descriptor. Closes ticket 15554.
10884 o Minor bugfixes (address selection):
10885 - When the fascist_firewall_choose_address_ functions don't find a
10886 reachable address, set the returned address to the null address
10887 and port. This is a precautionary measure, because some callers do
10888 not check the return value. Fixes bug 24736; bugfix
10891 o Minor bugfixes (bootstrapping):
10892 - When warning about state file clock skew, report the correct
10893 direction for the detected skew. Fixes bug 23606; bugfix
10896 o Minor bugfixes (bridge clients, bootstrap):
10897 - Retry directory downloads when we get our first bridge descriptor
10898 during bootstrap or while reconnecting to the network. Keep
10899 retrying every time we get a bridge descriptor, until we have a
10900 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
10901 - Stop delaying bridge descriptor fetches when we have cached bridge
10902 descriptors. Instead, only delay bridge descriptor fetches when we
10903 have at least one reachable bridge. Fixes part of bug 24367;
10904 bugfix on 0.2.0.3-alpha.
10905 - Stop delaying directory fetches when we have cached bridge
10906 descriptors. Instead, only delay bridge descriptor fetches when
10907 all our bridges are definitely unreachable. Fixes part of bug
10908 24367; bugfix on 0.2.0.3-alpha.
10910 o Minor bugfixes (bridge):
10911 - Overwrite the bridge address earlier in the process of retrieving
10912 its descriptor, to make sure we reach it on the configured
10913 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
10915 o Minor bugfixes (build, compilation):
10916 - Fix a compilation warning when building with zstd support on
10917 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
10918 and fixed by Andreas Stieger.
10919 - When searching for OpenSSL, don't accept any OpenSSL library that
10920 lacks TLSv1_1_method(): Tor doesn't build with those versions.
10921 Additionally, look in /usr/local/opt/openssl, if it's present.
10922 These changes together repair the default build on OSX systems
10923 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
10924 - Fix a signed/unsigned comparison warning introduced by our fix to
10925 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
10926 - Fix a memory leak warning in one of the libevent-related
10927 configuration tests that could occur when manually specifying
10928 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
10929 Found and patched by Alex Xu.
10930 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
10931 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
10933 o Minor bugfixes (certificate handling):
10934 - Fix a time handling bug in Tor certificates set to expire after
10935 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
10936 Coverity as CID 1415728.
10938 o Minor bugfixes (client):
10939 - By default, do not enable storage of client-side DNS values. These
10940 values were unused by default previously, but they should not have
10941 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
10943 o Minor bugfixes (client, usability):
10944 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
10945 SOCKS4a requests that contain IP address strings, even when
10946 SafeSocks in enabled, as this prevents user from connecting to
10947 known IP addresses without relying on DNS for resolving. SafeSocks
10948 still rejects SOCKS connections that connect to IP addresses when
10949 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
10950 bugfix on Tor 0.2.6.2-alpha.
10952 o Minor bugfixes (code correctness):
10953 - Call htons() in extend_cell_format() for encoding a 16-bit value.
10954 Previously we used ntohs(), which happens to behave the same on
10955 all the platforms we support, but which isn't really correct.
10956 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
10957 - For defense-in-depth, make the controller's write_escaped_data()
10958 function robust to extremely long inputs. Fixes bug 19281; bugfix
10959 on 0.1.1.1-alpha. Reported by Guido Vranken.
10960 - Fix several places in our codebase where a C compiler would be
10961 likely to eliminate a check, based on assuming that undefined
10962 behavior had not happened elsewhere in the code. These cases are
10963 usually a sign of redundant checking or dubious arithmetic. Found
10964 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
10965 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
10968 o Minor bugfixes (compression):
10969 - Handle a pathological case when decompressing Zstandard data when
10970 the output buffer size is zero. Fixes bug 23551; bugfix
10973 o Minor bugfixes (consensus expiry):
10974 - Check for adequate directory information correctly. Previously, Tor
10975 would reconsider whether it had sufficient directory information
10976 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
10978 o Minor bugfixes (control port, linux seccomp2 sandbox):
10979 - Avoid a crash when attempting to use the seccomp2 sandbox together
10980 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
10983 o Minor bugfixes (control port, onion services):
10984 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
10985 HS_DESC event when a service is not able to upload a descriptor.
10986 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
10988 o Minor bugfixes (directory cache):
10989 - Recover better from empty or corrupt files in the consensus cache
10990 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
10991 - When a consensus diff calculation is only partially successful,
10992 only record the successful parts as having succeeded. Partial
10993 success can happen if (for example) one compression method fails
10994 but the others succeed. Previously we misrecorded all the
10995 calculations as having succeeded, which would later cause a
10996 nonfatal assertion failure. Fixes bug 24086; bugfix
10999 o Minor bugfixes (directory client):
11000 - On failure to download directory information, delay retry attempts
11001 by a random amount based on the "decorrelated jitter" algorithm.
11002 Our previous delay algorithm tended to produce extra-long delays
11003 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
11005 o Minor bugfixes (directory protocol):
11006 - Directory servers now include a "Date:" http header for response
11007 codes other than 200. Clients starting with a skewed clock and a
11008 recent consensus were getting "304 Not modified" responses from
11009 directory authorities, so without the Date header, the client
11010 would never hear about a wrong clock. Fixes bug 23499; bugfix
11012 - Make clients wait for 6 seconds before trying to download a
11013 consensus from an authority. Fixes bug 17750; bugfix
11016 o Minor bugfixes (documentation):
11017 - Document better how to read gcov, and what our gcov postprocessing
11018 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
11019 - Fix manpage to not refer to the obsolete (and misspelled)
11020 UseEntryGuardsAsDirectoryGuards parameter in the description of
11021 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
11023 o Minor bugfixes (DoS-resistance):
11024 - If future code asks if there are any running bridges, without
11025 checking if bridges are enabled, log a BUG warning rather than
11026 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
11028 o Minor bugfixes (entry guards):
11029 - Tor now updates its guard state when it reads a consensus
11030 regardless of whether it's missing descriptors. That makes tor use
11031 its primary guards to fetch descriptors in some edge cases where
11032 it would previously have used fallback directories. Fixes bug
11033 23862; bugfix on 0.3.0.1-alpha.
11035 o Minor bugfixes (format strictness):
11036 - Restrict several data formats to decimal. Previously, the
11037 BuildTimeHistogram entries in the state file, the "bw=" entries in
11038 the bandwidth authority file, and the process IDs passed to the
11039 __OwningControllerProcess option could all be specified in hex or
11040 octal as well as in decimal. This was not an intentional feature.
11041 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
11044 o Minor bugfixes (heartbeat):
11045 - If we fail to write a heartbeat message, schedule a retry for the
11046 minimum heartbeat interval number of seconds in the future. Fixes
11047 bug 19476; bugfix on 0.2.3.1-alpha.
11049 o Minor bugfixes (logging):
11050 - Suppress a log notice when relay descriptors arrive. We already
11051 have a bootstrap progress for this so no need to log notice
11052 everytime tor receives relay descriptors. Microdescriptors behave
11053 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
11054 - Remove duplicate log messages regarding opening non-local
11055 SocksPorts upon parsing config and opening listeners at startup.
11056 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
11057 - Use a more comprehensible log message when telling the user
11058 they've excluded every running exit node. Fixes bug 7890; bugfix
11060 - When logging the number of descriptors we intend to download per
11061 directory request, do not log a number higher than then the number
11062 of descriptors we're fetching in total. Fixes bug 19648; bugfix
11064 - When warning about a directory owned by the wrong user, log the
11065 actual name of the user owning the directory. Previously, we'd log
11066 the name of the process owner twice. Fixes bug 23487; bugfix
11068 - Fix some messages on unexpected errors from the seccomp2 library.
11069 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
11070 - The tor specification says hop counts are 1-based, so fix two log
11071 messages that mistakenly logged 0-based hop counts. Fixes bug
11072 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
11073 Credit to Xiaofan Li for reporting this issue.
11075 o Minor bugfixes (logging, relay shutdown, annoyance):
11076 - When a circuit is marked for close, do not attempt to package any
11077 cells for channels on that circuit. Previously, we would detect
11078 this condition lower in the call stack, when we noticed that the
11079 circuit had no attached channel, and log an annoying message.
11080 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
11082 o Minor bugfixes (memory safety, defensive programming):
11083 - Clear the target address when node_get_prim_orport() returns
11084 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
11086 o Minor bugfixes (memory usage):
11087 - When queuing DESTROY cells on a channel, only queue the circuit-id
11088 and reason fields: not the entire 514-byte cell. This fix should
11089 help mitigate any bugs or attacks that fill up these queues, and
11090 free more RAM for other uses. Fixes bug 24666; bugfix
11093 o Minor bugfixes (network layer):
11094 - When closing a connection via close_connection_immediately(), we
11095 mark it as "not blocked on bandwidth", to prevent later calls from
11096 trying to unblock it, and give it permission to read. This fixes a
11097 backtrace warning that can happen on relays under various
11098 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
11100 o Minor bugfixes (onion services):
11101 - The introduction circuit was being timed out too quickly while
11102 waiting for the rendezvous circuit to complete. Keep the intro
11103 circuit around longer instead of timing out and reopening new ones
11104 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
11105 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
11106 so it matches dir-spec.txt. Fixes bug 24262; bugfix
11108 - When handling multiple SOCKS request for the same .onion address,
11109 only fetch the service descriptor once.
11110 - Avoid a possible double close of a circuit by the intro point on
11111 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
11112 bugfix on 0.3.0.1-alpha.
11113 - When reloading configured onion services, copy all information
11114 from the old service object. Previously, some data was omitted,
11115 causing delays in descriptor upload, and other bugs. Fixes bug
11116 23790; bugfix on 0.2.1.9-alpha.
11118 o Minor bugfixes (path selection):
11119 - When selecting relays by bandwidth, avoid a rounding error that
11120 could sometimes cause load to be imbalanced incorrectly.
11121 Previously, we would always round upwards; now, we round towards
11122 the nearest integer. This had the biggest effect when a relay's
11123 weight adjustments should have given it weight 0, but it got
11124 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
11125 - When calculating the fraction of nodes that have descriptors, and
11126 all nodes in the network have zero bandwidths, count the number of
11127 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
11128 - Actually log the total bandwidth in compute_weighted_bandwidths().
11129 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
11131 o Minor bugfixes (portability):
11132 - Stop using the PATH_MAX variable, which is not defined on GNU
11133 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
11134 - Fix a bug in the bit-counting parts of our timing-wheel code on
11135 MSVC. (Note that MSVC is still not a supported build platform, due
11136 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
11139 o Minor bugfixes (relay):
11140 - When uploading our descriptor for the first time after startup,
11141 report the reason for uploading as "Tor just started" rather than
11142 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
11143 - Avoid unnecessary calls to directory_fetches_from_authorities() on
11144 relays, to prevent spurious address resolutions and descriptor
11145 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
11146 bugfix on in 0.2.8.1-alpha.
11147 - Avoid a crash when transitioning from client mode to bridge mode.
11148 Previously, we would launch the worker threads whenever our
11149 "public server" mode changed, but not when our "server" mode
11150 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
11152 o Minor bugfixes (testing):
11153 - Fix a spurious fuzzing-only use of an uninitialized value. Found
11154 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
11155 - Test that IPv6-only clients can use microdescriptors when running
11156 "make test-network-all". Requires chutney master 61c28b9 or later.
11157 Closes ticket 24109.
11158 - Prevent scripts/test/coverage from attempting to move gcov output
11159 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
11160 - Capture and detect several "Result does not fit" warnings in unit
11161 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
11163 - Fix additional channelpadding unit test failures by using mocked
11164 time instead of actual time for all tests. Fixes bug 23608; bugfix
11166 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
11167 to correctly handle cases where a caller gives it an RSA key of
11168 under 160 bits. (This is not actually a bug in Tor itself, but
11169 rather in our fuzzing code.) Fixes bug 24247; bugfix on
11170 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
11171 - Fix a broken unit test for the OutboundAddress option: the parsing
11172 function was never returning an error on failure. Fixes bug 23366;
11173 bugfix on 0.3.0.3-alpha.
11174 - Fix a signed-integer overflow in the unit tests for
11175 dir/download_status_random_backoff, which was untriggered until we
11176 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
11178 o Minor bugfixes (usability, control port):
11179 - Stop making an unnecessary routerlist check in NETINFO clock skew
11180 detection; this was preventing clients from reporting NETINFO clock
11181 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
11183 o Code simplification and refactoring:
11184 - Remove various ways of testing circuits and connections for
11185 "clientness"; instead, favor channel_is_client(). Part of
11187 - Extract the code for handling newly-open channels into a separate
11188 function from the general code to handle channel state
11189 transitions. This change simplifies our callgraph, reducing the
11190 size of the largest strongly connected component by roughly a
11191 factor of two. Closes ticket 22608.
11192 - Remove dead code for largely unused statistics on the number of
11193 times we've attempted various public key operations. Fixes bug
11194 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
11195 - Remove several now-obsolete functions for asking about old
11196 variants directory authority status. Closes ticket 22311; patch
11198 - Remove some of the code that once supported "Named" and "Unnamed"
11199 routers. Authorities no longer vote for these flags. Closes
11201 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
11202 and old hidden services, to indicate that they aren't suitable for
11203 new protocols or formats. Closes ticket 23026.
11204 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
11205 22521. Patch from Neel Chauhan.
11206 - Split the enormous circuit_send_next_onion_skin() function into
11207 multiple subfunctions. Closes ticket 22804.
11208 - Split the portions of the buffer.c module that handle particular
11209 protocols into separate modules. Part of ticket 23149.
11210 - Use our test macros more consistently, to produce more useful
11211 error messages when our unit tests fail. Add coccinelle patches to
11212 allow us to re-check for test macro uses. Closes ticket 22497.
11214 o Deprecated features:
11215 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
11216 now deprecated; they do not apply to relays, and they have had no
11217 effect on clients since 0.2.8.x. Closes ticket 19704.
11218 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
11219 only applies to direct unencrypted HTTP connections to your
11220 directory server, which your Tor probably isn't using. Closes
11224 - Add notes in man page regarding OS support for the various
11225 scheduler types. Attempt to use less jargon in the scheduler
11226 section. Closes ticket 24254.
11227 - Clarify that the Address option is entirely about setting an
11228 advertised IPv4 address. Closes ticket 18891.
11229 - Clarify the manpage's use of the term "address" to clarify what
11230 kind of address is intended. Closes ticket 21405.
11231 - Document that onion service subdomains are allowed, and ignored.
11232 Closes ticket 18736.
11233 - Clarify in the manual that "Sandbox 1" is only supported on Linux
11234 kernels. Closes ticket 22677.
11235 - Document all values of PublishServerDescriptor in the manpage.
11236 Closes ticket 15645.
11237 - Improve the documentation for the directory port part of the
11238 DirAuthority line. Closes ticket 20152.
11239 - Restore documentation for the authorities' "approved-routers"
11240 file. Closes ticket 21148.
11242 o Removed features:
11243 - The AllowDotExit option has been removed as unsafe. It has been
11244 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
11245 - The ClientDNSRejectInternalAddresses flag can no longer be set on
11246 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
11247 Closes ticket 21031.
11248 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
11249 nobody was using it any longer. Closes ticket 22377.
11252 Changes in version 0.3.1.9 - 2017-12-01:
11253 Tor 0.3.1.9 backports important security and stability fixes from the
11254 0.3.2 development series. All Tor users should upgrade to this
11255 release, or to another of the releases coming out today.
11257 o Major bugfixes (security, backport from 0.3.2.6-alpha):
11258 - Fix a denial of service bug where an attacker could use a
11259 malformed directory object to cause a Tor instance to pause while
11260 OpenSSL would try to read a passphrase from the terminal. (Tor
11261 instances run without a terminal, which is the case for most Tor
11262 packages, are not impacted.) Fixes bug 24246; bugfix on every
11263 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11264 Found by OSS-Fuzz as testcase 6360145429790720.
11265 - Fix a denial of service issue where an attacker could crash a
11266 directory authority using a malformed router descriptor. Fixes bug
11267 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
11269 - When checking for replays in the INTRODUCE1 cell data for a
11270 (legacy) onion service, correctly detect replays in the RSA-
11271 encrypted part of the cell. We were previously checking for
11272 replays on the entire cell, but those can be circumvented due to
11273 the malleability of Tor's legacy hybrid encryption. This fix helps
11274 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11275 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11278 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
11279 - Fix a use-after-free error that could crash v2 Tor onion services
11280 when they failed to open circuits while expiring introduction
11281 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
11282 also tracked as TROVE-2017-013 and CVE-2017-8823.
11284 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11285 - When running as a relay, make sure that we never build a path
11286 through ourselves, even in the case where we have somehow lost the
11287 version of our descriptor appearing in the consensus. Fixes part
11288 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
11289 as TROVE-2017-012 and CVE-2017-8822.
11290 - When running as a relay, make sure that we never choose ourselves
11291 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
11292 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
11294 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
11295 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
11296 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
11297 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
11298 identifying and finding a workaround to this bug and to Moritz,
11299 Arthur Edelstein, and Roger for helping to track it down and
11302 o Minor features (bridge):
11303 - Bridges now include notice in their descriptors that they are
11304 bridges, and notice of their distribution status, based on their
11305 publication settings. Implements ticket 18329. For more fine-
11306 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11309 o Minor features (directory authority, backport from 0.3.2.6-alpha):
11310 - Add an IPv6 address for the "bastet" directory authority. Closes
11313 o Minor features (geoip):
11314 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11317 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
11318 - Avoid unnecessary calls to directory_fetches_from_authorities() on
11319 relays, to prevent spurious address resolutions and descriptor
11320 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
11321 bugfix on in 0.2.8.1-alpha.
11323 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
11324 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
11325 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
11327 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
11328 - When a circuit is marked for close, do not attempt to package any
11329 cells for channels on that circuit. Previously, we would detect
11330 this condition lower in the call stack, when we noticed that the
11331 circuit had no attached channel, and log an annoying message.
11332 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
11334 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
11335 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
11336 so it matches dir-spec.txt. Fixes bug 24262; bugfix
11339 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
11340 - Avoid a crash when transitioning from client mode to bridge mode.
11341 Previously, we would launch the worker threads whenever our
11342 "public server" mode changed, but not when our "server" mode
11343 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
11346 Changes in version 0.3.0.13 - 2017-12-01
11347 Tor 0.3.0.13 backports important security and stability bugfixes from
11348 later Tor releases. All Tor users should upgrade to this release, or
11349 to another of the releases coming out today.
11351 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
11352 2018. If you need a release with long-term support, please stick with
11353 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11355 o Major bugfixes (security, backport from 0.3.2.6-alpha):
11356 - Fix a denial of service bug where an attacker could use a
11357 malformed directory object to cause a Tor instance to pause while
11358 OpenSSL would try to read a passphrase from the terminal. (Tor
11359 instances run without a terminal, which is the case for most Tor
11360 packages, are not impacted.) Fixes bug 24246; bugfix on every
11361 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11362 Found by OSS-Fuzz as testcase 6360145429790720.
11363 - Fix a denial of service issue where an attacker could crash a
11364 directory authority using a malformed router descriptor. Fixes bug
11365 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
11367 - When checking for replays in the INTRODUCE1 cell data for a
11368 (legacy) onion service, correctly detect replays in the RSA-
11369 encrypted part of the cell. We were previously checking for
11370 replays on the entire cell, but those can be circumvented due to
11371 the malleability of Tor's legacy hybrid encryption. This fix helps
11372 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11373 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11376 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
11377 - Fix a use-after-free error that could crash v2 Tor onion services
11378 when they failed to open circuits while expiring introduction
11379 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
11380 also tracked as TROVE-2017-013 and CVE-2017-8823.
11382 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11383 - When running as a relay, make sure that we never build a path
11384 through ourselves, even in the case where we have somehow lost the
11385 version of our descriptor appearing in the consensus. Fixes part
11386 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
11387 as TROVE-2017-012 and CVE-2017-8822.
11388 - When running as a relay, make sure that we never choose ourselves
11389 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
11390 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
11392 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
11393 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
11394 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
11395 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
11396 identifying and finding a workaround to this bug and to Moritz,
11397 Arthur Edelstein, and Roger for helping to track it down and
11400 o Minor features (security, windows, backport from 0.3.1.1-alpha):
11401 - Enable a couple of pieces of Windows hardening: one
11402 (HeapEnableTerminationOnCorruption) that has been on-by-default
11403 since Windows 8, and unavailable before Windows 7; and one
11404 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
11405 affect us, but shouldn't do any harm. Closes ticket 21953.
11407 o Minor features (bridge, backport from 0.3.1.9):
11408 - Bridges now include notice in their descriptors that they are
11409 bridges, and notice of their distribution status, based on their
11410 publication settings. Implements ticket 18329. For more fine-
11411 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11414 o Minor features (directory authority, backport from 0.3.2.6-alpha):
11415 - Add an IPv6 address for the "bastet" directory authority. Closes
11418 o Minor features (geoip):
11419 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11422 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
11423 - Avoid unnecessary calls to directory_fetches_from_authorities() on
11424 relays, to prevent spurious address resolutions and descriptor
11425 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
11426 bugfix on in 0.2.8.1-alpha.
11428 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
11429 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
11430 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
11432 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
11433 - When a circuit is marked for close, do not attempt to package any
11434 cells for channels on that circuit. Previously, we would detect
11435 this condition lower in the call stack, when we noticed that the
11436 circuit had no attached channel, and log an annoying message.
11437 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
11439 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
11440 - Avoid a crash when transitioning from client mode to bridge mode.
11441 Previously, we would launch the worker threads whenever our
11442 "public server" mode changed, but not when our "server" mode
11443 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
11445 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
11446 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
11447 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
11450 Changes in version 0.2.9.14 - 2017-12-01
11451 Tor 0.3.0.13 backports important security and stability bugfixes from
11452 later Tor releases. All Tor users should upgrade to this release, or
11453 to another of the releases coming out today.
11455 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
11456 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
11457 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
11458 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
11459 identifying and finding a workaround to this bug and to Moritz,
11460 Arthur Edelstein, and Roger for helping to track it down and
11463 o Major bugfixes (security, backport from 0.3.2.6-alpha):
11464 - Fix a denial of service bug where an attacker could use a
11465 malformed directory object to cause a Tor instance to pause while
11466 OpenSSL would try to read a passphrase from the terminal. (Tor
11467 instances run without a terminal, which is the case for most Tor
11468 packages, are not impacted.) Fixes bug 24246; bugfix on every
11469 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11470 Found by OSS-Fuzz as testcase 6360145429790720.
11471 - Fix a denial of service issue where an attacker could crash a
11472 directory authority using a malformed router descriptor. Fixes bug
11473 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
11475 - When checking for replays in the INTRODUCE1 cell data for a
11476 (legacy) onion service, correctly detect replays in the RSA-
11477 encrypted part of the cell. We were previously checking for
11478 replays on the entire cell, but those can be circumvented due to
11479 the malleability of Tor's legacy hybrid encryption. This fix helps
11480 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11481 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11484 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
11485 - Fix a use-after-free error that could crash v2 Tor onion services
11486 when they failed to open circuits while expiring introduction
11487 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
11488 also tracked as TROVE-2017-013 and CVE-2017-8823.
11490 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11491 - When running as a relay, make sure that we never build a path
11492 through ourselves, even in the case where we have somehow lost the
11493 version of our descriptor appearing in the consensus. Fixes part
11494 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
11495 as TROVE-2017-012 and CVE-2017-8822.
11497 o Minor features (bridge, backport from 0.3.1.9):
11498 - Bridges now include notice in their descriptors that they are
11499 bridges, and notice of their distribution status, based on their
11500 publication settings. Implements ticket 18329. For more fine-
11501 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11504 o Minor features (directory authority, backport from 0.3.2.6-alpha):
11505 - Add an IPv6 address for the "bastet" directory authority. Closes
11508 o Minor features (geoip):
11509 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11512 o Minor features (security, windows, backport from 0.3.1.1-alpha):
11513 - Enable a couple of pieces of Windows hardening: one
11514 (HeapEnableTerminationOnCorruption) that has been on-by-default
11515 since Windows 8, and unavailable before Windows 7; and one
11516 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
11517 affect us, but shouldn't do any harm. Closes ticket 21953.
11519 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
11520 - Avoid unnecessary calls to directory_fetches_from_authorities() on
11521 relays, to prevent spurious address resolutions and descriptor
11522 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
11523 bugfix on in 0.2.8.1-alpha.
11525 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
11526 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
11527 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
11529 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
11530 - When a circuit is marked for close, do not attempt to package any
11531 cells for channels on that circuit. Previously, we would detect
11532 this condition lower in the call stack, when we noticed that the
11533 circuit had no attached channel, and log an annoying message.
11534 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
11536 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
11537 - Avoid a crash when transitioning from client mode to bridge mode.
11538 Previously, we would launch the worker threads whenever our
11539 "public server" mode changed, but not when our "server" mode
11540 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
11542 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
11543 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
11544 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
11547 Changes in version 0.2.8.17 - 2017-12-01
11548 Tor 0.2.8.17 backports important security and stability bugfixes from
11549 later Tor releases. All Tor users should upgrade to this release, or
11550 to another of the releases coming out today.
11552 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
11553 2018. If you need a release with long-term support, please upgrade with
11554 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11556 o Major bugfixes (security, backport from 0.3.2.6-alpha):
11557 - Fix a denial of service bug where an attacker could use a
11558 malformed directory object to cause a Tor instance to pause while
11559 OpenSSL would try to read a passphrase from the terminal. (Tor
11560 instances run without a terminal, which is the case for most Tor
11561 packages, are not impacted.) Fixes bug 24246; bugfix on every
11562 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11563 Found by OSS-Fuzz as testcase 6360145429790720.
11564 - When checking for replays in the INTRODUCE1 cell data for a
11565 (legacy) onion service, correctly detect replays in the RSA-
11566 encrypted part of the cell. We were previously checking for
11567 replays on the entire cell, but those can be circumvented due to
11568 the malleability of Tor's legacy hybrid encryption. This fix helps
11569 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11570 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11573 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
11574 - Fix a use-after-free error that could crash v2 Tor onion services
11575 when they failed to open circuits while expiring introduction
11576 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
11577 also tracked as TROVE-2017-013 and CVE-2017-8823.
11579 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11580 - When running as a relay, make sure that we never build a path through
11581 ourselves, even in the case where we have somehow lost the version of
11582 our descriptor appearing in the consensus. Fixes part of bug 21534;
11583 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
11586 o Minor features (bridge, backport from 0.3.1.9):
11587 - Bridges now include notice in their descriptors that they are
11588 bridges, and notice of their distribution status, based on their
11589 publication settings. Implements ticket 18329. For more fine-
11590 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11593 o Minor features (directory authority, backport from 0.3.2.6-alpha):
11594 - Add an IPv6 address for the "bastet" directory authority. Closes
11597 o Minor features (geoip):
11598 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11601 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
11602 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
11603 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
11606 Changes in version 0.2.5.16 - 2017-12-01
11607 Tor 0.2.5.13 backports important security and stability bugfixes from
11608 later Tor releases. All Tor users should upgrade to this release, or
11609 to another of the releases coming out today.
11611 Note: the Tor 0.2.5 series will no longer be supported after 1 May
11612 2018. If you need a release with long-term support, please upgrade to
11613 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11615 o Major bugfixes (security, backport from 0.3.2.6-alpha):
11616 - Fix a denial of service bug where an attacker could use a
11617 malformed directory object to cause a Tor instance to pause while
11618 OpenSSL would try to read a passphrase from the terminal. (Tor
11619 instances run without a terminal, which is the case for most Tor
11620 packages, are not impacted.) Fixes bug 24246; bugfix on every
11621 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
11622 Found by OSS-Fuzz as testcase 6360145429790720.
11623 - When checking for replays in the INTRODUCE1 cell data for a
11624 (legacy) onion service, correctly detect replays in the RSA-
11625 encrypted part of the cell. We were previously checking for
11626 replays on the entire cell, but those can be circumvented due to
11627 the malleability of Tor's legacy hybrid encryption. This fix helps
11628 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
11629 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
11632 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
11633 - When running as a relay, make sure that we never build a path
11634 through ourselves, even in the case where we have somehow lost the
11635 version of our descriptor appearing in the consensus. Fixes part
11636 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
11637 as TROVE-2017-012 and CVE-2017-8822.
11639 o Minor features (bridge, backport from 0.3.1.9):
11640 - Bridges now include notice in their descriptors that they are
11641 bridges, and notice of their distribution status, based on their
11642 publication settings. Implements ticket 18329. For more fine-
11643 grained control of how a bridge is distributed, upgrade to 0.3.2.x
11646 o Minor features (geoip):
11647 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
11651 Changes in version 0.2.5.15 - 2017-10-25
11652 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
11653 series. It also adds a new directory authority, Bastet.
11655 Note: the Tor 0.2.5 series will no longer be supported after 1 May
11656 2018. If you need a release with long-term support, please upgrade to
11657 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11659 o Directory authority changes:
11660 - Add "Bastet" as a ninth directory authority to the default list.
11661 Closes ticket 23910.
11662 - The directory authority "Longclaw" has changed its IP address.
11663 Closes ticket 23592.
11665 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
11666 - Avoid an assertion failure bug affecting our implementation of
11667 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11668 handling of "0xx" differs from what we had expected. Fixes bug
11669 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11671 o Minor features (geoip):
11672 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
11675 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
11676 - Fix a memset() off the end of an array when packing cells. This
11677 bug should be harmless in practice, since the corrupted bytes are
11678 still in the same structure, and are always padding bytes,
11679 ignored, or immediately overwritten, depending on compiler
11680 behavior. Nevertheless, because the memset()'s purpose is to make
11681 sure that any other cell-handling bugs can't expose bytes to the
11682 network, we need to fix it. Fixes bug 22737; bugfix on
11683 0.2.4.11-alpha. Fixes CID 1401591.
11685 o Build features (backport from 0.3.1.5-alpha):
11686 - Tor's repository now includes a Travis Continuous Integration (CI)
11687 configuration file (.travis.yml). This is meant to help new
11688 developers and contributors who fork Tor to a Github repository be
11689 better able to test their changes, and understand what we expect
11690 to pass. To use this new build feature, you must fork Tor to your
11691 Github account, then go into the "Integrations" menu in the
11692 repository settings for your fork and enable Travis, then push
11693 your changes. Closes ticket 22636.
11696 Changes in version 0.2.8.16 - 2017-10-25
11697 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
11698 series, including a bugfix for a crash issue that had affected relays
11699 under memory pressure. It also adds a new directory authority, Bastet.
11701 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
11702 2018. If you need a release with long-term support, please stick with
11703 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11705 o Directory authority changes:
11706 - Add "Bastet" as a ninth directory authority to the default list.
11707 Closes ticket 23910.
11708 - The directory authority "Longclaw" has changed its IP address.
11709 Closes ticket 23592.
11711 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
11712 - Fix a timing-based assertion failure that could occur when the
11713 circuit out-of-memory handler freed a connection's output buffer.
11714 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
11716 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
11717 - Remove longclaw's IPv6 address, as it will soon change. Authority
11718 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
11719 3/8 directory authorities with IPv6 addresses, but there are also
11720 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
11722 o Minor features (geoip):
11723 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
11727 Changes in version 0.2.9.13 - 2017-10-25
11728 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
11729 series, including a bugfix for a crash issue that had affected relays
11730 under memory pressure. It also adds a new directory authority, Bastet.
11732 o Directory authority changes:
11733 - Add "Bastet" as a ninth directory authority to the default list.
11734 Closes ticket 23910.
11735 - The directory authority "Longclaw" has changed its IP address.
11736 Closes ticket 23592.
11738 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
11739 - Fix a timing-based assertion failure that could occur when the
11740 circuit out-of-memory handler freed a connection's output buffer.
11741 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
11743 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
11744 - Remove longclaw's IPv6 address, as it will soon change. Authority
11745 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
11746 3/8 directory authorities with IPv6 addresses, but there are also
11747 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
11749 o Minor features (geoip):
11750 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
11753 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
11754 - When a directory authority rejects a descriptor or extrainfo with
11755 a given digest, mark that digest as undownloadable, so that we do
11756 not attempt to download it again over and over. We previously
11757 tried to avoid downloading such descriptors by other means, but we
11758 didn't notice if we accidentally downloaded one anyway. This
11759 behavior became problematic in 0.2.7.2-alpha, when authorities
11760 began pinning Ed25519 keys. Fixes bug 22349; bugfix
11763 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
11764 - Clear the address when node_get_prim_orport() returns early.
11765 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
11767 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
11768 - When running as a Windows service, set the ID of the main thread
11769 correctly. Failure to do so made us fail to send log messages to
11770 the controller in 0.2.1.16-rc, slowed down controller event
11771 delivery in 0.2.7.3-rc and later, and crash with an assertion
11772 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
11773 Patch and diagnosis from "Vort".
11776 Changes in version 0.3.0.12 - 2017-10-25
11777 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
11778 series, including a bugfix for a crash issue that had affected relays
11779 under memory pressure. It also adds a new directory authority, Bastet.
11781 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
11782 2018. If you need a release with long-term support, please stick with
11783 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
11785 o Directory authority changes:
11786 - Add "Bastet" as a ninth directory authority to the default list.
11787 Closes ticket 23910.
11788 - The directory authority "Longclaw" has changed its IP address.
11789 Closes ticket 23592.
11791 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
11792 - Fix a timing-based assertion failure that could occur when the
11793 circuit out-of-memory handler freed a connection's output buffer.
11794 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
11796 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
11797 - Remove longclaw's IPv6 address, as it will soon change. Authority
11798 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
11799 3/8 directory authorities with IPv6 addresses, but there are also
11800 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
11802 o Minor features (geoip):
11803 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
11806 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
11807 - When a directory authority rejects a descriptor or extrainfo with
11808 a given digest, mark that digest as undownloadable, so that we do
11809 not attempt to download it again over and over. We previously
11810 tried to avoid downloading such descriptors by other means, but we
11811 didn't notice if we accidentally downloaded one anyway. This
11812 behavior became problematic in 0.2.7.2-alpha, when authorities
11813 began pinning Ed25519 keys. Fixes bug 22349; bugfix
11816 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
11817 - Avoid a possible double close of a circuit by the intro point on
11818 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
11819 bugfix on 0.3.0.1-alpha.
11821 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
11822 - Clear the address when node_get_prim_orport() returns early.
11823 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
11825 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
11826 - When running as a Windows service, set the ID of the main thread
11827 correctly. Failure to do so made us fail to send log messages to
11828 the controller in 0.2.1.16-rc, slowed down controller event
11829 delivery in 0.2.7.3-rc and later, and crash with an assertion
11830 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
11831 Patch and diagnosis from "Vort".
11834 Changes in version 0.3.1.8 - 2017-10-25
11835 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
11836 It includes several bugfixes, including a bugfix for a crash issue
11837 that had affected relays under memory pressure. It also adds
11838 a new directory authority, Bastet.
11840 o Directory authority changes:
11841 - Add "Bastet" as a ninth directory authority to the default list.
11842 Closes ticket 23910.
11843 - The directory authority "Longclaw" has changed its IP address.
11844 Closes ticket 23592.
11846 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
11847 - Fix a timing-based assertion failure that could occur when the
11848 circuit out-of-memory handler freed a connection's output buffer.
11849 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
11851 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
11852 - Remove longclaw's IPv6 address, as it will soon change. Authority
11853 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
11854 3/8 directory authorities with IPv6 addresses, but there are also
11855 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
11857 o Minor features (geoip):
11858 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
11861 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
11862 - Fix a compilation warning when building with zstd support on
11863 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
11864 and fixed by Andreas Stieger.
11866 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
11867 - Handle a pathological case when decompressing Zstandard data when
11868 the output buffer size is zero. Fixes bug 23551; bugfix
11871 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
11872 - Remove the length limit on HTTP status lines that authorities can
11873 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
11875 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
11876 - Avoid a possible double close of a circuit by the intro point on
11877 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
11878 bugfix on 0.3.0.1-alpha.
11880 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
11881 - Clear the address when node_get_prim_orport() returns early.
11882 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
11884 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
11885 - Fix additional channelpadding unit test failures by using mocked
11886 time instead of actual time for all tests. Fixes bug 23608; bugfix
11890 Changes in version 0.2.8.15 - 2017-09-18
11891 Tor 0.2.8.15 backports a collection of bugfixes from later
11894 Most significantly, it includes a fix for TROVE-2017-008, a
11895 security bug that affects hidden services running with the
11896 SafeLogging option disabled. For more information, see
11897 https://trac.torproject.org/projects/tor/ticket/23490
11899 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
11900 2018. We suggest that you upgrade to the latest stable release if
11901 possible. If you can't, we recommend that you upgrade at least to
11902 0.2.9, which will be supported until 2020.
11904 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
11905 - Avoid an assertion failure bug affecting our implementation of
11906 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11907 handling of "0xx" differs from what we had expected. Fixes bug
11908 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11911 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
11914 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
11915 - Backport a fix for an "unused variable" warning that appeared
11916 in some versions of mingw. Fixes bug 22838; bugfix on
11919 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
11920 - Fix a memset() off the end of an array when packing cells. This
11921 bug should be harmless in practice, since the corrupted bytes are
11922 still in the same structure, and are always padding bytes,
11923 ignored, or immediately overwritten, depending on compiler
11924 behavior. Nevertheless, because the memset()'s purpose is to make
11925 sure that any other cell-handling bugs can't expose bytes to the
11926 network, we need to fix it. Fixes bug 22737; bugfix on
11927 0.2.4.11-alpha. Fixes CID 1401591.
11929 o Build features (backport from 0.3.1.5-alpha):
11930 - Tor's repository now includes a Travis Continuous Integration (CI)
11931 configuration file (.travis.yml). This is meant to help new
11932 developers and contributors who fork Tor to a Github repository be
11933 better able to test their changes, and understand what we expect
11934 to pass. To use this new build feature, you must fork Tor to your
11935 Github account, then go into the "Integrations" menu in the
11936 repository settings for your fork and enable Travis, then push
11937 your changes. Closes ticket 22636.
11940 Changes in version 0.2.9.12 - 2017-09-18
11941 Tor 0.2.9.12 backports a collection of bugfixes from later
11944 Most significantly, it includes a fix for TROVE-2017-008, a
11945 security bug that affects hidden services running with the
11946 SafeLogging option disabled. For more information, see
11947 https://trac.torproject.org/projects/tor/ticket/23490
11949 o Major features (security, backport from 0.3.0.2-alpha):
11950 - Change the algorithm used to decide DNS TTLs on client and server
11951 side, to better resist DNS-based correlation attacks like the
11952 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
11953 Feamster. Now relays only return one of two possible DNS TTL
11954 values, and clients are willing to believe DNS TTL values up to 3
11955 hours long. Closes ticket 19769.
11957 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
11958 - Fix a rare crash when sending a begin cell on a circuit whose
11959 linked directory connection had already been closed. Fixes bug
11960 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
11962 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
11963 - Fix a bug that prevented exit nodes from caching DNS records for
11964 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
11966 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
11967 - Fix a typo that had prevented TPROXY-based transparent proxying
11968 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
11969 Patch from "d4fq0fQAgoJ".
11971 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
11972 - Avoid an assertion failure bug affecting our implementation of
11973 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11974 handling of "0xx" differs from what we had expected. Fixes bug
11975 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11977 o Minor features (code style, backport from 0.3.1.3-alpha):
11978 - Add "Falls through" comments to our codebase, in order to silence
11979 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
11980 Stieger. Closes ticket 22446.
11982 o Minor features (geoip):
11983 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
11986 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
11987 - Roll over monthly accounting at the configured hour and minute,
11988 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
11989 Found by Andrey Karpov with PVS-Studio.
11991 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
11992 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
11993 bugfix on 0.2.8.1-alpha.
11994 - Fix warnings when building with libscrypt and openssl scrypt support
11995 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
11996 - When building with certain versions the mingw C header files, avoid
11997 float-conversion warnings when calling the C functions isfinite(),
11998 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
12000 o Minor bugfixes (compilation, backport from 0.3.1.7):
12001 - Avoid compiler warnings in the unit tests for running tor_sscanf()
12002 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
12004 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
12005 - Backport a fix for an "unused variable" warning that appeared
12006 in some versions of mingw. Fixes bug 22838; bugfix on
12009 o Minor bugfixes (controller, backport from 0.3.1.7):
12010 - Do not crash when receiving a HSPOST command with an empty body.
12011 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
12012 - Do not crash when receiving a POSTDESCRIPTOR command with an
12013 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
12015 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
12016 - Avoid Coverity build warnings related to our BUG() macro. By
12017 default, Coverity treats BUG() as the Linux kernel does: an
12018 instant abort(). We need to override that so our BUG() macro
12019 doesn't prevent Coverity from analyzing functions that use it.
12020 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
12022 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
12023 - Fix a memset() off the end of an array when packing cells. This
12024 bug should be harmless in practice, since the corrupted bytes are
12025 still in the same structure, and are always padding bytes,
12026 ignored, or immediately overwritten, depending on compiler
12027 behavior. Nevertheless, because the memset()'s purpose is to make
12028 sure that any other cell-handling bugs can't expose bytes to the
12029 network, we need to fix it. Fixes bug 22737; bugfix on
12030 0.2.4.11-alpha. Fixes CID 1401591.
12032 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
12033 - When setting the maximum number of connections allowed by the OS,
12034 always allow some extra file descriptors for other files. Fixes
12035 bug 22797; bugfix on 0.2.0.10-alpha.
12037 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
12038 - Avoid a sandbox failure when trying to re-bind to a socket and
12039 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
12041 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
12042 - Permit the fchmod system call, to avoid crashing on startup when
12043 starting with the seccomp2 sandbox and an unexpected set of
12044 permissions on the data directory or its contents. Fixes bug
12045 22516; bugfix on 0.2.5.4-alpha.
12047 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
12048 - Avoid a double-marked-circuit warning that could happen when we
12049 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
12052 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
12053 - Reject version numbers with non-numeric prefixes (such as +, -, or
12054 whitespace). Disallowing whitespace prevents differential version
12055 parsing between POSIX-based and Windows platforms. Fixes bug 21507
12056 and part of 21508; bugfix on 0.0.8pre1.
12058 o Build features (backport from 0.3.1.5-alpha):
12059 - Tor's repository now includes a Travis Continuous Integration (CI)
12060 configuration file (.travis.yml). This is meant to help new
12061 developers and contributors who fork Tor to a Github repository be
12062 better able to test their changes, and understand what we expect
12063 to pass. To use this new build feature, you must fork Tor to your
12064 Github account, then go into the "Integrations" menu in the
12065 repository settings for your fork and enable Travis, then push
12066 your changes. Closes ticket 22636.
12069 Changes in version 0.3.0.11 - 2017-09-18
12070 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
12073 Most significantly, it includes a fix for TROVE-2017-008, a
12074 security bug that affects hidden services running with the
12075 SafeLogging option disabled. For more information, see
12076 https://trac.torproject.org/projects/tor/ticket/23490
12078 o Minor features (code style, backport from 0.3.1.7):
12079 - Add "Falls through" comments to our codebase, in order to silence
12080 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
12081 Stieger. Closes ticket 22446.
12084 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
12087 o Minor bugfixes (compilation, backport from 0.3.1.7):
12088 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
12089 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
12091 o Minor bugfixes (controller, backport from 0.3.1.7):
12092 - Do not crash when receiving a HSPOST command with an empty body.
12093 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
12094 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
12095 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
12097 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
12098 - When setting the maximum number of connections allowed by the OS,
12099 always allow some extra file descriptors for other files. Fixes
12100 bug 22797; bugfix on 0.2.0.10-alpha.
12102 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
12103 - Remove a forgotten debugging message when an introduction point
12104 successfully establishes a hidden service prop224 circuit with
12106 - Change three other log_warn() for an introduction point to
12107 protocol warnings, because they can be failure from the network
12108 and are not relevant to the operator. Fixes bug 23078; bugfix on
12109 0.3.0.1-alpha and 0.3.0.2-alpha.
12112 Changes in version 0.3.1.7 - 2017-09-18
12113 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
12115 With the 0.3.1 series, Tor now serves and downloads directory
12116 information in more compact formats, to save on bandwidth overhead. It
12117 also contains a new padding system to resist netflow-based traffic
12118 analysis, and experimental support for building parts of Tor in Rust
12119 (though no parts of Tor are in Rust yet). There are also numerous
12120 small features, bugfixes on earlier release series, and groundwork for
12121 the hidden services revamp of 0.3.2.
12123 This release also includes a fix for TROVE-2017-008, a security bug
12124 that affects hidden services running with the SafeLogging option
12125 disabled. For more information, see
12126 https://trac.torproject.org/projects/tor/ticket/23490
12128 Per our stable release policy, we plan to support each stable release
12129 series for at least the next nine months, or for three months after
12130 the first stable release of the next series: whichever is longer. If
12131 you need a release with long-term support, we recommend that you stay
12132 with the 0.2.9 series.
12134 Below is a list of the changes since 0.3.0. For a list of all
12135 changes since 0.3.1.6-rc, see the ChangeLog file.
12137 o New dependencies:
12138 - To build with zstd and lzma support, Tor now requires the
12139 pkg-config tool at build time.
12141 o Major bugfixes (security, hidden services, loggging):
12142 - Fix a bug where we could log uninitialized stack when a certain
12143 hidden service error occurred while SafeLogging was disabled.
12144 Fixes bug #23490; bugfix on 0.2.7.2-alpha.
12145 This is also tracked as TROVE-2017-008 and CVE-2017-0380.
12147 o Major features (build system, continuous integration):
12148 - Tor's repository now includes a Travis Continuous Integration (CI)
12149 configuration file (.travis.yml). This is meant to help new
12150 developers and contributors who fork Tor to a Github repository be
12151 better able to test their changes, and understand what we expect
12152 to pass. To use this new build feature, you must fork Tor to your
12153 Github account, then go into the "Integrations" menu in the
12154 repository settings for your fork and enable Travis, then push
12155 your changes. Closes ticket 22636.
12157 o Major features (directory protocol):
12158 - Tor relays and authorities can now serve clients an abbreviated
12159 version of the consensus document, containing only the changes
12160 since an older consensus document that the client holds. Clients
12161 now request these documents when available. When both client and
12162 server use this new protocol, they will use far less bandwidth (up
12163 to 94% less) to keep the client's consensus up-to-date. Implements
12164 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
12165 - Tor can now compress directory traffic with lzma or with zstd
12166 compression algorithms, which can deliver better bandwidth
12167 performance. Because lzma is computationally expensive, it's only
12168 used for documents that can be compressed once and served many
12169 times. Support for these algorithms requires that tor is built
12170 with the libzstd and/or liblzma libraries available. Implements
12171 proposal 278; closes ticket 21662.
12172 - Relays now perform the more expensive compression operations, and
12173 consensus diff generation, in worker threads. This separation
12174 avoids delaying the main thread when a new consensus arrives.
12176 o Major features (experimental):
12177 - Tor can now build modules written in Rust. To turn this on, pass
12178 the "--enable-rust" flag to the configure script. It's not time to
12179 get excited yet: currently, there is no actual Rust functionality
12180 beyond some simple glue code, and a notice at startup to tell you
12181 that Rust is running. Still, we hope that programmers and
12182 packagers will try building Tor with Rust support, so that we can
12183 find issues and solve portability problems. Closes ticket 22106.
12185 o Major features (traffic analysis resistance):
12186 - Connections between clients and relays now send a padding cell in
12187 each direction every 1.5 to 9.5 seconds (tunable via consensus
12188 parameters). This padding will not resist specialized
12189 eavesdroppers, but it should be enough to make many ISPs' routine
12190 network flow logging less useful in traffic analysis against
12193 Padding is negotiated using Tor's link protocol, so both relays
12194 and clients must upgrade for this to take effect. Clients may
12195 still send padding despite the relay's version by setting
12196 ConnectionPadding 1 in torrc, and may disable padding by setting
12197 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
12198 users with the torrc option ReducedConnectionPadding. Implements
12199 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
12200 - Relays will publish 24 hour totals of padding and non-padding cell
12201 counts to their extra-info descriptors, unless PaddingStatistics 0
12202 is set in torrc. These 24 hour totals are also rounded to
12203 multiples of 10000.
12205 o Major bugfixes (hidden service, relay, security):
12206 - Fix a remotely triggerable assertion failure when a hidden service
12207 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
12208 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
12209 - Fix a remotely triggerable assertion failure caused by receiving a
12210 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12211 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12214 o Major bugfixes (path selection, security):
12215 - When choosing which guard to use for a circuit, avoid the exit's
12216 family along with the exit itself. Previously, the new guard
12217 selection logic avoided the exit, but did not consider its family.
12218 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
12219 006 and CVE-2017-0377.
12221 o Major bugfixes (connection usage):
12222 - We use NETINFO cells to try to determine if both relays involved
12223 in a connection will agree on the canonical status of that
12224 connection. We prefer the connections where this is the case for
12225 extend cells, and try to close connections where relays disagree
12226 on their canonical status early. Also, we now prefer the oldest
12227 valid connection for extend cells. These two changes should reduce
12228 the number of long-term connections that are kept open between
12229 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
12230 - Relays now log hourly statistics (look for
12231 "channel_check_for_duplicates" lines) on the total number of
12232 connections to other relays. If the number of connections per
12233 relay is unexpectedly large, this log message is at notice level.
12234 Otherwise it is at info.
12236 o Major bugfixes (entry guards):
12237 - When starting with an old consensus, do not add new entry guards
12238 unless the consensus is "reasonably live" (under 1 day old). Fixes
12239 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
12240 - Don't block bootstrapping when a primary bridge is offline and we
12241 can't get its descriptor. Fixes bug 22325; fixes one case of bug
12242 21969; bugfix on 0.3.0.3-alpha.
12244 o Major bugfixes (linux TPROXY support):
12245 - Fix a typo that had prevented TPROXY-based transparent proxying
12246 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
12247 Patch from "d4fq0fQAgoJ".
12249 o Major bugfixes (openbsd, denial-of-service):
12250 - Avoid an assertion failure bug affecting our implementation of
12251 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
12252 handling of "0xx" differs from what we had expected. Fixes bug
12253 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
12255 o Major bugfixes (relay, link handshake):
12256 - When performing the v3 link handshake on a TLS connection, report
12257 that we have the x509 certificate that we actually used on that
12258 connection, even if we have changed certificates since that
12259 connection was first opened. Previously, we would claim to have
12260 used our most recent x509 link certificate, which would sometimes
12261 make the link handshake fail. Fixes one case of bug 22460; bugfix
12264 o Major bugfixes (relays, key management):
12265 - Regenerate link and authentication certificates whenever the key
12266 that signs them changes; also, regenerate link certificates
12267 whenever the signed key changes. Previously, these processes were
12268 only weakly coupled, and we relays could (for minutes to hours)
12269 wind up with an inconsistent set of keys and certificates, which
12270 other relays would not accept. Fixes two cases of bug 22460;
12271 bugfix on 0.3.0.1-alpha.
12272 - When sending an Ed25519 signing->link certificate in a CERTS cell,
12273 send the certificate that matches the x509 certificate that we
12274 used on the TLS connection. Previously, there was a race condition
12275 if the TLS context rotated after we began the TLS handshake but
12276 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
12279 o Minor features (security, windows):
12280 - Enable a couple of pieces of Windows hardening: one
12281 (HeapEnableTerminationOnCorruption) that has been on-by-default
12282 since Windows 8, and unavailable before Windows 7; and one
12283 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
12284 affect us, but shouldn't do any harm. Closes ticket 21953.
12286 o Minor features (bridge authority):
12287 - Add "fingerprint" lines to the networkstatus-bridges file produced
12288 by bridge authorities. Closes ticket 22207.
12290 o Minor features (code style):
12291 - Add "Falls through" comments to our codebase, in order to silence
12292 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
12293 Stieger. Closes ticket 22446.
12295 o Minor features (config options):
12296 - Allow "%include" directives in torrc configuration files. These
12297 directives import the settings from other files, or from all the
12298 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
12299 - Make SAVECONF return an error when overwriting a torrc that has
12300 includes. Using SAVECONF with the FORCE option will allow it to
12301 overwrite torrc even if includes are used. Related to ticket 1922.
12302 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
12303 will work without the FORCE option. Related to ticket 1922.
12305 o Minor features (controller):
12306 - Warn the first time that a controller requests data in the long-
12307 deprecated 'GETINFO network-status' format. Closes ticket 21703.
12309 o Minor features (defaults):
12310 - The default value for UseCreateFast is now 0: clients which
12311 haven't yet received a consensus document will now use a proper
12312 ntor handshake to talk to their directory servers whenever they
12313 can. Closes ticket 21407.
12314 - Onion key rotation and expiry intervals are now defined as a
12315 network consensus parameter, per proposal 274. The default
12316 lifetime of an onion key is increased from 7 to 28 days. Old onion
12317 keys will expire after 7 days by default. This change will make
12318 consensus diffs much smaller, and save significant bandwidth.
12319 Closes ticket 21641.
12321 o Minor features (defensive programming):
12322 - Create a pair of consensus parameters, nf_pad_tor2web and
12323 nf_pad_single_onion, to disable netflow padding in the consensus
12324 for non-anonymous connections in case the overhead is high. Closes
12327 o Minor features (diagnostic):
12328 - Add a stack trace to the bug warnings that can be logged when
12329 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
12330 attempt for bug 23105.
12331 - Add logging messages to try to diagnose a rare bug that seems to
12332 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
12333 think this is happening because of incorrect system clocks, but
12334 we'd like to know for certain. Diagnostic for bug 22466.
12335 - Avoid an assertion failure, and log a better error message, when
12336 unable to remove a file from the consensus cache on Windows.
12337 Attempts to mitigate and diagnose bug 22752.
12339 o Minor features (directory authority):
12340 - Improve the message that authorities report to relays that present
12341 RSA/Ed25519 keypairs that conflict with previously pinned keys.
12342 Closes ticket 22348.
12344 o Minor features (directory cache, consensus diff):
12345 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
12346 operators with low-resource environments to adjust the number of
12347 consensuses they'll store and generate diffs from. Most cache
12348 operators should leave it unchanged. Helps to work around
12351 o Minor features (fallback directory list):
12352 - Update the fallback directory mirror whitelist and blacklist based
12353 on operator emails. Closes task 21121.
12354 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
12355 December 2016 (of which ~126 were still functional) with a list of
12356 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
12357 2017. Resolves ticket 21564.
12359 o Minor features (geoip):
12360 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
12363 o Minor features (hidden services, logging):
12364 - Log a message when a hidden service descriptor has fewer
12365 introduction points than specified in
12366 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
12367 - Log a message when a hidden service reaches its introduction point
12368 circuit limit, and when that limit is reset. Follow up to ticket
12369 21594; closes ticket 21622.
12370 - Warn user if multiple entries in EntryNodes and at least one
12371 HiddenService are used together. Pinning EntryNodes along with a
12372 hidden service can be possibly harmful; for instance see ticket
12373 14917 or 21155. Closes ticket 21155.
12375 o Minor features (linux seccomp2 sandbox):
12376 - We now have a document storage backend compatible with the Linux
12377 seccomp2 sandbox. This backend is used for consensus documents and
12378 diffs between them; in the long term, we'd like to use it for
12379 unparseable directory material too. Closes ticket 21645
12380 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
12381 from 1MB to 16MB. This was necessary with the glibc allocator in
12382 order to allow worker threads to allocate more memory -- which in
12383 turn is necessary because of our new use of worker threads for
12384 compression. Closes ticket 22096.
12386 o Minor features (logging):
12387 - Log files are no longer created world-readable by default.
12388 (Previously, most distributors would store the logs in a non-
12389 world-readable location to prevent inappropriate access. This
12390 change is an extra precaution.) Closes ticket 21729; patch
12393 o Minor features (performance):
12394 - Our Keccak (SHA-3) implementation now accesses memory more
12395 efficiently, especially on little-endian systems. Closes
12397 - Add an O(1) implementation of channel_find_by_global_id(), to
12398 speed some controller functions.
12400 o Minor features (relay, configuration):
12401 - The MyFamily option may now be repeated as many times as desired,
12402 for relays that want to configure large families. Closes ticket
12403 4998; patch by Daniel Pinto.
12405 o Minor features (relay, performance):
12406 - Always start relays with at least two worker threads, to prevent
12407 priority inversion on slow tasks. Part of the fix for bug 22883.
12408 - Allow background work to be queued with different priorities, so
12409 that a big pile of slow low-priority jobs will not starve out
12410 higher priority jobs. This lays the groundwork for a fix for
12413 o Minor features (safety):
12414 - Add an explicit check to extrainfo_parse_entry_from_string() for
12415 NULL inputs. We don't believe this can actually happen, but it may
12416 help silence a warning from the Clang analyzer. Closes
12419 o Minor features (testing):
12420 - Add more tests for compression backend initialization. Closes
12422 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
12423 When Tor is compiled with this option, we disable a number of
12424 redundant memory-safety failsafes that are intended to stop bugs
12425 from becoming security issues. This makes it easier to hunt for
12426 bugs that would be security issues without the failsafes turned
12427 on. Closes ticket 21439.
12428 - Add a general event-tracing instrumentation support to Tor. This
12429 subsystem will enable developers and researchers to add fine-
12430 grained instrumentation to their Tor instances, for use when
12431 examining Tor network performance issues. There are no trace
12432 events yet, and event-tracing is off by default unless enabled at
12433 compile time. Implements ticket 13802.
12434 - Improve our version parsing tests: add tests for typical version
12435 components, add tests for invalid versions, including numeric
12436 range and non-numeric prefixes. Unit tests 21278, 21450, and
12437 21507. Partially implements 21470.
12439 o Minor bugfixes (bandwidth accounting):
12440 - Roll over monthly accounting at the configured hour and minute,
12441 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
12442 Found by Andrey Karpov with PVS-Studio.
12444 o Minor bugfixes (code correctness):
12445 - Accurately identify client connections by their lack of peer
12446 authentication. This means that we bail out earlier if asked to
12447 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
12450 o Minor bugfixes (compilation warnings):
12451 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
12452 22915; bugfix on 0.2.8.1-alpha.
12453 - Fix warnings when building with libscrypt and openssl scrypt
12454 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
12455 - When building with certain versions of the mingw C header files,
12456 avoid float-conversion warnings when calling the C functions
12457 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
12460 o Minor bugfixes (compilation):
12461 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
12462 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
12464 o Minor bugfixes (compression):
12465 - When spooling compressed data to an output buffer, don't try to
12466 spool more data when there is no more data to spool and we are not
12467 trying to flush the input. Previously, we would sometimes launch
12468 compression requests with nothing to do, which interferes with our
12469 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
12471 o Minor bugfixes (configuration):
12472 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
12473 bug 22252; bugfix on 0.2.9.3-alpha.
12475 o Minor bugfixes (connection lifespan):
12476 - Allow more control over how long TLS connections are kept open:
12477 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
12478 single option called CircuitsAvailableTimeout. Also, allow the
12479 consensus to control the default values for both this preference
12480 and the lifespan of relay-to-relay connections. Fixes bug 17592;
12481 bugfix on 0.2.5.5-alpha.
12482 - Increase the initial circuit build timeout testing frequency, to
12483 help ensure that ReducedConnectionPadding clients finish learning
12484 a timeout before their orconn would expire. The initial testing
12485 rate was set back in the days of TAP and before the Tor Browser
12486 updater, when we had to be much more careful about new clients
12487 making lots of circuits. With this change, a circuit build timeout
12488 is learned in about 15-20 minutes, instead of 100-120 minutes.
12490 o Minor bugfixes (controller):
12491 - Do not crash when receiving a HSPOST command with an empty body.
12492 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
12493 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
12494 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
12495 - GETINFO onions/current and onions/detached no longer respond with
12496 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
12497 - Trigger HS descriptor events on the control port when the client
12498 fails to pick a hidden service directory for a hidden service.
12499 This can happen if all the hidden service directories are in
12500 ExcludeNodes, or they have all been queried within the last 15
12501 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
12503 o Minor bugfixes (correctness):
12504 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12505 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12507 o Minor bugfixes (coverity build support):
12508 - Avoid Coverity build warnings related to our BUG() macro. By
12509 default, Coverity treats BUG() as the Linux kernel does: an
12510 instant abort(). We need to override that so our BUG() macro
12511 doesn't prevent Coverity from analyzing functions that use it.
12512 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
12514 o Minor bugfixes (defensive programming):
12515 - Detect and break out of infinite loops in our compression code. We
12516 don't think that any such loops exist now, but it's best to be
12517 safe. Closes ticket 22672.
12518 - Fix a memset() off the end of an array when packing cells. This
12519 bug should be harmless in practice, since the corrupted bytes are
12520 still in the same structure, and are always padding bytes,
12521 ignored, or immediately overwritten, depending on compiler
12522 behavior. Nevertheless, because the memset()'s purpose is to make
12523 sure that any other cell-handling bugs can't expose bytes to the
12524 network, we need to fix it. Fixes bug 22737; bugfix on
12525 0.2.4.11-alpha. Fixes CID 1401591.
12527 o Minor bugfixes (directory authority):
12528 - When a directory authority rejects a descriptor or extrainfo with
12529 a given digest, mark that digest as undownloadable, so that we do
12530 not attempt to download it again over and over. We previously
12531 tried to avoid downloading such descriptors by other means, but we
12532 didn't notice if we accidentally downloaded one anyway. This
12533 behavior became problematic in 0.2.7.2-alpha, when authorities
12534 began pinning Ed25519 keys. Fixes bug 22349; bugfix
12536 - When rejecting a router descriptor for running an obsolete version
12537 of Tor without ntor support, warn about the obsolete tor version,
12538 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
12539 - Prevent the shared randomness subsystem from asserting when
12540 initialized by a bridge authority with an incomplete configuration
12541 file. Fixes bug 21586; bugfix on 0.2.9.8.
12543 o Minor bugfixes (error reporting, windows):
12544 - When formatting Windows error messages, use the English format to
12545 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
12548 o Minor bugfixes (exit-side DNS):
12549 - Fix an untriggerable assertion that checked the output of a
12550 libevent DNS error, so that the assertion actually behaves as
12551 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
12552 Karpov using PVS-Studio.
12554 o Minor bugfixes (fallback directories):
12555 - Make the usage example in updateFallbackDirs.py actually work, and
12556 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
12557 - Decrease the guard flag average required to be a fallback. This
12558 allows us to keep relays that have their guard flag removed when
12559 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
12560 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
12561 bugfix on 0.2.8.1-alpha.
12562 - Make sure fallback directory mirrors have the same address, port,
12563 and relay identity key for at least 30 days before they are
12564 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
12566 o Minor bugfixes (file limits, osx):
12567 - When setting the maximum number of connections allowed by the OS,
12568 always allow some extra file descriptors for other files. Fixes
12569 bug 22797; bugfix on 0.2.0.10-alpha.
12571 o Minor bugfixes (hidden services):
12572 - Increase the number of circuits that a service is allowed to
12573 open over a specific period of time. The value was lower than it
12574 should be (8 vs 12) in the normal case of 3 introduction points.
12575 Fixes bug 22159; bugfix on 0.3.0.5-rc.
12576 - Fix a BUG warning during HSv3 descriptor decoding that could be
12577 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
12578 on 0.3.0.1-alpha. Bug found by "haxxpop".
12579 - Stop printing a cryptic warning when a hidden service gets a
12580 request to connect to a virtual port that it hasn't configured.
12581 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
12582 - Simplify hidden service descriptor creation by using an existing
12583 flag to check if an introduction point is established. Fixes bug
12584 21599; bugfix on 0.2.7.2-alpha.
12586 o Minor bugfixes (link handshake):
12587 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
12588 months, and regenerate it when it is within one month of expiring.
12589 Previously, we had generated this certificate at startup with a
12590 ten-year lifetime, but that could lead to weird behavior when Tor
12591 was started with a grossly inaccurate clock. Mitigates bug 22466;
12592 mitigation on 0.3.0.1-alpha.
12594 o Minor bugfixes (linux seccomp2 sandbox):
12595 - Avoid a sandbox failure when trying to re-bind to a socket and
12596 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
12597 - Permit the fchmod system call, to avoid crashing on startup when
12598 starting with the seccomp2 sandbox and an unexpected set of
12599 permissions on the data directory or its contents. Fixes bug
12600 22516; bugfix on 0.2.5.4-alpha.
12602 o Minor bugfixes (logging):
12603 - When decompressing, do not warn if we fail to decompress using a
12604 compression method that we merely guessed. Fixes part of bug
12605 22670; bugfix on 0.1.1.14-alpha.
12606 - When decompressing, treat mismatch between content-encoding and
12607 actual compression type as a protocol warning. Fixes part of bug
12608 22670; bugfix on 0.1.1.9-alpha.
12609 - Downgrade "assigned_to_cpuworker failed" message to info-level
12610 severity. In every case that can reach it, either a better warning
12611 has already been logged, or no warning is warranted. Fixes bug
12612 22356; bugfix on 0.2.6.3-alpha.
12613 - Log a better message when a directory authority replies to an
12614 upload with an unexpected status code. Fixes bug 11121; bugfix
12616 - Downgrade a log statement about unexpected relay cells from "bug"
12617 to "protocol warning", because there is at least one use case
12618 where it can be triggered by a buggy tor implementation. Fixes bug
12619 21293; bugfix on 0.1.1.14-alpha.
12621 o Minor bugfixes (logging, relay):
12622 - Remove a forgotten debugging message when an introduction point
12623 successfully establishes a hidden service prop224 circuit with
12625 - Change three other log_warn() for an introduction point to
12626 protocol warnings, because they can be failure from the network
12627 and are not relevant to the operator. Fixes bug 23078; bugfix on
12628 0.3.0.1-alpha and 0.3.0.2-alpha.
12630 o Minor bugfixes (relay):
12631 - Inform the geoip and rephist modules about all requests, even on
12632 relays that are only fetching microdescriptors. Fixes a bug
12633 related to 21585; bugfix on 0.3.0.1-alpha.
12635 o Minor bugfixes (memory leaks):
12636 - Fix a small memory leak at exit from the backtrace handler code.
12637 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
12638 - When directory authorities reject a router descriptor due to
12639 keypinning, free the router descriptor rather than leaking the
12640 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
12641 - Fix a small memory leak when validating a configuration that uses
12642 two or more AF_UNIX sockets for the same port type. Fixes bug
12643 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
12645 o Minor bugfixes (process behavior):
12646 - When exiting because of an error, always exit with a nonzero exit
12647 status. Previously, we would fail to report an error in our exit
12648 status in cases related to __OwningControllerProcess failure,
12649 lockfile contention, and Ed25519 key initialization. Fixes bug
12650 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
12651 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
12654 o Minor bugfixes (robustness, error handling):
12655 - Improve our handling of the cases where OpenSSL encounters a
12656 memory error while encoding keys and certificates. We haven't
12657 observed these errors in the wild, but if they do happen, we now
12658 detect and respond better. Fixes bug 19418; bugfix on all versions
12659 of Tor. Reported by Guido Vranken.
12661 o Minor bugfixes (testing):
12662 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
12663 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
12664 - Use unbuffered I/O for utility functions around the
12665 process_handle_t type. This fixes unit test failures reported on
12666 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
12667 - Make display of captured unit test log messages consistent. Fixes
12668 bug 21510; bugfix on 0.2.9.3-alpha.
12669 - Make test-network.sh always call chutney's test-network.sh.
12670 Previously, this only worked on systems which had bash installed,
12671 due to some bash-specific code in the script. Fixes bug 19699;
12672 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
12673 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
12674 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
12675 - The unit tests now pass on systems where localhost is misconfigured
12676 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
12679 o Minor bugfixes (voting consistency):
12680 - Reject version numbers with non-numeric prefixes (such as +, -, or
12681 whitespace). Disallowing whitespace prevents differential version
12682 parsing between POSIX-based and Windows platforms. Fixes bug 21507
12683 and part of 21508; bugfix on 0.0.8pre1.
12685 o Minor bugfixes (Windows service):
12686 - When running as a Windows service, set the ID of the main thread
12687 correctly. Failure to do so made us fail to send log messages to
12688 the controller in 0.2.1.16-rc, slowed down controller event
12689 delivery in 0.2.7.3-rc and later, and crash with an assertion
12690 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
12691 Patch and diagnosis from "Vort".
12693 o Minor bugfixes (windows, relay):
12694 - Resolve "Failure from drain_fd: No error" warnings on Windows
12695 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
12697 o Code simplification and refactoring:
12698 - Break up the 630-line function connection_dir_client_reached_eof()
12699 into a dozen smaller functions. This change should help
12700 maintainability and readability of the client directory code.
12701 - Isolate our use of the openssl headers so that they are only
12702 included from our crypto wrapper modules, and from tests that
12703 examine those modules' internals. Closes ticket 21841.
12704 - Simplify our API to launch directory requests, making it more
12705 extensible and less error-prone. Now it's easier to add extra
12706 headers to directory requests. Closes ticket 21646.
12707 - Our base64 decoding functions no longer overestimate the output
12708 space that they need when parsing unpadded inputs. Closes
12710 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
12711 Resolves ticket 22213.
12712 - The logic that directory caches use to spool request to clients,
12713 serving them one part at a time so as not to allocate too much
12714 memory, has been refactored for consistency. Previously there was
12715 a separate spooling implementation per type of spoolable data. Now
12716 there is one common spooling implementation, with extensible data
12717 types. Closes ticket 21651.
12718 - Tor's compression module now supports multiple backends. Part of
12719 the implementation for proposal 278; closes ticket 21663.
12722 - Add a manpage description for the key-pinning-journal file. Closes
12724 - Correctly note that bandwidth accounting values are stored in the
12725 state file, and the bw_accounting file is now obsolete. Closes
12727 - Document more of the files in the Tor data directory, including
12728 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
12729 approved-routers, sr-random, and diff-cache. Found while fixing
12731 - Clarify the manpage for the (deprecated) torify script. Closes
12733 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
12734 Closes ticket 21873.
12735 - Correct documentation about the default DataDirectory value.
12736 Closes ticket 21151.
12737 - Document the default behavior of NumEntryGuards and
12738 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
12740 - Document key=value pluggable transport arguments for Bridge lines
12741 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
12742 - Note that bandwidth-limiting options don't affect TCP headers or
12743 DNS. Closes ticket 17170.
12745 o Removed features (configuration options, all in ticket 22060):
12746 - These configuration options are now marked Obsolete, and no longer
12747 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
12748 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
12749 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
12750 in 0.2.9.2-alpha and have now been removed. The previous default
12751 behavior is now always chosen; the previous (less secure) non-
12752 default behavior is now unavailable.
12753 - CloseHSClientCircuitsImmediatelyOnTimeout and
12754 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
12755 0.2.9.2-alpha and now have been removed. HS circuits never close
12756 on circuit build timeout; they have a longer timeout period.
12757 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
12758 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
12759 (and others) to configure listen-only and advertise-only addresses.
12761 o Removed features (tools):
12762 - We've removed the tor-checkkey tool from src/tools. Long ago, we
12763 used it to help people detect RSA keys that were generated by
12764 versions of Debian affected by CVE-2008-0166. But those keys have
12765 been out of circulation for ages, and this tool is no longer
12766 required. Closes ticket 21842.
12769 Changes in version 0.3.0.10 - 2017-08-02
12770 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
12771 from the current Tor alpha series. OpenBSD users and TPROXY users
12772 should upgrade; others are probably okay sticking with 0.3.0.9.
12774 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
12775 - Tor's repository now includes a Travis Continuous Integration (CI)
12776 configuration file (.travis.yml). This is meant to help new
12777 developers and contributors who fork Tor to a Github repository be
12778 better able to test their changes, and understand what we expect
12779 to pass. To use this new build feature, you must fork Tor to your
12780 Github account, then go into the "Integrations" menu in the
12781 repository settings for your fork and enable Travis, then push
12782 your changes. Closes ticket 22636.
12784 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
12785 - Fix a typo that had prevented TPROXY-based transparent proxying
12786 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
12787 Patch from "d4fq0fQAgoJ".
12789 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
12790 - Avoid an assertion failure bug affecting our implementation of
12791 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
12792 handling of "0xbar" differs from what we had expected. Fixes bug
12793 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
12795 o Minor features (backport from 0.3.1.5-alpha):
12796 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
12799 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
12800 - Roll over monthly accounting at the configured hour and minute,
12801 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
12802 Found by Andrey Karpov with PVS-Studio.
12804 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
12805 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
12806 bugfix on 0.2.8.1-alpha.
12807 - Fix warnings when building with libscrypt and openssl scrypt
12808 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
12809 - When building with certain versions of the mingw C header files,
12810 avoid float-conversion warnings when calling the C functions
12811 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
12814 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
12815 - Backport a fix for an "unused variable" warning that appeared
12816 in some versions of mingw. Fixes bug 22838; bugfix on
12819 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
12820 - Avoid Coverity build warnings related to our BUG() macro. By
12821 default, Coverity treats BUG() as the Linux kernel does: an
12822 instant abort(). We need to override that so our BUG() macro
12823 doesn't prevent Coverity from analyzing functions that use it.
12824 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
12826 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
12827 - When rejecting a router descriptor for running an obsolete version
12828 of Tor without ntor support, warn about the obsolete tor version,
12829 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
12831 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
12832 - Avoid a sandbox failure when trying to re-bind to a socket and
12833 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
12835 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
12836 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
12837 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
12840 Changes in version 0.3.0.9 - 2017-06-29
12841 Tor 0.3.0.9 fixes a path selection bug that would allow a client
12842 to use a guard that was in the same network family as a chosen exit
12843 relay. This is a security regression; all clients running earlier
12844 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
12847 This release also backports several other bugfixes from the 0.3.1.x
12850 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
12851 - When choosing which guard to use for a circuit, avoid the exit's
12852 family along with the exit itself. Previously, the new guard
12853 selection logic avoided the exit, but did not consider its family.
12854 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
12855 006 and CVE-2017-0377.
12857 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
12858 - Don't block bootstrapping when a primary bridge is offline and we
12859 can't get its descriptor. Fixes bug 22325; fixes one case of bug
12860 21969; bugfix on 0.3.0.3-alpha.
12862 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
12863 - When starting with an old consensus, do not add new entry guards
12864 unless the consensus is "reasonably live" (under 1 day old). Fixes
12865 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
12867 o Minor features (geoip):
12868 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
12871 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
12872 - Reject version numbers with non-numeric prefixes (such as +, -, or
12873 whitespace). Disallowing whitespace prevents differential version
12874 parsing between POSIX-based and Windows platforms. Fixes bug 21507
12875 and part of 21508; bugfix on 0.0.8pre1.
12877 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
12878 - Permit the fchmod system call, to avoid crashing on startup when
12879 starting with the seccomp2 sandbox and an unexpected set of
12880 permissions on the data directory or its contents. Fixes bug
12881 22516; bugfix on 0.2.5.4-alpha.
12883 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
12884 - Fix a memset() off the end of an array when packing cells. This
12885 bug should be harmless in practice, since the corrupted bytes are
12886 still in the same structure, and are always padding bytes,
12887 ignored, or immediately overwritten, depending on compiler
12888 behavior. Nevertheless, because the memset()'s purpose is to make
12889 sure that any other cell-handling bugs can't expose bytes to the
12890 network, we need to fix it. Fixes bug 22737; bugfix on
12891 0.2.4.11-alpha. Fixes CID 1401591.
12894 Changes in version 0.3.0.8 - 2017-06-08
12895 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
12896 remotely crash a hidden service with an assertion failure. Anyone
12897 running a hidden service should upgrade to this version, or to some
12898 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
12900 Tor 0.3.0.8 also includes fixes for several key management bugs
12901 that sometimes made relays unreliable, as well as several other
12902 bugfixes described below.
12904 o Major bugfixes (hidden service, relay, security, backport
12905 from 0.3.1.3-alpha):
12906 - Fix a remotely triggerable assertion failure when a hidden service
12907 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
12908 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
12909 - Fix a remotely triggerable assertion failure caused by receiving a
12910 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12911 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12914 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
12915 - When performing the v3 link handshake on a TLS connection, report
12916 that we have the x509 certificate that we actually used on that
12917 connection, even if we have changed certificates since that
12918 connection was first opened. Previously, we would claim to have
12919 used our most recent x509 link certificate, which would sometimes
12920 make the link handshake fail. Fixes one case of bug 22460; bugfix
12923 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
12924 - Regenerate link and authentication certificates whenever the key
12925 that signs them changes; also, regenerate link certificates
12926 whenever the signed key changes. Previously, these processes were
12927 only weakly coupled, and we relays could (for minutes to hours)
12928 wind up with an inconsistent set of keys and certificates, which
12929 other relays would not accept. Fixes two cases of bug 22460;
12930 bugfix on 0.3.0.1-alpha.
12931 - When sending an Ed25519 signing->link certificate in a CERTS cell,
12932 send the certificate that matches the x509 certificate that we
12933 used on the TLS connection. Previously, there was a race condition
12934 if the TLS context rotated after we began the TLS handshake but
12935 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
12938 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
12939 - Stop rejecting v3 hidden service descriptors because their size
12940 did not match an old padding rule. Fixes bug 22447; bugfix on
12943 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
12944 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
12945 December 2016 (of which ~126 were still functional) with a list of
12946 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
12947 2017. Resolves ticket 21564.
12949 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
12950 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
12951 bug 22252; bugfix on 0.2.9.3-alpha.
12953 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
12954 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12955 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12957 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
12958 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
12959 months, and regenerate it when it is within one month of expiring.
12960 Previously, we had generated this certificate at startup with a
12961 ten-year lifetime, but that could lead to weird behavior when Tor
12962 was started with a grossly inaccurate clock. Mitigates bug 22466;
12963 mitigation on 0.3.0.1-alpha.
12965 o Minor bugfixes (memory leak, directory authority, backport from
12967 - When directory authorities reject a router descriptor due to
12968 keypinning, free the router descriptor rather than leaking the
12969 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
12972 Changes in version 0.2.9.11 - 2017-06-08
12973 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
12974 remotely crash a hidden service with an assertion failure. Anyone
12975 running a hidden service should upgrade to this version, or to some
12976 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
12977 are not affected by TROVE-2017-004.)
12979 Tor 0.2.9.11 also backports fixes for several key management bugs
12980 that sometimes made relays unreliable, as well as several other
12981 bugfixes described below.
12983 o Major bugfixes (hidden service, relay, security, backport
12984 from 0.3.1.3-alpha):
12985 - Fix a remotely triggerable assertion failure caused by receiving a
12986 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12987 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12990 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
12991 - When performing the v3 link handshake on a TLS connection, report
12992 that we have the x509 certificate that we actually used on that
12993 connection, even if we have changed certificates since that
12994 connection was first opened. Previously, we would claim to have
12995 used our most recent x509 link certificate, which would sometimes
12996 make the link handshake fail. Fixes one case of bug 22460; bugfix
12999 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
13000 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
13001 December 2016 (of which ~126 were still functional) with a list of
13002 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
13003 2017. Resolves ticket 21564.
13005 o Minor features (future-proofing, backport from 0.3.0.7):
13006 - Tor no longer refuses to download microdescriptors or descriptors if
13007 they are listed as "published in the future". This change will
13008 eventually allow us to stop listing meaningful "published" dates
13009 in microdescriptor consensuses, and thereby allow us to reduce the
13010 resources required to download consensus diffs by over 50%.
13011 Implements part of ticket 21642; implements part of proposal 275.
13013 o Minor features (directory authorities, backport from 0.3.0.4-rc)
13014 - Directory authorities now reject relays running versions
13015 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
13016 suffer from bug 20499 and don't keep their consensus cache
13017 up-to-date. Resolves ticket 20509.
13019 o Minor features (geoip):
13020 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
13023 o Minor bugfixes (control port, backport from 0.3.0.6):
13024 - The GETINFO extra-info/digest/<digest> command was broken because
13025 of a wrong base16 decode return value check, introduced when
13026 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
13028 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
13029 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13030 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13032 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
13033 - The getpid() system call is now permitted under the Linux seccomp2
13034 sandbox, to avoid crashing with versions of OpenSSL (and other
13035 libraries) that attempt to learn the process's PID by using the
13036 syscall rather than the VDSO code. Fixes bug 21943; bugfix
13039 o Minor bugfixes (memory leak, directory authority, backport
13040 from 0.3.1.2-alpha):
13041 - When directory authorities reject a router descriptor due to
13042 keypinning, free the router descriptor rather than leaking the
13043 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
13045 Changes in version 0.2.8.14 - 2017-06-08
13046 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
13047 remotely crash a hidden service with an assertion failure. Anyone
13048 running a hidden service should upgrade to this version, or to some
13049 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
13050 are not affected by TROVE-2017-004.)
13052 o Major bugfixes (hidden service, relay, security):
13053 - Fix a remotely triggerable assertion failure caused by receiving a
13054 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13055 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13058 o Minor features (geoip):
13059 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
13062 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
13063 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
13064 December 2016 (of which ~126 were still functional) with a list of
13065 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
13066 2017. Resolves ticket 21564.
13068 o Minor bugfixes (correctness):
13069 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13070 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13072 Changes in version 0.2.7.8 - 2017-06-08
13073 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
13074 remotely crash a hidden service with an assertion failure. Anyone
13075 running a hidden service should upgrade to this version, or to some
13076 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
13077 are not affected by TROVE-2017-004.)
13079 o Major bugfixes (hidden service, relay, security):
13080 - Fix a remotely triggerable assertion failure caused by receiving a
13081 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13082 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13085 o Minor features (geoip):
13086 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
13089 o Minor bugfixes (correctness):
13090 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13091 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13094 Changes in version 0.2.6.12 - 2017-06-08
13095 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
13096 remotely crash a hidden service with an assertion failure. Anyone
13097 running a hidden service should upgrade to this version, or to some
13098 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
13099 are not affected by TROVE-2017-004.)
13101 o Major bugfixes (hidden service, relay, security):
13102 - Fix a remotely triggerable assertion failure caused by receiving a
13103 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13104 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13107 o Minor features (geoip):
13108 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
13111 o Minor bugfixes (correctness):
13112 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13113 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13115 Changes in version 0.2.5.14 - 2017-06-08
13116 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
13117 remotely crash a hidden service with an assertion failure. Anyone
13118 running a hidden service should upgrade to this version, or to some
13119 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
13120 are not affected by TROVE-2017-004.)
13122 o Major bugfixes (hidden service, relay, security):
13123 - Fix a remotely triggerable assertion failure caused by receiving a
13124 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13125 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13128 o Minor features (geoip):
13129 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
13132 o Minor bugfixes (correctness):
13133 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13134 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13136 Changes in version 0.2.4.29 - 2017-06-08
13137 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
13138 remotely crash a hidden service with an assertion failure. Anyone
13139 running a hidden service should upgrade to this version, or to some
13140 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
13141 are not affected by TROVE-2017-004.)
13143 o Major bugfixes (hidden service, relay, security):
13144 - Fix a remotely triggerable assertion failure caused by receiving a
13145 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
13146 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
13149 o Minor features (geoip):
13150 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
13153 o Minor bugfixes (correctness):
13154 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
13155 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
13158 Changes in version 0.3.0.7 - 2017-05-15
13159 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
13160 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
13161 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
13162 clients are not affected.
13164 o Major bugfixes (hidden service directory, security):
13165 - Fix an assertion failure in the hidden service directory code, which
13166 could be used by an attacker to remotely cause a Tor relay process to
13167 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
13168 should upgrade. This security issue is tracked as TROVE-2017-002.
13169 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
13172 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
13175 o Minor features (future-proofing):
13176 - Tor no longer refuses to download microdescriptors or descriptors
13177 if they are listed as "published in the future". This change will
13178 eventually allow us to stop listing meaningful "published" dates
13179 in microdescriptor consensuses, and thereby allow us to reduce the
13180 resources required to download consensus diffs by over 50%.
13181 Implements part of ticket 21642; implements part of proposal 275.
13183 o Minor bugfixes (Linux seccomp2 sandbox):
13184 - The getpid() system call is now permitted under the Linux seccomp2
13185 sandbox, to avoid crashing with versions of OpenSSL (and other
13186 libraries) that attempt to learn the process's PID by using the
13187 syscall rather than the VDSO code. Fixes bug 21943; bugfix
13191 Changes in version 0.3.0.6 - 2017-04-26
13192 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
13194 With the 0.3.0 series, clients and relays now use Ed25519 keys to
13195 authenticate their link connections to relays, rather than the old
13196 RSA1024 keys that they used before. (Circuit crypto has been
13197 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
13198 the guard selection and replacement algorithm to behave more robustly
13199 in the presence of unreliable networks, and to resist guard-
13202 This series also includes numerous other small features and bugfixes,
13203 along with more groundwork for the upcoming hidden-services revamp.
13205 Per our stable release policy, we plan to support the Tor 0.3.0
13206 release series for at least the next nine months, or for three months
13207 after the first stable release of the 0.3.1 series: whichever is
13208 longer. If you need a release with long-term support, we recommend
13209 that you stay with the 0.2.9 series.
13211 Below are the changes since 0.2.9.10. For a list of only the changes
13212 since 0.3.0.5-rc, see the ChangeLog file.
13214 o Major features (directory authority, security):
13215 - The default for AuthDirPinKeys is now 1: directory authorities
13216 will reject relays where the RSA identity key matches a previously
13217 seen value, but the Ed25519 key has changed. Closes ticket 18319.
13219 o Major features (guard selection algorithm):
13220 - Tor's guard selection algorithm has been redesigned from the
13221 ground up, to better support unreliable networks and restrictive
13222 sets of entry nodes, and to better resist guard-capture attacks by
13223 hostile local networks. Implements proposal 271; closes
13226 o Major features (next-generation hidden services):
13227 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
13228 prop224 aka "Next Generation Hidden Services". Service and clients
13229 don't use this functionality yet. Closes ticket 19043. Based on
13230 initial code by Alec Heifetz.
13231 - Relays now support the HSDir version 3 protocol, so that they can
13232 can store and serve v3 descriptors. This is part of the next-
13233 generation onion service work detailed in proposal 224. Closes
13236 o Major features (protocol, ed25519 identity keys):
13237 - Clients now support including Ed25519 identity keys in the EXTEND2
13238 cells they generate. By default, this is controlled by a consensus
13239 parameter, currently disabled. You can turn this feature on for
13240 testing by setting ExtendByEd25519ID in your configuration. This
13241 might make your traffic appear different than the traffic
13242 generated by other users, however. Implements part of ticket
13243 15056; part of proposal 220.
13244 - Relays now understand requests to extend to other relays by their
13245 Ed25519 identity keys. When an Ed25519 identity key is included in
13246 an EXTEND2 cell, the relay will only extend the circuit if the
13247 other relay can prove ownership of that identity. Implements part
13248 of ticket 15056; part of proposal 220.
13249 - Relays now use Ed25519 to prove their Ed25519 identities and to
13250 one another, and to clients. This algorithm is faster and more
13251 secure than the RSA-based handshake we've been doing until now.
13252 Implements the second big part of proposal 220; Closes
13255 o Major features (security):
13256 - Change the algorithm used to decide DNS TTLs on client and server
13257 side, to better resist DNS-based correlation attacks like the
13258 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
13259 Feamster. Now relays only return one of two possible DNS TTL
13260 values, and clients are willing to believe DNS TTL values up to 3
13261 hours long. Closes ticket 19769.
13263 o Major bugfixes (client, onion service, also in 0.2.9.9):
13264 - Fix a client-side onion service reachability bug, where multiple
13265 socks requests to an onion service (or a single slow request)
13266 could cause us to mistakenly mark some of the service's
13267 introduction points as failed, and we cache that failure so
13268 eventually we run out and can't reach the service. Also resolves a
13269 mysterious "Remote server sent bogus reason code 65021" log
13270 warning. The bug was introduced in ticket 17218, where we tried to
13271 remember the circuit end reason as a uint16_t, which mangled
13272 negative values. Partially fixes bug 21056 and fixes bug 20307;
13273 bugfix on 0.2.8.1-alpha.
13275 o Major bugfixes (crash, directory connections):
13276 - Fix a rare crash when sending a begin cell on a circuit whose
13277 linked directory connection had already been closed. Fixes bug
13278 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
13280 o Major bugfixes (directory authority):
13281 - During voting, when marking a relay as a probable sybil, do not
13282 clear its BadExit flag: sybils can still be bad in other ways
13283 too. (We still clear the other flags.) Fixes bug 21108; bugfix
13286 o Major bugfixes (DNS):
13287 - Fix a bug that prevented exit nodes from caching DNS records for
13288 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
13290 o Major bugfixes (IPv6 Exits):
13291 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
13292 any IPv6 addresses. Instead, only reject a port over IPv6 if the
13293 exit policy rejects that port on more than an IPv6 /16 of
13294 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
13295 which rejected a relay's own IPv6 address by default. Fixes bug
13296 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
13298 o Major bugfixes (parsing):
13299 - Fix an integer underflow bug when comparing malformed Tor
13300 versions. This bug could crash Tor when built with
13301 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13302 0.2.9.8, which were built with -ftrapv by default. In other cases
13303 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13304 on 0.0.8pre1. Found by OSS-Fuzz.
13305 - When parsing a malformed content-length field from an HTTP
13306 message, do not read off the end of the buffer. This bug was a
13307 potential remote denial-of-service attack against Tor clients and
13308 relays. A workaround was released in October 2016, to prevent this
13309 bug from crashing Tor. This is a fix for the underlying issue,
13310 which should no longer matter (if you applied the earlier patch).
13311 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
13312 using AFL (http://lcamtuf.coredump.cx/afl/).
13314 o Major bugfixes (scheduler):
13315 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
13316 caused the channel scheduler to behave more or less randomly,
13317 rather than preferring channels with higher-priority circuits.
13318 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
13320 o Major bugfixes (security, also in 0.2.9.9):
13321 - Downgrade the "-ftrapv" option from "always on" to "only on when
13322 --enable-expensive-hardening is provided." This hardening option,
13323 like others, can turn survivable bugs into crashes--and having it
13324 on by default made a (relatively harmless) integer overflow bug
13325 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
13326 bugfix on 0.2.9.1-alpha.
13328 o Minor feature (client):
13329 - Enable IPv6 traffic on the SocksPort by default. To disable this,
13330 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
13332 o Minor feature (fallback scripts):
13333 - Add a check_existing mode to updateFallbackDirs.py, which checks
13334 if fallbacks in the hard-coded list are working. Closes ticket
13335 20174. Patch by haxxpop.
13337 o Minor feature (protocol versioning):
13338 - Add new protocol version for proposal 224. HSIntro now advertises
13339 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
13341 o Minor features (ciphersuite selection):
13342 - Allow relays to accept a wider range of ciphersuites, including
13343 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
13344 - Clients now advertise a list of ciphersuites closer to the ones
13345 preferred by Firefox. Closes part of ticket 15426.
13347 o Minor features (controller):
13348 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
13349 shared-random values to the controller. Closes ticket 19925.
13350 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
13351 rather than "unrecognized." Closes ticket 20389; patch from
13354 o Minor features (controller, configuration):
13355 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
13356 and so on, now comes with a __*Port variant that will not be saved
13357 to the torrc file by the controller's SAVECONF command. This
13358 change allows TorBrowser to set up a single-use domain socket for
13359 each time it launches Tor. Closes ticket 20956.
13360 - The GETCONF command can now query options that may only be
13361 meaningful in context-sensitive lists. This allows the controller
13362 to query the mixed SocksPort/__SocksPort style options introduced
13363 in feature 20956. Implements ticket 21300.
13365 o Minor features (diagnostic, directory client):
13366 - Warn when we find an unexpected inconsistency in directory
13367 download status objects. Prevents some negative consequences of
13370 o Minor features (directory authorities):
13371 - Directory authorities now reject descriptors that claim to be
13372 malformed versions of Tor. Helps prevent exploitation of
13374 - Reject version numbers with components that exceed INT32_MAX.
13375 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
13376 Fixes bug 21450; bugfix on 0.0.8pre1.
13378 o Minor features (directory authority):
13379 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
13380 default) to control whether authorities should try to probe relays
13381 by their Ed25519 link keys. This option will go away in a few
13382 releases--unless we encounter major trouble in our ed25519 link
13383 protocol rollout, in which case it will serve as a safety option.
13385 o Minor features (directory cache):
13386 - Relays and bridges will now refuse to serve the consensus they
13387 have if they know it is too old for a client to use. Closes
13390 o Minor features (ed25519 link handshake):
13391 - Advertise support for the ed25519 link handshake using the
13392 subprotocol-versions mechanism, so that clients can tell which
13393 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
13395 o Minor features (entry guards):
13396 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
13397 break regression tests.
13398 - Require UseEntryGuards when UseBridges is set, in order to make
13399 sure bridges aren't bypassed. Resolves ticket 20502.
13401 o Minor features (fallback directories):
13402 - Allow 3 fallback relays per operator, which is safe now that we
13403 are choosing 200 fallback relays. Closes ticket 20912.
13404 - Annotate updateFallbackDirs.py with the bandwidth and consensus
13405 weight for each candidate fallback. Closes ticket 20878.
13406 - Display the relay fingerprint when downloading consensuses from
13407 fallbacks. Closes ticket 20908.
13408 - Exclude relays affected by bug 20499 from the fallback list.
13409 Exclude relays from the fallback list if they are running versions
13410 known to be affected by bug 20499, or if in our tests they deliver
13411 a stale consensus (i.e. one that expired more than 24 hours ago).
13412 Closes ticket 20539.
13413 - Make it easier to change the output sort order of fallbacks.
13414 Closes ticket 20822.
13415 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
13417 - Require fallback directories to have the same address and port for
13418 7 days (now that we have enough relays with this stability).
13419 Relays whose OnionOO stability timer is reset on restart by bug
13420 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
13421 this issue. Closes ticket 20880; maintains short-term fix
13423 - Require fallbacks to have flags for 90% of the time (weighted
13424 decaying average), rather than 95%. This allows at least 73% of
13425 clients to bootstrap in the first 5 seconds without contacting an
13426 authority. Part of ticket 18828.
13427 - Select 200 fallback directories for each release. Closes
13430 o Minor features (fingerprinting resistance, authentication):
13431 - Extend the length of RSA keys used for TLS link authentication to
13432 2048 bits. (These weren't used for forward secrecy; for forward
13433 secrecy, we used P256.) Closes ticket 13752.
13435 o Minor features (geoip):
13436 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
13439 o Minor features (geoip, also in 0.2.9.9):
13440 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
13443 o Minor features (infrastructure):
13444 - Implement smartlist_add_strdup() function. Replaces the use of
13445 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
13447 o Minor features (linting):
13448 - Enhance the changes file linter to warn on Tor versions that are
13449 prefixed with "tor-". Closes ticket 21096.
13451 o Minor features (logging):
13452 - In several places, describe unset ed25519 keys as "<unset>",
13453 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
13455 o Minor features (portability, compilation):
13456 - Autoconf now checks to determine if OpenSSL structures are opaque,
13457 instead of explicitly checking for OpenSSL version numbers. Part
13459 - Support building with recent LibreSSL code that uses opaque
13460 structures. Closes ticket 21359.
13462 o Minor features (relay):
13463 - We now allow separation of exit and relay traffic to different
13464 source IP addresses, using the OutboundBindAddressExit and
13465 OutboundBindAddressOR options respectively. Closes ticket 17975.
13466 Written by Michael Sonntag.
13468 o Minor features (reliability, crash):
13469 - Try better to detect problems in buffers where they might grow (or
13470 think they have grown) over 2 GB in size. Diagnostic for
13473 o Minor features (testing):
13474 - During 'make test-network-all', if tor logs any warnings, ask
13475 chutney to output them. Requires a recent version of chutney with
13476 the 21572 patch. Implements 21570.
13478 o Minor bugfix (control protocol):
13479 - The reply to a "GETINFO config/names" request via the control
13480 protocol now spells the type "Dependent" correctly. This is a
13481 breaking change in the control protocol. (The field seems to be
13482 ignored by the most common known controllers.) Fixes bug 18146;
13483 bugfix on 0.1.1.4-alpha.
13484 - The GETINFO extra-info/digest/<digest> command was broken because
13485 of a wrong base16 decode return value check, introduced when
13486 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
13488 o Minor bugfix (logging):
13489 - Don't recommend the use of Tor2web in non-anonymous mode.
13490 Recommending Tor2web is a bad idea because the client loses all
13491 anonymity. Tor2web should only be used in specific cases by users
13492 who *know* and understand the issues. Fixes bug 21294; bugfix
13495 o Minor bugfixes (bug resilience):
13496 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
13497 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
13498 Hans Jerry Illikainen.
13500 o Minor bugfixes (build):
13501 - Replace obsolete Autoconf macros with their modern equivalent and
13502 prevent similar issues in the future. Fixes bug 20990; bugfix
13505 o Minor bugfixes (certificate expiration time):
13506 - Avoid using link certificates that don't become valid till some
13507 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
13509 o Minor bugfixes (client):
13510 - Always recover from failures in extend_info_from_node(), in an
13511 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
13512 bugfix on 0.2.3.1-alpha.
13513 - When clients that use bridges start up with a cached consensus on
13514 disk, they were ignoring it and downloading a new one. Now they
13515 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
13517 o Minor bugfixes (code correctness):
13518 - Repair a couple of (unreachable or harmless) cases of the risky
13519 comparison-by-subtraction pattern that caused bug 21278.
13521 o Minor bugfixes (config):
13522 - Don't assert on startup when trying to get the options list and
13523 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
13524 options so of course they aren't ready yet. Fixes bug 21062;
13525 bugfix on 0.2.9.3-alpha.
13527 o Minor bugfixes (configuration):
13528 - Accept non-space whitespace characters after the severity level in
13529 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
13530 - Support "TByte" and "TBytes" units in options given in bytes.
13531 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
13532 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
13534 o Minor bugfixes (configure, autoconf):
13535 - Rename the configure option --enable-expensive-hardening to
13536 --enable-fragile-hardening. Expensive hardening makes the tor
13537 daemon abort when some kinds of issues are detected. Thus, it
13538 makes tor more at risk of remote crashes but safer against RCE or
13539 heartbleed bug category. We now try to explain this issue in a
13540 message from the configure script. Fixes bug 21290; bugfix
13543 o Minor bugfixes (consensus weight):
13544 - Add new consensus method that initializes bw weights to 1 instead
13545 of 0. This prevents a zero weight from making it all the way to
13546 the end (happens in small testing networks) and causing an error.
13547 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
13549 o Minor bugfixes (crash prevention):
13550 - Fix an (currently untriggerable, but potentially dangerous) crash
13551 bug when base32-encoding inputs whose sizes are not a multiple of
13552 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
13554 o Minor bugfixes (dead code):
13555 - Remove a redundant check for PidFile changes at runtime in
13556 options_transition_allowed(): this check is already performed
13557 regardless of whether the sandbox is active. Fixes bug 21123;
13558 bugfix on 0.2.5.4-alpha.
13560 o Minor bugfixes (descriptors):
13561 - Correctly recognise downloaded full descriptors as valid, even
13562 when using microdescriptors as circuits. This affects clients with
13563 FetchUselessDescriptors set, and may affect directory authorities.
13564 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
13566 o Minor bugfixes (directory mirrors):
13567 - Allow relays to use directory mirrors without a DirPort: these
13568 relays need to be contacted over their ORPorts using a begindir
13569 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
13570 - Clarify the message logged when a remote relay is unexpectedly
13571 missing an ORPort or DirPort: users were confusing this with a
13572 local port. Fixes another case of bug 20711; bugfix
13575 o Minor bugfixes (directory system):
13576 - Bridges and relays now use microdescriptors (like clients do)
13577 rather than old-style router descriptors. Now bridges will blend
13578 in with clients in terms of the circuits they build. Fixes bug
13579 6769; bugfix on 0.2.3.2-alpha.
13580 - Download all consensus flavors, descriptors, and authority
13581 certificates when FetchUselessDescriptors is set, regardless of
13582 whether tor is a directory cache or not. Fixes bug 20667; bugfix
13583 on all recent tor versions.
13585 o Minor bugfixes (documentation):
13586 - Update the tor manual page to document every option that can not
13587 be changed while tor is running. Fixes bug 21122.
13589 o Minor bugfixes (ed25519 certificates):
13590 - Correctly interpret ed25519 certificates that would expire some
13591 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
13593 o Minor bugfixes (fallback directories):
13594 - Avoid checking fallback candidates' DirPorts if they are down in
13595 OnionOO. When a relay operator has multiple relays, this
13596 prioritizes relays that are up over relays that are down. Fixes
13597 bug 20926; bugfix on 0.2.8.3-alpha.
13598 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
13599 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
13600 - Stop failing when a relay has no uptime data in
13601 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
13603 o Minor bugfixes (hidden service):
13604 - Clean up the code for expiring intro points with no associated
13605 circuits. It was causing, rarely, a service with some expiring
13606 introduction points to not open enough additional introduction
13607 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
13608 - Resolve two possible underflows which could lead to creating and
13609 closing a lot of introduction point circuits in a non-stop loop.
13610 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
13611 - Stop setting the torrc option HiddenServiceStatistics to "0" just
13612 because we're not a bridge or relay. Instead, we preserve whatever
13613 value the user set (or didn't set). Fixes bug 21150; bugfix
13616 o Minor bugfixes (hidden services):
13617 - Make hidden services check for failed intro point connections,
13618 even when they have exceeded their intro point creation limit.
13619 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
13620 - Make hidden services with 8 to 10 introduction points check for
13621 failed circuits immediately after startup. Previously, they would
13622 wait for 5 minutes before performing their first checks. Fixes bug
13623 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
13624 - Stop ignoring misconfigured hidden services. Instead, refuse to
13625 start tor until the misconfigurations have been corrected. Fixes
13626 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
13629 o Minor bugfixes (IPv6):
13630 - Make IPv6-using clients try harder to find an IPv6 directory
13631 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
13632 - When IPv6 addresses have not been downloaded yet (microdesc
13633 consensus documents don't list relay IPv6 addresses), use hard-
13634 coded addresses for authorities, fallbacks, and configured
13635 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
13636 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
13638 o Minor bugfixes (memory leak at exit):
13639 - Fix a small harmless memory leak at exit of the previously unused
13640 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
13643 o Minor bugfixes (onion services):
13644 - Allow the number of introduction points to be as low as 0, rather
13645 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
13647 o Minor bugfixes (portability):
13648 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
13649 It is supported by OpenBSD itself, and also by most OpenBSD
13650 variants (such as Bitrig). Fixes bug 20980; bugfix
13653 o Minor bugfixes (portability, also in 0.2.9.9):
13654 - Avoid crashing when Tor is built using headers that contain
13655 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
13656 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
13658 - Fix Libevent detection on platforms without Libevent 1 headers
13659 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
13661 o Minor bugfixes (relay):
13662 - Avoid a double-marked-circuit warning that could happen when we
13663 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
13665 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
13666 initializing the keys would reset the DataDirectory to 0700
13667 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
13668 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
13670 o Minor bugfixes (testing):
13671 - Fix Raspbian build issues related to missing socket errno in
13672 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
13673 - Remove undefined behavior from the backtrace generator by removing
13674 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
13675 - Use bash in src/test/test-network.sh. This ensures we reliably
13676 call chutney's newer tools/test-network.sh when available. Fixes
13677 bug 21562; bugfix on 0.2.9.1-alpha.
13679 o Minor bugfixes (tor-resolve):
13680 - The tor-resolve command line tool now rejects hostnames over 255
13681 characters in length. Previously, it would silently truncate them,
13682 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
13683 Patch by "junglefowl".
13685 o Minor bugfixes (unit tests):
13686 - Allow the unit tests to pass even when DNS lookups of bogus
13687 addresses do not fail as expected. Fixes bug 20862 and 20863;
13688 bugfix on unit tests introduced in 0.2.8.1-alpha
13689 through 0.2.9.4-alpha.
13691 o Minor bugfixes (util):
13692 - When finishing writing a file to disk, if we were about to replace
13693 the file with the temporary file created before and we fail to
13694 replace it, remove the temporary file so it doesn't stay on disk.
13695 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
13697 o Minor bugfixes (Windows services):
13698 - Be sure to initialize the monotonic time subsystem before using
13699 it, even when running as an NT service. Fixes bug 21356; bugfix
13702 o Minor bugfixes (Windows):
13703 - Check for getpagesize before using it to mmap files. This fixes
13704 compilation in some MinGW environments. Fixes bug 20530; bugfix on
13705 0.1.2.1-alpha. Reported by "ice".
13707 o Code simplification and refactoring:
13708 - Abolish all global guard context in entrynodes.c; replace with new
13709 guard_selection_t structure as preparation for proposal 271.
13710 Closes ticket 19858.
13711 - Extract magic numbers in circuituse.c into defined variables.
13712 - Introduce rend_service_is_ephemeral() that tells if given onion
13713 service is ephemeral. Replace unclear NULL-checkings for service
13714 directory with this function. Closes ticket 20526.
13715 - Refactor circuit_is_available_for_use to remove unnecessary check.
13716 - Refactor circuit_predict_and_launch_new for readability and
13717 testability. Closes ticket 18873.
13718 - Refactor code to manipulate global_origin_circuit_list into
13719 separate functions. Closes ticket 20921.
13720 - Refactor large if statement in purpose_needs_anonymity to use
13721 switch statement instead. Closes part of ticket 20077.
13722 - Refactor the hashing API to return negative values for errors, as
13723 is done as throughout the codebase. Closes ticket 20717.
13724 - Remove data structures that were used to index or_connection
13725 objects by their RSA identity digests. These structures are fully
13726 redundant with the similar structures used in the
13727 channel abstraction.
13728 - Remove duplicate code in the channel_write_*cell() functions.
13729 Closes ticket 13827; patch from Pingl.
13730 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
13731 use only purpose_needs_anonymity. Closes part of ticket 20077.
13732 - The code to generate and parse EXTEND and EXTEND2 cells has been
13733 replaced with code automatically generated by the
13736 o Documentation (formatting):
13737 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
13738 blocks were incorrectly appearing. Closes ticket 20885.
13740 o Documentation (man page):
13741 - Clarify many options in tor.1 and add some min/max values for
13742 HiddenService options. Closes ticket 21058.
13745 - Change '1' to 'weight_scale' in consensus bw weights calculation
13746 comments, as that is reality. Closes ticket 20273. Patch
13748 - Clarify that when ClientRejectInternalAddresses is enabled (which
13749 is the default), multicast DNS hostnames for machines on the local
13750 network (of the form *.local) are also rejected. Closes
13752 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
13753 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
13754 - Include the "TBits" unit in Tor's man page. Fixes part of bug
13755 20622; bugfix on 0.2.5.1-alpha.
13756 - Small fixes to the fuzzing documentation. Closes ticket 21472.
13757 - Stop the man page from incorrectly stating that HiddenServiceDir
13758 must already exist. Fixes 20486.
13759 - Update the description of the directory server options in the
13760 manual page, to clarify that a relay no longer needs to set
13761 DirPort in order to be a directory cache. Closes ticket 21720.
13763 o Removed features:
13764 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
13765 limit for relays running on a single IP applies to authority IP
13766 addresses as well as to non-authority IP addresses. Closes
13768 - The UseDirectoryGuards torrc option no longer exists: all users
13769 that use entry guards will also use directory guards. Related to
13770 proposal 271; implements part of ticket 20831.
13773 - Add tests for networkstatus_compute_bw_weights_v10.
13774 - Add unit tests circuit_predict_and_launch_new.
13775 - Extract dummy_origin_circuit_new so it can be used by other
13777 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
13778 from "overcaffeinated".
13779 - Perform the coding style checks when running the tests and fail
13780 when coding style violations are found. Closes ticket 5500.
13783 Changes in version 0.2.8.13 - 2017-03-03
13784 Tor 0.2.8.13 backports a security fix from later Tor
13785 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
13786 this release, if for some reason they cannot upgrade to a later
13787 release series, and if they build Tor with the --enable-expensive-hardening
13790 Note that support for Tor 0.2.8.x is ending next year: we will not issue
13791 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
13792 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
13794 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
13795 - Fix an integer underflow bug when comparing malformed Tor
13796 versions. This bug could crash Tor when built with
13797 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13798 0.2.9.8, which were built with -ftrapv by default. In other cases
13799 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13800 on 0.0.8pre1. Found by OSS-Fuzz.
13802 o Minor features (geoip):
13803 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13807 Changes in version 0.2.7.7 - 2017-03-03
13808 Tor 0.2.7.7 backports a number of security fixes from later Tor
13809 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
13810 this release, if for some reason they cannot upgrade to a later
13813 Note that support for Tor 0.2.7.x is ending this year: we will not issue
13814 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
13815 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
13817 o Directory authority changes (backport from 0.2.8.5-rc):
13818 - Urras is no longer a directory authority. Closes ticket 19271.
13820 o Directory authority changes (backport from 0.2.9.2-alpha):
13821 - The "Tonga" bridge authority has been retired; the new bridge
13822 authority is "Bifroest". Closes tickets 19728 and 19690.
13824 o Directory authority key updates (backport from 0.2.8.1-alpha):
13825 - Update the V3 identity key for the dannenberg directory authority:
13826 it was changed on 18 November 2015. Closes task 17906. Patch
13829 o Major bugfixes (parsing, security, backport from 0.2.9.8):
13830 - Fix a bug in parsing that could cause clients to read a single
13831 byte past the end of an allocated region. This bug could be used
13832 to cause hardened clients (built with --enable-expensive-hardening)
13833 to crash if they tried to visit a hostile hidden service. Non-
13834 hardened clients are only affected depending on the details of
13835 their platform's memory allocator. Fixes bug 21018; bugfix on
13836 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13837 2016-12-002 and as CVE-2016-1254.
13839 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
13840 - Stop a crash that could occur when a client running with DNSPort
13841 received a query with multiple address types, and the first
13842 address type was not supported. Found and fixed by Scott Dial.
13843 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
13844 - Prevent a class of security bugs caused by treating the contents
13845 of a buffer chunk as if they were a NUL-terminated string. At
13846 least one such bug seems to be present in all currently used
13847 versions of Tor, and would allow an attacker to remotely crash
13848 most Tor instances, especially those compiled with extra compiler
13849 hardening. With this defense in place, such bugs can't crash Tor,
13850 though we should still fix them as they occur. Closes ticket
13851 20384 (TROVE-2016-10-001).
13853 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
13854 - Avoid a difficult-to-trigger heap corruption attack when extending
13855 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
13856 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
13857 Reported by Guido Vranken.
13859 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
13860 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
13861 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
13863 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
13864 - If OpenSSL fails to generate an RSA key, do not retain a dangling
13865 pointer to the previous (uninitialized) key value. The impact here
13866 should be limited to a difficult-to-trigger crash, if OpenSSL is
13867 running an engine that makes key generation failures possible, or
13868 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
13869 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
13872 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
13873 - Fix an integer underflow bug when comparing malformed Tor
13874 versions. This bug could crash Tor when built with
13875 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13876 0.2.9.8, which were built with -ftrapv by default. In other cases
13877 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13878 on 0.0.8pre1. Found by OSS-Fuzz.
13880 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
13881 - Make memwipe() do nothing when passed a NULL pointer or buffer of
13882 zero size. Check size argument to memwipe() for underflow. Fixes
13883 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
13886 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
13887 - Make Tor survive errors involving connections without a
13888 corresponding event object. Previously we'd fail with an
13889 assertion; now we produce a log message. Related to bug 16248.
13891 o Minor features (geoip):
13892 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13896 Changes in version 0.2.6.11 - 2017-03-03
13897 Tor 0.2.6.11 backports a number of security fixes from later Tor
13898 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
13899 this release, if for some reason they cannot upgrade to a later
13902 Note that support for Tor 0.2.6.x is ending this year: we will not issue
13903 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
13904 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
13906 o Directory authority changes (backport from 0.2.8.5-rc):
13907 - Urras is no longer a directory authority. Closes ticket 19271.
13909 o Directory authority changes (backport from 0.2.9.2-alpha):
13910 - The "Tonga" bridge authority has been retired; the new bridge
13911 authority is "Bifroest". Closes tickets 19728 and 19690.
13913 o Directory authority key updates (backport from 0.2.8.1-alpha):
13914 - Update the V3 identity key for the dannenberg directory authority:
13915 it was changed on 18 November 2015. Closes task 17906. Patch
13918 o Major features (security fixes, backport from 0.2.9.4-alpha):
13919 - Prevent a class of security bugs caused by treating the contents
13920 of a buffer chunk as if they were a NUL-terminated string. At
13921 least one such bug seems to be present in all currently used
13922 versions of Tor, and would allow an attacker to remotely crash
13923 most Tor instances, especially those compiled with extra compiler
13924 hardening. With this defense in place, such bugs can't crash Tor,
13925 though we should still fix them as they occur. Closes ticket
13926 20384 (TROVE-2016-10-001).
13928 o Major bugfixes (parsing, security, backport from 0.2.9.8):
13929 - Fix a bug in parsing that could cause clients to read a single
13930 byte past the end of an allocated region. This bug could be used
13931 to cause hardened clients (built with --enable-expensive-hardening)
13932 to crash if they tried to visit a hostile hidden service. Non-
13933 hardened clients are only affected depending on the details of
13934 their platform's memory allocator. Fixes bug 21018; bugfix on
13935 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13936 2016-12-002 and as CVE-2016-1254.
13938 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
13939 - Stop a crash that could occur when a client running with DNSPort
13940 received a query with multiple address types, and the first
13941 address type was not supported. Found and fixed by Scott Dial.
13942 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
13944 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
13945 - Fix an error that could cause us to read 4 bytes before the
13946 beginning of an openssl string. This bug could be used to cause
13947 Tor to crash on systems with unusual malloc implementations, or
13948 systems with unusual hardening installed. Fixes bug 17404; bugfix
13951 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
13952 - Avoid a difficult-to-trigger heap corruption attack when extending
13953 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
13954 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
13955 Reported by Guido Vranken.
13957 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
13958 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
13959 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
13961 o Major bugfixes (guard selection, backport from 0.2.7.6):
13962 - Actually look at the Guard flag when selecting a new directory
13963 guard. When we implemented the directory guard design, we
13964 accidentally started treating all relays as if they have the Guard
13965 flag during guard selection, leading to weaker anonymity and worse
13966 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
13969 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
13970 - If OpenSSL fails to generate an RSA key, do not retain a dangling
13971 pointer to the previous (uninitialized) key value. The impact here
13972 should be limited to a difficult-to-trigger crash, if OpenSSL is
13973 running an engine that makes key generation failures possible, or
13974 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
13975 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
13978 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
13979 - Fix an integer underflow bug when comparing malformed Tor
13980 versions. This bug could crash Tor when built with
13981 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13982 0.2.9.8, which were built with -ftrapv by default. In other cases
13983 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13984 on 0.0.8pre1. Found by OSS-Fuzz.
13986 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
13987 - Make memwipe() do nothing when passed a NULL pointer or buffer of
13988 zero size. Check size argument to memwipe() for underflow. Fixes
13989 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
13992 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
13993 - Make Tor survive errors involving connections without a
13994 corresponding event object. Previously we'd fail with an
13995 assertion; now we produce a log message. Related to bug 16248.
13997 o Minor features (geoip):
13998 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
14001 o Minor bugfixes (compilation, backport from 0.2.7.6):
14002 - Fix a compilation warning with Clang 3.6: Do not check the
14003 presence of an address which can never be NULL. Fixes bug 17781.
14006 Changes in version 0.2.5.13 - 2017-03-03
14007 Tor 0.2.5.13 backports a number of security fixes from later Tor
14008 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
14009 this release, if for some reason they cannot upgrade to a later
14012 Note that support for Tor 0.2.5.x is ending next year: we will not issue
14013 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
14014 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
14016 o Directory authority changes (backport from 0.2.8.5-rc):
14017 - Urras is no longer a directory authority. Closes ticket 19271.
14019 o Directory authority changes (backport from 0.2.9.2-alpha):
14020 - The "Tonga" bridge authority has been retired; the new bridge
14021 authority is "Bifroest". Closes tickets 19728 and 19690.
14023 o Directory authority key updates (backport from 0.2.8.1-alpha):
14024 - Update the V3 identity key for the dannenberg directory authority:
14025 it was changed on 18 November 2015. Closes task 17906. Patch
14028 o Major features (security fixes, backport from 0.2.9.4-alpha):
14029 - Prevent a class of security bugs caused by treating the contents
14030 of a buffer chunk as if they were a NUL-terminated string. At
14031 least one such bug seems to be present in all currently used
14032 versions of Tor, and would allow an attacker to remotely crash
14033 most Tor instances, especially those compiled with extra compiler
14034 hardening. With this defense in place, such bugs can't crash Tor,
14035 though we should still fix them as they occur. Closes ticket
14036 20384 (TROVE-2016-10-001).
14038 o Major bugfixes (parsing, security, backport from 0.2.9.8):
14039 - Fix a bug in parsing that could cause clients to read a single
14040 byte past the end of an allocated region. This bug could be used
14041 to cause hardened clients (built with --enable-expensive-hardening)
14042 to crash if they tried to visit a hostile hidden service. Non-
14043 hardened clients are only affected depending on the details of
14044 their platform's memory allocator. Fixes bug 21018; bugfix on
14045 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
14046 2016-12-002 and as CVE-2016-1254.
14048 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
14049 - Stop a crash that could occur when a client running with DNSPort
14050 received a query with multiple address types, and the first
14051 address type was not supported. Found and fixed by Scott Dial.
14052 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
14054 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
14055 - Fix an error that could cause us to read 4 bytes before the
14056 beginning of an openssl string. This bug could be used to cause
14057 Tor to crash on systems with unusual malloc implementations, or
14058 systems with unusual hardening installed. Fixes bug 17404; bugfix
14061 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
14062 - Avoid a difficult-to-trigger heap corruption attack when extending
14063 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
14064 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
14065 Reported by Guido Vranken.
14067 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
14068 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
14069 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
14071 o Major bugfixes (guard selection, backport from 0.2.7.6):
14072 - Actually look at the Guard flag when selecting a new directory
14073 guard. When we implemented the directory guard design, we
14074 accidentally started treating all relays as if they have the Guard
14075 flag during guard selection, leading to weaker anonymity and worse
14076 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
14079 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
14080 - If OpenSSL fails to generate an RSA key, do not retain a dangling
14081 pointer to the previous (uninitialized) key value. The impact here
14082 should be limited to a difficult-to-trigger crash, if OpenSSL is
14083 running an engine that makes key generation failures possible, or
14084 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
14085 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
14088 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
14089 - Fix an integer underflow bug when comparing malformed Tor
14090 versions. This bug could crash Tor when built with
14091 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
14092 0.2.9.8, which were built with -ftrapv by default. In other cases
14093 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
14094 on 0.0.8pre1. Found by OSS-Fuzz.
14096 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
14097 - Make memwipe() do nothing when passed a NULL pointer or buffer of
14098 zero size. Check size argument to memwipe() for underflow. Fixes
14099 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
14102 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
14103 - Make Tor survive errors involving connections without a
14104 corresponding event object. Previously we'd fail with an
14105 assertion; now we produce a log message. Related to bug 16248.
14107 o Minor features (geoip):
14108 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
14111 o Minor bugfixes (compilation, backport from 0.2.7.6):
14112 - Fix a compilation warning with Clang 3.6: Do not check the
14113 presence of an address which can never be NULL. Fixes bug 17781.
14115 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
14116 - Check for failures from crypto_early_init, and refuse to continue.
14117 A previous typo meant that we could keep going with an
14118 uninitialized crypto library, and would have OpenSSL initialize
14119 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
14120 when implementing ticket 4900. Patch by "teor".
14122 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
14123 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
14124 a client authorized hidden service. Fixes bug 15823; bugfix
14128 Changes in version 0.2.4.28 - 2017-03-03
14129 Tor 0.2.4.28 backports a number of security fixes from later Tor
14130 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
14131 this release, if for some reason they cannot upgrade to a later
14134 Note that support for Tor 0.2.4.x is ending soon: we will not issue
14135 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
14136 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
14138 o Directory authority changes (backport from 0.2.8.5-rc):
14139 - Urras is no longer a directory authority. Closes ticket 19271.
14141 o Directory authority changes (backport from 0.2.9.2-alpha):
14142 - The "Tonga" bridge authority has been retired; the new bridge
14143 authority is "Bifroest". Closes tickets 19728 and 19690.
14145 o Directory authority key updates (backport from 0.2.8.1-alpha):
14146 - Update the V3 identity key for the dannenberg directory authority:
14147 it was changed on 18 November 2015. Closes task 17906. Patch
14150 o Major features (security fixes, backport from 0.2.9.4-alpha):
14151 - Prevent a class of security bugs caused by treating the contents
14152 of a buffer chunk as if they were a NUL-terminated string. At
14153 least one such bug seems to be present in all currently used
14154 versions of Tor, and would allow an attacker to remotely crash
14155 most Tor instances, especially those compiled with extra compiler
14156 hardening. With this defense in place, such bugs can't crash Tor,
14157 though we should still fix them as they occur. Closes ticket
14158 20384 (TROVE-2016-10-001).
14160 o Major bugfixes (parsing, security, backport from 0.2.9.8):
14161 - Fix a bug in parsing that could cause clients to read a single
14162 byte past the end of an allocated region. This bug could be used
14163 to cause hardened clients (built with --enable-expensive-hardening)
14164 to crash if they tried to visit a hostile hidden service. Non-
14165 hardened clients are only affected depending on the details of
14166 their platform's memory allocator. Fixes bug 21018; bugfix on
14167 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
14168 2016-12-002 and as CVE-2016-1254.
14170 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
14171 - Fix an error that could cause us to read 4 bytes before the
14172 beginning of an openssl string. This bug could be used to cause
14173 Tor to crash on systems with unusual malloc implementations, or
14174 systems with unusual hardening installed. Fixes bug 17404; bugfix
14177 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
14178 - Avoid a difficult-to-trigger heap corruption attack when extending
14179 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
14180 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
14181 Reported by Guido Vranken.
14183 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
14184 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
14185 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
14187 o Major bugfixes (guard selection, backport from 0.2.7.6):
14188 - Actually look at the Guard flag when selecting a new directory
14189 guard. When we implemented the directory guard design, we
14190 accidentally started treating all relays as if they have the Guard
14191 flag during guard selection, leading to weaker anonymity and worse
14192 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
14195 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
14196 - If OpenSSL fails to generate an RSA key, do not retain a dangling
14197 pointer to the previous (uninitialized) key value. The impact here
14198 should be limited to a difficult-to-trigger crash, if OpenSSL is
14199 running an engine that makes key generation failures possible, or
14200 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
14201 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
14204 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
14205 - Fix an integer underflow bug when comparing malformed Tor
14206 versions. This bug could crash Tor when built with
14207 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
14208 0.2.9.8, which were built with -ftrapv by default. In other cases
14209 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
14210 on 0.0.8pre1. Found by OSS-Fuzz.
14212 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
14213 - Make memwipe() do nothing when passed a NULL pointer or buffer of
14214 zero size. Check size argument to memwipe() for underflow. Fixes
14215 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
14218 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
14219 - Make Tor survive errors involving connections without a
14220 corresponding event object. Previously we'd fail with an
14221 assertion; now we produce a log message. Related to bug 16248.
14223 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
14224 - Make it harder for attackers to overload hidden services with
14225 introductions, by blocking multiple introduction requests on the
14226 same circuit. Resolves ticket 15515.
14228 o Minor features (geoip):
14229 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
14232 o Minor bugfixes (compilation, backport from 0.2.7.6):
14233 - Fix a compilation warning with Clang 3.6: Do not check the
14234 presence of an address which can never be NULL. Fixes bug 17781.
14236 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
14237 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
14238 a client authorized hidden service. Fixes bug 15823; bugfix
14242 Changes in version 0.2.9.10 - 2017-03-01
14243 Tor 0.2.9.10 backports a security fix from later Tor release. It also
14244 includes fixes for some major issues affecting directory authorities,
14245 LibreSSL compatibility, and IPv6 correctness.
14247 The Tor 0.2.9.x release series is now marked as a long-term-support
14248 series. We intend to backport security fixes to 0.2.9.x until at
14249 least January of 2020.
14251 o Major bugfixes (directory authority, 0.3.0.3-alpha):
14252 - During voting, when marking a relay as a probable sybil, do not
14253 clear its BadExit flag: sybils can still be bad in other ways
14254 too. (We still clear the other flags.) Fixes bug 21108; bugfix
14257 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
14258 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
14259 any IPv6 addresses. Instead, only reject a port over IPv6 if the
14260 exit policy rejects that port on more than an IPv6 /16 of
14261 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
14262 which rejected a relay's own IPv6 address by default. Fixes bug
14263 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
14265 o Major bugfixes (parsing, also in 0.3.0.4-rc):
14266 - Fix an integer underflow bug when comparing malformed Tor
14267 versions. This bug could crash Tor when built with
14268 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
14269 0.2.9.8, which were built with -ftrapv by default. In other cases
14270 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
14271 on 0.0.8pre1. Found by OSS-Fuzz.
14273 o Minor features (directory authorities, also in 0.3.0.4-rc):
14274 - Directory authorities now reject descriptors that claim to be
14275 malformed versions of Tor. Helps prevent exploitation of
14277 - Reject version numbers with components that exceed INT32_MAX.
14278 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
14279 Fixes bug 21450; bugfix on 0.0.8pre1.
14281 o Minor features (geoip):
14282 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
14285 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
14286 - Autoconf now checks to determine if OpenSSL structures are opaque,
14287 instead of explicitly checking for OpenSSL version numbers. Part
14289 - Support building with recent LibreSSL code that uses opaque
14290 structures. Closes ticket 21359.
14292 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
14293 - Repair a couple of (unreachable or harmless) cases of the risky
14294 comparison-by-subtraction pattern that caused bug 21278.
14296 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
14297 - The tor-resolve command line tool now rejects hostnames over 255
14298 characters in length. Previously, it would silently truncate them,
14299 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
14300 Patch by "junglefowl".
14303 Changes in version 0.2.9.9 - 2017-01-23
14304 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
14305 cause relays and clients to crash, even if they were not built with
14306 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
14307 versions, and also affects 0.3.0.1-alpha: all relays running an affected
14308 version should upgrade.
14310 This release also resolves a client-side onion service reachability
14311 bug, and resolves a pair of small portability issues.
14313 o Major bugfixes (security):
14314 - Downgrade the "-ftrapv" option from "always on" to "only on when
14315 --enable-expensive-hardening is provided." This hardening option,
14316 like others, can turn survivable bugs into crashes -- and having
14317 it on by default made a (relatively harmless) integer overflow bug
14318 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
14319 bugfix on 0.2.9.1-alpha.
14321 o Major bugfixes (client, onion service):
14322 - Fix a client-side onion service reachability bug, where multiple
14323 socks requests to an onion service (or a single slow request)
14324 could cause us to mistakenly mark some of the service's
14325 introduction points as failed, and we cache that failure so
14326 eventually we run out and can't reach the service. Also resolves a
14327 mysterious "Remote server sent bogus reason code 65021" log
14328 warning. The bug was introduced in ticket 17218, where we tried to
14329 remember the circuit end reason as a uint16_t, which mangled
14330 negative values. Partially fixes bug 21056 and fixes bug 20307;
14331 bugfix on 0.2.8.1-alpha.
14333 o Minor features (geoip):
14334 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
14337 o Minor bugfixes (portability):
14338 - Avoid crashing when Tor is built using headers that contain
14339 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
14340 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
14342 - Fix Libevent detection on platforms without Libevent 1 headers
14343 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
14346 Changes in version 0.2.8.12 - 2016-12-19
14347 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
14348 below) where Tor clients could crash when attempting to visit a
14349 hostile hidden service. Clients are recommended to upgrade as packages
14350 become available for their systems.
14352 It also includes an updated list of fallback directories, backported
14355 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
14356 backported to 0.2.8 in the future.
14358 o Major bugfixes (parsing, security, backported from 0.2.9.8):
14359 - Fix a bug in parsing that could cause clients to read a single
14360 byte past the end of an allocated region. This bug could be used
14361 to cause hardened clients (built with --enable-expensive-hardening)
14362 to crash if they tried to visit a hostile hidden service. Non-
14363 hardened clients are only affected depending on the details of
14364 their platform's memory allocator. Fixes bug 21018; bugfix on
14365 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
14366 2016-12-002 and as CVE-2016-1254.
14368 o Minor features (fallback directory list, backported from 0.2.9.8):
14369 - Replace the 81 remaining fallbacks of the 100 originally
14370 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
14371 fallbacks (123 new, 54 existing, 27 removed) generated in December
14372 2016. Resolves ticket 20170.
14374 o Minor features (geoip, backported from 0.2.9.7-rc):
14375 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
14379 Changes in version 0.2.9.8 - 2016-12-19
14380 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
14382 The Tor 0.2.9 series makes mandatory a number of security features
14383 that were formerly optional. It includes support for a new shared-
14384 randomness protocol that will form the basis for next generation
14385 hidden services, includes a single-hop hidden service mode for
14386 optimizing .onion services that don't actually want to be hidden,
14387 tries harder not to overload the directory authorities with excessive
14388 downloads, and supports a better protocol versioning scheme for
14389 improved compatibility with other implementations of the Tor protocol.
14391 And of course, there are numerous other bugfixes and improvements.
14393 This release also includes a fix for a medium-severity issue (bug
14394 21018 below) where Tor clients could crash when attempting to visit a
14395 hostile hidden service. Clients are recommended to upgrade as packages
14396 become available for their systems.
14398 Below are listed the changes since Tor 0.2.8.11. For a list of
14399 changes since 0.2.9.7-rc, see the ChangeLog file.
14401 o New system requirements:
14402 - When building with OpenSSL, Tor now requires version 1.0.1 or
14403 later. OpenSSL 1.0.0 and earlier are no longer supported by the
14404 OpenSSL team, and should not be used. Closes ticket 20303.
14405 - Tor now requires Libevent version 2.0.10-stable or later. Older
14406 versions of Libevent have less efficient backends for several
14407 platforms, and lack the DNS code that we use for our server-side
14408 DNS support. This implements ticket 19554.
14409 - Tor now requires zlib version 1.2 or later, for security,
14410 efficiency, and (eventually) gzip support. (Back when we started,
14411 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
14412 released in 2003. We recommend the latest version.)
14414 o Deprecated features:
14415 - A number of DNS-cache-related sub-options for client ports are now
14416 deprecated for security reasons, and may be removed in a future
14417 version of Tor. (We believe that client-side DNS caching is a bad
14418 idea for anonymity, and you should not turn it on.) The options
14419 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
14420 UseIPv4Cache, and UseIPv6Cache.
14421 - A number of options are deprecated for security reasons, and may
14422 be removed in a future version of Tor. The options are:
14423 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
14424 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
14425 CloseHSClientCircuitsImmediatelyOnTimeout,
14426 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
14427 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
14428 UseNTorHandshake, and WarnUnsafeSocks.
14429 - The *ListenAddress options are now deprecated as unnecessary: the
14430 corresponding *Port options should be used instead. These options
14431 may someday be removed. The affected options are:
14432 ControlListenAddress, DNSListenAddress, DirListenAddress,
14433 NATDListenAddress, ORListenAddress, SocksListenAddress,
14434 and TransListenAddress.
14436 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
14437 - Fix a bug in parsing that could cause clients to read a single
14438 byte past the end of an allocated region. This bug could be used
14439 to cause hardened clients (built with --enable-expensive-hardening)
14440 to crash if they tried to visit a hostile hidden service. Non-
14441 hardened clients are only affected depending on the details of
14442 their platform's memory allocator. Fixes bug 21018; bugfix on
14443 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
14444 2016-12-002 and as CVE-2016-1254.
14446 o Major features (build, hardening):
14447 - Tor now builds with -ftrapv by default on compilers that support
14448 it. This option detects signed integer overflow (which C forbids),
14449 and turns it into a hard-failure. We do not apply this option to
14450 code that needs to run in constant time to avoid side-channels;
14451 instead, we use -fwrapv in that code. Closes ticket 17983.
14452 - When --enable-expensive-hardening is selected, stop applying the
14453 clang/gcc sanitizers to code that needs to run in constant time.
14454 Although we are aware of no introduced side-channels, we are not
14455 able to prove that there are none. Related to ticket 17983.
14457 o Major features (circuit building, security):
14458 - Authorities, relays, and clients now require ntor keys in all
14459 descriptors, for all hops (except for rare hidden service protocol
14460 cases), for all circuits, and for all other roles. Part of
14462 - Authorities, relays, and clients only use ntor, except for
14463 rare cases in the hidden service protocol. Part of ticket 19163.
14465 o Major features (compilation):
14466 - Our big list of extra GCC warnings is now enabled by default when
14467 building with GCC (or with anything like Clang that claims to be
14468 GCC-compatible). To make all warnings into fatal compilation
14469 errors, pass --enable-fatal-warnings to configure. Closes
14471 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
14472 turn on C and POSIX extensions. (Previously, we attempted to do
14473 this on an ad hoc basis.) Closes ticket 19139.
14475 o Major features (directory authorities, hidden services):
14476 - Directory authorities can now perform the shared randomness
14477 protocol specified by proposal 250. Using this protocol, directory
14478 authorities generate a global fresh random value every day. In the
14479 future, this value will be used by hidden services to select
14480 HSDirs. This release implements the directory authority feature;
14481 the hidden service side will be implemented in the future as part
14482 of proposal 224. Resolves ticket 16943; implements proposal 250.
14484 o Major features (downloading, random exponential backoff):
14485 - When we fail to download an object from a directory service, wait
14486 for an (exponentially increasing) randomized amount of time before
14487 retrying, rather than a fixed interval as we did before. This
14488 prevents a group of Tor instances from becoming too synchronized,
14489 or a single Tor instance from becoming too predictable, in its
14490 download schedule. Closes ticket 15942.
14492 o Major features (resource management):
14493 - Tor can now notice it is about to run out of sockets, and
14494 preemptively close connections of lower priority. (This feature is
14495 off by default for now, since the current prioritizing method is
14496 yet not mature enough. You can enable it by setting
14497 "DisableOOSCheck 0", but watch out: it might close some sockets
14498 you would rather have it keep.) Closes ticket 18640.
14500 o Major features (single-hop "hidden" services):
14501 - Add experimental HiddenServiceSingleHopMode and
14502 HiddenServiceNonAnonymousMode options. When both are set to 1,
14503 every hidden service on that Tor instance becomes a non-anonymous
14504 Single Onion Service. Single Onions make one-hop (direct)
14505 connections to their introduction and rendezvous points. One-hop
14506 circuits make Single Onion servers easily locatable, but clients
14507 remain location-anonymous. This is compatible with the existing
14508 hidden service implementation, and works on the current Tor
14509 network without any changes to older relays or clients. Implements
14510 proposal 260, completes ticket 17178. Patch by teor and asn.
14512 o Major features (subprotocol versions):
14513 - Tor directory authorities now vote on a set of recommended
14514 "subprotocol versions", and on a set of required subprotocol
14515 versions. Clients and relays that lack support for a _required_
14516 subprotocol version will not start; those that lack support for a
14517 _recommended_ subprotocol version will warn the user to upgrade.
14518 This change allows compatible implementations of the Tor protocol(s)
14519 to exist without pretending to be 100% bug-compatible with
14520 particular releases of Tor itself. Closes ticket 19958; implements
14521 part of proposal 264.
14523 o Major bugfixes (circuit building):
14524 - Hidden service client-to-intro-point and service-to-rendezvous-
14525 point circuits use the TAP key supplied by the protocol, to avoid
14526 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
14528 o Major bugfixes (download scheduling):
14529 - Avoid resetting download status for consensuses hourly, since we
14530 already have another, smarter retry mechanism. Fixes bug 8625;
14531 bugfix on 0.2.0.9-alpha.
14532 - If a consensus expires while we are waiting for certificates to
14533 download, stop waiting for certificates.
14534 - If we stop waiting for certificates less than a minute after we
14535 started downloading them, do not consider the certificate download
14536 failure a separate failure. Fixes bug 20533; bugfix
14538 - When using exponential backoff in test networks, use a lower
14539 exponent, so the delays do not vary as much. This helps test
14540 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
14542 o Major bugfixes (exit policies):
14543 - Avoid disclosing exit outbound bind addresses, configured port
14544 bind addresses, and local interface addresses in relay descriptors
14545 by default under ExitPolicyRejectPrivate. Instead, only reject
14546 these (otherwise unlisted) addresses if
14547 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
14548 0.2.7.2-alpha. Patch by teor.
14550 o Major bugfixes (hidden services):
14551 - Allow Tor clients with appropriate controllers to work with
14552 FetchHidServDescriptors set to 0. Previously, this option also
14553 disabled descriptor cache lookup, thus breaking hidden services
14554 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
14555 - Clients now require hidden services to include the TAP keys for
14556 their intro points in the hidden service descriptor. This prevents
14557 an inadvertent upgrade to ntor, which a malicious hidden service
14558 could use to distinguish clients by consensus version. Fixes bug
14559 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
14561 o Major bugfixes (relay, resolver, logging):
14562 - For relays that don't know their own address, avoid attempting a
14563 local hostname resolve for each descriptor we download. This
14564 will cut down on the number of "Success: chose address 'x.x.x.x'"
14565 log lines, and also avoid confusing clock jumps if the resolver
14566 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
14568 o Minor features (port flags):
14569 - Add new flags to the *Port options to give finer control over which
14570 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
14571 and the synthetic flag OnionTrafficOnly, which is equivalent to
14572 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
14573 18693; patch by "teor".
14575 o Minor features (build, hardening):
14576 - Detect and work around a libclang_rt problem that would prevent
14577 clang from finding __mulodi4() on some 32-bit platforms, and thus
14578 keep -ftrapv from linking on those systems. Closes ticket 19079.
14579 - When building on a system without runtime support for the runtime
14580 hardening options, try to log a useful warning at configuration
14581 time, rather than an incomprehensible warning at link time. If
14582 expensive hardening was requested, this warning becomes an error.
14583 Closes ticket 18895.
14585 o Minor features (client, directory):
14586 - Since authorities now omit all routers that lack the Running and
14587 Valid flags, we assume that any relay listed in the consensus must
14588 have those flags. Closes ticket 20001; implements part of
14591 o Minor features (code safety):
14592 - In our integer-parsing functions, ensure that the maximum value we
14593 allow is no smaller than the minimum value. Closes ticket 19063;
14594 patch from "U+039b".
14596 o Minor features (compilation, portability):
14597 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
14600 o Minor features (config):
14601 - Warn users when descriptor and port addresses are inconsistent.
14602 Mitigates bug 13953; patch by teor.
14604 o Minor features (controller):
14605 - Allow controllers to configure basic client authorization on
14606 hidden services when they create them with the ADD_ONION controller
14607 command. Implements ticket 15588. Patch by "special".
14608 - Fire a STATUS_SERVER controller event whenever the hibernation
14609 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
14610 - Implement new GETINFO queries for all downloads that use
14611 download_status_t to schedule retries. This allows controllers to
14612 examine the schedule for pending downloads. Closes ticket 19323.
14614 o Minor features (development tools, etags):
14615 - Teach the "make tags" Makefile target how to correctly find
14616 "MOCK_IMPL" function definitions. Patch from nherring; closes
14619 o Minor features (directory authority):
14620 - After voting, if the authorities decide that a relay is not
14621 "Valid", they no longer include it in the consensus at all. Closes
14622 ticket 20002; implements part of proposal 272.
14623 - Directory authorities now only give the Guard flag to a relay if
14624 they are also giving it the Stable flag. This change allows us to
14625 simplify path selection for clients. It should have minimal effect
14626 in practice, since >99% of Guards already have the Stable flag.
14627 Implements ticket 18624.
14628 - Directory authorities now write their v3-status-votes file out to
14629 disk earlier in the consensus process, so we have a record of the
14630 votes even if we abort the consensus process. Resolves
14633 o Minor features (fallback directory list, new since 0.2.9.7-rc):
14634 - Replace the 81 remaining fallbacks of the 100 originally
14635 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
14636 fallbacks (123 new, 54 existing, 27 removed) generated in December
14637 2016. Resolves ticket 20170.
14639 o Minor features (hidden service):
14640 - Stop being so strict about the payload length of "rendezvous1"
14641 cells. We used to be locked in to the "TAP" handshake length, and
14642 now we can handle better handshakes like "ntor". Resolves
14645 o Minor features (infrastructure, time):
14646 - Tor now includes an improved timer backend, so that we can
14647 efficiently support tens or hundreds of thousands of concurrent
14648 timers, as will be needed for some of our planned anti-traffic-
14649 analysis work. This code is based on William Ahern's "timeout.c"
14650 project, which implements a "tickless hierarchical timing wheel".
14651 Closes ticket 18365.
14652 - Tor now uses the operating system's monotonic timers (where
14653 available) for internal fine-grained timing. Previously we would
14654 look at the system clock, and then attempt to compensate for the
14655 clock running backwards. Closes ticket 18908.
14657 o Minor features (logging):
14658 - Add a set of macros to check nonfatal assertions, for internal
14659 use. Migrating more of our checks to these should help us avoid
14660 needless crash bugs. Closes ticket 18613.
14661 - Provide a more useful warning message when configured with an
14662 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
14663 - When dumping unparseable router descriptors, optionally store them
14664 in separate files, named by digest, up to a configurable size
14665 limit. You can change the size limit by setting the
14666 MaxUnparseableDescSizeToLog option, and disable this feature by
14667 setting that option to 0. Closes ticket 18322.
14669 o Minor features (performance):
14670 - Change the "optimistic data" extension from "off by default" to
14671 "on by default". The default was ordinarily overridden by a
14672 consensus option, but when clients were bootstrapping for the
14673 first time, they would not have a consensus to get the option
14674 from. Changing this default saves a round-trip during startup.
14675 Closes ticket 18815.
14677 o Minor features (relay, usability):
14678 - When the directory authorities refuse a bad relay's descriptor,
14679 encourage the relay operator to contact us. Many relay operators
14680 won't notice this line in their logs, but it's a win if even a few
14681 learn why we don't like what their relay was doing. Resolves
14684 o Minor features (security, TLS):
14685 - Servers no longer support clients that lack AES ciphersuites.
14686 (3DES is no longer considered an acceptable cipher.) We believe
14687 that no such Tor clients currently exist, since Tor has required
14688 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
14690 o Minor features (testing):
14691 - Disable memory protections on OpenBSD when performing our unit
14692 tests for memwipe(). The test deliberately invokes undefined
14693 behavior, and the OpenBSD protections interfere with this. Patch
14694 from "rubiate". Closes ticket 20066.
14695 - Move the test-network.sh script to chutney, and modify tor's test-
14696 network.sh to call the (newer) chutney version when available.
14697 Resolves ticket 19116. Patch by teor.
14698 - Use the lcov convention for marking lines as unreachable, so that
14699 we don't count them when we're generating test coverage data.
14700 Update our coverage tools to understand this convention. Closes
14702 - Our link-handshake unit tests now check that when invalid
14703 handshakes fail, they fail with the error messages we expected.
14704 - Our unit testing code that captures log messages no longer
14705 prevents them from being written out if the user asked for them
14706 (by passing --debug or --info or --notice or --warn to the "test"
14707 binary). This change prevents us from missing unexpected log
14708 messages simply because we were looking for others. Related to
14710 - The unit tests now log all warning messages with the "BUG" flag.
14711 Previously, they only logged errors by default. This change will
14712 help us make our testing code more correct, and make sure that we
14713 only hit this code when we mean to. In the meantime, however,
14714 there will be more warnings in the unit test logs than before.
14715 This is preparatory work for ticket 19999.
14716 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
14717 assertion as a test failure.
14718 - We've done significant work to make the unit tests run faster.
14720 o Minor features (testing, ipv6):
14721 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
14722 tests. Remove bridges+hs, as it's somewhat redundant. This
14723 requires a recent chutney version that supports IPv6 clients,
14724 relays, and authorities. Closes ticket 20069; patch by teor.
14725 - Add the single-onion and single-onion-ipv6 chutney targets to
14726 "make test-network-all". This requires a recent chutney version
14727 with the single onion network flavors (git c72a652 or later).
14728 Closes ticket 20072; patch by teor.
14730 o Minor features (Tor2web):
14731 - Make Tor2web clients respect ReachableAddresses. This feature was
14732 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
14733 0.2.8.7. Implements feature 20034. Patch by teor.
14735 o Minor features (unix domain sockets):
14736 - When configuring a unix domain socket for a SocksPort,
14737 ControlPort, or Hidden service, you can now wrap the address in
14738 quotes, using C-style escapes inside the quotes. This allows unix
14739 domain socket paths to contain spaces. Resolves ticket 18753.
14741 o Minor features (user interface):
14742 - Tor now supports the ability to declare options deprecated, so
14743 that we can recommend that people stop using them. Previously, this
14744 was done in an ad-hoc way. There is a new --list-deprecated-options
14745 command-line option to list all of the deprecated options. Closes
14748 o Minor features (virtual addresses):
14749 - Increase the maximum number of bits for the IPv6 virtual network
14750 prefix from 16 to 104. In this way, the condition for address
14751 allocation is less restrictive. Closes ticket 20151; feature
14754 o Minor bug fixes (circuits):
14755 - Use the CircuitBuildTimeout option whenever
14756 LearnCircuitBuildTimeout is disabled. Previously, we would respect
14757 the option when a user disabled it, but not when it was disabled
14758 because some other option was set. Fixes bug 20073; bugfix on
14759 0.2.4.12-alpha. Patch by teor.
14761 o Minor bugfixes (build):
14762 - The current Git revision when building from a local repository is
14763 now detected correctly when using git worktrees. Fixes bug 20492;
14764 bugfix on 0.2.3.9-alpha.
14766 o Minor bugfixes (relay address discovery):
14767 - Stop reordering IP addresses returned by the OS. This makes it
14768 more likely that Tor will guess the same relay IP address every
14769 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
14770 Reported by René Mayrhofer, patch by "cypherpunks".
14772 o Minor bugfixes (memory allocation):
14773 - Change how we allocate memory for large chunks on buffers, to
14774 avoid a (currently impossible) integer overflow, and to waste less
14775 space when allocating unusually large chunks. Fixes bug 20081;
14776 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
14778 o Minor bugfixes (bootstrap):
14779 - Remember the directory server we fetched the consensus or previous
14780 certificates from, and use it to fetch future authority
14781 certificates. This change improves bootstrapping performance.
14782 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
14784 o Minor bugfixes (circuits):
14785 - Make sure extend_info_from_router() is only called on servers.
14786 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
14788 o Minor bugfixes (client, fascistfirewall):
14789 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
14790 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
14792 o Minor bugfixes (client, unix domain sockets):
14793 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
14794 the client address is meaningless. Fixes bug 20261; bugfix
14797 o Minor bugfixes (code style):
14798 - Fix an integer signedness conversion issue in the case conversion
14799 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
14801 o Minor bugfixes (compilation):
14802 - Build correctly on versions of libevent2 without support for
14803 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
14805 - When building with Clang, use a full set of GCC warnings.
14806 (Previously, we included only a subset, because of the way we
14807 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
14808 - Detect Libevent2 functions correctly on systems that provide
14809 libevent2, but where libevent1 is linked with -levent. Fixes bug
14810 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
14811 - Run correctly when built on Windows build environments that
14812 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
14814 o Minor bugfixes (configuration):
14815 - When parsing quoted configuration values from the torrc file,
14816 handle Windows line endings correctly. Fixes bug 19167; bugfix on
14817 0.2.0.16-alpha. Patch from "Pingl".
14819 o Minor bugfixes (directory authority):
14820 - Authorities now sort the "package" lines in their votes, for ease
14821 of debugging. (They are already sorted in consensus documents.)
14822 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
14823 - Die with a more useful error when the operator forgets to place
14824 the authority_signing_key file into the keys directory. This
14825 avoids an uninformative assert & traceback about having an invalid
14826 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
14827 - When allowing private addresses, mark Exits that only exit to
14828 private locations as such. Fixes bug 20064; bugfix
14830 - When parsing a detached signature, make sure we use the length of
14831 the digest algorithm instead of a hardcoded DIGEST256_LEN in
14832 order to avoid comparing bytes out-of-bounds with a smaller digest
14833 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
14835 o Minor bugfixes (getpass):
14836 - Defensively fix a non-triggerable heap corruption at do_getpass()
14837 to protect ourselves from mistakes in the future. Fixes bug
14838 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
14841 o Minor bugfixes (guard selection):
14842 - Don't mark guards as unreachable if connection_connect() fails.
14843 That function fails for local reasons, so it shouldn't reveal
14844 anything about the status of the guard. Fixes bug 14334; bugfix
14846 - Use a single entry guard even if the NumEntryGuards consensus
14847 parameter is not provided. Fixes bug 17688; bugfix
14850 o Minor bugfixes (hidden services):
14851 - Increase the minimum number of internal circuits we preemptively
14852 build from 2 to 3, so a circuit is available when a client
14853 connects to another onion service. Fixes bug 13239; bugfix
14855 - Allow hidden services to run on IPv6 addresses even when the
14856 IPv6Exit option is not set. Fixes bug 18357; bugfix
14858 - Stop logging intro point details to the client log on certain
14859 error conditions. Fixed as part of bug 20012; bugfix on
14860 0.2.4.8-alpha. Patch by teor.
14861 - When deleting an ephemeral hidden service, close its intro points
14862 even if they are not completely open. Fixes bug 18604; bugfix
14864 - When configuring hidden services, check every hidden service
14865 directory's permissions. Previously, we only checked the last
14866 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
14868 o Minor bugfixes (IPv6, testing):
14869 - Check for IPv6 correctly on Linux when running test networks.
14870 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
14872 o Minor bugfixes (Linux seccomp2 sandbox):
14873 - Add permission to run the sched_yield() and sigaltstack() system
14874 calls, in order to support versions of Tor compiled with asan or
14875 ubsan code that use these calls. Now "sandbox 1" and
14876 "--enable-expensive-hardening" should be compatible on more
14877 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
14879 o Minor bugfixes (logging):
14880 - Downgrade a harmless log message about the
14881 pending_entry_connections list from "warn" to "info". Mitigates
14883 - Log a more accurate message when we fail to dump a microdescriptor.
14884 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
14885 - When logging a directory ownership mismatch, log the owning
14886 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
14887 - When we are unable to remove the bw_accounting file, do not warn
14888 if the reason we couldn't remove it was that it didn't exist.
14889 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
14891 o Minor bugfixes (memory leak):
14892 - Fix a series of slow memory leaks related to parsing torrc files
14893 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
14894 - Avoid a small memory leak when informing worker threads about
14895 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
14896 - Fix a small memory leak when receiving AF_UNIX connections on a
14897 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
14898 - When moving a signed descriptor object from a source to an
14899 existing destination, free the allocated memory inside that
14900 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
14901 - Fix a memory leak and use-after-free error when removing entries
14902 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
14903 0.2.5.5-alpha. Patch from "cypherpunks".
14904 - Fix a small, uncommon memory leak that could occur when reading a
14905 truncated ed25519 key file. Fixes bug 18956; bugfix
14908 o Minor bugfixes (option parsing):
14909 - Count unix sockets when counting client listeners (SOCKS, Trans,
14910 NATD, and DNS). This has no user-visible behavior changes: these
14911 options are set once, and never read. Required for correct
14912 behavior in ticket 17178. Fixes bug 19677; bugfix on
14913 0.2.6.3-alpha. Patch by teor.
14915 o Minor bugfixes (options):
14916 - Check the consistency of UseEntryGuards and EntryNodes more
14917 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
14919 - Stop changing the configured value of UseEntryGuards on
14920 authorities and Tor2web clients. Fixes bug 20074; bugfix on
14921 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
14924 o Minor bugfixes (relay):
14925 - Ensure relays don't make multiple connections during bootstrap.
14926 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
14927 - Do not try to parallelize workers more than 16x without the user
14928 explicitly configuring us to do so, even if we do detect more than
14929 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
14931 o Minor bugfixes (testing):
14932 - The test-stem and test-network makefile targets now depend only on
14933 the tor binary that they are testing. Previously, they depended on
14934 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
14935 patch from "cypherpunks".
14936 - Allow clients to retry HSDirs much faster in test networks. Fixes
14937 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
14938 - Avoid a unit test failure on systems with over 16 detectable CPU
14939 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
14940 - Let backtrace tests work correctly under AddressSanitizer:
14941 disable ASAN's detection of segmentation faults while running
14942 test_bt.sh, so that we can make sure that our own backtrace
14943 generation code works. Fixes bug 18934; bugfix
14944 on 0.2.5.2-alpha. Patch from "cypherpunks".
14945 - Fix the test-network-all target on out-of-tree builds by using the
14946 correct path to the test driver script. Fixes bug 19421; bugfix
14948 - Stop spurious failures in the local interface address discovery
14949 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
14951 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
14952 removed the ECDH ciphers which caused the tests to fail on
14953 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
14954 - The tor_tls_server_info_callback unit test no longer crashes when
14955 debug-level logging is turned on. Fixes bug 20041; bugfix
14958 o Minor bugfixes (time):
14959 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
14960 bugfix on all released tor versions.
14961 - When computing the difference between two times in milliseconds,
14962 we now round to the nearest millisecond correctly. Previously, we
14963 could sometimes round in the wrong direction. Fixes bug 19428;
14964 bugfix on 0.2.2.2-alpha.
14966 o Minor bugfixes (Tor2web):
14967 - Prevent Tor2web clients from running hidden services: these services
14968 are not anonymous due to the one-hop client paths. Fixes bug
14969 19678. Patch by teor.
14971 o Minor bugfixes (user interface):
14972 - Display a more accurate number of suppressed messages in the log
14973 rate-limiter. Previously, there was a potential integer overflow
14974 in the counter. Now, if the number of messages hits a maximum, the
14975 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
14977 - Fix a typo in the passphrase prompt for the ed25519 identity key.
14978 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
14980 o Code simplification and refactoring:
14981 - Remove redundant declarations of the MIN macro. Closes
14983 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
14984 Closes ticket 18462; patch from "icanhasaccount".
14985 - Split the 600-line directory_handle_command_get function into
14986 separate functions for different URL types. Closes ticket 16698.
14989 - Add module-level internal documentation for 36 C files that
14990 previously didn't have a high-level overview. Closes ticket 20385.
14991 - Correct the IPv6 syntax in our documentation for the
14992 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
14993 - Correct the minimum bandwidth value in torrc.sample, and queue a
14994 corresponding change for torrc.minimal. Closes ticket 20085.
14995 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
14996 ticket 19153. Patch from "U+039b".
14997 - Module-level documentation for several more modules. Closes
14998 tickets 19287 and 19290.
14999 - Document the --passphrase-fd option in the tor manpage. Fixes bug
15000 19504; bugfix on 0.2.7.3-rc.
15001 - Document the default PathsNeededToBuildCircuits value that's used
15002 by clients when the directory authorities don't set
15003 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
15004 Patch by teor, reported by Jesse V.
15005 - Fix manual for the User option: it takes a username, not a UID.
15006 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
15008 - Fix the description of the --passphrase-fd option in the
15009 tor-gencert manpage. The option is used to pass the number of a
15010 file descriptor to read the passphrase from, not to read the file
15011 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
15014 - We no longer include the (dead, deprecated) bufferevent code in
15015 Tor. Closes ticket 19450. Based on a patch from "U+039b".
15017 o Removed features:
15018 - Remove support for "GET /tor/bytes.txt" DirPort request, and
15019 "GETINFO dir-usage" controller request, which were only available
15020 via a compile-time option in Tor anyway. Feature was added in
15021 0.2.2.1-alpha. Resolves ticket 19035.
15022 - There is no longer a compile-time option to disable support for
15023 TransPort. (If you don't want TransPort, just don't use it.) Patch
15024 from "U+039b". Closes ticket 19449.
15027 - Run more workqueue tests as part of "make check". These had
15028 previously been implemented, but you needed to know special
15029 command-line options to enable them.
15030 - We now have unit tests for our code to reject zlib "compression
15031 bombs". (Fortunately, the code works fine.)
15034 Changes in version 0.2.8.11 - 2016-12-08
15035 Tor 0.2.8.11 backports fixes for additional portability issues that
15036 could prevent Tor from building correctly on OSX Sierra, or with
15037 OpenSSL 1.1. Affected users should upgrade; others can safely stay
15040 o Minor bugfixes (portability):
15041 - Avoid compilation errors when building on OSX Sierra. Sierra began
15042 to support the getentropy() and clock_gettime() APIs, but created
15043 a few problems in doing so. Tor 0.2.9 has a more thorough set of
15044 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
15045 monotonic time interfaces. Fixes bug 20865. Bugfix
15048 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
15049 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
15050 architectures. Closes ticket 20588.
15053 Changes in version 0.2.8.10 - 2016-12-02
15054 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
15055 unusable after they left standby mode. It also backports fixes for
15056 a few portability issues and a small but problematic memory leak.
15058 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
15059 - When Tor leaves standby because of a new application request, open
15060 circuits as needed to serve that request. Previously, we would
15061 potentially wait a very long time. Fixes part of bug 19969; bugfix
15064 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
15065 - Clients now respond to new application stream requests immediately
15066 when they arrive, rather than waiting up to one second before
15067 starting to handle them. Fixes part of bug 19969; bugfix
15070 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
15071 - Work around a bug in the OSX 10.12 SDK that would prevent us from
15072 successfully targeting earlier versions of OSX. Resolves
15075 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
15076 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
15077 20551; bugfix on 0.2.1.1-alpha.
15079 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
15080 - Work around a memory leak in OpenSSL 1.1 when encoding public
15081 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
15083 o Minor features (geoip):
15084 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
15088 Changes in version 0.2.8.9 - 2016-10-17
15089 Tor 0.2.8.9 backports a fix for a security hole in previous versions
15090 of Tor that would allow a remote attacker to crash a Tor client,
15091 hidden service, relay, or authority. All Tor users should upgrade to
15092 this version, or to 0.2.9.4-alpha. Patches will be released for older
15095 o Major features (security fixes, also in 0.2.9.4-alpha):
15096 - Prevent a class of security bugs caused by treating the contents
15097 of a buffer chunk as if they were a NUL-terminated string. At
15098 least one such bug seems to be present in all currently used
15099 versions of Tor, and would allow an attacker to remotely crash
15100 most Tor instances, especially those compiled with extra compiler
15101 hardening. With this defense in place, such bugs can't crash Tor,
15102 though we should still fix them as they occur. Closes ticket
15103 20384 (TROVE-2016-10-001).
15105 o Minor features (geoip):
15106 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
15110 Changes in version 0.2.8.8 - 2016-09-23
15111 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
15112 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
15113 who select public relays as their bridges.
15115 o Major bugfixes (crash):
15116 - Fix a complicated crash bug that could affect Tor clients
15117 configured to use bridges when replacing a networkstatus consensus
15118 in which one of their bridges was mentioned. OpenBSD users saw
15119 more crashes here, but all platforms were potentially affected.
15120 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
15122 o Major bugfixes (relay, OOM handler):
15123 - Fix a timing-dependent assertion failure that could occur when we
15124 tried to flush from a circuit after having freed its cells because
15125 of an out-of-memory condition. Fixes bug 20203; bugfix on
15126 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
15129 o Minor feature (fallback directories):
15130 - Remove broken fallbacks from the hard-coded fallback directory
15131 list. Closes ticket 20190; patch by teor.
15133 o Minor features (geoip):
15134 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
15138 Changes in version 0.2.8.7 - 2016-08-24
15139 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
15140 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
15141 who sets the ReachableAddresses option, and all bridges, are strongly
15142 encouraged to upgrade.
15144 o Directory authority changes:
15145 - The "Tonga" bridge authority has been retired; the new bridge
15146 authority is "Bifroest". Closes tickets 19728 and 19690.
15148 o Major bugfixes (client, security):
15149 - Only use the ReachableAddresses option to restrict the first hop
15150 in a path. In earlier versions of 0.2.8.x, it would apply to
15151 every hop in the path, with a possible degradation in anonymity
15152 for anyone using an uncommon ReachableAddress setting. Fixes bug
15153 19973; bugfix on 0.2.8.2-alpha.
15155 o Minor features (geoip):
15156 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
15159 o Minor bugfixes (compilation):
15160 - Remove an inappropriate "inline" in tortls.c that was causing
15161 warnings on older versions of GCC. Fixes bug 19903; bugfix
15164 o Minor bugfixes (fallback directories):
15165 - Avoid logging a NULL string pointer when loading fallback
15166 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
15167 and 0.2.8.1-alpha. Report and patch by "rubiate".
15170 Changes in version 0.2.8.6 - 2016-08-02
15172 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
15174 The Tor 0.2.8 series improves client bootstrapping performance,
15175 completes the authority-side implementation of improved identity
15176 keys for relays, and includes numerous bugfixes and performance
15177 improvements throughout the program. This release continues to
15178 improve the coverage of Tor's test suite. For a full list of
15179 changes since Tor 0.2.7, see the ReleaseNotes file.
15181 Below is a list of the changes since Tor 0.2.7.
15183 o New system requirements:
15184 - Tor no longer attempts to support platforms where the "time_t"
15185 type is unsigned. (To the best of our knowledge, only OpenVMS does
15186 this, and Tor has never actually built on OpenVMS.) Closes
15188 - Tor no longer supports versions of OpenSSL with a broken
15189 implementation of counter mode. (This bug was present in OpenSSL
15190 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
15191 longer runs with, these versions.
15192 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
15193 later (released in 2008 and 2009 respectively). If you are
15194 building Tor from the git repository instead of from the source
15195 distribution, and your tools are older than this, you will need to
15196 upgrade. Closes ticket 17732.
15198 o Directory authority changes:
15199 - Update the V3 identity key for the dannenberg directory authority:
15200 it was changed on 18 November 2015. Closes task 17906. Patch
15202 - Urras is no longer a directory authority. Closes ticket 19271.
15204 o Major features (directory system):
15205 - Include a trial list of default fallback directories, based on an
15206 opt-in survey of suitable relays. Doing this should make clients
15207 bootstrap more quickly and reliably, and reduce the load on the
15208 directory authorities. Closes ticket 15775. Patch by teor.
15209 Candidates identified using an OnionOO script by weasel, teor,
15210 gsathya, and karsten.
15211 - Previously only relays that explicitly opened a directory port
15212 (DirPort) accepted directory requests from clients. Now all
15213 relays, with and without a DirPort, accept and serve tunneled
15214 directory requests that they receive through their ORPort. You can
15215 disable this behavior using the new DirCache option. Closes
15217 - When bootstrapping multiple consensus downloads at a time, use the
15218 first one that starts downloading, and close the rest. This
15219 reduces failures when authorities or fallback directories are slow
15220 or down. Together with the code for feature 15775, this feature
15221 should reduces failures due to fallback churn. Implements ticket
15222 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
15223 mikeperry and teor.
15225 o Major features (security, Linux):
15226 - When Tor starts as root on Linux and is told to switch user ID, it
15227 can now retain the capability to bind to low ports. By default,
15228 Tor will do this only when it's switching user ID and some low
15229 ports have been configured. You can change this behavior with the
15230 new option KeepBindCapabilities. Closes ticket 8195.
15232 o Major bugfixes (client, bootstrapping):
15233 - Check if bootstrap consensus downloads are still needed when the
15234 linked connection attaches. This prevents tor making unnecessary
15235 begindir-style connections, which are the only directory
15236 connections tor clients make since the fix for 18483 was merged.
15237 - Fix some edge cases where consensus download connections may not
15238 have been closed, even though they were not needed. Related to fix
15240 - Make relays retry consensus downloads the correct number of times,
15241 rather than the more aggressive client retry count. Fixes part of
15244 o Major bugfixes (dns proxy mode, crash):
15245 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
15246 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
15248 o Major bugfixes (ed25519, voting):
15249 - Actually enable support for authorities to match routers by their
15250 Ed25519 identities. Previously, the code had been written, but
15251 some debugging code that had accidentally been left in the
15252 codebase made it stay turned off. Fixes bug 17702; bugfix
15254 - When collating votes by Ed25519 identities, authorities now
15255 include a "NoEdConsensus" flag if the ed25519 value (or lack
15256 thereof) for a server does not reflect the majority consensus.
15257 Related to bug 17668; bugfix on 0.2.7.2-alpha.
15258 - When generating a vote with keypinning disabled, never include two
15259 entries for the same ed25519 identity. This bug was causing
15260 authorities to generate votes that they could not parse when a
15261 router violated key pinning by changing its RSA identity but
15262 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
15263 18318. Bugfix on 0.2.7.2-alpha.
15265 o Major bugfixes (key management):
15266 - If OpenSSL fails to generate an RSA key, do not retain a dangling
15267 pointer to the previous (uninitialized) key value. The impact here
15268 should be limited to a difficult-to-trigger crash, if OpenSSL is
15269 running an engine that makes key generation failures possible, or
15270 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
15271 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
15274 o Major bugfixes (security, client, DNS proxy):
15275 - Stop a crash that could occur when a client running with DNSPort
15276 received a query with multiple address types, and the first
15277 address type was not supported. Found and fixed by Scott Dial.
15278 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
15280 o Major bugfixes (security, compilation):
15281 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
15282 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
15283 cause a compiler warning, thereby making other checks fail, and
15284 needlessly disabling compiler-hardening support. Fixes one case of
15285 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
15286 - Repair hardened builds under the clang compiler. Previously, our
15287 use of _FORTIFY_SOURCE would conflict with clang's address
15288 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
15290 o Major bugfixes (security, pointers):
15291 - Avoid a difficult-to-trigger heap corruption attack when extending
15292 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
15293 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
15294 Reported by Guido Vranken.
15296 o Major bugfixes (testing):
15297 - Fix a bug that would block 'make test-network-all' on systems where
15298 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
15300 o Major bugfixes (user interface):
15301 - Correctly give a warning in the cases where a relay is specified
15302 by nickname, and one such relay is found, but it is not officially
15303 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
15305 o Minor features (accounting):
15306 - Added two modes to the AccountingRule option: One for limiting
15307 only the number of bytes sent ("AccountingRule out"), and one for
15308 limiting only the number of bytes received ("AccountingRule in").
15309 Closes ticket 15989; patch from "unixninja92".
15311 o Minor features (bug-resistance):
15312 - Make Tor survive errors involving connections without a
15313 corresponding event object. Previously we'd fail with an
15314 assertion; now we produce a log message. Related to bug 16248.
15315 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
15316 level code, to harden against accidental failures to NUL-
15317 terminate. Part of ticket 17852. Patch from jsturgix. Found
15320 o Minor features (build):
15321 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
15322 as having possible IPFW support. Closes ticket 18448. Patch from
15323 Steven Chamberlain.
15324 - Since our build process now uses "make distcheck", we no longer
15325 force "make dist" to depend on "make check". Closes ticket 17893;
15326 patch from "cypherpunks".
15327 - Tor now builds once again with the recent OpenSSL 1.1 development
15328 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
15329 tracking OpenSSL 1.1 development as it has progressed, and fixing
15330 numerous compatibility issues as they arose. See tickets
15331 17549, 17921, 17984, 19499, and 18286.
15332 - When building manual pages, set the timezone to "UTC", so that the
15333 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
15334 Patch from intrigeri.
15336 o Minor features (clients):
15337 - Make clients, onion services, and bridge relays always use an
15338 encrypted begindir connection for directory requests. Resolves
15339 ticket 18483. Patch by teor.
15341 o Minor features (controller):
15342 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
15343 controllers can examine the the reject rules added by
15344 ExitPolicyRejectPrivate. This makes it easier for stem to display
15346 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
15347 tickets 16774 and 17817. Patch by George Tankersley.
15348 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
15349 service descriptor from a service's local hidden service
15350 descriptor cache. Closes ticket 14846.
15352 o Minor features (crypto):
15353 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
15354 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
15356 - Improve performance when hashing non-multiple of 8 sized buffers,
15357 based on Andrew Moon's public domain SipHash-2-4 implementation.
15358 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
15359 - Validate the hard-coded Diffie-Hellman parameters and ensure that
15360 p is a safe prime, and g is a suitable generator. Closes
15362 - When allocating a digest state object, allocate no more space than
15363 we actually need. Previously, we would allocate as much space as
15364 the state for the largest algorithm would need. This change saves
15365 up to 672 bytes per circuit. Closes ticket 17796.
15367 o Minor features (directory downloads):
15368 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
15369 directory mirrors. The default is 1; set it to 0 to disable
15370 fallbacks. Implements ticket 17576. Patch by teor.
15371 - Wait for busy authorities and fallback directories to become non-
15372 busy when bootstrapping. (A similar change was made in 6c443e987d
15373 for directory caches chosen from the consensus.) Closes ticket
15374 17864; patch by teor.
15376 o Minor features (geoip):
15377 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
15380 o Minor features (hidden service directory):
15381 - Streamline relay-side hsdir handling: when relays consider whether
15382 to accept an uploaded hidden service descriptor, they no longer
15383 check whether they are one of the relays in the network that is
15384 "supposed" to handle that descriptor. Implements ticket 18332.
15386 o Minor features (IPv6):
15387 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
15388 to 1, tor prefers IPv6 directory addresses.
15389 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
15390 avoids using IPv4 for client OR and directory connections.
15391 - Add address policy assume_action support for IPv6 addresses.
15392 - Add an argument 'ipv6=address:orport' to the DirAuthority and
15393 FallbackDir torrc options, to specify an IPv6 address for an
15394 authority or fallback directory. Add hard-coded ipv6 addresses for
15395 directory authorities that have them. Closes ticket 17327; patch
15396 from Nick Mathewson and teor.
15397 - Allow users to configure directory authorities and fallback
15398 directory servers with IPv6 addresses and ORPorts. Resolves
15400 - Limit IPv6 mask bits to 128.
15401 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
15402 17638; bugfix on 0.0.2pre8. Patch by teor.
15403 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
15404 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
15405 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
15406 - Warn when comparing against an AF_UNSPEC address in a policy, it's
15407 almost always a bug. Closes ticket 17863; patch by teor.
15408 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
15409 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
15411 o Minor features (Linux seccomp2 sandbox):
15412 - Reject attempts to change our Address with "Sandbox 1" enabled.
15413 Changing Address with Sandbox turned on would never actually work,
15414 but previously it would fail in strange and confusing ways. Found
15415 while fixing 18548.
15417 o Minor features (logging):
15418 - When logging to syslog, allow a tag to be added to the syslog
15419 identity (the string prepended to every log message). The tag can
15420 be configured with SyslogIdentityTag and defaults to none. Setting
15421 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
15424 o Minor features (portability):
15425 - Use timingsafe_memcmp() where available. Closes ticket 17944;
15426 patch from <logan@hackers.mu>.
15428 o Minor features (relay, address discovery):
15429 - Add a family argument to get_interface_addresses_raw() and
15430 subfunctions to make network interface address interogation more
15431 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
15432 types of interfaces from the operating system. Resolves
15434 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
15435 fails to enumerate interface addresses using the platform-specific
15436 API, have it rely on the UDP socket fallback technique to try and
15437 find out what IP addresses (both IPv4 and IPv6) our machine has.
15438 Resolves ticket 17951.
15440 o Minor features (replay cache):
15441 - The replay cache now uses SHA256 instead of SHA1. Implements
15442 feature 8961. Patch by teor, issue reported by rransom.
15444 o Minor features (robustness):
15445 - Exit immediately with an error message if the code attempts to use
15446 Libevent without having initialized it. This should resolve some
15447 frequently-made mistakes in our unit tests. Closes ticket 18241.
15449 o Minor features (security, clock):
15450 - Warn when the system clock appears to move back in time (when the
15451 state file was last written in the future). Tor doesn't know that
15452 consensuses have expired if the clock is in the past. Patch by
15453 teor. Implements ticket 17188.
15455 o Minor features (security, exit policies):
15456 - ExitPolicyRejectPrivate now rejects more private addresses by
15457 default. Specifically, it now rejects the relay's outbound bind
15458 addresses (if configured), and the relay's configured port
15459 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
15460 0.2.0.11-alpha. Patch by teor.
15462 o Minor features (security, memory erasure):
15463 - Make memwipe() do nothing when passed a NULL pointer or buffer of
15464 zero size. Check size argument to memwipe() for underflow. Fixes
15465 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
15467 - Set the unused entries in a smartlist to NULL. This helped catch
15468 a (harmless) bug, and shouldn't affect performance too much.
15469 Implements ticket 17026.
15470 - Use SecureMemoryWipe() function to securely clean memory on
15471 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
15472 Implements feature 17986.
15473 - Use explicit_bzero or memset_s when present. Previously, we'd use
15474 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
15475 from <logan@hackers.mu> and <selven@hackers.mu>.
15477 o Minor features (security, RNG):
15478 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
15479 positively are not allowed to fail. Previously we depended on
15480 internal details of OpenSSL's behavior. Closes ticket 17686.
15481 - Never use the system entropy output directly for anything besides
15482 seeding the PRNG. When we want to generate important keys, instead
15483 of using system entropy directly, we now hash it with the PRNG
15484 stream. This may help resist certain attacks based on broken OS
15485 entropy implementations. Closes part of ticket 17694.
15486 - Use modern system calls (like getentropy() or getrandom()) to
15487 generate strong entropy on platforms that have them. Closes
15490 o Minor features (security, win32):
15491 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
15492 attack. Fixes bug 18123; bugfix on all tor versions. Patch
15495 o Minor features (unix domain sockets):
15496 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
15497 Unix domain sockets without checking the permissions on the parent
15498 directory. (Tor checks permissions by default because some
15499 operating systems only check permissions on the parent directory.
15500 However, some operating systems do look at permissions on the
15501 socket, and tor's default check is unneeded.) Closes ticket 18458.
15504 o Minor features (unix file permissions):
15505 - Defer creation of Unix sockets until after setuid. This avoids
15506 needing CAP_CHOWN and CAP_FOWNER when using systemd's
15507 CapabilityBoundingSet, or chown and fowner when using SELinux.
15508 Implements part of ticket 17562. Patch from Jamie Nguyen.
15509 - If any directory created by Tor is marked as group readable, the
15510 filesystem group is allowed to be either the default GID or the
15511 root user. Allowing root to read the DataDirectory prevents the
15512 need for CAP_READ_SEARCH when using systemd's
15513 CapabilityBoundingSet, or dac_read_search when using SELinux.
15514 Implements part of ticket 17562. Patch from Jamie Nguyen.
15515 - Introduce a new DataDirectoryGroupReadable option. If it is set to
15516 1, the DataDirectory will be made readable by the default GID.
15517 Implements part of ticket 17562. Patch from Jamie Nguyen.
15519 o Minor bugfixes (accounting):
15520 - The max bandwidth when using 'AccountRule sum' is now correctly
15521 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
15522 from "unixninja92".
15524 o Minor bugfixes (assert, portability):
15525 - Fix an assertion failure in memarea.c on systems where "long" is
15526 shorter than the size of a pointer. Fixes bug 18716; bugfix
15529 o Minor bugfixes (bootstrap):
15530 - Consistently use the consensus download schedule for authority
15531 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
15533 o Minor bugfixes (build):
15534 - Avoid spurious failures from configure files related to calling
15535 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
15536 0.2.0.1-alpha. Patch from "cypherpunks".
15537 - Do not link the unit tests against both the testing and non-
15538 testing versions of the static libraries. Fixes bug 18490; bugfix
15540 - Resolve warnings when building on systems that are concerned with
15541 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
15543 - Silence spurious clang-scan warnings in the ed25519_donna code by
15544 explicitly initializing some objects. Fixes bug 18384; bugfix on
15545 0.2.7.2-alpha. Patch by teor.
15546 - When libscrypt.h is found, but no libscrypt library can be linked,
15547 treat libscrypt as absent. Fixes bug 19161; bugfix
15549 - Cause the unit tests to compile correctly on mingw64 versions that
15550 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
15551 - Don't try to use the pthread_condattr_setclock() function unless
15552 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
15553 17819; bugfix on 0.2.6.3-alpha.
15554 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
15556 - Fix search for libevent libraries on OpenBSD (and other systems
15557 that install libevent 1 and libevent 2 in parallel). Fixes bug
15558 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
15559 - Isolate environment variables meant for tests from the rest of the
15560 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
15561 - Mark all object files that include micro-revision.i as depending
15562 on it, so as to make parallel builds more reliable. Fixes bug
15563 17826; bugfix on 0.2.5.1-alpha.
15564 - Remove config.log only from make distclean, not from make clean.
15565 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
15566 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
15568 - Remove an #endif from configure.ac so that we correctly detect the
15569 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
15572 o Minor bugfixes (client, bootstrap):
15573 - Count receipt of new microdescriptors as progress towards
15574 bootstrapping. Previously, with EntryNodes set, Tor might not
15575 successfully repopulate the guard set on bootstrapping. Fixes bug
15576 16825; bugfix on 0.2.3.1-alpha.
15578 o Minor bugfixes (code correctness):
15579 - Fix a bad memory handling bug that would occur if we had queued a
15580 cell on a channel's incoming queue. Fortunately, we can't actually
15581 queue a cell like that as our code is constructed today, but it's
15582 best to avoid this kind of error, even if there isn't any code
15583 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
15584 - Assert that allocated memory held by the reputation code is freed
15585 according to its internal counters. Fixes bug 17753; bugfix
15587 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
15589 - Update to the latest version of Trunnel, which tries harder to
15590 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
15591 by clang address sanitizer. Fixes bug 18373; bugfix
15593 - When closing an entry connection, generate a warning if we should
15594 have sent an end cell for it but we haven't. Fixes bug 17876;
15595 bugfix on 0.2.3.2-alpha.
15597 o Minor bugfixes (configuration):
15598 - Fix a tiny memory leak when parsing a port configuration ending in
15599 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
15601 o Minor bugfixes (containers):
15602 - If we somehow attempt to construct a heap with more than
15603 1073741822 elements, avoid an integer overflow when maintaining
15604 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
15606 o Minor bugfixes (controller, microdescriptors):
15607 - Make GETINFO dir/status-vote/current/consensus conform to the
15608 control specification by returning "551 Could not open cached
15609 consensus..." when not caching consensuses. Fixes bug 18920;
15610 bugfix on 0.2.2.6-alpha.
15612 o Minor bugfixes (crypto):
15613 - Check the return value of HMAC() and assert on failure. Fixes bug
15614 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
15616 o Minor bugfixes (directories):
15617 - When fetching extrainfo documents, compare their SHA256 digests
15618 and Ed25519 signing key certificates with the routerinfo that led
15619 us to fetch them, rather than with the most recent routerinfo.
15620 Otherwise we generate many spurious warnings about mismatches.
15621 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
15622 - When generating a URL for a directory server on an IPv6 address,
15623 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
15624 on 0.2.3.9-alpha. Patch from Malek.
15626 o Minor bugfixes (downloading):
15627 - Predict more correctly whether we'll be downloading over HTTP when
15628 we determine the maximum length of a URL. This should avoid a
15629 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
15632 o Minor bugfixes (exit policies, security):
15633 - Refresh an exit relay's exit policy when interface addresses
15634 change. Previously, tor only refreshed the exit policy when the
15635 configured external address changed. Fixes bug 18208; bugfix on
15636 0.2.7.3-rc. Patch by teor.
15638 o Minor bugfixes (fallback directories):
15639 - Mark fallbacks as "too busy" when they return a 503 response,
15640 rather than just marking authorities. Fixes bug 17572; bugfix on
15641 0.2.4.7-alpha. Patch by teor.
15642 - When requesting extrainfo descriptors from a trusted directory
15643 server, check whether it is an authority or a fallback directory
15644 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
15645 0.2.4.7-alpha. Reported by atagar, patch by teor.
15647 o Minor bugfixes (hidden service, client):
15648 - Handle the case where the user makes several fast consecutive
15649 requests to the same .onion address. Previously, the first six
15650 requests would each trigger a descriptor fetch, each picking a
15651 directory (there are 6 overall) and the seventh one would fail
15652 because no directories were left, thereby triggering a close on
15653 all current directory connections asking for the hidden service.
15654 The solution here is to not close the connections if we have
15655 pending directory fetches. Fixes bug 15937; bugfix
15658 o Minor bugfixes (hidden service, control port):
15659 - Add the onion address to the HS_DESC event for the UPLOADED action
15660 both on success or failure. It was previously hardcoded with
15661 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
15663 o Minor bugfixes (hidden service, directory):
15664 - Bridges now refuse "rendezvous2" (hidden service descriptor)
15665 publish attempts. Suggested by ticket 18332.
15667 o Minor bugfixes (IPv6):
15668 - Update the limits in max_dl_per_request for IPv6 address length.
15669 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
15671 o Minor bugfixes (Linux seccomp2 sandbox):
15672 - Allow more syscalls when running with "Sandbox 1" enabled:
15673 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
15674 some systems, these are required for Tor to start. Fixes bug
15675 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
15676 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
15677 so that get_interface_address6_via_udp_socket_hack() can work.
15678 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
15679 - Allow the setrlimit syscall, and the prlimit and prlimit64
15680 syscalls, which some libc implementations use under the hood.
15681 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
15682 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
15683 enabled and no DNS resolvers configured. This should help TAILS
15684 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
15685 - Fix a crash when using offline master ed25519 keys with the Linux
15686 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
15687 - Allow statistics to be written to disk when "Sandbox 1" is
15688 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
15689 0.2.6.1-alpha respectively.
15691 o Minor bugfixes (logging):
15692 - In log messages that include a function name, use __FUNCTION__
15693 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
15694 with clang __PRETTY_FUNCTION__ has extra information we don't
15695 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
15697 - Remove needless quotes from a log message about unparseable
15698 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
15699 - Scrub service name in "unrecognized service ID" log messages.
15700 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
15701 - When logging information about an unparsable networkstatus vote or
15702 consensus, do not say "vote" when we mean consensus. Fixes bug
15703 18368; bugfix on 0.2.0.8-alpha.
15704 - When we can't generate a signing key because OfflineMasterKey is
15705 set, do not imply that we should have been able to load it. Fixes
15706 bug 18133; bugfix on 0.2.7.2-alpha.
15707 - When logging a malformed hostname received through socks4, scrub
15708 it if SafeLogging says we should. Fixes bug 17419; bugfix
15711 o Minor bugfixes (memory safety):
15712 - Avoid freeing an uninitialized pointer when opening a socket fails
15713 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
15714 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
15716 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
15717 18672; bugfix on 0.2.5.1-alpha.
15718 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
15721 o Minor bugfixes (pluggable transports):
15722 - Avoid reporting a spurious error when we decide that we don't need
15723 to terminate a pluggable transport because it has already exited.
15724 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
15726 o Minor bugfixes (pointer arithmetic):
15727 - Fix a bug in memarea_alloc() that could have resulted in remote
15728 heap write access, if Tor had ever passed an unchecked size to
15729 memarea_alloc(). Fortunately, all the sizes we pass to
15730 memarea_alloc() are pre-checked to be less than 128 kilobytes.
15731 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
15734 o Minor bugfixes (private directory):
15735 - Prevent a race condition when creating private directories. Fixes
15736 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
15737 Patch from jsturgix. Found with Flawfinder.
15739 o Minor bugfixes (relays):
15740 - Check that both the ORPort and DirPort (if present) are reachable
15741 before publishing a relay descriptor. Otherwise, relays publish a
15742 descriptor with DirPort 0 when the DirPort reachability test takes
15743 longer than the ORPort reachability test. Fixes bug 18050; bugfix
15744 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
15745 - Resolve some edge cases where we might launch an ORPort
15746 reachability check even when DisableNetwork is set. Noticed while
15747 fixing bug 18616; bugfix on 0.2.3.9-alpha.
15749 o Minor bugfixes (relays, hidden services):
15750 - Refuse connection requests to private OR addresses unless
15751 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
15752 then refuse to send any cells to a private address. Fixes bugs
15753 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
15755 o Minor bugfixes (security, hidden services):
15756 - Prevent hidden services connecting to client-supplied rendezvous
15757 addresses that are reserved as internal or multicast. Fixes bug
15758 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
15760 o Minor bugfixes (statistics):
15761 - Consistently check for overflow in round_*_to_next_multiple_of
15762 functions, and add unit tests with additional and maximal values.
15763 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
15764 - Handle edge cases in the laplace functions: avoid division by
15765 zero, avoid taking the log of zero, and silence clang type
15766 conversion warnings using round and trunc. Add unit tests for edge
15767 cases with maximal values. Fixes part of bug 13192; bugfix
15769 - We now include consensus downloads via IPv6 in our directory-
15770 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
15772 o Minor bugfixes (test networks, IPv6):
15773 - Allow internal IPv6 addresses in descriptors in test networks.
15774 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
15777 o Minor bugfixes (testing):
15778 - Check the full results of SHA256 and SHA512 digests in the unit
15779 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
15780 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
15782 - Fix a small memory leak that would occur when the
15783 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
15784 bugfix on 0.2.5.2-alpha.
15785 - Make unit tests pass on IPv6-only systems, and systems without
15786 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
15787 bugfix on 0.2.7.3-rc. Patch by teor.
15788 - The test for log_heartbeat was incorrectly failing in timezones
15789 with non-integer offsets. Instead of comparing the end of the time
15790 string against a constant, compare it to the output of
15791 format_local_iso_time when given the correct input. Fixes bug
15792 18039; bugfix on 0.2.5.4-alpha.
15793 - We no longer disable assertions in the unit tests when coverage is
15794 enabled. Instead, we require you to say --disable-asserts-in-tests
15795 to the configure script if you need assertions disabled in the
15796 unit tests (for example, if you want to perform branch coverage).
15797 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
15799 o Minor bugfixes (time handling):
15800 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
15801 field. Otherwise, our unit tests crash on Windows. Fixes bug
15802 18977; bugfix on 0.2.2.25-alpha.
15803 - Avoid overflow in tor_timegm when parsing dates in and after 2038
15804 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
15805 0.0.2pre14. Patch by teor.
15807 o Minor bugfixes (tor-gencert):
15808 - Correctly handle the case where an authority operator enters a
15809 passphrase but sends an EOF before sending a newline. Fixes bug
15810 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
15812 o Code simplification and refactoring:
15813 - Clean up a little duplicated code in
15814 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
15816 - Decouple the list of streams waiting to be attached to circuits
15817 from the overall connection list. This change makes it possible to
15818 attach streams quickly while simplifying Tor's callgraph and
15819 avoiding O(N) scans of the entire connection list. Closes
15821 - Extract the more complicated parts of circuit_mark_for_close()
15822 into a new function that we run periodically before circuits are
15823 freed. This change removes more than half of the functions
15824 currently in the "blob". Closes ticket 17218.
15825 - Move logging of redundant policy entries in
15826 policies_parse_exit_policy_internal into its own function. Closes
15827 ticket 17608; patch from "juce".
15828 - Quote all the string interpolations in configure.ac -- even those
15829 which we are pretty sure can't contain spaces. Closes ticket
15830 17744. Patch from zerosion.
15831 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
15832 use them. Closes ticket 17926.
15833 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
15834 inplace, so there's no need to have a separate implementation for
15835 the non-inplace code. Closes ticket 18258. Patch from Malek.
15836 - Simplify return types for some crypto functions that can't
15837 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
15838 - When a direct directory request fails immediately on launch,
15839 instead of relaunching that request from inside the code that
15840 launches it, instead mark the connection for teardown. This change
15841 simplifies Tor's callback and prevents the directory-request
15842 launching code from invoking itself recursively. Closes
15846 - Add a description of the correct use of the '--keygen' command-
15847 line option. Closes ticket 17583; based on text by 's7r'.
15848 - Change build messages to refer to "Fedora" instead of "Fedora
15849 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
15850 Patches from "icanhasaccount" and "cypherpunks".
15851 - Document the contents of the 'datadir/keys' subdirectory in the
15852 manual page. Closes ticket 17621.
15853 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
15854 - Explain actual minima for BandwidthRate. Closes ticket 16382.
15855 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
15856 - Mention torspec URL in the manpage and point the reader to it
15857 whenever we mention a document that belongs in torspce. Fixes
15859 - Stop recommending use of nicknames to identify relays in our
15860 MapAddress documentation. Closes ticket 18312.
15862 o Removed features:
15863 - Remove client-side support for connecting to Tor relays running
15864 versions of Tor before 0.2.3.6-alpha. These relays didn't support
15865 the v3 TLS handshake protocol, and are no longer allowed on the
15866 Tor network. Implements the client side of ticket 11150. Based on
15867 patches by Tom van der Woerdt.
15868 - We no longer maintain an internal freelist in memarea.c.
15869 Allocators should be good enough to make this code unnecessary,
15870 and it's doubtful that it ever had any performance benefit.
15873 - Add unit tests to check for common RNG failure modes, such as
15874 returning all zeroes, identical values, or incrementing values
15875 (OpenSSL's rand_predictable feature). Patch by teor.
15876 - Always test both ed25519 backends, so that we can be sure that our
15877 batch-open replacement code works. Part of ticket 16794.
15878 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
15879 portion of ticket 16831.
15880 - Fix several warnings from clang's address sanitizer produced in
15882 - Log more information when the backtrace tests fail. Closes ticket
15883 17892. Patch from "cypherpunks."
15884 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
15885 util_format.c, directory.c, and options_validate.c. Closes tickets
15886 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
15888 - Treat backtrace test failures as expected on FreeBSD until we
15889 solve bug 17808. Closes ticket 18204.
15890 - Unit tests for directory_handle_command_get. Closes ticket 17004.
15891 Patch from Reinaldo de Souza Jr.
15894 Changes in version 0.2.7.6 - 2015-12-10
15895 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
15896 well as a minor bug in hidden service reliability.
15898 o Major bugfixes (guard selection):
15899 - Actually look at the Guard flag when selecting a new directory
15900 guard. When we implemented the directory guard design, we
15901 accidentally started treating all relays as if they have the Guard
15902 flag during guard selection, leading to weaker anonymity and worse
15903 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
15906 o Minor features (geoip):
15907 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
15910 o Minor bugfixes (compilation):
15911 - When checking for net/pfvar.h, include netinet/in.h if possible.
15912 This fixes transparent proxy detection on OpenBSD. Fixes bug
15913 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
15914 - Fix a compilation warning with Clang 3.6: Do not check the
15915 presence of an address which can never be NULL. Fixes bug 17781.
15917 o Minor bugfixes (correctness):
15918 - When displaying an IPv6 exit policy, include the mask bits
15919 correctly even when the number is greater than 31. Fixes bug
15920 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
15921 - The wrong list was used when looking up expired intro points in a
15922 rend service object, causing what we think could be reachability
15923 issues for hidden services, and triggering a BUG log. Fixes bug
15924 16702; bugfix on 0.2.7.2-alpha.
15925 - Fix undefined behavior in the tor_cert_checksig function. Fixes
15926 bug 17722; bugfix on 0.2.7.2-alpha.
15929 Changes in version 0.2.7.5 - 2015-11-20
15930 The Tor 0.2.7 release series is dedicated to the memory of Tor user
15931 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
15932 tirelessly to advocate human rights regardless of national borders,
15933 and oppose the encroachments of mass surveillance. He opposed national
15934 exceptionalism, he brought clarity to legal and policy debates, he
15935 understood and predicted the impact of mass surveillance on the world,
15936 and he laid the groundwork for resisting it. While serving on the Tor
15937 Project's board of directors, he brought us his uncompromising focus
15938 on technical excellence in the service of humankind. Caspar was an
15939 inimitable force for good and a wonderful friend. He was kind,
15940 humorous, generous, gallant, and believed we should protect one
15941 another without exception. We honor him here for his ideals, his
15942 efforts, and his accomplishments. Please honor his memory with works
15943 that would make him proud.
15945 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
15947 The 0.2.7 series adds a more secure identity key type for relays,
15948 improves cryptography performance, resolves several longstanding
15949 hidden-service performance issues, improves controller support for
15950 hidden services, and includes small bugfixes and performance
15951 improvements throughout the program. This release series also includes
15952 more tests than before, and significant simplifications to which parts
15953 of Tor invoke which others. For a full list of changes, see below.
15955 o New system requirements:
15956 - Tor no longer includes workarounds to support Libevent versions
15957 before 1.3e. Libevent 2.0 or later is recommended. Closes
15959 - Tor no longer supports copies of OpenSSL that are missing support
15960 for Elliptic Curve Cryptography. (We began using ECC when
15961 available in 0.2.4.8-alpha, for more safe and efficient key
15962 negotiation.) In particular, support for at least one of P256 or
15963 P224 is now required, with manual configuration needed if only
15964 P224 is available. Resolves ticket 16140.
15965 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
15966 on an operating system that has not upgraded to OpenSSL 1.0 or
15967 later, and you compile Tor from source, you will need to install a
15968 more recent OpenSSL to link Tor against.) These versions of
15969 OpenSSL are still supported by the OpenSSL, but the numerous
15970 cryptographic improvements in later OpenSSL releases makes them a
15971 clear choice. Resolves ticket 16034.
15973 o Major features (controller):
15974 - Add the ADD_ONION and DEL_ONION commands that allow the creation
15975 and management of hidden services via the controller. Closes
15977 - New "GETINFO onions/current" and "GETINFO onions/detached"
15978 commands to get information about hidden services created via the
15979 controller. Part of ticket 6411.
15980 - New HSFETCH command to launch a request for a hidden service
15981 descriptor. Closes ticket 14847.
15982 - New HSPOST command to upload a hidden service descriptor. Closes
15983 ticket 3523. Patch by "DonnchaC".
15985 o Major features (Ed25519 identity keys, Proposal 220):
15986 - Add support for offline encrypted Ed25519 master keys. To use this
15987 feature on your tor relay, run "tor --keygen" to make a new master
15988 key (or to make a new signing key if you already have a master
15989 key). Closes ticket 13642.
15990 - All relays now maintain a stronger identity key, using the Ed25519
15991 elliptic curve signature format. This master key is designed so
15992 that it can be kept offline. Relays also generate an online
15993 signing key, and a set of other Ed25519 keys and certificates.
15994 These are all automatically regenerated and rotated as needed.
15995 Implements part of ticket 12498.
15996 - Directory authorities now vote on Ed25519 identity keys along with
15997 RSA1024 keys. Implements part of ticket 12498.
15998 - Directory authorities track which Ed25519 identity keys have been
15999 used with which RSA1024 identity keys, and do not allow them to
16000 vary freely. Implements part of ticket 12498.
16001 - Microdescriptors now include Ed25519 identity keys. Implements
16002 part of ticket 12498.
16003 - Add a --newpass option to allow changing or removing the
16004 passphrase of an encrypted key with tor --keygen. Implements part
16006 - Add a new OfflineMasterKey option to tell Tor never to try loading
16007 or generating a secret Ed25519 identity key. You can use this in
16008 combination with tor --keygen to manage offline and/or encrypted
16009 Ed25519 keys. Implements ticket 16944.
16010 - On receiving a HUP signal, check to see whether the Ed25519
16011 signing key has changed, and reload it if so. Closes ticket 16790.
16012 - Significant usability improvements for Ed25519 key management. Log
16013 messages are better, and the code can recover from far more
16014 failure conditions. Thanks to "s7r" for reporting and diagnosing
16017 o Major features (ECC performance):
16018 - Improve the runtime speed of Ed25519 signature verification by
16019 using Ed25519-donna's batch verification support. Implements
16021 - Improve the speed of Ed25519 operations and Curve25519 keypair
16022 generation when built targeting 32 bit x86 platforms with SSE2
16023 available. Implements ticket 16535.
16024 - Improve the runtime speed of Ed25519 operations by using the
16025 public-domain Ed25519-donna by Andrew M. ("floodyberry").
16026 Implements ticket 16467.
16027 - Improve the runtime speed of the ntor handshake by using an
16028 optimized curve25519 basepoint scalarmult implementation from the
16029 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
16030 ideas by Adam Langley. Implements ticket 9663.
16032 o Major features (Hidden services):
16033 - Hidden services, if using the EntryNodes option, are required to
16034 use more than one EntryNode, in order to avoid a guard discovery
16035 attack. (This would only affect people who had configured hidden
16036 services and manually specified the EntryNodes option with a
16037 single entry-node. The impact was that it would be easy to
16038 remotely identify the guard node used by such a hidden service.
16039 See ticket for more information.) Fixes ticket 14917.
16040 - Add the torrc option HiddenServiceNumIntroductionPoints, to
16041 specify a fixed number of introduction points. Its maximum value
16042 is 10 and default is 3. Using this option can increase a hidden
16043 service's reliability under load, at the cost of making it more
16044 visible that the hidden service is facing extra load. Closes
16046 - Remove the adaptive algorithm for choosing the number of
16047 introduction points, which used to change the number of
16048 introduction points (poorly) depending on the number of
16049 connections the HS sees. Closes ticket 4862.
16051 o Major features (onion key cross-certification):
16052 - Relay descriptors now include signatures of their own identity
16053 keys, made using the TAP and ntor onion keys. These signatures
16054 allow relays to prove ownership of their own onion keys. Because
16055 of this change, microdescriptors will no longer need to include
16056 RSA identity keys. Implements proposal 228; closes ticket 12499.
16058 o Major bugfixes (client-side privacy, also in 0.2.6.9):
16059 - Properly separate out each SOCKSPort when applying stream
16060 isolation. The error occurred because each port's session group
16061 was being overwritten by a default value when the listener
16062 connection was initialized. Fixes bug 16247; bugfix on
16063 0.2.6.3-alpha. Patch by "jojelino".
16065 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
16066 - Stop refusing to store updated hidden service descriptors on a
16067 client. This reverts commit 9407040c59218 (which indeed fixed bug
16068 14219, but introduced a major hidden service reachability
16069 regression detailed in bug 16381). This is a temporary fix since
16070 we can live with the minor issue in bug 14219 (it just results in
16071 some load on the network) but the regression of 16381 is too much
16072 of a setback. First-round fix for bug 16381; bugfix
16075 o Major bugfixes (hidden services):
16076 - Revert commit that made directory authorities assign the HSDir
16077 flag to relays without a DirPort; this was bad because such relays
16078 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
16080 - When cannibalizing a circuit for an introduction point, always
16081 extend to the chosen exit node (creating a 4 hop circuit).
16082 Previously Tor would use the current circuit exit node, which
16083 changed the original choice of introduction point, and could cause
16084 the hidden service to skip excluded introduction points or
16085 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
16088 o Major bugfixes (memory leaks):
16089 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
16090 17398; bugfix on 0.2.6.1-alpha.
16092 o Major bugfixes (open file limit):
16093 - The open file limit wasn't checked before calling
16094 tor_accept_socket_nonblocking(), which would make Tor exceed the
16095 limit. Now, before opening a new socket, Tor validates the open
16096 file limit just before, and if the max has been reached, return an
16097 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
16099 o Major bugfixes (security, correctness):
16100 - Fix an error that could cause us to read 4 bytes before the
16101 beginning of an openssl string. This bug could be used to cause
16102 Tor to crash on systems with unusual malloc implementations, or
16103 systems with unusual hardening installed. Fixes bug 17404; bugfix
16106 o Major bugfixes (stability, also in 0.2.6.10):
16107 - Stop crashing with an assertion failure when parsing certain kinds
16108 of malformed or truncated microdescriptors. Fixes bug 16400;
16109 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
16110 by "cypherpunks_backup".
16111 - Stop random client-side assertion failures that could occur when
16112 connecting to a busy hidden service, or connecting to a hidden
16113 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
16116 o Minor features (client, SOCKS):
16117 - Add GroupWritable and WorldWritable options to unix-socket based
16118 SocksPort and ControlPort options. These options apply to a single
16119 socket, and override {Control,Socks}SocketsGroupWritable. Closes
16121 - Relax the validation done to hostnames in SOCKS5 requests, and
16122 allow a single trailing '.' to cope with clients that pass FQDNs
16123 using that syntax to explicitly indicate that the domain name is
16124 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
16125 - Relax the validation of hostnames in SOCKS5 requests, allowing the
16126 character '_' to appear, in order to cope with domains observed in
16127 the wild that are serving non-RFC compliant records. Resolves
16130 o Minor features (client-side privacy):
16131 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
16132 lifespan when IsolateSOCKSAuth and streams with SOCKS
16133 authentication are attached to the circuit. This allows
16134 applications like TorBrowser to manage circuit lifetime on their
16135 own. Implements feature 15482.
16136 - When logging malformed hostnames from SOCKS5 requests, respect
16137 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
16139 o Minor features (clock-jump tolerance):
16140 - Recover better when our clock jumps back many hours, like might
16141 happen for Tails or Whonix users who start with a very wrong
16142 hardware clock, use Tor to discover a more accurate time, and then
16143 fix their clock. Resolves part of ticket 8766.
16145 o Minor features (command-line interface):
16146 - Make --hash-password imply --hush to prevent unnecessary noise.
16147 Closes ticket 15542. Patch from "cypherpunks".
16148 - Print a warning whenever we find a relative file path being used
16149 as torrc option. Resolves issue 14018.
16151 o Minor features (compilation):
16152 - Give a warning as early as possible when trying to build with an
16153 unsupported OpenSSL version. Closes ticket 16901.
16154 - Use C99 variadic macros when the compiler is not GCC. This avoids
16155 failing compilations on MSVC, and fixes a log-file-based race
16156 condition in our old workarounds. Original patch from Gisle Vanem.
16158 o Minor features (control protocol):
16159 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
16160 the control protocol. Resolves ticket 15358.
16162 o Minor features (controller):
16163 - Add DirAuthority lines for default directory authorities to the
16164 output of the "GETINFO config/defaults" command if not already
16165 present. Implements ticket 14840.
16166 - Controllers can now use "GETINFO hs/client/desc/id/..." to
16167 retrieve items from the client's hidden service descriptor cache.
16168 Closes ticket 14845.
16169 - Implement a new controller command "GETINFO status/fresh-relay-
16170 descs" to fetch a descriptor/extrainfo pair that was generated on
16171 demand just for the controller's use. Implements ticket 14784.
16173 o Minor features (directory authorities):
16174 - Directory authorities no longer vote against the "Fast", "Stable",
16175 and "HSDir" flags just because they were going to vote against
16176 "Running": if the consensus turns out to be that the router was
16177 running, then the authority's vote should count. Patch from Peter
16178 Retzlaff; closes issue 8712.
16180 o Minor features (directory authorities, security, also in 0.2.6.9):
16181 - The HSDir flag given by authorities now requires the Stable flag.
16182 For the current network, this results in going from 2887 to 2806
16183 HSDirs. Also, it makes it harder for an attacker to launch a sybil
16184 attack by raising the effort for a relay to become Stable to
16185 require at the very least 7 days, while maintaining the 96 hours
16186 uptime requirement for HSDir. Implements ticket 8243.
16188 o Minor features (DoS-resistance):
16189 - Make it harder for attackers to overload hidden services with
16190 introductions, by blocking multiple introduction requests on the
16191 same circuit. Resolves ticket 15515.
16193 o Minor features (geoip):
16194 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
16197 o Minor features (hidden services):
16198 - Add the new options "HiddenServiceMaxStreams" and
16199 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
16200 limit the maximum number of simultaneous streams per circuit, and
16201 optionally tear down the circuit when the limit is exceeded. Part
16203 - Client now uses an introduction point failure cache to know when
16204 to fetch or keep a descriptor in their cache. Previously, failures
16205 were recorded implicitly, but not explicitly remembered. Closes
16207 - Relays need to have the Fast flag to get the HSDir flag. As this
16208 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
16209 drop. This change should make some attacks against the hidden
16210 service directory system harder. Fixes ticket 15963.
16211 - Turn on hidden service statistics collection by setting the torrc
16212 option HiddenServiceStatistics to "1" by default. (This keeps
16213 track only of the fraction of traffic used by hidden services, and
16214 the total number of hidden services in existence.) Closes
16216 - To avoid leaking HS popularity, don't cycle the introduction point
16217 when we've handled a fixed number of INTRODUCE2 cells but instead
16218 cycle it when a random number of introductions is reached, thus
16219 making it more difficult for an attacker to find out the amount of
16220 clients that have used the introduction point for a specific HS.
16221 Closes ticket 15745.
16223 o Minor features (logging):
16224 - Include the Tor version in all LD_BUG log messages, since people
16225 tend to cut and paste those into the bugtracker. Implements
16228 o Minor features (pluggable transports):
16229 - When launching managed pluggable transports on Linux systems,
16230 attempt to have the kernel deliver a SIGTERM on tor exit if the
16231 pluggable transport process is still running. Resolves
16233 - When launching managed pluggable transports, setup a valid open
16234 stdin in the child process that can be used to detect if tor has
16235 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
16236 can be used by implementations to detect this new behavior.
16237 Resolves ticket 15435.
16239 o Minor bugfixes (torrc exit policies):
16240 - In each instance above, usage advice is provided to avoid the
16241 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
16242 16069; bugfix on 0.2.4.7-alpha.
16243 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
16244 produce IPv6 wildcard addresses. Previously they would produce
16245 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
16246 of bug 16069; bugfix on 0.2.4.7-alpha.
16247 - When parsing torrc ExitPolicies, we now issue an info-level
16248 message when expanding an "accept/reject *" line to include both
16249 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
16250 - When parsing torrc ExitPolicies, we now warn for a number of cases
16251 where the user's intent is likely to differ from Tor's actual
16252 behavior. These include: using an IPv4 address with an accept6 or
16253 reject6 line; using "private" on an accept6 or reject6 line; and
16254 including any ExitPolicy lines after accept *:* or reject *:*.
16255 Related to ticket 16069.
16257 o Minor bugfixes (command-line interface):
16258 - When "--quiet" is provided along with "--validate-config", do not
16259 write anything to stdout on success. Fixes bug 14994; bugfix
16261 - When complaining about bad arguments to "--dump-config", use
16262 stderr, not stdout.
16263 - Print usage information for --dump-config when it is used without
16264 an argument. Also, fix the error message to use different wording
16265 and add newline at the end. Fixes bug 15541; bugfix
16268 o Minor bugfixes (compilation):
16269 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
16270 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
16271 - Repair compilation with the most recent (unreleased, alpha)
16272 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
16274 o Minor bugfixes (compilation, also in 0.2.6.9):
16275 - Build with --enable-systemd correctly when libsystemd is
16276 installed, but systemd is not. Fixes bug 16164; bugfix on
16277 0.2.6.3-alpha. Patch from Peter Palfrader.
16279 o Minor bugfixes (configuration, unit tests):
16280 - Only add the default fallback directories when the DirAuthorities,
16281 AlternateDirAuthority, and FallbackDir directory config options
16282 are set to their defaults. The default fallback directory list is
16283 currently empty, this fix will only change tor's behavior when it
16284 has default fallback directories. Includes unit tests for
16285 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
16286 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
16288 o Minor bugfixes (controller):
16289 - Add the descriptor ID in each HS_DESC control event. It was
16290 missing, but specified in control-spec.txt. Fixes bug 15881;
16291 bugfix on 0.2.5.2-alpha.
16293 o Minor bugfixes (correctness):
16294 - For correctness, avoid modifying a constant string in
16295 handle_control_postdescriptor. Fixes bug 15546; bugfix
16297 - Remove side-effects from tor_assert() calls. This was harmless,
16298 because we never disable assertions, but it is bad style and
16299 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
16301 - When calling channel_free_list(), avoid calling smartlist_remove()
16302 while inside a FOREACH loop. This partially reverts commit
16303 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
16304 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
16306 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
16307 - Check for failures from crypto_early_init, and refuse to continue.
16308 A previous typo meant that we could keep going with an
16309 uninitialized crypto library, and would have OpenSSL initialize
16310 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
16311 when implementing ticket 4900. Patch by "teor".
16313 o Minor bugfixes (hidden service):
16314 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
16315 a client authorized hidden service. Fixes bug 15823; bugfix
16317 - Remove an extraneous newline character from the end of hidden
16318 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
16320 o Minor bugfixes (Linux seccomp2 sandbox):
16321 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
16322 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
16323 - Allow bridge authorities to run correctly under the seccomp2
16324 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
16325 - Add the "hidserv-stats" filename to our sandbox filter for the
16326 HiddenServiceStatistics option to work properly. Fixes bug 17354;
16327 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
16329 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
16330 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
16331 these when eventfd2() support is missing. Fixes bug 16363; bugfix
16332 on 0.2.6.3-alpha. Patch from "teor".
16334 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
16335 - Allow systemd connections to work with the Linux seccomp2 sandbox
16336 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
16338 - Fix sandboxing to work when running as a relay, by allowing the
16339 renaming of secret_id_key, and allowing the eventfd2 and futex
16340 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
16343 o Minor bugfixes (logging):
16344 - When building Tor under Clang, do not include an extra set of
16345 parentheses in log messages that include function names. Fixes bug
16346 15269; bugfix on every released version of Tor when compiled with
16347 recent enough Clang.
16349 o Minor bugfixes (network):
16350 - When attempting to use fallback technique for network interface
16351 lookup, disregard loopback and multicast addresses since they are
16352 unsuitable for public communications.
16354 o Minor bugfixes (open file limit):
16355 - Fix set_max_file_descriptors() to set by default the max open file
16356 limit to the current limit when setrlimit() fails. Fixes bug
16357 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
16359 o Minor bugfixes (portability):
16360 - Check correctly for Windows socket errors in the workqueue
16361 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
16362 - Try harder to normalize the exit status of the Tor process to the
16363 standard-provided range. Fixes bug 16975; bugfix on every version
16365 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
16366 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
16368 o Minor bugfixes (relay):
16369 - Ensure that worker threads actually exit when a fatal error or
16370 shutdown is indicated. This fix doesn't currently affect the
16371 behavior of Tor, because Tor workers never indicates fatal error
16372 or shutdown except in the unit tests. Fixes bug 16868; bugfix
16374 - Fix a rarely-encountered memory leak when failing to initialize
16375 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
16376 from "cypherpunks".
16377 - Unblock threads before releasing the work queue mutex to ensure
16378 predictable scheduling behavior. Fixes bug 16644; bugfix
16381 o Minor bugfixes (security, exit policies):
16382 - ExitPolicyRejectPrivate now also rejects the relay's published
16383 IPv6 address (if any), and any publicly routable IPv4 or IPv6
16384 addresses on any local interfaces. ticket 17027. Patch by "teor".
16385 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
16387 o Minor bugfixes (statistics):
16388 - Disregard the ConnDirectionStatistics torrc options when Tor is
16389 not a relay since in that mode of operation no sensible data is
16390 being collected and because Tor might run into measurement hiccups
16391 when running as a client for some time, then becoming a relay.
16392 Fixes bug 15604; bugfix on 0.2.2.35.
16394 o Minor bugfixes (systemd):
16395 - Tor's systemd unit file no longer contains extraneous spaces.
16396 These spaces would sometimes confuse tools like deb-systemd-
16397 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
16399 o Minor bugfixes (test networks):
16400 - When self-testing reachability, use ExtendAllowPrivateAddresses to
16401 determine if local/private addresses imply reachability. The
16402 previous fix used TestingTorNetwork, which implies
16403 ExtendAllowPrivateAddresses, but this excluded rare configurations
16404 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
16405 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
16406 issue discovered by CJ Ess.
16408 o Minor bugfixes (tests, also in 0.2.6.9):
16409 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
16410 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
16412 o Code simplification and refactoring:
16413 - Change the function that's called when we need to retry all
16414 downloads so that it only reschedules the downloads to happen
16415 immediately, rather than launching them all at once itself. This
16416 further simplifies Tor's callgraph.
16417 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
16418 to ensure they remain consistent and visible everywhere.
16419 - Move some format-parsing functions out of crypto.c and
16420 crypto_curve25519.c into crypto_format.c and/or util_format.c.
16421 - Move the client-only parts of init_keys() into a separate
16422 function. Closes ticket 16763.
16423 - Move the hacky fallback code out of get_interface_address6() into
16424 separate function and get it covered with unit-tests. Resolves
16426 - Refactor hidden service client-side cache lookup to intelligently
16427 report its various failure cases, and disentangle failure cases
16428 involving a lack of introduction points. Closes ticket 14391.
16429 - Remove some vestigial workarounds for the MSVC6 compiler. We
16430 haven't supported that in ages.
16431 - Remove the unused "nulterminate" argument from buf_pullup().
16432 - Simplify the microdesc_free() implementation so that it no longer
16433 appears (to code analysis tools) to potentially invoke a huge
16434 suite of other microdesc functions.
16435 - Simply the control graph further by deferring the inner body of
16436 directory_all_unreachable() into a callback. Closes ticket 16762.
16437 - The link authentication code has been refactored for better
16438 testability and reliability. It now uses code generated with the
16439 "trunnel" binary encoding generator, to reduce the risk of bugs
16440 due to programmer error. Done as part of ticket 12498.
16441 - Treat the loss of an owning controller as equivalent to a SIGTERM
16442 signal. This removes a tiny amount of duplicated code, and
16443 simplifies our callgraph. Closes ticket 16788.
16444 - Use our own Base64 encoder instead of OpenSSL's, to allow more
16445 control over the output. Part of ticket 15652.
16446 - When generating an event to send to the controller, we no longer
16447 put the event over the network immediately. Instead, we queue
16448 these events, and use a Libevent callback to deliver them. This
16449 change simplifies Tor's callgraph by reducing the number of
16450 functions from which all other Tor functions are reachable. Closes
16452 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
16453 that try to scan or compile every file on Unix won't decide that
16457 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
16458 - Improve the descriptions of statistics-related torrc options in
16459 the manpage to describe rationale and possible uses cases. Fixes
16461 - Improve the layout and formatting of ./configure --help messages.
16462 Closes ticket 15024. Patch from "cypherpunks".
16463 - Include a specific and (hopefully) accurate documentation of the
16464 torrc file's meta-format in doc/torrc_format.txt. This is mainly
16465 of interest to people writing programs to parse or generate torrc
16466 files. This document is not a commitment to long-term
16467 compatibility; some aspects of the current format are a bit
16468 ridiculous. Closes ticket 2325.
16469 - Include the TUNING document in our source tarball. It is referred
16470 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
16472 - Note that HiddenServicePorts can take a unix domain socket. Closes
16474 - Recommend a 40 GB example AccountingMax in torrc.sample rather
16475 than a 4 GB max. Closes ticket 16742.
16476 - Standardize on the term "server descriptor" in the manual page.
16477 Previously, we had used "router descriptor", "server descriptor",
16478 and "relay descriptor" interchangeably. Part of ticket 14987.
16479 - Advise users on how to configure separate IPv4 and IPv6 exit
16480 policies in the manpage and sample torrcs. Related to ticket 16069.
16481 - Fix an error in the manual page and comments for
16482 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
16483 required "ORPort connectivity". While this is true, it is in no
16484 way unique to the HSDir flag. Of all the flags, only HSDirs need a
16485 DirPort configured in order for the authorities to assign that
16486 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
16488 - Fix the usage message of tor-resolve(1) so that it no longer lists
16489 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
16492 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
16493 and always use the internal Base64 decoder. The internal decoder
16494 has been part of tor since 0.2.0.10-alpha, and no one should
16495 be using the OpenSSL one. Part of ticket 15652.
16496 - Remove the 'tor_strclear()' function; use memwipe() instead.
16497 Closes ticket 14922.
16498 - Remove the code that would try to aggressively flush controller
16499 connections while writing to them. This code was introduced in
16500 0.1.2.7-alpha, in order to keep output buffers from exceeding
16501 their limits. But there is no longer a maximum output buffer size,
16502 and flushing data in this way caused some undesirable recursions
16503 in our call graph. Closes ticket 16480.
16504 - The internal pure-C tor-fw-helper tool is now removed from the Tor
16505 distribution, in favor of the pure-Go clone available from
16506 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
16507 used by the C tor-fw-helper are not, in our opinion, very
16508 confidence- inspiring in their secure-programming techniques.
16509 Closes ticket 13338.
16511 o Removed features:
16512 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
16513 fingerprinting we now recommend pluggable transports; for forward-
16514 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
16515 - Remove the HidServDirectoryV2 option. Now all relays offer to
16516 store hidden service descriptors. Related to 16543.
16517 - Remove the VoteOnHidServDirectoriesV2 option, since all
16518 authorities have long set it to 1. Closes ticket 16543.
16519 - Remove the undocumented "--digests" command-line option. It
16520 complicated our build process, caused subtle build issues on
16521 multiple platforms, and is now redundant since we started
16522 including git version identifiers. Closes ticket 14742.
16523 - Tor no longer contains checks for ancient directory cache versions
16524 that didn't know about microdescriptors.
16525 - Tor no longer contains workarounds for stat files generated by
16526 super-old versions of Tor that didn't choose guards sensibly.
16529 - The test-network.sh script now supports performance testing.
16530 Requires corresponding chutney performance testing changes. Patch
16531 by "teor". Closes ticket 14175.
16532 - Add a new set of callgraph analysis scripts that use clang to
16533 produce a list of which Tor functions are reachable from which
16534 other Tor functions. We're planning to use these to help simplify
16535 our code structure by identifying illogical dependencies.
16536 - Add new 'test-full' and 'test-full-online' targets to run all
16537 tests, including integration tests with stem and chutney.
16538 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
16539 by-side in the same parent directory. Closes ticket 16903. Patch
16541 - Document use of coverity, clang static analyzer, and clang dynamic
16542 undefined behavior and address sanitizers in doc/HACKING. Include
16543 detailed usage instructions in the blacklist. Patch by "teor".
16544 Closes ticket 15817.
16545 - Make "bridges+hs" the default test network. This tests almost all
16546 tor functionality during make test-network, while allowing tests
16547 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
16548 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
16549 (chutney). Patches by "teor".
16550 - Make the test-workqueue test work on Windows by initializing the
16551 network before we begin.
16552 - New make target (make test-network-all) to run multiple applicable
16553 chutney test cases. Patch from Teor; closes 16953.
16554 - Now that OpenSSL has its own scrypt implementation, add an unit
16555 test that checks for interoperability between libscrypt_scrypt()
16556 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
16557 and rely on EVP_PBE_scrypt() whenever possible. Resolves
16559 - The link authentication protocol code now has extensive tests.
16560 - The relay descriptor signature testing code now has
16562 - The test_workqueue program now runs faster, and is enabled by
16563 default as a part of "make check".
16564 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
16565 functions in dns.c. Implements a portion of ticket 16831.
16566 - Use environment variables rather than autoconf substitutions to
16567 send variables from the build system to the test scripts. This
16568 change should be easier to maintain, and cause 'make distcheck' to
16569 work better than before. Fixes bug 17148.
16570 - When building Tor with testing coverage enabled, run Chutney tests
16571 (if any) using the 'tor-cov' coverage binary.
16572 - When running test-network or test-stem, check for the absence of
16573 stem/chutney before doing any build operations.
16574 - Add a test to verify that the compiler does not eliminate our
16575 memwipe() implementation. Closes ticket 15377.
16576 - Add make rule `check-changes` to verify the format of changes
16577 files. Closes ticket 15180.
16578 - Add unit tests for control_event_is_interesting(). Add a compile-
16579 time check that the number of events doesn't exceed the capacity
16580 of control_event_t.event_mask. Closes ticket 15431, checks for
16581 bugs similar to 13085. Patch by "teor".
16582 - Command-line argument tests moved to Stem. Resolves ticket 14806.
16583 - Integrate the ntor, backtrace, and zero-length keys tests into the
16584 automake test suite. Closes ticket 15344.
16585 - Remove assertions during builds to determine Tor's test coverage.
16586 We don't want to trigger these even in assertions, so including
16587 them artificially makes our branch coverage look worse than it is.
16588 This patch provides the new test-stem-full and coverage-html-full
16589 configure options. Implements ticket 15400.
16590 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
16591 explicitly manage consensus flags in testing networks. Patch by
16592 "robgjansen", modified by "teor". Implements part of ticket 14882.
16593 - Check for matching value in server response in ntor_ref.py. Fixes
16594 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
16596 - Set the severity correctly when testing
16597 get_interface_addresses_ifaddrs() and
16598 get_interface_addresses_win32(), so that the tests fail gracefully
16599 instead of triggering an assertion. Fixes bug 15759; bugfix on
16600 0.2.6.3-alpha. Reported by Nicolas Derive.
16602 Changes in version 0.2.6.10 - 2015-07-12
16603 Tor version 0.2.6.10 fixes some significant stability and hidden
16604 service client bugs, bulletproofs the cryptography init process, and
16605 fixes a bug when using the sandbox code with some older versions of
16606 Linux. Everyone running an older version, especially an older version
16607 of 0.2.6, should upgrade.
16609 o Major bugfixes (hidden service clients, stability):
16610 - Stop refusing to store updated hidden service descriptors on a
16611 client. This reverts commit 9407040c59218 (which indeed fixed bug
16612 14219, but introduced a major hidden service reachability
16613 regression detailed in bug 16381). This is a temporary fix since
16614 we can live with the minor issue in bug 14219 (it just results in
16615 some load on the network) but the regression of 16381 is too much
16616 of a setback. First-round fix for bug 16381; bugfix
16619 o Major bugfixes (stability):
16620 - Stop crashing with an assertion failure when parsing certain kinds
16621 of malformed or truncated microdescriptors. Fixes bug 16400;
16622 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
16623 by "cypherpunks_backup".
16624 - Stop random client-side assertion failures that could occur when
16625 connecting to a busy hidden service, or connecting to a hidden
16626 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
16629 o Minor features (geoip):
16630 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
16631 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
16633 o Minor bugfixes (crypto error-handling):
16634 - Check for failures from crypto_early_init, and refuse to continue.
16635 A previous typo meant that we could keep going with an
16636 uninitialized crypto library, and would have OpenSSL initialize
16637 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
16638 when implementing ticket 4900. Patch by "teor".
16640 o Minor bugfixes (Linux seccomp2 sandbox):
16641 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
16642 these when eventfd2() support is missing. Fixes bug 16363; bugfix
16643 on 0.2.6.3-alpha. Patch from "teor".
16646 Changes in version 0.2.6.9 - 2015-06-11
16647 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
16648 requirements for receiving an HSDir flag, and addresses some other small
16649 bugs in the systemd and sandbox code. Clients using circuit isolation
16650 should upgrade; all directory authorities should upgrade.
16652 o Major bugfixes (client-side privacy):
16653 - Properly separate out each SOCKSPort when applying stream
16654 isolation. The error occurred because each port's session group was
16655 being overwritten by a default value when the listener connection
16656 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
16659 o Minor feature (directory authorities, security):
16660 - The HSDir flag given by authorities now requires the Stable flag.
16661 For the current network, this results in going from 2887 to 2806
16662 HSDirs. Also, it makes it harder for an attacker to launch a sybil
16663 attack by raising the effort for a relay to become Stable which
16664 takes at the very least 7 days to do so and by keeping the 96
16665 hours uptime requirement for HSDir. Implements ticket 8243.
16667 o Minor bugfixes (compilation):
16668 - Build with --enable-systemd correctly when libsystemd is
16669 installed, but systemd is not. Fixes bug 16164; bugfix on
16670 0.2.6.3-alpha. Patch from Peter Palfrader.
16672 o Minor bugfixes (Linux seccomp2 sandbox):
16673 - Fix sandboxing to work when running as a relaymby renaming of
16674 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
16675 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
16676 - Allow systemd connections to work with the Linux seccomp2 sandbox
16677 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
16680 o Minor bugfixes (tests):
16681 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
16682 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
16685 Changes in version 0.2.6.8 - 2015-05-21
16686 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
16687 fixes an authority-side bug in assigning the HSDir flag. All directory
16688 authorities should upgrade.
16690 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
16691 - Revert commit that made directory authorities assign the HSDir
16692 flag to relays without a DirPort; this was bad because such relays
16693 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
16696 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
16697 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
16698 a client authorized hidden service. Fixes bug 15823; bugfix
16701 o Minor features (geoip):
16702 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
16703 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
16707 Changes in version 0.2.6.7 - 2015-04-06
16708 Tor 0.2.6.7 fixes two security issues that could be used by an
16709 attacker to crash hidden services, or crash clients visiting hidden
16710 services. Hidden services should upgrade as soon as possible; clients
16711 should upgrade whenever packages become available.
16713 This release also contains two simple improvements to make hidden
16714 services a bit less vulnerable to denial-of-service attacks.
16716 o Major bugfixes (security, hidden service):
16717 - Fix an issue that would allow a malicious client to trigger an
16718 assertion failure and halt a hidden service. Fixes bug 15600;
16719 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
16720 - Fix a bug that could cause a client to crash with an assertion
16721 failure when parsing a malformed hidden service descriptor. Fixes
16722 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
16724 o Minor features (DoS-resistance, hidden service):
16725 - Introduction points no longer allow multiple INTRODUCE1 cells to
16726 arrive on the same circuit. This should make it more expensive for
16727 attackers to overwhelm hidden services with introductions.
16728 Resolves ticket 15515.
16729 - Decrease the amount of reattempts that a hidden service performs
16730 when its rendezvous circuits fail. This reduces the computational
16731 cost for running a hidden service under heavy load. Resolves
16735 Changes in version 0.2.5.12 - 2015-04-06
16736 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
16737 could be used by an attacker to crash hidden services, or crash clients
16738 visiting hidden services. Hidden services should upgrade as soon as
16739 possible; clients should upgrade whenever packages become available.
16741 This release also backports a simple improvement to make hidden
16742 services a bit less vulnerable to denial-of-service attacks.
16744 o Major bugfixes (security, hidden service):
16745 - Fix an issue that would allow a malicious client to trigger an
16746 assertion failure and halt a hidden service. Fixes bug 15600;
16747 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
16748 - Fix a bug that could cause a client to crash with an assertion
16749 failure when parsing a malformed hidden service descriptor. Fixes
16750 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
16752 o Minor features (DoS-resistance, hidden service):
16753 - Introduction points no longer allow multiple INTRODUCE1 cells to
16754 arrive on the same circuit. This should make it more expensive for
16755 attackers to overwhelm hidden services with introductions.
16756 Resolves ticket 15515.
16759 Changes in version 0.2.4.27 - 2015-04-06
16760 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
16761 could be used by an attacker to crash hidden services, or crash clients
16762 visiting hidden services. Hidden services should upgrade as soon as
16763 possible; clients should upgrade whenever packages become available.
16765 This release also backports a simple improvement to make hidden
16766 services a bit less vulnerable to denial-of-service attacks.
16768 o Major bugfixes (security, hidden service):
16769 - Fix an issue that would allow a malicious client to trigger an
16770 assertion failure and halt a hidden service. Fixes bug 15600;
16771 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
16772 - Fix a bug that could cause a client to crash with an assertion
16773 failure when parsing a malformed hidden service descriptor. Fixes
16774 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
16776 o Minor features (DoS-resistance, hidden service):
16777 - Introduction points no longer allow multiple INTRODUCE1 cells to
16778 arrive on the same circuit. This should make it more expensive for
16779 attackers to overwhelm hidden services with introductions.
16780 Resolves ticket 15515.
16783 Changes in version 0.2.6.6 - 2015-03-24
16784 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
16786 It adds numerous safety, security, correctness, and performance
16787 improvements. Client programs can be configured to use more kinds of
16788 sockets, AutomapHosts works better, the multithreading backend is
16789 improved, cell transmission is refactored, test coverage is much
16790 higher, more denial-of-service attacks are handled, guard selection is
16791 improved to handle long-term guards better, pluggable transports
16792 should work a bit better, and some annoying hidden service performance
16793 bugs should be addressed.
16795 o New compiler and system requirements:
16796 - Tor 0.2.6.x requires that your compiler support more of the C99
16797 language standard than before. The 'configure' script now detects
16798 whether your compiler supports C99 mid-block declarations and
16799 designated initializers. If it does not, Tor will not compile.
16801 We may revisit this requirement if it turns out that a significant
16802 number of people need to build Tor with compilers that don't
16803 bother implementing a 15-year-old standard. Closes ticket 13233.
16804 - Tor no longer supports systems without threading support. When we
16805 began working on Tor, there were several systems that didn't have
16806 threads, or where the thread support wasn't able to run the
16807 threads of a single process on multiple CPUs. That no longer
16808 holds: every system where Tor needs to run well now has threading
16809 support. Resolves ticket 12439.
16811 o Deprecated versions and removed support:
16812 - Tor relays older than 0.2.4.18-rc are no longer allowed to
16813 advertise themselves on the network. Closes ticket 13555.
16814 - Tor clients no longer support connecting to hidden services
16815 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
16816 option has been removed. (There shouldn't be any hidden services
16817 running these versions on the network.) Closes ticket 7803.
16819 o Directory authority changes:
16820 - The directory authority Faravahar has a new IP address. This
16821 closes ticket 14487.
16822 - Remove turtles as a directory authority.
16823 - Add longclaw as a new (v3) directory authority. This implements
16824 ticket 13296. This keeps the directory authority count at 9.
16826 o Major features (bridges):
16827 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
16828 transports if they are configured via the "TOR_PT_PROXY"
16829 environment variable. Implements proposal 232. Resolves
16832 o Major features (changed defaults):
16833 - Prevent relay operators from unintentionally running exits: When a
16834 relay is configured as an exit node, we now warn the user unless
16835 the "ExitRelay" option is set to 1. We warn even more loudly if
16836 the relay is configured with the default exit policy, since this
16837 can indicate accidental misconfiguration. Setting "ExitRelay 0"
16838 stops Tor from running as an exit relay. Closes ticket 10067.
16840 o Major features (client performance, hidden services):
16841 - Allow clients to use optimistic data when connecting to a hidden
16842 service, which should remove a round-trip from hidden service
16843 initialization. See proposal 181 for details. Implements
16846 o Major features (directory system):
16847 - Upon receiving an unparseable directory object, if its digest
16848 matches what we expected, then don't try to download it again.
16849 Previously, when we got a descriptor we didn't like, we would keep
16850 trying to download it over and over. Closes ticket 11243.
16851 - When downloading server- or microdescriptors from a directory
16852 server, we no longer launch multiple simultaneous requests to the
16853 same server. This reduces load on the directory servers,
16854 especially when directory guards are in use. Closes ticket 9969.
16855 - When downloading server- or microdescriptors over a tunneled
16856 connection, do not limit the length of our requests to what the
16857 Squid proxy is willing to handle. Part of ticket 9969.
16858 - Authorities can now vote on the correct digests and latest
16859 versions for different software packages. This allows packages
16860 that include Tor to use the Tor authority system as a way to get
16861 notified of updates and their correct digests. Implements proposal
16862 227. Closes ticket 10395.
16864 o Major features (guards):
16865 - Introduce the Guardfraction feature to improves load balancing on
16866 guard nodes. Specifically, it aims to reduce the traffic gap that
16867 guard nodes experience when they first get the Guard flag. This is
16868 a required step if we want to increase the guard lifetime to 9
16869 months or greater. Closes ticket 9321.
16871 o Major features (hidden services):
16872 - Make HS port scanning more difficult by immediately closing the
16873 circuit when a user attempts to connect to a nonexistent port.
16874 Closes ticket 13667.
16875 - Add a HiddenServiceStatistics option that allows Tor relays to
16876 gather and publish statistics about the overall size and volume of
16877 hidden service usage. Specifically, when this option is turned on,
16878 an HSDir will publish an approximate number of hidden services
16879 that have published descriptors to it the past 24 hours. Also, if
16880 a relay has acted as a hidden service rendezvous point, it will
16881 publish the approximate amount of rendezvous cells it has relayed
16882 the past 24 hours. The statistics themselves are obfuscated so
16883 that the exact values cannot be derived. For more details see
16884 proposal 238, "Better hidden service stats from Tor relays". This
16885 feature is currently disabled by default. Implements feature 13192.
16887 o Major features (performance):
16888 - Make the CPU worker implementation more efficient by avoiding the
16889 kernel and lengthening pipelines. The original implementation used
16890 sockets to transfer data from the main thread to the workers, and
16891 didn't allow any thread to be assigned more than a single piece of
16892 work at once. The new implementation avoids communications
16893 overhead by making requests in shared memory, avoiding kernel IO
16894 where possible, and keeping more requests in flight at once.
16895 Implements ticket 9682.
16897 o Major features (relay):
16898 - Raise the minimum acceptable configured bandwidth rate for bridges
16899 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
16900 20 KiB/sec.) Closes ticket 13822.
16901 - Complete revision of the code that relays use to decide which cell
16902 to send next. Formerly, we selected the best circuit to write on
16903 each channel, but we didn't select among channels in any
16904 sophisticated way. Now, we choose the best circuits globally from
16905 among those whose channels are ready to deliver traffic.
16907 This patch implements a new inter-cmux comparison API, a global
16908 high/low watermark mechanism and a global scheduler loop for
16909 transmission prioritization across all channels as well as among
16910 circuits on one channel. This schedule is currently tuned to
16911 (tolerantly) avoid making changes in network performance, but it
16912 should form the basis for major circuit performance increases in
16913 the future. Code by Andrea; tuning by Rob Jansen; implements
16916 o Major features (sample torrc):
16917 - Add a new, infrequently-changed "torrc.minimal". This file is
16918 similar to torrc.sample, but it will change as infrequently as
16919 possible, for the benefit of users whose systems prompt them for
16920 intervention whenever a default configuration file is changed.
16921 Making this change allows us to update torrc.sample to be a more
16922 generally useful "sample torrc".
16924 o Major features (security, unix domain sockets):
16925 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
16926 applications can reach Tor without having to create AF_INET or
16927 AF_INET6 sockets, meaning they can completely disable their
16928 ability to make non-Tor network connections. To create a socket of
16929 this type, use "SocksPort unix:/path/to/socket". Implements
16931 - Support mapping hidden service virtual ports to AF_UNIX sockets.
16932 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
16933 Implements ticket 11485.
16935 o Major bugfixes (client, automap):
16936 - Repair automapping with IPv6 addresses. This automapping should
16937 have worked previously, but one piece of debugging code that we
16938 inserted to detect a regression actually caused the regression to
16939 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
16940 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
16943 o Major bugfixes (crash, OSX, security):
16944 - Fix a remote denial-of-service opportunity caused by a bug in
16945 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
16948 o Major bugfixes (directory authorities):
16949 - Do not assign the HSDir flag to relays if they are not Valid, or
16950 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
16952 o Major bugfixes (directory bandwidth performance):
16953 - Don't flush the zlib buffer aggressively when compressing
16954 directory information for clients. This should save about 7% of
16955 the bandwidth currently used for compressed descriptors and
16956 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
16958 o Major bugfixes (exit node stability):
16959 - Fix an assertion failure that could occur under high DNS load.
16960 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
16961 diagnosed and fixed by "cypherpunks".
16963 o Major bugfixes (FreeBSD IPFW transparent proxy):
16964 - Fix address detection with FreeBSD transparent proxies, when
16965 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
16968 o Major bugfixes (hidden services):
16969 - When closing an introduction circuit that was opened in parallel
16970 with others, don't mark the introduction point as unreachable.
16971 Previously, the first successful connection to an introduction
16972 point would make the other introduction points get marked as
16973 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
16975 o Major bugfixes (Linux seccomp2 sandbox):
16976 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
16977 crash during attempts to call wait4. Fixes bug 15088; bugfix on
16978 0.2.5.1-alpha. Patch from "sanic".
16980 o Major bugfixes (mixed relay-client operation):
16981 - When running as a relay and client at the same time (not
16982 recommended), if we decide not to use a new guard because we want
16983 to retry older guards, only close the locally-originating circuits
16984 passing through that guard. Previously we would close all the
16985 circuits through that guard. Fixes bug 9819; bugfix on
16986 0.2.1.1-alpha. Reported by "skruffy".
16988 o Major bugfixes (pluggable transports):
16989 - Initialize the extended OR Port authentication cookie before
16990 launching pluggable transports. This prevents a race condition
16991 that occurred when server-side pluggable transports would cache the
16992 authentication cookie before it has been (re)generated. Fixes bug
16993 15240; bugfix on 0.2.5.1-alpha.
16995 o Major bugfixes (relay, stability, possible security):
16996 - Fix a bug that could lead to a relay crashing with an assertion
16997 failure if a buffer of exactly the wrong layout is passed to
16998 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
16999 0.2.0.10-alpha. Patch from "cypherpunks".
17000 - Do not assert if the 'data' pointer on a buffer is advanced to the
17001 very end of the buffer; log a BUG message instead. Only assert if
17002 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
17004 o Minor features (build):
17005 - New --disable-system-torrc compile-time option to prevent Tor from
17006 looking for the system-wide torrc or torrc-defaults files.
17007 Resolves ticket 13037.
17009 o Minor features (client):
17010 - Clients are now willing to send optimistic data (before they
17011 receive a 'connected' cell) to relays of any version. (Relays
17012 without support for optimistic data are no longer supported on the
17013 Tor network.) Resolves ticket 13153.
17015 o Minor features (client):
17016 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
17017 is enabled, reject requests with IP addresses as hostnames.
17018 Resolves ticket 13315.
17020 o Minor features (controller):
17021 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
17022 write an unscheduled heartbeat message to the log. Implements
17024 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
17025 events so controllers can observe circuit isolation inputs. Closes
17027 - ControlPort now supports the unix:/path/to/socket syntax as an
17028 alternative to the ControlSocket option, for consistency with
17029 SocksPort and HiddenServicePort. Closes ticket 14451.
17030 - New "GETINFO bw-event-cache" to get information about recent
17031 bandwidth events. Closes ticket 14128. Useful for controllers to
17032 get recent bandwidth history after the fix for ticket 13988.
17033 - Messages about problems in the bootstrap process now include
17034 information about the server we were trying to connect to when we
17035 noticed the problem. Closes ticket 15006.
17037 o Minor features (Denial of service resistance):
17038 - Count the total number of bytes used storing hidden service
17039 descriptors against the value of MaxMemInQueues. If we're low on
17040 memory, and more than 20% of our memory is used holding hidden
17041 service descriptors, free them until no more than 10% of our
17042 memory holds hidden service descriptors. Free the least recently
17043 fetched descriptors first. Resolves ticket 13806.
17044 - When we have recently been under memory pressure (over 3/4 of
17045 MaxMemInQueues is allocated), then allocate smaller zlib objects
17046 for small requests. Closes ticket 11791.
17048 o Minor features (directory authorities):
17049 - Don't list relays with a bandwidth estimate of 0 in the consensus.
17050 Implements a feature proposed during discussion of bug 13000.
17051 - In tor-gencert, report an error if the user provides the same
17052 argument more than once.
17053 - If a directory authority can't find a best consensus method in the
17054 votes that it holds, it now falls back to its favorite consensus
17055 method. Previously, it fell back to method 1. Neither of these is
17056 likely to get enough signatures, but "fall back to favorite"
17057 doesn't require us to maintain support an obsolete consensus
17058 method. Implements part of proposal 215.
17060 o Minor features (geoip):
17061 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
17062 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
17065 o Minor features (guard nodes):
17066 - Reduce the time delay before saving guard status to disk from 10
17067 minutes to 30 seconds (or from one hour to 10 minutes if
17068 AvoidDiskWrites is set). Closes ticket 12485.
17070 o Minor features (heartbeat):
17071 - On relays, report how many connections we negotiated using each
17072 version of the Tor link protocols. This information will let us
17073 know if removing support for very old versions of the Tor
17074 protocols is harming the network. Closes ticket 15212.
17076 o Minor features (hidden service):
17077 - Make Sybil attacks against hidden services harder by changing the
17078 minimum time required to get the HSDir flag from 25 hours up to 96
17079 hours. Addresses ticket 14149.
17080 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
17081 services to disable the anti-scanning feature introduced in
17082 0.2.6.2-alpha. With this option not set, a connection to an
17083 unlisted port closes the circuit. With this option set, only a
17084 RELAY_DONE cell is sent. Closes ticket 14084.
17085 - When re-enabling the network, don't try to build introduction
17086 circuits until we have successfully built a circuit. This makes
17087 hidden services come up faster when the network is re-enabled.
17088 Patch from "akwizgran". Closes ticket 13447.
17089 - When we fail to retrieve a hidden service descriptor, send the
17090 controller an "HS_DESC FAILED" controller event. Implements
17092 - New HiddenServiceDirGroupReadable option to cause hidden service
17093 directories and hostname files to be created group-readable. Patch
17094 from "anon", David Stainton, and "meejah". Closes ticket 11291.
17096 o Minor features (interface):
17097 - Implement "-f -" command-line option to read torrc configuration
17098 from standard input, if you don't want to store the torrc file in
17099 the file system. Implements feature 13865.
17101 o Minor features (logging):
17102 - Add a count of unique clients to the bridge heartbeat message.
17103 Resolves ticket 6852.
17104 - Suppress "router info incompatible with extra info" message when
17105 reading extrainfo documents from cache. (This message got loud
17106 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
17108 - Elevate hidden service authorized-client message from DEBUG to
17109 INFO. Closes ticket 14015.
17110 - On Unix-like systems, you can now use named pipes as the target of
17111 the Log option, and other options that try to append to files.
17112 Closes ticket 12061. Patch from "carlo von lynX".
17113 - When opening a log file at startup, send it every log message that
17114 we generated between startup and opening it. Previously, log
17115 messages that were generated before opening the log file were only
17116 logged to stdout. Closes ticket 6938.
17117 - Add a TruncateLogFile option to overwrite logs instead of
17118 appending to them. Closes ticket 5583.
17119 - Quiet some log messages in the heartbeat and at startup. Closes
17122 o Minor features (portability, Solaris):
17123 - Threads are no longer disabled by default on Solaris; we believe
17124 that the versions of Solaris with broken threading support are all
17125 obsolete by now. Resolves ticket 9495.
17127 o Minor features (relay):
17128 - Re-check our address after we detect a changed IP address from
17129 getsockname(). This ensures that the controller command "GETINFO
17130 address" will report the correct value. Resolves ticket 11582.
17132 - A new AccountingRule option lets Relays set whether they'd like
17133 AccountingMax to be applied separately to inbound and outbound
17134 traffic, or applied to the sum of inbound and outbound traffic.
17135 Resolves ticket 961. Patch by "chobe".
17136 - When identity keypair is generated for first time, log a
17137 congratulatory message that links to the new relay lifecycle
17138 document. Implements feature 10427.
17140 o Minor features (security, memory wiping):
17141 - Ensure we securely wipe keys from memory after
17142 crypto_digest_get_digest and init_curve25519_keypair_from_file
17143 have finished using them. Resolves ticket 13477.
17145 o Minor features (security, out-of-memory handling):
17146 - When handling an out-of-memory condition, allocate less memory for
17147 temporary data structures. Fixes issue 10115.
17148 - When handling an out-of-memory condition, consider more types of
17149 buffers, including those on directory connections, and zlib
17150 buffers. Resolves ticket 11792.
17152 o Minor features (stability):
17153 - Add assertions in our hash-table iteration code to check for
17154 corrupted values that could cause infinite loops. Closes
17157 o Minor features (systemd):
17158 - Various improvements and modernizations in systemd hardening
17159 support. Closes ticket 13805. Patch from Craig Andrews.
17160 - Where supported, when running with systemd, report successful
17161 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
17162 - When running with systemd, support systemd watchdog messages. Part
17163 of ticket 11016. Patch by Michael Scherer.
17165 o Minor features (testing networks):
17166 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
17167 the "Exit" flag regardless of their uptime, bandwidth, or exit
17168 policy. TestingTorNetwork must be set for this option to have any
17169 effect. Previously, authorities would take up to 35 minutes to
17170 give nodes the Exit flag in a test network. Partially implements
17172 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
17173 and the default on a testing network to 2 minutes. Drop the
17174 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
17175 keep the default on a testing network at 30 seconds. This reduces
17176 HS bootstrap time to around 25 seconds. Also, change the default
17177 time in test-network.sh to match. Closes ticket 13401. Patch
17179 - Create TestingDirAuthVoteHSDir to correspond to
17180 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
17181 HSDir flag for the listed relays regardless of uptime or ORPort
17182 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
17183 Partial implementation for ticket 14067. Patch by "teor".
17185 o Minor features (tor2web mode):
17186 - Introduce the config option Tor2webRendezvousPoints, which allows
17187 clients in Tor2webMode to select a specific Rendezvous Point to be
17188 used in HS circuits. This might allow better performance for
17189 Tor2Web nodes. Implements ticket 12844.
17191 o Minor features (transparent proxy):
17192 - Update the transparent proxy option checks to allow for both ipfw
17193 and pf on OS X. Closes ticket 14002.
17194 - Use the correct option when using IPv6 with transparent proxy
17195 support on Linux. Resolves 13808. Patch by Francisco Blas
17198 o Minor features (validation):
17199 - Check all date/time values passed to tor_timegm and
17200 parse_rfc1123_time for validity, taking leap years into account.
17201 Improves HTTP header validation. Implemented with bug 13476.
17202 - In correct_tm(), limit the range of values returned by system
17203 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
17204 This means we don't have to deal with negative or too large dates,
17205 even if a clock is wrong. Otherwise we might fail to read a file
17206 written by us which includes such a date. Fixes bug 13476.
17207 - Stop allowing invalid address patterns like "*/24" that contain
17208 both a wildcard address and a bit prefix length. This affects all
17209 our address-range parsing code. Fixes bug 7484; bugfix
17212 o Minor bugfixes (bridge clients):
17213 - When configured to use a bridge without an identity digest (not
17214 recommended), avoid launching an extra channel to it when
17215 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
17217 o Minor bugfixes (bridges):
17218 - When DisableNetwork is set, do not launch pluggable transport
17219 plugins, and if any are running, terminate them. Fixes bug 13213;
17220 bugfix on 0.2.3.6-alpha.
17222 o Minor bugfixes (C correctness):
17223 - Fix several instances of possible integer overflow/underflow/NaN.
17224 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
17226 - In circuit_build_times_calculate_timeout() in circuitstats.c,
17227 avoid dividing by zero in the pareto calculations. This traps
17228 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
17230 - Fix an integer overflow in format_time_interval(). Fixes bug
17231 13393; bugfix on 0.2.0.10-alpha.
17232 - Set the correct day of year value when the system's localtime(_r)
17233 or gmtime(_r) functions fail to set struct tm. Not externally
17234 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
17235 - Avoid unlikely signed integer overflow in tor_timegm on systems
17236 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
17238 o Minor bugfixes (certificate handling):
17239 - If an authority operator accidentally makes a signing certificate
17240 with a future publication time, do not discard its real signing
17241 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
17242 - Remove any old authority certificates that have been superseded
17243 for at least two days. Previously, we would keep superseded
17244 certificates until they expired, if they were published close in
17245 time to the certificate that superseded them. Fixes bug 11454;
17246 bugfix on 0.2.1.8-alpha.
17248 o Minor bugfixes (client):
17249 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
17250 BadExit flag are not considered worthy candidates. Fixes bug
17251 13066; bugfix on 0.1.2.3-alpha.
17252 - Use the consensus schedule for downloading consensuses, and not
17253 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
17254 - Handle unsupported or malformed SOCKS5 requests properly by
17255 responding with the appropriate error message before closing the
17256 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
17258 o Minor bugfixes (client, automapping):
17259 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
17260 no value follows the option. Fixes bug 14142; bugfix on
17261 0.2.4.7-alpha. Patch by "teor".
17262 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
17263 14195; bugfix on 0.1.0.1-rc.
17264 - Prevent changes to other options from removing the wildcard value
17265 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
17267 - Allow MapAddress and AutomapHostsOnResolve to work together when
17268 an address is mapped into another address type (like .onion) that
17269 must be automapped at resolve time. Fixes bug 7555; bugfix
17272 o Minor bugfixes (client, bridges):
17273 - When we are using bridges and we had a network connectivity
17274 problem, only retry connecting to our currently configured
17275 bridges, not all bridges we know about and remember using. Fixes
17276 bug 14216; bugfix on 0.2.2.17-alpha.
17278 o Minor bugfixes (client, DNS):
17279 - Report the correct cached DNS expiration times on SOCKS port or in
17280 DNS replies. Previously, we would report everything as "never
17281 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
17282 - Avoid a small memory leak when we find a cached answer for a
17283 reverse DNS lookup in a client-side DNS cache. (Remember, client-
17284 side DNS caching is off by default, and is not recommended.) Fixes
17285 bug 14259; bugfix on 0.2.0.1-alpha.
17287 o Minor bugfixes (client, IPv6):
17288 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
17289 flag is not set; and not because the NoIPv4Traffic flag was set.
17290 Previously we'd looked at the NoIPv4Traffic flag for both types of
17291 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
17293 o Minor bugfixes (client, microdescriptors):
17294 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
17295 computing which microdescriptors to download. This keeps us from
17296 erroneous download behavior if two microdescriptor digests ever
17297 have the same first 160 bits. Fixes part of bug 13399; bugfix
17299 - Reset a router's status if its microdescriptor digest changes,
17300 even if the first 160 bits remain the same. Fixes part of bug
17301 13399; bugfix on 0.2.3.1-alpha.
17303 o Minor bugfixes (client, torrc):
17304 - Stop modifying the value of our DirReqStatistics torrc option just
17305 because we're not a bridge or relay. This bug was causing Tor
17306 Browser users to write "DirReqStatistics 0" in their torrc files
17307 as if they had chosen to change the config. Fixes bug 4244; bugfix
17309 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
17310 that our options have changed every time we SIGHUP. Fixes bug
17311 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
17313 o Minor bugfixes (compilation):
17314 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
17316 - Silence clang warnings under --enable-expensive-hardening,
17317 including implicit truncation of 64 bit values to 32 bit, const
17318 char assignment to self, tautological compare, and additional
17319 parentheses around equality tests. Fixes bug 13577; bugfix
17321 - Fix a clang warning about checking whether an address in the
17322 middle of a structure is NULL. Fixes bug 14001; bugfix
17324 - The address of an array in the middle of a structure will always
17325 be non-NULL. clang recognises this and complains. Disable the
17326 tautologous and redundant check to silence this warning. Fixes bug
17327 14001; bugfix on 0.2.1.2-alpha.
17328 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
17329 Addresses ticket 14188.
17330 - Build without warnings with the stock OpenSSL srtp.h header, which
17331 has a duplicate declaration of SSL_get_selected_srtp_profile().
17332 Fixes bug 14220; this is OpenSSL's bug, not ours.
17333 - Do not compile any code related to Tor2Web mode when Tor2Web mode
17334 is not enabled at compile time. Previously, this code was included
17335 in a disabled state. See discussion on ticket 12844.
17336 - Allow our configure script to build correctly with autoconf 2.62
17337 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
17338 - Improve the error message from ./configure to make it clear that
17339 when asciidoc has not been found, the user will have to either add
17340 --disable-asciidoc argument or install asciidoc. Resolves
17343 o Minor bugfixes (controller):
17344 - Report "down" in response to the "GETINFO entry-guards" command
17345 when relays are down with an unreachable_since value. Previously,
17346 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
17347 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
17348 14116; bugfix on 0.2.2.9-alpha.
17350 o Minor bugfixes (controller):
17351 - Return an error when the second or later arguments of the
17352 "setevents" controller command are invalid events. Previously we
17353 would return success while silently skipping invalid events. Fixes
17354 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
17356 o Minor bugfixes (directory authority):
17357 - Allow directory authorities to fetch more data from one another if
17358 they find themselves missing lots of votes. Previously, they had
17359 been bumping against the 10 MB queued data limit. Fixes bug 14261;
17360 bugfix on 0.1.2.5-alpha.
17361 - Do not attempt to download extrainfo documents which we will be
17362 unable to validate with a matching server descriptor. Fixes bug
17363 13762; bugfix on 0.2.0.1-alpha.
17364 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
17365 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
17366 - Enlarge the buffer to read bwauth generated files to avoid an
17367 issue when parsing the file in dirserv_read_measured_bandwidths().
17368 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
17369 - When running as a v3 directory authority, advertise that you serve
17370 extra-info documents so that clients who want them can find them
17371 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
17373 o Minor bugfixes (directory system):
17374 - Always believe that v3 directory authorities serve extra-info
17375 documents, whether they advertise "caches-extra-info" or not.
17376 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
17377 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
17378 Previously, directories offering BRIDGE_DIRINFO and some other
17379 flag (i.e. microdescriptors or extrainfo) would be ignored when
17380 looking for bridges. Partially fixes bug 13163; bugfix
17383 o Minor bugfixes (file handling):
17384 - Stop failing when key files are zero-length. Instead, generate new
17385 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
17386 on all versions of Tor. Patch by "teor".
17387 - Stop generating a fresh .old RSA onion key file when the .old file
17388 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
17389 - Avoid overwriting .old key files with empty key files.
17390 - Skip loading zero-length extrainfo store, router store, stats,
17391 state, and key files.
17392 - Avoid crashing when trying to reload a torrc specified as a
17393 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
17396 o Minor bugfixes (hidden services):
17397 - Close the introduction circuit when we have no more usable intro
17398 points, instead of waiting for it to time out. This also ensures
17399 that no follow-up HS descriptor fetch is triggered when the
17400 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
17401 - When fetching a hidden service descriptor for a down service that
17402 was recently up, do not keep refetching until we try the same
17403 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
17404 - Correctly send a controller event when we find that a rendezvous
17405 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
17406 - Pre-check directory permissions for new hidden-services to avoid
17407 at least one case of "Bug: Acting on config options left us in a
17408 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
17409 - When fetching hidden service descriptors, we now check not only
17410 for whether we got the hidden service we had in mind, but also
17411 whether we got the particular descriptors we wanted. This prevents
17412 a class of inefficient but annoying DoS attacks by hidden service
17413 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
17416 o Minor bugfixes (Linux seccomp2 sandbox):
17417 - Make transparent proxy support work along with the seccomp2
17418 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
17419 by Francisco Blas Izquierdo Riera.
17420 - Fix a memory leak in tor-resolve when running with the sandbox
17421 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
17422 - Allow glibc fatal errors to be sent to stderr before Tor exits.
17423 Previously, glibc would try to write them to /dev/tty, and the
17424 sandbox would trap the call and make Tor exit prematurely. Fixes
17425 bug 14759; bugfix on 0.2.5.1-alpha.
17427 o Minor bugfixes (logging):
17428 - Avoid crashing when there are more log domains than entries in
17429 domain_list. Bugfix on 0.2.3.1-alpha.
17430 - Downgrade warnings about RSA signature failures to info log level.
17431 Emit a warning when an extra info document is found incompatible
17432 with a corresponding router descriptor. Fixes bug 9812; bugfix
17434 - Make connection_ap_handshake_attach_circuit() log the circuit ID
17435 correctly. Fixes bug 13701; bugfix on 0.0.6.
17437 o Minor bugfixes (networking):
17438 - Check for orconns and use connection_or_close_for_error() rather
17439 than connection_mark_for_close() directly in the getsockopt()
17440 failure case of connection_handle_write_impl(). Fixes bug 11302;
17441 bugfix on 0.2.4.4-alpha.
17443 o Minor bugfixes (parsing):
17444 - Stop accepting milliseconds (or other junk) at the end of
17445 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
17446 - Support two-number and three-number version numbers correctly, in
17447 case we change the Tor versioning system in the future. Fixes bug
17448 13661; bugfix on 0.0.8pre1.
17450 o Minor bugfixes (portability):
17451 - Fix the ioctl()-based network interface lookup code so that it
17452 will work on systems that have variable-length struct ifreq, for
17454 - Use the correct datatype in the SipHash-2-4 function to prevent
17455 compilers from assuming any sort of alignment. Fixes bug 15436;
17456 bugfix on 0.2.5.3-alpha.
17458 o Minor bugfixes (preventative security, C safety):
17459 - When reading a hexadecimal, base-32, or base-64 encoded value from
17460 a string, always overwrite the whole output buffer. This prevents
17461 some bugs where we would look at (but fortunately, not reveal)
17462 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
17464 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
17465 just the part that's used. This makes it harder for data leak bugs
17466 to occur in the event of other programming failures. Resolves
17469 o Minor bugfixes (relay):
17470 - When generating our family list, remove spaces from around the
17471 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
17472 - If our previous bandwidth estimate was 0 bytes, allow publishing a
17473 new relay descriptor immediately. Fixes bug 13000; bugfix
17476 o Minor bugfixes (shutdown):
17477 - When shutting down, always call event_del() on lingering read or
17478 write events before freeing them. Otherwise, we risk double-frees
17479 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
17482 o Minor bugfixes (small memory leaks):
17483 - Avoid leaking memory when using IPv6 virtual address mappings.
17484 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
17487 o Minor bugfixes (statistics):
17488 - Increase period over which bandwidth observations are aggregated
17489 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
17491 o Minor bugfixes (systemd support):
17492 - Run correctly under systemd with the RunAsDaemon option set. Fixes
17493 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
17494 - Inform the systemd supervisor about more changes in the Tor
17495 process status. Implements part of ticket 14141. Patch from
17498 o Minor bugfixes (testing networks):
17499 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
17500 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
17501 - Stop using the default authorities in networks which provide both
17502 AlternateDirAuthority and AlternateBridgeAuthority. Partially
17503 fixes bug 13163; bugfix on 0.2.0.13-alpha.
17505 o Minor bugfixes (testing networks, fast startup):
17506 - Allow Tor to build circuits using a consensus with no exits. If
17507 the consensus has no exits (typical of a bootstrapping test
17508 network), allow Tor to build circuits once enough descriptors have
17509 been downloaded. This assists in bootstrapping a testing Tor
17510 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
17512 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
17513 header to directory servers. This allows us to obtain consensuses
17514 promptly when the consensus interval is very short. This assists
17515 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
17516 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
17517 - Stop assuming that private addresses are local when checking
17518 reachability in a TestingTorNetwork. Instead, when testing, assume
17519 all OR connections are remote. (This is necessary due to many test
17520 scenarios running all relays on localhost.) This assists in
17521 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
17522 0.1.0.1-rc. Patch by "teor".
17523 - Avoid building exit circuits from a consensus with no exits. Now
17524 thanks to our fix for 13718, we accept a no-exit network as not
17525 wholly lost, but we need to remember not to try to build exit
17526 circuits on it. Closes ticket 13814; patch by "teor".
17527 - Stop requiring exits to have non-zero bandwithcapacity in a
17528 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
17529 ignore exit bandwidthcapacity. This assists in bootstrapping a
17530 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
17531 on 0.2.0.3-alpha. Patch by "teor".
17532 - Add "internal" to some bootstrap statuses when no exits are
17533 available. If the consensus does not contain Exits, Tor will only
17534 build internal circuits. In this case, relevant statuses will
17535 contain the word "internal" as indicated in the Tor control-
17536 spec.txt. When bootstrap completes, Tor will be ready to build
17537 internal circuits. If a future consensus contains Exits, exit
17538 circuits may become available. Fixes part of bug 13718; bugfix on
17539 0.2.4.10-alpha. Patch by "teor".
17540 - Decrease minimum consensus interval to 10 seconds when
17541 TestingTorNetwork is set, or 5 seconds for the first consensus.
17542 Fix assumptions throughout the code that assume larger intervals.
17543 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
17545 - Avoid excluding guards from path building in minimal test
17546 networks, when we're in a test network and excluding guards would
17547 exclude all relays. This typically occurs in incredibly small tor
17548 networks, and those using "TestingAuthVoteGuard *". Fixes part of
17549 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
17551 o Minor bugfixes (testing):
17552 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
17553 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
17554 - Stop spawn test failures due to a race condition between the
17555 SIGCHLD handler updating the process status, and the test reading
17556 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
17557 - Avoid passing an extra backslash when creating a temporary
17558 directory for running the unit tests on Windows. Fixes bug 12392;
17559 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
17561 o Minor bugfixes (TLS):
17562 - Check more thoroughly throughout the TLS code for possible
17563 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
17565 o Minor bugfixes (transparent proxy):
17566 - Use getsockname, not getsockopt, to retrieve the address for a
17567 TPROXY-redirected connection. Fixes bug 13796; bugfix
17570 o Minor bugfixes (windows):
17571 - Remove code to special-case handling of NTE_BAD_KEYSET when
17572 acquiring windows CryptoAPI context. This error can't actually
17573 occur for the parameters we're providing. Fixes bug 10816; bugfix
17576 o Minor bugfixes (zlib):
17577 - Avoid truncating a zlib stream when trying to finalize it with an
17578 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
17580 o Code simplification and refactoring:
17581 - Change the entry_is_live() function to take named bitfield
17582 elements instead of an unnamed list of booleans. Closes
17584 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
17585 Resolves ticket 12205.
17586 - Use calloc and reallocarray functions instead of multiply-
17587 then-malloc. This makes it less likely for us to fall victim to an
17588 integer overflow attack when allocating. Resolves ticket 12855.
17589 - Use the standard macro name SIZE_MAX, instead of our
17591 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
17592 functions which take them as arguments. Replace 0 with NO_DIRINFO
17593 in a function call for clarity. Seeks to prevent future issues
17595 - Avoid 4 null pointer errors under clang static analysis by using
17596 tor_assert() to prove that the pointers aren't null. Fixes
17598 - Rework the API of policies_parse_exit_policy() to use a bitmask to
17599 represent parsing options, instead of a confusing mess of
17600 booleans. Resolves ticket 8197.
17601 - Introduce a helper function to parse ExitPolicy in
17602 or_options_t structure.
17603 - Move fields related to isolating and configuring client ports into
17604 a shared structure. Previously, they were duplicated across
17605 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
17606 to copy them correctly had been the cause of at least one bug in
17607 the past. Closes ticket 8546.
17608 - Refactor the get_interface_addresses_raw() doom-function into
17609 multiple smaller and simpler subfunctions. Cover the resulting
17610 subfunctions with unit-tests. Fixes a significant portion of
17612 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
17613 only for version <= 0.2.2.24 which is now deprecated. Closes
17615 - Remove a test for a long-defunct broken version-one
17617 - Refactor main loop to extract the 'loop' part. This makes it
17618 easier to run Tor under Shadow. Closes ticket 15176.
17619 - Stop using can_complete_circuits as a global variable; access it
17620 with a function instead.
17621 - Avoid using operators directly as macro arguments: this lets us
17622 apply coccinelle transformations to our codebase more directly.
17623 Closes ticket 13172.
17624 - Combine the functions used to parse ClientTransportPlugin and
17625 ServerTransportPlugin into a single function. Closes ticket 6456.
17626 - Add inline functions and convenience macros for inspecting channel
17627 state. Refactor the code to use convenience macros instead of
17628 checking channel state directly. Fixes issue 7356.
17629 - Document all members of was_router_added_t and rename
17630 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
17631 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
17632 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
17633 constant instead of hardcoded value. Fixes issue 13840.
17634 - Refactor our generic strmap and digestmap types into a single
17635 implementation, so that we can add a new digest256map
17639 - Add a doc/TUNING document with tips for handling large numbers of
17640 TCP connections when running busy Tor relay. Update the warning
17641 message to point to this file when running out of sockets
17642 operating system is allowing to use simultaneously. Resolves
17644 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
17645 for writing the OpenBSD-specific tips. Resolves ticket 13702.
17646 - Make the tor-resolve documentation match its help string and its
17647 options. Resolves part of ticket 14325.
17648 - Log a more useful error message from tor-resolve when failing to
17649 look up a hidden service address. Resolves part of ticket 14325.
17650 - Document the bridge-authority-only 'networkstatus-bridges' file.
17651 Closes ticket 13713; patch from "tom".
17652 - Fix typo in PredictedPortsRelevanceTime option description in
17653 manpage. Resolves issue 13707.
17654 - Stop suggesting that users specify relays by nickname: it isn't a
17655 good idea. Also, properly cross-reference how to specify relays in
17656 all parts of manual documenting options that take a list of
17657 relays. Closes ticket 13381.
17658 - Clarify the HiddenServiceDir option description in manpage to make
17659 it clear that relative paths are taken with respect to the current
17660 working directory. Also clarify that this behavior is not
17661 guaranteed to remain indefinitely. Fixes issue 13913.
17663 o Distribution (systemd):
17664 - systemd unit file: only allow tor to write to /var/lib/tor and
17665 /var/log/tor. The rest of the filesystem is accessible for reading
17666 only. Patch by intrigeri; resolves ticket 12751.
17667 - systemd unit file: ensure that the process and all its children
17668 can never gain new privileges. Patch by intrigeri; resolves
17670 - systemd unit file: set up /var/run/tor as writable for the Tor
17671 service. Patch by intrigeri; resolves ticket 13196.
17673 o Downgraded warnings:
17674 - Don't warn when we've attempted to contact a relay using the wrong
17675 ntor onion key. Closes ticket 9635.
17678 - Remove some lingering dead code that once supported mempools.
17679 Mempools were disabled by default in 0.2.5, and removed entirely
17680 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
17683 o Removed features (directory authorities):
17684 - Remove code that prevented authorities from listing Tor relays
17685 affected by CVE-2011-2769 as guards. These relays are already
17686 rejected altogether due to the minimum version requirement of
17687 0.2.3.16-alpha. Closes ticket 13152.
17688 - The "AuthDirRejectUnlisted" option no longer has any effect, as
17689 the fingerprints file (approved-routers) has been deprecated.
17690 - Directory authorities do not support being Naming dirauths anymore.
17691 The "NamingAuthoritativeDir" config option is now obsolete.
17692 - Directory authorities do not support giving out the BadDirectory
17694 - Directory authorities no longer advertise or support consensus
17695 methods 1 through 12 inclusive. These consensus methods were
17696 obsolete and/or insecure: maintaining the ability to support them
17697 served no good purpose. Implements part of proposal 215; closes
17700 o Removed features:
17701 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
17702 longer silently accepted as an alias for "ExitNodes".
17703 - The --enable-mempool and --enable-buf-freelists options, which
17704 were originally created to work around bad malloc implementations,
17705 no longer exist. They were off-by-default in 0.2.5. Closes
17707 - We no longer remind the user about configuration options that have
17708 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
17709 - Remove our old, non-weighted bandwidth-based node selection code.
17710 Previously, we used it as a fallback when we couldn't perform
17711 weighted bandwidth-based node selection. But that would only
17712 happen in the cases where we had no consensus, or when we had a
17713 consensus generated by buggy or ancient directory authorities. In
17714 either case, it's better to use the more modern, better maintained
17715 algorithm, with reasonable defaults for the weights. Closes
17717 - Remove the --disable-curve25519 configure option. Relays and
17718 clients now are required to support curve25519 and the
17720 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
17721 used to be deprecated synonyms for "StrictNodes", are now marked
17722 obsolete. Resolves ticket 12226.
17723 - Clients don't understand the BadDirectory flag in the consensus
17724 anymore, and ignore it.
17726 o Removed platform support:
17727 - We no longer include special code to build on Windows CE; as far
17728 as we know, nobody has used Tor on Windows CE in a very long time.
17729 Closes ticket 11446.
17731 o Testing (test-network.sh):
17732 - Stop using "echo -n", as some shells' built-in echo doesn't
17733 support "-n". Instead, use "/bin/echo -n". Partially fixes
17735 - Stop an apparent test-network hang when used with make -j2. Fixes
17737 - Add a --delay option to test-network.sh, which configures the
17738 delay before the chutney network tests for data transmission.
17739 Partially implements ticket 13161.
17742 - Test that tor does not fail when key files are zero-length. Check
17743 that tor generates new keys, and overwrites the empty key files.
17744 - Test that tor generates new keys when keys are missing
17745 (existing behavior).
17746 - Test that tor does not overwrite key files that already contain
17747 data (existing behavior). Tests bug 13111. Patch by "teor".
17748 - New "make test-stem" target to run stem integration tests.
17749 Requires that the "STEM_SOURCE_DIR" environment variable be set.
17750 Closes ticket 14107.
17751 - Make the test_cmdline_args.py script work correctly on Windows.
17752 Patch from Gisle Vanem.
17753 - Move the slower unit tests into a new "./src/test/test-slow"
17754 binary that can be run independently of the other tests. Closes
17756 - New tests for many parts of channel, relay, and circuitmux
17757 functionality. Code by Andrea; part of 9262.
17758 - New tests for parse_transport_line(). Part of ticket 6456.
17759 - In the unit tests, use chgrp() to change the group of the unit
17760 test temporary directory to the current user, so that the sticky
17761 bit doesn't interfere with tests that check directory groups.
17763 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
17765 - Refactor the function that chooses guard nodes so that it can more
17766 easily be tested; write some tests for it.
17767 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
17768 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
17769 - Create unit tests for format_time_interval(). With bug 13393.
17770 - Add unit tests for tor_timegm signed overflow, tor_timegm and
17771 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
17772 tests (visible) fixes in bug 13476.
17773 - Add a "coverage-html" make target to generate HTML-visualized
17774 coverage results when building with --enable-coverage. (Requires
17775 lcov.) Patch from Kevin Murray.
17776 - Enable the backtrace handler (where supported) when running the
17778 - Revise all unit tests that used the legacy test_* macros to
17779 instead use the recommended tt_* macros. This patch was generated
17780 with coccinelle, to avoid manual errors. Closes ticket 13119.
17782 Changes in version 0.2.5.11 - 2015-03-17
17783 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
17785 It backports several bugfixes from the 0.2.6 branch, including a
17786 couple of medium-level security fixes for relays and exit nodes.
17787 It also updates the list of directory authorities.
17789 o Directory authority changes:
17790 - Remove turtles as a directory authority.
17791 - Add longclaw as a new (v3) directory authority. This implements
17792 ticket 13296. This keeps the directory authority count at 9.
17793 - The directory authority Faravahar has a new IP address. This
17794 closes ticket 14487.
17796 o Major bugfixes (crash, OSX, security):
17797 - Fix a remote denial-of-service opportunity caused by a bug in
17798 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
17801 o Major bugfixes (relay, stability, possible security):
17802 - Fix a bug that could lead to a relay crashing with an assertion
17803 failure if a buffer of exactly the wrong layout was passed to
17804 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
17805 0.2.0.10-alpha. Patch from 'cypherpunks'.
17806 - Do not assert if the 'data' pointer on a buffer is advanced to the
17807 very end of the buffer; log a BUG message instead. Only assert if
17808 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
17810 o Major bugfixes (exit node stability):
17811 - Fix an assertion failure that could occur under high DNS load.
17812 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
17813 diagnosed and fixed by "cypherpunks".
17815 o Major bugfixes (Linux seccomp2 sandbox):
17816 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
17817 crash during attempts to call wait4. Fixes bug 15088; bugfix on
17818 0.2.5.1-alpha. Patch from "sanic".
17820 o Minor features (controller):
17821 - New "GETINFO bw-event-cache" to get information about recent
17822 bandwidth events. Closes ticket 14128. Useful for controllers to
17823 get recent bandwidth history after the fix for ticket 13988.
17825 o Minor features (geoip):
17826 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
17827 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
17830 o Minor bugfixes (client, automapping):
17831 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
17832 no value follows the option. Fixes bug 14142; bugfix on
17833 0.2.4.7-alpha. Patch by "teor".
17834 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
17835 14195; bugfix on 0.1.0.1-rc.
17837 o Minor bugfixes (compilation):
17838 - Build without warnings with the stock OpenSSL srtp.h header, which
17839 has a duplicate declaration of SSL_get_selected_srtp_profile().
17840 Fixes bug 14220; this is OpenSSL's bug, not ours.
17842 o Minor bugfixes (directory authority):
17843 - Allow directory authorities to fetch more data from one another if
17844 they find themselves missing lots of votes. Previously, they had
17845 been bumping against the 10 MB queued data limit. Fixes bug 14261;
17846 bugfix on 0.1.2.5-alpha.
17847 - Enlarge the buffer to read bwauth generated files to avoid an
17848 issue when parsing the file in dirserv_read_measured_bandwidths().
17849 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
17851 o Minor bugfixes (statistics):
17852 - Increase period over which bandwidth observations are aggregated
17853 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
17855 o Minor bugfixes (preventative security, C safety):
17856 - When reading a hexadecimal, base-32, or base-64 encoded value from
17857 a string, always overwrite the whole output buffer. This prevents
17858 some bugs where we would look at (but fortunately, not reveal)
17859 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
17863 Changes in version 0.2.4.26 - 2015-03-17
17864 Tor 0.2.4.26 includes an updated list of directory authorities. It
17865 also backports a couple of stability and security bugfixes from 0.2.5
17868 o Directory authority changes:
17869 - Remove turtles as a directory authority.
17870 - Add longclaw as a new (v3) directory authority. This implements
17871 ticket 13296. This keeps the directory authority count at 9.
17872 - The directory authority Faravahar has a new IP address. This
17873 closes ticket 14487.
17875 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
17876 - Fix an assertion failure that could occur under high DNS load.
17877 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
17878 diagnosed and fixed by "cypherpunks".
17880 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
17881 - Fix a bug that could lead to a relay crashing with an assertion
17882 failure if a buffer of exactly the wrong layout was passed to
17883 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
17884 0.2.0.10-alpha. Patch from 'cypherpunks'.
17885 - Do not assert if the 'data' pointer on a buffer is advanced to the
17886 very end of the buffer; log a BUG message instead. Only assert if
17887 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
17889 o Minor features (geoip):
17890 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
17891 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
17894 Changes in version 0.2.5.10 - 2014-10-24
17895 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
17897 It adds several new security features, including improved
17898 denial-of-service resistance for relays, new compiler hardening
17899 options, and a system-call sandbox for hardened installations on Linux
17900 (requires seccomp2). The controller protocol has several new features,
17901 resolving IPv6 addresses should work better than before, and relays
17902 should be a little more CPU-efficient. We've added support for more
17903 OpenBSD and FreeBSD transparent proxy types. We've improved the build
17904 system and testing infrastructure to allow unit testing of more parts
17905 of the Tor codebase. Finally, we've addressed several nagging pluggable
17906 transport usability issues, and included numerous other small bugfixes
17907 and features mentioned below.
17909 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
17910 have accumulated many known flaws; everyone should upgrade.
17912 o Major features (security):
17913 - The ntor handshake is now on-by-default, no matter what the
17914 directory authorities recommend. Implements ticket 8561.
17915 - Make the "tor-gencert" tool used by directory authority operators
17916 create 2048-bit signing keys by default (rather than 1024-bit, since
17917 1024-bit is uncomfortably small these days). Addresses ticket 10324.
17918 - Warn about attempts to run hidden services and relays in the same
17919 process: that's probably not a good idea. Closes ticket 12908.
17920 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
17921 today support TLS 1.0 or later, so we can safely turn off support
17922 for this old (and insecure) protocol. Fixes bug 13426.
17924 o Major features (relay security, DoS-resistance):
17925 - When deciding whether we have run out of memory and we need to
17926 close circuits, also consider memory allocated in buffers for
17927 streams attached to each circuit.
17929 This change, which extends an anti-DoS feature introduced in
17930 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
17931 better resist more memory-based DoS attacks than before. Since the
17932 MaxMemInCellQueues option now applies to all queues, it is renamed
17933 to MaxMemInQueues. This feature fixes bug 10169.
17934 - Avoid hash-flooding denial-of-service attacks by using the secure
17935 SipHash-2-4 hash function for our hashtables. Without this
17936 feature, an attacker could degrade performance of a targeted
17937 client or server by flooding their data structures with a large
17938 number of entries to be stored at the same hash table position,
17939 thereby slowing down the Tor instance. With this feature, hash
17940 table positions are derived from a randomized cryptographic key,
17941 and an attacker cannot predict which entries will collide. Closes
17943 - If you don't specify MaxMemInQueues yourself, Tor now tries to
17944 pick a good value based on your total system memory. Previously,
17945 the default was always 8 GB. You can still override the default by
17946 setting MaxMemInQueues yourself. Resolves ticket 11396.
17948 o Major features (bridges and pluggable transports):
17949 - Add support for passing arguments to managed pluggable transport
17950 proxies. Implements ticket 3594.
17951 - Bridges now track GeoIP information and the number of their users
17952 even when pluggable transports are in use, and report usage
17953 statistics in their extra-info descriptors. Resolves tickets 4773
17955 - Don't launch pluggable transport proxies if we don't have any
17956 bridges configured that would use them. Now we can list many
17957 pluggable transports, and Tor will dynamically start one when it
17958 hears a bridge address that needs it. Resolves ticket 5018.
17959 - The bridge directory authority now assigns status flags (Stable,
17960 Guard, etc) to bridges based on thresholds calculated over all
17961 Running bridges. Now bridgedb can finally make use of its features
17962 to e.g. include at least one Stable bridge in its answers. Fixes
17965 o Major features (controller):
17966 - Extend ORCONN controller event to include an "ID" parameter,
17967 and add four new controller event types CONN_BW, CIRC_BW,
17968 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
17969 The new events are emitted in private Tor networks only, with the
17970 goal of being able to better track performance and load during
17971 full-network simulations. Implements proposal 218 and ticket 7359.
17973 o Major features (relay performance):
17974 - Speed up server-side lookups of rendezvous and introduction point
17975 circuits by using hashtables instead of linear searches. These
17976 functions previously accounted between 3 and 7% of CPU usage on
17977 some busy relays. Resolves ticket 9841.
17978 - Avoid wasting CPU when extending a circuit over a channel that is
17979 nearly out of circuit IDs. Previously, we would do a linear scan
17980 over possible circuit IDs before finding one or deciding that we
17981 had exhausted our possibilities. Now, we try at most 64 random
17982 circuit IDs before deciding that we probably won't succeed. Fixes
17983 a possible root cause of ticket 11553.
17985 o Major features (seccomp2 sandbox, Linux only):
17986 - Use the seccomp2 syscall filtering facility on Linux to limit
17987 which system calls Tor can invoke. This is an experimental,
17988 Linux-only feature to provide defense-in-depth against unknown
17989 attacks. To try turning it on, set "Sandbox 1" in your torrc
17990 file. Please be ready to report bugs. We hope to add support
17991 for better sandboxing in the future, including more fine-grained
17992 filters, better division of responsibility, and support for more
17993 platforms. This work has been done by Cristian-Matei Toader for
17994 Google Summer of Code. Resolves tickets 11351 and 11465.
17996 o Major features (testing networks):
17997 - Make testing Tor networks bootstrap better: lower directory fetch
17998 retry schedules and maximum interval without directory requests,
17999 and raise maximum download tries. Implements ticket 6752.
18000 - Add make target 'test-network' to run tests on a Chutney network.
18001 Implements ticket 8530.
18003 o Major features (other):
18004 - On some platforms (currently: recent OSX versions, glibc-based
18005 platforms that support the ELF format, and a few other
18006 Unix-like operating systems), Tor can now dump stack traces
18007 when a crash occurs or an assertion fails. By default, traces
18008 are dumped to stderr (if possible) and to any logs that are
18009 reporting errors. Implements ticket 9299.
18011 o Deprecated versions:
18012 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
18013 attention for some while.
18015 o Major bugfixes (security, directory authorities):
18016 - Directory authorities now include a digest of each relay's
18017 identity key as a part of its microdescriptor.
18019 This is a workaround for bug 11743 (reported by "cypherpunks"),
18020 where Tor clients do not support receiving multiple
18021 microdescriptors with the same SHA256 digest in the same
18022 consensus. When clients receive a consensus like this, they only
18023 use one of the relays. Without this fix, a hostile relay could
18024 selectively disable some client use of target relays by
18025 constructing a router descriptor with a different identity and the
18026 same microdescriptor parameters and getting the authorities to
18027 list it in a microdescriptor consensus. This fix prevents an
18028 attacker from causing a microdescriptor collision, because the
18029 router's identity is not forgeable.
18031 o Major bugfixes (openssl bug workaround):
18032 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
18033 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
18034 bug 13471. This is a workaround for an OpenSSL bug.
18036 o Major bugfixes (client):
18037 - Perform circuit cleanup operations even when circuit
18038 construction operations are disabled (because the network is
18039 disabled, or because there isn't enough directory information).
18040 Previously, when we were not building predictive circuits, we
18041 were not closing expired circuits either. Fixes bug 8387; bugfix on
18042 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
18043 became more strict about when we have "enough directory information
18044 to build circuits".
18046 o Major bugfixes (client, pluggable transports):
18047 - When managing pluggable transports, use OS notification facilities
18048 to learn if they have crashed, and don't attempt to kill any
18049 process that has already exited. Fixes bug 8746; bugfix
18052 o Major bugfixes (relay denial of service):
18053 - Instead of writing destroy cells directly to outgoing connection
18054 buffers, queue them and intersperse them with other outgoing cells.
18055 This can prevent a set of resource starvation conditions where too
18056 many pending destroy cells prevent data cells from actually getting
18057 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
18058 bugfix on 0.2.0.1-alpha.
18060 o Major bugfixes (relay):
18061 - Avoid queuing or sending destroy cells for circuit ID zero when we
18062 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
18063 Found and fixed by "cypherpunks".
18064 - Fix ORPort reachability detection on relays running behind a
18065 proxy, by correctly updating the "local" mark on the controlling
18066 channel when changing the address of an or_connection_t after the
18067 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
18068 - Use a direct dirport connection when uploading non-anonymous
18069 descriptors to the directory authorities. Previously, relays would
18070 incorrectly use tunnel connections under a fairly wide variety of
18071 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
18072 - When a circuit accidentally has the same circuit ID for its
18073 forward and reverse direction, correctly detect the direction of
18074 cells using that circuit. Previously, this bug made roughly one
18075 circuit in a million non-functional. Fixes bug 12195; this is a
18076 bugfix on every version of Tor.
18078 o Minor features (security):
18079 - New --enable-expensive-hardening option to enable security
18080 hardening options that consume nontrivial amounts of CPU and
18081 memory. Right now, this includes AddressSanitizer and UbSan, which
18082 are supported in newer versions of GCC and Clang. Closes ticket
18084 - Authorities now assign the Guard flag to the fastest 25% of the
18085 network (it used to be the fastest 50%). Also raise the consensus
18086 weight that guarantees the Guard flag from 250 to 2000. For the
18087 current network, this results in about 1100 guards, down from 2500.
18088 This step paves the way for moving the number of entry guards
18089 down to 1 (proposal 236) while still providing reasonable expected
18090 performance for most users. Implements ticket 12690.
18092 o Minor features (security, memory management):
18093 - Memory allocation tricks (mempools and buffer freelists) are now
18094 disabled by default. You can turn them back on with
18095 --enable-mempools and --enable-buf-freelists respectively. We're
18096 disabling these features because malloc performance is good enough
18097 on most platforms, and a similar feature in OpenSSL exacerbated
18098 exploitation of the Heartbleed attack. Resolves ticket 11476.
18100 o Minor features (bridge client):
18101 - Report a more useful failure message when we can't connect to a
18102 bridge because we don't have the right pluggable transport
18103 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
18105 o Minor features (bridge):
18106 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
18107 cookie file for the ExtORPort g+r by default.
18109 o Minor features (bridges, pluggable transports):
18110 - Bridges now write the SHA1 digest of their identity key
18111 fingerprint (that is, a hash of a hash of their public key) to
18112 notice-level logs, and to a new hashed-fingerprint file. This
18113 information will help bridge operators look up their bridge in
18114 Globe and similar tools. Resolves ticket 10884.
18115 - Improve the message that Tor displays when running as a bridge
18116 using pluggable transports without an Extended ORPort listener.
18117 Also, log the message in the log file too. Resolves ticket 11043.
18118 - Add threshold cutoffs to the networkstatus document created by
18119 the Bridge Authority. Fixes bug 1117.
18120 - On Windows, spawn background processes using the CREATE_NO_WINDOW
18121 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
18122 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
18123 Vidalia set this option for us.) Implements ticket 10297.
18125 o Minor features (build):
18126 - The configure script has a --disable-seccomp option to turn off
18127 support for libseccomp on systems that have it, in case it (or
18128 Tor's use of it) is broken. Resolves ticket 11628.
18129 - Assume that a user using ./configure --host wants to cross-compile,
18130 and give an error if we cannot find a properly named
18131 tool-chain. Add a --disable-tool-name-check option to proceed
18132 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
18133 - If we run ./configure and the compiler recognizes -fstack-protector
18134 but the linker rejects it, warn the user about a potentially missing
18135 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
18136 - Add support for `--library-versions` flag. Implements ticket 6384.
18137 - Return the "unexpected sendme" warnings to a warn severity, but make
18138 them rate limited, to help diagnose ticket 8093.
18139 - Detect a missing asciidoc, and warn the user about it, during
18140 configure rather than at build time. Fixes issue 6506. Patch from
18143 o Minor features (client):
18144 - Add a new option, PredictedPortsRelevanceTime, to control how long
18145 after having received a request to connect to a given port Tor
18146 will try to keep circuits ready in anticipation of future requests
18147 for that port. Patch from "unixninja92"; implements ticket 9176.
18149 o Minor features (config options and command line):
18150 - Add an --allow-missing-torrc commandline option that tells Tor to
18151 run even if the configuration file specified by -f is not available.
18152 Implements ticket 10060.
18153 - Add support for the TPROXY transparent proxying facility on Linux.
18154 See documentation for the new TransProxyType option for more
18155 details. Implementation by "thomo". Closes ticket 10582.
18157 o Minor features (config options):
18158 - Config (torrc) lines now handle fingerprints which are missing
18159 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
18160 - Support a --dump-config option to print some or all of the
18161 configured options. Mainly useful for debugging the command-line
18162 option parsing code. Helps resolve ticket 4647.
18163 - Raise awareness of safer logging: notify user of potentially
18164 unsafe config options, like logging more verbosely than severity
18165 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
18166 - Add a new configuration option TestingV3AuthVotingStartOffset
18167 that bootstraps a network faster by changing the timing for
18168 consensus votes. Addresses ticket 8532.
18169 - Add a new torrc option "ServerTransportOptions" that allows
18170 bridge operators to pass configuration parameters to their
18171 pluggable transports. Resolves ticket 8929.
18172 - The config (torrc) file now accepts bandwidth and space limits in
18173 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
18174 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
18177 o Minor features (controller):
18178 - Make the entire exit policy available from the control port via
18179 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
18181 - Because of the fix for ticket 11396, the real limit for memory
18182 usage may no longer match the configured MaxMemInQueues value. The
18183 real limit is now exposed via GETINFO limits/max-mem-in-queues.
18184 - Add a new "HS_DESC" controller event that reports activities
18185 related to hidden service descriptors. Resolves ticket 8510.
18186 - New "DROPGUARDS" controller command to forget all current entry
18187 guards. Not recommended for ordinary use, since replacing guards
18188 too frequently makes several attacks easier. Resolves ticket 9934;
18190 - Implement the TRANSPORT_LAUNCHED control port event that
18191 notifies controllers about new launched pluggable
18192 transports. Resolves ticket 5609.
18194 o Minor features (diagnostic):
18195 - When logging a warning because of bug 7164, additionally check the
18196 hash table for consistency (as proposed on ticket 11737). This may
18197 help diagnose bug 7164.
18198 - When we log a heartbeat, log how many one-hop circuits we have
18199 that are at least 30 minutes old, and log status information about
18200 a few of them. This is an attempt to track down bug 8387.
18201 - When encountering an unexpected CR while writing text to a file on
18202 Windows, log the name of the file. Should help diagnosing
18204 - Give more specific warnings when a client notices that an onion
18205 handshake has failed. Fixes ticket 9635.
18206 - Add significant new logging code to attempt to diagnose bug 12184,
18207 where relays seem to run out of available circuit IDs.
18208 - Improve the diagnostic log message for bug 8387 even further to
18209 try to improve our odds of figuring out why one-hop directory
18210 circuits sometimes do not get closed.
18211 - Add more log messages to diagnose bug 7164, which causes
18212 intermittent "microdesc_free() called but md was still referenced"
18213 warnings. We now include more information, to figure out why we
18214 might be cleaning a microdescriptor for being too old if it's
18215 still referenced by a live node_t object.
18216 - Log current accounting state (bytes sent and received + remaining
18217 time for the current accounting period) in the relay's heartbeat
18218 message. Implements ticket 5526; patch from Peter Retzlaff.
18220 o Minor features (geoip):
18221 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
18224 o Minor features (interface):
18225 - Generate a warning if any ports are listed in the SocksPolicy,
18226 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
18227 AuthDirBadExit options. (These options only support address
18228 ranges.) Fixes part of ticket 11108.
18230 o Minor features (kernel API usage):
18231 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
18232 sockets in a single system call. Implements ticket 5129.
18234 o Minor features (log messages):
18235 - When ServerTransportPlugin is set on a bridge, Tor can write more
18236 useful statistics about bridge use in its extrainfo descriptors,
18237 but only if the Extended ORPort ("ExtORPort") is set too. Add a
18238 log message to inform the user in this case. Resolves ticket 9651.
18239 - When receiving a new controller connection, log the origin address.
18240 Resolves ticket 9698; patch from "sigpipe".
18241 - When logging OpenSSL engine status at startup, log the status of
18242 more engines. Fixes ticket 10043; patch from Joshua Datko.
18244 o Minor features (log verbosity):
18245 - Demote the message that we give when a flushing connection times
18246 out for too long from NOTICE to INFO. It was usually meaningless.
18247 Resolves ticket 5286.
18248 - Don't log so many notice-level bootstrapping messages at startup
18249 about downloading descriptors. Previously, we'd log a notice
18250 whenever we learned about more routers. Now, we only log a notice
18251 at every 5% of progress. Fixes bug 9963.
18252 - Warn less verbosely when receiving a malformed
18253 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
18255 o Minor features (performance):
18256 - If we're using the pure-C 32-bit curve25519_donna implementation
18257 of curve25519, build it with the -fomit-frame-pointer option to
18258 make it go faster on register-starved hosts. This improves our
18259 handshake performance by about 6% on i386 hosts without nacl.
18260 Closes ticket 8109.
18262 o Minor features (relay):
18263 - If a circuit timed out for at least 3 minutes, check if we have a
18264 new external IP address, and publish a new descriptor with the new
18265 IP address if it changed. Resolves ticket 2454.
18267 o Minor features (testing):
18268 - If Python is installed, "make check" now runs extra tests beyond
18269 the unit test scripts.
18270 - When bootstrapping a test network, sometimes very few relays get
18271 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
18272 specify a set of relays which should be voted Guard regardless of
18273 their uptime or bandwidth. Addresses ticket 9206.
18275 o Minor features (transparent proxy, *BSD):
18276 - Support FreeBSD's ipfw firewall interface for TransPort ports on
18277 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
18278 10267; patch from "yurivict".
18279 - Support OpenBSD's divert-to rules with the pf firewall for
18280 transparent proxy ports. To enable it, set "TransProxyType
18281 pf-divert". This allows Tor to run a TransPort transparent proxy
18282 port on OpenBSD 4.4 or later without root privileges. See the
18283 pf.conf(5) manual page for information on configuring pf to use
18284 divert-to rules. Closes ticket 10896; patch from Dana Koch.
18286 o Minor bugfixes (bridge client):
18287 - Stop accepting bridge lines containing hostnames. Doing so would
18288 cause clients to perform DNS requests on the hostnames, which was
18289 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
18291 o Minor bugfixes (bridges):
18292 - Avoid potential crashes or bad behavior when launching a
18293 server-side managed proxy with ORPort or ExtORPort temporarily
18294 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
18295 - Fix a bug where the first connection works to a bridge that uses a
18296 pluggable transport with client-side parameters, but we don't send
18297 the client-side parameters on subsequent connections. (We don't
18298 use any pluggable transports with client-side parameters yet,
18299 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
18300 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
18302 o Minor bugfixes (build, auxiliary programs):
18303 - Stop preprocessing the "torify" script with autoconf, since
18304 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
18306 - The tor-fw-helper program now follows the standard convention and
18307 exits with status code "0" on success. Fixes bug 9030; bugfix on
18308 0.2.3.1-alpha. Patch by Arlo Breault.
18309 - Corrected ./configure advice for what openssl dev package you should
18310 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
18312 o Minor bugfixes (client):
18313 - Avoid "Tried to open a socket with DisableNetwork set" warnings
18314 when starting a client with bridges configured and DisableNetwork
18315 set. (Tor launcher starts Tor with DisableNetwork set the first
18316 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
18317 - Improve the log message when we can't connect to a hidden service
18318 because all of the hidden service directory nodes hosting its
18319 descriptor are excluded. Improves on our fix for bug 10722, which
18320 was a bugfix on 0.2.0.10-alpha.
18321 - Raise a control port warning when we fail to connect to all of
18322 our bridges. Previously, we didn't inform the controller, and
18323 the bootstrap process would stall. Fixes bug 11069; bugfix on
18325 - Exit immediately when a process-owning controller exits.
18326 Previously, tor relays would wait for a little while after their
18327 controller exited, as if they had gotten an INT signal -- but this
18328 was problematic, since there was no feedback for the user. To do a
18329 clean shutdown, controllers should send an INT signal and give Tor
18330 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
18331 - Stop attempting to connect to bridges before our pluggable
18332 transports are configured (harmless but resulted in some erroneous
18333 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
18334 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
18335 generating incorrect SOCKS5 responses, and confusing client
18336 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
18338 o Minor bugfixes (client, DNSPort):
18339 - When using DNSPort, try to respond to AAAA requests with AAAA
18340 answers. Previously, we hadn't looked at the request type when
18341 deciding which answer type to prefer. Fixes bug 10468; bugfix on
18343 - When receiving a DNS query for an unsupported record type, reply
18344 with no answer rather than with a NOTIMPL error. This behavior
18345 isn't correct either, but it will break fewer client programs, we
18346 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
18349 o Minor bugfixes (client, logging during bootstrap):
18350 - Only report the first fatal bootstrap error on a given OR
18351 connection. This stops us from telling the controller bogus error
18352 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
18353 - Avoid generating spurious warnings when starting with
18354 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
18357 o Minor bugfixes (closing OR connections):
18358 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
18359 check if it's an or_connection_t and correctly call
18360 connection_or_close_for_error() rather than
18361 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
18363 - When closing all connections on setting DisableNetwork to 1, use
18364 connection_or_close_normally() rather than closing OR connections
18365 out from under the channel layer. Fixes bug 11306; bugfix on
18368 o Minor bugfixes (code correctness):
18369 - Previously we used two temporary files when writing descriptors to
18370 disk; now we only use one. Fixes bug 1376.
18371 - Remove an erroneous (but impossible and thus harmless) pointer
18372 comparison that would have allowed compilers to skip a bounds
18373 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
18374 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
18375 - Fix an always-true assertion in pluggable transports code so it
18376 actually checks what it was trying to check. Fixes bug 10046;
18377 bugfix on 0.2.3.9-alpha. Found by "dcb".
18379 o Minor bugfixes (command line):
18380 - Use a single command-line parser for parsing torrc options on the
18381 command line and for finding special command-line options to avoid
18382 inconsistent behavior for torrc option arguments that have the same
18383 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
18385 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
18386 9573; bugfix on 0.0.9pre5.
18388 o Minor bugfixes (compilation):
18389 - Compile correctly with builds and forks of OpenSSL (such as
18390 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
18391 0.2.1.1-alpha. Patch from "dhill".
18392 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
18393 turned off (that is, without support for v2 link handshakes). Fixes
18394 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
18395 - In routerlist_assert_ok(), don't take the address of a
18396 routerinfo's cache_info member unless that routerinfo is non-NULL.
18397 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
18398 - Fix a large number of false positive warnings from the clang
18399 analyzer static analysis tool. This should make real warnings
18400 easier for clang analyzer to find. Patch from "teor". Closes
18402 - Resolve GCC complaints on OpenBSD about discarding constness in
18403 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
18404 on 0.1.1.23. Patch from Dana Koch.
18405 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
18406 treatment of long and time_t as comparable types. Fixes part of
18407 bug 11633. Patch from Dana Koch.
18408 - When deciding whether to build the 64-bit curve25519
18409 implementation, detect platforms where we can compile 128-bit
18410 arithmetic but cannot link it. Fixes bug 11729; bugfix on
18411 0.2.4.8-alpha. Patch from "conradev".
18412 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
18413 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
18414 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
18416 - Build and run correctly on systems like OpenBSD-current that have
18417 patched OpenSSL to remove get_cipher_by_char and/or its
18418 implementations. Fixes issue 13325.
18420 o Minor bugfixes (controller and command-line):
18421 - If changing a config option via "setconf" fails in a recoverable
18422 way, we used to nonetheless write our new control ports to the
18423 file described by the "ControlPortWriteToFile" option. Now we only
18424 write out that file if we successfully switch to the new config
18425 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
18427 o Minor bugfixes (directory server):
18428 - No longer accept malformed http headers when parsing urls from
18429 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
18430 bugfix on 0.0.6pre1.
18431 - When sending a compressed set of descriptors or microdescriptors,
18432 make sure to finalize the zlib stream. Previously, we would write
18433 all the compressed data, but if the last descriptor we wanted to
18434 send was missing or too old, we would not mark the stream as
18435 finished. This caused problems for decompression tools. Fixes bug
18436 11648; bugfix on 0.1.1.23.
18438 o Minor bugfixes (hidden service):
18439 - Only retry attempts to connect to a chosen rendezvous point 8
18440 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
18442 o Minor bugfixes (interface):
18443 - Reject relative control socket paths and emit a warning. Previously,
18444 single-component control socket paths would be rejected, but Tor
18445 would not log why it could not validate the config. Fixes bug 9258;
18446 bugfix on 0.2.3.16-alpha.
18448 o Minor bugfixes (log messages):
18449 - Fix a bug where clients using bridges would report themselves
18450 as 50% bootstrapped even without a live consensus document.
18451 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
18452 - Suppress a warning where, if there's only one directory authority
18453 in the network, we would complain that votes and signatures cannot
18454 be uploaded to other directory authorities. Fixes bug 10842;
18455 bugfix on 0.2.2.26-beta.
18456 - Report bootstrapping progress correctly when we're downloading
18457 microdescriptors. We had updated our "do we have enough microdescs
18458 to begin building circuits?" logic most recently in 0.2.4.10-alpha
18459 (see bug 5956), but we left the bootstrap status event logic at
18460 "how far through getting 1/4 of them are we?" Fixes bug 9958;
18461 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
18463 o Minor bugfixes (logging):
18464 - Downgrade "Unexpected onionskin length after decryption" warning
18465 to a protocol-warn, since there's nothing relay operators can do
18466 about a client that sends them a malformed create cell. Resolves
18467 bug 12996; bugfix on 0.0.6rc1.
18468 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
18469 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
18470 - When logging information about an EXTEND2 or EXTENDED2 cell, log
18471 their names correctly. Fixes part of bug 12700; bugfix
18473 - When logging information about a relay cell whose command we don't
18474 recognize, log its command as an integer. Fixes part of bug 12700;
18475 bugfix on 0.2.1.10-alpha.
18476 - Escape all strings from the directory connection before logging
18477 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
18478 - Squelch a spurious LD_BUG message "No origin circuit for
18479 successful SOCKS stream" in certain hidden service failure cases;
18481 - Downgrade the severity of the 'unexpected sendme cell from client'
18482 from 'warn' to 'protocol warning'. Closes ticket 8093.
18484 o Minor bugfixes (misc code correctness):
18485 - In munge_extrainfo_into_routerinfo(), check the return value of
18486 memchr(). This would have been a serious issue if we ever passed
18487 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
18489 - On the chance that somebody manages to build Tor on a
18490 platform where time_t is unsigned, correct the way that
18491 microdesc_add_to_cache() handles negative time arguments.
18492 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
18493 - Fix various instances of undefined behavior in channeltls.c,
18494 tor_memmem(), and eventdns.c that would cause us to construct
18495 pointers to memory outside an allocated object. (These invalid
18496 pointers were not accessed, but C does not even allow them to
18497 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
18498 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
18499 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
18500 fix some miscellaneous errors in our tests and codebase. Fixes bug
18501 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
18502 - Always check return values for unlink, munmap, UnmapViewOfFile;
18503 check strftime return values more often. In some cases all we can
18504 do is report a warning, but this may help prevent deeper bugs from
18505 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
18507 - Fix numerous warnings from the clang "scan-build" static analyzer.
18508 Some of these are programming style issues; some of them are false
18509 positives that indicated awkward code; some are undefined behavior
18510 cases related to constructing (but not using) invalid pointers;
18511 some are assumptions about API behavior; some are (harmlessly)
18512 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
18513 correct; and one or two are genuine bugs that weren't reachable
18514 from the rest of the program. Fixes bug 8793; bugfixes on many,
18517 o Minor bugfixes (node selection):
18518 - If ExcludeNodes is set, consider non-excluded hidden service
18519 directory servers before excluded ones. Do not consider excluded
18520 hidden service directory servers at all if StrictNodes is
18521 set. (Previously, we would sometimes decide to connect to those
18522 servers, and then realize before we initiated a connection that
18523 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
18524 Reported by "mr-4".
18525 - If we set the ExitNodes option but it doesn't include any nodes
18526 that have the Exit flag, we would choose not to bootstrap. Now we
18527 bootstrap so long as ExitNodes includes nodes which can exit to
18528 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
18530 o Minor bugfixes (performance):
18531 - Avoid a bug where every successful connection made us recompute
18532 the flag telling us whether we have sufficient information to
18533 build circuits. Previously, we would forget our cached value
18534 whenever we successfully opened a channel (or marked a router as
18535 running or not running for any other reason), regardless of
18536 whether we had previously believed the router to be running. This
18537 forced us to run an expensive update operation far too often.
18538 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
18539 - Avoid using tor_memeq() for checking relay cell integrity. This
18540 removes a possible performance bottleneck. Fixes part of bug
18541 12169; bugfix on 0.2.1.31.
18543 o Minor bugfixes (platform-specific):
18544 - When dumping a malformed directory object to disk, save it in
18545 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
18547 - Don't report failures from make_socket_reuseable() on incoming
18548 sockets on OSX: this can happen when incoming connections close
18549 early. Fixes bug 10081.
18551 o Minor bugfixes (pluggable transports):
18552 - Avoid another 60-second delay when starting Tor in a pluggable-
18553 transport-using configuration when we already have cached
18554 descriptors for our bridges. Fixes bug 11965; bugfix
18557 o Minor bugfixes (protocol correctness):
18558 - When receiving a VERSIONS cell with an odd number of bytes, close
18559 the connection immediately since the cell is malformed. Fixes bug
18560 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
18563 o Minor bugfixes (relay, other):
18564 - We now drop CREATE cells for already-existent circuit IDs and for
18565 zero-valued circuit IDs, regardless of other factors that might
18566 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
18568 - When rejecting DATA cells for stream_id zero, still count them
18569 against the circuit's deliver window so that we don't fail to send
18570 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
18572 o Minor bugfixes (relay, threading):
18573 - Check return code on spawn_func() in cpuworker code, so that we
18574 don't think we've spawned a nonworking cpuworker and write junk to
18575 it forever. Fix related to bug 4345; bugfix on all released Tor
18576 versions. Found by "skruffy".
18577 - Use a pthread_attr to make sure that spawn_func() cannot return an
18578 error while at the same time launching a thread. Fix related to
18579 bug 4345; bugfix on all released Tor versions. Reported
18582 o Minor bugfixes (relays and bridges):
18583 - Avoid crashing on a malformed resolv.conf file when running a
18584 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
18585 - Non-exit relays no longer launch mock DNS requests to check for
18586 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
18587 non-exit relays stopped servicing DNS requests. Fixes bug 965;
18588 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
18589 - Bridges now report complete directory request statistics. Related
18590 to bug 5824; bugfix on 0.2.2.1-alpha.
18591 - Bridges now never collect statistics that were designed for
18592 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
18594 o Minor bugfixes (testing):
18595 - Fix all valgrind warnings produced by the unit tests. There were
18596 over a thousand memory leak warnings previously, mostly produced
18597 by forgetting to free things in the unit test code. Fixes bug
18598 11618, bugfixes on many versions of Tor.
18600 o Minor bugfixes (tor-fw-helper):
18601 - Give a correct log message when tor-fw-helper fails to launch.
18602 (Previously, we would say something like "tor-fw-helper sent us a
18603 string we could not parse".) Fixes bug 9781; bugfix
18606 o Minor bugfixes (trivial memory leaks):
18607 - Fix a small memory leak when signing a directory object. Fixes bug
18608 11275; bugfix on 0.2.4.13-alpha.
18609 - Resolve some memory leaks found by coverity in the unit tests, on
18610 exit in tor-gencert, and on a failure to compute digests for our
18611 own keys when generating a v3 networkstatus vote. These leaks
18612 should never have affected anyone in practice.
18614 o Code simplification and refactoring:
18615 - Remove some old fallback code designed to keep Tor clients working
18616 in a network with only two working relays. Elsewhere in the code we
18617 have long since stopped supporting such networks, so there wasn't
18618 much point in keeping it around. Addresses ticket 9926.
18619 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
18620 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
18621 - Extract the common duplicated code for creating a subdirectory
18622 of the data directory and writing to a file in it. Fixes ticket
18623 4282; patch from Peter Retzlaff.
18624 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
18625 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
18626 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
18627 - Add a set of accessor functions for the circuit timeout data
18628 structure. Fixes ticket 6153; patch from "piet".
18629 - Clean up exit paths from connection_listener_new(). Closes ticket
18630 8789. Patch from Arlo Breault.
18631 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
18632 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
18633 - Use a doubly-linked list to implement the global circuit list.
18634 Resolves ticket 9108. Patch from Marek Majkowski.
18635 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
18636 - Remove constants and tests for PKCS1 padding; it's insecure and
18637 shouldn't be used for anything new. Fixes bug 8792; patch
18639 - Remove instances of strcpy() from the unit tests. They weren't
18640 hurting anything, since they were only in the unit tests, but it's
18641 embarrassing to have strcpy() in the code at all, and some analysis
18642 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
18643 0.2.3.8-alpha. Patch from Arlo Breault.
18644 - Remove is_internal_IP() function. Resolves ticket 4645.
18645 - Remove unused function circuit_dump_by_chan from circuitlist.c.
18646 Closes issue 9107; patch from "marek".
18647 - Change our use of the ENUM_BF macro to avoid declarations that
18649 - Get rid of router->address, since in all cases it was just the
18650 string representation of router->addr. Resolves ticket 5528.
18653 - Adjust the URLs in the README to refer to the new locations of
18654 several documents on the website. Fixes bug 12830. Patch from
18656 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
18658 - Update manpage to describe some of the files you can expect to
18659 find in Tor's DataDirectory. Addresses ticket 9839.
18660 - Clean up several option names in the manpage to match their real
18661 names, add the missing documentation for a couple of testing and
18662 directory authority options, remove the documentation for a
18663 V2-directory fetching option that no longer exists. Resolves
18665 - Correct the documentation so that it lists the correct directory
18666 for the stats files. (They are in a subdirectory called "stats",
18668 - In the manpage, move more authority-only options into the
18669 directory authority section so that operators of regular directory
18670 caches don't get confused.
18671 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
18672 11061; bugfix on 0.2.4.7-alpha.
18673 - Resolve warnings from Doxygen.
18674 - Document in the manpage that "KBytes" may also be written as
18675 "kilobytes" or "KB", that "Kbits" may also be written as
18676 "kilobits", and so forth. Closes ticket 9222.
18677 - Document that the ClientOnly config option overrides ORPort.
18678 Our old explanation made ClientOnly sound as though it did
18679 nothing at all. Resolves bug 9059.
18680 - Explain that SocksPolicy, DirPolicy, and similar options don't
18681 take port arguments. Fixes the other part of ticket 11108.
18682 - Fix a comment about the rend_server_descriptor_t.protocols field
18683 to more accurately describe its range. Also, make that field
18684 unsigned, to more accurately reflect its usage. Fixes bug 9099;
18685 bugfix on 0.2.1.5-alpha.
18686 - Fix the manpage's description of HiddenServiceAuthorizeClient:
18687 the maximum client name length is 16, not 19. Fixes bug 11118;
18688 bugfix on 0.2.1.6-alpha.
18691 - The contrib directory has been sorted and tidied. Before, it was
18692 an unsorted dumping ground for useful and not-so-useful things.
18693 Now, it is divided based on functionality, and the items which
18694 seemed to be nonfunctional or useless have been removed. Resolves
18695 ticket 8966; based on patches from "rl1987".
18697 o Removed code and features:
18698 - Clients now reject any directory authority certificates lacking
18699 a dir-key-crosscert element. These have been included since
18700 0.2.1.9-alpha, so there's no real reason for them to be optional
18701 any longer. Completes proposal 157. Resolves ticket 10162.
18702 - Remove all code that existed to support the v2 directory system,
18703 since there are no longer any v2 directory authorities. Resolves
18705 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
18706 options, which were used for designating authorities as "Hidden
18707 service authorities". There has been no use of hidden service
18708 authorities since 0.2.2.1-alpha, when we stopped uploading or
18709 downloading v0 hidden service descriptors. Fixes bug 10881; also
18710 part of a fix for bug 10841.
18711 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
18712 and MTBF calculations, but that nobody was using. Fixes bug 11742.
18713 - The TunnelDirConns and PreferTunnelledDirConns options no longer
18714 exist; tunneled directory connections have been available since
18715 0.1.2.5-alpha, and turning them off is not a good idea. This is a
18716 brute-force fix for 10849, where "TunnelDirConns 0" would break
18718 - Remove all code for the long unused v1 directory protocol.
18719 Resolves ticket 11070.
18720 - Remove all remaining code related to version-0 hidden service
18721 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
18722 the rest of bug 10841.
18723 - Remove migration code from when we renamed the "cached-routers"
18724 file to "cached-descriptors" back in 0.2.0.8-alpha. This
18725 incidentally resolves ticket 6502 by cleaning up the related code
18726 a bit. Patch from Akshay Hebbar.
18728 o Test infrastructure:
18729 - Tor now builds each source file in two modes: a mode that avoids
18730 exposing identifiers needlessly, and another mode that exposes
18731 more identifiers for testing. This lets the compiler do better at
18732 optimizing the production code, while enabling us to take more
18733 radical measures to let the unit tests test things.
18734 - The production builds no longer include functions used only in
18735 the unit tests; all functions exposed from a module only for
18736 unit-testing are now static in production builds.
18737 - Add an --enable-coverage configuration option to make the unit
18738 tests (and a new src/or/tor-cov target) to build with gcov test
18740 - Update to the latest version of tinytest.
18741 - Improve the tinytest implementation of string operation tests so
18742 that comparisons with NULL strings no longer crash the tests; they
18743 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
18744 - New macros in test.h to simplify writing mock-functions for unit
18745 tests. Part of ticket 11507. Patch from Dana Koch.
18746 - We now have rudimentary function mocking support that our unit
18747 tests can use to test functions in isolation. Function mocking
18748 lets the tests temporarily replace a function's dependencies with
18749 stub functions, so that the tests can check the function without
18750 invoking the other functions it calls.
18753 - Complete tests for the status.c module. Resolves ticket 11507.
18754 Patch from Dana Koch.
18755 - Add more unit tests for the <circid,channel>->circuit map, and
18756 the destroy-cell-tracking code to fix bug 7912.
18757 - Unit tests for failing cases of the TAP onion handshake.
18758 - More unit tests for address-manipulation functions.
18760 o Distribution (systemd):
18761 - Include a tor.service file in contrib/dist for use with systemd.
18762 Some distributions will be able to use this file unmodified;
18763 others will need to tweak it, or write their own. Patch from Jamie
18764 Nguyen; resolves ticket 8368.
18765 - Verify configuration file via ExecStartPre in the systemd unit
18766 file. Patch from intrigeri; resolves ticket 12730.
18767 - Explicitly disable RunAsDaemon in the systemd unit file. Our
18768 current systemd unit uses "Type = simple", so systemd does not
18769 expect tor to fork. If the user has "RunAsDaemon 1" in their
18770 torrc, then things won't work as expected. This is e.g. the case
18771 on Debian (and derivatives), since there we pass "--defaults-torrc
18772 /usr/share/tor/tor-service-defaults-torrc" (that contains
18773 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
18777 Changes in version 0.2.4.25 - 2014-10-20
18778 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
18779 (even though POODLE does not affect Tor). It also works around a crash
18780 bug caused by some operating systems' response to the "POODLE" attack
18781 (which does affect Tor).
18783 o Major security fixes (also in 0.2.5.9-rc):
18784 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
18785 today support TLS 1.0 or later, so we can safely turn off support
18786 for this old (and insecure) protocol. Fixes bug 13426.
18788 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
18789 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
18790 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
18791 13471. This is a workaround for an OpenSSL bug.
18794 Changes in version 0.2.4.24 - 2014-09-22
18795 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
18796 connecting to hidden services, and it updates the location of one of
18797 the directory authorities.
18800 - Clients now send the correct address for their chosen rendezvous
18801 point when trying to access a hidden service. They used to send
18802 the wrong address, which would still work some of the time because
18803 they also sent the identity digest of the rendezvous point, and if
18804 the hidden service happened to try connecting to the rendezvous
18805 point from a relay that already had a connection open to it,
18806 the relay would reuse that connection. Now connections to hidden
18807 services should be more robust and faster. Also, this bug meant
18808 that clients were leaking to the hidden service whether they were
18809 on a little-endian (common) or big-endian (rare) system, which for
18810 some users might have reduced their anonymity. Fixes bug 13151;
18811 bugfix on 0.2.1.5-alpha.
18813 o Directory authority changes:
18814 - Change IP address for gabelmoo (v3 directory authority).
18816 o Minor features (geoip):
18817 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
18821 Changes in version 0.2.4.23 - 2014-07-28
18822 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
18823 guard rotation, and also backports several important fixes from the
18824 Tor 0.2.5 alpha release series.
18827 - Clients now look at the "usecreatefast" consensus parameter to
18828 decide whether to use CREATE_FAST or CREATE cells for the first hop
18829 of their circuit. This approach can improve security on connections
18830 where Tor's circuit handshake is stronger than the available TLS
18831 connection security levels, but the tradeoff is more computational
18832 load on guard relays. Implements proposal 221. Resolves ticket 9386.
18833 - Make the number of entry guards configurable via a new
18834 NumEntryGuards consensus parameter, and the number of directory
18835 guards configurable via a new NumDirectoryGuards consensus
18836 parameter. Implements ticket 12688.
18839 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
18840 implementation that caused incorrect results on 32-bit
18841 implementations when certain malformed inputs were used along with
18842 a small class of private ntor keys. This bug does not currently
18843 appear to allow an attacker to learn private keys or impersonate a
18844 Tor server, but it could provide a means to distinguish 32-bit Tor
18845 implementations from 64-bit Tor implementations. Fixes bug 12694;
18846 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
18850 - Warn and drop the circuit if we receive an inbound 'relay early'
18851 cell. Those used to be normal to receive on hidden service circuits
18852 due to bug 1038, but the buggy Tor versions are long gone from
18853 the network so we can afford to resume watching for them. Resolves
18854 the rest of bug 1038; bugfix on 0.2.1.19.
18855 - Correct a confusing error message when trying to extend a circuit
18856 via the control protocol but we don't know a descriptor or
18857 microdescriptor for one of the specified relays. Fixes bug 12718;
18858 bugfix on 0.2.3.1-alpha.
18859 - Avoid an illegal read from stack when initializing the TLS
18860 module using a version of OpenSSL without all of the ciphers
18861 used by the v2 link handshake. Fixes bug 12227; bugfix on
18862 0.2.4.8-alpha. Found by "starlight".
18865 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
18869 Changes in version 0.2.4.22 - 2014-05-16
18870 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
18871 alpha release series. These include blocking all authority signing
18872 keys that may have been affected by the OpenSSL "heartbleed" bug,
18873 choosing a far more secure set of TLS ciphersuites by default, closing
18874 a couple of memory leaks that could be used to run a target relay out
18875 of RAM, and several others.
18877 o Major features (security, backport from 0.2.5.4-alpha):
18878 - Block authority signing keys that were used on authorities
18879 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
18880 don't have any evidence that these keys _were_ compromised; we're
18881 doing this to be prudent.) Resolves ticket 11464.
18883 o Major bugfixes (security, OOM):
18884 - Fix a memory leak that could occur if a microdescriptor parse
18885 fails during the tokenizing step. This bug could enable a memory
18886 exhaustion attack by directory servers. Fixes bug 11649; bugfix
18889 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
18890 - The relay ciphersuite list is now generated automatically based on
18891 uniform criteria, and includes all OpenSSL ciphersuites with
18892 acceptable strength and forward secrecy. Previously, we had left
18893 some perfectly fine ciphersuites unsupported due to omission or
18894 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
18895 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
18896 - Relays now trust themselves to have a better view than clients of
18897 which TLS ciphersuites are better than others. (Thanks to bug
18898 11513, the relay list is now well-considered, whereas the client
18899 list has been chosen mainly for anti-fingerprinting purposes.)
18900 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
18901 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
18902 AES128. Resolves ticket 11528.
18903 - Clients now try to advertise the same list of ciphersuites as
18904 Firefox 28. This change enables selection of (fast) GCM
18905 ciphersuites, disables some strange old ciphers, and stops
18906 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
18907 Resolves ticket 11438.
18909 o Minor bugfixes (configuration, security):
18910 - When running a hidden service, do not allow TunneledDirConns 0:
18911 trying to set that option together with a hidden service would
18912 otherwise prevent the hidden service from running, and also make
18913 it publish its descriptors directly over HTTP. Fixes bug 10849;
18914 bugfix on 0.2.1.1-alpha.
18916 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
18917 - Avoid sending a garbage value to the controller when a circuit is
18918 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
18920 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
18921 - Stop leaking memory when we successfully resolve a PTR record.
18922 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
18924 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
18925 - Avoid 60-second delays in the bootstrapping process when Tor is
18926 launching for a second time while using bridges. Fixes bug 9229;
18927 bugfix on 0.2.0.3-alpha.
18929 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
18930 - Give the correct URL in the warning message when trying to run a
18931 relay on an ancient version of Windows. Fixes bug 9393.
18933 o Minor bugfixes (compilation):
18934 - Fix a compilation error when compiling with --disable-curve25519.
18935 Fixes bug 9700; bugfix on 0.2.4.17-rc.
18938 - Downgrade the warning severity for the the "md was still
18939 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
18940 for trying to diagnose this bug, and the current warning in
18941 earlier versions of tor achieves nothing useful. Addresses warning
18944 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
18945 - When we run out of usable circuit IDs on a channel, log only one
18946 warning for the whole channel, and describe how many circuits
18947 there were on the channel. Fixes part of ticket 11553.
18949 o Minor features (security, backport from 0.2.5.4-alpha):
18950 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
18951 leave the default at 8GBytes), to better support Raspberry Pi
18952 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
18954 o Documentation (backport from 0.2.5.4-alpha):
18955 - Correctly document that we search for a system torrc file before
18956 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
18960 Changes in version 0.2.4.21 - 2014-02-28
18961 Tor 0.2.4.21 further improves security against potential adversaries who
18962 find breaking 1024-bit crypto doable, and backports several stability
18963 and robustness patches from the 0.2.5 branch.
18965 o Major features (client security):
18966 - When we choose a path for a 3-hop circuit, make sure it contains
18967 at least one relay that supports the NTor circuit extension
18968 handshake. Otherwise, there is a chance that we're building
18969 a circuit that's worth attacking by an adversary who finds
18970 breaking 1024-bit crypto doable, and that chance changes the game
18971 theory. Implements ticket 9777.
18974 - Do not treat streams that fail with reason
18975 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
18976 since it could also indicate an ENETUNREACH connection error. Fixes
18977 part of bug 10777; bugfix on 0.2.4.8-alpha.
18979 o Code simplification and refactoring:
18980 - Remove data structures which were introduced to implement the
18981 CellStatistics option: they are now redundant with the new timestamp
18982 field in the regular packed_cell_t data structure, which we did
18983 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
18986 - Always clear OpenSSL bignums before freeing them -- even bignums
18987 that don't contain secrets. Resolves ticket 10793. Patch by
18989 - Build without warnings under clang 3.4. (We have some macros that
18990 define static functions only some of which will get used later in
18991 the module. Starting with clang 3.4, these give a warning unless the
18992 unused attribute is set on them.) Resolves ticket 10904.
18993 - Update geoip and geoip6 files to the February 7 2014 Maxmind
18994 GeoLite2 Country database.
18997 - Set the listen() backlog limit to the largest actually supported
18998 on the system, not to the value in a header file. Fixes bug 9716;
18999 bugfix on every released Tor.
19000 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
19001 exit node as a NOROUTE error, not an INTERNAL error, since they
19002 can apparently happen when trying to connect to the wrong sort
19003 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
19004 - Fix build warnings about missing "a2x" comment when building the
19005 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
19006 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
19007 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
19008 not entirely remove it from the connection lists. Fixes bug 9602;
19009 bugfix on 0.2.4.4-alpha.
19010 - Fix a segmentation fault in our benchmark code when running with
19011 Fedora's OpenSSL package, or any other OpenSSL that provides
19012 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
19013 - Turn "circuit handshake stats since last time" log messages into a
19014 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
19016 o Documentation fixes:
19017 - Document that all but one DirPort entry must have the NoAdvertise
19018 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
19021 Changes in version 0.2.4.20 - 2013-12-22
19022 Tor 0.2.4.20 fixes potentially poor random number generation for users
19023 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
19024 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
19025 and 4) have no state file in their DataDirectory (as would happen on
19026 first start). Users who generated relay or hidden service identity
19027 keys in such a situation should discard them and generate new ones.
19029 This release also fixes a logic error that caused Tor clients to build
19030 many more preemptive circuits than they actually need.
19033 - Do not allow OpenSSL engines to replace the PRNG, even when
19034 HardwareAccel is set. The only default builtin PRNG engine uses
19035 the Intel RDRAND instruction to replace the entire PRNG, and
19036 ignores all attempts to seed it with more entropy. That's
19037 cryptographically stupid: the right response to a new alleged
19038 entropy source is never to discard all previously used entropy
19039 sources. Fixes bug 10402; works around behavior introduced in
19040 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
19042 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
19043 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
19044 - Avoid launching spurious extra circuits when a stream is pending.
19045 This fixes a bug where any circuit that _wasn't_ unusable for new
19046 streams would be treated as if it were, causing extra circuits to
19047 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
19050 - Avoid a crash bug when starting with a corrupted microdescriptor
19051 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
19052 - If we fail to dump a previously cached microdescriptor to disk, avoid
19053 freeing duplicate data later on. Fixes bug 10423; bugfix on
19054 0.2.4.13-alpha. Spotted by "bobnomnom".
19057 Changes in version 0.2.4.19 - 2013-12-11
19058 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
19059 (1986-2013). Aaron worked on diverse projects including helping to guide
19060 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
19061 transparency to the U.S government's PACER documents, and contributing
19062 design and development for Tor and Tor2Web. Aaron was one of the latest
19063 martyrs in our collective fight for civil liberties and human rights,
19064 and his death is all the more painful because he was one of us.
19066 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
19067 a new circuit handshake and link encryption that use ECC to provide
19068 better security and efficiency; makes relays better manage circuit
19069 creation requests; uses "directory guards" to reduce client enumeration
19070 risks; makes bridges collect and report statistics about the pluggable
19071 transports they support; cleans up and improves our geoip database;
19072 gets much closer to IPv6 support for clients, bridges, and relays; makes
19073 directory authorities use measured bandwidths rather than advertised
19074 ones when computing flags and thresholds; disables client-side DNS
19075 caching to reduce tracking risks; and fixes a big bug in bridge
19076 reachability testing. This release introduces two new design
19077 abstractions in the code: a new "channel" abstraction between circuits
19078 and or_connections to allow for implementing alternate relay-to-relay
19079 transports, and a new "circuitmux" abstraction storing the queue of
19080 circuits for a channel. The release also includes many stability,
19081 security, and privacy fixes.
19083 o Major features (new circuit handshake):
19084 - Tor now supports a new circuit extension handshake designed by Ian
19085 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
19086 circuit extension handshake, later called "TAP", was a bit slow
19087 (especially on the relay side), had a fragile security proof, and
19088 used weaker keys than we'd now prefer. The new circuit handshake
19089 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
19090 function, making it significantly more secure than the older
19091 handshake, and significantly faster. Tor can use one of two built-in
19092 pure-C curve25519-donna implementations by Adam Langley, or it
19093 can link against the "nacl" library for a tuned version if present.
19095 The built-in version is very fast for 64-bit systems when building
19096 with GCC. The built-in 32-bit version is still faster than the
19097 old TAP protocol, but using libnacl is better on most such hosts.
19099 Implements proposal 216; closes ticket 7202.
19101 o Major features (better link encryption):
19102 - Relays can now enable the ECDHE TLS ciphersuites when available
19103 and appropriate. These ciphersuites let us negotiate forward-secure
19104 TLS secret keys more safely and more efficiently than with our
19105 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
19106 public relays prefer the (faster) P224 group, and bridges prefer
19107 the (more common) P256 group; you can override this with the
19110 This feature requires clients running 0.2.3.17-beta or later,
19111 and requires both sides to be running OpenSSL 1.0.0 or later
19112 with ECC support. OpenSSL 1.0.1, with the compile-time option
19113 "enable-ec_nistp_64_gcc_128", is highly recommended.
19115 Implements the relay side of proposal 198; closes ticket 7200.
19117 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
19118 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
19119 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
19120 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
19121 them to solve bug 6033.)
19123 o Major features (relay performance):
19124 - Instead of limiting the number of queued onionskins (aka circuit
19125 create requests) to a fixed, hard-to-configure number, we limit
19126 the size of the queue based on how many we expect to be able to
19127 process in a given amount of time. We estimate the time it will
19128 take to process an onionskin based on average processing time
19129 of previous onionskins. Closes ticket 7291. You'll never have to
19130 configure MaxOnionsPending again.
19131 - Relays process the new "NTor" circuit-level handshake requests
19132 with higher priority than the old "TAP" circuit-level handshake
19133 requests. We still process some TAP requests to not totally starve
19134 0.2.3 clients when NTor becomes popular. A new consensus parameter
19135 "NumNTorsPerTAP" lets us tune the balance later if we need to.
19136 Implements ticket 9574.
19138 o Major features (client bootstrapping resilience):
19139 - Add a new "FallbackDir" torrc option to use when we can't use
19140 a directory mirror from the consensus (either because we lack a
19141 consensus, or because they're all down). Currently, all authorities
19142 are fallbacks by default, and there are no other default fallbacks,
19143 but that will change. This option will allow us to give clients a
19144 longer list of servers to try to get a consensus from when first
19145 connecting to the Tor network, and thereby reduce load on the
19146 directory authorities. Implements proposal 206, "Preconfigured
19147 directory sources for bootstrapping". We also removed the old
19148 "FallbackNetworkstatus" option, since we never got it working well
19149 enough to use it. Closes bug 572.
19150 - If we have no circuits open, use a relaxed timeout (the
19151 95th-percentile cutoff) until a circuit succeeds. This heuristic
19152 should allow Tor to succeed at building circuits even when the
19153 network connection drastically changes. Should help with bug 3443.
19155 o Major features (use of guards):
19156 - Support directory guards (proposal 207): when possible, clients now
19157 use their entry guards for non-anonymous directory requests. This
19158 can help prevent client enumeration. Note that this behavior only
19159 works when we have a usable consensus directory, and when options
19160 about what to download are more or less standard. In the future we
19161 should re-bootstrap from our guards, rather than re-bootstrapping
19162 from the preconfigured list of directory sources that ships with
19163 Tor. Resolves ticket 6526.
19164 - Raise the default time that a client keeps an entry guard from
19165 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
19166 2012 paper. (We would make it even longer, but we need better client
19167 load balancing first.) Also, make the guard lifetime controllable
19168 via a new GuardLifetime torrc option and a GuardLifetime consensus
19169 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
19171 o Major features (bridges with pluggable transports):
19172 - Bridges now report the pluggable transports they support to the
19173 bridge authority, so it can pass the supported transports on to
19174 bridgedb and/or eventually do reachability testing. Implements
19176 - Automatically forward the TCP ports of pluggable transport
19177 proxies using tor-fw-helper if PortForwarding is enabled. Implements
19180 o Major features (geoip database):
19181 - Maxmind began labelling Tor relays as being in country "A1",
19182 which breaks by-country node selection inside Tor. Now we use a
19183 script to replace "A1" ("Anonymous Proxy") entries in our geoip
19184 file with real country codes. This script fixes about 90% of "A1"
19185 entries automatically and uses manual country code assignments to
19186 fix the remaining 10%. See src/config/README.geoip for details.
19188 - Add GeoIP database for IPv6 addresses. The new config option
19190 - Update to the October 2 2013 Maxmind GeoLite Country database.
19192 o Major features (IPv6):
19193 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
19194 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
19195 to happen. Implements ticket 5535.
19196 - All kind of relays, not just bridges, can now advertise an IPv6
19197 OR port. Implements ticket 6362.
19198 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
19199 connectivity, then set the IPv6Exit flag to 1. Also make sure your
19200 exit policy reads as you would like: the address * applies to all
19201 address families, whereas *4 is IPv4 address only, and *6 is IPv6
19202 addresses only. On the client side, you'll need to wait for enough
19203 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
19204 and use Socks5. Closes ticket 5547, implements proposal 117 as
19205 revised in proposal 208.
19206 - Bridge authorities now accept IPv6 bridge addresses and include
19207 them in network status documents. Implements ticket 5534.
19208 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
19210 o Major features (directory authorities):
19211 - Directory authorities now prefer using measured bandwidths to
19212 advertised ones when computing flags and thresholds. Resolves
19214 - Directory authorities that vote measured bandwidths about more
19215 than a threshold number of relays now treat relays with
19216 unmeasured bandwidths as having bandwidth 0 when computing their
19217 flags. Resolves ticket 8435.
19218 - Directory authorities now support a new consensus method (17)
19219 where they cap the published bandwidth of relays for which
19220 insufficient bandwidth measurements exist. Fixes part of bug 2286.
19221 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
19222 serve any v2 directory information. Now we can test disabling the
19223 old deprecated v2 directory format, and see whether doing so has
19224 any effect on network load. Begins to fix bug 6783.
19226 o Major features (build and portability):
19227 - Switch to a nonrecursive Makefile structure. Now instead of each
19228 Makefile.am invoking other Makefile.am's, there is a master
19229 Makefile.am that includes the others. This change makes our build
19230 process slightly more maintainable, and improves parallelism for
19231 building with make -j. Original patch by Stewart Smith; various
19232 fixes by Jim Meyering.
19233 - Where available, we now use automake's "silent" make rules by
19234 default, so that warnings are easier to spot. You can get the old
19235 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
19236 - Resume building correctly with MSVC and Makefile.nmake. This patch
19237 resolves numerous bugs and fixes reported by ultramage, including
19238 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
19240 o Security features:
19241 - Switch to a completely time-invariant approach for picking nodes
19242 weighted by bandwidth. Our old approach would run through the
19243 part of the loop after it had made its choice slightly slower
19244 than it ran through the part of the loop before it had made its
19245 choice. Addresses ticket 6538.
19246 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
19247 by tor2web clients allows hidden services to identify tor2web
19248 clients through their repeated selection of the same rendezvous
19249 and introduction point circuit endpoints (their guards). Resolves
19252 o Major bugfixes (relay denial of service):
19253 - When we have too much memory queued in circuits (according to a new
19254 MaxMemInCellQueues option), close the circuits that have the oldest
19255 queued cells, on the theory that those are most responsible for
19256 us running low on memory. This prevents us from running out of
19257 memory as a relay if circuits fill up faster than they can be
19258 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
19259 Tor. This bug is a further fix beyond bug 6252, whose fix was
19260 merged into 0.2.3.21-rc.
19261 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
19262 ID: these could be used to create unexpected streams and circuits
19263 which would count as "present" to some parts of Tor but "absent"
19264 to others, leading to zombie circuits and streams or to a bandwidth
19265 denial-of-service. Fixes bug 7889; bugfix on every released version
19266 of Tor. Reported by "oftc_must_be_destroyed".
19267 - Avoid a bug where our response to TLS renegotiation under certain
19268 network conditions could lead to a busy-loop, with 100% CPU
19269 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
19271 o Major bugfixes (asserts, crashes, leaks):
19272 - Prevent the get_freelists() function from running off the end of
19273 the list of freelists if it somehow gets an unrecognized
19274 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
19276 - Avoid a memory leak where we would leak a consensus body when we
19277 find that a consensus which we couldn't previously verify due to
19278 missing certificates is now verifiable. Fixes bug 8719; bugfix
19280 - If we are unable to save a microdescriptor to the journal, do not
19281 drop it from memory and then reattempt downloading it. Fixes bug
19282 9645; bugfix on 0.2.2.6-alpha.
19283 - Fix an assertion failure that would occur when disabling the
19284 ORPort setting on a running Tor process while accounting was
19285 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
19286 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
19287 when an exit connection with optimistic data succeeds immediately
19288 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
19290 - Fix a memory leak that would occur whenever a configuration
19291 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
19293 o Major bugfixes (relay rate limiting):
19294 - When a TLS write is partially successful but incomplete, remember
19295 that the flushed part has been flushed, and notice that bytes were
19296 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
19297 bugfix on Tor 0.1.0.5-rc.
19298 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
19299 to 1GB/1GB. The previous defaults were intended to be "basically
19300 infinite", but it turns out they're now limiting our 100mbit+
19301 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
19302 last time we raised it).
19303 - No longer stop reading or writing on cpuworker connections when
19304 our rate limiting buckets go empty. Now we should handle circuit
19305 handshake requests more promptly. Resolves bug 9731.
19307 o Major bugfixes (client-side privacy):
19308 - When we mark a circuit as unusable for new circuits, have it
19309 continue to be unusable for new circuits even if MaxCircuitDirtiness
19310 is increased too much at the wrong time, or the system clock jumps
19311 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
19312 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
19313 which have resolved to internal addresses") is set, apply that
19314 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
19315 - When an exit relay rejects a stream with reason "exit policy", but
19316 we only know an exit policy summary (e.g. from the microdesc
19317 consensus) for it, do not mark the relay as useless for all exiting.
19318 Instead, mark just the circuit as unsuitable for that particular
19319 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
19321 o Major bugfixes (stream isolation):
19322 - Allow applications to get proper stream isolation with
19323 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
19324 username/password authentication also offer "no authentication". Tor
19325 had previously preferred "no authentication", so the applications
19326 never actually sent Tor their auth details. Now Tor selects
19327 username/password authentication if it's offered. You can disable
19328 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
19329 bug 8117; bugfix on 0.2.3.3-alpha.
19330 - Follow the socks5 protocol when offering username/password
19331 authentication. The fix for bug 8117 exposed this bug, and it
19332 turns out real-world applications like Pidgin do care. Bugfix on
19333 0.2.3.2-alpha; fixes bug 8879.
19335 o Major bugfixes (client circuit building):
19336 - Alter circuit build timeout measurement to start at the point
19337 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
19338 initialization). This should make our timeout measurements more
19339 uniform. Previously, we were sometimes including ORconn setup time
19340 in our circuit build time measurements. Should resolve bug 3443.
19341 - If the circuit build timeout logic is disabled (via the consensus,
19342 or because we are an authority), then don't build testing circuits.
19343 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
19345 o Major bugfixes (client-side DNS):
19346 - Turn off the client-side DNS cache by default. Updating and using
19347 the DNS cache is now configurable on a per-client-port
19348 level. SOCKSPort, DNSPort, etc lines may now contain
19349 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
19350 cache these types of DNS answers when we receive them from an
19351 exit node in response to an application request on this port, and
19352 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
19353 cached DNS answers of these types, we shouldn't use them. It's
19354 potentially risky to use cached DNS answers at the client, since
19355 doing so can indicate to one exit what answers we've gotten
19356 for DNS lookups in the past. With IPv6, this becomes especially
19357 problematic. Using cached DNS answers for requests on the same
19358 circuit would present less linkability risk, since all traffic
19359 on a circuit is already linkable, but it would also provide
19360 little performance benefit: the exit node caches DNS replies
19361 too. Implements a simplified version of Proposal 205. Implements
19364 o Major bugfixes (hidden service privacy):
19365 - Limit hidden service descriptors to at most ten introduction
19366 points, to slow one kind of guard enumeration. Fixes bug 9002;
19367 bugfix on 0.1.1.11-alpha.
19369 o Major bugfixes (directory fetching):
19370 - If the time to download the next old-style networkstatus is in
19371 the future, do not decline to consider whether to download the
19372 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
19374 - We used to always request authority certificates by identity digest,
19375 meaning we'd get the newest one even when we wanted one with a
19376 different signing key. Then we would complain about being given
19377 a certificate we already had, and never get the one we really
19378 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
19379 resource to request the one we want. Fixes bug 5595; bugfix on
19382 o Major bugfixes (bridge reachability):
19383 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
19384 previously they did not, which prevented them from receiving
19385 successful connections from relays for self-test or bandwidth
19386 testing. Also, when a relay is extending a circuit to a bridge,
19387 it needs to send a NETINFO cell, even when the bridge hasn't sent
19388 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
19390 o Major bugfixes (control interface):
19391 - When receiving a new configuration file via the control port's
19392 LOADCONF command, do not treat the defaults file as absent.
19393 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
19395 o Major bugfixes (directory authorities):
19396 - Stop marking every relay as having been down for one hour every
19397 time we restart a directory authority. These artificial downtimes
19398 were messing with our Stable and Guard flag calculations. Fixes
19399 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
19400 - When computing directory thresholds, ignore any rejected-as-sybil
19401 nodes during the computation so that they can't influence Fast,
19402 Guard, etc. (We should have done this for proposal 109.) Fixes
19404 - When marking a node as a likely sybil, reset its uptime metrics
19405 to zero, so that it cannot time towards getting marked as Guard,
19406 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
19408 - Fix a bug in the voting algorithm that could yield incorrect results
19409 when a non-naming authority declared too many flags. Fixes bug 9200;
19410 bugfix on 0.2.0.3-alpha.
19412 o Internal abstraction features:
19413 - Introduce new channel_t abstraction between circuits and
19414 or_connection_t to allow for implementing alternate OR-to-OR
19415 transports. A channel_t is an abstract object which can either be a
19416 cell-bearing channel, which is responsible for authenticating and
19417 handshaking with the remote OR and transmitting cells to and from
19418 it, or a listening channel, which spawns new cell-bearing channels
19419 at the request of remote ORs. Implements part of ticket 6465.
19420 - Make a channel_tls_t subclass of channel_t, adapting it to the
19421 existing or_connection_t code. The V2/V3 protocol handshaking
19422 code which formerly resided in command.c has been moved below the
19423 channel_t abstraction layer and may be found in channeltls.c now.
19424 Implements the rest of ticket 6465.
19425 - Introduce new circuitmux_t storing the queue of circuits for
19426 a channel; this encapsulates and abstracts the queue logic and
19427 circuit selection policy, and allows the latter to be overridden
19428 easily by switching out a policy object. The existing EWMA behavior
19429 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
19431 o New build requirements:
19432 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
19433 strongly recommended.
19434 - Tor maintainers now require Automake version 1.9 or later to build
19435 Tor from the Git repository. (Automake is not required when building
19436 from a source distribution.)
19438 o Minor features (protocol):
19439 - No longer include the "opt" prefix when generating routerinfos
19440 or v2 directories: it has been needless since Tor 0.1.2. Closes
19442 - Reject EXTEND cells sent to nonexistent streams. According to the
19443 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
19444 we were only checking for stream IDs that were currently in use.
19445 Found while hunting for more instances of bug 6271. Bugfix on
19446 0.0.2pre8, which introduced incremental circuit construction.
19447 - Tor relays and clients now support a better CREATE/EXTEND cell
19448 format, allowing the sender to specify multiple address, identity,
19449 and handshake types. Implements Robert Ransom's proposal 200;
19450 closes ticket 7199.
19451 - Reject as invalid most directory objects containing a NUL.
19452 Belt-and-suspender fix for bug 8037.
19454 o Minor features (security):
19455 - Clear keys and key-derived material left on the stack in
19456 rendservice.c and rendclient.c. Check return value of
19457 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
19458 These fixes should make us more forward-secure against cold-boot
19459 attacks and the like. Fixes bug 2385.
19460 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
19461 Irix's random() only return 15 bits; Solaris's random() returns more
19462 bits but its RAND_MAX says it only returns 15, and so on. Motivated
19463 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
19465 o Minor features (control protocol):
19466 - Add a "GETINFO signal/names" control port command. Implements
19468 - Provide default values for all options via "GETINFO config/defaults".
19469 Implements ticket 4971.
19470 - Allow an optional $ before the node identity digest in the
19471 controller command GETINFO ns/id/<identity>, for consistency with
19472 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
19473 - Add CACHED keyword to ADDRMAP events in the control protocol
19474 to indicate whether a DNS result will be cached or not. Resolves
19476 - Generate bootstrapping status update events correctly when fetching
19477 microdescriptors. Fixes bug 9927.
19479 o Minor features (path selection):
19480 - When deciding whether we have enough descriptors to build circuits,
19481 instead of looking at raw relay counts, look at which fraction
19482 of (bandwidth-weighted) paths we're able to build. This approach
19483 keeps clients from building circuits if their paths are likely to
19484 stand out statistically. The default fraction of paths needed is
19485 taken from the consensus directory; you can override it with the
19486 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
19487 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
19488 and we have GeoIP information, also exclude all nodes with unknown
19489 countries "??" and "A1". This behavior is controlled by the
19490 new GeoIPExcludeUnknown option: you can make such nodes always
19491 excluded with "GeoIPExcludeUnknown 1", and disable the feature
19492 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
19493 gets you the default behavior. Implements feature 7706.
19495 o Minor features (hidden services):
19496 - Improve circuit build timeout handling for hidden services.
19497 In particular: adjust build timeouts more accurately depending
19498 upon the number of hop-RTTs that a particular circuit type
19499 undergoes. Additionally, launch intro circuits in parallel
19500 if they timeout, and take the first one to reply as valid.
19501 - The Tor client now ignores sub-domain components of a .onion
19502 address. This change makes HTTP "virtual" hosting
19503 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
19504 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
19505 hosted on the same hidden service. Implements proposal 204.
19506 - Enable Tor to read configuration, state, and key information from
19507 a FIFO. Previously Tor would only read from files with a positive
19508 stat.st_size. Code from meejah; fixes bug 6044.
19510 o Minor features (clients):
19511 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
19512 microdescriptor-related dir requests, and only fall back to normal
19513 descriptors if none of their bridges can handle microdescriptors
19514 (as opposed to the fix in ticket 4013, which caused them to fall
19515 back to normal descriptors if *any* of their bridges preferred
19516 them). Resolves ticket 4994.
19517 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
19518 TCP ports to forward. In the past it only accepted two ports:
19519 the ORPort and the DirPort.
19521 o Minor features (protecting client timestamps):
19522 - Clients no longer send timestamps in their NETINFO cells. These were
19523 not used for anything, and they provided one small way for clients
19524 to be distinguished from each other as they moved from network to
19525 network or behind NAT. Implements part of proposal 222.
19526 - Clients now round timestamps in INTRODUCE cells down to the nearest
19527 10 minutes. If a new Support022HiddenServices option is set to 0, or
19528 if it's set to "auto" and the feature is disabled in the consensus,
19529 the timestamp is sent as 0 instead. Implements part of proposal 222.
19530 - Stop sending timestamps in AUTHENTICATE cells. This is not such
19531 a big deal from a security point of view, but it achieves no actual
19532 good purpose, and isn't needed. Implements part of proposal 222.
19533 - Reduce down accuracy of timestamps in hidden service descriptors.
19534 Implements part of proposal 222.
19536 o Minor features (bridges):
19537 - Make bridge relays check once a minute for whether their IP
19538 address has changed, rather than only every 15 minutes. Resolves
19539 bugs 1913 and 1992.
19540 - Bridge statistics now count bridge clients connecting over IPv6:
19541 bridge statistics files now list "bridge-ip-versions" and
19542 extra-info documents list "geoip6-db-digest". The control protocol
19543 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
19544 implementation by "shkoo", addressing ticket 5055.
19545 - Add a new torrc option "ServerTransportListenAddr" to let bridge
19546 operators select the address where their pluggable transports will
19547 listen for connections. Resolves ticket 7013.
19548 - Randomize the lifetime of our SSL link certificate, so censors can't
19549 use the static value for filtering Tor flows. Resolves ticket 8443;
19550 related to ticket 4014 which was included in 0.2.2.33.
19552 o Minor features (relays):
19553 - Option OutboundBindAddress can be specified multiple times and
19554 accepts IPv6 addresses. Resolves ticket 6876.
19556 o Minor features (IPv6, client side):
19557 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
19558 prefer to hand out virtual IPv6 addresses, since there are more of
19559 them and we can't run out. To override this behavior and make IPv4
19560 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
19561 or DNSPort you're using for resolving. Implements ticket 7571.
19562 - AutomapHostsOnResolve responses are now randomized, to avoid
19563 annoying situations where Tor is restarted and applications
19564 connect to the wrong addresses.
19565 - Never try more than 1000 times to pick a new virtual address when
19566 AutomapHostsOnResolve is set. That's good enough so long as we
19567 aren't close to handing out our entire virtual address space;
19568 if you're getting there, it's best to switch to IPv6 virtual
19571 o Minor features (IPv6, relay/authority side):
19572 - New config option "AuthDirHasIPv6Connectivity 1" that directory
19573 authorities should set if they have IPv6 connectivity and want to
19574 do reachability tests for IPv6 relays. Implements feature 5974.
19575 - A relay with an IPv6 OR port now sends that address in NETINFO
19576 cells (in addition to its other address). Implements ticket 6364.
19578 o Minor features (directory authorities):
19579 - Directory authorities no long accept descriptors for any version of
19580 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
19581 These versions are insecure, unsupported, or both. Implements
19583 - When directory authorities are computing thresholds for flags,
19584 never let the threshold for the Fast flag fall below 4096
19585 bytes. Also, do not consider nodes with extremely low bandwidths
19586 when deciding thresholds for various directory flags. This change
19587 should raise our threshold for Fast relays, possibly in turn
19588 improving overall network performance; see ticket 1854. Resolves
19590 - Directory authorities now include inside each vote a statement of
19591 the performance thresholds they used when assigning flags.
19592 Implements ticket 8151.
19593 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
19594 in directory authority votes to describe whether they have enough
19595 measured bandwidths to ignore advertised (relay descriptor)
19596 bandwidth claims. Resolves ticket 8711.
19598 o Minor features (path bias detection):
19599 - Path Use Bias: Perform separate accounting for successful circuit
19600 use. Keep separate statistics on stream attempt rates versus stream
19601 success rates for each guard. Provide configurable thresholds to
19602 determine when to emit log messages or disable use of guards that
19603 fail too many stream attempts. Resolves ticket 7802.
19604 - Create three levels of Path Bias log messages, as opposed to just
19605 two. These are configurable via consensus as well as via the torrc
19606 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
19607 The default values are 0.70, 0.50, and 0.30 respectively.
19608 - Separate the log message levels from the decision to drop guards,
19609 which also is available via torrc option PathBiasDropGuards.
19610 PathBiasDropGuards still defaults to 0 (off).
19611 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
19612 in combination with PathBiasExtremeRate.
19613 - Increase the default values for PathBiasScaleThreshold and
19614 PathBiasCircThreshold from (200, 20) to (300, 150).
19615 - Add in circuit usage accounting to path bias. If we try to use a
19616 built circuit but fail for any reason, it counts as path bias.
19617 Certain classes of circuits where the adversary gets to pick your
19618 destination node are exempt from this accounting. Usage accounting
19619 can be specifically disabled via consensus parameter or torrc.
19620 - Convert all internal path bias state to double-precision floating
19621 point, to avoid roundoff error and other issues.
19622 - Only record path bias information for circuits that have completed
19623 *two* hops. Assuming end-to-end tagging is the attack vector, this
19624 makes us more resilient to ambient circuit failure without any
19625 detection capability loss.
19627 o Minor features (build):
19628 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
19629 dhill. Resolves ticket 6982.
19630 - Compile on win64 using mingw64. Fixes bug 7260; patches from
19632 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
19633 separate error codes; or at least, don't break for that reason.
19634 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
19636 o Build improvements (autotools):
19637 - Warn if building on a platform with an unsigned time_t: there
19638 are too many places where Tor currently assumes that time_t can
19639 hold negative values. We'd like to fix them all, but probably
19641 - Do not report status verbosely from autogen.sh unless the -v flag
19642 is specified. Fixes issue 4664. Patch from Onizuka.
19643 - Detect and reject attempts to build Tor with threading support
19644 when OpenSSL has been compiled without threading support.
19646 - Try to detect if we are ever building on a platform where
19647 memset(...,0,...) does not set the value of a double to 0.0. Such
19648 platforms are permitted by the C standard, though in practice
19649 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
19650 currently support them, but it's better to detect them and fail
19651 than to perform erroneously.
19652 - We no longer warn so much when generating manpages from their
19654 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
19655 the signs of types during autoconf. This is better than our old
19656 approach, which didn't work when cross-compiling.
19658 o Minor features (log messages, warnings):
19659 - Detect when we're running with a version of OpenSSL other than the
19660 one we compiled with. This conflict has occasionally given people
19661 hard-to-track-down errors.
19662 - Warn users who run hidden services on a Tor client with
19663 UseEntryGuards disabled that their hidden services will be
19664 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
19665 attack which motivated Tor to support entry guards in the first
19666 place). Resolves ticket 6889.
19667 - Warn when we are binding low ports when hibernation is enabled;
19668 previously we had warned when we were _advertising_ low ports with
19669 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
19670 - Issue a warning when running with the bufferevents backend enabled.
19671 It's still not stable, and people should know that they're likely
19672 to hit unexpected problems. Closes ticket 9147.
19674 o Minor features (log messages, notices):
19675 - Refactor resolve_my_address() so it returns the method by which we
19676 decided our public IP address (explicitly configured, resolved from
19677 explicit hostname, guessed from interfaces, learned by gethostname).
19678 Now we can provide more helpful log messages when a relay guesses
19679 its IP address incorrectly (e.g. due to unexpected lines in
19680 /etc/hosts). Resolves ticket 2267.
19681 - Track how many "TAP" and "NTor" circuit handshake requests we get,
19682 and how many we complete, and log it every hour to help relay
19683 operators follow trends in network load. Addresses ticket 9658.
19685 o Minor features (log messages, diagnostics):
19686 - If we fail to free a microdescriptor because of bug 7164, log
19687 the filename and line number from which we tried to free it.
19688 - We compute the overhead from passing onionskins back and forth to
19689 cpuworkers, and report it when dumping statistics in response to
19690 SIGUSR1. Supports ticket 7291.
19691 - Add another diagnostic to the heartbeat message: track and log
19692 overhead that TLS is adding to the data we write. If this is
19693 high, we are sending too little data to SSL_write at a time.
19694 Diagnostic for bug 7707.
19695 - Log packaged cell fullness as part of the heartbeat message.
19696 Diagnosis to try to determine the extent of bug 7743.
19697 - Add more detail to a log message about relaxed timeouts, to help
19699 - When learning a fingerprint for a bridge, log its corresponding
19700 transport type. Implements ticket 7896.
19701 - Warn more aggressively when flushing microdescriptors to a
19702 microdescriptor cache fails, in an attempt to mitigate bug 8031,
19703 or at least make it more diagnosable.
19704 - Improve the log message when "Bug/attack: unexpected sendme cell
19705 from client" occurs, to help us track bug 8093.
19706 - Improve debugging output to help track down bug 8185 ("Bug:
19707 outgoing relay cell has n_chan==NULL. Dropping.")
19709 o Minor features (log messages, quieter bootstrapping):
19710 - Log fewer lines at level "notice" about our OpenSSL and Libevent
19711 versions and capabilities when everything is going right. Resolves
19712 part of ticket 6736.
19713 - Omit the first heartbeat log message, because it never has anything
19714 useful to say, and it clutters up the bootstrapping messages.
19715 Resolves ticket 6758.
19716 - Don't log about reloading the microdescriptor cache at startup. Our
19717 bootstrap warnings are supposed to tell the user when there's a
19718 problem, and our bootstrap notices say when there isn't. Resolves
19719 ticket 6759; bugfix on 0.2.2.6-alpha.
19720 - Don't log "I learned some more directory information" when we're
19721 reading cached directory information. Reserve it for when new
19722 directory information arrives in response to a fetch. Resolves
19724 - Don't complain about bootstrapping problems while hibernating.
19725 These complaints reflect a general code problem, but not one
19726 with any problematic effects (no connections are actually
19727 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
19729 o Minor features (testing):
19730 - In our testsuite, create temporary directories with a bit more
19731 entropy in their name to make name collisions less likely. Fixes
19733 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
19734 (P-256) Diffie-Hellman handshakes to src/or/bench.
19735 - Add benchmark functions to test onion handshake performance.
19738 - The DirServer option is now DirAuthority, for consistency with
19739 current naming patterns. You can still use the old DirServer form.
19741 o Minor bugfixes (protocol):
19742 - Fix the handling of a TRUNCATE cell when it arrives while the
19743 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
19744 - When a Tor client gets a "truncated" relay cell, the first byte of
19745 its payload specifies why the circuit was truncated. We were
19746 ignoring this 'reason' byte when tearing down the circuit, resulting
19747 in the controller not being told why the circuit closed. Now we
19748 pass the reason from the truncated cell to the controller. Bugfix
19749 on 0.1.2.3-alpha; fixes bug 7039.
19750 - Fix a misframing issue when reading the version numbers in a
19751 VERSIONS cell. Previously we would recognize [00 01 00 02] as
19752 'version 1, version 2, and version 0x100', when it should have
19753 only included versions 1 and 2. Fixes bug 8059; bugfix on
19754 0.2.0.10-alpha. Reported pseudonymously.
19755 - Make the format and order of STREAM events for DNS lookups
19756 consistent among the various ways to launch DNS lookups. Fixes
19757 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
19759 o Minor bugfixes (syscalls and disk interaction):
19760 - Always check the return values of functions fcntl() and
19761 setsockopt(). We don't believe these are ever actually failing in
19762 practice, but better safe than sorry. Also, checking these return
19763 values should please analysis tools like Coverity. Patch from
19764 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
19765 - Avoid double-closing the listener socket in our socketpair()
19766 replacement (used on Windows) in the case where the addresses on
19767 our opened sockets don't match what we expected. Fixes bug 9400;
19768 bugfix on 0.0.2pre7. Found by Coverity.
19769 - Correctly store microdescriptors and extrainfo descriptors that
19770 include an internal NUL byte. Fixes bug 8037; bugfix on
19771 0.2.0.1-alpha. Bug reported by "cypherpunks".
19772 - If for some reason we fail to write a microdescriptor while
19773 rebuilding the cache, do not let the annotations from that
19774 microdescriptor linger in the cache file, and do not let the
19775 microdescriptor stay recorded as present in its old location.
19776 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
19777 - Use direct writes rather than stdio when building microdescriptor
19778 caches, in an attempt to mitigate bug 8031, or at least make it
19781 o Minor fixes (config options):
19782 - Warn and fail if a server is configured not to advertise any
19783 ORPorts at all. (We need *something* to put in our descriptor,
19784 or we just won't work.)
19785 - Behave correctly when the user disables LearnCircuitBuildTimeout
19786 but doesn't tell us what they would like the timeout to be. Fixes
19787 bug 6304; bugfix on 0.2.2.14-alpha.
19788 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
19789 to start with a triple-underscore so the controller won't touch it.
19790 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
19791 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
19792 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
19793 - When autodetecting the number of CPUs, use the number of available
19794 CPUs in preference to the number of configured CPUs. Inform the
19795 user if this reduces the number of available CPUs. Fixes bug 8002;
19796 bugfix on 0.2.3.1-alpha.
19797 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
19798 - Make it an error when you set EntryNodes but disable UseGuardNodes,
19799 since it will (surprisingly to some users) ignore EntryNodes. Fixes
19800 bug 8180; bugfix on 0.2.3.11-alpha.
19801 - Avoid overflows when the user sets MaxCircuitDirtiness to a
19802 ridiculously high value, by imposing a (ridiculously high) 30-day
19803 maximum on MaxCircuitDirtiness.
19805 o Minor bugfixes (control protocol):
19806 - Stop sending a stray "(null)" in some cases for the server status
19807 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
19809 - The ADDRMAP command can no longer generate an ill-formed error
19810 code on a failed MAPADDRESS. It now says "internal" rather than
19811 an English sentence fragment with spaces in the middle. Bugfix on
19812 Tor 0.2.0.19-alpha.
19814 o Minor bugfixes (clients / edges):
19815 - When we receive a RELAY_END cell with the reason DONE, or with no
19816 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
19817 status as "connection refused". Previously we reported these cases
19818 as success but then immediately closed the connection. Fixes bug
19819 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
19820 - If the guard we choose first doesn't answer, we would try the
19821 second guard, but once we connected to the second guard we would
19822 abandon it and retry the first one, slowing down bootstrapping.
19823 The fix is to treat all our initially chosen guards as acceptable
19824 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
19825 - When choosing which stream on a formerly stalled circuit to wake
19826 first, make better use of the platform's weak RNG. Previously,
19827 we had been using the % ("modulo") operator to try to generate a
19828 1/N chance of picking each stream, but this behaves badly with
19829 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
19832 o Minor bugfixes (path bias detection):
19833 - If the state file's path bias counts are invalid (presumably from a
19834 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
19835 additional checks and log messages to the scaling of Path Bias
19836 counts, in case there still are remaining issues with scaling.
19837 Should help resolve bug 8235.
19838 - Prevent rounding error in path bias counts when scaling
19839 them down, and use the correct scale factor default. Also demote
19840 some path bias related log messages down a level and make others
19841 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
19842 - Remove a source of rounding error during path bias count scaling;
19843 don't count cannibalized circuits as used for path bias until we
19844 actually try to use them; and fix a circuit_package_relay_cell()
19845 warning message about n_chan==NULL. Fixes bug 7802.
19846 - Paste the description for PathBias parameters from the man
19847 page into or.h, so the code documents them too. Fixes bug 7982;
19848 bugfix on 0.2.3.17-beta.
19850 o Minor bugfixes (relays):
19851 - Stop trying to resolve our hostname so often (e.g. every time we
19852 think about doing a directory fetch). Now we reuse the cached
19853 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
19854 and 2410 (bugfix on 0.1.2.2-alpha).
19855 - When examining the list of network interfaces to find our address,
19856 do not consider non-running or disabled network interfaces. Fixes
19857 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
19859 o Minor bugfixes (blocking resistance):
19860 - Only disable TLS session ticket support when running as a TLS
19861 server. Now clients will blend better with regular Firefox
19862 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
19864 o Minor bugfixes (IPv6):
19865 - Use square brackets around IPv6 addresses in numerous places
19866 that needed them, including log messages, HTTPS CONNECT proxy
19867 requests, TransportProxy statefile entries, and pluggable transport
19868 extra-info lines. Fixes bug 7011; patch by David Fifield.
19870 o Minor bugfixes (directory authorities):
19871 - Reject consensus votes with more than 64 known-flags. We aren't even
19872 close to that limit yet, and our code doesn't handle it correctly.
19873 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
19874 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
19875 bugfix on 0.2.0.3-alpha.
19877 o Minor bugfixes (memory leaks):
19878 - Avoid leaking memory if we fail to compute a consensus signature
19879 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
19880 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
19881 on 0.2.1.1-alpha; fixes bug 7816.
19882 - Fix a memory leak during safe-cookie controller authentication.
19883 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
19884 - Free some more still-in-use memory at exit, to make hunting for
19885 memory leaks easier. Resolves bug 7029.
19887 o Minor bugfixes (code correctness):
19888 - Increase the width of the field used to remember a connection's
19889 link protocol version to two bytes. Harmless for now, since the
19890 only currently recognized versions are one byte long. Reported
19891 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
19892 - Fix a crash when debugging unit tests on Windows: deallocate a
19893 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
19894 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
19895 - When detecting the largest possible file descriptor (in order to
19896 close all file descriptors when launching a new program), actually
19897 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
19898 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
19900 - Avoid a crash if we fail to generate an extrainfo descriptor.
19901 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
19902 this is CID 718634.
19903 - Avoid an off-by-one error when checking buffer boundaries when
19904 formatting the exit status of a pluggable transport helper.
19905 This is probably not an exploitable bug, but better safe than
19906 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
19908 - Get rid of a couple of harmless clang warnings, where we compared
19909 enums to ints. These warnings are newly introduced in clang 3.2.
19911 o Minor bugfixes (code cleanliness):
19912 - Avoid use of reserved identifiers in our C code. The C standard
19913 doesn't like us declaring anything that starts with an
19914 underscore, so let's knock it off before we get in trouble. Fix
19915 for bug 1031; bugfix on the first Tor commit.
19916 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
19917 with large values. This situation was untriggered, but nevertheless
19918 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
19919 - Fix an impossible buffer overrun in the AES unit tests. Fixes
19920 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
19921 - Fix handling of rendezvous client authorization types over 8.
19922 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
19923 - Remove a couple of extraneous semicolons that were upsetting the
19924 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
19925 bugfix on 0.2.2.1-alpha.
19926 - When complaining about a client port on a public address, log
19927 which address we're complaining about. Fixes bug 4020; bugfix on
19928 0.2.3.3-alpha. Patch by Tom Fitzhenry.
19930 o Minor bugfixes (log messages, warnings):
19931 - If we encounter a write failure on a SOCKS connection before we
19932 finish our SOCKS handshake, don't warn that we closed the
19933 connection before we could send a SOCKS reply. Fixes bug 8427;
19934 bugfix on 0.1.0.1-rc.
19935 - Fix a directory authority warn caused when we have a large amount
19936 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
19937 - Downgrade "Failed to hand off onionskin" messages to "debug"
19938 severity, since they're typically redundant with the "Your computer
19939 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
19940 - Avoid spurious warnings when configuring multiple client ports of
19941 which only some are nonlocal. Previously, we had claimed that some
19942 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
19945 o Minor bugfixes (log messages, other):
19946 - Fix log messages and comments to avoid saying "GMT" when we mean
19947 "UTC". Fixes bug 6113.
19948 - When rejecting a configuration because we were unable to parse a
19949 quoted string, log an actual error message. Fixes bug 7950; bugfix
19951 - Correctly recognize that [::1] is a loopback address. Fixes
19952 bug 8377; bugfix on 0.2.1.3-alpha.
19953 - Don't log inappropriate heartbeat messages when hibernating: a
19954 hibernating node is _expected_ to drop out of the consensus,
19955 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
19956 bugfix on 0.2.3.1-alpha.
19957 - Eliminate several instances where we use "Nickname=ID" to refer to
19958 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
19959 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
19962 o Minor bugfixes (build):
19963 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
19964 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
19965 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
19967 o Documentation fixes:
19968 - Make the torify manpage no longer refer to tsocks; torify hasn't
19969 supported tsocks since 0.2.3.14-alpha.
19970 - Make the tor manpage no longer reference tsocks.
19971 - Fix the GeoIPExcludeUnknown documentation to refer to
19972 ExcludeExitNodes rather than the currently nonexistent
19973 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
19974 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
19976 - Say "KBytes" rather than "KB" in the man page (for various values
19977 of K), to further reduce confusion about whether Tor counts in
19978 units of memory or fractions of units of memory. Resolves ticket 7054.
19979 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
19980 names match. Fixes bug 7768.
19981 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
19982 message is logged at notice, not at info.
19983 - Clarify the usage and risks of setting the ContactInfo torrc line
19984 for your relay or bridge. Resolves ticket 9854.
19985 - Add anchors to the manpage so we can link to the html version of
19986 the documentation for specific options. Resolves ticket 9866.
19987 - Replace remaining references to DirServer in man page and
19988 log entries. Resolves ticket 10124.
19990 o Removed features:
19991 - Stop exporting estimates of v2 and v3 directory traffic shares
19992 in extrainfo documents. They were unneeded and sometimes inaccurate.
19993 Also stop exporting any v2 directory request statistics. Resolves
19995 - Drop support for detecting and warning about versions of Libevent
19996 before 1.3e. Nothing reasonable ships with them any longer; warning
19997 the user about them shouldn't be needed. Resolves ticket 6826.
19998 - Now that all versions before 0.2.2.x are disallowed, we no longer
19999 need to work around their missing features. Remove a bunch of
20000 compatibility code.
20003 - The tor-tsocks.conf is no longer distributed or installed. We
20004 recommend that tsocks users use torsocks instead. Resolves
20006 - Remove some of the older contents of doc/ as obsolete; move others
20007 to torspec.git. Fixes bug 8965.
20009 o Code simplification:
20010 - Avoid using character buffers when constructing most directory
20011 objects: this approach was unwieldy and error-prone. Instead,
20012 build smartlists of strings, and concatenate them when done.
20013 - Rename "isin" functions to "contains", for grammar. Resolves
20015 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
20016 with the natural logarithm function from the system libm. Resolves
20018 - Start using OpenBSD's implementation of queue.h, so that we don't
20019 need to hand-roll our own pointer and list structures whenever we
20020 need them. (We can't rely on a sys/queue.h, since some operating
20021 systems don't have them, and the ones that do have them don't all
20022 present the same extensions.)
20023 - Start using OpenBSD's implementation of queue.h (originally by
20025 - Enhance our internal sscanf replacement so that we can eliminate
20026 the last remaining uses of the system sscanf. (Though those uses
20027 of sscanf were safe, sscanf itself is generally error prone, so
20028 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
20030 - Replace all calls to snprintf() outside of src/ext with
20031 tor_snprintf(). Also remove the #define to replace snprintf with
20032 _snprintf on Windows; they have different semantics, and all of
20033 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
20036 - Add a wrapper function for the common "log a message with a
20038 - Split the onion.c file into separate modules for the onion queue
20039 and the different handshakes it supports.
20040 - Move the client-side address-map/virtual-address/DNS-cache code
20041 out of connection_edge.c into a new addressmap.c module.
20042 - Move the entry node code from circuitbuild.c to its own file.
20043 - Move the circuit build timeout tracking code from circuitbuild.c
20045 - Source files taken from other packages now reside in src/ext;
20046 previously they were scattered around the rest of Tor.
20047 - Move the generic "config" code into a new file, and have "config.c"
20048 hold only torrc- and state-related code. Resolves ticket 6823.
20049 - Move the core of our "choose a weighted element at random" logic
20050 into its own function, and give it unit tests. Now the logic is
20051 testable, and a little less fragile too.
20052 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
20053 - Move last_reachable and testing_since from routerinfo_t to node_t.
20054 Implements ticket 5529.
20055 - Add replaycache_t structure, functions and unit tests, then refactor
20056 rend_service_introduce() to be more clear to read, improve, debug,
20057 and test. Resolves bug 6177.
20060 - Remove some now-needless code that tried to aggressively flush
20061 OR connections as data was added to them. Since 0.2.0.1-alpha, our
20062 cell queue logic has saved us from the failure mode that this code
20063 was supposed to prevent. Removing this code will limit the number
20064 of baroque control flow paths through Tor's network logic. Reported
20065 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
20066 - Remove unused code for parsing v1 directories and "running routers"
20067 documents. Fixes bug 6887.
20068 - Remove the marshalling/unmarshalling code for sending requests to
20069 cpuworkers over a socket, and instead just send structs. The
20070 recipient will always be the same Tor binary as the sender, so
20071 any encoding is overkill.
20072 - Remove the testing_since field of node_t, which hasn't been used
20073 for anything since 0.2.0.9-alpha.
20074 - Finally remove support for malloc_good_size and malloc_usable_size.
20075 We had hoped that these functions would let us eke a little more
20076 memory out of our malloc implementation. Unfortunately, the only
20077 implementations that provided these functions are also ones that
20078 are already efficient about not overallocation: they never got us
20079 more than 7 or so bytes per allocation. Removing them saves us a
20080 little code complexity and a nontrivial amount of build complexity.
20083 Changes in version 0.2.3.25 - 2012-11-19
20084 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
20085 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
20086 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
20087 programmer, and friend. Unstinting in his dedication to the cause of
20088 freedom, he inspired and helped many of us as we began our work on
20089 anonymity, and inspires us still. Please honor his memory by writing
20090 software to protect people's freedoms, and by helping others to do so.
20092 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
20093 significantly reduced directory overhead (via microdescriptors),
20094 enormous crypto performance improvements for fast relays on new
20095 enough hardware, a new v3 TLS handshake protocol that can better
20096 resist fingerprinting, support for protocol obfuscation plugins (aka
20097 pluggable transports), better scalability for hidden services, IPv6
20098 support for bridges, performance improvements like allowing clients
20099 to skip the first round-trip on the circuit ("optimistic data") and
20100 refilling token buckets more often, a new "stream isolation" design
20101 to isolate different applications on different circuits, and many
20102 stability, security, and privacy fixes.
20104 Major features (v3 directory protocol):
20105 - Clients now use microdescriptors instead of regular descriptors
20106 to build circuits. Microdescriptors are authority-generated
20107 summaries of regular descriptors' contents, designed to change very
20108 rarely (see proposal 158 for details). This feature is designed
20109 to save bandwidth, especially for clients on slow internet
20110 connections. Use "UseMicrodescriptors 0" to disable it.
20111 - Caches now download, cache, and serve microdescriptors, as well
20112 as multiple "flavors" of the consensus, including a flavor that
20113 describes microdescriptors.
20115 o Major features (build hardening):
20116 - Enable gcc and ld hardening by default. Resolves ticket 5210.
20118 o Major features (relay scaling):
20119 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
20120 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
20121 vectorized AES implementations as appropriate. These can be much,
20122 much faster than other AES implementations.
20123 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
20124 implementation. It makes AES_CTR about 7% faster than our old one
20125 (which was about 10% faster than the one OpenSSL used to provide).
20126 Resolves ticket 4526.
20127 - Use OpenSSL's EVP interface for AES encryption, so that all AES
20128 operations can use hardware acceleration (if present). Resolves
20130 - Unconditionally use OpenSSL's AES implementation instead of our
20131 old built-in one. OpenSSL's AES has been better for a while, and
20132 relatively few servers should still be on any version of OpenSSL
20133 that doesn't have good optimized assembly AES.
20135 o Major features (blocking resistance):
20136 - Update TLS cipher list to match Firefox 8 and later. Resolves
20138 - Remove support for clients falsely claiming to support standard
20139 ciphersuites that they can actually provide. As of modern OpenSSL
20140 versions, it's not necessary to fake any standard ciphersuite,
20141 and doing so prevents us from using better ciphersuites in the
20142 future, since servers can't know whether an advertised ciphersuite
20143 is really supported or not. Some hosts -- notably, ones with very
20144 old versions of OpenSSL or where OpenSSL has been built with ECC
20145 disabled -- will stand out because of this change; TBB users should
20146 not be affected. Implements the client side of proposal 198.
20147 - Implement a new handshake protocol (v3) for authenticating Tors to
20148 each other over TLS. It should be more resistant to fingerprinting
20149 than previous protocols, and should require less TLS hacking for
20150 future Tor implementations. Implements proposal 176.
20151 - Allow variable-length padding cells, to disguise the length of
20152 Tor's TLS records. Implements part of proposal 184.
20153 - While we're trying to bootstrap, record how many TLS connections
20154 fail in each state, and report which states saw the most failures
20155 in response to any bootstrap failures. This feature may speed up
20156 diagnosis of censorship events. Implements ticket 3116.
20158 o Major features (pluggable transports):
20159 - Clients and bridges can now be configured to use a separate
20160 "transport" proxy. This approach makes the censorship arms race
20161 easier by allowing bridges to use protocol obfuscation plugins.
20162 Implements proposal 180 (tickets 2841 and 3472).
20164 o Major features (DoS resistance):
20165 - Now that Tor 0.2.0.x is completely deprecated, enable the final
20166 part of "Proposal 110: Avoiding infinite length circuits" by
20167 refusing all circuit-extend requests that do not use a relay_early
20168 cell. This change helps Tor resist a class of denial-of-service
20169 attacks by limiting the maximum circuit length.
20170 - Tear down the circuit if we get an unexpected SENDME cell. Clients
20171 could use this trick to make their circuits receive cells faster
20172 than our flow control would have allowed, or to gum up the network,
20173 or possibly to do targeted memory denial-of-service attacks on
20174 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
20175 from July 2002, before the release of Tor 0.0.0.
20177 o Major features (hidden services):
20178 - Adjust the number of introduction points that a hidden service
20179 will try to maintain based on how long its introduction points
20180 remain in use and how many introductions they handle. Fixes
20182 - Add a "tor2web mode" for clients that want to connect to hidden
20183 services non-anonymously (and possibly more quickly). As a safety
20184 measure to try to keep users from turning this on without knowing
20185 what they are doing, tor2web mode must be explicitly enabled at
20186 compile time, and a copy of Tor compiled to run in tor2web mode
20187 cannot be used as a normal Tor client. Implements feature 2553.
20189 o Major features (IPv6):
20190 - Clients can now connect to private bridges over IPv6. Bridges
20191 still need at least one IPv4 address in order to connect to
20192 other relays. Note that we don't yet handle the case where the
20193 user has two bridge lines for the same bridge (one IPv4, one
20194 IPv6). Implements parts of proposal 186.
20196 o Major features (directory authorities):
20197 - Use a more secure consensus parameter voting algorithm. Now at
20198 least three directory authorities or a majority of them must
20199 vote on a given parameter before it will be included in the
20200 consensus. Implements proposal 178.
20201 - Remove the artificially low cutoff of 20KB to guarantee the Fast
20202 flag. In the past few years the average relay speed has picked
20203 up, and while the "top 7/8 of the network get the Fast flag" and
20204 "all relays with 20KB or more of capacity get the Fast flag" rules
20205 used to have the same result, now the top 7/8 of the network has
20206 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
20208 o Major features (performance):
20209 - Exit nodes now accept and queue data on not-yet-connected streams.
20210 Previously, the client wasn't allowed to send data until the
20211 stream was connected, which slowed down all connections. This
20212 change will enable clients to perform a "fast-start" on streams
20213 and send data without having to wait for a confirmation that the
20214 stream has opened. Patch from Ian Goldberg; implements the server
20215 side of Proposal 174.
20216 - When using an exit relay running 0.2.3.x, clients can now
20217 "optimistically" send data before the exit relay reports that
20218 the stream has opened. This saves a round trip when starting
20219 connections where the client speaks first (such as web browsing).
20220 This behavior is controlled by a consensus parameter (currently
20221 disabled). To turn it on or off manually, use the "OptimisticData"
20222 torrc option. Implements proposal 181; code by Ian Goldberg.
20223 - Add a new TokenBucketRefillInterval option to refill token buckets
20224 more frequently than once per second. This should improve network
20225 performance, alleviate queueing problems, and make traffic less
20226 bursty. Implements proposal 183; closes ticket 3630. Design by
20227 Florian Tschorsch and Björn Scheuermann; implementation by
20229 - Raise the threshold of server descriptors needed (75%) and exit
20230 server descriptors needed (50%) before we will declare ourselves
20231 bootstrapped. This will make clients start building circuits a
20232 little later, but makes the initially constructed circuits less
20233 skewed and less in conflict with further directory fetches. Fixes
20236 o Major features (relays):
20237 - Relays now try regenerating and uploading their descriptor more
20238 frequently if they are not listed in the consensus, or if the
20239 version of their descriptor listed in the consensus is too
20240 old. This fix should prevent situations where a server declines
20241 to re-publish itself because it has done so too recently, even
20242 though the authorities decided not to list its recent-enough
20243 descriptor. Fix for bug 3327.
20245 o Major features (stream isolation):
20246 - You can now configure Tor so that streams from different
20247 applications are isolated on different circuits, to prevent an
20248 attacker who sees your streams as they leave an exit node from
20249 linking your sessions to one another. To do this, choose some way
20250 to distinguish the applications: have them connect to different
20251 SocksPorts, or have one of them use SOCKS4 while the other uses
20252 SOCKS5, or have them pass different authentication strings to the
20253 SOCKS proxy. Then, use the new SocksPort syntax to configure the
20254 degree of isolation you need. This implements Proposal 171.
20255 - There's a new syntax for specifying multiple client ports (such as
20256 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
20257 multiple *Port entries with full addr:port syntax on each.
20258 The old *ListenAddress format is still supported, but you can't
20259 mix it with the new *Port syntax.
20261 o Major features (bufferevents):
20262 - Tor can now optionally build with the "bufferevents" buffered IO
20263 backend provided by Libevent 2. To use this feature, make sure you
20264 have the latest possible version of Libevent, and pass the
20265 --enable-bufferevents flag to configure when building Tor from
20266 source. This feature will make our networking code more flexible,
20267 let us stack layers on each other, and let us use more efficient
20268 zero-copy transports where available.
20269 - Add experimental support for running on Windows with IOCP and no
20270 kernel-space socket buffers. This feature is controlled by a new
20271 "UserspaceIOCPBuffers" config option (off by default), which has
20272 no effect unless Tor has been built with bufferevents enabled,
20273 you're running on Windows, and you've set "DisableIOCP 0". In the
20274 long run, this may help solve or mitigate bug 98.
20276 o Major features (path selection):
20277 - The EntryNodes option can now include country codes like {de} or IP
20278 addresses or network masks. Previously we had disallowed these
20279 options because we didn't have an efficient way to keep the list up
20280 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
20283 o Major features (port forwarding):
20284 - Add support for automatic port mapping on the many home routers
20285 that support NAT-PMP or UPnP. To build the support code, you'll
20286 need to have the libnatpnp library and/or the libminiupnpc library,
20287 and you'll need to enable the feature specifically by passing
20288 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
20289 it on, use the new PortForwarding option.
20291 o Major features (logging):
20292 - Add a new 'Heartbeat' log message type to periodically log a message
20293 describing Tor's status at level Notice. This feature is meant for
20294 operators who log at notice, and want to make sure that their Tor
20295 server is still working. Implementation by George Kadianakis.
20296 - Make logging resolution configurable with a new LogTimeGranularity
20297 option, and change the default from 1 millisecond to 1 second.
20298 Implements enhancement 1668.
20300 o Major features (other):
20301 - New "DisableNetwork" config option to prevent Tor from launching any
20302 connections or accepting any connections except on a control port.
20303 Bundles and controllers can set this option before letting Tor talk
20304 to the rest of the network, for example to prevent any connections
20305 to a non-bridge address. Packages like Orbot can also use this
20306 option to instruct Tor to save power when the network is off.
20307 - Try to use system facilities for enumerating local interface
20308 addresses, before falling back to our old approach (which was
20309 binding a UDP socket, and calling getsockname() on it). That
20310 approach was scaring OS X users whose draconian firewall
20311 software warned about binding to UDP sockets regardless of
20312 whether packets were sent. Now we try to use getifaddrs(),
20313 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
20314 system supports. Resolves ticket 1827.
20315 - Add experimental support for a "defaults" torrc file to be parsed
20316 before the regular torrc. Torrc options override the defaults file's
20317 options in the same way that the command line overrides the torrc.
20318 The SAVECONF controller command saves only those options which
20319 differ between the current configuration and the defaults file. HUP
20320 reloads both files. Implements task 4552.
20322 o New directory authorities:
20323 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
20324 authority. Closes ticket 5749.
20326 o Security/privacy fixes:
20327 - Avoid read-from-freed-memory and double-free bugs that could occur
20328 when a DNS request fails while launching it. Fixes bug 6480;
20329 bugfix on 0.2.0.1-alpha.
20330 - Reject any attempt to extend to an internal address. Without
20331 this fix, a router could be used to probe addresses on an internal
20332 network to see whether they were accepting connections. Fixes bug
20333 6710; bugfix on 0.0.8pre1.
20334 - Close any connection that sends unrecognized junk before the TLS
20335 handshake. Solves an issue noted in bug 4369.
20336 - The advertised platform of a relay now includes only its operating
20337 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
20338 its service pack level (for Windows) or its CPU architecture
20339 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
20340 can insert an extra string in the platform line by setting the
20341 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
20342 - Disable TLS session tickets. OpenSSL's implementation was giving
20343 our TLS session keys the lifetime of our TLS context objects, when
20344 perfect forward secrecy would want us to discard anything that
20345 could decrypt a link connection as soon as the link connection
20346 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
20347 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
20348 - Tor tries to wipe potentially sensitive data after using it, so
20349 that if some subsequent security failure exposes Tor's memory,
20350 the damage will be limited. But we had a bug where the compiler
20351 was eliminating these wipe operations when it decided that the
20352 memory was no longer visible to a (correctly running) program,
20353 hence defeating our attempt at defense in depth. We fix that
20354 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
20355 is unlikely to optimize away. Future versions of Tor may use
20356 a less ridiculously heavy approach for this. Fixes bug 7352.
20357 Reported in an article by Andrey Karpov.
20359 o Major bugfixes (crashes and asserts):
20360 - Avoid a pair of double-free and use-after-mark bugs that can
20361 occur with certain timings in canceled and re-received DNS
20362 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
20363 - Fix a denial of service attack by which any directory authority
20364 could crash all the others, or by which a single v2 directory
20365 authority could crash everybody downloading v2 directory
20366 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
20367 - Fix an assert that directory authorities could trigger on sighup
20368 during some configuration state transitions. We now don't treat
20369 it as a fatal error when the new descriptor we just generated in
20370 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
20371 - Avoid segfault when starting up having run with an extremely old
20372 version of Tor and parsing its state file. Fixes bug 6801; bugfix
20375 o Major bugfixes (clients):
20376 - If we are unable to find any exit that supports our predicted ports,
20377 stop calling them predicted, so that we don't loop and build
20378 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
20379 which introduced predicted ports.
20380 - Check at each new consensus whether our entry guards were picked
20381 long enough ago that we should rotate them. Previously, we only
20382 did this check at startup, which could lead to us holding a guard
20383 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
20384 - When fetching a bridge descriptor from a bridge authority,
20385 always do so anonymously, whether we have been able to open
20386 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
20387 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
20388 but we'll need to wait for bug 6010 before it's actually usable.
20390 o Major bugfixes (directory voting):
20391 - Check more thoroughly to prevent a rogue authority from
20392 double-voting on any consensus directory parameter. Previously,
20393 authorities would crash in this case if the total number of
20394 votes for any parameter exceeded the number of active voters,
20395 but would let it pass otherwise. Partially fixes bug 5786; bugfix
20397 - When computing weight parameters, behave more robustly in the
20398 presence of a bad bwweightscale value. Previously, the authorities
20399 would crash if they agreed on a sufficiently broken weight_scale
20400 value; now, they use a reasonable default and carry on. Fixes the
20401 rest of bug 5786; bugfix on 0.2.2.17-alpha.
20402 - If authorities are unable to get a v2 consensus document from other
20403 directory authorities, they no longer fall back to fetching
20404 them from regular directory caches. Fixes bug 5635; bugfix on
20405 0.2.2.26-beta, where routers stopped downloading v2 consensus
20406 documents entirely.
20408 o Major bugfixes (relays):
20409 - Fix a bug handling SENDME cells on nonexistent streams that could
20410 result in bizarre window values. Report and patch contributed
20411 pseudonymously. Fixes part of bug 6271. This bug was introduced
20412 before the first Tor release, in svn commit r152.
20413 - Don't update the AccountingSoftLimitHitAt state file entry whenever
20414 tor gets started. This prevents a wrong average bandwidth
20415 estimate, which would cause relays to always start a new accounting
20416 interval at the earliest possible moment. Fixes bug 2003; bugfix
20417 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
20418 immensely in tracking this bug down.
20419 - Fix a possible crash bug when checking for deactivated circuits
20420 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
20421 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
20422 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
20423 connections. This change should allow busy exit relays to stop
20424 running out of available sockets as quickly. Fixes bug 4950;
20425 bugfix on 0.2.2.26-beta.
20427 o Major bugfixes (blocking resistance):
20428 - Bridges no longer include their address in NETINFO cells on outgoing
20429 OR connections, to allow them to blend in better with clients.
20430 Removes another avenue for enumerating bridges. Reported by
20431 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
20432 cells were introduced.
20433 - Warn the user when HTTPProxy, but no other proxy type, is
20434 configured. This can cause surprising behavior: it doesn't send
20435 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
20436 directory traffic only. Resolves ticket 4663.
20438 o Major bugfixes (hidden services):
20439 - Improve hidden service robustness: when an attempt to connect to
20440 a hidden service ends, be willing to refetch its hidden service
20441 descriptors from each of the HSDir relays responsible for them
20442 immediately. Previously, we would not consider refetching the
20443 service's descriptors from each HSDir for 15 minutes after the last
20444 fetch, which was inconvenient if the hidden service was not running
20445 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
20446 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
20447 They used to check that the timestamp was within 30 minutes
20448 of their system clock, so they could cap the size of their
20449 replay-detection cache, but that approach unnecessarily refused
20450 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
20451 the v3 intro-point protocol (the first one which sent a timestamp
20452 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
20453 - When one of a hidden service's introduction points appears to be
20454 unreachable, stop trying it. Previously, we would keep trying
20455 to build circuits to the introduction point until we lost the
20456 descriptor, usually because the user gave up and restarted Tor.
20457 Fixes part of bug 3825.
20459 o Changes to default torrc file:
20460 - Stop listing "socksport 9050" in torrc.sample. We open a socks
20461 port on 9050 by default anyway, so this should not change anything
20463 - Stop mentioning the deprecated *ListenAddress options in
20464 torrc.sample. Fixes bug 5438.
20465 - Document unit of bandwidth-related options in sample torrc.
20467 - Fix broken URLs in the sample torrc file, and tell readers about
20468 the OutboundBindAddress, ExitPolicyRejectPrivate, and
20469 PublishServerDescriptor options. Addresses bug 4652.
20471 o Minor features (directory authorities):
20472 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
20473 change when the authority is deciding whether to accept a newly
20474 uploaded descriptor. Implements ticket 6423.
20475 - Directory authorities are now a little more lenient at accepting
20476 older router descriptors, or newer router descriptors that don't
20477 make big changes. This should help ameliorate past and future
20478 issues where routers think they have uploaded valid descriptors,
20479 but the authorities don't think so. Fix for ticket 2479.
20480 - Authority operators can now vote for all relays in a given
20481 set of countries to be BadDir/BadExit/Invalid/Rejected.
20482 - Provide two consensus parameters (FastFlagMinThreshold and
20483 FastFlagMaxThreshold) to control the range of allowable bandwidths
20484 for the Fast directory flag. These allow authorities to run
20485 experiments on appropriate requirements for being a "Fast" node.
20486 The AuthDirFastGuarantee config value still applies. Implements
20489 o Minor features (bridges / bridge authorities):
20490 - Make bridge SSL certificates a bit more stealthy by using random
20491 serial numbers, in the same fashion as OpenSSL when generating
20492 self-signed certificates. Implements ticket 4584.
20493 - Tag a bridge's descriptor as "never to be sent unencrypted".
20494 This shouldn't matter, since bridges don't open non-anonymous
20495 connections to the bridge authority and don't allow unencrypted
20496 directory connections from clients, but we might as well make
20497 sure. Closes bug 5139.
20498 - The Bridge Authority now writes statistics on how many bridge
20499 descriptors it gave out in total, and how many unique descriptors
20500 it gave out. It also lists how often the most and least commonly
20501 fetched descriptors were given out, as well as the median and
20502 25th/75th percentile. Implements tickets 4200 and 4294.
20504 o Minor features (IPv6):
20505 - Make the code that clients use to detect an address change be
20506 IPv6-aware, so that it won't fill clients' logs with error
20507 messages when trying to get the IPv4 address of an IPv6
20508 connection. Implements ticket 5537.
20509 - Relays now understand an IPv6 address when they get one from a
20510 directory server. Resolves ticket 4875.
20512 o Minor features (hidden services):
20513 - Expire old or over-used hidden service introduction points.
20514 Required by fix for bug 3460.
20515 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
20516 public key replay-detection cache from 60 minutes to 5 minutes. This
20517 replay-detection cache is now used only to detect multiple
20518 INTRODUCE2 cells specifying the same rendezvous point, so we can
20519 avoid launching multiple simultaneous attempts to connect to it.
20520 - When a hidden service's introduction point times out, consider
20521 trying it again during the next attempt to connect to the
20522 HS. Previously, we would not try it again unless a newly fetched
20523 descriptor contained it. Required by fixes for bugs 1297 and 3825.
20525 o Minor features (relays):
20526 - Relays now include a reason for regenerating their descriptors
20527 in an HTTP header when uploading to the authorities. This will
20528 make it easier to debug descriptor-upload issues in the future.
20529 - Turn on directory request statistics by default and include them in
20530 extra-info descriptors. Don't break if we have no GeoIP database.
20531 - Replace files in stats/ rather than appending to them. Now that we
20532 include statistics in extra-info descriptors, it makes no sense to
20533 keep old statistics forever. Implements ticket 2930.
20534 - Relays that set "ConnDirectionStatistics 1" write statistics on the
20535 bidirectional use of connections to disk every 24 hours.
20536 - Add a GeoIP file digest to the extra-info descriptor. Implements
20539 o Minor features (new config options):
20540 - New config option "DynamicDHGroups" (disabled by default) provides
20541 each bridge with a unique prime DH modulus to be used during
20542 SSL handshakes. This option attempts to help against censors
20543 who might use the Apache DH modulus as a static identifier for
20544 bridges. Addresses ticket 4548.
20545 - New config option "DisableDebuggerAttachment" (on by default)
20546 to prevent basic debugging attachment attempts by other processes.
20547 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
20548 - Ordinarily, Tor does not count traffic from private addresses (like
20549 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
20550 There is now a new option, CountPrivateBandwidth, to disable this
20551 behavior. Patch from Daniel Cagara.
20553 o Minor features (different behavior for old config options):
20554 - Allow MapAddress directives to specify matches against super-domains,
20555 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
20556 Implements issue 933.
20557 - Don't disable the DirPort when we cannot exceed our AccountingMax
20558 limit during this interval because the effective bandwidthrate is
20559 low enough. This is useful in a situation where AccountMax is only
20560 used as an additional safeguard or to provide statistics.
20561 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
20562 implements ticket 3439.
20563 - When configuring a large set of nodes in EntryNodes, and there are
20564 enough of them listed as Guard so that we don't need to consider
20565 the non-guard entries, prefer the ones listed with the Guard flag.
20566 - If you set the NumCPUs option to 0, Tor will now try to detect how
20567 many CPUs you have. This is the new default behavior.
20568 - The NodeFamily option -- which let you declare that you want to
20569 consider nodes to be part of a family whether they list themselves
20570 that way or not -- now allows IP address ranges and country codes.
20572 o Minor features (new command-line config behavior):
20573 - Slightly change behavior of "list" options (that is, config
20574 options that can appear more than once) when they appear both in
20575 torrc and on the command line. Previously, the command-line options
20576 would be appended to the ones from torrc. Now, the command-line
20577 options override the torrc options entirely. This new behavior
20578 allows the user to override list options (like exit policies and
20579 ports to listen on) from the command line, rather than simply
20580 appending to the list.
20581 - You can get the old (appending) command-line behavior for "list"
20582 options by prefixing the option name with a "+".
20583 - You can remove all the values for a "list" option from the command
20584 line without adding any new ones by prefixing the option name
20587 o Minor features (controller, new events):
20588 - Extend the control protocol to report flags that control a circuit's
20589 path selection in CIRC events and in replies to 'GETINFO
20590 circuit-status'. Implements part of ticket 2411.
20591 - Extend the control protocol to report the hidden service address
20592 and current state of a hidden-service-related circuit in CIRC
20593 events and in replies to 'GETINFO circuit-status'. Implements part
20595 - Include the creation time of a circuit in CIRC and CIRC2
20596 control-port events and the list produced by the 'GETINFO
20597 circuit-status' control-port command.
20598 - Add a new CONF_CHANGED event so that controllers can be notified
20599 of any configuration changes made by other controllers, or by the
20600 user. Implements ticket 1692.
20601 - Add a new SIGNAL event to the controller interface so that
20602 controllers can be notified when Tor handles a signal. Resolves
20603 issue 1955. Patch by John Brooks.
20605 o Minor features (controller, new getinfo options):
20606 - Expose our view of whether we have gone dormant to the controller,
20607 via a new "GETINFO dormant" value. Torbutton and other controllers
20608 can use this to avoid doing periodic requests through Tor while
20609 it's dormant (bug 4718). Resolves ticket 5954.
20610 - Add a new GETINFO option to get total bytes read and written. Patch
20611 from pipe, revised by atagar. Resolves ticket 2345.
20612 - Implement new GETINFO controller fields to provide information about
20613 the Tor process's pid, euid, username, and resource limits.
20615 o Minor features (controller, other):
20616 - Allow controllers to request an event notification whenever a
20617 circuit is cannibalized or its purpose is changed. Implements
20618 part of ticket 3457.
20619 - Use absolute path names when reporting the torrc filename in the
20620 control protocol, so a controller can more easily find the torrc
20621 file. Resolves bug 1101.
20622 - When reporting the path to the cookie file to the controller,
20623 give an absolute path. Resolves ticket 4881.
20625 o Minor features (log messages):
20626 - Add more information to a log statement that might help track down
20627 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
20628 non-IP address" messages (or any Bug messages, for that matter!),
20629 please let us know about it.
20630 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
20631 EntryNodes will have no effect. Resolves issue 2571.
20632 - Try to make the introductory warning message that Tor prints on
20633 startup more useful for actually finding help and information.
20634 Resolves ticket 2474.
20635 - When the system call to create a listener socket fails, log the
20636 error message explaining why. This may help diagnose bug 4027.
20638 o Minor features (other):
20639 - When we fail to initialize Libevent, retry with IOCP disabled so we
20640 don't need to turn on multi-threading support in Libevent, which in
20641 turn requires a working socketpair(). This is a workaround for bug
20642 4457, which affects Libevent versions from 2.0.1-alpha through
20644 - When starting as root and then changing our UID via the User
20645 control option, and we have a ControlSocket configured, make sure
20646 that the ControlSocket is owned by the same account that Tor will
20647 run under. Implements ticket 3421; fix by Jérémy Bobbio.
20648 - Accept attempts to include a password authenticator in the
20649 handshake, as supported by SOCKS5. This handles SOCKS clients that
20650 don't know how to omit a password when authenticating. Resolves
20652 - Check for and recover from inconsistency in the microdescriptor
20653 cache. This will make it harder for us to accidentally free a
20654 microdescriptor without removing it from the appropriate data
20655 structures. Fixes issue 3135; issue noted by "wanoskarnet".
20656 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
20658 o Minor bugfixes (code security):
20659 - Prevent a null-pointer dereference when receiving a data cell
20660 for a nonexistent stream when the circuit in question has an
20661 empty deliver window. We don't believe this is triggerable,
20662 since we don't currently allow deliver windows to become empty,
20663 but the logic is tricky enough that it's better to make the code
20664 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
20665 - Fix a (harmless) integer overflow in cell statistics reported by
20666 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
20667 - Fix our implementation of crypto_random_hostname() so it can't
20668 overflow on ridiculously large inputs. (No Tor version has ever
20669 provided this kind of bad inputs, but let's be correct in depth.)
20670 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
20671 - Add a (probably redundant) memory clear between iterations of
20672 the router status voting loop, to prevent future coding errors
20673 where data might leak between iterations of the loop. Resolves
20676 o Minor bugfixes (wrapper functions):
20677 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
20678 utility function used in the control-port code). This shouldn't
20679 ever happen unless Tor is completely out of memory, but if it did
20680 happen and Tor somehow recovered from it, Tor could have sent a log
20681 message to a control port in the middle of a reply to a controller
20682 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
20683 - Fix some (not actually triggerable) buffer size checks in usage of
20684 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
20686 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
20687 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
20688 - Enforce correct return behavior of tor_vsscanf() when the '%%'
20689 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
20690 - Make our replacement implementation of strtok_r() compatible with
20691 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
20692 bugfix on 0.2.2.1-alpha.
20693 - Find more places in the code that should have been testing for
20694 invalid sockets using the SOCKET_OK macro. Required for a fix
20695 for bug 4533. Bugfix on 0.2.2.28-beta.
20697 o Minor bugfixes (code correctness):
20698 - Check return value of fputs() when writing authority certificate
20699 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
20700 - When building Tor on Windows with -DUNICODE (not default), ensure
20701 that error messages, filenames, and DNS server names are always
20702 NUL-terminated when we convert them to a single-byte encoding.
20703 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
20704 - Fix a memory leak when trying to launch a DNS request when the
20705 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
20707 - Correct file sizes when reading binary files on Cygwin, to avoid
20708 a bug where Tor would fail to read its state file. Fixes bug 6844;
20709 bugfix on 0.1.2.7-alpha.
20710 - Make sure to set *socket_error in all error cases in
20711 connection_connect(), so it can't produce a warning about
20712 errno being zero from errno_to_orconn_end_reason(). Bugfix on
20713 0.2.1.1-alpha; resolves ticket 6028.
20714 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
20715 bug 4532; found by "troll_un".
20717 o Minor bugfixes (clients):
20718 - Allow one-hop directory-fetching circuits the full "circuit build
20719 timeout" period, rather than just half of it, before failing them
20720 and marking the relay down. This fix should help reduce cases where
20721 clients declare relays (or worse, bridges) unreachable because
20722 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
20723 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
20725 - Ensure we don't cannibalize circuits that are longer than three hops
20726 already, so we don't end up making circuits with 5 or more
20727 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
20728 0.1.0.1-rc which introduced cannibalization.
20730 o Minor bugfixes (relays):
20731 - Don't publish a new relay descriptor when we reload our onion key,
20732 unless the onion key has actually changed. Fixes bug 3263 and
20733 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
20734 - When relays refuse a "create" cell because their queue of pending
20735 create cells is too big (typically because their cpu can't keep up
20736 with the arrival rate), send back reason "resource limit" rather
20737 than reason "internal", so network measurement scripts can get a
20738 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
20739 - Exit nodes don't need to fetch certificates for authorities that
20740 they don't recognize; only directory authorities, bridges,
20741 and caches need to do that. Fixes part of bug 2297; bugfix on
20744 o Minor bugfixes (directory authority / mirrors):
20745 - Avoid O(n^2) performance characteristics when parsing a large
20746 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
20747 - Authorities no longer include any router in their microdescriptor
20748 consensuses for which they couldn't generate or agree on a
20749 microdescriptor. Fixes the second piece of bug 6404; fix on
20751 - When checking for requested signatures on the latest consensus
20752 before serving it to a client, make sure to check the right
20753 consensus flavor. Bugfix on 0.2.2.6-alpha.
20754 - Fix an edge case where TestingTorNetwork is set but the authorities
20755 and relays all have an uptime of zero, so the private Tor network
20756 could briefly lack support for hidden services. Fixes bug 3886;
20757 bugfix on 0.2.2.18-alpha.
20758 - Directory caches no longer refuse to clean out descriptors because
20759 of missing v2 networkstatus documents, unless they're configured
20760 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
20761 0.2.2.26-beta. Patch by Daniel Bryg.
20762 - Don't serve or accept v2 hidden service descriptors over a relay's
20763 DirPort. It's never correct to do so, and disabling it might
20764 make it more annoying to exploit any bugs that turn up in the
20765 descriptor-parsing code. Fixes bug 7149.
20767 o Minor bugfixes (hidden services, client-side):
20768 - Assert that hidden-service-related operations are not performed
20769 using single-hop circuits. Previously, Tor would assert that
20770 client-side streams are not attached to single-hop circuits,
20771 but not that other sensitive operations on the client and service
20772 side are not performed using single-hop circuits. Fixes bug 3332;
20774 - Avoid undefined behavior when parsing the list of supported
20775 rendezvous/introduction protocols in a hidden service descriptor.
20776 Previously, Tor would have confused (as-yet-unused) protocol version
20777 numbers greater than 32 with lower ones on many platforms. Fixes
20778 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
20779 - Don't close hidden service client circuits which have almost
20780 finished connecting to their destination when they reach
20781 the normal circuit-build timeout. Previously, we would close
20782 introduction circuits which are waiting for an acknowledgement
20783 from the introduction point, and rendezvous circuits which have
20784 been specified in an INTRODUCE1 cell sent to a hidden service,
20785 after the normal CBT. Now, we mark them as 'timed out', and launch
20786 another rendezvous attempt in parallel. This behavior change can
20787 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
20788 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
20790 o Minor bugfixes (hidden services, service-side):
20791 - Don't close hidden-service-side rendezvous circuits when they
20792 reach the normal circuit-build timeout. This behavior change can
20793 be disabled using the new
20794 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
20795 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
20796 - Don't launch more than 10 service-side introduction-point circuits
20797 for a hidden service in five minutes. Previously, we would consider
20798 launching more introduction-point circuits if at least one second
20799 had passed without any introduction-point circuits failing. Fixes
20800 bug 4607; bugfix on 0.0.7pre1.
20802 o Minor bugfixes (config option behavior):
20803 - If the user tries to set MyFamily on a bridge, refuse to
20804 do so, and warn about the security implications. Fixes bug 4657;
20805 bugfix on 0.2.0.3-alpha.
20806 - The "--quiet" and "--hush" options now apply not only to Tor's
20807 behavior before logs are configured, but also to Tor's behavior in
20808 the absence of configured logs. Fixes bug 3550; bugfix on
20810 - Change the AllowDotExit rules so they should actually work.
20811 We now enforce AllowDotExit only immediately after receiving an
20812 address via SOCKS or DNSPort: other sources are free to provide
20813 .exit addresses after the resolution occurs. Fixes bug 3940;
20814 bugfix on 0.2.2.1-alpha.
20815 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
20816 don't depend on the consensus parameters or compute adaptive
20817 timeouts when it is disabled. Fixes bug 5049; bugfix on
20819 - After we pick a directory mirror, we would refuse to use it if
20820 it's in our ExcludeExitNodes list, resulting in mysterious failures
20821 to bootstrap for people who just wanted to avoid exiting from
20822 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
20823 - When told to add a bridge with the same digest as a preexisting
20824 bridge but a different addr:port, change the addr:port as
20825 requested. Previously we would not notice the change. Fixes half
20826 of bug 5603; fix on 0.2.2.26-beta.
20828 o Minor bugfixes (controller):
20829 - Allow manual 'authenticate' commands to the controller interface
20830 from netcat (nc) as well as telnet. We were rejecting them because
20831 they didn't come with the expected whitespace at the end of the
20832 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
20833 - Report a real bootstrap problem to the controller on router
20834 identity mismatch. Previously we just said "foo", which probably
20835 made a lot of sense at the time. Fixes bug 4169; bugfix on
20837 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
20838 option is set to 0 (which Vidalia version 0.2.16 now does when
20839 a SAVECONF attempt fails), perform other actions that SIGHUP
20840 usually causes (like reopening the logs). Fixes bug 5095; bugfix
20842 - Correctly handle checking the permissions on the parent
20843 directory of a control socket in the root directory. Bug found
20844 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
20846 - End AUTHCHALLENGE error messages (in the control protocol) with
20847 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
20849 o Minor bugfixes (network reading/writing):
20850 - Disable writing on marked-for-close connections when they are
20851 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
20852 bug 5263; bugfix on 0.0.2pre13, where we first added a special
20853 case for flushing marked connections.
20854 - Make sure that there are no unhandled pending TLS errors before
20855 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
20856 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
20857 Bugfix on 0.1.0.5-rc; fixes bug 4528.
20858 - Detect SSL handshake even when the initial attempt to write the
20859 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
20860 - If the client fails to set a reasonable set of ciphersuites
20861 during its v2 handshake renegotiation, allow the renegotiation to
20862 continue nevertheless (i.e. send all the required certificates).
20863 Fixes bug 4591; bugfix on 0.2.0.20-rc.
20865 o Minor bugfixes (other):
20866 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
20867 resource exhaustion, so that clients can adjust their load to
20868 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
20869 started using END_STREAM_REASON_RESOURCELIMIT.
20870 - Don't check for whether the address we're using for outbound
20871 connections has changed until after the outbound connection has
20872 completed. On Windows, getsockname() doesn't succeed until the
20873 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
20874 - Don't hold a Windows file handle open for every file mapping;
20875 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
20877 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
20878 bugfix on 0.2.1.10-alpha.
20879 - If we fail to write a microdescriptor to the disk cache, do not
20880 continue replacing the old microdescriptor file. Fixes bug 2954;
20881 bugfix on 0.2.2.6-alpha.
20883 o Minor bugfixes (log messages, path selection):
20884 - Downgrade "set buildtimeout to low value" messages to "info"
20885 severity; they were never an actual problem, there was never
20886 anything reasonable to do about them, and they tended to spam logs
20887 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
20888 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
20889 more information to it, so that we can track it down in case it
20890 returns again. Mitigates bug 5235.
20891 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
20892 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
20893 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
20894 - Issue a log message if a guard completes less than 40% of your
20895 circuits. Threshold is configurable by torrc option
20896 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
20897 additional, off-by-default code to disable guards which fail too
20898 many circuits. Addresses ticket 5458.
20900 o Minor bugfixes (log messages, client):
20901 - Downgrade "Got a certificate, but we already have it" log messages
20902 from warning to info, except when we're a dirauth. Fixes bug 5238;
20903 bugfix on 0.2.1.7-alpha.
20904 - Fix the log message describing how we work around discovering
20905 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
20906 4837; bugfix on 0.2.2.9-alpha.
20907 - When logging about a disallowed .exit name, do not also call it
20908 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
20909 - Fix a log message suggesting that people contact a non-existent
20910 email address. Fixes bug 3448.
20911 - Rephrase the log message emitted if the TestSocks check is
20912 successful. Patch from Fabian Keil; fixes bug 4094.
20913 - Log (at debug level) whenever a circuit's purpose is changed.
20914 - Log SSL state transitions at log level DEBUG, log domain
20915 HANDSHAKE. This can be useful for debugging censorship events.
20916 Implements ticket 3264.
20917 - We now log which torrc file we're using on startup. Implements
20919 - Rate-limit log messages when asked to connect anonymously to
20920 a private address. When these hit, they tended to hit fast and
20921 often. Also, don't bother trying to connect to addresses that we
20922 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
20923 reply makes us think we have been lied to, even when the address the
20924 client tried to connect to was "localhost." Resolves ticket 2822.
20926 o Minor bugfixes (log messages, non-client):
20927 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
20928 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
20929 - Don't log that we have "decided to publish new relay descriptor"
20930 unless we are actually publishing a descriptor. Fixes bug 3942;
20931 bugfix on 0.2.2.28-beta.
20932 - Log which authority we're missing votes from when we go to fetch
20933 them from the other auths.
20934 - Replace "Sending publish request" log messages with "Launching
20935 upload", so that they no longer confusingly imply that we're
20936 sending something to a directory we might not even be connected
20937 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
20938 - Warn when Tor is configured to use accounting in a way that can
20939 link a hidden service to some other hidden service or public
20940 address. Resolves ticket 6490.
20941 - Fix a minor formatting issue in one of tor-gencert's error messages.
20945 - Update to the latest version of the tinytest unit testing framework.
20946 This includes a couple of bugfixes that can be relevant for
20947 running forked unit tests on Windows, and removes all reserved
20949 - Avoid a false positive in the util/threads unit test by increasing
20950 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
20951 - Make it possible to set the TestingTorNetwork configuration
20952 option using AlternateDirAuthority and AlternateBridgeAuthority
20953 as an alternative to setting DirServer. Addresses ticket 6377.
20954 - Add a unit test for the environment_variable_names_equal() function.
20955 - A wide variety of new unit tests by Esteban Manchado Velázquez.
20956 - Numerous new unit tests for functions in util.c and address.c by
20958 - The long-disabled benchmark tests are now split into their own
20959 ./src/test/bench binary.
20960 - The benchmark tests can now use more accurate timers than
20961 gettimeofday() when such timers are available.
20962 - Use tt_assert(), not tor_assert(), for checking for test failures.
20963 This makes the unit tests more able to go on in the event that
20966 o Build improvements:
20967 - Use the dead_strip option when building Tor on OS X. This reduces
20968 binary size by almost 19% when linking openssl and libevent
20969 statically, which we do for Tor Browser Bundle.
20970 - Provide a better error message about possible OSX Asciidoc failure
20971 reasons. Fixes bug 6436.
20972 - Detect attempts to build Tor on (as yet hypothetical) versions
20973 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
20974 fix for bug 4533. Bugfix on 0.2.2.28-beta.
20975 - On Windows, we now define the _WIN32_WINNT macros only if they
20976 are not already defined. This lets the person building Tor decide,
20977 if they want, to require a later version of Windows.
20978 - Our autogen.sh script now uses autoreconf to launch autoconf,
20979 automake, and so on. This is more robust against some of the failure
20980 modes associated with running the autotools pieces on their own.
20981 - Running "make version" now displays the version of Tor that
20982 we're about to build. Idea from katmagic; resolves issue 4400.
20983 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
20984 on 0.2.2.4-alpha; fixes bug 3427.
20985 - New --enable-static-tor configure option for building Tor as
20986 statically as possible. Idea, general hackery and thoughts from
20987 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
20989 - Limited, experimental support for building with nmake and MSVC.
20991 o Build requirements:
20992 - Building Tor with bufferevent support now requires Libevent
20993 2.0.13-stable or later. Previous versions of Libevent had bugs in
20994 SSL-related bufferevents and related issues that would make Tor
20995 work badly with bufferevents. Requiring 2.0.13-stable also allows
20996 Tor with bufferevents to take advantage of Libevent APIs
20997 introduced after 2.0.8-rc.
20998 - Our build system requires automake 1.6 or later to create the
20999 Makefile.in files. Previously, you could have used 1.4.
21000 This only affects developers and people building Tor from git;
21001 people who build Tor from the source distribution without changing
21002 the Makefile.am files should be fine.
21003 - Detect when we try to build on a platform that doesn't define
21004 AF_UNSPEC to 0. We don't work there, so refuse to compile.
21006 o Build fixes (compile/link):
21007 - Format more doubles with %f, not %lf. Patch from grarpamp to make
21008 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
21010 - When building with --enable-static-tor on OpenBSD, do not
21011 erroneously attempt to link -lrt. Fixes bug 5103.
21012 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
21013 that IPv6 stuff will compile on MSVC, and compilation issues
21014 will be easier to track down. Fixes bug 5861.
21015 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
21016 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
21017 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
21018 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
21020 o Build fixes (other):
21021 - Use the _WIN32 macro throughout our code to detect Windows.
21022 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
21024 - Properly handle the case where the build-tree is not the same
21025 as the source tree when generating src/common/common_sha1.i,
21026 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
21027 bugfix on 0.2.0.1-alpha.
21028 - During configure, search for library containing cos function as
21029 libm lives in libcore on some platforms (BeOS/Haiku). Linking
21030 against libm was hard-coded before. Fixes the first part of bug
21031 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
21033 - Prevent a false positive from the check-spaces script, by disabling
21034 the "whitespace between function name and (" check for functions
21037 o Packaging (RPM) changes:
21038 - Update our default RPM spec files to work with mock and rpmbuild
21039 on RHEL/Fedora. They have an updated set of dependencies and
21040 conflicts, a fix for an ancient typo when creating the "_tor"
21041 user, and better instructions. Thanks to Ondrej Mikle for the
21042 patch series. Fixes bug 6043.
21043 - On OpenSUSE, create the /var/run/tor directory on startup if it
21044 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
21046 o Code refactoring (safety):
21047 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
21048 10 lines. Also, don't nest them. Doing so in the past has
21049 led to hard-to-debug code. The new style is to use the
21050 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
21051 - Use macros to indicate OpenSSL versions, so we don't need to worry
21052 about accidental hexadecimal bit shifts.
21053 - Use tor_sscanf() in place of scanf() in more places through the
21054 code. This makes us a little more locale-independent, and
21055 should help shut up code-analysis tools that can't tell
21056 a safe sscanf string from a dangerous one.
21057 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
21058 - Use the smartlist_add_asprintf() alias more consistently.
21060 o Code refactoring (consolidate):
21061 - A major revision to our internal node-selecting and listing logic.
21062 Tor already had at least two major ways to look at the question of
21063 "which Tor servers do we know about": a list of router descriptors,
21064 and a list of entries in the current consensus. With
21065 microdescriptors, we're adding a third. Having so many systems
21066 without an abstraction layer over them was hurting the codebase.
21067 Now, we have a new "node_t" abstraction that presents a consistent
21068 interface to a client's view of a Tor node, and holds (nearly) all
21069 of the mutable state formerly in routerinfo_t and routerstatus_t.
21070 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
21071 Libevent's notion of cached time when possible.
21072 - Remove duplicate code for invoking getrlimit() from control.c.
21073 - Use OpenSSL's built-in SSL_state_string_long() instead of our
21074 own homebrewed ssl_state_to_string() replacement. Patch from
21075 Emile Snyder. Fixes bug 4653.
21076 - Change the symmetric cipher interface so that creating and
21077 initializing a stream cipher are no longer separate functions.
21079 o Code refactoring (separate):
21080 - Make a new "entry connection" struct as an internal subtype of "edge
21081 connection", to simplify the code and make exit connections smaller.
21082 - Split connection_about_to_close() into separate functions for each
21084 - Rewrite the listener-selection logic so that parsing which ports
21085 we want to listen on is now separate from binding to the ports
21088 o Code refactoring (name changes):
21089 - Rename a handful of old identifiers, mostly related to crypto
21090 structures and crypto functions. By convention, our "create an
21091 object" functions are called "type_new()", our "free an object"
21092 functions are called "type_free()", and our types indicate that
21093 they are types only with a final "_t". But a handful of older
21094 types and functions broke these rules, with function names like
21095 "type_create" or "subsystem_op_type", or with type names like
21097 - Rename Tor functions that turn strings into addresses, so that
21098 "parse" indicates that no hostname resolution occurs, and
21099 "lookup" indicates that hostname resolution may occur. This
21100 should help prevent mistakes in the future. Fixes bug 3512.
21101 - Use the name "CERTS" consistently to refer to the new cell type;
21102 we were calling it CERT in some places and CERTS in others.
21103 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
21104 invalid value, rather than just -1.
21105 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
21106 can pick them up when the tests aren't disabled. Bugfix on
21107 0.2.2.4-alpha which introduced tinytest.
21109 o Code refactoring (other):
21110 - Defensively refactor rend_mid_rendezvous() so that protocol
21111 violations and length checks happen in the beginning. Fixes
21113 - Remove the pure attribute from all functions that used it
21114 previously. In many cases we assigned it incorrectly, because the
21115 functions might assert or call impure functions, and we don't have
21116 evidence that keeping the pure attribute is worthwhile. Implements
21117 changes suggested in ticket 4421.
21118 - Move the replay-detection cache for the RSA-encrypted parts of
21119 INTRODUCE2 cells to the introduction point data structures.
21120 Previously, we would use one replay-detection cache per hidden
21121 service. Required by fix for bug 3460.
21122 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
21123 no longer link against Libevent: they never used it, but
21124 our library structure used to force them to link it.
21126 o Removed features and files:
21127 - Remove all internal support for unpadded RSA. We never used it, and
21128 it would be a bad idea to start.
21129 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
21131 - Remove some redundant #include directives throughout the code.
21132 Patch from Andrea Gelmini.
21133 - Remove some old code to remember statistics about which descriptors
21134 we've served as a directory mirror. The feature wasn't used and
21135 is outdated now that microdescriptors are around.
21136 - Remove some old code to work around even older versions of Tor that
21137 used forked processes to handle DNS requests. Such versions of Tor
21138 are no longer in use as relays.
21139 - The "torify" script no longer supports the "tsocks" socksifier
21140 tool, since tsocks doesn't support DNS and UDP right for Tor.
21141 Everyone should be using torsocks instead. Fixes bugs 3530 and
21142 5180. Based on a patch by "ugh".
21143 - Remove the torrc.bridge file: we don't use it for anything, and
21144 it had become badly desynchronized from torrc.sample. Resolves
21148 - Begin a doc/state-contents.txt file to explain the contents of
21149 the Tor state file. Fixes bug 2987.
21150 - Clarify the documentation for the Alternate*Authority options.
21152 - Document the --defaults-torrc option, and the new semantics for
21153 overriding, extending, and clearing lists of options. Closes
21155 - Add missing man page documentation for consensus and microdesc
21156 files. Resolves ticket 6732.
21157 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
21159 o Documentation fixes:
21160 - Improve the manual's documentation for the NT Service command-line
21161 options. Addresses ticket 3964.
21162 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
21163 - Document the changes to the ORPort and DirPort options, and the
21164 fact that {OR/Dir}ListenAddress is now unnecessary (and
21165 therefore deprecated). Resolves ticket 5597.
21166 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
21167 - Clarify that hidden services are TCP only. Fixes bug 6024.
21170 Changes in version 0.2.2.39 - 2012-09-11
21171 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
21175 - Fix an assertion failure in tor_timegm() that could be triggered
21176 by a badly formatted directory object. Bug found by fuzzing with
21177 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
21178 - Do not crash when comparing an address with port value 0 to an
21179 address policy. This bug could have been used to cause a remote
21180 assertion failure by or against directory authorities, or to
21181 allow some applications to crash clients. Fixes bug 6690; bugfix
21185 Changes in version 0.2.2.38 - 2012-08-12
21186 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
21187 attack that could in theory leak path information.
21190 - Avoid an uninitialized memory read when reading a vote or consensus
21191 document that has an unrecognized flavor name. This read could
21192 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
21193 - Try to leak less information about what relays a client is
21194 choosing to a side-channel attacker. Previously, a Tor client would
21195 stop iterating through the list of available relays as soon as it
21196 had chosen one, thus finishing a little earlier when it picked
21197 a router earlier in the list. If an attacker can recover this
21198 timing information (nontrivial but not proven to be impossible),
21199 they could learn some coarse-grained information about which relays
21200 a client was picking (middle nodes in particular are likelier to
21201 be affected than exits). The timing attack might be mitigated by
21202 other factors (see bug 6537 for some discussion), but it's best
21203 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
21206 Changes in version 0.2.2.37 - 2012-06-06
21207 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
21208 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
21212 - Work around a bug in OpenSSL that broke renegotiation with TLS
21213 1.1 and TLS 1.2. Without this workaround, all attempts to speak
21214 the v2 Tor connection protocol when both sides were using OpenSSL
21215 1.0.1 would fail. Resolves ticket 6033.
21216 - When waiting for a client to renegotiate, don't allow it to add
21217 any bytes to the input buffer. This fixes a potential DoS issue.
21218 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
21219 - Fix an edge case where if we fetch or publish a hidden service
21220 descriptor, we might build a 4-hop circuit and then use that circuit
21221 for exiting afterwards -- even if the new last hop doesn't obey our
21222 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
21225 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
21226 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
21229 - Tell GCC and Clang to check for any errors in format strings passed
21230 to the tor_v*(print|scan)f functions.
21233 Changes in version 0.2.2.36 - 2012-05-24
21234 Tor 0.2.2.36 updates the addresses for two of the eight directory
21235 authorities, fixes some potential anonymity and security issues,
21236 and fixes several crash bugs.
21238 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
21239 known flaws, and nobody should be using them. You should upgrade. If
21240 you're using a Linux or BSD and its packages are obsolete, stop using
21241 those packages and upgrade anyway.
21243 o Directory authority changes:
21244 - Change IP address for maatuska (v3 directory authority).
21245 - Change IP address for ides (v3 directory authority), and rename
21249 - When building or running with any version of OpenSSL earlier
21250 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
21251 versions have a bug (CVE-2011-4576) in which their block cipher
21252 padding includes uninitialized data, potentially leaking sensitive
21253 information to any peer with whom they make a SSLv3 connection. Tor
21254 does not use SSL v3 by default, but a hostile client or server
21255 could force an SSLv3 connection in order to gain information that
21256 they shouldn't have been able to get. The best solution here is to
21257 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
21258 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
21259 to make sure that the bug can't happen.
21260 - Never use a bridge or a controller-supplied node as an exit, even
21261 if its exit policy allows it. Found by wanoskarnet. Fixes bug
21262 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
21263 and 0.2.0.3-alpha (for bridge-purpose descriptors).
21264 - Only build circuits if we have a sufficient threshold of the total
21265 descriptors that are marked in the consensus with the "Exit"
21266 flag. This mitigates an attack proposed by wanoskarnet, in which
21267 all of a client's bridges collude to restrict the exit nodes that
21268 the client knows about. Fixes bug 5343.
21269 - Provide controllers with a safer way to implement the cookie
21270 authentication mechanism. With the old method, if another locally
21271 running program could convince a controller that it was the Tor
21272 process, then that program could trick the controller into telling
21273 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
21274 authentication method uses a challenge-response approach to prevent
21275 this attack. Fixes bug 5185; implements proposal 193.
21278 - Avoid logging uninitialized data when unable to decode a hidden
21279 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
21280 - Avoid a client-side assertion failure when receiving an INTRODUCE2
21281 cell on a general purpose circuit. Fixes bug 5644; bugfix on
21283 - Fix builds when the path to sed, openssl, or sha1sum contains
21284 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
21286 - Correct our replacements for the timeradd() and timersub() functions
21287 on platforms that lack them (for example, Windows). The timersub()
21288 function is used when expiring circuits, while timeradd() is
21289 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
21290 bugfix on 0.2.2.24-alpha.
21291 - Fix the SOCKET_OK test that we use to tell when socket
21292 creation fails so that it works on Win64. Fixes part of bug 4533;
21293 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
21296 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
21297 Fixes bug 5346; bugfix on 0.0.8pre3.
21298 - Make our number-parsing functions always treat too-large values
21299 as an error, even when those values exceed the width of the
21300 underlying type. Previously, if the caller provided these
21301 functions with minima or maxima set to the extreme values of the
21302 underlying integer type, these functions would return those
21303 values on overflow rather than treating overflow as an error.
21304 Fixes part of bug 5786; bugfix on 0.0.9.
21305 - Older Linux kernels erroneously respond to strange nmap behavior
21306 by having accept() return successfully with a zero-length
21307 socket. When this happens, just close the connection. Previously,
21308 we would try harder to learn the remote address: but there was
21309 no such remote address to learn, and our method for trying to
21310 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
21311 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
21312 - Correct parsing of certain date types in parse_http_time().
21313 Without this patch, If-Modified-Since would behave
21314 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
21315 Esteban Manchado Velázques.
21316 - Change the BridgePassword feature (part of the "bridge community"
21317 design, which is not yet implemented) to use a time-independent
21318 comparison. The old behavior might have allowed an adversary
21319 to use timing to guess the BridgePassword value. Fixes bug 5543;
21320 bugfix on 0.2.0.14-alpha.
21321 - Detect and reject certain misformed escape sequences in
21322 configuration values. Previously, these values would cause us
21323 to crash if received in a torrc file or over an authenticated
21324 control port. Bug found by Esteban Manchado Velázquez, and
21325 independently by Robert Connolly from Matta Consulting who further
21326 noted that it allows a post-authentication heap overflow. Patch
21327 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
21328 bugfix on 0.2.0.16-alpha.
21329 - Fix a compile warning when using the --enable-openbsd-malloc
21330 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
21331 - During configure, detect when we're building with clang version
21332 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
21333 CFLAGS. clang doesn't support them yet.
21334 - When sending an HTTP/1.1 proxy request, include a Host header.
21335 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
21336 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
21337 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
21338 - If we hit the error case where routerlist_insert() replaces an
21339 existing (old) server descriptor, make sure to remove that
21340 server descriptor from the old_routers list. Fix related to bug
21341 1776. Bugfix on 0.2.2.18-alpha.
21343 o Minor bugfixes (documentation and log messages):
21344 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
21345 Fixes bug 4856; bugfix on Tor 0.0.6.
21346 - Update "ClientOnly" man page entry to explain that there isn't
21347 really any point to messing with it. Resolves ticket 5005.
21348 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
21349 directory authority option (introduced in Tor 0.2.2.34).
21350 - Downgrade the "We're missing a certificate" message from notice
21351 to info: people kept mistaking it for a real problem, whereas it
21352 is seldom the problem even when we are failing to bootstrap. Fixes
21353 bug 5067; bugfix on 0.2.0.10-alpha.
21354 - Correctly spell "connect" in a log message on failure to create a
21355 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
21356 - Clarify the behavior of MaxCircuitDirtiness with hidden service
21357 circuits. Fixes issue 5259.
21360 - Directory authorities now reject versions of Tor older than
21361 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
21362 inclusive. These versions accounted for only a small fraction of
21363 the Tor network, and have numerous known security issues. Resolves
21365 - Update to the May 1 2012 Maxmind GeoLite Country database.
21368 - When sending or relaying a RELAY_EARLY cell, we used to convert
21369 it to a RELAY cell if the connection was using the v1 link
21370 protocol. This was a workaround for older versions of Tor, which
21371 didn't handle RELAY_EARLY cells properly. Now that all supported
21372 versions can handle RELAY_EARLY cells, and now that we're enforcing
21373 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
21374 remove this workaround. Addresses bug 4786.
21377 Changes in version 0.2.2.35 - 2011-12-16
21378 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
21379 buffers code. Absolutely everybody should upgrade.
21381 The bug relied on an incorrect calculation when making data continuous
21382 in one of our IO buffers, if the first chunk of the buffer was
21383 misaligned by just the wrong amount. The miscalculation would allow an
21384 attacker to overflow a piece of heap-allocated memory. To mount this
21385 attack, the attacker would need to either open a SOCKS connection to
21386 Tor's SocksPort (usually restricted to localhost), or target a Tor
21387 instance configured to make its connections through a SOCKS proxy
21388 (which Tor does not do by default).
21390 Good security practice requires that all heap-overflow bugs should be
21391 presumed to be exploitable until proven otherwise, so we are treating
21392 this as a potential code execution attack. Please upgrade immediately!
21393 This bug does not affect bufferevents-based builds of Tor. Special
21394 thanks to "Vektor" for reporting this issue to us!
21396 Tor 0.2.2.35 also fixes several bugs in previous versions, including
21397 crash bugs for unusual configurations, and a long-term bug that
21398 would prevent Tor from starting on Windows machines with draconian
21401 With this release, we remind everyone that 0.2.0.x has reached its
21402 formal end-of-life. Those Tor versions have many known flaws, and
21403 nobody should be using them. You should upgrade -- ideally to the
21404 0.2.2.x series. If you're using a Linux or BSD and its packages are
21405 obsolete, stop using those packages and upgrade anyway.
21407 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
21408 longer receive support after some time in early 2012.
21411 - Fix a heap overflow bug that could occur when trying to pull
21412 data into the first chunk of a buffer, when that chunk had
21413 already had some data drained from it. Fixes CVE-2011-2778;
21414 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
21415 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
21416 that it doesn't attempt to allocate a socketpair. This could cause
21417 some problems on Windows systems with overzealous firewalls. Fix for
21418 bug 4457; workaround for Libevent versions 2.0.1-alpha through
21420 - If we mark an OR connection for close based on a cell we process,
21421 don't process any further cells on it. We already avoid further
21422 reads on marked-for-close connections, but now we also discard the
21423 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
21424 which was the first version where we might mark a connection for
21425 close based on processing a cell on it.
21426 - Correctly sanity-check that we don't underflow on a memory
21427 allocation (and then assert) for hidden service introduction
21428 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
21429 bugfix on 0.2.1.5-alpha.
21430 - Fix a memory leak when we check whether a hidden service
21431 descriptor has any usable introduction points left. Fixes bug
21432 4424. Bugfix on 0.2.2.25-alpha.
21433 - Don't crash when we're running as a relay and don't have a GeoIP
21434 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
21435 we've had in the 0.2.3.x branch already.
21436 - When running as a client, do not print a misleading (and plain
21437 wrong) log message that we're collecting "directory request"
21438 statistics: clients don't collect statistics. Also don't create a
21439 useless (because empty) stats file in the stats/ directory. Fixes
21440 bug 4353; bugfix on 0.2.2.34.
21443 - Detect failure to initialize Libevent. This fix provides better
21444 detection for future instances of bug 4457.
21445 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
21446 function. This was eating up hideously large amounts of time on some
21447 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
21448 - Resolve an integer overflow bug in smartlist_ensure_capacity().
21449 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
21451 - Don't warn about unused log_mutex in log.c when building with
21452 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
21453 0.1.0.6-rc which introduced --disable-threads.
21454 - When configuring, starting, or stopping an NT service, stop
21455 immediately after the service configuration attempt has succeeded
21456 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
21457 - When sending a NETINFO cell, include the original address
21458 received for the other side, not its canonical address. Found
21459 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
21460 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
21461 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
21462 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
21463 occurred when a client tried to fetch a descriptor for a bridge
21464 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
21465 - Backport fixes for a pair of compilation warnings on Windows.
21466 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
21467 - If we had ever tried to call tor_addr_to_str on an address of
21468 unknown type, we would have done a strdup on an uninitialized
21469 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
21470 Reported by "troll_un".
21471 - Correctly detect and handle transient lookup failures from
21472 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
21473 Reported by "troll_un".
21474 - Fix null-pointer access that could occur if TLS allocation failed.
21475 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
21476 - Use tor_socket_t type for listener argument to accept(). Fixes bug
21477 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
21480 - Add two new config options for directory authorities:
21481 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
21482 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
21483 that is always sufficient to satisfy the bandwidth requirement for
21484 the Guard flag. Now it will be easier for researchers to simulate
21485 Tor networks with different values. Resolves ticket 4484.
21486 - When Tor ignores a hidden service specified in its configuration,
21487 include the hidden service's directory in the warning message.
21488 Previously, we would only tell the user that some hidden service
21489 was ignored. Bugfix on 0.0.6; fixes bug 4426.
21490 - Update to the December 6 2011 Maxmind GeoLite Country database.
21492 o Packaging changes:
21493 - Make it easier to automate expert package builds on Windows,
21494 by removing an absolute path from makensis.exe command.
21497 Changes in version 0.2.1.32 - 2011-12-16
21498 Tor 0.2.1.32 backports important security and privacy fixes for
21499 oldstable. This release is intended only for package maintainers and
21500 others who cannot use the 0.2.2 stable series. All others should be
21501 using Tor 0.2.2.x or newer.
21503 The Tor 0.2.1.x series will reach formal end-of-life some time in
21504 early 2012; we will stop releasing patches for it then.
21506 o Major bugfixes (also included in 0.2.2.x):
21507 - Correctly sanity-check that we don't underflow on a memory
21508 allocation (and then assert) for hidden service introduction
21509 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
21510 bugfix on 0.2.1.5-alpha.
21511 - Fix a heap overflow bug that could occur when trying to pull
21512 data into the first chunk of a buffer, when that chunk had
21513 already had some data drained from it. Fixes CVE-2011-2778;
21514 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
21517 - Update to the December 6 2011 Maxmind GeoLite Country database.
21520 Changes in version 0.2.2.34 - 2011-10-26
21521 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
21522 can deanonymize Tor users. Everybody should upgrade.
21524 The attack relies on four components: 1) Clients reuse their TLS cert
21525 when talking to different relays, so relays can recognize a user by
21526 the identity key in her cert. 2) An attacker who knows the client's
21527 identity key can probe each guard relay to see if that identity key
21528 is connected to that guard relay right now. 3) A variety of active
21529 attacks in the literature (starting from "Low-Cost Traffic Analysis
21530 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
21531 discover the guard relays that a Tor user visiting the website is using.
21532 4) Clients typically pick three guards at random, so the set of guards
21533 for a given user could well be a unique fingerprint for her. This
21534 release fixes components #1 and #2, which is enough to block the attack;
21535 the other two remain as open research problems. Special thanks to
21536 "frosty_un" for reporting the issue to us!
21538 Clients should upgrade so they are no longer recognizable by the TLS
21539 certs they present. Relays should upgrade so they no longer allow a
21540 remote attacker to probe them to test whether unpatched clients are
21541 currently connected to them.
21543 This release also fixes several vulnerabilities that allow an attacker
21544 to enumerate bridge relays. Some bridge enumeration attacks still
21545 remain; see for example proposal 188.
21547 o Privacy/anonymity fixes (clients):
21548 - Clients and bridges no longer send TLS certificate chains on
21549 outgoing OR connections. Previously, each client or bridge would
21550 use the same cert chain for all outgoing OR connections until
21551 its IP address changes, which allowed any relay that the client
21552 or bridge contacted to determine which entry guards it is using.
21553 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
21554 - If a relay receives a CREATE_FAST cell on a TLS connection, it
21555 no longer considers that connection as suitable for satisfying a
21556 circuit EXTEND request. Now relays can protect clients from the
21557 CVE-2011-2768 issue even if the clients haven't upgraded yet.
21558 - Directory authorities no longer assign the Guard flag to relays
21559 that haven't upgraded to the above "refuse EXTEND requests
21560 to client connections" fix. Now directory authorities can
21561 protect clients from the CVE-2011-2768 issue even if neither
21562 the clients nor the relays have upgraded yet. There's a new
21563 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
21564 to let us transition smoothly, else tomorrow there would be no
21567 o Privacy/anonymity fixes (bridge enumeration):
21568 - Bridge relays now do their directory fetches inside Tor TLS
21569 connections, like all the other clients do, rather than connecting
21570 directly to the DirPort like public relays do. Removes another
21571 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
21572 - Bridges relays now build circuits for themselves in a more similar
21573 way to how clients build them. Removes another avenue for
21574 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
21575 when bridges were introduced.
21576 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
21577 that they initiated. Relays could distinguish incoming bridge
21578 connections from client connections, creating another avenue for
21579 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
21580 Found by "frosty_un".
21583 - Fix a crash bug when changing node restrictions while a DNS lookup
21584 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
21586 - Don't launch a useless circuit after failing to use one of a
21587 hidden service's introduction points. Previously, we would
21588 launch a new introduction circuit, but not set the hidden service
21589 which that circuit was intended to connect to, so it would never
21590 actually be used. A different piece of code would then create a
21591 new introduction circuit correctly. Bug reported by katmagic and
21592 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
21595 - Change an integer overflow check in the OpenBSD_Malloc code so
21596 that GCC is less likely to eliminate it as impossible. Patch
21597 from Mansour Moufid. Fixes bug 4059.
21598 - When a hidden service turns an extra service-side introduction
21599 circuit into a general-purpose circuit, free the rend_data and
21600 intro_key fields first, so we won't leak memory if the circuit
21601 is cannibalized for use as another service-side introduction
21602 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
21603 - Bridges now skip DNS self-tests, to act a little more stealthily.
21604 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
21605 bridges. Patch by "warms0x".
21606 - Fix internal bug-checking logic that was supposed to catch
21607 failures in digest generation so that it will fail more robustly
21608 if we ask for a nonexistent algorithm. Found by Coverity Scan.
21609 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
21610 - Report any failure in init_keys() calls launched because our
21611 IP address has changed. Spotted by Coverity Scan. Bugfix on
21612 0.1.1.4-alpha; fixes CID 484.
21614 o Minor bugfixes (log messages and documentation):
21615 - Remove a confusing dollar sign from the example fingerprint in the
21616 man page, and also make the example fingerprint a valid one. Fixes
21617 bug 4309; bugfix on 0.2.1.3-alpha.
21618 - The next version of Windows will be called Windows 8, and it has
21619 a major version of 6, minor version of 2. Correctly identify that
21620 version instead of calling it "Very recent version". Resolves
21621 ticket 4153; reported by funkstar.
21622 - Downgrade log messages about circuit timeout calibration from
21623 "notice" to "info": they don't require or suggest any human
21624 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
21625 bugfix on 0.2.2.14-alpha.
21628 - Turn on directory request statistics by default and include them in
21629 extra-info descriptors. Don't break if we have no GeoIP database.
21630 Backported from 0.2.3.1-alpha; implements ticket 3951.
21631 - Update to the October 4 2011 Maxmind GeoLite Country database.
21634 Changes in version 0.2.1.31 - 2011-10-26
21635 Tor 0.2.1.31 backports important security and privacy fixes for
21636 oldstable. This release is intended only for package maintainers and
21637 others who cannot use the 0.2.2 stable series. All others should be
21638 using Tor 0.2.2.x or newer.
21640 o Security fixes (also included in 0.2.2.x):
21641 - Replace all potentially sensitive memory comparison operations
21642 with versions whose runtime does not depend on the data being
21643 compared. This will help resist a class of attacks where an
21644 adversary can use variations in timing information to learn
21645 sensitive data. Fix for one case of bug 3122. (Safe memcmp
21646 implementation by Robert Ransom based partially on code by DJB.)
21647 - Fix an assert in parsing router descriptors containing IPv6
21648 addresses. This one took down the directory authorities when
21649 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
21651 o Privacy/anonymity fixes (also included in 0.2.2.x):
21652 - Clients and bridges no longer send TLS certificate chains on
21653 outgoing OR connections. Previously, each client or bridge would
21654 use the same cert chain for all outgoing OR connections until
21655 its IP address changes, which allowed any relay that the client
21656 or bridge contacted to determine which entry guards it is using.
21657 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
21658 - If a relay receives a CREATE_FAST cell on a TLS connection, it
21659 no longer considers that connection as suitable for satisfying a
21660 circuit EXTEND request. Now relays can protect clients from the
21661 CVE-2011-2768 issue even if the clients haven't upgraded yet.
21662 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
21663 that they initiated. Relays could distinguish incoming bridge
21664 connections from client connections, creating another avenue for
21665 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
21666 Found by "frosty_un".
21667 - When receiving a hidden service descriptor, check that it is for
21668 the hidden service we wanted. Previously, Tor would store any
21669 hidden service descriptors that a directory gave it, whether it
21670 wanted them or not. This wouldn't have let an attacker impersonate
21671 a hidden service, but it did let directories pre-seed a client
21672 with descriptors that it didn't want. Bugfix on 0.0.6.
21673 - Avoid linkability based on cached hidden service descriptors: forget
21674 all hidden service descriptors cached as a client when processing a
21675 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
21676 - Make the bridge directory authority refuse to answer directory
21677 requests for "all" descriptors. It used to include bridge
21678 descriptors in its answer, which was a major information leak.
21679 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
21680 - Don't attach new streams to old rendezvous circuits after SIGNAL
21681 NEWNYM. Previously, we would keep using an existing rendezvous
21682 circuit if it remained open (i.e. if it were kept open by a
21683 long-lived stream, or if a new stream were attached to it before
21684 Tor could notice that it was old and no longer in use). Bugfix on
21685 0.1.1.15-rc; fixes bug 3375.
21687 o Minor bugfixes (also included in 0.2.2.x):
21688 - When we restart our relay, we might get a successful connection
21689 from the outside before we've started our reachability tests,
21690 triggering a warning: "ORPort found reachable, but I have no
21691 routerinfo yet. Failing to inform controller of success." This
21692 bug was harmless unless Tor is running under a controller
21693 like Vidalia, in which case the controller would never get a
21694 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
21696 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
21697 enabled. Fixes bug 1526.
21698 - Remove undocumented option "-F" from tor-resolve: it hasn't done
21699 anything since 0.2.1.16-rc.
21700 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
21701 None of the cases where we did this before were wrong, but by making
21702 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
21703 - Fix a rare crash bug that could occur when a client was configured
21704 with a large number of bridges. Fixes bug 2629; bugfix on
21705 0.2.1.2-alpha. Bugfix by trac user "shitlei".
21706 - Correct the warning displayed when a rendezvous descriptor exceeds
21707 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
21709 - Fix an uncommon assertion failure when running with DNSPort under
21710 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
21711 - When warning about missing zlib development packages during compile,
21712 give the correct package names. Bugfix on 0.2.0.1-alpha.
21713 - Require that introduction point keys and onion keys have public
21714 exponent 65537. Bugfix on 0.2.0.10-alpha.
21715 - Do not crash when our configuration file becomes unreadable, for
21716 example due to a permissions change, between when we start up
21717 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
21719 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
21721 - Always NUL-terminate the sun_path field of a sockaddr_un before
21722 passing it to the kernel. (Not a security issue: kernels are
21723 smart enough to reject bad sockaddr_uns.) Found by Coverity;
21724 CID #428. Bugfix on Tor 0.2.0.3-alpha.
21725 - Don't stack-allocate the list of supplementary GIDs when we're
21726 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
21727 could take up to 256K, which is way too much stack. Found by
21728 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
21730 o Minor bugfixes (only in 0.2.1.x):
21731 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
21732 rely on them. Bugfix on 0.2.1.30.
21733 - Use git revisions instead of svn revisions when generating our
21734 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
21736 o Minor features (also included in 0.2.2.x):
21737 - Adjust the expiration time on our SSL session certificates to
21738 better match SSL certs seen in the wild. Resolves ticket 4014.
21739 - Allow nameservers with IPv6 address. Resolves bug 2574.
21740 - Update to the October 4 2011 Maxmind GeoLite Country database.
21743 Changes in version 0.2.2.33 - 2011-09-13
21744 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
21745 TLS handshake that makes relays and bridges that run this new version
21746 reachable from Iran again.
21749 - Avoid an assertion failure when reloading a configuration with
21750 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
21751 3923; bugfix on 0.2.2.25-alpha.
21753 o Minor features (security):
21754 - Check for replays of the public-key encrypted portion of an
21755 INTRODUCE1 cell, in addition to the current check for replays of
21756 the g^x value. This prevents a possible class of active attacks
21757 by an attacker who controls both an introduction point and a
21758 rendezvous point, and who uses the malleability of AES-CTR to
21759 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
21760 that these attacks are infeasible (requiring the attacker to send
21761 on the order of zettabytes of altered cells in a short interval),
21762 but we'd rather block them off in case there are any classes of
21763 this attack that we missed. Reported by Willem Pinckaers.
21766 - Adjust the expiration time on our SSL session certificates to
21767 better match SSL certs seen in the wild. Resolves ticket 4014.
21768 - Change the default required uptime for a relay to be accepted as
21769 a HSDir (hidden service directory) from 24 hours to 25 hours.
21770 Improves on 0.2.0.10-alpha; resolves ticket 2649.
21771 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
21772 authorities to abstain from voting on assignment of the HSDir
21773 consensus flag. Related to bug 2649.
21774 - Update to the September 6 2011 Maxmind GeoLite Country database.
21776 o Minor bugfixes (documentation and log messages):
21777 - Correct the man page to explain that HashedControlPassword and
21778 CookieAuthentication can both be set, in which case either method
21779 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
21780 when we decided to allow these config options to both be set. Issue
21781 raised by bug 3898.
21782 - Demote the 'replay detected' log message emitted when a hidden
21783 service receives the same Diffie-Hellman public key in two different
21784 INTRODUCE2 cells to info level. A normal Tor client can cause that
21785 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
21786 fixes part of bug 2442.
21787 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
21788 level. There is nothing that a hidden service's operator can do
21789 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
21791 - Clarify a log message specifying the characters permitted in
21792 HiddenServiceAuthorizeClient client names. Previously, the log
21793 message said that "[A-Za-z0-9+-_]" were permitted; that could have
21794 given the impression that every ASCII character between "+" and "_"
21795 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
21798 - Provide a substitute implementation of lround() for MSVC, which
21799 apparently lacks it. Patch from Gisle Vanem.
21800 - Clean up some code issues that prevented Tor from building on older
21801 BSDs. Fixes bug 3894; reported by "grarpamp".
21802 - Search for a platform-specific version of "ar" when cross-compiling.
21803 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
21806 Changes in version 0.2.2.32 - 2011-08-27
21807 The Tor 0.2.2 release series is dedicated to the memory of Andreas
21808 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
21809 a founder of the PETS community, a leader in our field, a mentor,
21810 and a friend. He left us with these words: "I had the possibility
21811 to contribute to this world that is not as it should be. I hope I
21812 could help in some areas to make the world a better place, and that
21813 I could also encourage other people to be engaged in improving the
21814 world. Please, stay engaged. This world needs you, your love, your
21815 initiative -- now I cannot be part of that anymore."
21817 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
21818 ready. More than two years in the making, this release features improved
21819 client performance and hidden service reliability, better compatibility
21820 for Android, correct behavior for bridges that listen on more than
21821 one address, more extensible and flexible directory object handling,
21822 better reporting of network statistics, improved code security, and
21823 many many other features and bugfixes.
21825 o Major features (client performance):
21826 - When choosing which cells to relay first, relays now favor circuits
21827 that have been quiet recently, to provide lower latency for
21828 low-volume circuits. By default, relays enable or disable this
21829 feature based on a setting in the consensus. They can override
21830 this default by using the new "CircuitPriorityHalflife" config
21831 option. Design and code by Ian Goldberg, Can Tang, and Chris
21833 - Directory authorities now compute consensus weightings that instruct
21834 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
21835 and no flag. Clients use these weightings to distribute network load
21836 more evenly across these different relay types. The weightings are
21837 in the consensus so we can change them globally in the future. Extra
21838 thanks to "outofwords" for finding some nasty security bugs in
21839 the first implementation of this feature.
21841 o Major features (client performance, circuit build timeout):
21842 - Tor now tracks how long it takes to build client-side circuits
21843 over time, and adapts its timeout to local network performance.
21844 Since a circuit that takes a long time to build will also provide
21845 bad performance, we get significant latency improvements by
21846 discarding the slowest 20% of circuits. Specifically, Tor creates
21847 circuits more aggressively than usual until it has enough data
21848 points for a good timeout estimate. Implements proposal 151.
21849 - Circuit build timeout constants can be controlled by consensus
21850 parameters. We set good defaults for these parameters based on
21851 experimentation on broadband and simulated high-latency links.
21852 - Circuit build time learning can be disabled via consensus parameter
21853 or by the client via a LearnCircuitBuildTimeout config option. We
21854 also automatically disable circuit build time calculation if either
21855 AuthoritativeDirectory is set, or if we fail to write our state
21856 file. Implements ticket 1296.
21858 o Major features (relays use their capacity better):
21859 - Set SO_REUSEADDR socket option on all sockets, not just
21860 listeners. This should help busy exit nodes avoid running out of
21861 useable ports just because all the ports have been used in the
21862 near past. Resolves issue 2850.
21863 - Relays now save observed peak bandwidth throughput rates to their
21864 state file (along with total usage, which was already saved),
21865 so that they can determine their correct estimated bandwidth on
21866 restart. Resolves bug 1863, where Tor relays would reset their
21867 estimated bandwidth to 0 after restarting.
21868 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
21869 should give us approximately 40-50% more Guard-flagged nodes,
21870 improving the anonymity the Tor network can provide and also
21871 decreasing the dropoff in throughput that relays experience when
21872 they first get the Guard flag.
21873 - Directory authorities now take changes in router IP address and
21874 ORPort into account when determining router stability. Previously,
21875 if a router changed its IP or ORPort, the authorities would not
21876 treat it as having any downtime for the purposes of stability
21877 calculation, whereas clients would experience downtime since the
21878 change would take a while to propagate to them. Resolves issue 1035.
21879 - New AccelName and AccelDir options add support for dynamic OpenSSL
21880 hardware crypto acceleration engines.
21882 o Major features (relays control their load better):
21883 - Exit relays now try harder to block exit attempts from unknown
21884 relays, to make it harder for people to use them as one-hop proxies
21885 a la tortunnel. Controlled by the refuseunknownexits consensus
21886 parameter (currently enabled), or you can override it on your
21887 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
21888 based on a variant of proposal 163.
21889 - Add separate per-conn write limiting to go with the per-conn read
21890 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
21891 but never per-conn write limits.
21892 - New consensus params "bwconnrate" and "bwconnburst" to let us
21893 rate-limit client connections as they enter the network. It's
21894 controlled in the consensus so we can turn it on and off for
21895 experiments. It's starting out off. Based on proposal 163.
21897 o Major features (controllers):
21898 - Export GeoIP information on bridge usage to controllers even if we
21899 have not yet been running for 24 hours. Now Vidalia bridge operators
21900 can get more accurate and immediate feedback about their
21901 contributions to the network.
21902 - Add an __OwningControllerProcess configuration option and a
21903 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
21904 that when it exits, Tor will shut down. Implements feature 3049.
21906 o Major features (directory authorities):
21907 - Directory authorities now create, vote on, and serve multiple
21908 parallel formats of directory data as part of their voting process.
21909 Partially implements Proposal 162: "Publish the consensus in
21911 - Directory authorities now agree on and publish small summaries
21912 of router information that clients can use in place of regular
21913 server descriptors. This transition will allow Tor 0.2.3 clients
21914 to use far less bandwidth for downloading information about the
21915 network. Begins the implementation of Proposal 158: "Clients
21916 download consensus + microdescriptors".
21917 - The directory voting system is now extensible to use multiple hash
21918 algorithms for signatures and resource selection. Newer formats
21919 are signed with SHA256, with a possibility for moving to a better
21920 hash algorithm in the future.
21921 - Directory authorities can now vote on arbitrary integer values as
21922 part of the consensus process. This is designed to help set
21923 network-wide parameters. Implements proposal 167.
21925 o Major features and bugfixes (node selection):
21926 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
21927 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
21928 options. Previously, we had been ambiguous in describing what
21929 counted as an "exit" node, and what operations exactly "StrictNodes
21930 0" would permit. This created confusion when people saw nodes built
21931 through unexpected circuits, and made it hard to tell real bugs from
21932 surprises. Now the intended behavior is:
21933 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
21934 a node that delivers user traffic outside the Tor network.
21935 . "Entry", in the context of EntryNodes, means a node used as the
21936 first hop of a multihop circuit. It doesn't include direct
21937 connections to directory servers.
21938 . "ExcludeNodes" applies to all nodes.
21939 . "StrictNodes" changes the behavior of ExcludeNodes only. When
21940 StrictNodes is set, Tor should avoid all nodes listed in
21941 ExcludeNodes, even when it will make user requests fail. When
21942 StrictNodes is *not* set, then Tor should follow ExcludeNodes
21943 whenever it can, except when it must use an excluded node to
21944 perform self-tests, connect to a hidden service, provide a
21945 hidden service, fulfill a .exit request, upload directory
21946 information, or fetch directory information.
21947 Collectively, the changes to implement the behavior fix bug 1090.
21948 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
21949 change during a config reload, mark and discard all our origin
21950 circuits. This fix should address edge cases where we change the
21951 config options and but then choose a circuit that we created before
21953 - Make EntryNodes config option much more aggressive even when
21954 StrictNodes is not set. Before it would prepend your requested
21955 entrynodes to your list of guard nodes, but feel free to use others
21956 after that. Now it chooses only from your EntryNodes if any of
21957 those are available, and only falls back to others if a) they're
21958 all down and b) StrictNodes is not set.
21959 - Now we refresh your entry guards from EntryNodes at each consensus
21960 fetch -- rather than just at startup and then they slowly rot as
21961 the network changes.
21962 - Add support for the country code "{??}" in torrc options like
21963 ExcludeNodes, to indicate all routers of unknown country. Closes
21965 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
21966 a node is listed in both, it's treated as excluded.
21967 - ExcludeNodes now applies to directory nodes -- as a preference if
21968 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
21969 Don't exclude all the directory authorities and set StrictNodes to 1
21970 unless you really want your Tor to break.
21971 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
21972 - ExcludeExitNodes now overrides .exit requests.
21973 - We don't use bridges listed in ExcludeNodes.
21974 - When StrictNodes is 1:
21975 . We now apply ExcludeNodes to hidden service introduction points
21976 and to rendezvous points selected by hidden service users. This
21977 can make your hidden service less reliable: use it with caution!
21978 . If we have used ExcludeNodes on ourself, do not try relay
21979 reachability self-tests.
21980 . If we have excluded all the directory authorities, we will not
21981 even try to upload our descriptor if we're a relay.
21982 . Do not honor .exit requests to an excluded node.
21983 - When the set of permitted nodes changes, we now remove any mappings
21984 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
21986 - We never cannibalize a circuit that had excluded nodes on it, even
21987 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
21988 - Improve log messages related to excluded nodes.
21990 o Major features (misc):
21991 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
21992 to help Tor build correctly for Android phones.
21993 - The options SocksPort, ControlPort, and so on now all accept a
21994 value "auto" that opens a socket on an OS-selected port. A
21995 new ControlPortWriteToFile option tells Tor to write its
21996 actual control port or ports to a chosen file. If the option
21997 ControlPortFileGroupReadable is set, the file is created as
21998 group-readable. Now users can run two Tor clients on the same
21999 system without needing to manually mess with parameters. Resolves
22000 part of ticket 3076.
22001 - Tor now supports tunneling all of its outgoing connections over
22002 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
22003 configuration options. Code by Christopher Davis.
22005 o Code security improvements:
22006 - Replace all potentially sensitive memory comparison operations
22007 with versions whose runtime does not depend on the data being
22008 compared. This will help resist a class of attacks where an
22009 adversary can use variations in timing information to learn
22010 sensitive data. Fix for one case of bug 3122. (Safe memcmp
22011 implementation by Robert Ransom based partially on code by DJB.)
22012 - Enable Address Space Layout Randomization (ASLR) and Data Execution
22013 Prevention (DEP) by default on Windows to make it harder for
22014 attackers to exploit vulnerabilities. Patch from John Brooks.
22015 - New "--enable-gcc-hardening" ./configure flag (off by default)
22016 to turn on gcc compile time hardening options. It ensures
22017 that signed ints have defined behavior (-fwrapv), enables
22018 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
22019 with canaries (-fstack-protector-all), turns on ASLR protection if
22020 supported by the kernel (-fPIE, -pie), and adds additional security
22021 related warnings. Verified to work on Mac OS X and Debian Lenny.
22022 - New "--enable-linker-hardening" ./configure flag (off by default)
22023 to turn on ELF specific hardening features (relro, now). This does
22024 not work with Mac OS X or any other non-ELF binary format.
22025 - Always search the Windows system directory for system DLLs, and
22026 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
22027 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
22028 current and future memory pages via mlockall(). On supported
22029 platforms (modern Linux and probably BSD but not Windows or OS X),
22030 this should effectively disable any and all attempts to page out
22031 memory. This option requires that you start your Tor as root --
22032 if you use DisableAllSwap, please consider using the User option
22033 to properly reduce the privileges of your Tor.
22035 o Major bugfixes (crashes):
22036 - Fix crash bug on platforms where gmtime and localtime can return
22037 NULL. Windows 7 users were running into this one. Fixes part of bug
22038 2077. Bugfix on all versions of Tor. Found by boboper.
22039 - Introduce minimum/maximum values that clients will believe
22040 from the consensus. Now we'll have a better chance to avoid crashes
22041 or worse when a consensus param has a weird value.
22042 - Fix a rare crash bug that could occur when a client was configured
22043 with a large number of bridges. Fixes bug 2629; bugfix on
22044 0.2.1.2-alpha. Bugfix by trac user "shitlei".
22045 - Do not crash when our configuration file becomes unreadable, for
22046 example due to a permissions change, between when we start up
22047 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
22049 - If we're in the pathological case where there's no exit bandwidth
22050 but there is non-exit bandwidth, or no guard bandwidth but there
22051 is non-guard bandwidth, don't crash during path selection. Bugfix
22053 - Fix a crash bug when trying to initialize the evdns module in
22054 Libevent 2. Bugfix on 0.2.1.16-rc.
22056 o Major bugfixes (stability):
22057 - Fix an assert in parsing router descriptors containing IPv6
22058 addresses. This one took down the directory authorities when
22059 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
22060 - Fix an uncommon assertion failure when running with DNSPort under
22061 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
22062 - Treat an unset $HOME like an empty $HOME rather than triggering an
22063 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
22064 - More gracefully handle corrupt state files, removing asserts
22065 in favor of saving a backup and resetting state.
22066 - Instead of giving an assertion failure on an internal mismatch
22067 on estimated freelist size, just log a BUG warning and try later.
22068 Mitigates but does not fix bug 1125.
22069 - Fix an assert that got triggered when using the TestingTorNetwork
22070 configuration option and then issuing a GETINFO config-text control
22071 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
22072 - If the cached cert file is unparseable, warn but don't exit.
22074 o Privacy fixes (relays/bridges):
22075 - Don't list Windows capabilities in relay descriptors. We never made
22076 use of them, and maybe it's a bad idea to publish them. Bugfix
22078 - If the Nickname configuration option isn't given, Tor would pick a
22079 nickname based on the local hostname as the nickname for a relay.
22080 Because nicknames are not very important in today's Tor and the
22081 "Unnamed" nickname has been implemented, this is now problematic
22082 behavior: It leaks information about the hostname without being
22083 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
22084 introduced the Unnamed nickname. Reported by tagnaq.
22085 - Maintain separate TLS contexts and certificates for incoming and
22086 outgoing connections in bridge relays. Previously we would use the
22087 same TLS contexts and certs for incoming and outgoing connections.
22088 Bugfix on 0.2.0.3-alpha; addresses bug 988.
22089 - Maintain separate identity keys for incoming and outgoing TLS
22090 contexts in bridge relays. Previously we would use the same
22091 identity keys for incoming and outgoing TLS contexts. Bugfix on
22092 0.2.0.3-alpha; addresses the other half of bug 988.
22093 - Make the bridge directory authority refuse to answer directory
22094 requests for "all descriptors". It used to include bridge
22095 descriptors in its answer, which was a major information leak.
22096 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
22098 o Privacy fixes (clients):
22099 - When receiving a hidden service descriptor, check that it is for
22100 the hidden service we wanted. Previously, Tor would store any
22101 hidden service descriptors that a directory gave it, whether it
22102 wanted them or not. This wouldn't have let an attacker impersonate
22103 a hidden service, but it did let directories pre-seed a client
22104 with descriptors that it didn't want. Bugfix on 0.0.6.
22105 - Start the process of disabling ".exit" address notation, since it
22106 can be used for a variety of esoteric application-level attacks
22107 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
22109 - Reject attempts at the client side to open connections to private
22110 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
22111 a randomly chosen exit node. Attempts to do so are always
22112 ill-defined, generally prevented by exit policies, and usually
22113 in error. This will also help to detect loops in transparent
22114 proxy configurations. You can disable this feature by setting
22115 "ClientRejectInternalAddresses 0" in your torrc.
22116 - Log a notice when we get a new control connection. Now it's easier
22117 for security-conscious users to recognize when a local application
22118 is knocking on their controller door. Suggested by bug 1196.
22120 o Privacy fixes (newnym):
22121 - Avoid linkability based on cached hidden service descriptors: forget
22122 all hidden service descriptors cached as a client when processing a
22123 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
22124 - On SIGHUP, do not clear out all TrackHostExits mappings, client
22125 DNS cache entries, and virtual address mappings: that's what
22126 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
22127 - Don't attach new streams to old rendezvous circuits after SIGNAL
22128 NEWNYM. Previously, we would keep using an existing rendezvous
22129 circuit if it remained open (i.e. if it were kept open by a
22130 long-lived stream, or if a new stream were attached to it before
22131 Tor could notice that it was old and no longer in use). Bugfix on
22132 0.1.1.15-rc; fixes bug 3375.
22134 o Major bugfixes (relay bandwidth accounting):
22135 - Fix a bug that could break accounting on 64-bit systems with large
22136 time_t values, making them hibernate for impossibly long intervals.
22137 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
22138 - Fix a bug in bandwidth accounting that could make us use twice
22139 the intended bandwidth when our interval start changes due to
22140 daylight saving time. Now we tolerate skew in stored vs computed
22141 interval starts: if the start of the period changes by no more than
22142 50% of the period's duration, we remember bytes that we transferred
22143 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
22145 o Major bugfixes (bridges):
22146 - Bridges now use "reject *:*" as their default exit policy. Bugfix
22147 on 0.2.0.3-alpha. Fixes bug 1113.
22148 - If you configure your bridge with a known identity fingerprint,
22149 and the bridge authority is unreachable (as it is in at least
22150 one country now), fall back to directly requesting the descriptor
22151 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
22153 - Fix a bug where bridge users who configure the non-canonical
22154 address of a bridge automatically switch to its canonical
22155 address. If a bridge listens at more than one address, it
22156 should be able to advertise those addresses independently and
22157 any non-blocked addresses should continue to work. Bugfix on Tor
22158 0.2.0.3-alpha. Fixes bug 2510.
22159 - If you configure Tor to use bridge A, and then quit and
22160 configure Tor to use bridge B instead (or if you change Tor
22161 to use bridge B via the controller), it would happily continue
22162 to use bridge A if it's still reachable. While this behavior is
22163 a feature if your goal is connectivity, in some scenarios it's a
22164 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
22165 - When the controller configures a new bridge, don't wait 10 to 60
22166 seconds before trying to fetch its descriptor. Bugfix on
22167 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
22169 o Major bugfixes (directory authorities):
22170 - Many relays have been falling out of the consensus lately because
22171 not enough authorities know about their descriptor for them to get
22172 a majority of votes. When we deprecated the v2 directory protocol,
22173 we got rid of the only way that v3 authorities can hear from each
22174 other about other descriptors. Now authorities examine every v3
22175 vote for new descriptors, and fetch them from that authority. Bugfix
22177 - Authorities could be tricked into giving out the Exit flag to relays
22178 that didn't allow exiting to any ports. This bug could screw
22179 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
22180 1238. Bug discovered by Martin Kowalczyk.
22181 - If all authorities restart at once right before a consensus vote,
22182 nobody will vote about "Running", and clients will get a consensus
22183 with no usable relays. Instead, authorities refuse to build a
22184 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
22186 o Major bugfixes (stream-level fairness):
22187 - When receiving a circuit-level SENDME for a blocked circuit, try
22188 to package cells fairly from all the streams that had previously
22189 been blocked on that circuit. Previously, we had started with the
22190 oldest stream, and allowed each stream to potentially exhaust
22191 the circuit's package window. This gave older streams on any
22192 given circuit priority over newer ones. Fixes bug 1937. Detected
22193 originally by Camilo Viecco. This bug was introduced before the
22194 first Tor release, in svn commit r152: it is the new winner of
22195 the longest-lived bug prize.
22196 - Fix a stream fairness bug that would cause newer streams on a given
22197 circuit to get preference when reading bytes from the origin or
22198 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
22199 introduced before the first Tor release, in svn revision r152.
22200 - When the exit relay got a circuit-level sendme cell, it started
22201 reading on the exit streams, even if had 500 cells queued in the
22202 circuit queue already, so the circuit queue just grew and grew in
22203 some cases. We fix this by not re-enabling reading on receipt of a
22204 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
22205 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
22207 - Newly created streams were allowed to read cells onto circuits,
22208 even if the circuit's cell queue was blocked and waiting to drain.
22209 This created potential unfairness, as older streams would be
22210 blocked, but newer streams would gladly fill the queue completely.
22211 We add code to detect this situation and prevent any stream from
22212 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
22215 o Major bugfixes (hidden services):
22216 - Apply circuit timeouts to opened hidden-service-related circuits
22217 based on the correct start time. Previously, we would apply the
22218 circuit build timeout based on time since the circuit's creation;
22219 it was supposed to be applied based on time since the circuit
22220 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
22221 - Improve hidden service robustness: When we find that we have
22222 extended a hidden service's introduction circuit to a relay not
22223 listed as an introduction point in the HS descriptor we currently
22224 have, retry with an introduction point from the current
22225 descriptor. Previously we would just give up. Fixes bugs 1024 and
22226 1930; bugfix on 0.2.0.10-alpha.
22227 - Directory authorities now use data collected from their own
22228 uptime observations when choosing whether to assign the HSDir flag
22229 to relays, instead of trusting the uptime value the relay reports in
22230 its descriptor. This change helps prevent an attack where a small
22231 set of nodes with frequently-changing identity keys can blackhole
22232 a hidden service. (Only authorities need upgrade; others will be
22233 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
22234 - Stop assigning the HSDir flag to relays that disable their
22235 DirPort (and thus will refuse to answer directory requests). This
22236 fix should dramatically improve the reachability of hidden services:
22237 hidden services and hidden service clients pick six HSDir relays
22238 to store and retrieve the hidden service descriptor, and currently
22239 about half of the HSDir relays will refuse to work. Bugfix on
22240 0.2.0.10-alpha; fixes part of bug 1693.
22242 o Major bugfixes (misc):
22243 - Clients now stop trying to use an exit node associated with a given
22244 destination by TrackHostExits if they fail to reach that exit node.
22245 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
22246 - Fix a regression that caused Tor to rebind its ports if it receives
22247 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
22248 - Remove an extra pair of quotation marks around the error
22249 message in control-port STATUS_GENERAL BUG events. Bugfix on
22250 0.1.2.6-alpha; fixes bug 3732.
22252 o Minor features (relays):
22253 - Ensure that no empty [dirreq-](read|write)-history lines are added
22254 to an extrainfo document. Implements ticket 2497.
22255 - When bandwidth accounting is enabled, be more generous with how
22256 much bandwidth we'll use up before entering "soft hibernation".
22257 Previously, we'd refuse new connections and circuits once we'd
22258 used up 95% of our allotment. Now, we use up 95% of our allotment,
22259 AND make sure that we have no more than 500MB (or 3 hours of
22260 expected traffic, whichever is lower) remaining before we enter
22262 - Relays now log the reason for publishing a new relay descriptor,
22263 so we have a better chance of hunting down instances of bug 1810.
22264 Resolves ticket 3252.
22265 - Log a little more clearly about the times at which we're no longer
22266 accepting new connections (e.g. due to hibernating). Resolves
22268 - When AllowSingleHopExits is set, print a warning to explain to the
22269 relay operator why most clients are avoiding her relay.
22270 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
22271 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
22272 clients are already deprecated because of security bugs.
22274 o Minor features (network statistics):
22275 - Directory mirrors that set "DirReqStatistics 1" write statistics
22276 about directory requests to disk every 24 hours. As compared to the
22277 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
22278 improvements: 1) stats are written to disk exactly every 24 hours;
22279 2) estimated shares of v2 and v3 requests are determined as mean
22280 values, not at the end of a measurement period; 3) unresolved
22281 requests are listed with country code '??'; 4) directories also
22282 measure download times.
22283 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
22284 number of exit streams and transferred bytes per port to disk every
22286 - Relays that set "CellStatistics 1" write statistics on how long
22287 cells spend in their circuit queues to disk every 24 hours.
22288 - Entry nodes that set "EntryStatistics 1" write statistics on the
22289 rough number and origins of connecting clients to disk every 24
22291 - Relays that write any of the above statistics to disk and set
22292 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
22293 their extra-info documents. Implements proposal 166.
22295 o Minor features (GeoIP and statistics):
22296 - Provide a log message stating which geoip file we're parsing
22297 instead of just stating that we're parsing the geoip file.
22298 Implements ticket 2432.
22299 - Make sure every relay writes a state file at least every 12 hours.
22300 Previously, a relay could go for weeks without writing its state
22301 file, and on a crash could lose its bandwidth history, capacity
22302 estimates, client country statistics, and so on. Addresses bug 3012.
22303 - Relays report the number of bytes spent on answering directory
22304 requests in extra-info descriptors similar to {read,write}-history.
22305 Implements enhancement 1790.
22306 - Report only the top 10 ports in exit-port stats in order not to
22307 exceed the maximum extra-info descriptor length of 50 KB. Implements
22309 - If writing the state file to disk fails, wait up to an hour before
22310 retrying again, rather than trying again each second. Fixes bug
22311 2346; bugfix on Tor 0.1.1.3-alpha.
22312 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
22313 when we switch from being a public relay to a bridge. Otherwise
22314 there will still be clients that see the relay in their consensus,
22315 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
22317 - Update to the August 2 2011 Maxmind GeoLite Country database.
22319 o Minor features (clients):
22320 - When expiring circuits, use microsecond timers rather than
22321 one-second timers. This can avoid an unpleasant situation where a
22322 circuit is launched near the end of one second and expired right
22323 near the beginning of the next, and prevent fluctuations in circuit
22325 - If we've configured EntryNodes and our network goes away and/or all
22326 our entrynodes get marked down, optimistically retry them all when
22327 a new socks application request appears. Fixes bug 1882.
22328 - Always perform router selections using weighted relay bandwidth,
22329 even if we don't need a high capacity circuit at the time. Non-fast
22330 circuits now only differ from fast ones in that they can use relays
22331 not marked with the Fast flag. This "feature" could turn out to
22332 be a horrible bug; we should investigate more before it goes into
22334 - When we run out of directory information such that we can't build
22335 circuits, but then get enough that we can build circuits, log when
22336 we actually construct a circuit, so the user has a better chance of
22337 knowing what's going on. Fixes bug 1362.
22338 - Log SSL state transitions at debug level during handshake, and
22339 include SSL states in error messages. This may help debug future
22340 SSL handshake issues.
22342 o Minor features (directory authorities):
22343 - When a router changes IP address or port, authorities now launch
22344 a new reachability test for it. Implements ticket 1899.
22345 - Directory authorities now reject relays running any versions of
22346 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
22347 known bugs that keep RELAY_EARLY cells from working on rendezvous
22348 circuits. Followup to fix for bug 2081.
22349 - Directory authorities now reject relays running any version of Tor
22350 older than 0.2.0.26-rc. That version is the earliest that fetches
22351 current directory information correctly. Fixes bug 2156.
22352 - Directory authorities now do an immediate reachability check as soon
22353 as they hear about a new relay. This change should slightly reduce
22354 the time between setting up a relay and getting listed as running
22355 in the consensus. It should also improve the time between setting
22356 up a bridge and seeing use by bridge users.
22357 - Directory authorities no longer launch a TLS connection to every
22358 relay as they startup. Now that we have 2k+ descriptors cached,
22359 the resulting network hiccup is becoming a burden. Besides,
22360 authorities already avoid voting about Running for the first half
22361 hour of their uptime.
22362 - Directory authorities now log the source of a rejected POSTed v3
22363 networkstatus vote, so we can track failures better.
22364 - Backport code from 0.2.3.x that allows directory authorities to
22365 clean their microdescriptor caches. Needed to resolve bug 2230.
22367 o Minor features (hidden services):
22368 - Use computed circuit-build timeouts to decide when to launch
22369 parallel introduction circuits for hidden services. (Previously,
22370 we would retry after 15 seconds.)
22371 - Don't allow v0 hidden service authorities to act as clients.
22372 Required by fix for bug 3000.
22373 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
22374 by fix for bug 3000.
22375 - Make hidden services work better in private Tor networks by not
22376 requiring any uptime to join the hidden service descriptor
22377 DHT. Implements ticket 2088.
22378 - Log (at info level) when purging pieces of hidden-service-client
22379 state because of SIGNAL NEWNYM.
22381 o Minor features (controller interface):
22382 - New "GETINFO net/listeners/(type)" controller command to return
22383 a list of addresses and ports that are bound for listeners for a
22384 given connection type. This is useful when the user has configured
22385 "SocksPort auto" and the controller needs to know which port got
22386 chosen. Resolves another part of ticket 3076.
22387 - Have the controller interface give a more useful message than
22388 "Internal Error" in response to failed GETINFO requests.
22389 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
22390 event, to give information on the current rate of circuit timeouts
22391 over our stored history.
22392 - The 'EXTENDCIRCUIT' control port command can now be used with
22393 a circ id of 0 and no path. This feature will cause Tor to build
22394 a new 'fast' general purpose circuit using its own path selection
22396 - Added a BUILDTIMEOUT_SET controller event to describe changes
22397 to the circuit build timeout.
22398 - New controller command "getinfo config-text". It returns the
22399 contents that Tor would write if you send it a SAVECONF command,
22400 so the controller can write the file to disk itself.
22402 o Minor features (controller protocol):
22403 - Add a new ControlSocketsGroupWritable configuration option: when
22404 it is turned on, ControlSockets are group-writeable by the default
22405 group of the current user. Patch by Jérémy Bobbio; implements
22407 - Tor now refuses to create a ControlSocket in a directory that is
22408 world-readable (or group-readable if ControlSocketsGroupWritable
22409 is 0). This is necessary because some operating systems do not
22410 enforce permissions on an AF_UNIX sockets. Permissions on the
22411 directory holding the socket, however, seems to work everywhere.
22412 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
22413 not. This would lead to a cookie that is still not group readable.
22414 Closes bug 1843. Suggested by katmagic.
22415 - Future-proof the controller protocol a bit by ignoring keyword
22416 arguments we do not recognize.
22418 o Minor features (more useful logging):
22419 - Revise most log messages that refer to nodes by nickname to
22420 instead use the "$key=nickname at address" format. This should be
22421 more useful, especially since nicknames are less and less likely
22422 to be unique. Resolves ticket 3045.
22423 - When an HTTPS proxy reports "403 Forbidden", we now explain
22424 what it means rather than calling it an unexpected status code.
22425 Closes bug 2503. Patch from Michael Yakubovich.
22426 - Rate-limit a warning about failures to download v2 networkstatus
22427 documents. Resolves part of bug 1352.
22428 - Rate-limit the "your application is giving Tor only an IP address"
22429 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
22430 - Rate-limit "Failed to hand off onionskin" warnings.
22431 - When logging a rate-limited warning, we now mention how many messages
22432 got suppressed since the last warning.
22433 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
22434 2 no signature, 4 required" messages about consensus signatures
22435 easier to read, and make sure they get logged at the same severity
22436 as the messages explaining which keys are which. Fixes bug 1290.
22437 - Don't warn when we have a consensus that we can't verify because
22438 of missing certificates, unless those certificates are ones
22439 that we have been trying and failing to download. Fixes bug 1145.
22441 o Minor features (log domains):
22442 - Add documentation for configuring logging at different severities in
22443 different log domains. We've had this feature since 0.2.1.1-alpha,
22444 but for some reason it never made it into the manpage. Fixes
22446 - Make it simpler to specify "All log domains except for A and B".
22447 Previously you needed to say "[*,~A,~B]". Now you can just say
22449 - Add a "LogMessageDomains 1" option to include the domains of log
22450 messages along with the messages. Without this, there's no way
22451 to use log domains without reading the source or doing a lot
22453 - Add a new "Handshake" log domain for activities that happen
22454 during the TLS handshake.
22456 o Minor features (build process):
22457 - Make compilation with clang possible when using
22458 "--enable-gcc-warnings" by removing two warning options that clang
22459 hasn't implemented yet and by fixing a few warnings. Resolves
22461 - Detect platforms that brokenly use a signed size_t, and refuse to
22462 build there. Found and analyzed by doorss and rransom.
22463 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
22465 - Add support for statically linking zlib by specifying
22466 "--enable-static-zlib", to go with our support for statically
22467 linking openssl and libevent. Resolves bug 1358.
22468 - Instead of adding the svn revision to the Tor version string, report
22469 the git commit (when we're building from a git checkout).
22470 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
22472 - New --digests command-line switch to output the digests of the
22473 source files Tor was built with.
22474 - Generate our manpage and HTML documentation using Asciidoc. This
22475 change should make it easier to maintain the documentation, and
22476 produce nicer HTML. The build process fails if asciidoc cannot
22477 be found and building with asciidoc isn't disabled (via the
22478 "--disable-asciidoc" argument to ./configure. Skipping the manpage
22479 speeds up the build considerably.
22481 o Minor features (options / torrc):
22482 - Warn when the same option is provided more than once in a torrc
22483 file, on the command line, or in a single SETCONF statement, and
22484 the option is one that only accepts a single line. Closes bug 1384.
22485 - Warn when the user configures two HiddenServiceDir lines that point
22486 to the same directory. Bugfix on 0.0.6 (the version introducing
22487 HiddenServiceDir); fixes bug 3289.
22488 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
22489 do individual connection-level rate limiting of clients. The torrc
22490 config options with the same names trump the consensus params, if
22491 both are present. Replaces the old "bwconnrate" and "bwconnburst"
22492 consensus params which were broken from 0.2.2.7-alpha through
22493 0.2.2.14-alpha. Closes bug 1947.
22494 - New config option "WarnUnsafeSocks 0" disables the warning that
22495 occurs whenever Tor receives a socks handshake using a version of
22496 the socks protocol that can only provide an IP address (rather
22497 than a hostname). Setups that do DNS locally over Tor are fine,
22498 and we shouldn't spam the logs in that case.
22499 - New config option "CircuitStreamTimeout" to override our internal
22500 timeout schedule for how many seconds until we detach a stream from
22501 a circuit and try a new circuit. If your network is particularly
22502 slow, you might want to set this to a number like 60.
22503 - New options for SafeLogging to allow scrubbing only log messages
22504 generated while acting as a relay. Specify "SafeLogging relay" if
22505 you want to ensure that only messages known to originate from
22506 client use of the Tor process will be logged unsafely.
22507 - Time and memory units in the configuration file can now be set to
22508 fractional units. For example, "2.5 GB" is now a valid value for
22510 - Support line continuations in the torrc config file. If a line
22511 ends with a single backslash character, the newline is ignored, and
22512 the configuration value is treated as continuing on the next line.
22515 o Minor features (unit tests):
22516 - Revise our unit tests to use the "tinytest" framework, so we
22517 can run tests in their own processes, have smarter setup/teardown
22518 code, and so on. The unit test code has moved to its own
22519 subdirectory, and has been split into multiple modules.
22520 - Add a unit test for cross-platform directory-listing code.
22521 - Add some forgotten return value checks during unit tests. Found
22523 - Use GetTempDir to find the proper temporary directory location on
22524 Windows when generating temporary files for the unit tests. Patch
22527 o Minor features (misc):
22528 - The "torify" script now uses torsocks where available.
22529 - Make Libevent log messages get delivered to controllers later,
22530 and not from inside the Libevent log handler. This prevents unsafe
22531 reentrant Libevent calls while still letting the log messages
22533 - Certain Tor clients (such as those behind check.torproject.org) may
22534 want to fetch the consensus in an extra early manner. To enable this
22535 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
22536 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
22537 as only certain clients who must have this information sooner should
22539 - Expand homedirs passed to tor-checkkey. This should silence a
22540 coverity complaint about passing a user-supplied string into
22541 open() without checking it.
22542 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
22543 used on bridges, and it makes bridge scanning somewhat easier.
22544 - Create the /var/run/tor directory on startup on OpenSUSE if it is
22545 not already created. Patch from Andreas Stieger. Fixes bug 2573.
22547 o Minor bugfixes (relays):
22548 - When a relay decides that its DNS is too broken for it to serve
22549 as an exit server, it advertised itself as a non-exit, but
22550 continued to act as an exit. This could create accidental
22551 partitioning opportunities for users. Instead, if a relay is
22552 going to advertise reject *:* as its exit policy, it should
22553 really act with exit policy "reject *:*". Fixes bug 2366.
22554 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
22555 - Publish a router descriptor even if generating an extra-info
22556 descriptor fails. Previously we would not publish a router
22557 descriptor without an extra-info descriptor; this can cause fast
22558 exit relays collecting exit-port statistics to drop from the
22559 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
22560 - When we're trying to guess whether we know our IP address as
22561 a relay, we would log various ways that we failed to guess
22562 our address, but never log that we ended up guessing it
22563 successfully. Now add a log line to help confused and anxious
22564 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
22565 - For bandwidth accounting, calculate our expected bandwidth rate
22566 based on the time during which we were active and not in
22567 soft-hibernation during the last interval. Previously, we were
22568 also considering the time spent in soft-hibernation. If this
22569 was a long time, we would wind up underestimating our bandwidth
22570 by a lot, and skewing our wakeup time towards the start of the
22571 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
22572 - Demote a confusing TLS warning that relay operators might get when
22573 someone tries to talk to their ORPort. It is not the operator's
22574 fault, nor can they do anything about it. Fixes bug 1364; bugfix
22576 - Change "Application request when we're believed to be offline."
22577 notice to "Application request when we haven't used client
22578 functionality lately.", to clarify that it's not an error. Bugfix
22579 on 0.0.9.3; fixes bug 1222.
22581 o Minor bugfixes (bridges):
22582 - When a client starts or stops using bridges, never use a circuit
22583 that was built before the configuration change. This behavior could
22584 put at risk a user who uses bridges to ensure that her traffic
22585 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
22587 - Do not reset the bridge descriptor download status every time we
22588 re-parse our configuration or get a configuration change. Fixes
22589 bug 3019; bugfix on 0.2.0.3-alpha.
22590 - Users couldn't configure a regular relay to be their bridge. It
22591 didn't work because when Tor fetched the bridge descriptor, it found
22592 that it already had it, and didn't realize that the purpose of the
22593 descriptor had changed. Now we replace routers with a purpose other
22594 than bridge with bridge descriptors when fetching them. Bugfix on
22595 0.1.1.9-alpha. Fixes bug 1776.
22596 - In the special case where you configure a public exit relay as your
22597 bridge, Tor would be willing to use that exit relay as the last
22598 hop in your circuit as well. Now we fail that circuit instead.
22599 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
22601 o Minor bugfixes (clients):
22602 - We now ask the other side of a stream (the client or the exit)
22603 for more data on that stream when the amount of queued data on
22604 that stream dips low enough. Previously, we wouldn't ask the
22605 other side for more data until either it sent us more data (which
22606 it wasn't supposed to do if it had exhausted its window!) or we
22607 had completely flushed all our queued data. This flow control fix
22608 should improve throughput. Fixes bug 2756; bugfix on the earliest
22609 released versions of Tor (svn commit r152).
22610 - When a client finds that an origin circuit has run out of 16-bit
22611 stream IDs, we now mark it as unusable for new streams. Previously,
22612 we would try to close the entire circuit. Bugfix on 0.0.6.
22613 - Make it explicit that we don't cannibalize one-hop circuits. This
22614 happens in the wild, but doesn't turn out to be a problem because
22615 we fortunately don't use those circuits. Many thanks to outofwords
22616 for the initial analysis and to swissknife who confirmed that
22617 two-hop circuits are actually created.
22618 - Resolve an edge case in path weighting that could make us misweight
22619 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
22620 - Make the DNSPort option work with libevent 2.x. Don't alter the
22621 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
22623 o Minor bugfixes (directory authorities):
22624 - Make directory authorities more accurate at recording when
22625 relays that have failed several reachability tests became
22626 unreachable, so we can provide more accuracy at assigning Stable,
22627 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
22628 - Directory authorities are now more robust to hops back in time
22629 when calculating router stability. Previously, if a run of uptime
22630 or downtime appeared to be negative, the calculation could give
22631 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
22633 - Directory authorities will now attempt to download consensuses
22634 if their own efforts to make a live consensus have failed. This
22635 change means authorities that restart will fetch a valid
22636 consensus, and it means authorities that didn't agree with the
22637 current consensus will still fetch and serve it if it has enough
22638 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
22639 - Never vote for a server as "Running" if we have a descriptor for
22640 it claiming to be hibernating, and that descriptor was published
22641 more recently than our last contact with the server. Bugfix on
22642 0.2.0.3-alpha; fixes bug 911.
22643 - Directory authorities no longer change their opinion of, or vote on,
22644 whether a router is Running, unless they have themselves been
22645 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
22648 o Minor bugfixes (hidden services):
22649 - Log malformed requests for rendezvous descriptors as protocol
22650 warnings, not warnings. Also, use a more informative log message
22651 in case someone sees it at log level warning without prior
22652 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
22653 - Accept hidden service descriptors if we think we might be a hidden
22654 service directory, regardless of what our consensus says. This
22655 helps robustness, since clients and hidden services can sometimes
22656 have a more up-to-date view of the network consensus than we do,
22657 and if they think that the directory authorities list us a HSDir,
22658 we might actually be one. Related to bug 2732; bugfix on
22660 - Correct the warning displayed when a rendezvous descriptor exceeds
22661 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
22663 - Clients and hidden services now use HSDir-flagged relays for hidden
22664 service descriptor downloads and uploads even if the relays have no
22665 DirPort set and the client has disabled TunnelDirConns. This will
22666 eventually allow us to give the HSDir flag to relays with no
22667 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
22668 - Only limit the lengths of single HS descriptors, even when multiple
22669 HS descriptors are published to an HSDir relay in a single POST
22670 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
22672 o Minor bugfixes (controllers):
22673 - Allow GETINFO fingerprint to return a fingerprint even when
22674 we have not yet built a router descriptor. Fixes bug 3577;
22675 bugfix on 0.2.0.1-alpha.
22676 - Send a SUCCEEDED stream event to the controller when a reverse
22677 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
22678 discovered by katmagic.
22679 - Remove a trailing asterisk from "exit-policy/default" in the
22680 output of the control port command "GETINFO info/names". Bugfix
22682 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
22683 2917. Bugfix on 0.1.1.1-alpha.
22684 - When we restart our relay, we might get a successful connection
22685 from the outside before we've started our reachability tests,
22686 triggering a warning: "ORPort found reachable, but I have no
22687 routerinfo yet. Failing to inform controller of success." This
22688 bug was harmless unless Tor is running under a controller
22689 like Vidalia, in which case the controller would never get a
22690 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
22692 - When a controller changes TrackHostExits, remove mappings for
22693 hosts that should no longer have their exits tracked. Bugfix on
22695 - When a controller changes VirtualAddrNetwork, remove any mappings
22696 for hosts that were automapped to the old network. Bugfix on
22698 - When a controller changes one of the AutomapHosts* options, remove
22699 any mappings for hosts that should no longer be automapped. Bugfix
22701 - Fix an off-by-one error in calculating some controller command
22702 argument lengths. Fortunately, this mistake is harmless since
22703 the controller code does redundant NUL termination too. Found by
22704 boboper. Bugfix on 0.1.1.1-alpha.
22705 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
22706 would return "551 Internal error" rather than "552 Unrecognized key
22707 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
22708 - Don't spam the controller with events when we have no file
22709 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
22710 for log messages was already solved from bug 748.)
22711 - Emit a GUARD DROPPED controller event for a case we missed.
22712 - Ensure DNS requests launched by "RESOLVE" commands from the
22713 controller respect the __LeaveStreamsUnattached setconf options. The
22714 same goes for requests launched via DNSPort or transparent
22715 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
22717 o Minor bugfixes (config options):
22718 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
22719 Change the limit to 512 characters by removing base64 newlines.
22720 Fixes bug 2752. Fix by Michael Yakubovich.
22721 - Complain if PublishServerDescriptor is given multiple arguments that
22722 include 0 or 1. This configuration will be rejected in the future.
22723 Bugfix on 0.2.0.1-alpha; closes bug 1107.
22724 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
22725 Bugfix on 0.2.0.13-alpha; closes bug 928.
22727 o Minor bugfixes (log subsystem fixes):
22728 - When unable to format an address as a string, report its value
22729 as "???" rather than reusing the last formatted address. Bugfix
22731 - Be more consistent in our treatment of file system paths. "~" should
22732 get expanded to the user's home directory in the Log config option.
22733 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
22734 feature for the -f and --DataDirectory options.
22736 o Minor bugfixes (memory management):
22737 - Don't stack-allocate the list of supplementary GIDs when we're
22738 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
22739 could take up to 256K, which is way too much stack. Found by
22740 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
22741 - Save a couple bytes in memory allocation every time we escape
22742 certain characters in a string. Patch from Florian Zumbiehl.
22744 o Minor bugfixes (protocol correctness):
22745 - When checking for 1024-bit keys, check for 1024 bits, not 128
22746 bytes. This allows Tor to correctly discard keys of length 1017
22747 through 1023. Bugfix on 0.0.9pre5.
22748 - Require that introduction point keys and onion handshake keys
22749 have a public exponent of 65537. Starts to fix bug 3207; bugfix
22751 - Handle SOCKS messages longer than 128 bytes long correctly, rather
22752 than waiting forever for them to finish. Fixes bug 2330; bugfix
22753 on 0.2.0.16-alpha. Found by doorss.
22754 - Never relay a cell for a circuit we have already destroyed.
22755 Between marking a circuit as closeable and finally closing it,
22756 it may have been possible for a few queued cells to get relayed,
22757 even though they would have been immediately dropped by the next
22758 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
22759 - Never queue a cell for a circuit that's already been marked
22761 - Fix a spec conformance issue: the network-status-version token
22762 must be the first token in a v3 consensus or vote. Discovered by
22763 "parakeep". Bugfix on 0.2.0.3-alpha.
22764 - A networkstatus vote must contain exactly one signature. Spec
22765 conformance issue. Bugfix on 0.2.0.3-alpha.
22766 - When asked about a DNS record type we don't support via a
22767 client DNSPort, reply with NOTIMPL rather than an empty
22768 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
22769 - Make more fields in the controller protocol case-insensitive, since
22770 control-spec.txt said they were.
22772 o Minor bugfixes (log messages):
22773 - Fix a log message that said "bits" while displaying a value in
22774 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
22776 - Downgrade "no current certificates known for authority" message from
22777 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
22778 - Correctly describe errors that occur when generating a TLS object.
22779 Previously we would attribute them to a failure while generating a
22780 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
22782 - Fix an instance where a Tor directory mirror might accidentally
22783 log the IP address of a misbehaving Tor client. Bugfix on
22785 - Stop logging at severity 'warn' when some other Tor client tries
22786 to establish a circuit with us using weak DH keys. It's a protocol
22787 violation, but that doesn't mean ordinary users need to hear about
22788 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
22789 - If your relay can't keep up with the number of incoming create
22790 cells, it would log one warning per failure into your logs. Limit
22791 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
22793 o Minor bugfixes (build fixes):
22794 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
22795 - When warning about missing zlib development packages during compile,
22796 give the correct package names. Bugfix on 0.2.0.1-alpha.
22797 - Fix warnings that newer versions of autoconf produce during
22798 ./autogen.sh. These warnings appear to be harmless in our case,
22799 but they were extremely verbose. Fixes bug 2020.
22800 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
22803 o Minor bugfixes (portability):
22804 - Write several files in text mode, on OSes that distinguish text
22805 mode from binary mode (namely, Windows). These files are:
22806 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
22807 that collect those statistics; 'client_keys' and 'hostname' for
22808 hidden services that use authentication; and (in the tor-gencert
22809 utility) newly generated identity and signing keys. Previously,
22810 we wouldn't specify text mode or binary mode, leading to an
22811 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
22812 the DirRecordUsageByCountry option which would have triggered
22813 the assertion failure was added), although this assertion failure
22814 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
22815 - Selectively disable deprecation warnings on OS X because Lion
22816 started deprecating the shipped copy of openssl. Fixes bug 3643.
22817 - Use a wide type to hold sockets when built for 64-bit Windows.
22819 - Fix an issue that prevented static linking of libevent on
22820 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
22821 where we introduced the "--with-static-libevent" configure option.
22822 - Fix a bug with our locking implementation on Windows that couldn't
22823 correctly detect when a file was already locked. Fixes bug 2504,
22824 bugfix on 0.2.1.6-alpha.
22825 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
22827 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
22828 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
22831 o Minor bugfixes (code correctness):
22832 - Always NUL-terminate the sun_path field of a sockaddr_un before
22833 passing it to the kernel. (Not a security issue: kernels are
22834 smart enough to reject bad sockaddr_uns.) Found by Coverity;
22835 CID #428. Bugfix on Tor 0.2.0.3-alpha.
22836 - Make connection_printf_to_buf()'s behavior sane. Its callers
22837 expect it to emit a CRLF iff the format string ends with CRLF;
22838 it actually emitted a CRLF iff (a) the format string ended with
22839 CRLF or (b) the resulting string was over 1023 characters long or
22840 (c) the format string did not end with CRLF *and* the resulting
22841 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
22842 fixes part of bug 3407.
22843 - Make send_control_event_impl()'s behavior sane. Its callers
22844 expect it to always emit a CRLF at the end of the string; it
22845 might have emitted extra control characters as well. Bugfix on
22846 0.1.1.9-alpha; fixes another part of bug 3407.
22847 - Make crypto_rand_int() check the value of its input correctly.
22848 Previously, it accepted values up to UINT_MAX, but could return a
22849 negative number if given a value above INT_MAX+1. Found by George
22850 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
22851 - Fix a potential null-pointer dereference while computing a
22852 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
22854 - If we fail to compute the identity digest of a v3 legacy keypair,
22855 warn, and don't use a buffer-full of junk instead. Bugfix on
22856 0.2.1.1-alpha; fixes bug 3106.
22857 - Resolve an untriggerable issue in smartlist_string_num_isin(),
22858 where if the function had ever in the future been used to check
22859 for the presence of a too-large number, it would have given an
22860 incorrect result. (Fortunately, we only used it for 16-bit
22861 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
22862 - Be more careful about reporting the correct error from a failed
22863 connect() system call. Under some circumstances, it was possible to
22864 look at an incorrect value for errno when sending the end reason.
22865 Bugfix on 0.1.0.1-rc.
22866 - Correctly handle an "impossible" overflow cases in connection byte
22867 counting, where we write or read more than 4GB on an edge connection
22868 in a single second. Bugfix on 0.1.2.8-beta.
22869 - Avoid a double mark-for-free warning when failing to attach a
22870 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
22872 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
22873 found by "cypherpunks". This bug was introduced before the first
22874 Tor release, in svn commit r110.
22875 - Fix a bug in bandwidth history state parsing that could have been
22876 triggered if a future version of Tor ever changed the timing
22877 granularity at which bandwidth history is measured. Bugfix on
22878 Tor 0.1.1.11-alpha.
22879 - Add assertions to check for overflow in arguments to
22880 base32_encode() and base32_decode(); fix a signed-unsigned
22881 comparison there too. These bugs are not actually reachable in Tor,
22882 but it's good to prevent future errors too. Found by doorss.
22883 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
22885 - Set target port in get_interface_address6() correctly. Bugfix
22886 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
22887 - Fix an impossible-to-actually-trigger buffer overflow in relay
22888 descriptor generation. Bugfix on 0.1.0.15.
22889 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
22891 o Minor bugfixes (code improvements):
22892 - After we free an internal connection structure, overwrite it
22893 with a different memory value than we use for overwriting a freed
22894 internal circuit structure. Should help with debugging. Suggested
22896 - If OpenSSL fails to make a duplicate of a private or public key, log
22897 an error message and try to exit cleanly. May help with debugging
22898 if bug 1209 ever remanifests.
22899 - Some options used different conventions for uppercasing of acronyms
22900 when comparing manpage and source. Fix those in favor of the
22901 manpage, as it makes sense to capitalize acronyms.
22902 - Take a first step towards making or.h smaller by splitting out
22903 function definitions for all source files in src/or/. Leave
22904 structures and defines in or.h for now.
22905 - Remove a few dead assignments during router parsing. Found by
22907 - Don't use 1-bit wide signed bit fields. Found by coverity.
22908 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
22909 None of the cases where we did this before were wrong, but by making
22910 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
22911 - The memarea code now uses a sentinel value at the end of each area
22912 to make sure nothing writes beyond the end of an area. This might
22913 help debug some conceivable causes of bug 930.
22914 - Always treat failure to allocate an RSA key as an unrecoverable
22916 - Add some more defensive programming for architectures that can't
22917 handle unaligned integer accesses. We don't know of any actual bugs
22918 right now, but that's the best time to fix them. Fixes bug 1943.
22920 o Minor bugfixes (misc):
22921 - Fix a rare bug in rend_fn unit tests: we would fail a test when
22922 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
22923 on 0.2.0.10-alpha; fixes bug 1808.
22924 - Where available, use Libevent 2.0's periodic timers so that our
22925 once-per-second cleanup code gets called even more closely to
22926 once per second than it would otherwise. Fixes bug 943.
22927 - Ignore OutboundBindAddress when connecting to localhost.
22928 Connections to localhost need to come _from_ localhost, or else
22929 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
22931 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
22933 - If any of the v3 certs we download are unparseable, we should
22934 actually notice the failure so we don't retry indefinitely. Bugfix
22935 on 0.2.0.x; reported by "rotator".
22936 - When Tor fails to parse a descriptor of any kind, dump it to disk.
22937 Might help diagnosing bug 1051.
22938 - Make our 'torify' script more portable; if we have only one of
22939 'torsocks' or 'tsocks' installed, don't complain to the user;
22940 and explain our warning about tsocks better.
22941 - Fix some urls in the exit notice file and make it XHTML1.1 strict
22942 compliant. Based on a patch from Christian Kujau.
22944 o Documentation changes:
22945 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
22946 - Resolve all doxygen warnings except those for missing documentation.
22948 - Add doxygen documentation for more functions, fields, and types.
22949 - Convert the HACKING file to asciidoc, and add a few new sections
22950 to it, explaining how we use Git, how we make changelogs, and
22951 what should go in a patch.
22952 - Document the default socks host and port (127.0.0.1:9050) for
22954 - Removed some unnecessary files from the source distribution. The
22955 AUTHORS file has now been merged into the people page on the
22956 website. The roadmaps and design doc can now be found in the
22957 projects directory in svn.
22959 o Deprecated and removed features (config):
22960 - Remove the torrc.complete file. It hasn't been kept up to date
22961 and users will have better luck checking out the manpage.
22962 - Remove the HSAuthorityRecordStats option that version 0 hidden
22963 service authorities could use to track statistics of overall v0
22964 hidden service usage.
22965 - Remove the obsolete "NoPublish" option; it has been flagged
22966 as obsolete and has produced a warning since 0.1.1.18-rc.
22967 - Caches no longer download and serve v2 networkstatus documents
22968 unless FetchV2Networkstatus flag is set: these documents haven't
22969 haven't been used by clients or relays since 0.2.0.x. Resolves
22972 o Deprecated and removed features (controller):
22973 - The controller no longer accepts the old obsolete "addr-mappings/"
22974 or "unregistered-servers-" GETINFO values.
22975 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
22976 always on; using them is necessary for correct forward-compatible
22979 o Deprecated and removed features (misc):
22980 - Hidden services no longer publish version 0 descriptors, and clients
22981 do not request or use version 0 descriptors. However, the old hidden
22982 service authorities still accept and serve version 0 descriptors
22983 when contacted by older hidden services/clients.
22984 - Remove undocumented option "-F" from tor-resolve: it hasn't done
22985 anything since 0.2.1.16-rc.
22986 - Remove everything related to building the expert bundle for OS X.
22987 It has confused many users, doesn't work right on OS X 10.6,
22988 and is hard to get rid of once installed. Resolves bug 1274.
22989 - Remove support for .noconnect style addresses. Nobody was using
22990 them, and they provided another avenue for detecting Tor users
22991 via application-level web tricks.
22992 - When we fixed bug 1038 we had to put in a restriction not to send
22993 RELAY_EARLY cells on rend circuits. This was necessary as long
22994 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
22995 active. Now remove this obsolete check. Resolves bug 2081.
22996 - Remove workaround code to handle directory responses from servers
22997 that had bug 539 (they would send HTTP status 503 responses _and_
22998 send a body too). Since only server versions before
22999 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
23000 keep the workaround in place.
23001 - Remove the old 'fuzzy time' logic. It was supposed to be used for
23002 handling calculations where we have a known amount of clock skew and
23003 an allowed amount of unknown skew. But we only used it in three
23004 places, and we never adjusted the known/unknown skew values. This is
23005 still something we might want to do someday, but if we do, we'll
23006 want to do it differently.
23007 - Remove the "--enable-iphone" option to ./configure. According to
23008 reports from Marco Bonetti, Tor builds fine without any special
23009 tweaking on recent iPhone SDK versions.
23012 Changes in version 0.2.1.30 - 2011-02-23
23013 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
23014 change is a slight tweak to Tor's TLS handshake that makes relays
23015 and bridges that run this new version reachable from Iran again.
23016 We don't expect this tweak will win the arms race long-term, but it
23017 buys us time until we roll out a better solution.
23020 - Stop sending a CLOCK_SKEW controller status event whenever
23021 we fetch directory information from a relay that has a wrong clock.
23022 Instead, only inform the controller when it's a trusted authority
23023 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
23024 the rest of bug 1074.
23025 - Fix a bounds-checking error that could allow an attacker to
23026 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
23027 Found by "piebeer".
23028 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
23029 Tor would ignore their RelayBandwidthBurst setting,
23030 potentially using more bandwidth than expected. Bugfix on
23031 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
23032 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
23033 hidserv" in her torrc. The 'hidserv' argument never controlled
23034 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
23037 - Adjust our TLS Diffie-Hellman parameters to match those used by
23039 - Update to the February 1 2011 Maxmind GeoLite Country database.
23042 - Check for and reject overly long directory certificates and
23043 directory tokens before they have a chance to hit any assertions.
23044 Bugfix on 0.2.1.28. Found by "doorss".
23045 - Bring the logic that gathers routerinfos and assesses the
23046 acceptability of circuits into line. This prevents a Tor OP from
23047 getting locked in a cycle of choosing its local OR as an exit for a
23048 path (due to a .exit request) and then rejecting the circuit because
23049 its OR is not listed yet. It also prevents Tor clients from using an
23050 OR running in the same instance as an exit (due to a .exit request)
23051 if the OR does not meet the same requirements expected of an OR
23052 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
23054 o Packaging changes:
23055 - Stop shipping the Tor specs files and development proposal documents
23056 in the tarball. They are now in a separate git repository at
23057 git://git.torproject.org/torspec.git
23058 - Do not include Git version tags as though they are SVN tags when
23059 generating a tarball from inside a repository that has switched
23060 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
23063 Changes in version 0.2.1.29 - 2011-01-15
23064 Tor 0.2.1.29 continues our recent code security audit work. The main
23065 fix resolves a remote heap overflow vulnerability that can allow remote
23066 code execution. Other fixes address a variety of assert and crash bugs,
23067 most of which we think are hard to exploit remotely.
23069 o Major bugfixes (security):
23070 - Fix a heap overflow bug where an adversary could cause heap
23071 corruption. This bug probably allows remote code execution
23072 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
23074 - Prevent a denial-of-service attack by disallowing any
23075 zlib-compressed data whose compression factor is implausibly
23076 high. Fixes part of bug 2324; reported by "doorss".
23077 - Zero out a few more keys in memory before freeing them. Fixes
23078 bug 2384 and part of bug 2385. These key instances found by
23079 "cypherpunks", based on Andrew Case's report about being able
23080 to find sensitive data in Tor's memory space if you have enough
23081 permissions. Bugfix on 0.0.2pre9.
23083 o Major bugfixes (crashes):
23084 - Prevent calls to Libevent from inside Libevent log handlers.
23085 This had potential to cause a nasty set of crashes, especially
23086 if running Libevent with debug logging enabled, and running
23087 Tor with a controller watching for low-severity log messages.
23088 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
23089 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
23090 underflow errors there too. Fixes the other part of bug 2324.
23091 - Fix a bug where we would assert if we ever had a
23092 cached-descriptors.new file (or another file read directly into
23093 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
23094 on 0.2.1.25. Found by doorss.
23095 - Fix some potential asserts and parsing issues with grossly
23096 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
23099 o Minor bugfixes (other):
23100 - Fix a bug with handling misformed replies to reverse DNS lookup
23101 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
23102 bug reported by doorss.
23103 - Fix compilation on mingw when a pthreads compatibility library
23104 has been installed. (We don't want to use it, so we shouldn't
23105 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
23106 - Fix a bug where we would declare that we had run out of virtual
23107 addresses when the address space was only half-exhausted. Bugfix
23109 - Correctly handle the case where AutomapHostsOnResolve is set but
23110 no virtual addresses are available. Fixes bug 2328; bugfix on
23111 0.1.2.1-alpha. Bug found by doorss.
23112 - Correctly handle wrapping around when we run out of virtual
23113 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
23116 - Update to the January 1 2011 Maxmind GeoLite Country database.
23117 - Introduce output size checks on all of our decryption functions.
23120 - Tor does not build packages correctly with Automake 1.6 and earlier;
23121 added a check to Makefile.am to make sure that we're building with
23122 Automake 1.7 or later.
23123 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
23124 because we built it with a too-old version of automake. Thus that
23125 release broke ./configure --enable-openbsd-malloc, which is popular
23126 among really fast exit relays on Linux.
23129 Changes in version 0.2.1.28 - 2010-12-17
23130 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
23131 exploitable bugs. We also took this opportunity to change the IP address
23132 for one of our directory authorities, and to update the geoip database
23136 - Fix a remotely exploitable bug that could be used to crash instances
23137 of Tor remotely by overflowing on the heap. Remote-code execution
23138 hasn't been confirmed, but can't be ruled out. Everyone should
23139 upgrade. Bugfix on the 0.1.1 series and later.
23141 o Directory authority changes:
23142 - Change IP address and ports for gabelmoo (v3 directory authority).
23145 - Update to the December 1 2010 Maxmind GeoLite Country database.
23148 Changes in version 0.2.1.27 - 2010-11-23
23149 Yet another OpenSSL security patch broke its compatibility with Tor:
23150 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
23151 also took this opportunity to fix several crash bugs, integrate a new
23152 directory authority, and update the bundled GeoIP database.
23155 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
23156 No longer set the tlsext_host_name extension on server SSL objects;
23157 but continue to set it on client SSL objects. Our goal in setting
23158 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
23159 bugfix on 0.2.1.1-alpha.
23160 - Do not log messages to the controller while shrinking buffer
23161 freelists. Doing so would sometimes make the controller connection
23162 try to allocate a buffer chunk, which would mess up the internals
23163 of the freelist and cause an assertion failure. Fixes bug 1125;
23164 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
23165 - Learn our external IP address when we're a relay or bridge, even if
23166 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
23167 where we introduced bridge relays that don't need to publish to
23168 be useful. Fixes bug 2050.
23169 - Do even more to reject (and not just ignore) annotations on
23170 router descriptors received anywhere but from the cache. Previously
23171 we would ignore such annotations at first, but cache them to disk
23172 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
23173 - When you're using bridges and your network goes away and your
23174 bridges get marked as down, recover when you attempt a new socks
23175 connection (if the network is back), rather than waiting up to an
23176 hour to try fetching new descriptors for your bridges. Bugfix on
23177 0.2.0.3-alpha; fixes bug 1981.
23180 - Move to the November 2010 Maxmind GeoLite country db (rather
23181 than the June 2009 ip-to-country GeoIP db) for our statistics that
23182 count how many users relays are seeing from each country. Now we'll
23183 have more accurate data, especially for many African countries.
23185 o New directory authorities:
23186 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
23190 - Fix an assertion failure that could occur in directory caches or
23191 bridge users when using a very short voting interval on a testing
23192 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
23194 - Enforce multiplicity rules when parsing annotations. Bugfix on
23195 0.2.0.8-alpha. Found by piebeer.
23196 - Allow handshaking OR connections to take a full KeepalivePeriod
23197 seconds to handshake. Previously, we would close them after
23198 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
23199 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
23201 - When building with --enable-gcc-warnings on OpenBSD, disable
23202 warnings in system headers. This makes --enable-gcc-warnings
23203 pass on OpenBSD 4.8.
23206 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
23207 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
23208 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
23209 Servers can start sending this code when enough clients recognize
23210 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
23211 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
23212 Patch from mingw-san.
23215 - Remove the old debian/ directory from the main Tor distribution.
23216 The official Tor-for-debian git repository lives at the URL
23217 https://git.torproject.org/debian/tor.git
23218 - Stop shipping the old doc/website/ directory in the tarball. We
23219 changed the website format in late 2010, and what we shipped in
23220 0.2.1.26 really wasn't that useful anyway.
23223 Changes in version 0.2.1.26 - 2010-05-02
23224 Tor 0.2.1.26 addresses the recent connection and memory overload
23225 problems we've been seeing on relays, especially relays with their
23226 DirPort open. If your relay has been crashing, or you turned it off
23227 because it used too many resources, give this release a try.
23229 This release also fixes yet another instance of broken OpenSSL libraries
23230 that was causing some relays to drop out of the consensus.
23233 - Teach relays to defend themselves from connection overload. Relays
23234 now close idle circuits early if it looks like they were intended
23235 for directory fetches. Relays are also more aggressive about closing
23236 TLS connections that have no circuits on them. Such circuits are
23237 unlikely to be re-used, and tens of thousands of them were piling
23238 up at the fast relays, causing the relays to run out of sockets
23239 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
23240 their directory fetches over TLS).
23241 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
23242 that claim to be earlier than 0.9.8m, but which have in reality
23243 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
23244 behavior. Possible fix for some cases of bug 1346.
23245 - Directory mirrors were fetching relay descriptors only from v2
23246 directory authorities, rather than v3 authorities like they should.
23247 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
23248 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
23251 - Finally get rid of the deprecated and now harmful notion of "clique
23252 mode", where directory authorities maintain TLS connections to
23256 - In the util/threads test, no longer free the test_mutex before all
23257 worker threads have finished. Bugfix on 0.2.1.6-alpha.
23258 - The master thread could starve the worker threads quite badly on
23259 certain systems, causing them to run only partially in the allowed
23260 window. This resulted in test failures. Now the master thread sleeps
23261 occasionally for a few microseconds while the two worker-threads
23262 compete for the mutex. Bugfix on 0.2.0.1-alpha.
23265 Changes in version 0.2.1.25 - 2010-03-16
23266 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
23267 prevent relays from guessing their IP address correctly. It also fixes
23268 several minor potential security bugs.
23271 - Fix a regression from our patch for bug 1244 that caused relays
23272 to guess their IP address incorrectly if they didn't set Address
23273 in their torrc and/or their address fails to resolve. Bugfix on
23274 0.2.1.23; fixes bug 1269.
23275 - When freeing a session key, zero it out completely. We only zeroed
23276 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
23277 patched by ekir. Fixes bug 1254.
23280 - Fix a dereference-then-NULL-check sequence when publishing
23281 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
23283 - Fix another dereference-then-NULL-check sequence. Bugfix on
23284 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
23285 - Make sure we treat potentially not NUL-terminated strings correctly.
23286 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
23289 Changes in version 0.2.1.24 - 2010-02-21
23290 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
23294 - Work correctly out-of-the-box with even more vendor-patched versions
23295 of OpenSSL. In particular, make it so Debian and OS X don't need
23296 customized patches to run/build.
23299 Changes in version 0.2.1.23 - 2010-02-13
23300 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
23301 again on the latest OS X, and updates the location of a directory
23304 o Major bugfixes (performance):
23305 - We were selecting our guards uniformly at random, and then weighting
23306 which of our guards we'd use uniformly at random. This imbalance
23307 meant that Tor clients were severely limited on throughput (and
23308 probably latency too) by the first hop in their circuit. Now we
23309 select guards weighted by currently advertised bandwidth. We also
23310 automatically discard guards picked using the old algorithm. Fixes
23311 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
23314 - Make Tor work again on the latest OS X: when deciding whether to
23315 use strange flags to turn TLS renegotiation on, detect the OpenSSL
23316 version at run-time, not compile time. We need to do this because
23317 Apple doesn't update its dev-tools headers when it updates its
23318 libraries in a security patch.
23319 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
23320 that could happen on 32-bit platforms with 64-bit time_t. Also fix
23321 a memory leak when requesting a hidden service descriptor we've
23322 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
23326 - Refactor resolve_my_address() to not use gethostbyname() anymore.
23327 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
23330 - Avoid a mad rush at the beginning of each month when each client
23331 rotates half of its guards. Instead we spread the rotation out
23332 throughout the month, but we still avoid leaving a precise timestamp
23333 in the state file about when we first picked the guard. Improves
23334 over the behavior introduced in 0.1.2.17.
23337 Changes in version 0.2.1.22 - 2010-01-19
23338 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
23339 authorities -- it would tell you its whole history of bridge descriptors
23340 if you make the right directory request. This stable update also
23341 rotates two of the seven v3 directory authority keys and locations.
23343 o Directory authority changes:
23344 - Rotate keys (both v3 identity and relay identity) for moria1
23348 - Stop bridge directory authorities from answering dbg-stability.txt
23349 directory queries, which would let people fetch a list of all
23350 bridge identities they track. Bugfix on 0.2.1.6-alpha.
23353 Changes in version 0.2.1.21 - 2009-12-21
23354 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
23355 library. If you use Tor on Linux / Unix and you're getting SSL
23356 renegotiation errors, upgrading should help. We also recommend an
23357 upgrade if you're an exit relay.
23360 - Work around a security feature in OpenSSL 0.9.8l that prevents our
23361 handshake from working unless we explicitly tell OpenSSL that we
23362 are using SSL renegotiation safely. We are, of course, but OpenSSL
23363 0.9.8l won't work unless we say we are.
23364 - Avoid crashing if the client is trying to upload many bytes and the
23365 circuit gets torn down at the same time, or if the flip side
23366 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
23369 - Do not refuse to learn about authority certs and v2 networkstatus
23370 documents that are older than the latest consensus. This bug might
23371 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
23372 Spotted and fixed by xmux.
23373 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
23374 trigger platform-specific option misparsing case found by Coverity
23376 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
23377 trigger assert. Fixes bug 1173.
23380 Changes in version 0.2.1.20 - 2009-10-15
23381 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
23382 services at once, prepares for more performance improvements, and
23383 fixes a bunch of smaller bugs.
23385 The Windows and OS X bundles also include a more recent Vidalia,
23386 and switch from Privoxy to Polipo.
23388 The OS X installers are now drag and drop. It's best to un-install
23389 Tor/Vidalia and then install this new bundle, rather than upgrade. If
23390 you want to upgrade, you'll need to update the paths for Tor and Polipo
23391 in the Vidalia Settings window.
23394 - Send circuit or stream sendme cells when our window has decreased
23395 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
23396 by Karsten when testing the "reduce circuit window" performance
23397 patch. Bugfix on the 54th commit on Tor -- from July 2002,
23398 before the release of Tor 0.0.0. This is the new winner of the
23400 - Fix a remotely triggerable memory leak when a consensus document
23401 contains more than one signature from the same voter. Bugfix on
23403 - Avoid segfault in rare cases when finishing an introduction circuit
23404 as a client and finding out that we don't have an introduction key
23405 for it. Fixes bug 1073. Reported by Aaron Swartz.
23408 - Tor now reads the "circwindow" parameter out of the consensus,
23409 and uses that value for its circuit package window rather than the
23410 default of 1000 cells. Begins the implementation of proposal 168.
23412 o New directory authorities:
23413 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
23415 - Move moria1 and tonga to alternate IP addresses.
23418 - Fix a signed/unsigned compile warning in 0.2.1.19.
23419 - Fix possible segmentation fault on directory authorities. Bugfix on
23421 - Fix an extremely rare infinite recursion bug that could occur if
23422 we tried to log a message after shutting down the log subsystem.
23423 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
23424 - Fix an obscure bug where hidden services on 64-bit big-endian
23425 systems might mis-read the timestamp in v3 introduce cells, and
23426 refuse to connect back to the client. Discovered by "rotor".
23427 Bugfix on 0.2.1.6-alpha.
23428 - We were triggering a CLOCK_SKEW controller status event whenever
23429 we connect via the v2 connection protocol to any relay that has
23430 a wrong clock. Instead, we should only inform the controller when
23431 it's a trusted authority that claims our clock is wrong. Bugfix
23432 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
23433 - We were telling the controller about CHECKING_REACHABILITY and
23434 REACHABILITY_FAILED status events whenever we launch a testing
23435 circuit or notice that one has failed. Instead, only tell the
23436 controller when we want to inform the user of overall success or
23437 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
23439 - Don't warn when we're using a circuit that ends with a node
23440 excluded in ExcludeExitNodes, but the circuit is not used to access
23441 the outside world. This should help fix bug 1090. Bugfix on
23443 - Work around a small memory leak in some versions of OpenSSL that
23444 stopped the memory used by the hostname TLS extension from being
23448 - Add a "getinfo status/accepted-server-descriptor" controller
23449 command, which is the recommended way for controllers to learn
23450 whether our server descriptor has been successfully received by at
23451 least on directory authority. Un-recommend good-server-descriptor
23452 getinfo and status events until we have a better design for them.
23455 Changes in version 0.2.1.19 - 2009-07-28
23456 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
23460 - Make accessing hidden services on 0.2.1.x work right again.
23461 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
23462 part of patch provided by "optimist".
23465 - When a relay/bridge is writing out its identity key fingerprint to
23466 the "fingerprint" file and to its logs, write it without spaces. Now
23467 it will look like the fingerprints in our bridges documentation,
23468 and confuse fewer users.
23471 - Relays no longer publish a new server descriptor if they change
23472 their MaxAdvertisedBandwidth config option but it doesn't end up
23473 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
23474 fixes bug 1026. Patch from Sebastian.
23475 - Avoid leaking memory every time we get a create cell but we have
23476 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
23477 fixes bug 1034. Reported by BarkerJr.
23480 Changes in version 0.2.1.18 - 2009-07-24
23481 Tor 0.2.1.18 lays the foundations for performance improvements,
23482 adds status events to help users diagnose bootstrap problems, adds
23483 optional authentication/authorization for hidden services, fixes a
23484 variety of potential anonymity problems, and includes a huge pile of
23485 other features and bug fixes.
23487 o Major features (clients):
23488 - Start sending "bootstrap phase" status events to the controller,
23489 so it can keep the user informed of progress fetching directory
23490 information and establishing circuits. Also inform the controller
23491 if we think we're stuck at a particular bootstrap phase. Implements
23493 - Clients replace entry guards that were chosen more than a few months
23494 ago. This change should significantly improve client performance,
23495 especially once more people upgrade, since relays that have been
23496 a guard for a long time are currently overloaded.
23497 - Network status consensus documents and votes now contain bandwidth
23498 information for each relay. Clients use the bandwidth values
23499 in the consensus, rather than the bandwidth values in each
23500 relay descriptor. This approach opens the door to more accurate
23501 bandwidth estimates once the directory authorities start doing
23502 active measurements. Implements part of proposal 141.
23504 o Major features (relays):
23505 - Disable and refactor some debugging checks that forced a linear scan
23506 over the whole server-side DNS cache. These accounted for over 50%
23507 of CPU time on a relatively busy exit node's gprof profile. Also,
23508 disable some debugging checks that appeared in exit node profile
23509 data. Found by Jacob.
23510 - New DirPortFrontPage option that takes an html file and publishes
23511 it as "/" on the DirPort. Now relay operators can provide a
23512 disclaimer without needing to set up a separate webserver. There's
23513 a sample disclaimer in contrib/tor-exit-notice.html.
23515 o Major features (hidden services):
23516 - Make it possible to build hidden services that only certain clients
23517 are allowed to connect to. This is enforced at several points,
23518 so that unauthorized clients are unable to send INTRODUCE cells
23519 to the service, or even (depending on the type of authentication)
23520 to learn introduction points. This feature raises the bar for
23521 certain kinds of active attacks against hidden services. Design
23522 and code by Karsten Loesing. Implements proposal 121.
23523 - Relays now store and serve v2 hidden service descriptors by default,
23524 i.e., the new default value for HidServDirectoryV2 is 1. This is
23525 the last step in proposal 114, which aims to make hidden service
23526 lookups more reliable.
23528 o Major features (path selection):
23529 - ExitNodes and Exclude*Nodes config options now allow you to restrict
23530 by country code ("{US}") or IP address or address pattern
23531 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
23532 refinement to decide what config options should take priority if
23533 you ask to both use a particular node and exclude it.
23535 o Major features (misc):
23536 - When building a consensus, do not include routers that are down.
23537 This cuts down 30% to 40% on consensus size. Implements proposal
23539 - New TestingTorNetwork config option to allow adjustment of
23540 previously constant values that could slow bootstrapping. Implements
23541 proposal 135. Patch from Karsten.
23542 - Convert many internal address representations to optionally hold
23543 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
23544 elements. Make resolver code handle nameservers located at IPv6
23546 - More work on making our TLS handshake blend in: modify the list
23547 of ciphers advertised by OpenSSL in client mode to even more
23548 closely resemble a common web browser. We cheat a little so that
23549 we can advertise ciphers that the locally installed OpenSSL doesn't
23551 - Use the TLS1 hostname extension to more closely resemble browser
23554 o Security fixes (anonymity/entropy):
23555 - Never use a connection with a mismatched address to extend a
23556 circuit, unless that connection is canonical. A canonical
23557 connection is one whose address is authenticated by the router's
23558 identity key, either in a NETINFO cell or in a router descriptor.
23559 - Implement most of proposal 110: The first K cells to be sent
23560 along a circuit are marked as special "early" cells; only K "early"
23561 cells will be allowed. Once this code is universal, we can block
23562 certain kinds of denial-of-service attack by requiring that EXTEND
23563 commands must be sent using an "early" cell.
23564 - Resume using OpenSSL's RAND_poll() for better (and more portable)
23565 cross-platform entropy collection again. We used to use it, then
23566 stopped using it because of a bug that could crash systems that
23567 called RAND_poll when they had a lot of fds open. It looks like the
23568 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
23569 at startup, and to call RAND_poll() when we reseed later only if
23570 we have a non-buggy OpenSSL version.
23571 - When the client is choosing entry guards, now it selects at most
23572 one guard from a given relay family. Otherwise we could end up with
23573 all of our entry points into the network run by the same operator.
23574 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
23575 - Do not use or believe expired v3 authority certificates. Patch
23576 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
23577 - Drop begin cells to a hidden service if they come from the middle
23578 of a circuit. Patch from lark.
23579 - When we erroneously receive two EXTEND cells for the same circuit
23580 ID on the same connection, drop the second. Patch from lark.
23581 - Authorities now vote for the Stable flag for any router whose
23582 weighted MTBF is at least 5 days, regardless of the mean MTBF.
23583 - Clients now never report any stream end reason except 'MISC'.
23584 Implements proposal 148.
23586 o Major bugfixes (crashes):
23587 - Parse dates and IPv4 addresses in a locale- and libc-independent
23588 manner, to avoid platform-dependent behavior on malformed input.
23589 - Fix a crash that occurs on exit nodes when a nameserver request
23590 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
23591 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
23593 - Do not assume that a stack-allocated character array will be
23594 64-bit aligned on platforms that demand that uint64_t access is
23595 aligned. Possible fix for bug 604.
23596 - Resolve a very rare crash bug that could occur when the user forced
23597 a nameserver reconfiguration during the middle of a nameserver
23598 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
23599 - Avoid a "0 divided by 0" calculation when calculating router uptime
23600 at directory authorities. Bugfix on 0.2.0.8-alpha.
23601 - Fix an assertion bug in parsing policy-related options; possible fix
23603 - Rate-limit too-many-sockets messages: when they happen, they happen
23604 a lot and end up filling up the disk. Resolves bug 748.
23605 - Fix a race condition that could cause crashes or memory corruption
23606 when running as a server with a controller listening for log
23608 - Avoid crashing when we have a policy specified in a DirPolicy or
23609 SocksPolicy or ReachableAddresses option with ports set on it,
23610 and we re-load the policy. May fix bug 996.
23611 - Fix an assertion failure on 64-bit platforms when we allocated
23612 memory right up to the end of a memarea, then realigned the memory
23613 one step beyond the end. Fixes a possible cause of bug 930.
23614 - Protect the count of open sockets with a mutex, so we can't
23615 corrupt it when two threads are closing or opening sockets at once.
23616 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
23618 o Major bugfixes (clients):
23619 - Discard router descriptors as we load them if they are more than
23620 five days old. Otherwise if Tor is off for a long time and then
23621 starts with cached descriptors, it will try to use the onion keys
23622 in those obsolete descriptors when building circuits. Fixes bug 887.
23623 - When we choose to abandon a new entry guard because we think our
23624 older ones might be better, close any circuits pending on that
23625 new entry guard connection. This fix should make us recover much
23626 faster when our network is down and then comes back. Bugfix on
23627 0.1.2.8-beta; found by lodger.
23628 - When Tor clients restart after 1-5 days, they discard all their
23629 cached descriptors as too old, but they still use the cached
23630 consensus document. This approach is good for robustness, but
23631 bad for performance: since they don't know any bandwidths, they
23632 end up choosing at random rather than weighting their choice by
23633 speed. Fixed by the above feature of putting bandwidths in the
23636 o Major bugfixes (relays):
23637 - Relays were falling out of the networkstatus consensus for
23638 part of a day if they changed their local config but the
23639 authorities discarded their new descriptor as "not sufficiently
23640 different". Now directory authorities accept a descriptor as changed
23641 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
23642 patch by Sebastian.
23643 - Ensure that two circuits can never exist on the same connection
23644 with the same circuit ID, even if one is marked for close. This
23645 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
23646 - Directory authorities were neglecting to mark relays down in their
23647 internal histories if the relays fall off the routerlist without
23648 ever being found unreachable. So there were relays in the histories
23649 that haven't been seen for eight months, and are listed as being
23650 up for eight months. This wreaked havoc on the "median wfu" and
23651 "median mtbf" calculations, in turn making Guard and Stable flags
23652 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
23655 o Major bugfixes (hidden services):
23656 - When establishing a hidden service, introduction points that
23657 originate from cannibalized circuits were completely ignored
23658 and not included in rendezvous service descriptors. This might
23659 have been another reason for delay in making a hidden service
23660 available. Bugfix from long ago (0.0.9.x?)
23662 o Major bugfixes (memory and resource management):
23663 - Fixed some memory leaks -- some quite frequent, some almost
23664 impossible to trigger -- based on results from Coverity.
23665 - Speed up parsing and cut down on memory fragmentation by using
23666 stack-style allocations for parsing directory objects. Previously,
23667 this accounted for over 40% of allocations from within Tor's code
23668 on a typical directory cache.
23669 - Use a Bloom filter rather than a digest-based set to track which
23670 descriptors we need to keep around when we're cleaning out old
23671 router descriptors. This speeds up the computation significantly,
23672 and may reduce fragmentation.
23674 o New/changed config options:
23675 - Now NodeFamily and MyFamily config options allow spaces in
23676 identity fingerprints, so it's easier to paste them in.
23677 Suggested by Lucky Green.
23678 - Allow ports 465 and 587 in the default exit policy again. We had
23679 rejected them in 0.1.0.15, because back in 2005 they were commonly
23680 misconfigured and ended up as spam targets. We hear they are better
23681 locked down these days.
23682 - Make TrackHostExit mappings expire a while after their last use, not
23683 after their creation. Patch from Robert Hogan.
23684 - Add an ExcludeExitNodes option so users can list a set of nodes
23685 that should be be excluded from the exit node position, but
23686 allowed elsewhere. Implements proposal 151.
23687 - New --hush command-line option similar to --quiet. While --quiet
23688 disables all logging to the console on startup, --hush limits the
23689 output to messages of warning and error severity.
23690 - New configure/torrc options (--enable-geoip-stats,
23691 DirRecordUsageByCountry) to record how many IPs we've served
23692 directory info to in each country code, how many status documents
23693 total we've sent to each country code, and what share of the total
23694 directory requests we should expect to see.
23695 - Make outbound DNS packets respect the OutboundBindAddress setting.
23696 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
23697 - Allow separate log levels to be configured for different logging
23698 domains. For example, this allows one to log all notices, warnings,
23699 or errors, plus all memory management messages of level debug or
23700 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
23701 - Update to the "June 3 2009" ip-to-country file.
23703 o Minor features (relays):
23704 - Raise the minimum rate limiting to be a relay from 20000 bytes
23705 to 20480 bytes (aka 20KB/s), to match our documentation. Also
23706 update directory authorities so they always assign the Fast flag
23707 to relays with 20KB/s of capacity. Now people running relays won't
23708 suddenly find themselves not seeing any use, if the network gets
23710 - If we're a relay and we change our IP address, be more verbose
23711 about the reason that made us change. Should help track down
23712 further bugs for relays on dynamic IP addresses.
23713 - Exit servers can now answer resolve requests for ip6.arpa addresses.
23714 - Implement most of Proposal 152: allow specialized servers to permit
23715 single-hop circuits, and clients to use those servers to build
23716 single-hop circuits when using a specialized controller. Patch
23717 from Josh Albrecht. Resolves feature request 768.
23718 - When relays do their initial bandwidth measurement, don't limit
23719 to just our entry guards for the test circuits. Otherwise we tend
23720 to have multiple test circuits going through a single entry guard,
23721 which makes our bandwidth test less accurate. Fixes part of bug 654;
23722 patch contributed by Josh Albrecht.
23724 o Minor features (directory authorities):
23725 - Try not to open more than one descriptor-downloading connection
23726 to an authority at once. This should reduce load on directory
23727 authorities. Fixes bug 366.
23728 - Add cross-certification to newly generated certificates, so that
23729 a signing key is enough information to look up a certificate. Start
23730 serving certificates by <identity digest, signing key digest>
23731 pairs. Implements proposal 157.
23732 - When a directory authority downloads a descriptor that it then
23733 immediately rejects, do not retry downloading it right away. Should
23734 save some bandwidth on authorities. Fix for bug 888. Patch by
23736 - Directory authorities now serve a /tor/dbg-stability.txt URL to
23737 help debug WFU and MTBF calculations.
23738 - In directory authorities' approved-routers files, allow
23739 fingerprints with or without space.
23741 o Minor features (directory mirrors):
23742 - When a download gets us zero good descriptors, do not notify
23743 Tor that new directory information has arrived.
23744 - Servers support a new URL scheme for consensus downloads that
23745 allows the client to specify which authorities are trusted.
23746 The server then only sends the consensus if the client will trust
23747 it. Otherwise a 404 error is sent back. Clients use this
23748 new scheme when the server supports it (meaning it's running
23749 0.2.1.1-alpha or later). Implements proposal 134.
23751 o Minor features (bridges):
23752 - If the bridge config line doesn't specify a port, assume 443.
23753 This makes bridge lines a bit smaller and easier for users to
23755 - If we're using bridges and our network goes away, be more willing
23756 to forgive our bridges and try again when we get an application
23759 o Minor features (hidden services):
23760 - When the client launches an introduction circuit, retry with a
23761 new circuit after 30 seconds rather than 60 seconds.
23762 - Launch a second client-side introduction circuit in parallel
23763 after a delay of 15 seconds (based on work by Christian Wilms).
23764 - Hidden services start out building five intro circuits rather
23765 than three, and when the first three finish they publish a service
23766 descriptor using those. Now we publish our service descriptor much
23767 faster after restart.
23768 - Drop the requirement to have an open dir port for storing and
23769 serving v2 hidden service descriptors.
23771 o Minor features (build and packaging):
23772 - On Linux, use the prctl call to re-enable core dumps when the User
23774 - Try to make sure that the version of Libevent we're running with
23775 is binary-compatible with the one we built with. May address bug
23777 - Add a new --enable-local-appdata configuration switch to change
23778 the default location of the datadir on win32 from APPDATA to
23779 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
23780 entirely. Patch from coderman.
23781 - Build correctly against versions of OpenSSL 0.9.8 or later that
23782 are built without support for deprecated functions.
23783 - On platforms with a maximum syslog string length, truncate syslog
23784 messages to that length ourselves, rather than relying on the
23785 system to do it for us.
23786 - Automatically detect MacOSX versions earlier than 10.4.0, and
23787 disable kqueue from inside Tor when running with these versions.
23788 We previously did this from the startup script, but that was no
23789 help to people who didn't use the startup script. Resolves bug 863.
23790 - Build correctly when configured to build outside the main source
23791 path. Patch from Michael Gold.
23792 - Disable GCC's strict alias optimization by default, to avoid the
23793 likelihood of its introducing subtle bugs whenever our code violates
23794 the letter of C99's alias rules.
23795 - Change the contrib/tor.logrotate script so it makes the new
23796 logs as "_tor:_tor" rather than the default, which is generally
23797 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
23798 - Change our header file guard macros to be less likely to conflict
23799 with system headers. Adam Langley noticed that we were conflicting
23800 with log.h on Android.
23801 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
23802 and stop using a warning that had become unfixably verbose under
23804 - Use a lockfile to make sure that two Tor processes are not
23805 simultaneously running with the same datadir.
23806 - Allow OpenSSL to use dynamic locks if it wants.
23807 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
23809 o Minor features (controllers):
23810 - When generating circuit events with verbose nicknames for
23811 controllers, try harder to look up nicknames for routers on a
23812 circuit. (Previously, we would look in the router descriptors we had
23813 for nicknames, but not in the consensus.) Partial fix for bug 941.
23814 - New controller event NEWCONSENSUS that lists the networkstatus
23815 lines for every recommended relay. Now controllers like Torflow
23816 can keep up-to-date on which relays they should be using.
23817 - New controller event "clients_seen" to report a geoip-based summary
23818 of which countries we've seen clients from recently. Now controllers
23819 like Vidalia can show bridge operators that they're actually making
23821 - Add a 'getinfo status/clients-seen' controller command, in case
23822 controllers want to hear clients_seen events but connect late.
23823 - New CONSENSUS_ARRIVED event to note when a new consensus has
23824 been fetched and validated.
23825 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
23826 controllers to prevent SIGHUP from reloading the configuration.
23828 - Return circuit purposes in response to GETINFO circuit-status.
23830 - Serve the latest v3 networkstatus consensus via the control
23831 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
23832 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
23833 controller can query our current bootstrap state in case it attaches
23834 partway through and wants to catch up.
23835 - Provide circuit purposes along with circuit events to the controller.
23837 o Minor features (tools):
23838 - Do not have tor-resolve automatically refuse all .onion addresses;
23839 if AutomapHostsOnResolve is set in your torrc, this will work fine.
23840 - Add a -p option to tor-resolve for specifying the SOCKS port: some
23841 people find host:port too confusing.
23842 - Print the SOCKS5 error message string as well as the error code
23843 when a tor-resolve request fails. Patch from Jacob.
23845 o Minor bugfixes (memory and resource management):
23846 - Clients no longer cache certificates for authorities they do not
23847 recognize. Bugfix on 0.2.0.9-alpha.
23848 - Do not use C's stdio library for writing to log files. This will
23849 improve logging performance by a minute amount, and will stop
23850 leaking fds when our disk is full. Fixes bug 861.
23851 - Stop erroneous use of O_APPEND in cases where we did not in fact
23852 want to re-seek to the end of a file before every last write().
23853 - Fix a small alignment and memory-wasting bug on buffer chunks.
23855 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
23856 to avoid unused RAM in buffer chunks and memory pools.
23857 - Reduce the default smartlist size from 32 to 16; it turns out that
23858 most smartlists hold around 8-12 elements tops.
23859 - Make dumpstats() log the fullness and size of openssl-internal
23861 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
23862 patch to their OpenSSL, turn it on to save memory on servers. This
23863 patch will (with any luck) get included in a mainline distribution
23865 - Fix a memory leak when v3 directory authorities load their keys
23866 and cert from disk. Bugfix on 0.2.0.1-alpha.
23867 - Stop using malloc_usable_size() to use more area than we had
23868 actually allocated: it was safe, but made valgrind really unhappy.
23869 - Make the assert_circuit_ok() function work correctly on circuits that
23870 have already been marked for close.
23871 - Fix uninitialized size field for memory area allocation: may improve
23872 memory performance during directory parsing.
23874 o Minor bugfixes (clients):
23875 - Stop reloading the router list from disk for no reason when we
23876 run out of reachable directory mirrors. Once upon a time reloading
23877 it would set the 'is_running' flag back to 1 for them. It hasn't
23878 done that for a long time.
23879 - When we had picked an exit node for a connection, but marked it as
23880 "optional", and it turned out we had no onion key for the exit,
23881 stop wanting that exit and try again. This situation may not
23882 be possible now, but will probably become feasible with proposal
23883 158. Spotted by rovv. Fixes another case of bug 752.
23884 - Fix a bug in address parsing that was preventing bridges or hidden
23885 service targets from being at IPv6 addresses.
23886 - Do not remove routers as too old if we do not have any consensus
23887 document. Bugfix on 0.2.0.7-alpha.
23888 - When an exit relay resolves a stream address to a local IP address,
23889 do not just keep retrying that same exit relay over and
23890 over. Instead, just close the stream. Addresses bug 872. Bugfix
23891 on 0.2.0.32. Patch from rovv.
23892 - Made Tor a little less aggressive about deleting expired
23893 certificates. Partial fix for bug 854.
23894 - Treat duplicate certificate fetches as failures, so that we do
23895 not try to re-fetch an expired certificate over and over and over.
23896 - Do not say we're fetching a certificate when we'll in fact skip it
23897 because of a pending download.
23898 - If we have correct permissions on $datadir, we complain to stdout
23899 and fail to start. But dangerous permissions on
23900 $datadir/cached-status/ would cause us to open a log and complain
23901 there. Now complain to stdout and fail to start in both cases. Fixes
23902 bug 820, reported by seeess.
23904 o Minor bugfixes (bridges):
23905 - When we made bridge authorities stop serving bridge descriptors over
23906 unencrypted links, we also broke DirPort reachability testing for
23907 bridges. So bridges with a non-zero DirPort were printing spurious
23908 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
23909 - Don't allow a bridge to publish its router descriptor to a
23910 non-bridge directory authority. Fixes part of bug 932.
23911 - When we change to or from being a bridge, reset our counts of
23912 client usage by country. Fixes bug 932.
23914 o Minor bugfixes (relays):
23915 - Log correct error messages for DNS-related network errors on
23917 - Actually return -1 in the error case for read_bandwidth_usage().
23918 Harmless bug, since we currently don't care about the return value
23919 anywhere. Bugfix on 0.2.0.9-alpha.
23920 - Provide a more useful log message if bug 977 (related to buffer
23921 freelists) ever reappears, and do not crash right away.
23922 - We were already rejecting relay begin cells with destination port
23923 of 0. Now also reject extend cells with destination port or address
23924 of 0. Suggested by lark.
23925 - When we can't transmit a DNS request due to a network error, retry
23926 it after a while, and eventually transmit a failing response to
23927 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
23928 - Solve a bug that kept hardware crypto acceleration from getting
23929 enabled when accounting was turned on. Fixes bug 907. Bugfix on
23931 - When a canonical connection appears later in our internal list
23932 than a noncanonical one for a given OR ID, always use the
23933 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
23935 - Avoid some nasty corner cases in the logic for marking connections
23936 as too old or obsolete or noncanonical for circuits. Partial
23938 - Fix another interesting corner-case of bug 891 spotted by rovv:
23939 Previously, if two hosts had different amounts of clock drift, and
23940 one of them created a new connection with just the wrong timing,
23941 the other might decide to deprecate the new connection erroneously.
23942 Bugfix on 0.1.1.13-alpha.
23943 - If one win32 nameserver fails to get added, continue adding the
23944 rest, and don't automatically fail.
23945 - Fix a bug where an unreachable relay would establish enough
23946 reachability testing circuits to do a bandwidth test -- if
23947 we already have a connection to the middle hop of the testing
23948 circuit, then it could establish the last hop by using the existing
23949 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
23950 circuits no longer use entry guards in 0.2.1.3-alpha.
23952 o Minor bugfixes (directory authorities):
23953 - Limit uploaded directory documents to be 16M rather than 500K.
23954 The directory authorities were refusing v3 consensus votes from
23955 other authorities, since the votes are now 504K. Fixes bug 959;
23956 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
23957 - Directory authorities should never send a 503 "busy" response to
23958 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
23960 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
23961 headers. Bugfix on 0.2.0.10-alpha.
23963 o Minor bugfixes (hidden services):
23964 - When we can't find an intro key for a v2 hidden service descriptor,
23965 fall back to the v0 hidden service descriptor and log a bug message.
23966 Workaround for bug 1024.
23967 - In very rare situations new hidden service descriptors were
23968 published earlier than 30 seconds after the last change to the
23969 service. (We currently think that a hidden service descriptor
23970 that's been stable for 30 seconds is worth publishing.)
23971 - If a hidden service sends us an END cell, do not consider
23972 retrying the connection; just close it. Patch from rovv.
23973 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
23974 service directories if they have no advertised dir port. Bugfix
23977 o Minor bugfixes (tools):
23978 - In the torify(1) manpage, mention that tsocks will leak your
23981 o Minor bugfixes (controllers):
23982 - If the controller claimed responsibility for a stream, but that
23983 stream never finished making its connection, it would live
23984 forever in circuit_wait state. Now we close it after SocksTimeout
23985 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
23986 - Make DNS resolved controller events into "CLOSED", not
23987 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
23989 - The control port would close the connection before flushing long
23990 replies, such as the network consensus, if a QUIT command was issued
23991 before the reply had completed. Now, the control port flushes all
23992 pending replies before closing the connection. Also fix a spurious
23993 warning when a QUIT command is issued after a malformed or rejected
23994 AUTHENTICATE command, but before the connection was closed. Patch
23995 by Marcus Griep. Fixes bugs 1015 and 1016.
23996 - Fix a bug that made stream bandwidth get misreported to the
23999 o Deprecated and removed features:
24000 - The old "tor --version --version" command, which would print out
24001 the subversion "Id" of most of the source files, is now removed. It
24002 turned out to be less useful than we'd expected, and harder to
24004 - RedirectExits has been removed. It was deprecated since
24006 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
24007 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
24008 - Cell pools are now always enabled; --disable-cell-pools is ignored.
24009 - Directory mirrors no longer fetch the v1 directory or
24010 running-routers files. They are obsolete, and nobody asks for them
24011 anymore. This is the first step to making v1 authorities obsolete.
24012 - Take out the TestVia config option, since it was a workaround for
24013 a bug that was fixed in Tor 0.1.1.21.
24014 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
24015 HiddenServiceExcludeNodes as obsolete: they never worked properly,
24016 and nobody seems to be using them. Fixes bug 754. Bugfix on
24017 0.1.0.1-rc. Patch from Christian Wilms.
24018 - Remove all backward-compatibility code for relays running
24019 versions of Tor so old that they no longer work at all on the
24022 o Code simplifications and refactoring:
24023 - Tool-assisted documentation cleanup. Nearly every function or
24024 static variable in Tor should have its own documentation now.
24025 - Rename the confusing or_is_obsolete field to the more appropriate
24026 is_bad_for_new_circs, and move it to or_connection_t where it
24028 - Move edge-only flags from connection_t to edge_connection_t: not
24029 only is this better coding, but on machines of plausible alignment,
24030 it should save 4-8 bytes per connection_t. "Every little bit helps."
24031 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
24032 for consistency; keep old option working for backward compatibility.
24033 - Simplify the code for finding connections to use for a circuit.
24034 - Revise the connection_new functions so that a more typesafe variant
24035 exists. This will work better with Coverity, and let us find any
24036 actual mistakes we're making here.
24037 - Refactor unit testing logic so that dmalloc can be used sensibly
24038 with unit tests to check for memory leaks.
24039 - Move all hidden-service related fields from connection and circuit
24040 structure to substructures: this way they won't eat so much memory.
24041 - Squeeze 2-5% out of client performance (according to oprofile) by
24042 improving the implementation of some policy-manipulation functions.
24043 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
24044 be more efficient. Formerly it was quadratic in the number of
24045 servers; now it should be linear. Fixes bug 509.
24046 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
24047 and n_conn_id_digest fields into a separate structure that's
24048 only needed when the circuit has not yet attached to an n_conn.
24049 - Optimize out calls to time(NULL) that occur for every IO operation,
24050 or for every cell. On systems like Windows where time() is a
24051 slow syscall, this fix will be slightly helpful.
24054 Changes in version 0.2.0.35 - 2009-06-24
24056 - Avoid crashing in the presence of certain malformed descriptors.
24057 Found by lark, and by automated fuzzing.
24058 - Fix an edge case where a malicious exit relay could convince a
24059 controller that the client's DNS question resolves to an internal IP
24060 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
24063 - Finally fix the bug where dynamic-IP relays disappear when their
24064 IP address changes: directory mirrors were mistakenly telling
24065 them their old address if they asked via begin_dir, so they
24066 never got an accurate answer about their new address, so they
24067 just vanished after a day. For belt-and-suspenders, relays that
24068 don't set Address in their config now avoid using begin_dir for
24069 all direct connections. Should fix bugs 827, 883, and 900.
24070 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
24071 that would occur on some exit nodes when DNS failures and timeouts
24072 occurred in certain patterns. Fix for bug 957.
24075 - When starting with a cache over a few days old, do not leak
24076 memory for the obsolete router descriptors in it. Bugfix on
24077 0.2.0.33; fixes bug 672.
24078 - Hidden service clients didn't use a cached service descriptor that
24079 was older than 15 minutes, but wouldn't fetch a new one either,
24080 because there was already one in the cache. Now, fetch a v2
24081 descriptor unless the same descriptor was added to the cache within
24082 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
24085 Changes in version 0.2.0.34 - 2009-02-08
24086 Tor 0.2.0.34 features several more security-related fixes. You should
24087 upgrade, especially if you run an exit relay (remote crash) or a
24088 directory authority (remote infinite loop), or you're on an older
24089 (pre-XP) or not-recently-patched Windows (remote exploit).
24091 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
24092 have many known flaws, and nobody should be using them. You should
24093 upgrade. If you're using a Linux or BSD and its packages are obsolete,
24094 stop using those packages and upgrade anyway.
24097 - Fix an infinite-loop bug on handling corrupt votes under certain
24098 circumstances. Bugfix on 0.2.0.8-alpha.
24099 - Fix a temporary DoS vulnerability that could be performed by
24100 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
24101 - Avoid a potential crash on exit nodes when processing malformed
24102 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
24103 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
24104 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
24107 - Fix compilation on systems where time_t is a 64-bit integer.
24108 Patch from Matthias Drochner.
24109 - Don't consider expiring already-closed client connections. Fixes
24110 bug 893. Bugfix on 0.0.2pre20.
24113 Changes in version 0.2.0.33 - 2009-01-21
24114 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
24115 useful to users. It also finally fixes a bug where a relay or client
24116 that's been off for many days would take a long time to bootstrap.
24118 This update also fixes an important security-related bug reported by
24119 Ilja van Sprundel. You should upgrade. (We'll send out more details
24120 about the bug once people have had some time to upgrade.)
24123 - Fix a heap-corruption bug that may be remotely triggerable on
24124 some platforms. Reported by Ilja van Sprundel.
24127 - When a stream at an exit relay is in state "resolving" or
24128 "connecting" and it receives an "end" relay cell, the exit relay
24129 would silently ignore the end cell and not close the stream. If
24130 the client never closes the circuit, then the exit relay never
24131 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
24132 reported by "wood".
24133 - When sending CREATED cells back for a given circuit, use a 64-bit
24134 connection ID to find the right connection, rather than an addr:port
24135 combination. Now that we can have multiple OR connections between
24136 the same ORs, it is no longer possible to use addr:port to uniquely
24137 identify a connection.
24138 - Bridge relays that had DirPort set to 0 would stop fetching
24139 descriptors shortly after startup, and then briefly resume
24140 after a new bandwidth test and/or after publishing a new bridge
24141 descriptor. Bridge users that try to bootstrap from them would
24142 get a recent networkstatus but would get descriptors from up to
24143 18 hours earlier, meaning most of the descriptors were obsolete
24144 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
24145 - Prevent bridge relays from serving their 'extrainfo' document
24146 to anybody who asks, now that extrainfo docs include potentially
24147 sensitive aggregated client geoip summaries. Bugfix on
24149 - If the cached networkstatus consensus is more than five days old,
24150 discard it rather than trying to use it. In theory it could be
24151 useful because it lists alternate directory mirrors, but in practice
24152 it just means we spend many minutes trying directory mirrors that
24153 are long gone from the network. Also discard router descriptors as
24154 we load them if they are more than five days old, since the onion
24155 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
24158 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
24159 could make gcc generate non-functional binary search code. Bugfix
24161 - Build correctly on platforms without socklen_t.
24162 - Compile without warnings on solaris.
24163 - Avoid potential crash on internal error during signature collection.
24164 Fixes bug 864. Patch from rovv.
24165 - Correct handling of possible malformed authority signing key
24166 certificates with internal signature types. Fixes bug 880.
24167 Bugfix on 0.2.0.3-alpha.
24168 - Fix a hard-to-trigger resource leak when logging credential status.
24170 - When we can't initialize DNS because the network is down, do not
24171 automatically stop Tor from starting. Instead, we retry failed
24172 dns_init() every 10 minutes, and change the exit policy to reject
24173 *:* until one succeeds. Fixes bug 691.
24174 - Use 64 bits instead of 32 bits for connection identifiers used with
24175 the controller protocol, to greatly reduce risk of identifier reuse.
24176 - When we're choosing an exit node for a circuit, and we have
24177 no pending streams, choose a good general exit rather than one that
24178 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
24179 - Fix another case of assuming, when a specific exit is requested,
24180 that we know more than the user about what hosts it allows.
24181 Fixes one case of bug 752. Patch from rovv.
24182 - Clip the MaxCircuitDirtiness config option to a minimum of 10
24183 seconds. Warn the user if lower values are given in the
24184 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
24185 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
24186 user if lower values are given in the configuration. Bugfix on
24187 0.1.1.17-rc. Patch by Sebastian.
24188 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
24189 the cache because we already had a v0 descriptor with the same ID.
24190 Bugfix on 0.2.0.18-alpha.
24191 - Fix a race condition when freeing keys shared between main thread
24192 and CPU workers that could result in a memory leak. Bugfix on
24193 0.1.0.1-rc. Fixes bug 889.
24194 - Send a valid END cell back when a client tries to connect to a
24195 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
24196 840. Patch from rovv.
24197 - Check which hops rendezvous stream cells are associated with to
24198 prevent possible guess-the-streamid injection attacks from
24199 intermediate hops. Fixes another case of bug 446. Based on patch
24201 - If a broken client asks a non-exit router to connect somewhere,
24202 do not even do the DNS lookup before rejecting the connection.
24203 Fixes another case of bug 619. Patch from rovv.
24204 - When a relay gets a create cell it can't decrypt (e.g. because it's
24205 using the wrong onion key), we were dropping it and letting the
24206 client time out. Now actually answer with a destroy cell. Fixes
24207 bug 904. Bugfix on 0.0.2pre8.
24209 o Minor bugfixes (hidden services):
24210 - Do not throw away existing introduction points on SIGHUP. Bugfix on
24211 0.0.6pre1. Patch by Karsten. Fixes bug 874.
24214 - Report the case where all signatures in a detached set are rejected
24215 differently than the case where there is an error handling the
24217 - When we realize that another process has modified our cached
24218 descriptors, print out a more useful error message rather than
24219 triggering an assertion. Fixes bug 885. Patch from Karsten.
24220 - Implement the 0x20 hack to better resist DNS poisoning: set the
24221 case on outgoing DNS requests randomly, and reject responses that do
24222 not match the case correctly. This logic can be disabled with the
24223 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
24224 of servers that do not reliably preserve case in replies. See
24225 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
24227 - Check DNS replies for more matching fields to better resist DNS
24229 - Never use OpenSSL compression: it wastes RAM and CPU trying to
24230 compress cells, which are basically all encrypted, compressed, or
24234 Changes in version 0.2.0.32 - 2008-11-20
24235 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
24236 packages (and maybe other packages) noticed by Theo de Raadt, fixes
24237 a smaller security flaw that might allow an attacker to access local
24238 services, further improves hidden service performance, and fixes a
24239 variety of other issues.
24242 - The "User" and "Group" config options did not clear the
24243 supplementary group entries for the Tor process. The "User" option
24244 is now more robust, and we now set the groups to the specified
24245 user's primary group. The "Group" option is now ignored. For more
24246 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
24247 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
24248 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
24249 - The "ClientDNSRejectInternalAddresses" config option wasn't being
24250 consistently obeyed: if an exit relay refuses a stream because its
24251 exit policy doesn't allow it, we would remember what IP address
24252 the relay said the destination address resolves to, even if it's
24253 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
24256 - Fix a DOS opportunity during the voting signature collection process
24257 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
24259 o Major bugfixes (hidden services):
24260 - When fetching v0 and v2 rendezvous service descriptors in parallel,
24261 we were failing the whole hidden service request when the v0
24262 descriptor fetch fails, even if the v2 fetch is still pending and
24263 might succeed. Similarly, if the last v2 fetch fails, we were
24264 failing the whole hidden service request even if a v0 fetch is
24265 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
24266 - When extending a circuit to a hidden service directory to upload a
24267 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
24268 requests failed, because the router descriptor has not been
24269 downloaded yet. In these cases, do not attempt to upload the
24270 rendezvous descriptor, but wait until the router descriptor is
24271 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
24272 descriptor from a hidden service directory for which the router
24273 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
24277 - Fix several infrequent memory leaks spotted by Coverity.
24278 - When testing for libevent functions, set the LDFLAGS variable
24279 correctly. Found by Riastradh.
24280 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
24281 bootstrapping with tunneled directory connections. Bugfix on
24282 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
24283 - When asked to connect to A.B.exit:80, if we don't know the IP for A
24284 and we know that server B rejects most-but-not all connections to
24285 port 80, we would previously reject the connection. Now, we assume
24286 the user knows what they were asking for. Fixes bug 752. Bugfix
24287 on 0.0.9rc5. Diagnosed by BarkerJr.
24288 - If we overrun our per-second write limits a little, count this as
24289 having used up our write allocation for the second, and choke
24290 outgoing directory writes. Previously, we had only counted this when
24291 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
24292 Bugfix on 0.2.0.x (??).
24293 - Remove the old v2 directory authority 'lefkada' from the default
24294 list. It has been gone for many months.
24295 - Stop doing unaligned memory access that generated bus errors on
24296 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
24297 - Make USR2 log-level switch take effect immediately. Bugfix on
24300 o Minor bugfixes (controller):
24301 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
24302 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
24305 Changes in version 0.2.0.31 - 2008-09-03
24306 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
24307 a big bug we're seeing where in rare cases traffic from one Tor stream
24308 gets mixed into another stream, and fixes a variety of smaller issues.
24311 - Make sure that two circuits can never exist on the same connection
24312 with the same circuit ID, even if one is marked for close. This
24313 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
24314 - Relays now reject risky extend cells: if the extend cell includes
24315 a digest of all zeroes, or asks to extend back to the relay that
24316 sent the extend cell, tear down the circuit. Ideas suggested
24318 - If not enough of our entry guards are available so we add a new
24319 one, we might use the new one even if it overlapped with the
24320 current circuit's exit relay (or its family). Anonymity bugfix
24321 pointed out by rovv.
24324 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
24325 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
24326 - Correctly detect the presence of the linux/netfilter_ipv4.h header
24327 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
24328 - Pick size of default geoip filename string correctly on windows.
24329 Fixes bug 806. Bugfix on 0.2.0.30.
24330 - Make the autoconf script accept the obsolete --with-ssl-dir
24331 option as an alias for the actually-working --with-openssl-dir
24332 option. Fix the help documentation to recommend --with-openssl-dir.
24333 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
24334 - When using the TransPort option on OpenBSD, and using the User
24335 option to change UID and drop privileges, make sure to open
24336 /dev/pf before dropping privileges. Fixes bug 782. Patch from
24337 Christopher Davis. Bugfix on 0.1.2.1-alpha.
24338 - Try to attach connections immediately upon receiving a RENDEZVOUS2
24339 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
24340 on the client side when connecting to a hidden service. Bugfix
24341 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
24342 - When closing an application-side connection because its circuit is
24343 getting torn down, generate the stream event correctly. Bugfix on
24344 0.1.2.x. Anonymous patch.
24347 Changes in version 0.2.0.30 - 2008-07-15
24348 This new stable release switches to a more efficient directory
24349 distribution design, adds features to make connections to the Tor
24350 network harder to block, allows Tor to act as a DNS proxy, adds separate
24351 rate limiting for relayed traffic to make it easier for clients to
24352 become relays, fixes a variety of potential anonymity problems, and
24353 includes the usual huge pile of other features and bug fixes.
24355 o New v3 directory design:
24356 - Tor now uses a new way to learn about and distribute information
24357 about the network: the directory authorities vote on a common
24358 network status document rather than each publishing their own
24359 opinion. Now clients and caches download only one networkstatus
24360 document to bootstrap, rather than downloading one for each
24361 authority. Clients only download router descriptors listed in
24362 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
24364 - Set up moria1, tor26, and dizum as v3 directory authorities
24365 in addition to being v2 authorities. Also add three new ones:
24366 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
24367 dannenberg (run by CCC).
24368 - Switch to multi-level keys for directory authorities: now their
24369 long-term identity key can be kept offline, and they periodically
24370 generate a new signing key. Clients fetch the "key certificates"
24371 to keep up to date on the right keys. Add a standalone tool
24372 "tor-gencert" to generate key certificates. Implements proposal 103.
24373 - Add a new V3AuthUseLegacyKey config option to make it easier for
24374 v3 authorities to change their identity keys if another bug like
24375 Debian's OpenSSL RNG flaw appears.
24376 - Authorities and caches fetch the v2 networkstatus documents
24377 less often, now that v3 is recommended.
24379 o Make Tor connections stand out less on the wire:
24380 - Use an improved TLS handshake designed by Steven Murdoch in proposal
24381 124, as revised in proposal 130. The new handshake is meant to
24382 be harder for censors to fingerprint, and it adds the ability
24383 to detect certain kinds of man-in-the-middle traffic analysis
24384 attacks. The new handshake format includes version negotiation for
24385 OR connections as described in proposal 105, which will allow us
24386 to improve Tor's link protocol more safely in the future.
24387 - Enable encrypted directory connections by default for non-relays,
24388 so censor tools that block Tor directory connections based on their
24389 plaintext patterns will no longer work. This means Tor works in
24390 certain censored countries by default again.
24391 - Stop including recognizeable strings in the commonname part of
24392 Tor's x509 certificates.
24394 o Implement bridge relays:
24395 - Bridge relays (or "bridges" for short) are Tor relays that aren't
24396 listed in the main Tor directory. Since there is no complete public
24397 list of them, even an ISP that is filtering connections to all the
24398 known Tor relays probably won't be able to block all the bridges.
24399 See doc/design-paper/blocking.pdf and proposal 125 for details.
24400 - New config option BridgeRelay that specifies you want to be a
24401 bridge relay rather than a normal relay. When BridgeRelay is set
24402 to 1, then a) you cache dir info even if your DirPort ins't on,
24403 and b) the default for PublishServerDescriptor is now "bridge"
24404 rather than "v2,v3".
24405 - New config option "UseBridges 1" for clients that want to use bridge
24406 relays instead of ordinary entry guards. Clients then specify
24407 bridge relays by adding "Bridge" lines to their config file. Users
24408 can learn about a bridge relay either manually through word of
24409 mouth, or by one of our rate-limited mechanisms for giving out
24410 bridge addresses without letting an attacker easily enumerate them
24411 all. See https://www.torproject.org/bridges for details.
24412 - Bridge relays behave like clients with respect to time intervals
24413 for downloading new v3 consensus documents -- otherwise they
24414 stand out. Bridge users now wait until the end of the interval,
24415 so their bridge relay will be sure to have a new consensus document.
24417 o Implement bridge directory authorities:
24418 - Bridge authorities are like normal directory authorities, except
24419 they don't serve a list of known bridges. Therefore users that know
24420 a bridge's fingerprint can fetch a relay descriptor for that bridge,
24421 including fetching updates e.g. if the bridge changes IP address,
24422 yet an attacker can't just fetch a list of all the bridges.
24423 - Set up Tonga as the default bridge directory authority.
24424 - Bridge authorities refuse to serve bridge descriptors or other
24425 bridge information over unencrypted connections (that is, when
24426 responding to direct DirPort requests rather than begin_dir cells.)
24427 - Bridge directory authorities do reachability testing on the
24428 bridges they know. They provide router status summaries to the
24429 controller via "getinfo ns/purpose/bridge", and also dump summaries
24430 to a file periodically, so we can keep internal stats about which
24431 bridges are functioning.
24432 - If bridge users set the UpdateBridgesFromAuthority config option,
24433 but the digest they ask for is a 404 on the bridge authority,
24434 they fall back to contacting the bridge directly.
24435 - Bridges always use begin_dir to publish their server descriptor to
24436 the bridge authority using an anonymous encrypted tunnel.
24437 - Early work on a "bridge community" design: if bridge authorities set
24438 the BridgePassword config option, they will serve a snapshot of
24439 known bridge routerstatuses from their DirPort to anybody who
24440 knows that password. Unset by default.
24441 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
24442 report sanitized aggregated summaries in their extra-info documents
24443 privately to the bridge authority, listing which countries are
24444 able to reach them. We hope this mechanism will let us learn when
24445 certain countries start trying to block bridges.
24446 - Bridge authorities write bridge descriptors to disk, so they can
24447 reload them after a reboot. They can also export the descriptors
24448 to other programs, so we can distribute them to blocked users via
24449 the BridgeDB interface, e.g. via https://bridges.torproject.org/
24450 and bridges@torproject.org.
24452 o Tor can be a DNS proxy:
24453 - The new client-side DNS proxy feature replaces the need for
24454 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
24455 for DNS requests on port 9999, use the Tor network to resolve them
24456 anonymously, and send the reply back like a regular DNS server.
24457 The code still only implements a subset of DNS.
24458 - Add a new AutomapHostsOnResolve option: when it is enabled, any
24459 resolve request for hosts matching a given pattern causes Tor to
24460 generate an internal virtual address mapping for that host. This
24461 allows DNSPort to work sensibly with hidden service users. By
24462 default, .exit and .onion addresses are remapped; the list of
24463 patterns can be reconfigured with AutomapHostsSuffixes.
24464 - Add an "-F" option to tor-resolve to force a resolve for a .onion
24465 address. Thanks to the AutomapHostsOnResolve option, this is no
24466 longer a completely silly thing to do.
24468 o Major features (relay usability):
24469 - New config options RelayBandwidthRate and RelayBandwidthBurst:
24470 a separate set of token buckets for relayed traffic. Right now
24471 relayed traffic is defined as answers to directory requests, and
24472 OR connections that don't have any local circuits on them. See
24473 proposal 111 for details.
24474 - Create listener connections before we setuid to the configured
24475 User and Group. Now non-Windows users can choose port values
24476 under 1024, start Tor as root, and have Tor bind those ports
24477 before it changes to another UID. (Windows users could already
24479 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
24480 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
24481 on "vserver" accounts. Patch from coderman.
24483 o Major features (directory authorities):
24484 - Directory authorities track weighted fractional uptime and weighted
24485 mean-time-between failures for relays. WFU is suitable for deciding
24486 whether a node is "usually up", while MTBF is suitable for deciding
24487 whether a node is "likely to stay up." We need both, because
24488 "usually up" is a good requirement for guards, while "likely to
24489 stay up" is a good requirement for long-lived connections.
24490 - Directory authorities use a new formula for selecting which relays
24491 to advertise as Guards: they must be in the top 7/8 in terms of
24492 how long we have known about them, and above the median of those
24493 nodes in terms of weighted fractional uptime.
24494 - Directory authorities use a new formula for selecting which relays
24495 to advertise as Stable: when we have 4 or more days of data, use
24496 median measured MTBF rather than median declared uptime. Implements
24498 - Directory authorities accept and serve "extra info" documents for
24499 routers. Routers now publish their bandwidth-history lines in the
24500 extra-info docs rather than the main descriptor. This step saves
24501 60% (!) on compressed router descriptor downloads. Servers upload
24502 extra-info docs to any authority that accepts them; directory
24503 authorities now allow multiple router descriptors and/or extra
24504 info documents to be uploaded in a single go. Authorities, and
24505 caches that have been configured to download extra-info documents,
24506 download them as needed. Implements proposal 104.
24507 - Authorities now list relays who have the same nickname as
24508 a different named relay, but list them with a new flag:
24509 "Unnamed". Now we can make use of relays that happen to pick the
24510 same nickname as a server that registered two years ago and then
24511 disappeared. Implements proposal 122.
24512 - Store routers in a file called cached-descriptors instead of in
24513 cached-routers. Initialize cached-descriptors from cached-routers
24514 if the old format is around. The new format allows us to store
24515 annotations along with descriptors, to record the time we received
24516 each descriptor, its source, and its purpose: currently one of
24517 general, controller, or bridge.
24519 o Major features (other):
24520 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
24521 Tor can warn and/or refuse connections to ports commonly used with
24522 vulnerable-plaintext protocols. Currently we warn on ports 23,
24523 109, 110, and 143, but we don't reject any. Based on proposal 129
24524 by Kevin Bauer and Damon McCoy.
24525 - Integrate Karsten Loesing's Google Summer of Code project to publish
24526 hidden service descriptors on a set of redundant relays that are a
24527 function of the hidden service address. Now we don't have to rely
24528 on three central hidden service authorities for publishing and
24529 fetching every hidden service descriptor. Implements proposal 114.
24530 - Allow tunnelled directory connections to ask for an encrypted
24531 "begin_dir" connection or an anonymized "uses a full Tor circuit"
24532 connection independently. Now we can make anonymized begin_dir
24533 connections for (e.g.) more secure hidden service posting and
24536 o Major bugfixes (crashes and assert failures):
24537 - Stop imposing an arbitrary maximum on the number of file descriptors
24538 used for busy servers. Bug reported by Olaf Selke; patch from
24540 - Avoid possible failures when generating a directory with routers
24541 with over-long versions strings, or too many flags set.
24542 - Fix a rare assert error when we're closing one of our threads:
24543 use a mutex to protect the list of logs, so we never write to the
24544 list as it's being freed. Fixes the very rare bug 575, which is
24545 kind of the revenge of bug 222.
24546 - Avoid segfault in the case where a badly behaved v2 versioning
24547 directory sends a signed networkstatus with missing client-versions.
24548 - When we hit an EOF on a log (probably because we're shutting down),
24549 don't try to remove the log from the list: just mark it as
24550 unusable. (Bulletproofs against bug 222.)
24552 o Major bugfixes (code security fixes):
24553 - Detect size overflow in zlib code. Reported by Justin Ferguson and
24555 - Rewrite directory tokenization code to never run off the end of
24556 a string. Fixes bug 455. Patch from croup.
24557 - Be more paranoid about overwriting sensitive memory on free(),
24558 as a defensive programming tactic to ensure forward secrecy.
24560 o Major bugfixes (anonymity fixes):
24561 - Reject requests for reverse-dns lookup of names that are in
24562 a private address space. Patch from lodger.
24563 - Never report that we've used more bandwidth than we're willing to
24564 relay: it leaks how much non-relay traffic we're using. Resolves
24566 - As a client, do not believe any server that tells us that an
24567 address maps to an internal address space.
24568 - Warn about unsafe ControlPort configurations.
24569 - Directory authorities now call routers Fast if their bandwidth is
24570 at least 100KB/s, and consider their bandwidth adequate to be a
24571 Guard if it is at least 250KB/s, no matter the medians. This fix
24572 complements proposal 107.
24573 - Directory authorities now never mark more than 2 servers per IP as
24574 Valid and Running (or 5 on addresses shared by authorities).
24575 Implements proposal 109, by Kevin Bauer and Damon McCoy.
24576 - If we're a relay, avoid picking ourselves as an introduction point,
24577 a rendezvous point, or as the final hop for internal circuits. Bug
24578 reported by taranis and lodger.
24579 - Exit relays that are used as a client can now reach themselves
24580 using the .exit notation, rather than just launching an infinite
24581 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
24582 - Fix a bug where, when we were choosing the 'end stream reason' to
24583 put in our relay end cell that we send to the exit relay, Tor
24584 clients on Windows were sometimes sending the wrong 'reason'. The
24585 anonymity problem is that exit relays may be able to guess whether
24586 the client is running Windows, thus helping partition the anonymity
24587 set. Down the road we should stop sending reasons to exit relays,
24588 or otherwise prevent future versions of this bug.
24589 - Only update guard status (usable / not usable) once we have
24590 enough directory information. This was causing us to discard all our
24591 guards on startup if we hadn't been running for a few weeks. Fixes
24593 - When our directory information has been expired for a while, stop
24594 being willing to build circuits using it. Fixes bug 401.
24596 o Major bugfixes (peace of mind for relay operators)
24597 - Non-exit relays no longer answer "resolve" relay cells, so they
24598 can't be induced to do arbitrary DNS requests. (Tor clients already
24599 avoid using non-exit relays for resolve cells, but now servers
24600 enforce this too.) Fixes bug 619. Patch from lodger.
24601 - When we setconf ClientOnly to 1, close any current OR and Dir
24602 listeners. Reported by mwenge.
24604 o Major bugfixes (other):
24605 - If we only ever used Tor for hidden service lookups or posts, we
24606 would stop building circuits and start refusing connections after
24607 24 hours, since we falsely believed that Tor was dormant. Reported
24609 - Add a new __HashedControlSessionPassword option for controllers
24610 to use for one-off session password hashes that shouldn't get
24611 saved to disk by SAVECONF --- Vidalia users were accumulating a
24612 pile of HashedControlPassword lines in their torrc files, one for
24613 each time they had restarted Tor and then clicked Save. Make Tor
24614 automatically convert "HashedControlPassword" to this new option but
24615 only when it's given on the command line. Partial fix for bug 586.
24616 - Patch from "Andrew S. Lists" to catch when we contact a directory
24617 mirror at IP address X and he says we look like we're coming from
24618 IP address X. Otherwise this would screw up our address detection.
24619 - Reject uploaded descriptors and extrainfo documents if they're
24620 huge. Otherwise we'll cache them all over the network and it'll
24621 clog everything up. Suggested by Aljosha Judmayer.
24622 - When a hidden service was trying to establish an introduction point,
24623 and Tor *did* manage to reuse one of the preemptively built
24624 circuits, it didn't correctly remember which one it used,
24625 so it asked for another one soon after, until there were no
24626 more preemptive circuits, at which point it launched one from
24627 scratch. Bugfix on 0.0.9.x.
24629 o Rate limiting and load balancing improvements:
24630 - When we add data to a write buffer in response to the data on that
24631 write buffer getting low because of a flush, do not consider the
24632 newly added data as a candidate for immediate flushing, but rather
24633 make it wait until the next round of writing. Otherwise, we flush
24634 and refill recursively, and a single greedy TLS connection can
24635 eat all of our bandwidth.
24636 - When counting the number of bytes written on a TLS connection,
24637 look at the BIO actually used for writing to the network, not
24638 at the BIO used (sometimes) to buffer data for the network.
24639 Looking at different BIOs could result in write counts on the
24640 order of ULONG_MAX. Fixes bug 614.
24641 - If we change our MaxAdvertisedBandwidth and then reload torrc,
24642 Tor won't realize it should publish a new relay descriptor. Fixes
24643 bug 688, reported by mfr.
24644 - Avoid using too little bandwidth when our clock skips a few seconds.
24645 - Choose which bridge to use proportional to its advertised bandwidth,
24646 rather than uniformly at random. This should speed up Tor for
24647 bridge users. Also do this for people who set StrictEntryNodes.
24649 o Bootstrapping faster and building circuits more intelligently:
24650 - Fix bug 660 that was preventing us from knowing that we should
24651 preemptively build circuits to handle expected directory requests.
24652 - When we're checking if we have enough dir info for each relay
24653 to begin establishing circuits, make sure that we actually have
24654 the descriptor listed in the consensus, not just any descriptor.
24655 - Correctly notify one-hop connections when a circuit build has
24656 failed. Possible fix for bug 669. Found by lodger.
24657 - Clients now hold circuitless TLS connections open for 1.5 times
24658 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
24659 rebuild a new circuit over them within that timeframe. Previously,
24660 they held them open only for KeepalivePeriod (5 minutes).
24662 o Performance improvements (memory):
24663 - Add OpenBSD malloc code from "phk" as an optional malloc
24664 replacement on Linux: some glibc libraries do very poorly with
24665 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
24666 ./configure to get the replacement malloc code.
24667 - Switch our old ring buffer implementation for one more like that
24668 used by free Unix kernels. The wasted space in a buffer with 1mb
24669 of data will now be more like 8k than 1mb. The new implementation
24670 also avoids realloc();realloc(); patterns that can contribute to
24671 memory fragmentation.
24672 - Change the way that Tor buffers data that it is waiting to write.
24673 Instead of queueing data cells in an enormous ring buffer for each
24674 client->OR or OR->OR connection, we now queue cells on a separate
24675 queue for each circuit. This lets us use less slack memory, and
24676 will eventually let us be smarter about prioritizing different kinds
24678 - Reference-count and share copies of address policy entries; only 5%
24679 of them were actually distinct.
24680 - Tune parameters for cell pool allocation to minimize amount of
24682 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
24683 for every single inactive connection_t. Free items from the
24684 4k/16k-buffer free lists when they haven't been used for a while.
24685 - Make memory debugging information describe more about history
24686 of cell allocation, so we can help reduce our memory use.
24687 - Be even more aggressive about releasing RAM from small
24688 empty buffers. Thanks to our free-list code, this shouldn't be too
24689 performance-intensive.
24690 - Log malloc statistics from mallinfo() on platforms where it exists.
24691 - Use memory pools to allocate cells with better speed and memory
24692 efficiency, especially on platforms where malloc() is inefficient.
24693 - Add a --with-tcmalloc option to the configure script to link
24694 against tcmalloc (if present). Does not yet search for non-system
24697 o Performance improvements (socket management):
24698 - Count the number of open sockets separately from the number of
24699 active connection_t objects. This will let us avoid underusing
24700 our allocated connection limit.
24701 - We no longer use socket pairs to link an edge connection to an
24702 anonymous directory connection or a DirPort test connection.
24703 Instead, we track the link internally and transfer the data
24704 in-process. This saves two sockets per "linked" connection (at the
24705 client and at the server), and avoids the nasty Windows socketpair()
24707 - We were leaking a file descriptor if Tor started with a zero-length
24708 cached-descriptors file. Patch by "freddy77".
24710 o Performance improvements (CPU use):
24711 - Never walk through the list of logs if we know that no log target
24712 is interested in a given message.
24713 - Call routerlist_remove_old_routers() much less often. This should
24714 speed startup, especially on directory caches.
24715 - Base64 decoding was actually showing up on our profile when parsing
24716 the initial descriptor file; switch to an in-process all-at-once
24717 implementation that's about 3.5x times faster than calling out to
24719 - Use a slightly simpler string hashing algorithm (copying Python's
24720 instead of Java's) and optimize our digest hashing algorithm to take
24721 advantage of 64-bit platforms and to remove some possibly-costly
24723 - When implementing AES counter mode, update only the portions of the
24724 counter buffer that need to change, and don't keep separate
24725 network-order and host-order counters on big-endian hosts (where
24726 they are the same).
24727 - Add an in-place version of aes_crypt() so that we can avoid doing a
24728 needless memcpy() call on each cell payload.
24729 - Use Critical Sections rather than Mutexes for synchronizing threads
24730 on win32; Mutexes are heavier-weight, and designed for synchronizing
24733 o Performance improvements (bandwidth use):
24734 - Don't try to launch new descriptor downloads quite so often when we
24735 already have enough directory information to build circuits.
24736 - Version 1 directories are no longer generated in full. Instead,
24737 authorities generate and serve "stub" v1 directories that list
24738 no servers. This will stop Tor versions 0.1.0.x and earlier from
24739 working, but (for security reasons) nobody should be running those
24741 - Avoid going directly to the directory authorities even if you're a
24742 relay, if you haven't found yourself reachable yet or if you've
24743 decided not to advertise your dirport yet. Addresses bug 556.
24744 - If we've gone 12 hours since our last bandwidth check, and we
24745 estimate we have less than 50KB bandwidth capacity but we could
24746 handle more, do another bandwidth test.
24747 - Support "If-Modified-Since" when answering HTTP requests for
24748 directories, running-routers documents, and v2 and v3 networkstatus
24749 documents. (There's no need to support it for router descriptors,
24750 since those are downloaded by descriptor digest.)
24751 - Stop fetching directory info so aggressively if your DirPort is
24752 on but your ORPort is off; stop fetching v2 dir info entirely.
24753 You can override these choices with the new FetchDirInfoEarly
24756 o Changed config option behavior (features):
24757 - Configuration files now accept C-style strings as values. This
24758 helps encode characters not allowed in the current configuration
24759 file format, such as newline or #. Addresses bug 557.
24760 - Add hidden services and DNSPorts to the list of things that make
24761 Tor accept that it has running ports. Change starting Tor with no
24762 ports from a fatal error to a warning; we might change it back if
24763 this turns out to confuse anybody. Fixes bug 579.
24764 - Make PublishServerDescriptor default to 1, so the default doesn't
24765 have to change as we invent new directory protocol versions.
24766 - Allow people to say PreferTunnelledDirConns rather than
24767 PreferTunneledDirConns, for those alternate-spellers out there.
24768 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
24769 accommodate the growing number of servers that use the default
24770 and are reaching it.
24771 - Make it possible to enable HashedControlPassword and
24772 CookieAuthentication at the same time.
24773 - When a TrackHostExits-chosen exit fails too many times in a row,
24774 stop using it. Fixes bug 437.
24776 o Changed config option behavior (bugfixes):
24777 - Do not read the configuration file when we've only been told to
24778 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
24779 based on patch from Sebastian Hahn.
24780 - Actually validate the options passed to AuthDirReject,
24781 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
24782 - Make "ClientOnly 1" config option disable directory ports too.
24783 - Don't stop fetching descriptors when FetchUselessDescriptors is
24784 set, even if we stop asking for circuits. Bug reported by tup
24786 - Servers used to decline to publish their DirPort if their
24787 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
24788 they look only at BandwidthRate and RelayBandwidthRate.
24789 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
24790 minus 1 byte: the actual maximum declared bandwidth.
24791 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
24792 - Make the NodeFamilies config option work. (Reported by
24793 lodger -- it has never actually worked, even though we added it
24795 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
24796 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
24798 o New config options:
24799 - New configuration options AuthDirMaxServersPerAddr and
24800 AuthDirMaxServersperAuthAddr to override default maximum number
24801 of servers allowed on a single IP address. This is important for
24802 running a test network on a single host.
24803 - Three new config options (AlternateDirAuthority,
24804 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
24805 user selectively replace the default directory authorities by type,
24806 rather than the all-or-nothing replacement that DirServer offers.
24807 - New config options AuthDirBadDir and AuthDirListBadDirs for
24808 authorities to mark certain relays as "bad directories" in the
24809 networkstatus documents. Also supports the "!baddir" directive in
24810 the approved-routers file.
24811 - New config option V2AuthoritativeDirectory that all v2 directory
24812 authorities must set. This lets v3 authorities choose not to serve
24813 v2 directory information.
24815 o Minor features (other):
24816 - When we're not serving v2 directory information, there is no reason
24817 to actually keep any around. Remove the obsolete files and directory
24818 on startup if they are very old and we aren't going to serve them.
24819 - When we negotiate a v2 link-layer connection (not yet implemented),
24820 accept RELAY_EARLY cells and turn them into RELAY cells if we've
24821 negotiated a v1 connection for their next step. Initial steps for
24823 - When we have no consensus, check FallbackNetworkstatusFile (defaults
24824 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
24825 we can start out knowing some directory caches. We don't ship with
24826 a fallback consensus by default though, because it was making
24827 bootstrapping take too long while we tried many down relays.
24828 - Authorities send back an X-Descriptor-Not-New header in response to
24829 an accepted-but-discarded descriptor upload. Partially implements
24831 - If we find a cached-routers file that's been sitting around for more
24832 than 28 days unmodified, then most likely it's a leftover from
24833 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
24835 - When we (as a cache) download a descriptor because it was listed
24836 in a consensus, remember when the consensus was supposed to expire,
24837 and don't expire the descriptor until then.
24838 - Optionally (if built with -DEXPORTMALLINFO) export the output
24839 of mallinfo via http, as tor/mallinfo.txt. Only accessible
24841 - Tag every guard node in our state file with the version that
24842 we believe added it, or with our own version if we add it. This way,
24843 if a user temporarily runs an old version of Tor and then switches
24844 back to a new one, she doesn't automatically lose her guards.
24845 - When somebody requests a list of statuses or servers, and we have
24846 none of those, return a 404 rather than an empty 200.
24847 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
24849 - Add an HSAuthorityRecordStats option that hidden service authorities
24850 can use to track statistics of overall hidden service usage without
24851 logging information that would be as useful to an attacker.
24852 - Allow multiple HiddenServicePort directives with the same virtual
24853 port; when they occur, the user is sent round-robin to one
24854 of the target ports chosen at random. Partially fixes bug 393 by
24855 adding limited ad-hoc round-robining.
24856 - Revamp file-writing logic so we don't need to have the entire
24857 contents of a file in memory at once before we write to disk. Tor,
24860 o Minor bugfixes (other):
24861 - Alter the code that tries to recover from unhandled write
24862 errors, to not try to flush onto a socket that's given us
24864 - Directory mirrors no longer include a guess at the client's IP
24865 address if the connection appears to be coming from the same /24
24866 network; it was producing too many wrong guesses.
24867 - If we're trying to flush the last bytes on a connection (for
24868 example, when answering a directory request), reset the
24869 time-to-give-up timeout every time we manage to write something
24871 - Reject router descriptors with out-of-range bandwidthcapacity or
24872 bandwidthburst values.
24873 - If we can't expand our list of entry guards (e.g. because we're
24874 using bridges or we have StrictEntryNodes set), don't mark relays
24875 down when they fail a directory request. Otherwise we're too quick
24876 to mark all our entry points down.
24877 - Authorities no longer send back "400 you're unreachable please fix
24878 it" errors to Tor servers that aren't online all the time. We're
24879 supposed to tolerate these servers now.
24880 - Let directory authorities startup even when they can't generate
24881 a descriptor immediately, e.g. because they don't know their
24883 - Correctly enforce that elements of directory objects do not appear
24884 more often than they are allowed to appear.
24885 - Stop allowing hibernating servers to be "stable" or "fast".
24886 - On Windows, we were preventing other processes from reading
24887 cached-routers while Tor was running. (Reported by janbar)
24888 - Check return values from pthread_mutex functions.
24889 - When opening /dev/null in finish_daemonize(), do not pass the
24890 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
24891 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
24893 o Controller features:
24894 - The GETCONF command now escapes and quotes configuration values
24895 that don't otherwise fit into the torrc file.
24896 - The SETCONF command now handles quoted values correctly.
24897 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
24898 ask about source, timestamp of arrival, purpose, etc. We need
24899 something like this to help Vidalia not do GeoIP lookups on bridge
24901 - Allow multiple HashedControlPassword config lines, to support
24902 multiple controller passwords.
24903 - Accept LF instead of CRLF on controller, since some software has a
24904 hard time generating real Internet newlines.
24905 - Add GETINFO values for the server status events
24906 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
24908 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
24909 GETINFO for Torstat to use until it can switch to using extrainfos.
24910 - New config option CookieAuthFile to choose a new location for the
24911 cookie authentication file, and config option
24912 CookieAuthFileGroupReadable to make it group-readable.
24913 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
24914 match requests to applications. Patch from Robert Hogan.
24915 - Add a RESOLVE command to launch hostname lookups. Original patch
24917 - Add GETINFO status/enough-dir-info to let controllers tell whether
24918 Tor has downloaded sufficient directory information. Patch from Tup.
24919 - You can now use the ControlSocket option to tell Tor to listen for
24920 controller connections on Unix domain sockets on systems that
24921 support them. Patch from Peter Palfrader.
24922 - New "GETINFO address-mappings/*" command to get address mappings
24923 with expiry information. "addr-mappings/*" is now deprecated.
24925 - Add a new config option __DisablePredictedCircuits designed for
24926 use by the controller, when we don't want Tor to build any circuits
24928 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
24929 so we can exit from the middle of the circuit.
24930 - Implement "getinfo status/circuit-established".
24931 - Implement "getinfo status/version/..." so a controller can tell
24932 whether the current version is recommended, and whether any versions
24933 are good, and how many authorities agree. Patch from "shibz".
24934 - Controllers should now specify cache=no or cache=yes when using
24935 the +POSTDESCRIPTOR command.
24936 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
24937 Robert Hogan. Fixes the first part of bug 681.
24938 - When reporting clock skew, and we know that the clock is _at least
24939 as skewed_ as some value, but we don't know the actual value,
24940 report the value as a "minimum skew."
24942 o Controller bugfixes:
24943 - Generate "STATUS_SERVER" events rather than misspelled
24944 "STATUS_SEVER" events. Caught by mwenge.
24945 - Reject controller commands over 1MB in length, so rogue
24946 processes can't run us out of memory.
24947 - Change the behavior of "getinfo status/good-server-descriptor"
24948 so it doesn't return failure when any authority disappears.
24949 - Send NAMESERVER_STATUS messages for a single failed nameserver
24951 - When the DANGEROUS_VERSION controller status event told us we're
24952 running an obsolete version, it used the string "OLD" to describe
24953 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
24954 "OBSOLETE" in both cases.
24955 - Respond to INT and TERM SIGNAL commands before we execute the
24956 signal, in case the signal shuts us down. We had a patch in
24957 0.1.2.1-alpha that tried to do this by queueing the response on
24958 the connection's buffer before shutting down, but that really
24959 isn't the same thing at all. Bug located by Matt Edman.
24960 - Provide DNS expiry times in GMT, not in local time. For backward
24961 compatibility, ADDRMAP events only provide GMT expiry in an extended
24962 field. "GETINFO address-mappings" always does the right thing.
24963 - Use CRLF line endings properly in NS events.
24964 - Make 'getinfo fingerprint' return a 551 error if we're not a
24965 server, so we match what the control spec claims we do. Reported
24967 - Fix a typo in an error message when extendcircuit fails that
24968 caused us to not follow the \r\n-based delimiter protocol. Reported
24970 - When tunneling an encrypted directory connection, and its first
24971 circuit fails, do not leave it unattached and ask the controller
24972 to deal. Fixes the second part of bug 681.
24973 - Treat some 403 responses from directory servers as INFO rather than
24974 WARN-severity events.
24976 o Portability / building / compiling:
24977 - When building with --enable-gcc-warnings, check for whether Apple's
24978 warning "-Wshorten-64-to-32" is available.
24979 - Support compilation to target iPhone; patch from cjacker huang.
24980 To build for iPhone, pass the --enable-iphone option to configure.
24981 - Port Tor to build and run correctly on Windows CE systems, using
24982 the wcecompat library. Contributed by Valerio Lupi.
24983 - Detect non-ASCII platforms (if any still exist) and refuse to
24984 build there: some of our code assumes that 'A' is 65 and so on.
24985 - Clear up some MIPSPro compiler warnings.
24986 - Make autoconf search for libevent, openssl, and zlib consistently.
24987 - Update deprecated macros in configure.in.
24988 - When warning about missing headers, tell the user to let us
24989 know if the compile succeeds anyway, so we can downgrade the
24991 - Include the current subversion revision as part of the version
24992 string: either fetch it directly if we're in an SVN checkout, do
24993 some magic to guess it if we're in an SVK checkout, or use
24994 the last-detected version if we're building from a .tar.gz.
24995 Use this version consistently in log messages.
24996 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
24997 - Read resolv.conf files correctly on platforms where read() returns
24998 partial results on small file reads.
24999 - Build without verbose warnings even on gcc 4.2 and 4.3.
25000 - On Windows, correctly detect errors when listing the contents of
25001 a directory. Fix from lodger.
25002 - Run 'make test' as part of 'make dist', so we stop releasing so
25003 many development snapshots that fail their unit tests.
25004 - Add support to detect Libevent versions in the 1.4.x series
25006 - Add command-line arguments to unit-test executable so that we can
25007 invoke any chosen test from the command line rather than having
25008 to run the whole test suite at once; and so that we can turn on
25009 logging for the unit tests.
25010 - Do not automatically run configure from autogen.sh. This
25011 non-standard behavior tended to annoy people who have built other
25013 - Fix a macro/CPP interaction that was confusing some compilers:
25014 some GCCs don't like #if/#endif pairs inside macro arguments.
25016 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
25017 Fixes bug 704; fix from Steven Murdoch.
25018 - Correctly detect transparent proxy support on Linux hosts that
25019 require in.h to be included before netfilter_ipv4.h. Patch
25022 o Logging improvements:
25023 - When we haven't had any application requests lately, don't bother
25024 logging that we have expired a bunch of descriptors.
25025 - When attempting to open a logfile fails, tell us why.
25026 - Only log guard node status when guard node status has changed.
25027 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
25028 make "INFO" 75% less verbose.
25029 - When SafeLogging is disabled, log addresses along with all TLS
25031 - Report TLS "zero return" case as a "clean close" and "IO error"
25032 as a "close". Stop calling closes "unexpected closes": existing
25033 Tors don't use SSL_close(), so having a connection close without
25034 the TLS shutdown handshake is hardly unexpected.
25035 - When we receive a consensus from the future, warn about skew.
25036 - Make "not enough dir info yet" warnings describe *why* Tor feels
25037 it doesn't have enough directory info yet.
25038 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
25039 consumers. (We already do this on HUP.)
25040 - Give more descriptive well-formedness errors for out-of-range
25041 hidden service descriptor/protocol versions.
25042 - Stop recommending that every server operator send mail to tor-ops.
25043 Resolves bug 597. Bugfix on 0.1.2.x.
25044 - Improve skew reporting: try to give the user a better log message
25045 about how skewed they are, and how much this matters.
25046 - New --quiet command-line option to suppress the default console log.
25047 Good in combination with --hash-password.
25048 - Don't complain that "your server has not managed to confirm that its
25049 ports are reachable" if we haven't been able to build any circuits
25051 - Detect the reason for failing to mmap a descriptor file we just
25052 wrote, and give a more useful log message. Fixes bug 533.
25053 - Always prepend "Bug: " to any log message about a bug.
25054 - When dumping memory usage, list bytes used in buffer memory
25056 - When running with dmalloc, dump more stats on hup and on exit.
25057 - Put a platform string (e.g. "Linux i686") in the startup log
25058 message, so when people paste just their logs, we know if it's
25059 OpenBSD or Windows or what.
25060 - When logging memory usage, break down memory used in buffers by
25062 - When we are reporting the DirServer line we just parsed, we were
25063 logging the second stanza of the key fingerprint, not the first.
25064 - Even though Windows is equally happy with / and \ as path separators,
25065 try to use \ consistently on Windows and / consistently on Unix: it
25066 makes the log messages nicer.
25067 - On OSX, stop warning the user that kqueue support in libevent is
25068 "experimental", since it seems to have worked fine for ages.
25070 o Contributed scripts and tools:
25071 - Update linux-tor-prio.sh script to allow QoS based on the uid of
25072 the Tor process. Patch from Marco Bonetti with tweaks from Mike
25074 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
25075 Unix users an easy way to script their Tor process (e.g. by
25076 adjusting bandwidth based on the time of the day).
25077 - In the exitlist script, only consider the most recently published
25078 server descriptor for each server. Also, when the user requests
25079 a list of servers that _reject_ connections to a given address,
25080 explicitly exclude the IPs that also have servers that accept
25081 connections to that address. Resolves bug 405.
25082 - Include a new contrib/tor-exit-notice.html file that exit relay
25083 operators can put on their website to help reduce abuse queries.
25085 o Newly deprecated features:
25086 - The status/version/num-versioning and status/version/num-concurring
25087 GETINFO controller options are no longer useful in the v3 directory
25088 protocol: treat them as deprecated, and warn when they're used.
25089 - The RedirectExits config option is now deprecated.
25091 o Removed features:
25092 - Drop the old code to choke directory connections when the
25093 corresponding OR connections got full: thanks to the cell queue
25094 feature, OR conns don't get full any more.
25095 - Remove the old "dns worker" server DNS code: it hasn't been default
25096 since 0.1.2.2-alpha, and all the servers are using the new
25098 - Remove the code to generate the oldest (v1) directory format.
25099 - Remove support for the old bw_accounting file: we've been storing
25100 bandwidth accounting information in the state file since
25101 0.1.2.5-alpha. This may result in bandwidth accounting errors
25102 if you try to upgrade from 0.1.1.x or earlier, or if you try to
25103 downgrade to 0.1.1.x or earlier.
25104 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
25105 it, it had no AES, and it hasn't seen any security patches since
25107 - Stop overloading the circuit_t.onionskin field for both "onionskin
25108 from a CREATE cell that we are waiting for a cpuworker to be
25109 assigned" and "onionskin from an EXTEND cell that we are going to
25110 send to an OR as soon as we are connected". Might help with bug 600.
25111 - Remove the tor_strpartition() function: its logic was confused,
25112 and it was only used for one thing that could be implemented far
25114 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
25115 and TorControl.py, as they use the old v0 controller protocol,
25116 and are obsoleted by TorFlow anyway.
25117 - Drop support for v1 rendezvous descriptors, since we never used
25118 them anyway, and the code has probably rotted by now. Based on
25119 patch from Karsten Loesing.
25120 - Stop allowing address masks that do not correspond to bit prefixes.
25121 We have warned about these for a really long time; now it's time
25122 to reject them. (Patch from croup.)
25123 - Remove an optimization in the AES counter-mode code that assumed
25124 that the counter never exceeded 2^68. When the counter can be set
25125 arbitrarily as an IV (as it is by Karsten's new hidden services
25126 code), this assumption no longer holds.
25127 - Disable the SETROUTERPURPOSE controller command: it is now
25131 Changes in version 0.1.2.19 - 2008-01-17
25132 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
25133 exit policy a little bit more conservative so it's safer to run an
25134 exit relay on a home system, and fixes a variety of smaller issues.
25137 - Exit policies now reject connections that are addressed to a
25138 relay's public (external) IP address too, unless
25139 ExitPolicyRejectPrivate is turned off. We do this because too
25140 many relays are running nearby to services that trust them based
25141 on network address.
25144 - When the clock jumps forward a lot, do not allow the bandwidth
25145 buckets to become negative. Fixes bug 544.
25146 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
25147 on every successful resolve. Reported by Mike Perry.
25148 - Purge old entries from the "rephist" database and the hidden
25149 service descriptor database even when DirPort is zero.
25150 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
25151 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
25152 crashing or mis-answering these requests.
25153 - When we decide to send a 503 response to a request for servers, do
25154 not then also send the server descriptors: this defeats the whole
25155 purpose. Fixes bug 539.
25158 - Changing the ExitPolicyRejectPrivate setting should cause us to
25159 rebuild our server descriptor.
25160 - Fix handling of hex nicknames when answering controller requests for
25161 networkstatus by name, or when deciding whether to warn about
25162 unknown routers in a config option. (Patch from mwenge.)
25163 - Fix a couple of hard-to-trigger autoconf problems that could result
25164 in really weird results on platforms whose sys/types.h files define
25165 nonstandard integer types.
25166 - Don't try to create the datadir when running --verify-config or
25167 --hash-password. Resolves bug 540.
25168 - If we were having problems getting a particular descriptor from the
25169 directory caches, and then we learned about a new descriptor for
25170 that router, we weren't resetting our failure count. Reported
25172 - Although we fixed bug 539 (where servers would send HTTP status 503
25173 responses _and_ send a body too), there are still servers out there
25174 that haven't upgraded. Therefore, make clients parse such bodies
25175 when they receive them.
25176 - Run correctly on systems where rlim_t is larger than unsigned long.
25177 This includes some 64-bit systems.
25178 - Run correctly on platforms (like some versions of OS X 10.5) where
25179 the real limit for number of open files is OPEN_FILES, not rlim_max
25180 from getrlimit(RLIMIT_NOFILES).
25181 - Avoid a spurious free on base64 failure.
25182 - Avoid segfaults on certain complex invocations of
25183 router_get_by_hexdigest().
25184 - Fix rare bug on REDIRECTSTREAM control command when called with no
25185 port set: it could erroneously report an error when none had
25189 Changes in version 0.1.2.18 - 2007-10-28
25190 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
25191 hidden service introduction that were causing huge delays, and a big
25192 bug that was causing some servers to disappear from the network status
25193 lists for a few hours each day.
25195 o Major bugfixes (crashes):
25196 - If a connection is shut down abruptly because of something that
25197 happened inside connection_flushed_some(), do not call
25198 connection_finished_flushing(). Should fix bug 451:
25199 "connection_stop_writing: Assertion conn->write_event failed"
25200 Bugfix on 0.1.2.7-alpha.
25201 - Fix possible segfaults in functions called from
25202 rend_process_relay_cell().
25204 o Major bugfixes (hidden services):
25205 - Hidden services were choosing introduction points uniquely by
25206 hexdigest, but when constructing the hidden service descriptor
25207 they merely wrote the (potentially ambiguous) nickname.
25208 - Clients now use the v2 intro format for hidden service
25209 connections: they specify their chosen rendezvous point by identity
25210 digest rather than by (potentially ambiguous) nickname. These
25211 changes could speed up hidden service connections dramatically.
25213 o Major bugfixes (other):
25214 - Stop publishing a new server descriptor just because we get a
25215 HUP signal. This led (in a roundabout way) to some servers getting
25216 dropped from the networkstatus lists for a few hours each day.
25217 - When looking for a circuit to cannibalize, consider family as well
25218 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
25219 circuit cannibalization).
25220 - When a router wasn't listed in a new networkstatus, we were leaving
25221 the flags for that router alone -- meaning it remained Named,
25222 Running, etc -- even though absence from the networkstatus means
25223 that it shouldn't be considered to exist at all anymore. Now we
25224 clear all the flags for routers that fall out of the networkstatus
25225 consensus. Fixes bug 529.
25228 - Don't try to access (or alter) the state file when running
25229 --list-fingerprint or --verify-config or --hash-password. Resolves
25231 - When generating information telling us how to extend to a given
25232 router, do not try to include the nickname if it is
25233 absent. Resolves bug 467.
25234 - Fix a user-triggerable segfault in expand_filename(). (There isn't
25235 a way to trigger this remotely.)
25236 - When sending a status event to the controller telling it that an
25237 OR address is reachable, set the port correctly. (Previously we
25238 were reporting the dir port.)
25239 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
25240 command. Bugfix on 0.1.2.17.
25241 - When loading bandwidth history, do not believe any information in
25242 the future. Fixes bug 434.
25243 - When loading entry guard information, do not believe any information
25245 - When we have our clock set far in the future and generate an
25246 onion key, then re-set our clock to be correct, we should not stop
25247 the onion key from getting rotated.
25248 - On some platforms, accept() can return a broken address. Detect
25249 this more quietly, and deal accordingly. Fixes bug 483.
25250 - It's not actually an error to find a non-pending entry in the DNS
25251 cache when canceling a pending resolve. Don't log unless stuff
25252 is fishy. Resolves bug 463.
25253 - Don't reset trusted dir server list when we set a configuration
25254 option. Patch from Robert Hogan.
25257 Changes in version 0.1.2.17 - 2007-08-30
25258 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
25259 X bundles. Vidalia 0.0.14 makes authentication required for the
25260 ControlPort in the default configuration, which addresses important
25261 security risks. Everybody who uses Vidalia (or another controller)
25264 In addition, this Tor update fixes major load balancing problems with
25265 path selection, which should speed things up a lot once many people
25268 o Major bugfixes (security):
25269 - We removed support for the old (v0) control protocol. It has been
25270 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
25271 become more of a headache than it's worth.
25273 o Major bugfixes (load balancing):
25274 - When choosing nodes for non-guard positions, weight guards
25275 proportionally less, since they already have enough load. Patch
25277 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
25278 will allow fast Tor servers to get more attention.
25279 - When we're upgrading from an old Tor version, forget our current
25280 guards and pick new ones according to the new weightings. These
25281 three load balancing patches could raise effective network capacity
25282 by a factor of four. Thanks to Mike Perry for measurements.
25284 o Major bugfixes (stream expiration):
25285 - Expire not-yet-successful application streams in all cases if
25286 they've been around longer than SocksTimeout. Right now there are
25287 some cases where the stream will live forever, demanding a new
25288 circuit every 15 seconds. Fixes bug 454; reported by lodger.
25290 o Minor features (controller):
25291 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
25292 is valid before any authentication has been received. It tells
25293 a controller what kind of authentication is expected, and what
25294 protocol is spoken. Implements proposal 119.
25296 o Minor bugfixes (performance):
25297 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
25298 greatly speeding up loading cached-routers from disk on startup.
25299 - Disable sentinel-based debugging for buffer code: we squashed all
25300 the bugs that this was supposed to detect a long time ago, and now
25301 its only effect is to change our buffer sizes from nice powers of
25302 two (which platform mallocs tend to like) to values slightly over
25303 powers of two (which make some platform mallocs sad).
25305 o Minor bugfixes (misc):
25306 - If exit bandwidth ever exceeds one third of total bandwidth, then
25307 use the correct formula to weight exit nodes when choosing paths.
25308 Based on patch from Mike Perry.
25309 - Choose perfectly fairly among routers when choosing by bandwidth and
25310 weighting by fraction of bandwidth provided by exits. Previously, we
25311 would choose with only approximate fairness, and correct ourselves
25312 if we ran off the end of the list.
25313 - If we require CookieAuthentication but we fail to write the
25314 cookie file, we would warn but not exit, and end up in a state
25315 where no controller could authenticate. Now we exit.
25316 - If we require CookieAuthentication, stop generating a new cookie
25317 every time we change any piece of our config.
25318 - Refuse to start with certain directory authority keys, and
25319 encourage people using them to stop.
25320 - Terminate multi-line control events properly. Original patch
25322 - Fix a minor memory leak when we fail to find enough suitable
25323 servers to choose a circuit.
25324 - Stop leaking part of the descriptor when we run into a particularly
25325 unparseable piece of it.
25328 Changes in version 0.1.2.16 - 2007-08-01
25329 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
25330 remote attacker in certain situations to rewrite the user's torrc
25331 configuration file. This can completely compromise anonymity of users
25332 in most configurations, including those running the Vidalia bundles,
25333 TorK, etc. Or worse.
25335 o Major security fixes:
25336 - Close immediately after missing authentication on control port;
25337 do not allow multiple authentication attempts.
25340 Changes in version 0.1.2.15 - 2007-07-17
25341 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
25342 problems, fixes compilation on BSD, and fixes a variety of other
25343 bugs. Everybody should upgrade.
25345 o Major bugfixes (compilation):
25346 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
25348 o Major bugfixes (crashes):
25349 - Try even harder not to dereference the first character after
25350 an mmap(). Reported by lodger.
25351 - Fix a crash bug in directory authorities when we re-number the
25352 routerlist while inserting a new router.
25353 - When the cached-routers file is an even multiple of the page size,
25354 don't run off the end and crash. (Fixes bug 455; based on idea
25356 - Fix eventdns.c behavior on Solaris: It is critical to include
25357 orconfig.h _before_ sys/types.h, so that we can get the expected
25358 definition of _FILE_OFFSET_BITS.
25360 o Major bugfixes (security):
25361 - Fix a possible buffer overrun when using BSD natd support. Bug
25363 - When sending destroy cells from a circuit's origin, don't include
25364 the reason for tearing down the circuit. The spec says we didn't,
25365 and now we actually don't. Reported by lodger.
25366 - Keep streamids from different exits on a circuit separate. This
25367 bug may have allowed other routers on a given circuit to inject
25368 cells into streams. Reported by lodger; fixes bug 446.
25369 - If there's a never-before-connected-to guard node in our list,
25370 never choose any guards past it. This way we don't expand our
25371 guard list unless we need to.
25373 o Minor bugfixes (guard nodes):
25374 - Weight guard selection by bandwidth, so that low-bandwidth nodes
25375 don't get overused as guards.
25377 o Minor bugfixes (directory):
25378 - Correctly count the number of authorities that recommend each
25379 version. Previously, we were under-counting by 1.
25380 - Fix a potential crash bug when we load many server descriptors at
25381 once and some of them make others of them obsolete. Fixes bug 458.
25383 o Minor bugfixes (hidden services):
25384 - Stop tearing down the whole circuit when the user asks for a
25385 connection to a port that the hidden service didn't configure.
25388 o Minor bugfixes (misc):
25389 - On Windows, we were preventing other processes from reading
25390 cached-routers while Tor was running. Reported by janbar.
25391 - Fix a possible (but very unlikely) bug in picking routers by
25392 bandwidth. Add a log message to confirm that it is in fact
25393 unlikely. Patch from lodger.
25394 - Backport a couple of memory leak fixes.
25395 - Backport miscellaneous cosmetic bugfixes.
25398 Changes in version 0.1.2.14 - 2007-05-25
25399 Tor 0.1.2.14 changes the addresses of two directory authorities (this
25400 change especially affects those who serve or use hidden services),
25401 and fixes several other crash- and security-related bugs.
25403 o Directory authority changes:
25404 - Two directory authorities (moria1 and moria2) just moved to new
25405 IP addresses. This change will particularly affect those who serve
25406 or use hidden services.
25408 o Major bugfixes (crashes):
25409 - If a directory server runs out of space in the connection table
25410 as it's processing a begin_dir request, it will free the exit stream
25411 but leave it attached to the circuit, leading to unpredictable
25412 behavior. (Reported by seeess, fixes bug 425.)
25413 - Fix a bug in dirserv_remove_invalid() that would cause authorities
25414 to corrupt memory under some really unlikely scenarios.
25415 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
25416 - Avoid segfaults when reading from mmaped descriptor file. (Reported
25419 o Major bugfixes (security):
25420 - When choosing an entry guard for a circuit, avoid using guards
25421 that are in the same family as the chosen exit -- not just guards
25422 that are exactly the chosen exit. (Reported by lodger.)
25424 o Major bugfixes (resource management):
25425 - If a directory authority is down, skip it when deciding where to get
25426 networkstatus objects or descriptors. Otherwise we keep asking
25427 every 10 seconds forever. Fixes bug 384.
25428 - Count it as a failure if we fetch a valid network-status but we
25429 don't want to keep it. Otherwise we'll keep fetching it and keep
25430 not wanting to keep it. Fixes part of bug 422.
25431 - If all of our dirservers have given us bad or no networkstatuses
25432 lately, then stop hammering them once per minute even when we
25433 think they're failed. Fixes another part of bug 422.
25436 - Actually set the purpose correctly for descriptors inserted with
25437 purpose=controller.
25438 - When we have k non-v2 authorities in our DirServer config,
25439 we ignored the last k authorities in the list when updating our
25441 - Correctly back-off from requesting router descriptors that we are
25442 having a hard time downloading.
25443 - Read resolv.conf files correctly on platforms where read() returns
25444 partial results on small file reads.
25445 - Don't rebuild the entire router store every time we get 32K of
25446 routers: rebuild it when the journal gets very large, or when
25447 the gaps in the store get very large.
25450 - When routers publish SVN revisions in their router descriptors,
25451 authorities now include those versions correctly in networkstatus
25453 - Warn when using a version of libevent before 1.3b to run a server on
25454 OSX or BSD: these versions interact badly with userspace threads.
25457 Changes in version 0.1.2.13 - 2007-04-24
25458 This release features some major anonymity fixes, such as safer path
25459 selection; better client performance; faster bootstrapping, better
25460 address detection, and better DNS support for servers; write limiting as
25461 well as read limiting to make servers easier to run; and a huge pile of
25462 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
25464 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
25465 of the Freenode IRC network, remembering his patience and vision for
25466 free speech on the Internet.
25468 o Major features, client performance:
25469 - Weight directory requests by advertised bandwidth. Now we can
25470 let servers enable write limiting but still allow most clients to
25471 succeed at their directory requests. (We still ignore weights when
25472 choosing a directory authority; I hope this is a feature.)
25473 - Stop overloading exit nodes -- avoid choosing them for entry or
25474 middle hops when the total bandwidth available from non-exit nodes
25475 is much higher than the total bandwidth available from exit nodes.
25476 - Rather than waiting a fixed amount of time between retrying
25477 application connections, we wait only 10 seconds for the first,
25478 10 seconds for the second, and 15 seconds for each retry after
25479 that. Hopefully this will improve the expected user experience.
25480 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
25481 to open a stream fails; now we do in more cases. This should
25482 make clients able to find a good exit faster in some cases, since
25483 unhandleable requests will now get an error rather than timing out.
25485 o Major features, client functionality:
25486 - Implement BEGIN_DIR cells, so we can connect to a directory
25487 server via TLS to do encrypted directory requests rather than
25488 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
25489 config options if you like. For now, this feature only works if
25490 you already have a descriptor for the destination dirserver.
25491 - Add support for transparent application connections: this basically
25492 bundles the functionality of trans-proxy-tor into the Tor
25493 mainline. Now hosts with compliant pf/netfilter implementations
25494 can redirect TCP connections straight to Tor without diverting
25495 through SOCKS. (Based on patch from tup.)
25496 - Add support for using natd; this allows FreeBSDs earlier than
25497 5.1.2 to have ipfw send connections through Tor without using
25498 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
25500 o Major features, servers:
25501 - Setting up a dyndns name for your server is now optional: servers
25502 with no hostname or IP address will learn their IP address by
25503 asking the directory authorities. This code only kicks in when you
25504 would normally have exited with a "no address" error. Nothing's
25505 authenticated, so use with care.
25506 - Directory servers now spool server descriptors, v1 directories,
25507 and v2 networkstatus objects to buffers as needed rather than en
25508 masse. They also mmap the cached-routers files. These steps save
25510 - Stop requiring clients to have well-formed certificates, and stop
25511 checking nicknames in certificates. (Clients have certificates so
25512 that they can look like Tor servers, but in the future we might want
25513 to allow them to look like regular TLS clients instead. Nicknames
25514 in certificates serve no purpose other than making our protocol
25515 easier to recognize on the wire.) Implements proposal 106.
25517 o Improvements on DNS support:
25518 - Add "eventdns" asynchronous dns library originally based on code
25519 from Adam Langley. Now we can discard the old rickety dnsworker
25520 concept, and support a wider variety of DNS functions. Allows
25521 multithreaded builds on NetBSD and OpenBSD again.
25522 - Add server-side support for "reverse" DNS lookups (using PTR
25523 records so clients can determine the canonical hostname for a given
25524 IPv4 address). Only supported by servers using eventdns; servers
25525 now announce in their descriptors if they don't support eventdns.
25526 - Workaround for name servers (like Earthlink's) that hijack failing
25527 DNS requests and replace the no-such-server answer with a "helpful"
25528 redirect to an advertising-driven search portal. Also work around
25529 DNS hijackers who "helpfully" decline to hijack known-invalid
25530 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
25531 lets you turn it off.
25532 - Servers now check for the case when common DNS requests are going to
25533 wildcarded addresses (i.e. all getting the same answer), and change
25534 their exit policy to reject *:* if it's happening.
25535 - When asked to resolve a hostname, don't use non-exit servers unless
25536 requested to do so. This allows servers with broken DNS to be
25537 useful to the network.
25538 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
25539 useless IPv6 DNS resolves.
25540 - Specify and implement client-side SOCKS5 interface for reverse DNS
25541 lookups (see doc/socks-extensions.txt). Also cache them.
25542 - When we change nameservers or IP addresses, reset and re-launch
25543 our tests for DNS hijacking.
25545 o Improvements on reachability testing:
25546 - Servers send out a burst of long-range padding cells once they've
25547 established that they're reachable. Spread them over 4 circuits,
25548 so hopefully a few will be fast. This exercises bandwidth and
25549 bootstraps them into the directory more quickly.
25550 - When we find our DirPort to be reachable, publish a new descriptor
25551 so we'll tell the world (reported by pnx).
25552 - Directory authorities now only decide that routers are reachable
25553 if their identity keys are as expected.
25554 - Do DirPort reachability tests less often, since a single test
25555 chews through many circuits before giving up.
25556 - Avoid some false positives during reachability testing: don't try
25557 to test via a server that's on the same /24 network as us.
25558 - Start publishing one minute or so after we find our ORPort
25559 to be reachable. This will help reduce the number of descriptors
25560 we have for ourselves floating around, since it's quite likely
25561 other things (e.g. DirPort) will change during that minute too.
25562 - Routers no longer try to rebuild long-term connections to directory
25563 authorities, and directory authorities no longer try to rebuild
25564 long-term connections to all servers. We still don't hang up
25565 connections in these two cases though -- we need to look at it
25566 more carefully to avoid flapping, and we likely need to wait til
25567 0.1.1.x is obsolete.
25569 o Improvements on rate limiting:
25570 - Enable write limiting as well as read limiting. Now we sacrifice
25571 capacity if we're pushing out lots of directory traffic, rather
25572 than overrunning the user's intended bandwidth limits.
25573 - Include TLS overhead when counting bandwidth usage; previously, we
25574 would count only the bytes sent over TLS, but not the bytes used
25576 - Servers decline directory requests much more aggressively when
25577 they're low on bandwidth. Otherwise they end up queueing more and
25578 more directory responses, which can't be good for latency.
25579 - But never refuse directory requests from local addresses.
25580 - Be willing to read or write on local connections (e.g. controller
25581 connections) even when the global rate limiting buckets are empty.
25582 - Flush local controller connection buffers periodically as we're
25583 writing to them, so we avoid queueing 4+ megabytes of data before
25585 - Revise and clean up the torrc.sample that we ship with; add
25586 a section for BandwidthRate and BandwidthBurst.
25588 o Major features, NT services:
25589 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
25590 command-line flag so that admins can override the default by saying
25591 "tor --service install --user "SomeUser"". This will not affect
25592 existing installed services. Also, warn the user that the service
25593 will look for its configuration file in the service user's
25594 %appdata% directory. (We can't do the "hardwire the user's appdata
25595 directory" trick any more, since we may not have read access to that
25597 - Support running the Tor service with a torrc not in the same
25598 directory as tor.exe and default to using the torrc located in
25599 the %appdata%\Tor\ of the user who installed the service. Patch
25601 - Add an --ignore-missing-torrc command-line option so that we can
25602 get the "use sensible defaults if the configuration file doesn't
25603 exist" behavior even when specifying a torrc location on the
25605 - When stopping an NT service, wait up to 10 sec for it to actually
25606 stop. (Patch from Matt Edman; resolves bug 295.)
25608 o Directory authority improvements:
25609 - Stop letting hibernating or obsolete servers affect uptime and
25611 - Stop listing hibernating servers in the v1 directory.
25612 - Authorities no longer recommend exits as guards if this would shift
25613 too much load to the exit nodes.
25614 - Authorities now specify server versions in networkstatus. This adds
25615 about 2% to the size of compressed networkstatus docs, and allows
25616 clients to tell which servers support BEGIN_DIR and which don't.
25617 The implementation is forward-compatible with a proposed future
25618 protocol version scheme not tied to Tor versions.
25619 - DirServer configuration lines now have an orport= option so
25620 clients can open encrypted tunnels to the authorities without
25621 having downloaded their descriptors yet. Enabled for moria1,
25622 moria2, tor26, and lefkada now in the default configuration.
25623 - Add a BadDirectory flag to network status docs so that authorities
25624 can (eventually) tell clients about caches they believe to be
25625 broken. Not used yet.
25626 - Allow authorities to list nodes as bad exits in their
25627 approved-routers file by fingerprint or by address. If most
25628 authorities set a BadExit flag for a server, clients don't think
25629 of it as a general-purpose exit. Clients only consider authorities
25630 that advertise themselves as listing bad exits.
25631 - Patch from Steve Hildrey: Generate network status correctly on
25632 non-versioning dirservers.
25633 - Have directory authorities allow larger amounts of drift in uptime
25634 without replacing the server descriptor: previously, a server that
25635 restarted every 30 minutes could have 48 "interesting" descriptors
25637 - Reserve the nickname "Unnamed" for routers that can't pick
25638 a hostname: any router can call itself Unnamed; directory
25639 authorities will never allocate Unnamed to any particular router;
25640 clients won't believe that any router is the canonical Unnamed.
25642 o Directory mirrors and clients:
25643 - Discard any v1 directory info that's over 1 month old (for
25644 directories) or over 1 week old (for running-routers lists).
25645 - Clients track responses with status 503 from dirservers. After a
25646 dirserver has given us a 503, we try not to use it until an hour has
25647 gone by, or until we have no dirservers that haven't given us a 503.
25648 - When we get a 503 from a directory, and we're not a server, we no
25649 longer count the failure against the total number of failures
25650 allowed for the object we're trying to download.
25651 - Prepare for servers to publish descriptors less often: never
25652 discard a descriptor simply for being too old until either it is
25653 recommended by no authorities, or until we get a better one for
25654 the same router. Make caches consider retaining old recommended
25655 routers for even longer.
25656 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
25657 headers for content, so that we can work better in the presence of
25658 caching HTTP proxies.
25659 - Stop fetching descriptors if you're not a dir mirror and you
25660 haven't tried to establish any circuits lately. (This currently
25661 causes some dangerous behavior, because when you start up again
25662 you'll use your ancient server descriptors.)
25664 o Major fixes, crashes:
25665 - Stop crashing when the controller asks us to resetconf more than
25666 one config option at once. (Vidalia 0.0.11 does this.)
25667 - Fix a longstanding obscure crash bug that could occur when we run
25668 out of DNS worker processes, if we're not using eventdns. (Resolves
25670 - Fix an assert that could trigger if a controller quickly set then
25671 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
25672 - Avoid crash when telling controller about stream-status and a
25673 stream is detached.
25674 - Avoid sending junk to controllers or segfaulting when a controller
25675 uses EVENT_NEW_DESC with verbose nicknames.
25676 - Stop triggering asserts if the controller tries to extend hidden
25677 service circuits (reported by mwenge).
25678 - If we start a server with ClientOnly 1, then set ClientOnly to 0
25679 and hup, stop triggering an assert based on an empty onion_key.
25680 - Mask out all signals in sub-threads; only the libevent signal
25681 handler should be processing them. This should prevent some crashes
25682 on some machines using pthreads. (Patch from coderman.)
25683 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
25685 o Major fixes, anonymity/security:
25686 - Automatically avoid picking more than one node from the same
25687 /16 network when constructing a circuit. Add an
25688 "EnforceDistinctSubnets" option to let people disable it if they
25689 want to operate private test networks on a single subnet.
25690 - When generating bandwidth history, round down to the nearest
25691 1k. When storing accounting data, round up to the nearest 1k.
25692 - When we're running as a server, remember when we last rotated onion
25693 keys, so that we will rotate keys once they're a week old even if
25694 we never stay up for a week ourselves.
25695 - If a client asked for a server by name, and there's a named server
25696 in our network-status but we don't have its descriptor yet, we
25697 could return an unnamed server instead.
25698 - Reject (most) attempts to use Tor circuits with length one. (If
25699 many people start using Tor as a one-hop proxy, exit nodes become
25700 a more attractive target for compromise.)
25701 - Just because your DirPort is open doesn't mean people should be
25702 able to remotely teach you about hidden service descriptors. Now
25703 only accept rendezvous posts if you've got HSAuthoritativeDir set.
25704 - Fix a potential race condition in the rpm installer. Found by
25706 - Do not log IPs with TLS failures for incoming TLS
25707 connections. (Fixes bug 382.)
25709 o Major fixes, other:
25710 - If our system clock jumps back in time, don't publish a negative
25711 uptime in the descriptor.
25712 - When we start during an accounting interval before it's time to wake
25713 up, remember to wake up at the correct time. (May fix bug 342.)
25714 - Previously, we would cache up to 16 old networkstatus documents
25715 indefinitely, if they came from nontrusted authorities. Now we
25716 discard them if they are more than 10 days old.
25717 - When we have a state file we cannot parse, tell the user and
25718 move it aside. Now we avoid situations where the user starts
25719 Tor in 1904, Tor writes a state file with that timestamp in it,
25720 the user fixes her clock, and Tor refuses to start.
25721 - Publish a new descriptor after we hup/reload. This is important
25722 if our config has changed such that we'll want to start advertising
25723 our DirPort now, etc.
25724 - If we are using an exit enclave and we can't connect, e.g. because
25725 its webserver is misconfigured to not listen on localhost, then
25726 back off and try connecting from somewhere else before we fail.
25728 o New config options or behaviors:
25729 - When EntryNodes are configured, rebuild the guard list to contain,
25730 in order: the EntryNodes that were guards before; the rest of the
25731 EntryNodes; the nodes that were guards before.
25732 - Do not warn when individual nodes in the configuration's EntryNodes,
25733 ExitNodes, etc are down: warn only when all possible nodes
25734 are down. (Fixes bug 348.)
25735 - Put a lower-bound on MaxAdvertisedBandwidth.
25736 - Start using the state file to store bandwidth accounting data:
25737 the bw_accounting file is now obsolete. We'll keep generating it
25738 for a while for people who are still using 0.1.2.4-alpha.
25739 - Try to batch changes to the state file so that we do as few
25740 disk writes as possible while still storing important things in
25742 - The state file and the bw_accounting file get saved less often when
25743 the AvoidDiskWrites config option is set.
25744 - Make PIDFile work on Windows.
25745 - Add internal descriptions for a bunch of configuration options:
25746 accessible via controller interface and in comments in saved
25748 - Reject *:563 (NNTPS) in the default exit policy. We already reject
25749 NNTP by default, so this seems like a sensible addition.
25750 - Clients now reject hostnames with invalid characters. This should
25751 avoid some inadvertent info leaks. Add an option
25752 AllowNonRFC953Hostnames to disable this behavior, in case somebody
25753 is running a private network with hosts called @, !, and #.
25754 - Check for addresses with invalid characters at the exit as well,
25755 and warn less verbosely when they fail. You can override this by
25756 setting ServerDNSAllowNonRFC953Addresses to 1.
25757 - Remove some options that have been deprecated since at least
25758 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
25759 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
25760 to set log options. Mark PathlenCoinWeight as obsolete.
25761 - Stop accepting certain malformed ports in configured exit policies.
25762 - When the user uses bad syntax in the Log config line, stop
25763 suggesting other bad syntax as a replacement.
25764 - Add new config option "ResolvConf" to let the server operator
25765 choose an alternate resolve.conf file when using eventdns.
25766 - If one of our entry guards is on the ExcludeNodes list, or the
25767 directory authorities don't think it's a good guard, treat it as
25768 if it were unlisted: stop using it as a guard, and throw it off
25769 the guards list if it stays that way for a long time.
25770 - Allow directory authorities to be marked separately as authorities
25771 for the v1 directory protocol, the v2 directory protocol, and
25772 as hidden service directories, to make it easier to retire old
25773 authorities. V1 authorities should set "HSAuthoritativeDir 1"
25774 to continue being hidden service authorities too.
25775 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
25776 - Make TrackExitHosts case-insensitive, and fix the behavior of
25777 ".suffix" TrackExitHosts items to avoid matching in the middle of
25779 - New DirPort behavior: if you have your dirport set, you download
25780 descriptors aggressively like a directory mirror, whether or not
25781 your ORPort is set.
25784 - Create a new file ReleaseNotes which was the old ChangeLog. The
25785 new ChangeLog file now includes the notes for all development
25787 - Add a new address-spec.txt document to describe our special-case
25788 addresses: .exit, .onion, and .noconnnect.
25789 - Fork the v1 directory protocol into its own spec document,
25790 and mark dir-spec.txt as the currently correct (v2) spec.
25792 o Packaging, porting, and contrib
25793 - "tor --verify-config" now exits with -1(255) or 0 depending on
25794 whether the config options are bad or good.
25795 - The Debian package now uses --verify-config when (re)starting,
25796 to distinguish configuration errors from other errors.
25797 - Adapt a patch from goodell to let the contrib/exitlist script
25798 take arguments rather than require direct editing.
25799 - Prevent the contrib/exitlist script from printing the same
25800 result more than once.
25801 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
25802 - In the hidden service example in torrc.sample, stop recommending
25803 esoteric and discouraged hidden service options.
25804 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
25805 values before failing, and always enables eventdns.
25806 - Try to detect Windows correctly when cross-compiling.
25807 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
25808 Try to fix this in configure.in by checking for most functions
25809 before we check for libevent.
25810 - Update RPMs to require libevent 1.2.
25811 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
25812 or later. Log when we are doing this, so we can diagnose it when
25813 it fails. (Also, recommend libevent 1.1b for kqueue and
25814 win32 methods; deprecate libevent 1.0b harder; make libevent
25815 recommendation system saner.)
25816 - Build with recent (1.3+) libevents on platforms that do not
25817 define the nonstandard types "u_int8_t" and friends.
25818 - Remove architecture from OS X builds. The official builds are
25819 now universal binaries.
25820 - Run correctly on OS X platforms with case-sensitive filesystems.
25821 - Correctly set maximum connection limit on Cygwin. (This time
25823 - Start compiling on MinGW on Windows (patches from Mike Chiussi
25825 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
25826 - Finally fix the openssl warnings from newer gccs that believe that
25827 ignoring a return value is okay, but casting a return value and
25828 then ignoring it is a sign of madness.
25829 - On architectures where sizeof(int)>4, still clamp declarable
25830 bandwidth to INT32_MAX.
25832 o Minor features, controller:
25833 - Warn the user when an application uses the obsolete binary v0
25834 control protocol. We're planning to remove support for it during
25835 the next development series, so it's good to give people some
25837 - Add STREAM_BW events to report per-entry-stream bandwidth
25838 use. (Patch from Robert Hogan.)
25839 - Rate-limit SIGNEWNYM signals in response to controllers that
25840 impolitely generate them for every single stream. (Patch from
25841 mwenge; closes bug 394.)
25842 - Add a REMAP status to stream events to note that a stream's
25843 address has changed because of a cached address or a MapAddress
25845 - Make REMAP stream events have a SOURCE (cache or exit), and
25846 make them generated in every case where we get a successful
25847 connected or resolved cell.
25848 - Track reasons for OR connection failure; make these reasons
25849 available via the controller interface. (Patch from Mike Perry.)
25850 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
25851 can learn when clients are sending malformed hostnames to Tor.
25852 - Specify and implement some of the controller status events.
25853 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
25854 - Reimplement GETINFO so that info/names stays in sync with the
25856 - Implement "GETINFO fingerprint".
25857 - Implement "SETEVENTS GUARD" so controllers can get updates on
25858 entry guard status as it changes.
25859 - Make all connections to addresses of the form ".noconnect"
25860 immediately get closed. This lets application/controller combos
25861 successfully test whether they're talking to the same Tor by
25862 watching for STREAM events.
25863 - Add a REASON field to CIRC events; for backward compatibility, this
25864 field is sent only to controllers that have enabled the extended
25865 event format. Also, add additional reason codes to explain why
25866 a given circuit has been destroyed or truncated. (Patches from
25868 - Add a REMOTE_REASON field to extended CIRC events to tell the
25869 controller why a remote OR told us to close a circuit.
25870 - Stream events also now have REASON and REMOTE_REASON fields,
25871 working much like those for circuit events.
25872 - There's now a GETINFO ns/... field so that controllers can ask Tor
25873 about the current status of a router.
25874 - A new event type "NS" to inform a controller when our opinion of
25875 a router's status has changed.
25876 - Add a GETINFO events/names and GETINFO features/names so controllers
25877 can tell which events and features are supported.
25878 - A new CLEARDNSCACHE signal to allow controllers to clear the
25879 client-side DNS cache without expiring circuits.
25880 - Fix CIRC controller events so that controllers can learn the
25881 identity digests of non-Named servers used in circuit paths.
25882 - Let controllers ask for more useful identifiers for servers. Instead
25883 of learning identity digests for un-Named servers and nicknames
25884 for Named servers, the new identifiers include digest, nickname,
25885 and indication of Named status. Off by default; see control-spec.txt
25886 for more information.
25887 - Add a "getinfo address" controller command so it can display Tor's
25888 best guess to the user.
25889 - New controller event to alert the controller when our server
25890 descriptor has changed.
25891 - Give more meaningful errors on controller authentication failure.
25892 - Export the default exit policy via the control port, so controllers
25893 don't need to guess what it is / will be later.
25895 o Minor bugfixes, controller:
25896 - When creating a circuit via the controller, send a 'launched'
25897 event when we're done, so we follow the spec better.
25898 - Correct the control spec to match how the code actually responds
25899 to 'getinfo addr-mappings/*'. Reported by daejees.
25900 - The control spec described a GUARDS event, but the code
25901 implemented a GUARD event. Standardize on GUARD, but let people
25902 ask for GUARDS too. Reported by daejees.
25903 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
25904 clear the corresponding on_circuit variable, and remember later
25905 that we don't need to send a redundant CLOSED event. (Resolves part
25907 - Report events where a resolve succeeded or where we got a socks
25908 protocol error correctly, rather than calling both of them
25910 - Change reported stream target addresses to IP consistently when
25911 we finally get the IP from an exit node.
25912 - Send log messages to the controller even if they happen to be very
25914 - Flush ERR-level controller status events just like we currently
25915 flush ERR-level log events, so that a Tor shutdown doesn't prevent
25916 the controller from learning about current events.
25917 - Report the circuit number correctly in STREAM CLOSED events. Bug
25918 reported by Mike Perry.
25919 - Do not report bizarre values for results of accounting GETINFOs
25920 when the last second's write or read exceeds the allotted bandwidth.
25921 - Report "unrecognized key" rather than an empty string when the
25922 controller tries to fetch a networkstatus that doesn't exist.
25923 - When the controller does a "GETINFO network-status", tell it
25924 about even those routers whose descriptors are very old, and use
25925 long nicknames where appropriate.
25926 - Fix handling of verbose nicknames with ORCONN controller events:
25927 make them show up exactly when requested, rather than exactly when
25929 - Controller signals now work on non-Unix platforms that don't define
25930 SIGUSR1 and SIGUSR2 the way we expect.
25931 - Respond to SIGNAL command before we execute the signal, in case
25932 the signal shuts us down. Suggested by Karsten Loesing.
25933 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
25935 o Minor features, code performance:
25936 - Major performance improvement on inserting descriptors: change
25937 algorithm from O(n^2) to O(n).
25938 - Do not rotate onion key immediately after setting it for the first
25940 - Call router_have_min_dir_info half as often. (This is showing up in
25941 some profiles, but not others.)
25942 - When using GCC, make log_debug never get called at all, and its
25943 arguments never get evaluated, when no debug logs are configured.
25944 (This is showing up in some profiles, but not others.)
25945 - Statistics dumped by -USR2 now include a breakdown of public key
25946 operations, for profiling.
25947 - Make the common memory allocation path faster on machines where
25948 malloc(0) returns a pointer.
25949 - Split circuit_t into origin_circuit_t and or_circuit_t, and
25950 split connection_t into edge, or, dir, control, and base structs.
25951 These will save quite a bit of memory on busy servers, and they'll
25952 also help us track down bugs in the code and bugs in the spec.
25953 - Use OpenSSL's AES implementation on platforms where it's faster.
25954 This could save us as much as 10% CPU usage.
25956 o Minor features, descriptors and descriptor handling:
25957 - Avoid duplicate entries on MyFamily line in server descriptor.
25958 - When Tor receives a router descriptor that it asked for, but
25959 no longer wants (because it has received fresh networkstatuses
25960 in the meantime), do not warn the user. Cache the descriptor if
25961 we're a cache; drop it if we aren't.
25962 - Servers no longer ever list themselves in their "family" line,
25963 even if configured to do so. This makes it easier to configure
25964 family lists conveniently.
25966 o Minor fixes, confusing/misleading log messages:
25967 - Display correct results when reporting which versions are
25968 recommended, and how recommended they are. (Resolves bug 383.)
25969 - Inform the server operator when we decide not to advertise a
25970 DirPort due to AccountingMax enabled or a low BandwidthRate.
25971 - Only include function names in log messages for info/debug messages.
25972 For notice/warn/err, the content of the message should be clear on
25973 its own, and printing the function name only confuses users.
25974 - Remove even more protocol-related warnings from Tor server logs,
25975 such as bad TLS handshakes and malformed begin cells.
25976 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
25977 when the IP address is mapped through MapAddress to a hostname.
25978 - Fix misleading log messages: an entry guard that is "unlisted",
25979 as well as not known to be "down" (because we've never heard
25980 of it), is not therefore "up".
25982 o Minor fixes, old/obsolete behavior:
25983 - Start assuming we can use a create_fast cell if we don't know
25984 what version a router is running.
25985 - We no longer look for identity and onion keys in "identity.key" and
25986 "onion.key" -- these were replaced by secret_id_key and
25987 secret_onion_key in 0.0.8pre1.
25988 - We no longer require unrecognized directory entries to be
25990 - Drop compatibility with obsolete Tors that permit create cells
25991 to have the wrong circ_id_type.
25992 - Remove code to special-case "-cvs" ending, since it has not
25993 actually mattered since 0.0.9.
25994 - Don't re-write the fingerprint file every restart, unless it has
25997 o Minor fixes, misc client-side behavior:
25998 - Always remove expired routers and networkstatus docs before checking
25999 whether we have enough information to build circuits. (Fixes
26001 - When computing clock skew from directory HTTP headers, consider what
26002 time it was when we finished asking for the directory, not what
26004 - Make our socks5 handling more robust to broken socks clients:
26005 throw out everything waiting on the buffer in between socks
26006 handshake phases, since they can't possibly (so the theory
26007 goes) have predicted what we plan to respond to them.
26008 - Expire socks connections if they spend too long waiting for the
26009 handshake to finish. Previously we would let them sit around for
26010 days, if the connecting application didn't close them either.
26011 - And if the socks handshake hasn't started, don't send a
26012 "DNS resolve socks failed" handshake reply; just close it.
26013 - If the user asks to use invalid exit nodes, be willing to use
26015 - Track unreachable entry guards correctly: don't conflate
26016 'unreachable by us right now' with 'listed as down by the directory
26017 authorities'. With the old code, if a guard was unreachable by us
26018 but listed as running, it would clog our guard list forever.
26019 - Behave correctly in case we ever have a network with more than
26020 2GB/s total advertised capacity.
26021 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
26022 - Fix a memory leak when we ask for "all" networkstatuses and we
26023 get one we don't recognize.
26026 Changes in version 0.1.1.26 - 2006-12-14
26027 o Security bugfixes:
26028 - Stop sending the HttpProxyAuthenticator string to directory
26029 servers when directory connections are tunnelled through Tor.
26030 - Clients no longer store bandwidth history in the state file.
26031 - Do not log introduction points for hidden services if SafeLogging
26035 - Fix an assert failure when a directory authority sets
26036 AuthDirRejectUnlisted and then receives a descriptor from an
26037 unlisted router (reported by seeess).
26040 Changes in version 0.1.1.25 - 2006-11-04
26042 - When a client asks us to resolve (rather than connect to)
26043 an address, and we have a cached answer, give them the cached
26044 answer. Previously, we would give them no answer at all.
26045 - We were building exactly the wrong circuits when we predict
26046 hidden service requirements, meaning Tor would have to build all
26047 its circuits on demand.
26048 - If none of our live entry guards have a high uptime, but we
26049 require a guard with a high uptime, try adding a new guard before
26050 we give up on the requirement. This patch should make long-lived
26051 connections more stable on average.
26052 - When testing reachability of our DirPort, don't launch new
26053 tests when there's already one in progress -- unreachable
26054 servers were stacking up dozens of testing streams.
26056 o Security bugfixes:
26057 - When the user sends a NEWNYM signal, clear the client-side DNS
26058 cache too. Otherwise we continue to act on previous information.
26061 - Avoid a memory corruption bug when creating a hash table for
26063 - Avoid possibility of controller-triggered crash when misusing
26064 certain commands from a v0 controller on platforms that do not
26065 handle printf("%s",NULL) gracefully.
26066 - Avoid infinite loop on unexpected controller input.
26067 - Don't log spurious warnings when we see a circuit close reason we
26068 don't recognize; it's probably just from a newer version of Tor.
26069 - Add Vidalia to the OS X uninstaller script, so when we uninstall
26070 Tor/Privoxy we also uninstall Vidalia.
26073 Changes in version 0.1.1.24 - 2006-09-29
26075 - Allow really slow clients to not hang up five minutes into their
26076 directory downloads (suggested by Adam J. Richter).
26077 - Fix major performance regression from 0.1.0.x: instead of checking
26078 whether we have enough directory information every time we want to
26079 do something, only check when the directory information has changed.
26080 This should improve client CPU usage by 25-50%.
26081 - Don't crash if, after a server has been running for a while,
26082 it can't resolve its hostname.
26083 - When a client asks us to resolve (not connect to) an address,
26084 and we have a cached answer, give them the cached answer.
26085 Previously, we would give them no answer at all.
26088 - Allow Tor to start when RunAsDaemon is set but no logs are set.
26089 - Don't crash when the controller receives a third argument to an
26090 "extendcircuit" request.
26091 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
26092 response; fix error code when "getinfo dir/status/" fails.
26093 - Fix configure.in to not produce broken configure files with
26094 more recent versions of autoconf. Thanks to Clint for his auto*
26096 - Fix security bug on NetBSD that could allow someone to force
26097 uninitialized RAM to be sent to a server's DNS resolver. This
26098 only affects NetBSD and other platforms that do not bounds-check
26100 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
26101 methods: these are known to be buggy.
26102 - If we're a directory mirror and we ask for "all" network status
26103 documents, we would discard status documents from authorities
26104 we don't recognize.
26107 Changes in version 0.1.1.23 - 2006-07-30
26109 - Fast Tor servers, especially exit nodes, were triggering asserts
26110 due to a bug in handling the list of pending DNS resolves. Some
26111 bugs still remain here; we're hunting them.
26112 - Entry guards could crash clients by sending unexpected input.
26113 - More fixes on reachability testing: if you find yourself reachable,
26114 then don't ever make any client requests (so you stop predicting
26115 circuits), then hup or have your clock jump, then later your IP
26116 changes, you won't think circuits are working, so you won't try to
26117 test reachability, so you won't publish.
26120 - Avoid a crash if the controller does a resetconf firewallports
26121 and then a setconf fascistfirewall=1.
26122 - Avoid an integer underflow when the dir authority decides whether
26123 a router is stable: we might wrongly label it stable, and compute
26124 a slightly wrong median stability, when a descriptor is published
26126 - Fix a place where we might trigger an assert if we can't build our
26127 own server descriptor yet.
26130 Changes in version 0.1.1.22 - 2006-07-05
26132 - Fix a big bug that was causing servers to not find themselves
26133 reachable if they changed IP addresses. Since only 0.1.1.22+
26134 servers can do reachability testing correctly, now we automatically
26135 make sure to test via one of these.
26136 - Fix to allow clients and mirrors to learn directory info from
26137 descriptor downloads that get cut off partway through.
26138 - Directory authorities had a bug in deciding if a newly published
26139 descriptor was novel enough to make everybody want a copy -- a few
26140 servers seem to be publishing new descriptors many times a minute.
26142 - Fix a rare bug that was causing some servers to complain about
26143 "closing wedged cpuworkers" and skip some circuit create requests.
26144 - Make the Exit flag in directory status documents actually work.
26147 Changes in version 0.1.1.21 - 2006-06-10
26148 o Crash and assert fixes from 0.1.1.20:
26149 - Fix a rare crash on Tor servers that have enabled hibernation.
26150 - Fix a seg fault on startup for Tor networks that use only one
26151 directory authority.
26152 - Fix an assert from a race condition that occurs on Tor servers
26153 while exiting, where various threads are trying to log that they're
26154 exiting, and delete the logs, at the same time.
26155 - Make our unit tests pass again on certain obscure platforms.
26158 - Add support for building SUSE RPM packages.
26159 - Speed up initial bootstrapping for clients: if we are making our
26160 first ever connection to any entry guard, then don't mark it down
26162 - When only one Tor server in the network is labelled as a guard,
26163 and we've already picked him, we would cycle endlessly picking him
26164 again, being unhappy about it, etc. Now we specifically exclude
26165 current guards when picking a new guard.
26166 - Servers send create cells more reliably after the TLS connection
26167 is established: we were sometimes forgetting to send half of them
26168 when we had more than one pending.
26169 - If we get a create cell that asks us to extend somewhere, but the
26170 Tor server there doesn't match the expected digest, we now send
26171 a destroy cell back, rather than silently doing nothing.
26172 - Make options->RedirectExit work again.
26173 - Make cookie authentication for the controller work again.
26174 - Stop being picky about unusual characters in the arguments to
26175 mapaddress. It's none of our business.
26176 - Add a new config option "TestVia" that lets you specify preferred
26177 middle hops to use for test circuits. Perhaps this will let me
26178 debug the reachability problems better.
26180 o Log / documentation fixes:
26181 - If we're a server and some peer has a broken TLS certificate, don't
26182 log about it unless ProtocolWarnings is set, i.e., we want to hear
26183 about protocol violations by others.
26184 - Fix spelling of VirtualAddrNetwork in man page.
26185 - Add a better explanation at the top of the autogenerated torrc file
26186 about what happened to our old torrc.
26189 Changes in version 0.1.1.20 - 2006-05-23
26190 o Crash and assert fixes from 0.1.0.17:
26191 - Fix assert bug in close_logs() on exit: when we close and delete
26192 logs, remove them all from the global "logfiles" list.
26193 - Fix an assert error when we're out of space in the connection_list
26194 and we try to post a hidden service descriptor (reported by Peter
26196 - Fix a rare assert error when we've tried all intro points for
26197 a hidden service and we try fetching the service descriptor again:
26198 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
26199 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
26200 out and refuse the setconf if it would fail.
26201 - If you specify a relative torrc path and you set RunAsDaemon in
26202 your torrc, then it chdir()'s to the new directory. If you then
26203 HUP, it tries to load the new torrc location, fails, and exits.
26204 The fix: no longer allow a relative path to torrc when using -f.
26205 - Check for integer overflows in more places, when adding elements
26206 to smartlists. This could possibly prevent a buffer overflow
26207 on malicious huge inputs.
26209 o Security fixes, major:
26210 - When we're printing strings from the network, don't try to print
26211 non-printable characters. Now we're safer against shell escape
26212 sequence exploits, and also against attacks to fool users into
26213 misreading their logs.
26214 - Implement entry guards: automatically choose a handful of entry
26215 nodes and stick with them for all circuits. Only pick new guards
26216 when the ones you have are unsuitable, and if the old guards
26217 become suitable again, switch back. This will increase security
26218 dramatically against certain end-point attacks. The EntryNodes
26219 config option now provides some hints about which entry guards you
26220 want to use most; and StrictEntryNodes means to only use those.
26221 Fixes CVE-2006-0414.
26222 - Implement exit enclaves: if we know an IP address for the
26223 destination, and there's a running Tor server at that address
26224 which allows exit to the destination, then extend the circuit to
26225 that exit first. This provides end-to-end encryption and end-to-end
26226 authentication. Also, if the user wants a .exit address or enclave,
26227 use 4 hops rather than 3, and cannibalize a general circ for it
26229 - Obey our firewall options more faithfully:
26230 . If we can't get to a dirserver directly, try going via Tor.
26231 . Don't ever try to connect (as a client) to a place our
26232 firewall options forbid.
26233 . If we specify a proxy and also firewall options, obey the
26234 firewall options even when we're using the proxy: some proxies
26235 can only proxy to certain destinations.
26236 - Make clients regenerate their keys when their IP address changes.
26237 - For the OS X package's modified privoxy config file, comment
26238 out the "logfile" line so we don't log everything passed
26240 - Our TLS handshakes were generating a single public/private
26241 keypair for the TLS context, rather than making a new one for
26242 each new connection. Oops. (But we were still rotating them
26243 periodically, so it's not so bad.)
26244 - When we were cannibalizing a circuit with a particular exit
26245 node in mind, we weren't checking to see if that exit node was
26246 already present earlier in the circuit. Now we are.
26247 - Require server descriptors to list IPv4 addresses -- hostnames
26248 are no longer allowed. This also fixes potential vulnerabilities
26249 to servers providing hostnames as their address and then
26250 preferentially resolving them so they can partition users.
26251 - Our logic to decide if the OR we connected to was the right guy
26252 was brittle and maybe open to a mitm for invalid routers.
26254 o Security fixes, minor:
26255 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
26256 Ian Goldberg can prove things about our handshake protocol more
26258 - Make directory authorities generate a separate "guard" flag to
26259 mean "would make a good entry guard". Clients now honor the
26260 is_guard flag rather than looking at is_fast or is_stable.
26261 - Try to list MyFamily elements by key, not by nickname, and warn
26262 if we've not heard of a server.
26263 - Start using RAND_bytes rather than RAND_pseudo_bytes from
26264 OpenSSL. Also, reseed our entropy every hour, not just at
26265 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
26266 - Refuse server descriptors where the fingerprint line doesn't match
26267 the included identity key. Tor doesn't care, but other apps (and
26268 humans) might actually be trusting the fingerprint line.
26269 - We used to kill the circuit when we receive a relay command we
26270 don't recognize. Now we just drop that cell.
26271 - Fix a bug found by Lasse Overlier: when we were making internal
26272 circuits (intended to be cannibalized later for rendezvous and
26273 introduction circuits), we were picking them so that they had
26274 useful exit nodes. There was no need for this, and it actually
26275 aids some statistical attacks.
26276 - Start treating internal circuits and exit circuits separately.
26277 It's important to keep them separate because internal circuits
26278 have their last hops picked like middle hops, rather than like
26279 exit hops. So exiting on them will break the user's expectations.
26280 - Fix a possible way to DoS dirservers.
26281 - When the client asked for a rendezvous port that the hidden
26282 service didn't want to provide, we were sending an IP address
26283 back along with the end cell. Fortunately, it was zero. But stop
26286 o Packaging improvements:
26287 - Implement --with-libevent-dir option to ./configure. Improve
26288 search techniques to find libevent, and use those for openssl too.
26289 - Fix a couple of bugs in OpenSSL detection. Deal better when
26290 there are multiple SSLs installed with different versions.
26291 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
26292 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
26294 - Make unit tests (and other invocations that aren't the real Tor)
26295 run without launching listeners, creating subdirectories, and so on.
26296 - The OS X installer was adding a symlink for tor_resolve but
26297 the binary was called tor-resolve (reported by Thomas Hardly).
26298 - Now we can target arch and OS in rpm builds (contributed by
26299 Phobos). Also make the resulting dist-rpm filename match the
26301 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
26302 if you log to syslog and want something other than LOG_DAEMON.
26303 - Fix the torify (tsocks) config file to not use Tor for localhost
26305 - Start shipping socks-extensions.txt, tor-doc-unix.html,
26306 tor-doc-server.html, and stylesheet.css in the tarball.
26307 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
26308 They are useless now.
26309 - Add Peter Palfrader's contributed check-tor script. It lets you
26310 easily check whether a given server (referenced by nickname)
26311 is reachable by you.
26312 - Add BSD-style contributed startup script "rc.subr" from Peter
26315 o Directory improvements -- new directory protocol:
26316 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
26317 - Authorities and caches publish individual descriptors (by
26318 digest, by fingerprint, by "all", and by "tell me yours").
26319 - Clients don't download or use the old directory anymore. Now they
26320 download network-statuses from the directory authorities, and
26321 fetch individual server descriptors as needed from mirrors.
26322 - Clients don't download descriptors of non-running servers.
26323 - Download descriptors by digest, not by fingerprint. Caches try to
26324 download all listed digests from authorities; clients try to
26325 download "best" digests from caches. This avoids partitioning
26326 and isolating attacks better.
26327 - Only upload a new server descriptor when options change, 18
26328 hours have passed, uptime is reset, or bandwidth changes a lot.
26329 - Directory authorities silently throw away new descriptors that
26330 haven't changed much if the timestamps are similar. We do this to
26331 tolerate older Tor servers that upload a new descriptor every 15
26332 minutes. (It seemed like a good idea at the time.)
26333 - Clients choose directory servers from the network status lists,
26334 not from their internal list of router descriptors. Now they can
26335 go to caches directly rather than needing to go to authorities
26336 to bootstrap the first set of descriptors.
26337 - When picking a random directory, prefer non-authorities if any
26339 - Add a new flag to network-status indicating whether the server
26340 can answer v2 directory requests too.
26341 - Directory mirrors now cache up to 16 unrecognized network-status
26342 docs, so new directory authorities will be cached too.
26343 - Stop parsing, storing, or using running-routers output (but
26344 mirrors still cache and serve it).
26345 - Clients consider a threshold of "versioning" directory authorities
26346 before deciding whether to warn the user that he's obsolete.
26347 - Authorities publish separate sorted lists of recommended versions
26348 for clients and for servers.
26349 - Change DirServers config line to note which dirs are v1 authorities.
26350 - Put nicknames on the DirServer line, so we can refer to them
26351 without requiring all our users to memorize their IP addresses.
26352 - Remove option when getting directory cache to see whether they
26353 support running-routers; they all do now. Replace it with one
26354 to see whether caches support v2 stuff.
26355 - Stop listing down or invalid nodes in the v1 directory. This
26356 reduces its bulk by about 1/3, and reduces load on mirrors.
26357 - Mirrors no longer cache the v1 directory as often.
26358 - If we as a directory mirror don't know of any v1 directory
26359 authorities, then don't try to cache any v1 directories.
26361 o Other directory improvements:
26362 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
26363 fifth authoritative directory servers.
26364 - Directory authorities no longer require an open connection from
26365 a server to consider him "reachable". We need this change because
26366 when we add new directory authorities, old servers won't know not
26367 to hang up on them.
26368 - Dir authorities now do their own external reachability testing
26369 of each server, and only list as running the ones they found to
26370 be reachable. We also send back warnings to the server's logs if
26371 it uploads a descriptor that we already believe is unreachable.
26372 - Spread the directory authorities' reachability testing over the
26373 entire testing interval, so we don't try to do 500 TLS's at once
26375 - Make the "stable" router flag in network-status be the median of
26376 the uptimes of running valid servers, and make clients pay
26377 attention to the network-status flags. Thus the cutoff adapts
26378 to the stability of the network as a whole, making IRC, IM, etc
26379 connections more reliable.
26380 - Make the v2 dir's "Fast" flag based on relative capacity, just
26381 like "Stable" is based on median uptime. Name everything in the
26382 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
26383 - Retry directory requests if we fail to get an answer we like
26384 from a given dirserver (we were retrying before, but only if
26385 we fail to connect).
26386 - Return a robots.txt on our dirport to discourage google indexing.
26388 o Controller protocol improvements:
26389 - Revised controller protocol (version 1) that uses ascii rather
26390 than binary: tor/doc/control-spec.txt. Add supporting libraries
26391 in python and java and c# so you can use the controller from your
26392 applications without caring how our protocol works.
26393 - Allow the DEBUG controller event to work again. Mark certain log
26394 entries as "don't tell this to controllers", so we avoid cycles.
26395 - New controller function "getinfo accounting", to ask how
26396 many bytes we've used in this time period.
26397 - Add a "resetconf" command so you can set config options like
26398 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
26399 a config option in the torrc with no value, then it clears it
26400 entirely (rather than setting it to its default).
26401 - Add a "getinfo config-file" to tell us where torrc is. Also
26402 expose guard nodes, config options/names.
26403 - Add a "quit" command (when when using the controller manually).
26404 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
26405 stop using any currently-dirty circuits for new streams, so we
26406 don't link new actions to old actions. This also occurs on HUP
26407 or "signal reload".
26408 - If we would close a stream early (e.g. it asks for a .exit that
26409 we know would refuse it) but the LeaveStreamsUnattached config
26410 option is set by the controller, then don't close it.
26411 - Add a new controller event type "authdir_newdescs" that allows
26412 controllers to get all server descriptors that were uploaded to
26413 a router in its role as directory authority.
26414 - New controller option "getinfo desc/all-recent" to fetch the
26415 latest server descriptor for every router that Tor knows about.
26416 - Fix the controller's "attachstream 0" command to treat conn like
26417 it just connected, doing address remapping, handling .exit and
26418 .onion idioms, and so on. Now we're more uniform in making sure
26419 that the controller hears about new and closing connections.
26420 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
26421 the controller. Also, rotate dns and cpu workers if the controller
26422 changes options that will affect them; and initialize the dns
26423 worker cache tree whether or not we start out as a server.
26424 - Add a new circuit purpose 'controller' to let the controller ask
26425 for a circuit that Tor won't try to use. Extend the "extendcircuit"
26426 controller command to let you specify the purpose if you're starting
26427 a new circuit. Add a new "setcircuitpurpose" controller command to
26428 let you change a circuit's purpose after it's been created.
26429 - Let the controller ask for "getinfo dir/server/foo" so it can ask
26430 directly rather than connecting to the dir port. "getinfo
26431 dir/status/foo" also works, but currently only if your DirPort
26433 - Let the controller tell us about certain router descriptors
26434 that it doesn't want Tor to use in circuits. Implement
26435 "setrouterpurpose" and modify "+postdescriptor" to do this.
26436 - If the controller's *setconf commands fail, collect an error
26437 message in a string and hand it back to the controller -- don't
26438 just tell them to go read their logs.
26440 o Scalability, resource management, and performance:
26441 - Fix a major load balance bug: we were round-robin reading in 16 KB
26442 chunks, and servers with bandwidthrate of 20 KB, while downloading
26443 a 600 KB directory, would starve their other connections. Now we
26444 try to be a bit more fair.
26445 - Be more conservative about whether to advertise our DirPort.
26446 The main change is to not advertise if we're running at capacity
26447 and either a) we could hibernate ever or b) our capacity is low
26448 and we're using a default DirPort.
26449 - We weren't cannibalizing circuits correctly for
26450 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
26451 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
26452 build those from scratch. This should make hidden services faster.
26453 - Predict required circuits better, with an eye toward making hidden
26454 services faster on the service end.
26455 - Compress exit policies even more: look for duplicate lines and
26457 - Generate 18.0.0.0/8 address policy format in descs when we can;
26458 warn when the mask is not reducible to a bit-prefix.
26459 - There used to be two ways to specify your listening ports in a
26460 server descriptor: on the "router" line and with a separate "ports"
26461 line. Remove support for the "ports" line.
26462 - Reduce memory requirements in our structs by changing the order
26463 of fields. Replace balanced trees with hash tables. Inline
26464 bottleneck smartlist functions. Add a "Map from digest to void*"
26465 abstraction so we can do less hex encoding/decoding, and use it
26466 in router_get_by_digest(). Many other CPU and memory improvements.
26467 - Allow tor_gzip_uncompress to extract as much as possible from
26468 truncated compressed data. Try to extract as many
26469 descriptors as possible from truncated http responses (when
26470 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
26471 - Make circ->onionskin a pointer, not a static array. moria2 was using
26472 125000 circuit_t's after it had been up for a few weeks, which
26473 translates to 20+ megs of wasted space.
26474 - The private half of our EDH handshake keys are now chosen out
26475 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
26476 - Stop doing the complex voodoo overkill checking for insecure
26477 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
26478 - Do round-robin writes for TLS of at most 16 kB per write. This
26479 might be more fair on loaded Tor servers.
26480 - Do not use unaligned memory access on alpha, mips, or mipsel.
26481 It *works*, but is very slow, so we treat them as if it doesn't.
26483 o Other bugfixes and improvements:
26484 - Start storing useful information to $DATADIR/state, so we can
26485 remember things across invocations of Tor. Retain unrecognized
26486 lines so we can be forward-compatible, and write a TorVersion line
26487 so we can be backward-compatible.
26488 - If ORPort is set, Address is not explicitly set, and our hostname
26489 resolves to a private IP address, try to use an interface address
26490 if it has a public address. Now Windows machines that think of
26491 themselves as localhost can guess their address.
26492 - Regenerate our local descriptor if it's dirty and we try to use
26493 it locally (e.g. if it changes during reachability detection).
26494 This was causing some Tor servers to keep publishing the same
26495 initial descriptor forever.
26496 - Tor servers with dynamic IP addresses were needing to wait 18
26497 hours before they could start doing reachability testing using
26498 the new IP address and ports. This is because they were using
26499 the internal descriptor to learn what to test, yet they were only
26500 rebuilding the descriptor once they decided they were reachable.
26501 - It turns out we couldn't bootstrap a network since we added
26502 reachability detection in 0.1.0.1-rc. Good thing the Tor network
26503 has never gone down. Add an AssumeReachable config option to let
26504 servers and authorities bootstrap. When we're trying to build a
26505 high-uptime or high-bandwidth circuit but there aren't enough
26506 suitable servers, try being less picky rather than simply failing.
26507 - Newly bootstrapped Tor networks couldn't establish hidden service
26508 circuits until they had nodes with high uptime. Be more tolerant.
26509 - Really busy servers were keeping enough circuits open on stable
26510 connections that they were wrapping around the circuit_id
26511 space. (It's only two bytes.) This exposed a bug where we would
26512 feel free to reuse a circuit_id even if it still exists but has
26513 been marked for close. Try to fix this bug. Some bug remains.
26514 - When we fail to bind or listen on an incoming or outgoing
26515 socket, we now close it before refusing, rather than just
26516 leaking it. (Thanks to Peter Palfrader for finding.)
26517 - Fix a file descriptor leak in start_daemon().
26518 - On Windows, you can't always reopen a port right after you've
26519 closed it. So change retry_listeners() to only close and re-open
26520 ports that have changed.
26521 - Workaround a problem with some http proxies that refuse GET
26522 requests that specify "Content-Length: 0". Reported by Adrian.
26523 - Recover better from TCP connections to Tor servers that are
26524 broken but don't tell you (it happens!); and rotate TLS
26525 connections once a week.
26526 - Fix a scary-looking but apparently harmless bug where circuits
26527 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
26528 servers, and never switch to state CIRCUIT_STATE_OPEN.
26529 - Check for even more Windows version flags when writing the platform
26530 string in server descriptors, and note any we don't recognize.
26531 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
26532 get a better idea of why their circuits failed. Not used yet.
26533 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
26534 We don't use them yet, but maybe one day our DNS resolver will be
26535 able to discover them.
26536 - Let people type "tor --install" as well as "tor -install" when they
26537 want to make it an NT service.
26538 - Looks like we were never delivering deflated (i.e. compressed)
26539 running-routers lists, even when asked. Oops.
26540 - We were leaking some memory every time the client changed IPs.
26541 - Clean up more of the OpenSSL memory when exiting, so we can detect
26542 memory leaks better.
26543 - Never call free() on tor_malloc()d memory. This will help us
26544 use dmalloc to detect memory leaks.
26545 - Some Tor servers process billions of cells per day. These
26546 statistics are now uint64_t's.
26547 - Check [X-]Forwarded-For headers in HTTP requests when generating
26548 log messages. This lets people run dirservers (and caches) behind
26549 Apache but still know which IP addresses are causing warnings.
26550 - Fix minor integer overflow in calculating when we expect to use up
26551 our bandwidth allocation before hibernating.
26552 - Lower the minimum required number of file descriptors to 1000,
26553 so we can have some overhead for Valgrind on Linux, where the
26554 default ulimit -n is 1024.
26555 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
26556 and its existence is confusing some users.
26558 o Config option fixes:
26559 - Add a new config option ExitPolicyRejectPrivate which defaults
26560 to on. Now all exit policies will begin with rejecting private
26561 addresses, unless the server operator explicitly turns it off.
26562 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
26563 - Add new ReachableORAddresses and ReachableDirAddresses options
26564 that understand address policies. FascistFirewall is now a synonym
26565 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
26566 - Start calling it FooListenAddress rather than FooBindAddress,
26567 since few of our users know what it means to bind an address
26569 - If the user gave Tor an odd number of command-line arguments,
26570 we were silently ignoring the last one. Now we complain and fail.
26571 This wins the oldest-bug prize -- this bug has been present since
26572 November 2002, as released in Tor 0.0.0.
26573 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
26574 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
26575 it would silently ignore the 6668.
26576 - If we get a linelist or linelist_s config option from the torrc,
26577 e.g. ExitPolicy, and it has no value, warn and skip rather than
26578 silently resetting it to its default.
26579 - Setconf was appending items to linelists, not clearing them.
26580 - Add MyFamily to torrc.sample in the server section, so operators
26581 will be more likely to learn that it exists.
26582 - Make ContactInfo mandatory for authoritative directory servers.
26583 - MaxConn has been obsolete for a while now. Document the ConnLimit
26584 config option, which is a *minimum* number of file descriptors
26585 that must be available else Tor refuses to start.
26586 - Get rid of IgnoreVersion undocumented config option, and make us
26587 only warn, never exit, when we're running an obsolete version.
26588 - Make MonthlyAccountingStart config option truly obsolete now.
26589 - Correct the man page entry on TrackHostExitsExpire.
26590 - Let directory authorities start even if they don't specify an
26591 Address config option.
26592 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
26593 reflect the updated flags in our v2 dir protocol.
26595 o Config option features:
26596 - Add a new config option FastFirstHopPK (on by default) so clients
26597 do a trivial crypto handshake for their first hop, since TLS has
26598 already taken care of confidentiality and authentication.
26599 - Let the user set ControlListenAddress in the torrc. This can be
26600 dangerous, but there are some cases (like a secured LAN) where it
26602 - New config options to help controllers: FetchServerDescriptors
26603 and FetchHidServDescriptors for whether to fetch server
26604 info and hidserv info or let the controller do it, and
26605 PublishServerDescriptor and PublishHidServDescriptors.
26606 - Also let the controller set the __AllDirActionsPrivate config
26607 option if you want all directory fetches/publishes to happen via
26608 Tor (it assumes your controller bootstraps your circuits).
26609 - Add "HardwareAccel" config option: support for crypto hardware
26610 accelerators via OpenSSL. Off by default, until we find somebody
26611 smart who can test it for us. (It appears to produce seg faults
26612 in at least some cases.)
26613 - New config option "AuthDirRejectUnlisted" for directory authorities
26614 as a panic button: if we get flooded with unusable servers we can
26615 revert to only listing servers in the approved-routers file.
26616 - Directory authorities can now reject/invalidate by key and IP,
26617 with the config options "AuthDirInvalid" and "AuthDirReject", or
26618 by marking a fingerprint as "!reject" or "!invalid" (as its
26619 nickname) in the approved-routers file. This is useful since
26620 currently we automatically list servers as running and usable
26621 even if we know they're jerks.
26622 - Add a new config option TestSocks so people can see whether their
26623 applications are using socks4, socks4a, socks5-with-ip, or
26624 socks5-with-fqdn. This way they don't have to keep mucking
26625 with tcpdump and wondering if something got cached somewhere.
26626 - Add "private:*" as an alias in configuration for policies. Now
26627 you can simplify your exit policy rather than needing to list
26628 every single internal or nonroutable network space.
26629 - Accept "private:*" in routerdesc exit policies; not generated yet
26630 because older Tors do not understand it.
26631 - Add configuration option "V1AuthoritativeDirectory 1" which
26632 moria1, moria2, and tor26 have set.
26633 - Implement an option, VirtualAddrMask, to set which addresses
26634 get handed out in response to mapaddress requests. This works
26635 around a bug in tsocks where 127.0.0.0/8 is never socksified.
26636 - Add a new config option FetchUselessDescriptors, off by default,
26637 for when you plan to run "exitlist" on your client and you want
26638 to know about even the non-running descriptors.
26639 - SocksTimeout: How long do we let a socks connection wait
26640 unattached before we fail it?
26641 - CircuitBuildTimeout: Cull non-open circuits that were born
26642 at least this many seconds ago.
26643 - CircuitIdleTimeout: Cull open clean circuits that were born
26644 at least this many seconds ago.
26645 - New config option SafeSocks to reject all application connections
26646 using unsafe socks protocols. Defaults to off.
26648 o Improved and clearer log messages:
26649 - Reduce clutter in server logs. We're going to try to make
26650 them actually usable now. New config option ProtocolWarnings that
26651 lets you hear about how _other Tors_ are breaking the protocol. Off
26653 - Divide log messages into logging domains. Once we put some sort
26654 of interface on this, it will let people looking at more verbose
26655 log levels specify the topics they want to hear more about.
26656 - Log server fingerprint on startup, so new server operators don't
26657 have to go hunting around their filesystem for it.
26658 - Provide dire warnings to any users who set DirServer manually;
26659 move it out of torrc.sample and into torrc.complete.
26660 - Make the log message less scary when all the dirservers are
26661 temporarily unreachable.
26662 - When tor_socketpair() fails in Windows, give a reasonable
26663 Windows-style errno back.
26664 - Improve tor_gettimeofday() granularity on windows.
26665 - We were printing the number of idle dns workers incorrectly when
26667 - Handle duplicate lines in approved-routers files without warning.
26668 - We were whining about using socks4 or socks5-with-local-lookup
26669 even when it's an IP address in the "virtual" range we designed
26670 exactly for this case.
26671 - Check for named servers when looking them up by nickname;
26672 warn when we're calling a non-named server by its nickname;
26673 don't warn twice about the same name.
26674 - Downgrade the dirserver log messages when whining about
26676 - Correct "your server is reachable" log entries to indicate that
26677 it was self-testing that told us so.
26678 - If we're trying to be a Tor server and running Windows 95/98/ME
26679 as a server, explain that we'll likely crash.
26680 - Provide a more useful warn message when our onion queue gets full:
26681 the CPU is too slow or the exit policy is too liberal.
26682 - Don't warn when we receive a 503 from a dirserver/cache -- this
26683 will pave the way for them being able to refuse if they're busy.
26684 - When we fail to bind a listener, try to provide a more useful
26685 log message: e.g., "Is Tor already running?"
26686 - Only start testing reachability once we've established a
26687 circuit. This will make startup on dir authorities less noisy.
26688 - Don't try to upload hidden service descriptors until we have
26689 established a circuit.
26690 - Tor didn't warn when it failed to open a log file.
26691 - Warn when listening on a public address for socks. We suspect a
26692 lot of people are setting themselves up as open socks proxies,
26693 and they have no idea that jerks on the Internet are using them,
26694 since they simply proxy the traffic into the Tor network.
26695 - Give a useful message when people run Tor as the wrong user,
26696 rather than telling them to start chowning random directories.
26697 - Fix a harmless bug that was causing Tor servers to log
26698 "Got an end because of misc error, but we're not an AP. Closing."
26699 - Fix wrong log message when you add a "HiddenServiceNodes" config
26700 line without any HiddenServiceDir line (reported by Chris Thomas).
26701 - Directory authorities now stop whining so loudly about bad
26702 descriptors that they fetch from other dirservers. So when there's
26703 a log complaint, it's for sure from a freshly uploaded descriptor.
26704 - When logging via syslog, include the pid whenever we provide
26705 a log entry. Suggested by Todd Fries.
26706 - When we're shutting down and we do something like try to post a
26707 server descriptor or rendezvous descriptor, don't complain that
26708 we seem to be unreachable. Of course we are, we're shutting down.
26709 - Change log line for unreachability to explicitly suggest /etc/hosts
26710 as the culprit. Also make it clearer what IP address and ports we're
26711 testing for reachability.
26712 - Put quotes around user-supplied strings when logging so users are
26713 more likely to realize if they add bad characters (like quotes)
26715 - NT service patch from Matt Edman to improve error messages on Win32.
26718 Changes in version 0.1.0.17 - 2006-02-17
26719 o Crash bugfixes on 0.1.0.x:
26720 - When servers with a non-zero DirPort came out of hibernation,
26721 sometimes they would trigger an assert.
26723 o Other important bugfixes:
26724 - On platforms that don't have getrlimit (like Windows), we were
26725 artificially constraining ourselves to a max of 1024
26726 connections. Now just assume that we can handle as many as 15000
26727 connections. Hopefully this won't cause other problems.
26729 o Backported features:
26730 - When we're a server, a client asks for an old-style directory,
26731 and our write bucket is empty, don't give it to him. This way
26732 small servers can continue to serve the directory *sometimes*,
26733 without getting overloaded.
26734 - Whenever you get a 503 in response to a directory fetch, try
26735 once more. This will become important once servers start sending
26736 503's whenever they feel busy.
26737 - Fetch a new directory every 120 minutes, not every 40 minutes.
26738 Now that we have hundreds of thousands of users running the old
26739 directory algorithm, it's starting to hurt a lot.
26740 - Bump up the period for forcing a hidden service descriptor upload
26741 from 20 minutes to 1 hour.
26744 Changes in version 0.1.0.16 - 2006-01-02
26745 o Crash bugfixes on 0.1.0.x:
26746 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
26747 corrupting the heap, losing FDs, or crashing when we need to resize
26748 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
26749 - It turns out sparc64 platforms crash on unaligned memory access
26750 too -- so detect and avoid this.
26751 - Handle truncated compressed data correctly (by detecting it and
26753 - Fix possible-but-unlikely free(NULL) in control.c.
26754 - When we were closing connections, there was a rare case that
26755 stomped on memory, triggering seg faults and asserts.
26756 - Avoid potential infinite recursion when building a descriptor. (We
26757 don't know that it ever happened, but better to fix it anyway.)
26758 - We were neglecting to unlink marked circuits from soon-to-close OR
26759 connections, which caused some rare scribbling on freed memory.
26760 - Fix a memory stomping race bug when closing the joining point of two
26761 rendezvous circuits.
26762 - Fix an assert in time parsing found by Steven Murdoch.
26764 o Other bugfixes on 0.1.0.x:
26765 - When we're doing reachability testing, provide more useful log
26766 messages so the operator knows what to expect.
26767 - Do not check whether DirPort is reachable when we are suppressing
26768 advertising it because of hibernation.
26769 - When building with -static or on Solaris, we sometimes needed -ldl.
26770 - One of the dirservers (tor26) changed its IP address.
26771 - When we're deciding whether a stream has enough circuits around
26772 that can handle it, count the freshly dirty ones and not the ones
26773 that are so dirty they won't be able to handle it.
26774 - When we're expiring old circuits, we had a logic error that caused
26775 us to close new rendezvous circuits rather than old ones.
26776 - Give a more helpful log message when you try to change ORPort via
26777 the controller: you should upgrade Tor if you want that to work.
26778 - We were failing to parse Tor versions that start with "Tor ".
26779 - Tolerate faulty streams better: when a stream fails for reason
26780 exitpolicy, stop assuming that the router is lying about his exit
26781 policy. When a stream fails for reason misc, allow it to retry just
26782 as if it was resolvefailed. When a stream has failed three times,
26783 reset its failure count so we can try again and get all three tries.
26786 Changes in version 0.1.0.15 - 2005-09-23
26787 o Bugfixes on 0.1.0.x:
26788 - Reject ports 465 and 587 (spam targets) in default exit policy.
26789 - Don't crash when we don't have any spare file descriptors and we
26790 try to spawn a dns or cpu worker.
26791 - Get rid of IgnoreVersion undocumented config option, and make us
26792 only warn, never exit, when we're running an obsolete version.
26793 - Don't try to print a null string when your server finds itself to
26794 be unreachable and the Address config option is empty.
26795 - Make the numbers in read-history and write-history into uint64s,
26796 so they don't overflow and publish negatives in the descriptor.
26797 - Fix a minor memory leak in smartlist_string_remove().
26798 - We were only allowing ourselves to upload a server descriptor at
26799 most every 20 minutes, even if it changed earlier than that.
26800 - Clean up log entries that pointed to old URLs.
26803 Changes in version 0.1.0.14 - 2005-08-08
26804 o Bugfixes on 0.1.0.x:
26805 - Fix the other half of the bug with crypto handshakes
26807 - Fix an assert trigger if you send a 'signal term' via the
26808 controller when it's listening for 'event info' messages.
26811 Changes in version 0.1.0.13 - 2005-08-04
26812 o Bugfixes on 0.1.0.x:
26813 - Fix a critical bug in the security of our crypto handshakes.
26814 - Fix a size_t underflow in smartlist_join_strings2() that made
26815 it do bad things when you hand it an empty smartlist.
26816 - Fix Windows installer to ship Tor license (thanks to Aphex for
26817 pointing out this oversight) and put a link to the doc directory
26819 - Explicitly set no-unaligned-access for sparc: it turns out the
26820 new gcc's let you compile broken code, but that doesn't make it
26824 Changes in version 0.1.0.12 - 2005-07-18
26825 o New directory servers:
26826 - tor26 has changed IP address.
26828 o Bugfixes on 0.1.0.x:
26829 - Fix a possible double-free in tor_gzip_uncompress().
26830 - When --disable-threads is set, do not search for or link against
26831 pthreads libraries.
26832 - Don't trigger an assert if an authoritative directory server
26833 claims its dirport is 0.
26834 - Fix bug with removing Tor as an NT service: some people were
26835 getting "The service did not return an error." Thanks to Matt
26839 Changes in version 0.1.0.11 - 2005-06-30
26840 o Bugfixes on 0.1.0.x:
26841 - Fix major security bug: servers were disregarding their
26842 exit policies if clients behaved unexpectedly.
26843 - Make OS X init script check for missing argument, so we don't
26844 confuse users who invoke it incorrectly.
26845 - Fix a seg fault in "tor --hash-password foo".
26846 - The MAPADDRESS control command was broken.
26849 Changes in version 0.1.0.10 - 2005-06-14
26851 - Make NT services work and start on startup on Win32 (based on
26852 patch by Matt Edman). See the FAQ entry for details.
26853 - Make 'platform' string in descriptor more accurate for Win32
26854 servers, so it's not just "unknown platform".
26855 - REUSEADDR on normal platforms means you can rebind to the port
26856 right after somebody else has let it go. But REUSEADDR on Win32
26857 means you can bind to the port _even when somebody else already
26858 has it bound_! So, don't do that on Win32.
26859 - Clean up the log messages when starting on Win32 with no config
26861 - Allow seeding the RNG on Win32 even when you're not running as
26862 Administrator. If seeding the RNG on Win32 fails, quit.
26864 o Assert / crash bugs:
26865 - Refuse relay cells that claim to have a length larger than the
26866 maximum allowed. This prevents a potential attack that could read
26867 arbitrary memory (e.g. keys) from an exit server's process
26869 - If unofficial Tor clients connect and send weird TLS certs, our
26870 Tor server triggers an assert. Stop asserting, and start handling
26871 TLS errors better in other situations too.
26872 - Fix a race condition that can trigger an assert when we have a
26873 pending create cell and an OR connection attempt fails.
26876 - Use pthreads for worker processes rather than forking. This was
26877 forced because when we forked, we ended up wasting a lot of
26878 duplicate ram over time.
26879 - Also switch to foo_r versions of some library calls to allow
26880 reentry and threadsafeness.
26881 - Implement --disable-threads configure option. Disable threads on
26882 netbsd and openbsd by default, because they have no reentrant
26883 resolver functions (!), and on solaris since it has other
26885 - Fix possible bug on threading platforms (e.g. win32) which was
26886 leaking a file descriptor whenever a cpuworker or dnsworker died.
26887 - Fix a minor memory leak when somebody establishes an introduction
26888 point at your Tor server.
26889 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
26891 - Add ./configure --with-dmalloc option, to track memory leaks.
26892 - And try to free all memory on closing, so we can detect what
26895 o Protocol correctness:
26896 - When we've connected to an OR and handshaked but didn't like
26897 the result, we were closing the conn without sending destroy
26898 cells back for pending circuits. Now send those destroys.
26899 - Start sending 'truncated' cells back rather than destroy cells
26900 if the circuit closes in front of you. This means we won't have
26901 to abandon partially built circuits.
26902 - Handle changed router status correctly when dirserver reloads
26903 fingerprint file. We used to be dropping all unverified descriptors
26904 right then. The bug was hidden because we would immediately
26905 fetch a directory from another dirserver, which would include the
26906 descriptors we just dropped.
26907 - Revise tor-spec to add more/better stream end reasons.
26908 - Revise all calls to connection_edge_end to avoid sending 'misc',
26909 and to take errno into account where possible.
26910 - Client now retries when streams end early for 'hibernating' or
26911 'resource limit' reasons, rather than failing them.
26912 - Try to be more zealous about calling connection_edge_end when
26913 things go bad with edge conns in connection.c.
26915 o Robustness improvements:
26916 - Better handling for heterogeneous / unreliable nodes:
26917 - Annotate circuits with whether they aim to contain high uptime
26918 nodes and/or high capacity nodes. When building circuits, choose
26920 - This means that every single node in an intro rend circuit,
26921 not just the last one, will have a minimum uptime.
26922 - New config option LongLivedPorts to indicate application streams
26923 that will want high uptime circuits.
26924 - Servers reset uptime when a dir fetch entirely fails. This
26925 hopefully reflects stability of the server's network connectivity.
26926 - If somebody starts his tor server in Jan 2004 and then fixes his
26927 clock, don't make his published uptime be a year.
26928 - Reset published uptime when we wake up from hibernation.
26929 - Introduce a notion of 'internal' circs, which are chosen without
26930 regard to the exit policy of the last hop. Intro and rendezvous
26931 circs must be internal circs, to avoid leaking information. Resolve
26932 and connect streams can use internal circs if they want.
26933 - New circuit pooling algorithm: keep track of what destination ports
26934 we've used recently (start out assuming we'll want to use 80), and
26935 make sure to have enough circs around to satisfy these ports. Also
26936 make sure to have 2 internal circs around if we've required internal
26937 circs lately (and with high uptime if we've seen that lately too).
26938 - Turn addr_policy_compare from a tristate to a quadstate; this should
26939 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
26940 for google.com" problem.
26941 - When a client asks us for a dir mirror and we don't have one,
26942 launch an attempt to get a fresh one.
26943 - First cut at support for "create-fast" cells. Clients can use
26944 these when extending to their first hop, since the TLS already
26945 provides forward secrecy and authentication. Not enabled on
26948 o Reachability testing.
26949 - Your Tor server will automatically try to see if its ORPort and
26950 DirPort are reachable from the outside, and it won't upload its
26951 descriptor until it decides at least ORPort is reachable (when
26952 DirPort is not yet found reachable, publish it as zero).
26953 - When building testing circs for ORPort testing, use only
26954 high-bandwidth nodes, so fewer circuits fail.
26955 - Notice when our IP changes, and reset stats/uptime/reachability.
26956 - Authdirservers don't do ORPort reachability detection, since
26957 they're in clique mode, so it will be rare to find a server not
26958 already connected to them.
26959 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
26963 - Now we allow two unverified servers with the same nickname
26964 but different keys. But if a nickname is verified, only that
26965 nickname+key are allowed.
26966 - If you're an authdirserver connecting to an address:port,
26967 and it's not the OR you were expecting, forget about that
26968 descriptor. If he *was* the one you were expecting, then forget
26969 about all other descriptors for that address:port.
26970 - Allow servers to publish descriptors from 12 hours in the future.
26971 Corollary: only whine about clock skew from the dirserver if
26972 he's a trusted dirserver (since now even verified servers could
26973 have quite wrong clocks).
26974 - Require servers that use the default dirservers to have public IP
26975 addresses. We have too many servers that are configured with private
26976 IPs and their admins never notice the log entries complaining that
26977 their descriptors are being rejected.
26979 o Efficiency improvements:
26980 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
26981 and /dev/poll), and hopefully work better on Windows too.
26982 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
26983 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
26984 - Find libevent even if it's hiding in /usr/local/ and your
26985 CFLAGS and LDFLAGS don't tell you to look there.
26986 - Be able to link with libevent as a shared library (the default
26987 after 1.0d), even if it's hiding in /usr/local/lib and even
26988 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
26989 assuming you're running gcc. Otherwise fail and give a useful
26991 - Switch to a new buffer management algorithm, which tries to avoid
26992 reallocing and copying quite as much. In first tests it looks like
26993 it uses *more* memory on average, but less cpu.
26994 - Switch our internal buffers implementation to use a ring buffer,
26995 to hopefully improve performance for fast servers a lot.
26996 - Reenable the part of the code that tries to flush as soon as an
26997 OR outbuf has a full TLS record available. Perhaps this will make
26998 OR outbufs not grow as huge except in rare cases, thus saving lots
26999 of CPU time plus memory.
27000 - Improve performance for dirservers: stop re-parsing the whole
27001 directory every time you regenerate it.
27002 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
27003 it much faster to look up a circuit for each relay cell.
27004 - Remove most calls to assert_all_pending_dns_resolves_ok(),
27005 since they're eating our cpu on exit nodes.
27006 - Stop wasting time doing a case insensitive comparison for every
27007 dns name every time we do any lookup. Canonicalize the names to
27008 lowercase when you first see them.
27011 - Handle unavailable hidden services better. Handle slow or busy
27012 hidden services better.
27013 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
27014 circ as necessary, if there are any completed ones lying around
27015 when we try to launch one.
27016 - Make hidden services try to establish a rendezvous for 30 seconds
27017 after fetching the descriptor, rather than for n (where n=3)
27018 attempts to build a circuit.
27019 - Adjust maximum skew and age for rendezvous descriptors: let skew
27020 be 48 hours rather than 90 minutes.
27021 - Reject malformed .onion addresses rather then passing them on as
27022 normal web requests.
27025 - More Tor controller support. See
27026 http://tor.eff.org/doc/control-spec.txt for all the new features,
27027 including signals to emulate unix signals from any platform;
27028 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
27029 closestream; closecircuit; etc.
27030 - Encode hashed controller passwords in hex instead of base64,
27031 to make it easier to write controllers.
27032 - Revise control spec and implementation to allow all log messages to
27033 be sent to controller with their severities intact (suggested by
27034 Matt Edman). Disable debug-level logs while delivering a debug-level
27035 log to the controller, to prevent loop. Update TorControl to handle
27036 new log event types.
27038 o New config options/defaults:
27039 - Begin scrubbing sensitive strings from logs by default. Turn off
27040 the config option SafeLogging if you need to do debugging.
27041 - New exit policy: accept most low-numbered ports, rather than
27042 rejecting most low-numbered ports.
27043 - Put a note in the torrc about abuse potential with the default
27045 - Add support for CONNECTing through https proxies, with "HttpsProxy"
27047 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
27048 based on patch from Adam Langley (basic auth only).
27049 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
27050 the fast servers that have been joining lately. (Clients are now
27051 willing to load balance over up to 2 MB of advertised bandwidth
27053 - New config option MaxAdvertisedBandwidth which lets you advertise
27054 a low bandwidthrate (to not attract as many circuits) while still
27055 allowing a higher bandwidthrate in reality.
27056 - Require BandwidthRate to be at least 20kB/s for servers.
27057 - Add a NoPublish config option, so you can be a server (e.g. for
27058 testing running Tor servers in other Tor networks) without
27059 publishing your descriptor to the primary dirservers.
27060 - Add a new AddressMap config directive to rewrite incoming socks
27061 addresses. This lets you, for example, declare an implicit
27062 required exit node for certain sites.
27063 - Add a new TrackHostExits config directive to trigger addressmaps
27064 for certain incoming socks addresses -- for sites that break when
27065 your exit keeps changing (based on patch from Mike Perry).
27066 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
27067 which describes how often we retry making new circuits if current
27068 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
27069 how long we're willing to make use of an already-dirty circuit.
27070 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
27071 a config option "ShutdownWaitLength" (when using kill -INT on
27073 - Fix an edge case in parsing config options: if they say "--"
27074 on the commandline, it's not a config option (thanks weasel).
27075 - New config option DirAllowPrivateAddresses for authdirservers.
27076 Now by default they refuse router descriptors that have non-IP or
27077 private-IP addresses.
27078 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
27079 smart" default value: low for servers and high for clients.
27080 - Some people were putting "Address " in their torrc, and they had
27081 a buggy resolver that resolved " " to 0.0.0.0. Oops.
27082 - If DataDir is ~/.tor, and that expands to /.tor, then default to
27083 LOCALSTATEDIR/tor instead.
27084 - Implement --verify-config command-line option to check if your torrc
27085 is valid without actually launching Tor.
27087 o Logging improvements:
27088 - When dirservers refuse a server descriptor, we now log its
27089 contactinfo, platform, and the poster's IP address.
27090 - Only warn once per nickname from add_nickname_list_to_smartlist()
27091 per failure, so an entrynode or exitnode choice that's down won't
27093 - When we're connecting to an OR and he's got a different nickname/key
27094 than we were expecting, only complain loudly if we're an OP or a
27095 dirserver. Complaining loudly to the OR admins just confuses them.
27096 - Whine at you if you're a server and you don't set your contactinfo.
27097 - Warn when exit policy implicitly allows local addresses.
27098 - Give a better warning when some other server advertises an
27099 ORPort that is actually an apache running ssl.
27100 - If we get an incredibly skewed timestamp from a dirserver mirror
27101 that isn't a verified OR, don't warn -- it's probably him that's
27103 - When a dirserver causes you to give a warn, mention which dirserver
27105 - Initialize libevent later in the startup process, so the logs are
27106 already established by the time we start logging libevent warns.
27107 - Use correct errno on win32 if libevent fails.
27108 - Check and warn about known-bad/slow libevent versions.
27109 - Stop warning about sigpipes in the logs. We're going to
27110 pretend that getting these occasionally is normal and fine.
27112 o New contrib scripts:
27113 - New experimental script tor/contrib/exitlist: a simple python
27114 script to parse directories and find Tor nodes that exit to listed
27116 - New experimental script tor/contrib/ExerciseServer.py (needs more
27117 work) that uses the controller interface to build circuits and
27118 fetch pages over them. This will help us bootstrap servers that
27119 have lots of capacity but haven't noticed it yet.
27120 - New experimental script tor/contrib/PathDemo.py (needs more work)
27121 that uses the controller interface to let you choose whole paths
27123 "<hostname>.<path,separated by dots>.<length of path>.path"
27124 - New contributed script "privoxy-tor-toggle" to toggle whether
27125 Privoxy uses Tor. Seems to be configured for Debian by default.
27126 - Have torctl.in/tor.sh.in check for location of su binary (needed
27130 - chdir() to your datadirectory at the *end* of the daemonize process,
27131 not the beginning. This was a problem because the first time you
27132 run tor, if your datadir isn't there, and you have runasdaemon set
27133 to 1, it will try to chdir to it before it tries to create it. Oops.
27134 - Fix several double-mark-for-close bugs, e.g. where we were finding
27135 a conn for a cell even if that conn is already marked for close.
27136 - Stop most cases of hanging up on a socks connection without sending
27138 - Fix a bug in the RPM package: set home directory for _tor to
27139 something more reasonable when first installing.
27140 - Stop putting nodename in the Platform string in server descriptors.
27141 It doesn't actually help, and it is confusing/upsetting some people.
27142 - When using preferred entry or exit nodes, ignore whether the
27143 circuit wants uptime or capacity. They asked for the nodes, they
27145 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
27146 artificially capped at 500kB.
27147 - Cache local dns resolves correctly even when they're .exit
27149 - If we're hibernating and we get a SIGINT, exit immediately.
27150 - tor-resolve requests were ignoring .exit if there was a working circuit
27151 they could use instead.
27152 - Pay more attention to the ClientOnly config option.
27153 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
27154 installer screens; and don't put stuff into StartupItems unless
27155 the user asks you to.
27158 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
27159 rather than just rejecting it.
27160 - If our clock jumps forward by 100 seconds or more, assume something
27161 has gone wrong with our network and abandon all not-yet-used circs.
27162 - When an application is using socks5, give him the whole variety of
27163 potential socks5 responses (connect refused, host unreachable, etc),
27164 rather than just "success" or "failure".
27165 - A more sane version numbering system. See
27166 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
27167 - Change version parsing logic: a version is "obsolete" if it is not
27168 recommended and (1) there is a newer recommended version in the
27169 same series, or (2) there are no recommended versions in the same
27170 series, but there are some recommended versions in a newer series.
27171 A version is "new" if it is newer than any recommended version in
27173 - Report HTTP reasons to client when getting a response from directory
27174 servers -- so you can actually know what went wrong.
27175 - Reject odd-looking addresses at the client (e.g. addresses that
27176 contain a colon), rather than having the server drop them because
27178 - Stop publishing socksport in the directory, since it's not
27179 actually meant to be public. For compatibility, publish a 0 there
27181 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
27182 cookies to disk and doesn't log each web request to disk. (Thanks
27183 to Brett Carrington for pointing this out.)
27184 - Add OSX uninstall instructions. An actual uninstall script will
27186 - Add "opt hibernating 1" to server descriptor to make it clearer
27187 whether the server is hibernating.
27190 Changes in version 0.0.9.10 - 2005-06-16
27191 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
27192 - Refuse relay cells that claim to have a length larger than the
27193 maximum allowed. This prevents a potential attack that could read
27194 arbitrary memory (e.g. keys) from an exit server's process
27198 Changes in version 0.0.9.9 - 2005-04-23
27199 o Bugfixes on 0.0.9.x:
27200 - If unofficial Tor clients connect and send weird TLS certs, our
27201 Tor server triggers an assert. This release contains a minimal
27202 backport from the broader fix that we put into 0.1.0.4-rc.
27205 Changes in version 0.0.9.8 - 2005-04-07
27206 o Bugfixes on 0.0.9.x:
27207 - We have a bug that I haven't found yet. Sometimes, very rarely,
27208 cpuworkers get stuck in the 'busy' state, even though the cpuworker
27209 thinks of itself as idle. This meant that no new circuits ever got
27210 established. Here's a workaround to kill any cpuworker that's been
27211 busy for more than 100 seconds.
27214 Changes in version 0.0.9.7 - 2005-04-01
27215 o Bugfixes on 0.0.9.x:
27216 - Fix another race crash bug (thanks to Glenn Fink for reporting).
27217 - Compare identity to identity, not to nickname, when extending to
27218 a router not already in the directory. This was preventing us from
27219 extending to unknown routers. Oops.
27220 - Make sure to create OS X Tor user in <500 range, so we aren't
27221 creating actual system users.
27222 - Note where connection-that-hasn't-sent-end was marked, and fix
27223 a few really loud instances of this harmless bug (it's fixed more
27227 Changes in version 0.0.9.6 - 2005-03-24
27228 o Bugfixes on 0.0.9.x (crashes and asserts):
27229 - Add new end stream reasons to maintenance branch. Fix bug where
27230 reason (8) could trigger an assert. Prevent bug from recurring.
27231 - Apparently win32 stat wants paths to not end with a slash.
27232 - Fix assert triggers in assert_cpath_layer_ok(), where we were
27233 blowing away the circuit that conn->cpath_layer points to, then
27234 checking to see if the circ is well-formed. Backport check to make
27235 sure we dont use the cpath on a closed connection.
27236 - Prevent circuit_resume_edge_reading_helper() from trying to package
27237 inbufs for marked-for-close streams.
27238 - Don't crash on hup if your options->address has become unresolvable.
27239 - Some systems (like OS X) sometimes accept() a connection and tell
27240 you the remote host is 0.0.0.0:0. If this happens, due to some
27241 other mis-features, we get confused; so refuse the conn for now.
27243 o Bugfixes on 0.0.9.x (other):
27244 - Fix harmless but scary "Unrecognized content encoding" warn message.
27245 - Add new stream error reason: TORPROTOCOL reason means "you are not
27246 speaking a version of Tor I understand; say bye-bye to your stream."
27247 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
27248 into the future, now that we are more tolerant of skew. This
27249 resolves a bug where a Tor server would refuse to cache a directory
27250 because all the directories it gets are too far in the future;
27251 yet the Tor server never logs any complaints about clock skew.
27252 - Mac packaging magic: make man pages useable, and do not overwrite
27253 existing torrc files.
27254 - Make OS X log happily to /var/log/tor/tor.log
27257 Changes in version 0.0.9.5 - 2005-02-22
27258 o Bugfixes on 0.0.9.x:
27259 - Fix an assert race at exit nodes when resolve requests fail.
27260 - Stop picking unverified dir mirrors--it only leads to misery.
27261 - Patch from Matt Edman to make NT services work better. Service
27262 support is still not compiled into the executable by default.
27263 - Patch from Dmitri Bely so the Tor service runs better under
27264 the win32 SYSTEM account.
27265 - Make tor-resolve actually work (?) on Win32.
27266 - Fix a sign bug when getrlimit claims to have 4+ billion
27267 file descriptors available.
27268 - Stop refusing to start when bandwidthburst == bandwidthrate.
27269 - When create cells have been on the onion queue more than five
27270 seconds, just send back a destroy and take them off the list.
27273 Changes in version 0.0.9.4 - 2005-02-03
27274 o Bugfixes on 0.0.9:
27275 - Fix an assert bug that took down most of our servers: when
27276 a server claims to have 1 GB of bandwidthburst, don't
27278 - Don't crash as badly if we have spawned the max allowed number
27279 of dnsworkers, or we're out of file descriptors.
27280 - Block more file-sharing ports in the default exit policy.
27281 - MaxConn is now automatically set to the hard limit of max
27282 file descriptors we're allowed (ulimit -n), minus a few for
27284 - Give a clearer message when servers need to raise their
27285 ulimit -n when they start running out of file descriptors.
27286 - SGI Compatibility patches from Jan Schaumann.
27287 - Tolerate a corrupt cached directory better.
27288 - When a dirserver hasn't approved your server, list which one.
27289 - Go into soft hibernation after 95% of the bandwidth is used,
27290 not 99%. This is especially important for daily hibernators who
27291 have a small accounting max. Hopefully it will result in fewer
27292 cut connections when the hard hibernation starts.
27293 - Load-balance better when using servers that claim more than
27294 800kB/s of capacity.
27295 - Make NT services work (experimental, only used if compiled in).
27298 Changes in version 0.0.9.3 - 2005-01-21
27299 o Bugfixes on 0.0.9:
27300 - Backport the cpu use fixes from main branch, so busy servers won't
27301 need as much processor time.
27302 - Work better when we go offline and then come back, or when we
27303 run Tor at boot before the network is up. We do this by
27304 optimistically trying to fetch a new directory whenever an
27305 application request comes in and we think we're offline -- the
27306 human is hopefully a good measure of when the network is back.
27307 - Backport some minimal hidserv bugfixes: keep rend circuits open as
27308 long as you keep using them; actually publish hidserv descriptors
27309 shortly after they change, rather than waiting 20-40 minutes.
27310 - Enable Mac startup script by default.
27311 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
27312 - When you update AllowUnverifiedNodes or FirewallPorts via the
27313 controller's setconf feature, we were always appending, never
27315 - When you update HiddenServiceDir via setconf, it was screwing up
27316 the order of reading the lines, making it fail.
27317 - Do not rewrite a cached directory back to the cache; otherwise we
27318 will think it is recent and not fetch a newer one on startup.
27319 - Workaround for webservers that lie about Content-Encoding: Tor
27320 now tries to autodetect compressed directories and compression
27321 itself. This lets us Proxypass dir fetches through apache.
27324 Changes in version 0.0.9.2 - 2005-01-04
27325 o Bugfixes on 0.0.9 (crashes and asserts):
27326 - Fix an assert on startup when the disk is full and you're logging
27328 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
27329 style address, then we'd crash.
27330 - Fix an assert trigger when the running-routers string we get from
27331 a dirserver is broken.
27332 - Make worker threads start and run on win32. Now win32 servers
27334 - Bandaid (not actually fix, but now it doesn't crash) an assert
27335 where the dns worker dies mysteriously and the main Tor process
27336 doesn't remember anything about the address it was resolving.
27338 o Bugfixes on 0.0.9 (Win32):
27339 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
27340 name out of the warning/assert messages.
27341 - Fix a superficial "unhandled error on read" bug on win32.
27342 - The win32 installer no longer requires a click-through for our
27343 license, since our Free Software license grants rights but does not
27345 - Win32: When connecting to a dirserver fails, try another one
27346 immediately. (This was already working for non-win32 Tors.)
27347 - Stop trying to parse $HOME on win32 when hunting for default
27349 - Make tor-resolve.c work on win32 by calling network_init().
27351 o Bugfixes on 0.0.9 (other):
27352 - Make 0.0.9.x build on Solaris again.
27353 - Due to a fencepost error, we were blowing away the \n when reporting
27354 confvalue items in the controller. So asking for multiple config
27355 values at once couldn't work.
27356 - When listing circuits that are pending on an opening OR connection,
27357 if we're an OR we were listing circuits that *end* at us as
27358 being pending on every listener, dns/cpu worker, etc. Stop that.
27359 - Dirservers were failing to create 'running-routers' or 'directory'
27360 strings if we had more than some threshold of routers. Fix them so
27361 they can handle any number of routers.
27362 - Fix a superficial "Duplicate mark for close" bug.
27363 - Stop checking for clock skew for OR connections, even for servers.
27364 - Fix a fencepost error that was chopping off the last letter of any
27365 nickname that is the maximum allowed nickname length.
27366 - Update URLs in log messages so they point to the new website.
27367 - Fix a potential problem in mangling server private keys while
27368 writing to disk (not triggered yet, as far as we know).
27369 - Include the licenses for other free software we include in Tor,
27370 now that we're shipping binary distributions more regularly.
27373 Changes in version 0.0.9.1 - 2004-12-15
27374 o Bugfixes on 0.0.9:
27375 - Make hibernation actually work.
27376 - Make HashedControlPassword config option work.
27377 - When we're reporting event circuit status to a controller,
27378 don't use the stream status code.
27381 Changes in version 0.0.9 - 2004-12-12
27382 o Bugfixes on 0.0.8.1 (Crashes and asserts):
27383 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
27384 write() call will fail and we handle it there.
27385 - When we run out of disk space, or other log writing error, don't
27386 crash. Just stop logging to that log and continue.
27387 - Fix isspace() and friends so they still make Solaris happy
27388 but also so they don't trigger asserts on win32.
27389 - Fix assert failure on malformed socks4a requests.
27390 - Fix an assert bug where a hidden service provider would fail if
27391 the first hop of his rendezvous circuit was down.
27392 - Better handling of size_t vs int, so we're more robust on 64
27395 o Bugfixes on 0.0.8.1 (Win32):
27396 - Make windows sockets actually non-blocking (oops), and handle
27397 win32 socket errors better.
27398 - Fix parse_iso_time on platforms without strptime (eg win32).
27399 - win32: when being multithreaded, leave parent fdarray open.
27400 - Better handling of winsock includes on non-MSV win32 compilers.
27401 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
27403 - Make unit tests work on win32.
27405 o Bugfixes on 0.0.8.1 (Path selection and streams):
27406 - Calculate timeout for waiting for a connected cell from the time
27407 we sent the begin cell, not from the time the stream started. If
27408 it took a long time to establish the circuit, we would time out
27409 right after sending the begin cell.
27410 - Fix router_compare_addr_to_addr_policy: it was not treating a port
27411 of * as always matching, so we were picking reject *:* nodes as
27412 exit nodes too. Oops.
27413 - When read() failed on a stream, we would close it without sending
27414 back an end. So 'connection refused' would simply be ignored and
27415 the user would get no response.
27416 - Stop a sigpipe: when an 'end' cell races with eof from the app,
27417 we shouldn't hold-open-until-flush if the eof arrived first.
27418 - Let resolve conns retry/expire also, rather than sticking around
27420 - Fix more dns related bugs: send back resolve_failed and end cells
27421 more reliably when the resolve fails, rather than closing the
27422 circuit and then trying to send the cell. Also attach dummy resolve
27423 connections to a circuit *before* calling dns_resolve(), to fix
27424 a bug where cached answers would never be sent in RESOLVED cells.
27426 o Bugfixes on 0.0.8.1 (Circuits):
27427 - Finally fix a bug that's been plaguing us for a year:
27428 With high load, circuit package window was reaching 0. Whenever
27429 we got a circuit-level sendme, we were reading a lot on each
27430 socket, but only writing out a bit. So we would eventually reach
27431 eof. This would be noticed and acted on even when there were still
27432 bytes sitting in the inbuf.
27433 - Use identity comparison, not nickname comparison, to choose which
27434 half of circuit-ID-space each side gets to use. This is needed
27435 because sometimes we think of a router as a nickname, and sometimes
27436 as a hex ID, and we can't predict what the other side will do.
27438 o Bugfixes on 0.0.8.1 (Other):
27439 - Fix a whole slew of memory leaks.
27440 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
27441 - If we are using select, make sure we stay within FD_SETSIZE.
27442 - When poll() is interrupted, we shouldn't believe the revents values.
27443 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
27444 and smartlist_len, which are two major profiling offenders.
27445 - If do_hup fails, actually notice.
27446 - Flush the log file descriptor after we print "Tor opening log file",
27447 so we don't see those messages days later.
27448 - Hidden service operators now correctly handle version 1 style
27449 INTRODUCE1 cells (nobody generates them still, so not a critical
27451 - Handle more errnos from accept() without closing the listener.
27452 Some OpenBSD machines were closing their listeners because
27453 they ran out of file descriptors.
27454 - Some people had wrapped their tor client/server in a script
27455 that would restart it whenever it died. This did not play well
27456 with our "shut down if your version is obsolete" code. Now people
27457 don't fetch a new directory if their local cached version is
27459 - Make our autogen.sh work on ksh as well as bash.
27460 - Better torrc example lines for dirbindaddress and orbindaddress.
27461 - Improved bounds checking on parsed ints (e.g. config options and
27462 the ones we find in directories.)
27463 - Stop using separate defaults for no-config-file and
27464 empty-config-file. Now you have to explicitly turn off SocksPort,
27465 if you don't want it open.
27466 - We were starting to daemonize before we opened our logs, so if
27467 there were any problems opening logs, we would complain to stderr,
27468 which wouldn't work, and then mysteriously exit.
27469 - If a verified OR connects to us before he's uploaded his descriptor,
27470 or we verify him and hup but he still has the original TLS
27471 connection, then conn->nickname is still set like he's unverified.
27473 o Code security improvements, inspired by Ilja:
27474 - tor_snprintf wrapper over snprintf with consistent (though not C99)
27476 - Replace sprintf with tor_snprintf. (I think they were all safe, but
27478 - Replace strcpy/strncpy with strlcpy in more places.
27479 - Avoid strcat; use tor_snprintf or strlcat instead.
27481 o Features (circuits and streams):
27482 - New circuit building strategy: keep a list of ports that we've
27483 used in the past 6 hours, and always try to have 2 circuits open
27484 or on the way that will handle each such port. Seed us with port
27485 80 so web users won't complain that Tor is "slow to start up".
27486 - Make kill -USR1 dump more useful stats about circuits.
27487 - When warning about retrying or giving up, print the address, so
27488 the user knows which one it's talking about.
27489 - If you haven't used a clean circuit in an hour, throw it away,
27490 just to be on the safe side. (This means after 6 hours a totally
27491 unused Tor client will have no circuits open.)
27492 - Support "foo.nickname.exit" addresses, to let Alice request the
27493 address "foo" as viewed by exit node "nickname". Based on a patch
27494 from Geoff Goodell.
27495 - If your requested entry or exit node has advertised bandwidth 0,
27497 - Be more greedy about filling up relay cells -- we try reading again
27498 once we've processed the stuff we read, in case enough has arrived
27499 to fill the last cell completely.
27500 - Refuse application socks connections to port 0.
27501 - Use only 0.0.9pre1 and later servers for resolve cells.
27503 o Features (bandwidth):
27504 - Hibernation: New config option "AccountingMax" lets you
27505 set how many bytes per month (in each direction) you want to
27506 allow your server to consume. Rather than spreading those
27507 bytes out evenly over the month, we instead hibernate for some
27508 of the month and pop up at a deterministic time, work until
27509 the bytes are consumed, then hibernate again. Config option
27510 "MonthlyAccountingStart" lets you specify which day of the month
27511 your billing cycle starts on.
27512 - Implement weekly/monthly/daily accounting: now you specify your
27513 hibernation properties by
27514 AccountingMax N bytes|KB|MB|GB|TB
27515 AccountingStart day|week|month [day] HH:MM
27516 Defaults to "month 1 0:00".
27517 - Let bandwidth and interval config options be specified as 5 bytes,
27518 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
27520 o Features (directories):
27521 - New "router-status" line in directory, to better bind each verified
27522 nickname to its identity key.
27523 - Clients can ask dirservers for /dir.z to get a compressed version
27524 of the directory. Only works for servers running 0.0.9, of course.
27525 - Make clients cache directories and use them to seed their router
27526 lists at startup. This means clients have a datadir again.
27527 - Respond to content-encoding headers by trying to uncompress as
27529 - Clients and servers now fetch running-routers; cache
27530 running-routers; compress running-routers; serve compressed
27532 - Make moria2 advertise a dirport of 80, so people behind firewalls
27533 will be able to get a directory.
27534 - Http proxy support
27535 - Dirservers translate requests for http://%s:%d/x to /x
27536 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
27537 be routed through this host.
27538 - Clients ask for /tor/x rather than /x for new enough dirservers.
27539 This way we can one day coexist peacefully with apache.
27540 - Clients specify a "Host: %s%d" http header, to be compatible
27541 with more proxies, and so running squid on an exit node can work.
27542 - Protect dirservers from overzealous descriptor uploading -- wait
27543 10 seconds after directory gets dirty, before regenerating.
27545 o Features (packages and install):
27546 - Add NSI installer contributed by J Doe.
27547 - Apply NT service patch from Osamu Fujino. Still needs more work.
27548 - Commit VC6 and VC7 workspace/project files.
27549 - Commit a tor.spec for making RPM files, with help from jbash.
27550 - Add contrib/torctl.in contributed by Glenn Fink.
27551 - Make expand_filename handle ~ and ~username.
27552 - Use autoconf to enable largefile support where necessary. Use
27553 ftello where available, since ftell can fail at 2GB.
27554 - Ship src/win32/ in the tarball, so people can use it to build.
27555 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
27558 o Features (ui controller):
27559 - Control interface: a separate program can now talk to your
27560 client/server over a socket, and get/set config options, receive
27561 notifications of circuits and streams starting/finishing/dying,
27562 bandwidth used, etc. The next step is to get some GUIs working.
27563 Let us know if you want to help out. See doc/control-spec.txt .
27564 - Ship a contrib/tor-control.py as an example script to interact
27565 with the control port.
27566 - "tor --hash-password zzyxz" will output a salted password for
27567 use in authenticating to the control interface.
27568 - Implement the control-spec's SAVECONF command, to write your
27569 configuration to torrc.
27570 - Get cookie authentication for the controller closer to working.
27571 - When set_conf changes our server descriptor, upload a new copy.
27572 But don't upload it too often if there are frequent changes.
27574 o Features (config and command-line):
27575 - Deprecate unofficial config option abbreviations, and abbreviations
27576 not on the command line.
27577 - Configuration infrastructure support for warning on obsolete
27579 - Give a slightly more useful output for "tor -h".
27580 - Break DirFetchPostPeriod into:
27581 - DirFetchPeriod for fetching full directory,
27582 - StatusFetchPeriod for fetching running-routers,
27583 - DirPostPeriod for posting server descriptor,
27584 - RendPostPeriod for posting hidden service descriptors.
27585 - New log format in config:
27586 "Log minsev[-maxsev] stdout|stderr|syslog" or
27587 "Log minsev[-maxsev] file /var/foo"
27588 - DirPolicy config option, to let people reject incoming addresses
27589 from their dirserver.
27590 - "tor --list-fingerprint" will list your identity key fingerprint
27592 - Make tor --version --version dump the cvs Id of every file.
27593 - New 'MyFamily nick1,...' config option for a server to
27594 specify other servers that shouldn't be used in the same circuit
27595 with it. Only believed if nick1 also specifies us.
27596 - New 'NodeFamily nick1,nick2,...' config option for a client to
27597 specify nodes that it doesn't want to use in the same circuit.
27598 - New 'Redirectexit pattern address:port' config option for a
27599 server to redirect exit connections, e.g. to a local squid.
27600 - Add "pass" target for RedirectExit, to make it easier to break
27601 out of a sequence of RedirectExit rules.
27602 - Make the dirservers file obsolete.
27603 - Include a dir-signing-key token in directories to tell the
27604 parsing entity which key is being used to sign.
27605 - Remove the built-in bulky default dirservers string.
27606 - New config option "Dirserver %s:%d [fingerprint]", which can be
27607 repeated as many times as needed. If no dirservers specified,
27608 default to moria1,moria2,tor26.
27609 - Make 'Routerfile' config option obsolete.
27610 - Discourage people from setting their dirfetchpostperiod more often
27611 than once per minute.
27613 o Features (other):
27614 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
27615 get back to normal.)
27616 - Accept *:706 (silc) in default exit policy.
27617 - Implement new versioning format for post 0.1.
27618 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
27619 log more informatively.
27620 - Check clock skew for verified servers, but allow unverified
27621 servers and clients to have any clock skew.
27622 - Make sure the hidden service descriptors are at a random offset
27623 from each other, to hinder linkability.
27624 - Clients now generate a TLS cert too, in preparation for having
27625 them act more like real nodes.
27626 - Add a pure-C tor-resolve implementation.
27627 - Use getrlimit and friends to ensure we can reach MaxConn (currently
27628 1024) file descriptors.
27629 - Raise the max dns workers from 50 to 100.
27632 Changes in version 0.0.8.1 - 2004-10-13
27634 - Fix a seg fault that can be triggered remotely for Tor
27635 clients/servers with an open dirport.
27636 - Fix a rare assert trigger, where routerinfos for entries in
27637 our cpath would expire while we're building the path.
27638 - Fix a bug in OutboundBindAddress so it (hopefully) works.
27639 - Fix a rare seg fault for people running hidden services on
27640 intermittent connections.
27641 - Fix a bug in parsing opt keywords with objects.
27642 - Fix a stale pointer assert bug when a stream detaches and
27644 - Fix a string format vulnerability (probably not exploitable)
27645 in reporting stats locally.
27646 - Fix an assert trigger: sometimes launching circuits can fail
27647 immediately, e.g. because too many circuits have failed recently.
27648 - Fix a compile warning on 64 bit platforms.
27651 Changes in version 0.0.8 - 2004-08-25
27653 - Made our unit tests compile again on OpenBSD 3.5, and tor
27654 itself compile again on OpenBSD on a sparc64.
27655 - We were neglecting milliseconds when logging on win32, so
27656 everything appeared to happen at the beginning of each second.
27657 - Check directory signature _before_ you decide whether you're
27658 you're running an obsolete version and should exit.
27659 - Check directory signature _before_ you parse the running-routers
27660 list to decide who's running.
27661 - Check return value of fclose while writing to disk, so we don't
27662 end up with broken files when servers run out of disk space.
27663 - Port it to SunOS 5.9 / Athena
27664 - Fix two bugs in saving onion keys to disk when rotating, so
27665 hopefully we'll get fewer people using old onion keys.
27666 - Remove our mostly unused -- and broken -- hex_encode()
27667 function. Use base16_encode() instead. (Thanks to Timo Lindfors
27668 for pointing out this bug.)
27669 - Only pick and establish intro points after we've gotten a
27671 - Fix assert triggers: if the other side returns an address 0.0.0.0,
27672 don't put it into the client dns cache.
27673 - If a begin failed due to exit policy, but we believe the IP
27674 address should have been allowed, switch that router to exitpolicy
27675 reject *:* until we get our next directory.
27677 o Protocol changes:
27678 - 'Extend' relay cell payloads now include the digest of the
27679 intended next hop's identity key. Now we can verify that we're
27680 extending to the right router, and also extend to routers we
27681 hadn't heard of before.
27684 - Tor nodes can now act as relays (with an advertised ORPort)
27685 without being manually verified by the dirserver operators.
27686 - Uploaded descriptors of unverified routers are now accepted
27687 by the dirservers, and included in the directory.
27688 - Verified routers are listed by nickname in the running-routers
27689 list; unverified routers are listed as "$<fingerprint>".
27690 - We now use hash-of-identity-key in most places rather than
27691 nickname or addr:port, for improved security/flexibility.
27692 - AllowUnverifiedNodes config option to let circuits choose no-name
27693 routers in entry,middle,exit,introduction,rendezvous positions.
27694 Allow middle and rendezvous positions by default.
27695 - When picking unverified routers, skip those with low uptime and/or
27696 low bandwidth, depending on what properties you care about.
27697 - ClientOnly option for nodes that never want to become servers.
27698 - Directory caching.
27699 - "AuthoritativeDir 1" option for the official dirservers.
27700 - Now other nodes (clients and servers) will cache the latest
27701 directory they've pulled down.
27702 - They can enable their DirPort to serve it to others.
27703 - Clients will pull down a directory from any node with an open
27704 DirPort, and check the signature/timestamp correctly.
27705 - Authoritative dirservers now fetch directories from other
27706 authdirservers, to stay better synced.
27707 - Running-routers list tells who's down also, along with noting
27708 if they're verified (listed by nickname) or unverified (listed
27710 - Allow dirservers to serve running-router list separately.
27711 This isn't used yet.
27712 - You can now fetch $DIRURL/running-routers to get just the
27713 running-routers line, not the whole descriptor list. (But
27714 clients don't use this yet.)
27715 - Clients choose nodes proportional to advertised bandwidth.
27716 - Clients avoid using nodes with low uptime as introduction points.
27717 - Handle servers with dynamic IP addresses: don't just replace
27718 options->Address with the resolved one at startup, and
27719 detect our address right before we make a routerinfo each time.
27720 - 'FascistFirewall' option to pick dirservers and ORs on specific
27721 ports; plus 'FirewallPorts' config option to tell FascistFirewall
27722 which ports are open. (Defaults to 80,443)
27723 - Try other dirservers immediately if the one you try is down. This
27724 should tolerate down dirservers better now.
27725 - ORs connect-on-demand to other ORs
27726 - If you get an extend cell to an OR you're not connected to,
27727 connect, handshake, and forward the create cell.
27728 - The authoritative dirservers stay connected to everybody,
27729 and everybody stays connected to 0.0.7 servers, but otherwise
27730 clients/servers expire unused connections after 5 minutes.
27731 - When servers get a sigint, they delay 30 seconds (refusing new
27732 connections) then exit. A second sigint causes immediate exit.
27733 - File and name management:
27734 - Look for .torrc if no CONFDIR "torrc" is found.
27735 - If no datadir is defined, then choose, make, and secure ~/.tor
27737 - If torrc not found, exitpolicy reject *:*.
27738 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
27739 - If no nickname is defined, derive default from hostname.
27740 - Rename secret key files, e.g. identity.key -> secret_id_key,
27741 to discourage people from mailing their identity key to tor-ops.
27742 - Refuse to build a circuit before the directory has arrived --
27743 it won't work anyway, since you won't know the right onion keys
27745 - Parse tor version numbers so we can do an is-newer-than check
27746 rather than an is-in-the-list check.
27747 - New socks command 'resolve', to let us shim gethostbyname()
27749 - A 'tor_resolve' script to access the socks resolve functionality.
27750 - A new socks-extensions.txt doc file to describe our
27751 interpretation and extensions to the socks protocols.
27752 - Add a ContactInfo option, which gets published in descriptor.
27753 - Write tor version at the top of each log file
27754 - New docs in the tarball:
27756 - Document that you should proxy your SSL traffic too.
27757 - Log a warning if the user uses an unsafe socks variant, so people
27758 are more likely to learn about privoxy or socat.
27759 - Log a warning if you're running an unverified server, to let you
27760 know you might want to get it verified.
27761 - Change the default exit policy to reject the default edonkey,
27762 kazaa, gnutella ports.
27763 - Add replace_file() to util.[ch] to handle win32's rename().
27764 - Publish OR uptime in descriptor (and thus in directory) too.
27765 - Remember used bandwidth (both in and out), and publish 15-minute
27766 snapshots for the past day into our descriptor.
27767 - Be more aggressive about trying to make circuits when the network
27768 has changed (e.g. when you unsuspend your laptop).
27769 - Check for time skew on http headers; report date in response to
27771 - If the entrynode config line has only one node, don't pick it as
27773 - Add strict{entry|exit}nodes config options. If set to 1, then
27774 we refuse to build circuits that don't include the specified entry
27776 - OutboundBindAddress config option, to bind to a specific
27777 IP address for outgoing connect()s.
27778 - End truncated log entries (e.g. directories) with "[truncated]".
27781 Changes in version 0.0.7.3 - 2004-08-12
27782 o Stop dnsworkers from triggering an assert failure when you
27783 ask them to resolve the host "".
27786 Changes in version 0.0.7.2 - 2004-07-07
27787 o A better fix for the 0.0.0.0 problem, that will hopefully
27788 eliminate the remaining related assertion failures.
27791 Changes in version 0.0.7.1 - 2004-07-04
27792 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
27793 since internally we use 0.0.0.0 to signify "not yet resolved".
27796 Changes in version 0.0.7 - 2004-06-07
27797 o Fixes for crashes and other obnoxious bugs:
27798 - Fix an epipe bug: sometimes when directory connections failed
27799 to connect, we would give them a chance to flush before closing
27801 - When we detached from a circuit because of resolvefailed, we
27802 would immediately try the same circuit twice more, and then
27803 give up on the resolve thinking we'd tried three different
27805 - Limit the number of intro circuits we'll attempt to build for a
27806 hidden service per 15-minute period.
27807 - Check recommended-software string *early*, before actually parsing
27808 the directory. Thus we can detect an obsolete version and exit,
27809 even if the new directory format doesn't parse.
27810 o Fixes for security bugs:
27811 - Remember which nodes are dirservers when you startup, and if a
27812 random OR enables his dirport, don't automatically assume he's
27813 a trusted dirserver.
27815 - Directory connections were asking the wrong poll socket to
27816 start writing, and not asking themselves to start writing.
27817 - When we detached from a circuit because we sent a begin but
27818 didn't get a connected, we would use it again the first time;
27819 but after that we would correctly switch to a different one.
27820 - Stop warning when the first onion decrypt attempt fails; they
27821 will sometimes legitimately fail now that we rotate keys.
27822 - Override unaligned-access-ok check when $host_cpu is ia64 or
27823 arm. Apparently they allow it but the kernel whines.
27824 - Dirservers try to reconnect periodically too, in case connections
27826 - Fix some memory leaks in directory servers.
27827 - Allow backslash in Win32 filenames.
27828 - Made Tor build complain-free on FreeBSD, hopefully without
27829 breaking other BSD builds. We'll see.
27830 - Check directory signatures based on name of signer, not on whom
27831 we got the directory from. This will let us cache directories more
27833 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
27836 - Doxygen markup on all functions and global variables.
27837 - Make directory functions update routerlist, not replace it. So
27838 now directory disagreements are not so critical a problem.
27839 - Remove the upper limit on number of descriptors in a dirserver's
27840 directory (not that we were anywhere close).
27841 - Allow multiple logfiles at different severity ranges.
27842 - Allow *BindAddress to specify ":port" rather than setting *Port
27843 separately. Allow multiple instances of each BindAddress config
27844 option, so you can bind to multiple interfaces if you want.
27845 - Allow multiple exit policy lines, which are processed in order.
27846 Now we don't need that huge line with all the commas in it.
27847 - Enable accept/reject policies on SOCKS connections, so you can bind
27848 to 0.0.0.0 but still control who can use your OP.
27849 - Updated the man page to reflect these features.
27852 Changes in version 0.0.6.2 - 2004-05-16
27853 o Our integrity-checking digest was checking only the most recent cell,
27854 not the previous cells like we'd thought.
27855 Thanks to Stefan Mark for finding the flaw!
27858 Changes in version 0.0.6.1 - 2004-05-06
27859 o Fix two bugs in our AES counter-mode implementation (this affected
27860 onion-level stream encryption, but not TLS-level). It turns
27861 out we were doing something much more akin to a 16-character
27862 polyalphabetic cipher. Oops.
27863 Thanks to Stefan Mark for finding the flaw!
27864 o Retire moria3 as a directory server, and add tor26 as a directory
27868 Changes in version 0.0.6 - 2004-05-02
27870 - Hidden services and rendezvous points are implemented. Go to
27871 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
27872 hidden services. (This only works via a socks4a proxy such as
27873 Privoxy, and currently it's quite slow.)
27874 - We now rotate link (tls context) keys and onion keys.
27875 - CREATE cells now include oaep padding, so you can tell
27876 if you decrypted them correctly.
27877 - Retry stream correctly when we fail to connect because of
27878 exit-policy-reject (should try another) or can't-resolve-address.
27879 - When we hup a dirserver and we've *removed* a server from the
27880 approved-routers list, now we remove that server from the
27881 in-memory directories too.
27882 - Add bandwidthburst to server descriptor.
27883 - Directories now say which dirserver signed them.
27884 - Use a tor_assert macro that logs failed assertions too.
27885 - Since we don't support truncateds much, don't bother sending them;
27886 just close the circ.
27887 - Fetch randomness from /dev/urandom better (not via fopen/fread)
27888 - Better debugging for tls errors
27889 - Set Content-Type on the directory and hidserv descriptor.
27890 - Remove IVs from cipher code, since AES-ctr has none.
27892 - Fix an assert trigger for exit nodes that's been plaguing us since
27893 the days of 0.0.2prexx (thanks weasel!)
27894 - Fix a bug where we were closing tls connections intermittently.
27895 It turns out openssl keeps its errors around -- so if an error
27896 happens, and you don't ask about it, and then another openssl
27897 operation happens and succeeds, and you ask if there was an error,
27898 it tells you about the first error.
27899 - Fix a bug that's been lurking since 27 may 03 (!)
27900 When passing back a destroy cell, we would use the wrong circ id.
27901 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
27902 - Some versions of openssl have an SSL_pending function that erroneously
27903 returns bytes when there is a non-application record pending.
27904 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
27905 o We were using an array of length zero in a few places.
27906 o Win32's gethostbyname can't resolve an IP to an IP.
27907 o Win32's close can't close a socket.
27908 o Handle windows socket errors correctly.
27910 - check for <sys/limits.h> so we build on FreeBSD again, and
27911 <machine/limits.h> for NetBSD.
27914 Changes in version 0.0.5 - 2004-03-30
27915 o Install torrc as torrc.sample -- we no longer clobber your
27917 o Fix mangled-state bug in directory fetching (was causing sigpipes).
27918 o Only build circuits after we've fetched the directory: clients were
27919 using only the directory servers before they'd fetched a directory.
27920 This also means longer startup time; so it goes.
27921 o Fix an assert trigger where an OP would fail to handshake, and we'd
27922 expect it to have a nickname.
27923 o Work around a tsocks bug: do a socks reject when AP connection dies
27924 early, else tsocks goes into an infinite loop.
27925 o Hold socks connection open until reply is flushed (if possible)
27926 o Make exit nodes resolve IPs to IPs immediately, rather than asking
27927 the dns farm to do it.
27928 o Fix c99 aliasing warnings in rephist.c
27929 o Don't include server descriptors that are older than 24 hours in the
27931 o Give socks 'reject' replies their whole 15s to attempt to flush,
27932 rather than seeing the 60s timeout and assuming the flush had failed.
27933 o Clean automake droppings from the cvs repository
27934 o Add in a 'notice' log level for things the operator should hear
27935 but that aren't warnings
27938 Changes in version 0.0.4 - 2004-03-26
27939 o When connecting to a dirserver or OR and the network is down,
27943 Changes in version 0.0.3 - 2004-03-26
27944 o Warn and fail if server chose a nickname with illegal characters
27945 o Port to Solaris and Sparc:
27946 - include missing header fcntl.h
27947 - have autoconf find -lsocket -lnsl automatically
27948 - deal with hardware word alignment
27949 - make uname() work (solaris has a different return convention)
27950 - switch from using signal() to sigaction()
27951 o Preliminary work on reputation system:
27952 - Keep statistics on success/fail of connect attempts; they're published
27953 by kill -USR1 currently.
27954 - Add a RunTesting option to try to learn link state by creating test
27955 circuits, even when SocksPort is off.
27956 - Remove unused open circuits when there are too many.
27959 Changes in version 0.0.2 - 2004-03-19
27960 - Include strlcpy and strlcat for safer string ops
27961 - define INADDR_NONE so we compile (but still not run) on solaris
27964 Changes in version 0.0.2pre27 - 2004-03-14
27966 - Allow internal tor networks (we were rejecting internal IPs,
27967 now we allow them if they're set explicitly).
27968 - And fix a few endian issues.
27971 Changes in version 0.0.2pre26 - 2004-03-14
27973 - If a stream times out after 15s without a connected cell, don't
27974 try that circuit again: try a new one.
27975 - Retry streams at most 4 times. Then give up.
27976 - When a dirserver gets a descriptor from an unknown router, it
27977 logs its fingerprint (so the dirserver operator can choose to
27978 accept it even without mail from the server operator).
27979 - Inform unapproved servers when we reject their descriptors.
27980 - Make tor build on Windows again. It works as a client, who knows
27982 - Clearer instructions in the torrc for how to set up a server.
27983 - Be more efficient about reading fd's when our global token bucket
27984 (used for rate limiting) becomes empty.
27986 - Stop asserting that computers always go forward in time. It's
27988 - When we sent a cell (e.g. destroy) and then marked an OR connection
27989 expired, we might close it before finishing a flush if the other
27990 side isn't reading right then.
27991 - Don't allow dirservers to start if they haven't defined
27992 RecommendedVersions
27993 - We were caching transient dns failures. Oops.
27994 - Prevent servers from publishing an internal IP as their address.
27995 - Address a strcat vulnerability in circuit.c
27998 Changes in version 0.0.2pre25 - 2004-03-04
28000 - Put the OR's IP in its router descriptor, not its fqdn. That way
28001 we'll stop being stalled by gethostbyname for nodes with flaky dns,
28004 - If the user typed in an address that didn't resolve, the server
28008 Changes in version 0.0.2pre24 - 2004-03-03
28010 - Fix an assertion failure in dns.c, where we were trying to dequeue
28011 a pending dns resolve even if it wasn't pending
28012 - Fix a spurious socks5 warning about still trying to write after the
28013 connection is finished.
28014 - Hold certain marked_for_close connections open until they're finished
28015 flushing, rather than losing bytes by closing them too early.
28016 - Correctly report the reason for ending a stream
28017 - Remove some duplicate calls to connection_mark_for_close
28018 - Put switch_id and start_daemon earlier in the boot sequence, so it
28019 will actually try to chdir() to options.DataDirectory
28020 - Make 'make test' exit(1) if a test fails; fix some unit tests
28021 - Make tor fail when you use a config option it doesn't know about,
28022 rather than warn and continue.
28023 - Make --version work
28024 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
28027 Changes in version 0.0.2pre23 - 2004-02-29
28029 - Print a statement when the first circ is finished, so the user
28030 knows it's working.
28031 - If a relay cell is unrecognized at the end of the circuit,
28032 send back a destroy. (So attacks to mutate cells are more
28034 - New config option 'excludenodes' to avoid certain nodes for circuits.
28035 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
28036 so you can collect coredumps there.
28038 - Fix a bug in tls flushing where sometimes data got wedged and
28039 didn't flush until more data got sent. Hopefully this bug was
28040 a big factor in the random delays we were seeing.
28041 - Make 'connected' cells include the resolved IP, so the client
28042 dns cache actually gets populated.
28043 - Disallow changing from ORPort=0 to ORPort>0 on hup.
28044 - When we time-out on a stream and detach from the circuit, send an
28045 end cell down it first.
28046 - Only warn about an unknown router (in exitnodes, entrynodes,
28047 excludenodes) after we've fetched a directory.
28050 Changes in version 0.0.2pre22 - 2004-02-26
28052 - Servers publish less revealing uname information in descriptors.
28053 - More memory tracking and assertions, to crash more usefully when
28055 - If the default torrc isn't there, just use some default defaults.
28056 Plus provide an internal dirservers file if they don't have one.
28057 - When the user tries to use Tor as an http proxy, give them an http
28058 501 failure explaining that we're a socks proxy.
28059 - Dump a new router.desc on hup, to help confused people who change
28060 their exit policies and then wonder why router.desc doesn't reflect
28062 - Clean up the generic tor.sh init script that we ship with.
28064 - If the exit stream is pending on the resolve, and a destroy arrives,
28065 then the stream wasn't getting removed from the pending list. I
28066 think this was the one causing recent server crashes.
28067 - Use a more robust poll on OSX 10.3, since their poll is flaky.
28068 - When it couldn't resolve any dirservers, it was useless from then on.
28069 Now it reloads the RouterFile (or default dirservers) if it has no
28071 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
28072 many users don't even *have* a /usr/local/sbin/.
28075 Changes in version 0.0.2pre21 - 2004-02-18
28077 - There's a ChangeLog file that actually reflects the changelog.
28078 - There's a 'torify' wrapper script, with an accompanying
28079 tor-tsocks.conf, that simplifies the process of using tsocks for
28080 tor. It even has a man page.
28081 - The tor binary gets installed to sbin rather than bin now.
28082 - Retry streams where the connected cell hasn't arrived in 15 seconds
28083 - Clean up exit policy handling -- get the default out of the torrc,
28084 so we can update it without forcing each server operator to fix
28086 - Allow imaps and pop3s in default exit policy
28088 - Prevent picking middleman nodes as the last node in the circuit
28091 Changes in version 0.0.2pre20 - 2004-01-30
28093 - We now have a deb package, and it's in debian unstable. Go to
28094 it, apt-getters. :)
28095 - I've split the TotalBandwidth option into BandwidthRate (how many
28096 bytes per second you want to allow, long-term) and
28097 BandwidthBurst (how many bytes you will allow at once before the cap
28098 kicks in). This better token bucket approach lets you, say, set
28099 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
28100 performance while not exceeding your monthly bandwidth quota.
28101 - Push out a tls record's worth of data once you've got it, rather
28102 than waiting until you've read everything waiting to be read. This
28103 may improve performance by pipelining better. We'll see.
28104 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
28105 from failed circuits (if they haven't been connected yet) and attach
28107 - Expire old streams that haven't managed to connect. Some day we'll
28108 have them reattach to new circuits instead.
28111 - Fix several memory leaks that were causing servers to become bloated
28113 - Fix a few very rare assert triggers. A few more remain.
28114 - Setuid to User _before_ complaining about running as root.
28117 Changes in version 0.0.2pre19 - 2004-01-07
28119 - Fix deadlock condition in dns farm. We were telling a child to die by
28120 closing the parent's file descriptor to him. But newer children were
28121 inheriting the open file descriptor from the parent, and since they
28122 weren't closing it, the socket never closed, so the child never read
28123 eof, so he never knew to exit. Similarly, dns workers were holding
28124 open other sockets, leading to all sorts of chaos.
28125 - New cleaner daemon() code for forking and backgrounding.
28126 - If you log to a file, it now prints an entry at the top of the
28127 logfile so you know it's working.
28128 - The onionskin challenge length was 30 bytes longer than necessary.
28129 - Started to patch up the spec so it's not quite so out of date.
28132 Changes in version 0.0.2pre18 - 2004-01-02
28134 - Fix endian issues with the 'integrity' field in the relay header.
28135 - Fix a potential bug where connections in state
28136 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
28139 Changes in version 0.0.2pre17 - 2003-12-30
28141 - Made --debuglogfile (or any second log file, actually) work.
28142 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
28143 adversary could force us into an infinite loop.
28146 - Each onionskin handshake now includes a hash of the computed key,
28147 to prove the server's identity and help perfect forward secrecy.
28148 - Changed cell size from 256 to 512 bytes (working toward compatibility
28150 - Changed cell length to 2 bytes, and moved it to the relay header.
28151 - Implemented end-to-end integrity checking for the payloads of
28153 - Separated streamid from 'recognized' (otherwise circuits will get
28154 messed up when we try to have streams exit from the middle). We
28155 use the integrity-checking to confirm that a cell is addressed to
28157 - Randomize the initial circid and streamid values, so an adversary who
28158 breaks into a node can't learn how many circuits or streams have
28162 Changes in version 0.0.2pre16 - 2003-12-14
28164 - Fixed a bug that made HUP trigger an assert
28165 - Fixed a bug where a circuit that immediately failed wasn't being
28166 counted as a failed circuit in counting retries.
28169 - Now we close the circuit when we get a truncated cell: otherwise we're
28170 open to an anonymity attack where a bad node in the path truncates
28171 the circuit and then we open streams at him.
28172 - Add port ranges to exit policies
28173 - Add a conservative default exit policy
28174 - Warn if you're running tor as root
28175 - on HUP, retry OR connections and close/rebind listeners
28176 - options.EntryNodes: try these nodes first when picking the first node
28177 - options.ExitNodes: if your best choices happen to include any of
28178 your preferred exit nodes, you choose among just those preferred
28180 - options.ExcludedNodes: nodes that are never picked in path building
28183 Changes in version 0.0.2pre15 - 2003-12-03
28184 o Robustness and bugfixes:
28185 - Sometimes clients would cache incorrect DNS resolves, which would
28186 really screw things up.
28187 - An OP that goes offline would slowly leak all its sockets and stop
28189 - A wide variety of bugfixes in exit node selection, exit policy
28190 handling, and processing pending streams when a new circuit is
28192 - Pick nodes for a path only from those the directory says are up
28193 - Choose randomly from all running dirservers, not always the first one
28194 - Increase allowed http header size for directory fetch.
28195 - Stop writing to stderr (if we're daemonized it will be closed).
28196 - Enable -g always, so cores will be more useful to me.
28197 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
28200 - Wrote a man page. It lists commonly used options.
28203 - Change default loglevel to warn.
28204 - Make PidFile default to null rather than littering in your CWD.
28205 - OnionRouter config option is now obsolete. Instead it just checks
28207 - Moved to a single unified torrc file for both clients and servers.
28210 Changes in version 0.0.2pre14 - 2003-11-29
28211 o Robustness and bugfixes:
28212 - Force the admin to make the DataDirectory himself
28213 - to get ownership/permissions right
28214 - so clients no longer make a DataDirectory and then never use it
28215 - fix bug where a client who was offline for 45 minutes would never
28216 pull down a directory again
28217 - fix (or at least hide really well) the dns assert bug that was
28218 causing server crashes
28219 - warnings and improved robustness wrt clockskew for certs
28220 - use the native daemon(3) to daemonize, when available
28221 - exit if bind() fails
28222 - exit if neither socksport nor orport is defined
28223 - include our own tor_timegm (Win32 doesn't have its own)
28224 - bugfix for win32 with lots of connections
28225 - fix minor bias in PRNG
28226 - make dirserver more robust to corrupt cached directory
28229 - Wrote the design document (woo)
28231 o Circuit building and exit policies:
28232 - Circuits no longer try to use nodes that the directory has told them
28234 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
28235 bitcounts (18.0.0.0/8).
28236 - Make AP connections standby for a circuit if no suitable circuit
28237 exists, rather than failing
28238 - Circuits choose exit node based on addr/port, exit policies, and
28239 which AP connections are standing by
28240 - Bump min pathlen from 2 to 3
28241 - Relay end cells have a payload to describe why the stream ended.
28242 - If the stream failed because of exit policy, try again with a new
28244 - Clients have a dns cache to remember resolved addresses.
28245 - Notice more quickly when we have no working circuits
28248 - APPort is now called SocksPort
28249 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
28251 - RecommendedVersions is now a config variable rather than
28252 hardcoded (for dirservers)
28253 - Reloads config on HUP
28254 - Usage info on -h or --help
28255 - If you set User and Group config vars, it'll setu/gid to them.
28257 Changes in version 0.0.2pre13 - 2003-10-19
28258 o General stability:
28259 - SSL_write no longer fails when it returns WANTWRITE and the number
28260 of bytes in the buf has changed by the next SSL_write call.
28261 - Fix segfault fetching directory when network is down
28262 - Fix a variety of minor memory leaks
28263 - Dirservers reload the fingerprints file on HUP, so I don't have
28264 to take down the network when I approve a new router
28265 - Default server config file has explicit Address line to specify fqdn
28268 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
28269 - Make listener connections not ever alloc bufs
28271 o Autoconf improvements:
28272 - don't clobber an external CFLAGS in ./configure
28273 - Make install now works
28274 - create var/lib/tor on make install
28275 - autocreate a tor.sh initscript to help distribs
28276 - autocreate the torrc and sample-server-torrc with correct paths
28278 o Log files and Daemonizing now work:
28279 - If --DebugLogFile is specified, log to it at -l debug
28280 - If --LogFile is specified, use it instead of commandline
28281 - If --RunAsDaemon is set, tor forks and backgrounds on startup