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.3.5.11 - 2020-07-09
6 Tor 0.3.5.11 backports fixes from later tor releases, including several
7 usability, portability, and reliability fixes.
9 This release also fixes TROVE-2020-001, a medium-severity denial of
10 service vulnerability affecting all versions of Tor when compiled with
11 the NSS encryption library. (This is not the default configuration.)
12 Using this vulnerability, an attacker could cause an affected Tor
13 instance to crash remotely. This issue is also tracked as CVE-2020-
14 15572. Anybody running a version of Tor built with the NSS library
15 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
18 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
19 - Fix a crash due to an out-of-bound memory access when Tor is
20 compiled with NSS support. Fixes bug 33119; bugfix on
21 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
24 o Major bugfixes (DoS defenses, bridges, pluggable transport, backport from 0.4.3.4-rc):
25 - Fix a bug that was preventing DoS defenses from running on bridges
26 with a pluggable transport. Previously, the DoS subsystem was not
27 given the transport name of the client connection, thus failed to
28 find the GeoIP cache entry for that client address. Fixes bug
29 33491; bugfix on 0.3.3.2-alpha.
31 o Minor features (testing, backport from 0.4.3.4-rc):
32 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
33 variable to specify a list of space-separated test cases that
34 should not be executed. We will use this to disable certain tests
35 that are failing on Appveyor because of mismatched OpenSSL
36 libraries. Part of ticket 33643.
38 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
39 - Use the correct 64-bit printf format when compiling with MINGW on
40 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
42 o Minor bugfix (relay, configuration, backport from 0.4.3.3-alpha):
43 - Warn if the ContactInfo field is not set, and tell the relay
44 operator that not having a ContactInfo field set might cause their
45 relay to get rejected in the future. Fixes bug 33361; bugfix
48 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
49 - Resume use of preemptively-built circuits when UseEntryGuards is set
50 to 0. We accidentally disabled this feature with that config
51 setting, leading to slower load times. Fixes bug 34303; bugfix
54 o Minor bugfixes (compiler compatibility, backport from 0.4.3.5):
55 - Avoid compiler warnings from Clang 10 related to the use of GCC-
56 style "/* falls through */" comments. Both Clang and GCC allow
57 __attribute__((fallthrough)) instead, so that's what we're using
58 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
60 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
61 - Fix a compiler warning on platforms with 32-bit time_t values.
62 Fixes bug 40028; bugfix on 0.3.2.8-rc.
64 o Minor bugfixes (embedded Tor, backport from 0.4.3.1-alpha):
65 - When starting Tor any time after the first time in a process,
66 register the thread in which it is running as the main thread.
67 Previously, we only did this on Windows, which could lead to bugs
68 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
71 o Minor bugfixes (key portability, backport from 0.4.3.4-rc):
72 - When reading PEM-encoded key data, tolerate CRLF line-endings even
73 if we are not running on Windows. Previously, non-Windows hosts
74 would reject these line-endings in certain positions, making
75 certain key files hard to move from one host to another. Fixes bug
76 33032; bugfix on 0.3.5.1-alpha.
78 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
79 - Downgrade a noisy log message that could occur naturally when
80 receiving an extrainfo document that we no longer want. Fixes bug
81 16016; bugfix on 0.2.6.3-alpha.
83 o Minor bugfixes (onion service v3, client, backport from 0.4.3.3-alpha):
84 - Remove a BUG() warning that would cause a stack trace if an onion
85 service descriptor was freed while we were waiting for a
86 rendezvous circuit to complete. Fixes bug 28992; bugfix
89 o Testing (CI, backport from 0.4.3.4-rc):
90 - In our Appveyor Windows CI, copy required DLLs to test and app
91 directories, before running tor's tests. This ensures that tor.exe
92 and test*.exe use the correct version of each DLL. This fix is not
93 required, but we hope it will avoid DLL search issues in future.
94 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
95 - On Appveyor, skip the crypto/openssl_version test, which is
96 failing because of a mismatched library installation. Fix
100 Changes in version 0.3.5.10 - 2020-03-18
101 Tor 0.3.5.10 backports many fixes from later Tor releases, including a
102 fix for TROVE-2020-002, a major denial-of-service vulnerability that
103 affected all released Tor instances since 0.2.1.5-alpha. Using this
104 vulnerability, an attacker could cause Tor instances to consume a huge
105 amount of CPU, disrupting their operations for several seconds or
106 minutes. This attack could be launched by anybody against a relay, or
107 by a directory cache against any client that had connected to it. The
108 attacker could launch this attack as much as they wanted, thereby
109 disrupting service or creating patterns that could aid in traffic
110 analysis. This issue was found by OSS-Fuzz, and is also tracked
113 We do not have reason to believe that this attack is currently being
114 exploited in the wild, but nonetheless we advise everyone to upgrade
115 as soon as packages are available.
117 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
118 - Fix a denial-of-service bug that could be used by anyone to
119 consume a bunch of CPU on any Tor relay or authority, or by
120 directories to consume a bunch of CPU on clients or hidden
121 services. Because of the potential for CPU consumption to
122 introduce observable timing patterns, we are treating this as a
123 high-severity security issue. Fixes bug 33119; bugfix on
124 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
125 as TROVE-2020-002 and CVE-2020-10592.
127 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
128 - Correct how we use libseccomp. Particularly, stop assuming that
129 rules are applied in a particular order or that more rules are
130 processed after the first match. Neither is the case! In
131 libseccomp <2.4.0 this lead to some rules having no effect.
132 libseccomp 2.4.0 changed how rules are generated, leading to a
133 different ordering, which in turn led to a fatal crash during
134 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
137 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
138 - Stop allowing failures on the Travis CI stem tests job. It looks
139 like all the stem hangs we were seeing before are now fixed.
142 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
143 - Lowercase the configured value of BridgeDistribution before adding
144 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
146 o Minor bugfixes (crash, backport from 0.4.2.4-rc):
147 - When running Tor with an option like --verify-config or
148 --dump-config that does not start the event loop, avoid crashing
149 if we try to exit early because of an error. Fixes bug 32407;
150 bugfix on 0.3.3.1-alpha.
152 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
153 - If we encounter a bug when flushing a buffer to a TLS connection,
154 only log the bug once per invocation of the Tor process.
155 Previously we would log with every occurrence, which could cause
156 us to run out of disk space. Fixes bug 33093; bugfix
159 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
160 - Fix an assertion failure that could result from a corrupted
161 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
162 bugfix on 0.3.3.1-alpha. This issue is also tracked
165 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
166 - Fix a syntax warning given by newer versions of Rust that was
167 creating problems for our continuous integration. Fixes bug 33212;
168 bugfix on 0.3.5.1-alpha.
170 o Testing (backport from 0.4.3.1-alpha):
171 - Re-enable the Travis CI macOS Chutney build, but don't let it
172 prevent the Travis job from finishing. (The Travis macOS jobs are
173 slow, so we don't want to have it delay the whole CI process.)
175 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
176 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
177 fix the sandbox errors in 32722. Closes ticket 32240.
179 o Testing (continuous integration, backport from 0.4.3.1-alpha):
180 - Use zstd in our Travis Linux builds. Closes ticket 32242.
182 o Testing (Travis CI, backport from 0.4.3.3-alpha):
183 - Remove a redundant distcheck job. Closes ticket 33194.
184 - Sort the Travis jobs in order of speed: putting the slowest jobs
185 first takes full advantage of Travis job concurrency. Closes
187 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
188 previously configured to fast_finish (which requires
189 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
190 tool to produce detailed diagnostic output. Closes ticket 32792.
193 Changes in version 0.3.5.9 - 2019-12-09
194 Tor 0.3.5.9 backports serveral fixes from later releases, including
195 several that affect bridge users, relay stability, onion services,
198 o Directory authority changes (backport from 0.4.1.5):
199 - The directory authority "dizum" has a new IP address. Closes
202 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
203 - Consider our directory information to have changed when our list
204 of bridges changes. Previously, Tor would not re-compute the
205 status of its directory information when bridges changed, and
206 therefore would not realize that it was no longer able to build
207 circuits. Fixes part of bug 29875.
208 - Do not count previously configured working bridges towards our
209 total of working bridges. Previously, when Tor's list of bridges
210 changed, it would think that the old bridges were still usable,
211 and delay fetching router descriptors for the new ones. Fixes part
212 of bug 29875; bugfix on 0.3.0.1-alpha.
214 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
215 - When considering upgrading circuits from "waiting for guard" to
216 "open", always ignore circuits that are marked for close. Otherwise,
217 we can end up in the situation where a subsystem is notified that
218 a closing circuit has just opened, leading to undesirable
219 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
221 o Major bugfixes (NSS, relay, backport from 0.4.0.4-rc):
222 - When running with NSS, disable TLS 1.2 ciphersuites that use
223 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
224 these ciphersuites don't work -- which caused relays to fail to
225 handshake with one another when these ciphersuites were enabled.
226 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
228 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
229 - Properly clean up the introduction point map when circuits change
230 purpose from onion service circuits to pathbias, measurement, or
231 other circuit types. This should fix some service-side instances
232 of introduction point failure. Fixes bug 29034; bugfix
235 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
236 - Fix an unreachable bug in which an introduction point could try to
237 send an INTRODUCE_ACK with a status code that Trunnel would refuse
238 to encode, leading the relay to assert(). We've consolidated the
239 ABI values into Trunnel now. Fixes bug 30454; bugfix
241 - Clients can now handle unknown status codes from INTRODUCE_ACK
242 cells. (The NACK behavior will stay the same.) This will allow us
243 to extend status codes in the future without breaking the normal
244 client behavior. Fixes another part of bug 30454; bugfix
247 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
248 - Stop ignoring torrc options after an %include directive, when the
249 included directory ends with a file that does not contain any
250 config options (but does contain comments or whitespace). Fixes
251 bug 31408; bugfix on 0.3.1.1-alpha.
253 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
254 - Onion services now always use the exact number of intro points
255 configured with the HiddenServiceNumIntroductionPoints option (or
256 fewer if nodes are excluded). Before, a service could sometimes
257 pick more intro points than configured. Fixes bug 31548; bugfix
260 o Minor features (address selection, backport from 0.4.0.3-alpha):
261 - Treat the subnet 100.64.0.0/10 as public for some purposes;
262 private for others. This subnet is the RFC 6598 (Carrier Grade
263 NAT) IP range, and is deployed by many ISPs as an alternative to
264 RFC 1918 that does not break existing internal networks. Tor now
265 blocks SOCKS and control ports on these addresses and warns users
266 if client ports or ExtORPorts are listening on a RFC 6598 address.
267 Closes ticket 28525. Patch by Neel Chauhan.
269 o Minor features (bandwidth authority, backport from 0.4.0.4-rc):
270 - Make bandwidth authorities ignore relays that are reported in the
271 bandwidth file with the flag "vote=0". This change allows us to
272 report unmeasured relays for diagnostic reasons without including
273 their bandwidth in the bandwidth authorities' vote. Closes
276 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
277 - Add a "--list-modules" command to print a list of which compile-
278 time modules are enabled. Closes ticket 30452.
280 o Minor features (continuous integration, backport from 0.4.0.4-rc):
281 - On Travis Rust builds, cleanup Rust registry and refrain from
282 caching the "target/" directory to speed up builds. Resolves
285 o Minor features (continuous integration, backport from 0.4.0.5):
286 - In Travis, tell timelimit to use stem's backtrace signals, and
287 launch python directly from timelimit, so python receives the
288 signals from timelimit, rather than make. Closes ticket 30117.
290 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
291 - Remove sudo configuration lines from .travis.yml as they are no
292 longer needed with current Travis build environment. Resolves
295 o Minor features (continuous integration, backport from 0.4.1.4-rc):
296 - Our Travis configuration now uses Chutney to run some network
297 integration tests automatically. Closes ticket 29280.
299 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
300 - When building on Appveyor and Travis, pass the "-k" flag to make,
301 so that we are informed of all compilation failures, not just the
302 first one or two. Closes ticket 31372.
304 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
305 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
306 in December 2018 (of which ~122 were still functional), with a
307 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
308 in June 2019. Closes ticket 28795.
310 o Minor features (geoip, backport from 0.4.2.5):
311 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
312 Country database. Closes ticket 32685.
314 o Minor features (NSS, diagnostic, backport from 0.4.0.4-rc):
315 - Try to log an error from NSS (if there is any) and a more useful
316 description of our situation if we are using NSS and a call to
317 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
319 o Minor features (stem tests, backport from 0.4.2.1-alpha):
320 - Change "make test-stem" so it only runs the stem tests that use
321 tor. This change makes test-stem faster and more reliable. Closes
324 o Minor bugfixes (security, backport from 0.4.0.4-rc):
325 - Verify in more places that we are not about to create a buffer
326 with more than INT_MAX bytes, to avoid possible OOB access in the
327 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
328 fixed by Tobias Stoeckmann.
329 - Fix a potential double free bug when reading huge bandwidth files.
330 The issue is not exploitable in the current Tor network because
331 the vulnerable code is only reached when directory authorities
332 read bandwidth files, but bandwidth files come from a trusted
333 source (usually the authorities themselves). Furthermore, the
334 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
335 which are not used by any of the current authorities. Fixes bug
336 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
339 o Minor bugfix (continuous integration, backport from 0.4.0.4-rc):
340 - Reset coverage state on disk after Travis CI has finished. This
341 should prevent future coverage merge errors from causing the test
342 suite for the "process" subsystem to fail. The process subsystem
343 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
345 - Terminate test-stem if it takes more than 9.5 minutes to run.
346 (Travis terminates the job after 10 minutes of no output.)
347 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
349 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
350 - Avoid spurious errors when Appveyor CI fails before the install step.
351 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
353 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
354 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
355 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
357 o Minor bugfixes (C correctness, backport from 0.4.0.4-rc):
358 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
359 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
362 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
363 - Fix a logic error that prevented the SessionGroup sub-option from
364 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
366 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
367 - Fix a BUG() assertion that occurs within a very small race window
368 between when a client intro circuit opens and when its descriptor
369 gets cleaned up from the cache. The circuit is now closed early,
370 which will trigger a re-fetch of the descriptor and continue the
371 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
373 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
374 - Don't believe clock skew results from NETINFO cells that appear to
375 arrive before we sent the VERSIONS cells they are responding to.
376 Previously, we would accept them up to 3 minutes "in the past".
377 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
379 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
380 - Fix a compilation warning on Windows about casting a function
381 pointer for GetTickCount64(). Fixes bug 31374; bugfix
384 o Minor bugfixes (compilation, backport from 0.4.0.2-alpha):
385 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
386 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
388 o Minor bugfixes (compilation, backport from 0.4.1.5):
389 - Avoid using labs() on time_t, which can cause compilation warnings
390 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
392 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
393 - Suppress spurious float-conversion warnings from GCC when calling
394 floating-point classifier functions on FreeBSD. Fixes part of bug
395 31687; bugfix on 0.3.1.5-alpha.
397 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
398 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
399 due to missing declarations of abort(), and prevent other such
400 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
402 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
403 - Fix a bug that prevented us from supporting SOCKS5 proxies that
404 want authentication along with configured (but unused!)
405 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
407 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
408 - Avoid trying to read data from closed connections, which can cause
409 needless loops in Libevent and infinite loops in Shadow. Fixes bug
410 30344; bugfix on 0.1.1.1-alpha.
412 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
413 - Allow the test-stem job to fail in Travis, because it sometimes
414 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
415 - Skip test_rebind on macOS in Travis, because it is unreliable on
416 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
417 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
418 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
420 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
421 - Avoid a set of possible code paths that could try to use freed
422 memory in routerlist_free() while Tor was exiting. Fixes bug
423 31003; bugfix on 0.1.2.2-alpha.
425 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
426 - Stop crashing after parsing an unknown descriptor purpose
427 annotation. We think this bug can only be triggered by modifying a
428 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
430 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
431 - Move the "bandwidth-file-headers" line in directory authority
432 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
435 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
436 - On abort, try harder to flush the output buffers of log messages.
437 On some platforms (macOS), log messages could be discarded when
438 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
439 - Report the tor version whenever an assertion fails. Previously, we
440 only reported the Tor version on some crashes, and some non-fatal
441 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
443 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
444 - When extracting an IPv6 address from a PF-based proxy, verify that
445 we are actually configured to receive an IPv6 address, and log an
446 internal error if not. Fixes part of bug 31687; bugfix
449 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
450 - When tor is missing descriptors for some primary entry guards,
451 make the log message less alarming. It's normal for descriptors to
452 expire, as long as tor fetches new ones soon after. Fixes bug
453 31657; bugfix on 0.3.3.1-alpha.
455 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
456 - Avoid logging that we are relaxing a circuit timeout when that
457 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
459 o Minor bugfixes (logging, backport from 0.4.0.3-alpha):
460 - Correct a misleading error message when IPv4Only or IPv6Only is
461 used but the resolved address can not be interpreted as an address
462 of the specified IP version. Fixes bug 13221; bugfix on
463 0.2.3.9-alpha. Patch from Kris Katterjohn.
464 - Log the correct port number for listening sockets when "auto" is
465 used to let Tor pick the port number. Previously, port 0 was
466 logged instead of the actual port number. Fixes bug 29144; bugfix
467 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
468 - Stop logging a BUG() warning when Tor is waiting for exit
469 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
471 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
472 - Do not log a warning when running with an OpenSSL version other
473 than the one Tor was compiled with, if the two versions should be
474 compatible. Previously, we would warn whenever the version was
475 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
477 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
478 - Change log level of message "Hash of session info was not as
479 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
482 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
483 - Rate-limit our the logging message about the obsolete .exit
484 notation. Previously, there was no limit on this warning, which
485 could potentially be triggered many times by a hostile website.
486 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
488 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
489 - Do not log a nonfatal assertion failure when receiving a VERSIONS
490 cell on a connection using the obsolete v1 link protocol. Log a
491 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
493 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
494 - Reset the periodic events' "enabled" flag when Tor is shut down
495 cleanly. Previously, this flag was left on, which caused periodic
496 events not to be re-enabled when Tor was relaunched in-process
497 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
500 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
501 - Avoid a minor memory leak that could occur on relays when failing
502 to create a "keys" directory. Fixes bug 30148; bugfix
505 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
506 - Fix a trivial memory leak when parsing an invalid value
507 from a download schedule in the configuration. Fixes bug
508 30894; bugfix on 0.3.4.1-alpha.
510 o Minor bugfixes (memory management, backport from 0.4.0.3-alpha):
511 - Refactor the shared random state's memory management so that it
512 actually takes ownership of the shared random value pointers.
513 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
515 o Minor bugfixes (memory management, testing, backport from 0.4.0.3-alpha):
516 - Stop leaking parts of the shared random state in the shared-random
517 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
519 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
520 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
521 implemenation) when failing to load an onion service client
522 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
524 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
525 - When purging the DNS cache because of an out-of-memory condition,
526 try purging just the older entries at first. Previously, we would
527 always purge the whole thing. Fixes bug 29617; bugfix
530 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
531 - Avoid crashing in our tor_vasprintf() implementation on systems
532 that define neither vasprintf() nor _vscprintf(). (This bug has
533 been here long enough that we question whether people are running
534 Tor on such systems, but we're applying the fix out of caution.)
535 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
538 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
539 - Avoid crashing when starting with a corrupt keys directory where
540 the old ntor key and the new ntor key are identical. Fixes bug
541 30916; bugfix on 0.2.4.8-alpha.
543 o Minor bugfixes (rust, backport from 0.4.0.5):
544 - Abort on panic in all build profiles, instead of potentially
545 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
547 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
548 - Correctly exclude a redundant rust build job in Travis. Fixes bug
549 31463; bugfix on 0.3.5.4-alpha.
551 o Minor bugfixes (single onion services, backport from 0.4.0.3-alpha):
552 - Allow connections to single onion services to remain idle without
553 being disconnected. Previously, relays acting as rendezvous points
554 for single onion services were mistakenly closing idle rendezvous
555 circuits after 60 seconds, thinking that they were unused
556 directory-fetching circuits that had served their purpose. Fixes
557 bug 29665; bugfix on 0.2.1.26.
559 o Minor bugfixes (stats, backport from 0.4.0.3-alpha):
560 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
561 relay and bridge extra-info documents. Fixes bug 29017; bugfix
564 o Minor bugfixes (testing, backport from 0.4.0.3-alpha):
565 - Downgrade some LOG_ERR messages in the address/* tests to
566 warnings. The LOG_ERR messages were occurring when we had no
567 configured network. We were failing the unit tests, because we
568 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
569 29530; bugfix on 0.3.5.8.
570 - Fix our gcov wrapper script to look for object files at the
571 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
573 o Minor bugfixes (testing, backport from 0.4.0.4-rc):
574 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
575 recent test-network.sh to use new chutney features in CI. Fixes
576 bug 29703; bugfix on 0.2.9.1-alpha.
577 - Fix a test failure on Windows caused by an unexpected "BUG"
578 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
581 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
582 - When testing port rebinding, don't busy-wait for tor to log.
583 Instead, actually sleep for a short time before polling again.
584 Also improve the formatting of control commands and log messages.
585 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
587 o Minor bugfixes (TLS protocol, backport form 0.4.0.4-rc):
588 - When classifying a client's selection of TLS ciphers, if the
589 client ciphers are not yet available, do not cache the result.
590 Previously, we had cached the unavailability of the cipher list
591 and never looked again, which in turn led us to assume that the
592 client only supported the ancient V1 link protocol. This, in turn,
593 was causing Stem integration tests to stall in some cases. Fixes
594 bug 30021; bugfix on 0.2.4.8-alpha.
596 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
597 - Log bugs about the TLS read buffer's length only once, rather than
598 filling the logs with similar warnings. Fixes bug 31939; bugfix
601 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
602 - Always retry v2 single onion service intro and rend circuits with
603 a 3-hop path. Previously, v2 single onion services used a 3-hop
604 path when rendezvous circuits were retried after a remote or
605 delayed failure, but a 1-hop path for immediate retries. Fixes bug
606 23818; bugfix on 0.2.9.3-alpha.
607 - Make v3 single onion services fall back to a 3-hop intro, when all
608 intro points are unreachable via a 1-hop path. Previously, v3
609 single onion services failed when all intro nodes were unreachable
610 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
612 o Minor bugfixes (Windows, CI, backport from 0.4.0.3-alpha):
613 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
614 Windows Server 2012 R2 job. The remaining 2 jobs still provide
615 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
616 fast_finish, so failed jobs terminate the build immediately. Fixes
617 bug 29601; bugfix on 0.3.5.4-alpha.
619 o Documentation (backport from 0.4.2.1-alpha):
620 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
621 notice.html so that operators no longer have to host it
622 themselves. Closes ticket 31089.
624 o Testing (backport from 0.4.1.2-alpha):
625 - Specify torrc paths (with empty files) when launching tor in
626 integration tests; refrain from reading user and system torrcs.
627 Resolves issue 29702.
629 o Testing (continuous integration, backport from 0.4.1.1-alpha):
630 - In Travis, show stem's tor log after failure. Closes ticket 30234.
632 o Testing (continuous integration, backport from 0.4.1.5):
633 - In Travis, make stem log a controller trace to the console, and
634 tail stem's tor log after failure. Closes ticket 30591.
635 - In Travis, only run the stem tests that use a tor binary. Closes
638 o Testing (continuous integration, backport from 0.4.2.3-alpha):
639 - Disable all but one Travis CI macOS build, to mitigate slow
640 scheduling of Travis macOS jobs. Closes ticket 32177.
641 - Run the chutney IPv6 networks as part of Travis CI. Closes
643 - Simplify the Travis CI build matrix, and optimise for build time.
645 - Use Windows Server 2019 instead of Windows Server 2016 in our
646 Appveyor builds. Closes ticket 32086.
648 o Testing (continuous integration, backport from 0.4.2.4-rc):
649 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
650 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
651 until we can fix some Bionic permissions issues (see ticket
652 32240). Related to ticket 31919.
653 - Install the mingw OpenSSL package in Appveyor. This makes sure
654 that the OpenSSL headers and libraries match in Tor's Appveyor
655 builds. (This bug was triggered by an Appveyor image update.)
656 Fixes bug 32449; bugfix on 0.3.5.6-rc.
657 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
659 o Testing (continuous integration, backport from 0.4.2.5):
660 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
661 extensions. Also activates clang's -Wtypedef-redefinition warnings.
662 Build some jobs with -std=gnu99, and some jobs without.
666 Changes in version 0.3.5.8 - 2019-02-21
667 Tor 0.3.5.8 backports serveral fixes from later releases, including fixes
668 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
671 It also includes a fix for a medium-severity security bug affecting Tor
672 0.3.2.1-alpha and later. All Tor instances running an affected release
673 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
675 o Major bugfixes (cell scheduler, KIST, security):
676 - Make KIST consider the outbuf length when computing what it can
677 put in the outbuf. Previously, KIST acted as though the outbuf
678 were empty, which could lead to the outbuf becoming too full. It
679 is possible that an attacker could exploit this bug to cause a Tor
680 client or relay to run out of memory and crash. Fixes bug 29168;
681 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
682 TROVE-2019-001 and CVE-2019-8955.
684 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
685 - Gracefully handle empty username/password fields in SOCKS5
686 username/password auth messsage and allow SOCKS5 handshake to
687 continue. Previously, we had rejected these handshakes, breaking
688 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
690 o Minor features (compilation, backport from 0.4.0.2-alpha):
691 - Compile correctly when OpenSSL is built with engine support
692 disabled, or with deprecated APIs disabled. Closes ticket 29026.
693 Patches from "Mangix".
695 o Minor features (geoip):
696 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
697 Country database. Closes ticket 29478.
699 o Minor features (testing, backport from 0.4.0.2-alpha):
700 - Treat all unexpected ERR and BUG messages as test failures. Closes
703 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
704 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
705 connection waiting for a descriptor that we actually have in the
706 cache. It turns out that this can actually happen, though it is
707 rare. Now, tor will recover and retry the descriptor. Fixes bug
708 28669; bugfix on 0.3.2.4-alpha.
710 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
711 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
712 IPv6 socket was bound using an address family of AF_INET instead
713 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
716 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
717 - Update Cargo.lock file to match the version made by the latest
718 version of Rust, so that "make distcheck" will pass again. Fixes
719 bug 29244; bugfix on 0.3.3.4-alpha.
721 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
722 - Select guards even if the consensus has expired, as long as the
723 consensus is still reasonably live. Fixes bug 24661; bugfix
726 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
727 - Compile correctly on OpenBSD; previously, we were missing some
728 headers required in order to detect it properly. Fixes bug 28938;
729 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
731 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
732 - Describe the contents of the v3 onion service client authorization
733 files correctly: They hold public keys, not private keys. Fixes
734 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
736 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
737 - Rework rep_hist_log_link_protocol_counts() to iterate through all
738 link protocol versions when logging incoming/outgoing connection
739 counts. Tor no longer skips version 5, and we won't have to
740 remember to update this function when new link protocol version is
741 developed. Fixes bug 28920; bugfix on 0.2.6.10.
743 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
744 - Log more information at "warning" level when unable to read a
745 private key; log more information at "info" level when unable to
746 read a public key. We had warnings here before, but they were lost
747 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
749 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
750 - The amount of total available physical memory is now determined
751 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
752 when it is defined and a 64-bit variant is not available. Fixes
753 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
755 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
756 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
757 than one private key for a hidden service. Fixes bug 29040; bugfix
759 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
760 "debug" level. Tor used to log it as a warning, which caused very
761 long log lines to appear for some users. Fixes bug 29135; bugfix
763 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
764 as a warning. Instead, log it as a protocol warning, because there
765 is nothing that relay operators can do to fix it. Fixes bug 29029;
766 bugfix on 0.2.5.7-rc.
768 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
769 - Mark outdated dirservers when Tor only has a reasonably live
770 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
772 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
773 - Detect and suppress "bug" warnings from the util/time test on
774 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
775 - Do not log an error-level message if we fail to find an IPv6
776 network interface from the unit tests. Fixes bug 29160; bugfix
779 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
780 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
781 Some users took this phrasing to mean that the mentioned guard was
782 under their control or responsibility, which it is not. Fixes bug
783 28895; bugfix on Tor 0.3.0.1-alpha.
786 Changes in version 0.3.5.7 - 2019-01-07
787 Tor 0.3.5.7 is the first stable release in its series; it includes
788 compilation and portability fixes, and a fix for a severe problem
789 affecting directory caches.
791 The Tor 0.3.5 series includes several new features and performance
792 improvements, including client authorization for v3 onion services,
793 cleanups to bootstrap reporting, support for improved bandwidth-
794 measurement tools, experimental support for NSS in place of OpenSSL,
795 and much more. It also begins a full reorganization of Tor's code
796 layout, for improved modularity and maintainability in the future.
797 Finally, there is the usual set of performance improvements and
798 bugfixes that we try to do in every release series.
800 There are a couple of changes in the 0.3.5 that may affect
801 compatibility. First, the default version for newly created onion
802 services is now v3. Use the HiddenServiceVersion option if you want to
803 override this. Second, some log messages related to bootstrapping have
804 changed; if you use stem, you may need to update to the latest version
805 so it will recognize them.
807 We have designated 0.3.5 as a "long-term support" (LTS) series: we
808 will continue to patch major bugs in typical configurations of 0.3.5
809 until at least 1 Feb 2022. (We do not plan to provide long-term
810 support for embedding, Rust support, NSS support, running a directory
811 authority, or unsupported platforms. For these, you will need to stick
812 with the latest stable release.)
814 Below are the changes since 0.3.4.9. For a complete list of changes
815 since 0.3.5.6-rc, see the ChangeLog file.
817 o Major features (bootstrap):
818 - Don't report directory progress until after a connection to a
819 relay or bridge has succeeded. Previously, we'd report 80%
820 progress based on cached directory information when we couldn't
821 even connect to the network. Closes ticket 27169.
823 o Major features (new code layout):
824 - Nearly all of Tor's source code has been moved around into more
825 logical places. The "common" directory is now divided into a set
826 of libraries in "lib", and files in the "or" directory have been
827 split into "core" (logic absolutely needed for onion routing),
828 "feature" (independent modules in Tor), and "app" (to configure
829 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
830 more information. Closes ticket 26481.
832 This refactoring is not complete: although the libraries have been
833 refactored to be acyclic, the main body of Tor is still too
834 interconnected. We will attempt to improve this in the future.
836 o Major features (onion services v3):
837 - Implement onion service client authorization at the descriptor
838 level: only authorized clients can decrypt a service's descriptor
839 to find out how to contact it. A new torrc option was added to
840 control this client side: ClientOnionAuthDir <path>. On the
841 service side, if the "authorized_clients/" directory exists in the
842 onion service directory path, client configurations are read from
843 the files within. See the manpage for more details. Closes ticket
844 27547. Patch done by Suphanat Chunhapanya (haxxpop).
845 - Improve revision counter generation in next-gen onion services.
846 Onion services can now scale by hosting multiple instances on
847 different hosts without synchronization between them, which was
848 previously impossible because descriptors would get rejected by
849 HSDirs. Addresses ticket 25552.
850 - Version 3 onion services can now use the per-service
851 HiddenServiceExportCircuitID option to differentiate client
852 circuits. It communicates with the service by using the HAProxy
853 protocol to assign virtual IP addresses to inbound client
854 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
856 o Major features (onion services, UI change):
857 - For a newly created onion service, the default version is now 3.
858 Tor still supports existing version 2 services, but the operator
859 now needs to set "HiddenServiceVersion 2" in order to create a new
860 version 2 service. For existing services, Tor now learns the
861 version by reading the key file. Closes ticket 27215.
863 o Major features (portability, cryptography, experimental, TLS):
864 - Tor now has the option to compile with the NSS library instead of
865 OpenSSL. This feature is experimental, and we expect that bugs may
866 remain. It is mainly intended for environments where Tor's
867 performance is not CPU-bound, and where NSS is already known to be
868 installed. To try it out, configure Tor with the --enable-nss
869 flag. Closes tickets 26631, 26815, and 26816.
871 If you are experimenting with this option and using an old cached
872 consensus, Tor may fail to start. To solve this, delete your
873 "cached-consensus" and "cached-microdesc-consensus" files,
874 (if present), and restart Tor.
876 o Major features (relay, UI change):
877 - Relays no longer run as exits by default. If the "ExitRelay"
878 option is auto (or unset), and no exit policy is specified with
879 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
880 Previously in this case, we allowed exit traffic and logged a
881 warning message. Closes ticket 21530. Patch by Neel Chauhan.
882 - Tor now validates that the ContactInfo config option is valid UTF-
883 8 when parsing torrc. Closes ticket 27428.
885 o Major bugfixes (compilation):
886 - Fix compilation on ARM (and other less-used CPUs) when compiling
887 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
889 o Major bugfixes (compilation, rust):
890 - Rust tests can now build and run successfully with the
891 --enable-fragile-hardening option enabled. Doing this currently
892 requires the rust beta channel; it will be possible with stable
893 rust once Rust version 1.31 is released. Patch from Alex Crichton.
894 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
896 o Major bugfixes (directory authority):
897 - Actually check that the address we get from DirAuthority
898 configuration line is valid IPv4. Explicitly disallow DirAuthority
899 address to be a DNS hostname. Fixes bug 26488; bugfix
902 o Major bugfixes (embedding, main loop):
903 - When DisableNetwork becomes set, actually disable periodic events
904 that are already enabled. (Previously, we would refrain from
905 enabling new ones, but we would leave the old ones turned on.)
906 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
908 o Major bugfixes (main loop, bootstrap):
909 - Make sure Tor bootstraps and works properly if only the
910 ControlPort is set. Prior to this fix, Tor would only bootstrap
911 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
912 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
914 o Major bugfixes (onion service v3):
915 - On an intro point for a version 3 onion service, stop closing
916 introduction circuits on a NACK. This lets the client decide
917 whether to reuse the circuit or discard it. Previously, we closed
918 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
919 0.3.2.1-alpha. Patch by Neel Chaunan.
921 o Major bugfixes (OpenSSL, portability):
922 - Fix our usage of named groups when running as a TLS 1.3 client in
923 OpenSSL 1.1.1. Previously, we only initialized EC groups when
924 running as a relay, which caused clients to fail to negotiate TLS
925 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
928 o Major bugfixes (relay bandwidth statistics):
929 - When we close relayed circuits, report the data in the circuit
930 queues as being written in our relay bandwidth stats. This
931 mitigates guard discovery and other attacks that close circuits
932 for the explicit purpose of noticing this discrepancy in
933 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
935 o Major bugfixes (relay):
936 - When our write bandwidth limit is exhausted, stop writing on the
937 connection. Previously, we had a typo in the code that would make
938 us stop reading instead, leading to relay connections being stuck
939 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
941 - Always reactivate linked connections in the main loop so long as
942 any linked connection has been active. Previously, connections
943 serving directory information wouldn't get reactivated after the
944 first chunk of data was sent (usually 32KB), which would prevent
945 clients from bootstrapping. Fixes bug 28912; bugfix on
946 0.3.4.1-alpha. Patch by "cypherpunks3".
948 o Major bugfixes (restart-in-process):
949 - Fix a use-after-free error that could be caused by passing Tor an
950 impossible set of options that would fail during options_act().
951 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
953 o Minor features (admin tools):
954 - Add a new --key-expiration option to print the expiration date of
955 the signing cert in an ed25519_signing_cert file. Resolves
958 o Minor features (build):
959 - If you pass the "--enable-pic" option to configure, Tor will try
960 to tell the compiler to build position-independent code suitable
961 to link into a dynamic library. (The default remains -fPIE, for
962 code suitable for a relocatable executable.) Closes ticket 23846.
964 o Minor features (code correctness, testing):
965 - Tor's build process now includes a "check-includes" make target to
966 verify that no module of Tor relies on any headers from a higher-
967 level module. We hope to use this feature over time to help
968 refactor our codebase. Closes ticket 26447.
970 o Minor features (code layout):
971 - We have a new "lowest-level" error-handling API for use by code
972 invoked from within the logging module. With this interface, the
973 logging code is no longer at risk of calling into itself if a
974 failure occurs while it is trying to log something. Closes
977 o Minor features (compilation):
978 - When possible, place our warning flags in a separate file, to
979 avoid flooding verbose build logs. Closes ticket 28924.
980 - Tor's configure script now supports a --with-malloc= option to
981 select your malloc implementation. Supported options are
982 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
983 default). Addresses part of ticket 20424. Based on a patch from
986 o Minor features (config):
987 - The "auto" keyword in torrc is now case-insensitive. Closes
990 o Minor features (continuous integration):
991 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
993 - Add new CI job to Travis configuration to run stem-based
994 integration tests. Closes ticket 27913.
995 - Use the Travis Homebrew addon to install packages on macOS during
996 Travis CI. The package list is the same, but the Homebrew addon
997 does not do a `brew update` by default. Implements ticket 27738.
998 - Report what program produced the mysterious core file that we
999 occasionally see on Travis CI during make distcheck. Closes
1001 - Don't do a distcheck with --disable-module-dirauth in Travis.
1002 Implements ticket 27252.
1003 - Install libcap-dev and libseccomp2-dev so these optional
1004 dependencies get tested on Travis CI. Closes ticket 26560.
1005 - Only run one online rust build in Travis, to reduce network
1006 errors. Skip offline rust builds on Travis for Linux gcc, because
1007 they're redundant. Implements ticket 27252.
1008 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1009 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1010 Linux with default settings, because all the non-default builds
1011 use gcc on Linux. Implements ticket 27252.
1013 o Minor features (continuous integration, Windows):
1014 - Always show the configure and test logs, and upload them as build
1015 artifacts, when building for Windows using Appveyor CI.
1017 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
1018 Appveyor's CI. Closes ticket 28318.
1020 o Minor features (controller):
1021 - Emit CIRC_BW events as soon as we detect that we processed an
1022 invalid or otherwise dropped cell on a circuit. This allows
1023 vanguards and other controllers to react more quickly to dropped
1024 cells. Closes ticket 27678.
1025 - For purposes of CIRC_BW-based dropped cell detection, track half-
1026 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
1027 bias check cells to arrive without counting it as dropped until
1028 either the END arrives, or the windows are empty. Closes
1030 - Implement a 'GETINFO md/all' controller command to enable getting
1031 all known microdescriptors. Closes ticket 8323.
1032 - The GETINFO command now support an "uptime" argument, to return
1033 Tor's uptime in seconds. Closes ticket 25132.
1035 o Minor features (denial-of-service avoidance):
1036 - Make our OOM handler aware of the DNS cache so that it doesn't
1037 fill up the memory. This check is important for our DoS mitigation
1038 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
1040 o Minor features (development):
1041 - Tor's makefile now supports running the "clippy" Rust style tool
1042 on our Rust code. Closes ticket 22156.
1044 o Minor features (directory authority):
1045 - There is no longer an artificial upper limit on the length of
1046 bandwidth lines. Closes ticket 26223.
1047 - When a bandwidth file is used to obtain the bandwidth measurements,
1048 include this bandwidth file headers in the votes. Closes
1050 - Improved support for networks with only a single authority or a
1051 single fallback directory. Patch from Gabriel Somlo. Closes
1054 o Minor features (embedding API):
1055 - The Tor controller API now supports a function to launch Tor with
1056 a preconstructed owning controller FD, so that embedding
1057 applications don't need to manage controller ports and
1058 authentication. Closes ticket 24204.
1059 - The Tor controller API now has a function that returns the name
1060 and version of the backend implementing the API. Closes
1063 o Minor features (fallback directory list):
1064 - Replace the 150 fallbacks originally introduced in Tor
1065 0.3.3.1-alpha in January 2018 (of which ~115 were still
1066 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1067 removed) generated in December 2018. Closes ticket 24803.
1069 o Minor features (geoip):
1070 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
1071 Country database. Closes ticket 29012.
1073 o Minor features (memory management):
1074 - Get Libevent to use the same memory allocator as Tor, by calling
1075 event_set_mem_functions() during initialization. Resolves
1078 o Minor features (memory usage):
1079 - When not using them, store legacy TAP public onion keys in DER-
1080 encoded format, rather than as expanded public keys. This should
1081 save several megabytes on typical clients. Closes ticket 27246.
1083 o Minor features (OpenSSL bug workaround):
1084 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1085 key export function from handling long labels. When this bug is
1086 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1087 version of OpenSSL without this bug when it becomes available.
1088 Closes ticket 28973.
1090 o Minor features (OpenSSL):
1091 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
1092 than our own. Resolves ticket 19979.
1094 o Minor features (performance):
1095 - Remove about 96% of the work from the function that we run at
1096 startup to test our curve25519_basepoint implementation. Since
1097 this function has yet to find an actual failure, we now only run
1098 it for 8 iterations instead of 200. Based on our profile
1099 information, this change should save around 8% of our startup time
1100 on typical desktops, and may have a similar effect on other
1101 platforms. Closes ticket 28838.
1102 - Stop re-validating our hardcoded Diffie-Hellman parameters on
1103 every startup. Doing this wasted time and cycles, especially on
1104 low-powered devices. Closes ticket 28851.
1106 o Minor features (Rust, code quality):
1107 - Improve rust code quality in the rust protover implementation by
1108 making it more idiomatic. Includes changing an internal API to
1109 take &str instead of &String. Closes ticket 26492.
1111 o Minor features (testing):
1112 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
1113 chutney. Implements ticket 27211.
1115 o Minor features (tor-resolve):
1116 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
1117 Side-effect of the refactoring for ticket 26526.
1119 o Minor features (UI):
1120 - Log each included configuration file or directory as we read it,
1121 to provide more visibility about where Tor is reading from. Patch
1122 from Unto Sten; closes ticket 27186.
1123 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
1124 Closes ticket 26703.
1126 o Minor bugfixes (32-bit OSX and iOS, timing):
1127 - Fix an integer overflow bug in our optimized 32-bit millisecond-
1128 difference algorithm for 32-bit Apple platforms. Previously, it
1129 would overflow when calculating the difference between two times
1130 more than 47 days apart. Fixes part of bug 27139; bugfix
1132 - Improve the precision of our 32-bit millisecond difference
1133 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
1134 bugfix on 0.3.4.1-alpha.
1135 - Relax the tolerance on the mainloop/update_time_jumps test when
1136 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
1139 o Minor bugfixes (bootstrap):
1140 - Try harder to get descriptors in non-exit test networks, by using
1141 the mid weight for the third hop when there are no exits. Fixes
1142 bug 27237; bugfix on 0.2.6.2-alpha.
1144 o Minor bugfixes (C correctness):
1145 - Avoid casting smartlist index to int implicitly, as it may trigger
1146 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
1147 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
1148 - Use time_t for all values in
1149 predicted_ports_prediction_time_remaining(). Rework the code that
1150 computes difference between durations/timestamps. Fixes bug 27165;
1151 bugfix on 0.3.1.1-alpha.
1153 o Minor bugfixes (client, memory usage):
1154 - When not running as a directory cache, there is no need to store
1155 the text of the current consensus networkstatus in RAM.
1156 Previously, however, clients would store it anyway, at a cost of
1157 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
1160 o Minor bugfixes (client, ReachableAddresses):
1161 - Instead of adding a "reject *:*" line to ReachableAddresses when
1162 loading the configuration, add one to the policy after parsing it
1163 in parse_reachable_addresses(). This prevents extra "reject *.*"
1164 lines from accumulating on reloads. Fixes bug 20874; bugfix on
1165 0.1.1.5-alpha. Patch by Neel Chauhan.
1167 o Minor bugfixes (code quality):
1168 - Rename sandbox_getaddrinfo() and other functions to no longer
1169 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
1170 bugfix on 0.2.7.1-alpha.
1172 o Minor bugfixes (code safety):
1173 - Rewrite our assertion macros so that they no longer suppress the
1174 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
1177 o Minor bugfixes (compilation):
1178 - Initialize a variable unconditionally in aes_new_cipher(), since
1179 some compilers cannot tell that we always initialize it before
1180 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1182 o Minor bugfixes (configuration):
1183 - Refuse to start with relative file paths and RunAsDaemon set
1184 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
1187 o Minor bugfixes (configuration, Onion Services):
1188 - In rend_service_parse_port_config(), disallow any input to remain
1189 after address-port pair was parsed. This will catch address and
1190 port being whitespace-separated by mistake of the user. Fixes bug
1191 27044; bugfix on 0.2.9.10.
1193 o Minor bugfixes (connection, relay):
1194 - Avoid a logging a BUG() stacktrace when closing connection held
1195 open because the write side is rate limited but not the read side.
1196 Now, the connection read side is simply shut down until Tor is
1197 able to flush the connection and close it. Fixes bug 27750; bugfix
1200 o Minor bugfixes (continuous integration, Windows):
1201 - Stop reinstalling identical packages in our Windows CI. Fixes bug
1202 27464; bugfix on 0.3.4.1-alpha.
1203 - Install only the necessary mingw packages during our appveyor
1204 builds. This change makes the build a little faster, and prevents
1205 a conflict with a preinstalled mingw openssl that appveyor now
1206 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
1207 - Explicitly specify the path to the OpenSSL library and do not
1208 download OpenSSL from Pacman, but instead use the library that is
1209 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
1210 - Manually configure the zstd compiler options, when building using
1211 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
1212 not come with a pkg-config file. Fixes bug 28454; bugfix
1214 - Stop using an external OpenSSL install, and stop installing MSYS2
1215 packages, when building using mingw on Appveyor Windows CI. Fixes
1216 bug 28399; bugfix on 0.3.4.1-alpha.
1218 o Minor bugfixes (controller):
1219 - Consider all routerinfo errors other than "not a server" to be
1220 transient for the purpose of "GETINFO exit-policy/*" controller
1221 request. Print stacktrace in the unlikely case of failing to
1222 recompute routerinfo digest. Fixes bug 27034; bugfix
1225 o Minor bugfixes (correctness):
1226 - Fix an unreached code path where we checked the value of
1227 "hostname" inside send_resolved_hostname_cell(). Previously, we
1228 used it before checking it; now we check it first. Fixes bug
1229 28879; bugfix on 0.1.2.7-alpha.
1231 o Minor bugfixes (directory connection shutdown):
1232 - Avoid a double-close when shutting down a stalled directory
1233 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
1235 o Minor bugfixes (directory permissions):
1236 - When a user requests a group-readable DataDirectory, give it to
1237 them. Previously, when the DataDirectory and the CacheDirectory
1238 were the same, the default setting (0) for
1239 CacheDirectoryGroupReadable would override the setting for
1240 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1243 o Minor bugfixes (HTTP tunnel):
1244 - Fix a bug warning when closing an HTTP tunnel connection due to an
1245 HTTP request we couldn't handle. Fixes bug 26470; bugfix
1248 o Minor bugfixes (ipv6):
1249 - In addrs_in_same_network_family(), we choose the subnet size based
1250 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
1251 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
1252 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
1254 o Minor bugfixes (Linux seccomp2 sandbox):
1255 - Permit the "shutdown()" system call, which is apparently used by
1256 OpenSSL under some circumstances. Fixes bug 28183; bugfix
1259 o Minor bugfixes (logging):
1260 - Stop talking about the Named flag in log messages. Clients have
1261 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
1263 - As a precaution, do an early return from log_addr_has_changed() if
1264 Tor is running as client. Also, log a stack trace for debugging as
1265 this function should only be called when Tor runs as server. Fixes
1266 bug 26892; bugfix on 0.1.1.9-alpha.
1267 - Refrain from mentioning bug 21018 in the logs, as it is already
1268 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
1270 o Minor bugfixes (logging, documentation):
1271 - When SafeLogging is enabled, scrub IP address in
1272 channel_tls_process_netinfo_cell(). Also, add a note to manpage
1273 that scrubbing is not guaranteed on loglevels below Notice. Fixes
1274 bug 26882; bugfix on 0.2.4.10-alpha.
1276 o Minor bugfixes (memory leaks):
1277 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1278 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1279 - Fix a small memory leak when calling Tor with --dump-config. Fixes
1280 bug 27893; bugfix on 0.3.2.1-alpha.
1282 o Minor bugfixes (netflow padding):
1283 - Ensure circuitmux queues are empty before scheduling or sending
1284 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
1286 o Minor bugfixes (onion service v2):
1287 - Log at level "info", not "warning", in the case that we do not
1288 have a consensus when a .onion request comes in. This can happen
1289 normally while bootstrapping. Fixes bug 27040; bugfix
1292 o Minor bugfixes (onion service v3):
1293 - When deleting an ephemeral onion service (DEL_ONION), do not close
1294 any rendezvous circuits in order to let the existing client
1295 connections finish by themselves or closed by the application. The
1296 HS v2 is doing that already so now we have the same behavior for
1297 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1298 - Build the service descriptor's signing key certificate before
1299 uploading, so we always have a fresh one: leaving no chances for
1300 it to expire service side. Fixes bug 27838; bugfix
1302 - Stop dumping a stack trace when trying to connect to an intro
1303 point without having a descriptor for it. Fixes bug 27774; bugfix
1305 - When selecting a v3 rendezvous point, don't only look at the
1306 protover, but also check whether the curve25519 onion key is
1307 present. This way we avoid picking a relay that supports the v3
1308 rendezvous but for which we don't have the microdescriptor. Fixes
1309 bug 27797; bugfix on 0.3.2.1-alpha.
1310 - Close all SOCKS request (for the same .onion) if the newly fetched
1311 descriptor is unusable. Before that, we would close only the first
1312 one leaving the other hanging and let to time out by themselves.
1313 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
1314 - When the onion service directory can't be created or has the wrong
1315 permissions, do not log a stack trace. Fixes bug 27335; bugfix
1317 - When replacing a descriptor in the client cache, make sure to
1318 close all client introduction circuits for the old descriptor, so
1319 we don't end up with unusable leftover circuits. Fixes bug 27471;
1320 bugfix on 0.3.2.1-alpha.
1322 o Minor bugfixes (OS compatibility):
1323 - Properly handle configuration changes that move a listener to/from
1324 wildcard IP address. If the first attempt to bind a socket fails,
1325 close the old listener and try binding the socket again. Fixes bug
1326 17873; bugfix on 0.0.8pre-1.
1328 o Minor bugfixes (performance)::
1329 - Rework node_is_a_configured_bridge() to no longer call
1330 node_get_all_orports(), which was performing too many memory
1331 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
1333 o Minor bugfixes (protover):
1334 - Reject protocol names containing bytes other than alphanumeric
1335 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
1338 o Minor bugfixes (protover, rust):
1339 - Reject extra commas in version strings. Fixes bug 27197; bugfix
1341 - protover_all_supported() would attempt to allocate up to 16GB on
1342 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1343 bugfix on 0.3.3.5-rc.
1344 - Compute protover votes correctly in the rust version of the
1345 protover code. Previously, the protover rewrite in 24031 allowed
1346 repeated votes from the same voter for the same protocol version
1347 to be counted multiple times in protover_compute_vote(). Fixes bug
1348 27649; bugfix on 0.3.3.5-rc.
1349 - Reject protover names that contain invalid characters. Fixes bug
1350 27687; bugfix on 0.3.3.1-alpha.
1352 o Minor bugfixes (relay shutdown, systemd):
1353 - Notify systemd of ShutdownWaitLength so it can be set to longer
1354 than systemd's TimeoutStopSec. In Tor's systemd service file, set
1355 TimeoutSec to 60 seconds to allow Tor some time to shut down.
1356 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
1358 o Minor bugfixes (relay statistics):
1359 - Update relay descriptor on bandwidth changes only when the uptime
1360 is smaller than 24h, in order to reduce the efficiency of guard
1361 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1363 o Minor bugfixes (relay):
1364 - Consider the fact that we'll be making direct connections to our
1365 entry and guard nodes when computing the fraction of nodes that
1366 have their descriptors. Also, if we are using bridges and there is
1367 at least one bridge with a full descriptor, treat the fraction of
1368 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
1369 Patch by Neel Chauhan.
1370 - Update the message logged on relays when DirCache is disabled.
1371 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
1372 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
1374 o Minor bugfixes (testing):
1375 - Stop running stem's unit tests as part of "make test-stem", but
1376 continue to run stem's unit and online tests during "make test-
1377 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
1378 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1379 bugfix on 0.3.0.1-alpha.
1380 - Make the hs_service tests use the same time source when creating
1381 the introduction point and when testing it. Now tests work better
1382 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
1384 - Revise the "conditionvar_timeout" test so that it succeeds even on
1385 heavily loaded systems where the test threads are not scheduled
1386 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
1387 - Fix two unit tests to work when HOME environment variable is not
1388 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
1389 - If a unit test running in a subprocess exits abnormally or with a
1390 nonzero status code, treat the test as having failed, even if the
1391 test reported success. Without this fix, memory leaks don't cause
1392 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
1393 bugfix on 0.2.2.4-alpha.
1394 - When logging a version mismatch in our openssl_version tests,
1395 report the actual offending version strings. Fixes bug 26152;
1396 bugfix on 0.2.9.1-alpha.
1397 - Fix forking tests on Windows when there is a space somewhere in
1398 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
1400 o Minor bugfixes (Windows):
1401 - Correctly identify Windows 8.1, Windows 10, and Windows Server
1402 2008 and later from their NT versions. Fixes bug 28096; bugfix on
1403 0.2.2.34; reported by Keifer Bly.
1404 - On recent Windows versions, the GetVersionEx() function may report
1405 an earlier Windows version than the running OS. To avoid user
1406 confusion, add "[or later]" to Tor's version string on affected
1407 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
1409 - Remove Windows versions that were never supported by the
1410 GetVersionEx() function. Stop duplicating the latest Windows
1411 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
1412 reported by Keifer Bly.
1414 o Code simplification and refactoring:
1415 - When parsing a port configuration, make it more obvious to static
1416 analyzer tools that we always initialize the address. Closes
1418 - Divide more large Tor source files -- especially ones that span
1419 multiple areas of functionality -- into smaller parts, including
1420 onion.c and main.c. Closes ticket 26747.
1421 - Divide the "routerparse.c" module into separate modules for each
1422 group of parsed objects. Closes ticket 27924.
1423 - Move protover_rust.c to the same place protover.c was moved to.
1424 Closes ticket 27814.
1425 - Split directory.c into separate pieces for client, server, and
1426 common functionality. Closes ticket 26744.
1427 - Split the non-statistics-related parts from the rephist.c and
1428 geoip.c modules. Closes ticket 27892.
1429 - Split the router.c file into relay-only and shared components, to
1430 help with future modularization. Closes ticket 27864.
1431 - Divide the routerlist.c and dirserv.c modules into smaller parts.
1432 Closes ticket 27799.
1433 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
1434 longer needed. Closes ticket 26502.
1435 - Include paths to header files within Tor are now qualified by
1436 directory within the top-level src directory.
1437 - Many structures have been removed from the centralized "or.h"
1438 header, and moved into their own headers. This will allow us to
1439 reduce the number of places in the code that rely on each
1440 structure's contents and layout. Closes ticket 26383.
1441 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
1442 - Remove GetAdaptersAddresses_fn_t. The code that used it was
1443 removed as part of the 26481 refactor. Closes ticket 27467.
1444 - Rework Tor SOCKS server code to use Trunnel and benefit from
1445 autogenerated functions for parsing and generating SOCKS wire
1446 format. New implementation is cleaner, more maintainable and
1447 should be less prone to heartbleed-style vulnerabilities.
1448 Implements a significant fraction of ticket 3569.
1449 - Split sampled_guards_update_from_consensus() and
1450 select_entry_guard_for_circuit() into subfunctions. In
1451 entry_guards_update_primary() unite three smartlist enumerations
1452 into one and move smartlist comparison code out of the function.
1453 Closes ticket 21349.
1454 - Tor now assumes that you have standards-conformant stdint.h and
1455 inttypes.h headers when compiling. Closes ticket 26626.
1456 - Unify our bloom filter logic. Previously we had two copies of this
1457 code: one for routerlist filtering, and one for address set
1458 calculations. Closes ticket 26510.
1459 - Use the simpler strcmpstart() helper in
1460 rend_parse_v2_service_descriptor instead of strncmp(). Closes
1462 - Utility functions that can perform a DNS lookup are now wholly
1463 separated from those that can't, in separate headers and C
1464 modules. Closes ticket 26526.
1467 - In the tor-resolve(1) manpage, fix the reference to socks-
1468 extensions.txt by adding a web URL. Resolves ticket 27853.
1469 - Mention that we require Python to be 2.7 or newer for some
1470 integration tests that we ship with Tor. Resolves ticket 27677.
1471 - Copy paragraph and URL to Tor's code of conduct document from
1472 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
1473 - Remove old instructions from INSTALL document. Closes ticket 26588.
1474 - Warn users that they should not include MyFamily line(s) in their
1475 torrc when running Tor bridge. Closes ticket 26908.
1478 - Tor no longer supports building with the dmalloc library. For
1479 debugging memory issues, we suggest using gperftools or msan
1480 instead. Closes ticket 26426.
1481 - Tor no longer attempts to run on Windows environments without the
1482 GetAdaptersAddresses() function. This function has existed since
1483 Windows XP, which is itself already older than we support.
1484 - Remove Tor2web functionality for version 2 onion services. The
1485 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
1486 (This feature was never shipped in vanilla Tor and it was only
1487 possible to use this feature by building the support at compile
1488 time. Tor2webMode is not implemented for version 3 onion services.)
1489 Closes ticket 26367.
1492 - Increase logging and tag all log entries with timestamps in
1493 test_rebind.py. Provides diagnostics for issue 28229.
1495 o Code simplification and refactoring (shared random, dirauth):
1496 - Change many tor_assert() to use BUG() instead. The idea is to not
1497 crash a dirauth but rather scream loudly with a stacktrace and let
1498 it continue run. The shared random subsystem is very resilient and
1499 if anything wrong happens with it, at worst a non coherent value
1500 will be put in the vote and discarded by the other authorities.
1501 Closes ticket 19566.
1503 o Documentation (onion services):
1504 - Improve HSv3 client authorization by making some options more
1505 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
1506 - Document in the man page that changing ClientOnionAuthDir value or
1507 adding a new file in the directory will not work at runtime upon
1508 sending a HUP if Sandbox 1. Closes ticket 28128.
1509 - Note in the man page that the only real way to fully revoke an
1510 onion service v3 client authorization is by restarting the tor
1511 process. Closes ticket 28275.
1514 Changes in version 0.3.4.9 - 2018-11-02
1515 Tor 0.3.4.9 is the second stable release in its series; it backports
1516 numerous fixes, including a fix for a bandwidth management bug that
1517 was causing memory exhaustion on relays. Anyone running an earlier
1518 version of Tor 0.3.4.9 should upgrade.
1520 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
1521 - Fix compilation on ARM (and other less-used CPUs) when compiling
1522 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
1524 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
1525 - Make sure Tor bootstraps and works properly if only the
1526 ControlPort is set. Prior to this fix, Tor would only bootstrap
1527 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
1528 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
1530 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
1531 - When our write bandwidth limit is exhausted, stop writing on the
1532 connection. Previously, we had a typo in the code that would make
1533 us stop reading instead, leading to relay connections being stuck
1534 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
1537 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
1538 - Fix a use-after-free error that could be caused by passing Tor an
1539 impossible set of options that would fail during options_act().
1540 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1542 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
1543 - Don't do a distcheck with --disable-module-dirauth in Travis.
1544 Implements ticket 27252.
1545 - Only run one online rust build in Travis, to reduce network
1546 errors. Skip offline rust builds on Travis for Linux gcc, because
1547 they're redundant. Implements ticket 27252.
1548 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1549 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1550 Linux with default settings, because all the non-default builds
1551 use gcc on Linux. Implements ticket 27252.
1553 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
1554 - Use the Travis Homebrew addon to install packages on macOS during
1555 Travis CI. The package list is the same, but the Homebrew addon
1556 does not do a `brew update` by default. Implements ticket 27738.
1558 o Minor features (geoip):
1559 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
1560 Country database. Closes ticket 27991.
1562 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
1563 - Fix an integer overflow bug in our optimized 32-bit millisecond-
1564 difference algorithm for 32-bit Apple platforms. Previously, it
1565 would overflow when calculating the difference between two times
1566 more than 47 days apart. Fixes part of bug 27139; bugfix
1568 - Improve the precision of our 32-bit millisecond difference
1569 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
1570 bugfix on 0.3.4.1-alpha.
1571 - Relax the tolerance on the mainloop/update_time_jumps test when
1572 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
1575 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
1576 - Avoid undefined behavior in an end-of-string check when parsing
1577 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1580 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
1581 - Only install the necessary mingw packages during our appveyor
1582 builds. This change makes the build a little faster, and prevents
1583 a conflict with a preinstalled mingw openssl that appveyor now
1584 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
1586 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
1587 - Rewrite our assertion macros so that they no longer suppress the
1588 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
1590 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
1591 - Stop reinstalling identical packages in our Windows CI. Fixes bug
1592 27464; bugfix on 0.3.4.1-alpha.
1594 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
1595 - Log additional info when we get a relay that shares an ed25519 ID
1596 with a different relay, instead making a BUG() warning. Fixes bug
1597 27800; bugfix on 0.3.2.1-alpha.
1599 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
1600 - Avoid a double-close when shutting down a stalled directory
1601 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
1603 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
1604 - Fix a bug warning when closing an HTTP tunnel connection due to an
1605 HTTP request we couldn't handle. Fixes bug 26470; bugfix
1608 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
1609 - Ensure circuitmux queues are empty before scheduling or sending
1610 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
1612 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
1613 - When the onion service directory can't be created or has the wrong
1614 permissions, do not log a stack trace. Fixes bug 27335; bugfix
1617 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
1618 - Close all SOCKS request (for the same .onion) if the newly fetched
1619 descriptor is unusable. Before that, we would close only the first
1620 one leaving the other hanging and let to time out by themselves.
1621 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
1623 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1624 - When selecting a v3 rendezvous point, don't only look at the
1625 protover, but also check whether the curve25519 onion key is
1626 present. This way we avoid picking a relay that supports the v3
1627 rendezvous but for which we don't have the microdescriptor. Fixes
1628 bug 27797; bugfix on 0.3.2.1-alpha.
1630 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
1631 - Reject protocol names containing bytes other than alphanumeric
1632 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
1635 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
1636 - Compute protover votes correctly in the rust version of the
1637 protover code. Previously, the protover rewrite in 24031 allowed
1638 repeated votes from the same voter for the same protocol version
1639 to be counted multiple times in protover_compute_vote(). Fixes bug
1640 27649; bugfix on 0.3.3.5-rc.
1641 - Reject protover names that contain invalid characters. Fixes bug
1642 27687; bugfix on 0.3.3.1-alpha.
1644 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
1645 - protover_all_supported() would attempt to allocate up to 16GB on
1646 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1647 bugfix on 0.3.3.5-rc.
1649 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
1650 - Fix an API mismatch in the rust implementation of
1651 protover_compute_vote(). This bug could have caused crashes on any
1652 directory authorities running Tor with Rust (which we do not yet
1653 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1655 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
1656 - Fix a potential null dereference in protover_all_supported(). Add
1657 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1658 - Return a string that can be safely freed by C code, not one
1659 created by the rust allocator, in protover_all_supported(). Fixes
1660 bug 27740; bugfix on 0.3.3.1-alpha.
1662 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
1663 - If a unit test running in a subprocess exits abnormally or with a
1664 nonzero status code, treat the test as having failed, even if the
1665 test reported success. Without this fix, memory leaks don't cause
1666 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
1667 bugfix on 0.2.2.4-alpha.
1669 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
1670 - Make the hs_service tests use the same time source when creating
1671 the introduction point and when testing it. Now tests work better
1672 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
1675 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
1676 - Treat backtrace test failures as expected on BSD-derived systems
1677 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1678 (FreeBSD failures have been treated as expected since 18204 in
1679 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1682 Changes in version 0.2.9.17 - 2018-09-10
1683 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
1685 o Minor features (compatibility, backport from 0.3.4.8):
1686 - Tell OpenSSL to maintain backward compatibility with previous
1687 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
1688 ciphers are disabled by default. Closes ticket 27344.
1690 o Minor features (continuous integration, backport from 0.3.4.7-rc):
1691 - Enable macOS builds in our Travis CI configuration. Closes
1693 - Install libcap-dev and libseccomp2-dev so these optional
1694 dependencies get tested on Travis CI. Closes ticket 26560.
1695 - Run asciidoc during Travis CI. Implements ticket 27087.
1696 - Use ccache in our Travis CI configuration. Closes ticket 26952.
1698 o Minor features (geoip):
1699 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
1700 Country database. Closes ticket 27089.
1702 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
1703 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
1704 tell the compiler not to include the system malloc implementation.
1705 Fixes bug 20424; bugfix on 0.2.0.20-rc.
1707 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
1708 - Silence a spurious compiler warning on the GetAdaptersAddresses
1709 function pointer cast. This issue is already fixed by 26481 in
1710 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
1711 bugfix on 0.2.3.11-alpha.
1712 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
1713 supported, and always fails. Some compilers warn about the
1714 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
1717 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
1718 - Don't link or search for pthreads when building for Windows, even
1719 if we are using build environment (like mingw) that provides a
1720 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
1722 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
1723 - Skip a pair of unreliable key generation tests on Windows, until
1724 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
1725 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
1727 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
1728 - Pass the module flags to distcheck configure, and log the flags
1729 before running configure. (Backported to 0.2.9 and later as a
1730 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
1732 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
1733 - When a Travis build fails, and showing a log fails, keep trying to
1734 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
1735 - When we use echo in Travis, don't pass a --flag as the first
1736 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
1738 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
1739 - When voting for recommended versions, make sure that all of the
1740 versions are well-formed and parsable. Fixes bug 26485; bugfix
1743 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
1744 - Fix a bug in out sandboxing rules for the openat() syscall.
1745 Previously, no openat() call would be permitted, which would break
1746 filesystem operations on recent glibc versions. Fixes bug 25440;
1747 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
1749 o Minor bugfixes (onion services, backport from 0.3.4.8):
1750 - Silence a spurious compiler warning in
1751 rend_client_send_introduction(). Fixes bug 27463; bugfix
1754 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
1755 - Log a protocol warning when single onion services or Tor2web clients
1756 fail to authenticate direct connections to relays.
1757 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
1759 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
1760 - Disable core dumps in test_bt.sh, to avoid failures in "make
1761 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
1763 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
1764 - Before running make test-network-all, delete old logs and test
1765 result files, to avoid spurious failures. Fixes bug 27295; bugfix
1768 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
1769 - Our "tortls/cert_matches_key" unit test no longer relies on
1770 OpenSSL internals. Previously, it relied on unsupported OpenSSL
1771 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
1772 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
1774 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
1775 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
1776 27185; bugfix on 0.2.2.2-alpha.
1779 Changes in version 0.3.2.12 - 2018-09-10
1780 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
1782 o Minor features (compatibility, backport from 0.3.4.8):
1783 - Tell OpenSSL to maintain backward compatibility with previous
1784 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
1785 ciphers are disabled by default. Closes ticket 27344.
1787 o Minor features (continuous integration, backport from 0.3.4.7-rc):
1788 - Enable macOS builds in our Travis CI configuration. Closes
1790 - Install libcap-dev and libseccomp2-dev so these optional
1791 dependencies get tested on Travis CI. Closes ticket 26560.
1792 - Run asciidoc during Travis CI. Implements ticket 27087.
1793 - Use ccache in our Travis CI configuration. Closes ticket 26952.
1795 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
1796 - Use cargo cache in our Travis CI configuration. Closes
1799 o Minor features (controller, backport from 0.3.4.6-rc):
1800 - The control port now exposes the list of HTTPTunnelPorts and
1801 ExtOrPorts via GETINFO net/listeners/httptunnel and
1802 net/listeners/extor respectively. Closes ticket 26647.
1804 o Minor features (directory authorities, backport from 0.3.4.7-rc):
1805 - Authorities no longer vote to make the subprotocol version
1806 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
1807 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
1809 o Minor features (geoip):
1810 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
1811 Country database. Closes ticket 27089.
1813 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
1814 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
1815 tell the compiler not to include the system malloc implementation.
1816 Fixes bug 20424; bugfix on 0.2.0.20-rc.
1817 - Don't try to use a pragma to temporarily disable the
1818 -Wunused-const-variable warning if the compiler doesn't support
1819 it. Fixes bug 26785; bugfix on 0.3.2.11.
1821 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
1822 - Silence a spurious compiler warning on the GetAdaptersAddresses
1823 function pointer cast. This issue is already fixed by 26481 in
1824 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
1825 bugfix on 0.2.3.11-alpha.
1826 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
1827 supported, and always fails. Some compilers warn about the
1828 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
1831 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
1832 - Don't link or search for pthreads when building for Windows, even
1833 if we are using build environment (like mingw) that provides a
1834 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
1836 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
1837 - Skip a pair of unreliable key generation tests on Windows, until
1838 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
1839 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
1841 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
1842 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
1843 - Pass the module flags to distcheck configure, and log the flags
1844 before running configure. (Backported to 0.2.9 and later as a
1845 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
1847 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
1848 - When a Travis build fails, and showing a log fails, keep trying to
1849 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
1850 - When we use echo in Travis, don't pass a --flag as the first
1851 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
1853 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
1854 - When voting for recommended versions, make sure that all of the
1855 versions are well-formed and parsable. Fixes bug 26485; bugfix
1858 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
1859 - Fix a bug in out sandboxing rules for the openat() syscall.
1860 Previously, no openat() call would be permitted, which would break
1861 filesystem operations on recent glibc versions. Fixes bug 25440;
1862 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
1864 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
1865 - Improve the log message when connection initiators fail to
1866 authenticate direct connections to relays. Fixes bug 26927; bugfix
1869 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
1870 - Fix bug that causes services to not ever rotate their descriptors
1871 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
1874 o Minor bugfixes (onion services, backport from 0.3.4.8):
1875 - Silence a spurious compiler warning in
1876 rend_client_send_introduction(). Fixes bug 27463; bugfix
1879 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
1880 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
1882 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
1883 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
1884 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
1885 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
1887 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
1888 - Log a protocol warning when single onion services or Tor2web clients
1889 fail to authenticate direct connections to relays.
1890 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
1892 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
1893 - Disable core dumps in test_bt.sh, to avoid failures in "make
1894 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
1896 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
1897 - When running make test-network-all, use the mixed+hs-v2 network.
1898 (A previous fix to chutney removed v3 onion services from the
1899 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
1900 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
1901 - Before running make test-network-all, delete old logs and test
1902 result files, to avoid spurious failures. Fixes bug 27295; bugfix
1905 o Minor bugfixes (testing, openssl compatibility):
1906 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
1907 internals. Previously, it relied on unsupported OpenSSL behavior in
1908 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
1909 bugfix on 0.2.5.1-alpha.
1911 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
1912 - Our "tortls/cert_matches_key" unit test no longer relies on
1913 OpenSSL internals. Previously, it relied on unsupported OpenSSL
1914 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
1915 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
1917 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
1918 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
1919 27185; bugfix on 0.2.2.2-alpha.
1922 Changes in version 0.3.3.10 - 2018-09-10
1923 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
1925 o Minor features (bug workaround, backport from 0.3.4.7-rc):
1926 - Compile correctly on systems that provide the C11 stdatomic.h
1927 header, but where C11 atomic functions don't actually compile.
1928 Closes ticket 26779; workaround for Debian issue 903709.
1930 o Minor features (compatibility, backport from 0.3.4.8):
1931 - Tell OpenSSL to maintain backward compatibility with previous
1932 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
1933 ciphers are disabled by default. Closes ticket 27344.
1935 o Minor features (continuous integration, backport from 0.3.4.7-rc):
1936 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
1937 - Enable macOS builds in our Travis CI configuration. Closes
1939 - Install libcap-dev and libseccomp2-dev so these optional
1940 dependencies get tested on Travis CI. Closes ticket 26560.
1941 - Run asciidoc during Travis CI. Implements ticket 27087.
1942 - Use ccache in our Travis CI configuration. Closes ticket 26952.
1944 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
1945 - Use cargo cache in our Travis CI configuration. Closes
1948 o Minor features (controller, backport from 0.3.4.6-rc):
1949 - The control port now exposes the list of HTTPTunnelPorts and
1950 ExtOrPorts via GETINFO net/listeners/httptunnel and
1951 net/listeners/extor respectively. Closes ticket 26647.
1953 o Minor features (directory authorities, backport from 0.3.4.7-rc):
1954 - Authorities no longer vote to make the subprotocol version
1955 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
1956 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
1958 o Minor features (geoip):
1959 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
1960 Country database. Closes ticket 27089.
1962 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
1963 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
1964 tell the compiler not to include the system malloc implementation.
1965 Fixes bug 20424; bugfix on 0.2.0.20-rc.
1966 - Don't try to use a pragma to temporarily disable the
1967 -Wunused-const-variable warning if the compiler doesn't support
1968 it. Fixes bug 26785; bugfix on 0.3.2.11.
1970 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
1971 - Silence a spurious compiler warning on the GetAdaptersAddresses
1972 function pointer cast. This issue is already fixed by 26481 in
1973 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
1974 bugfix on 0.2.3.11-alpha.
1975 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
1976 supported, and always fails. Some compilers warn about the
1977 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
1980 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
1981 - Don't link or search for pthreads when building for Windows, even
1982 if we are using build environment (like mingw) that provides a
1983 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
1985 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
1986 - Skip a pair of unreliable key generation tests on Windows, until
1987 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
1988 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
1990 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
1991 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
1992 - Pass the module flags to distcheck configure, and log the flags
1993 before running configure. (Backported to 0.2.9 and later as a
1994 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
1996 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
1997 - When a Travis build fails, and showing a log fails, keep trying to
1998 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
1999 - When we use echo in Travis, don't pass a --flag as the first
2000 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2002 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2003 - When voting for recommended versions, make sure that all of the
2004 versions are well-formed and parsable. Fixes bug 26485; bugfix
2007 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
2008 - Always call tor_free_all() when leaving tor_run_main(). When we
2009 did not, restarting tor in-process would cause an assertion
2010 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
2012 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2013 - Fix a bug in our sandboxing rules for the openat() syscall.
2014 Previously, no openat() call would be permitted, which would break
2015 filesystem operations on recent glibc versions. Fixes bug 25440;
2016 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2018 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
2019 - Improve the log message when connection initiators fail to
2020 authenticate direct connections to relays. Fixes bug 26927; bugfix
2023 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
2024 - Fix bug that causes services to not ever rotate their descriptors
2025 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
2028 o Minor bugfixes (onion services, backport from 0.3.4.8):
2029 - Silence a spurious compiler warning in
2030 rend_client_send_introduction(). Fixes bug 27463; bugfix
2033 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
2034 - Work around two different bugs in the OS X 10.10 and later SDKs
2035 that would prevent us from successfully targeting earlier versions
2036 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
2038 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
2039 - Fix compilation of the unit tests on GNU/Hurd, which does not
2040 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
2043 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
2044 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
2046 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
2047 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
2048 - Protover parsing was accepting the presence of whitespace in
2049 version strings, which the C implementation would choke on, e.g.
2050 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
2051 - Protover parsing was ignoring a 2nd hyphen and everything after
2052 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
2054 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
2055 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
2056 - cd to ${abs_top_builddir}/src/rust before running cargo in
2057 src/test/test_rust.sh. This makes the working directory consistent
2058 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
2060 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2061 - Log a protocol warning when single onion services or Tor2web clients
2062 fail to authenticate direct connections to relays.
2063 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2065 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2066 - Disable core dumps in test_bt.sh, to avoid failures in "make
2067 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2069 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2070 - When running make test-network-all, use the mixed+hs-v2 network.
2071 (A previous fix to chutney removed v3 onion services from the
2072 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
2073 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
2074 - Before running make test-network-all, delete old logs and test
2075 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2078 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2079 - Our "tortls/cert_matches_key" unit test no longer relies on
2080 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2081 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2082 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2084 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
2085 - Stop sending ed25519 link specifiers in v3 onion service introduce
2086 cells and descriptors, when the rendezvous or introduction point
2087 doesn't support ed25519 link authentication. Fixes bug 26627;
2088 bugfix on 0.3.2.4-alpha.
2090 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2091 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2092 27185; bugfix on 0.2.2.2-alpha.
2095 Changes in version 0.3.4.8 - 2018-09-10
2096 Tor 0.3.4.8 is the first stable release in its series; it includes
2097 compilation and portability fixes.
2099 The Tor 0.3.4 series includes improvements for running Tor in
2100 low-power and embedded environments, which should help performance in
2101 general. We've begun work on better modularity, and included preliminary
2102 changes on the directory authority side to accommodate a new bandwidth
2103 measurement system. We've also integrated more continuous-integration
2104 systems into our development process, and made corresponding changes to
2105 Tor's testing infrastructure. Finally, we've continued to refine
2106 our anti-denial-of-service code.
2108 Below are the changes since 0.3.3.9. For a list of only the changes
2109 since 0.3.4.7-rc, see the ChangeLog file.
2111 o New system requirements:
2112 - Tor no longer tries to support old operating systems without
2113 mmap() or some local equivalent. Apparently, compilation on such
2114 systems has been broken for some time, without anybody noticing or
2115 complaining. Closes ticket 25398.
2117 o Major features (directory authority, modularization):
2118 - The directory authority subsystem has been modularized. The code
2119 is now located in src/or/dirauth/, and is compiled in by default.
2120 To disable the module, the configure option
2121 --disable-module-dirauth has been added. This module may be
2122 disabled by default in some future release. Closes ticket 25610.
2124 o Major features (main loop, CPU usage):
2125 - When Tor is disabled (via DisableNetwork or via hibernation), it
2126 no longer needs to run any per-second events. This change should
2127 make it easier for mobile applications to disable Tor while the
2128 device is sleeping, or Tor is not running. Closes ticket 26063.
2129 - Tor no longer enables all of its periodic events by default.
2130 Previously, Tor would enable all possible main loop events,
2131 regardless of whether it needed them. Furthermore, many of these
2132 events are now disabled when Tor is hibernating or DisableNetwork
2133 is set. This is a big step towards reducing client CPU usage by
2134 reducing the amount of wake-ups the daemon does. Closes tickets
2136 - The bandwidth-limitation logic has been refactored so that
2137 bandwidth calculations are performed on-demand, rather than every
2138 TokenBucketRefillInterval milliseconds. This change should improve
2139 the granularity of our bandwidth calculations, and limit the
2140 number of times that the Tor process needs to wake up when it is
2141 idle. Closes ticket 25373.
2142 - Move responsibility for many operations from a once-per-second
2143 callback to a callback that is only scheduled as needed. Moving
2144 this functionality has allowed us to disable the callback when
2145 Tor's network is disabled. Once enough items are removed from our
2146 once-per-second callback, we can eliminate it entirely to conserve
2147 CPU when idle. The functionality removed includes: closing
2148 connections, circuits, and channels (ticket 25932); consensus
2149 voting (25937); flushing log callbacks (25951); honoring delayed
2150 SIGNEWNYM requests (25949); rescanning the consensus cache
2151 (25931); saving the state file to disk (25948); warning relay
2152 operators about unreachable ports (25952); and keeping track of
2153 Tor's uptime (26009).
2155 o Minor features (accounting):
2156 - When Tor becomes dormant, it now uses a scheduled event to wake up
2157 at the right time. Previously, we would use the per-second timer
2158 to check whether to wake up, but we no longer have any per-second
2159 timers enabled when the network is disabled. Closes ticket 26064.
2161 o Minor features (bug workaround):
2162 - Compile correctly on systems that provide the C11 stdatomic.h
2163 header, but where C11 atomic functions don't actually compile.
2164 Closes ticket 26779; workaround for Debian issue 903709.
2166 o Minor features (code quality):
2167 - Add optional spell-checking for the Tor codebase, using the
2168 "misspell" program. To use this feature, run "make check-typos".
2169 Closes ticket 25024.
2171 o Minor features (compatibility):
2172 - Tell OpenSSL to maintain backward compatibility with previous
2173 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2174 ciphers are disabled by default. Closes ticket 27344.
2175 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
2176 the no-deprecated option, and builds correctly with them. Closes
2177 tickets 19429, 19981, and 25353.
2179 o Minor features (compilation):
2180 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2181 tell the compiler not to include the system malloc implementation.
2182 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2183 - Don't try to use a pragma to temporarily disable the
2184 -Wunused-const-variable warning if the compiler doesn't support
2185 it. Fixes bug 26785; bugfix on 0.3.2.11.
2186 - When building Tor, prefer to use Python 3 over Python 2, and more
2187 recent (contemplated) versions over older ones. Closes
2190 o Minor features (compression, zstd):
2191 - When running with zstd, Tor now considers using advanced functions
2192 that the zstd maintainers have labeled as potentially unstable. To
2193 prevent breakage, Tor will only use this functionality when the
2194 runtime version of the zstd library matches the version with which
2195 Tor was compiled. Closes ticket 25162.
2197 o Minor features (configuration):
2198 - The "DownloadSchedule" options have been renamed to end with
2199 "DownloadInitialDelay". The old names are still allowed, but will
2200 produce a warning. Comma-separated lists are still permitted for
2201 these options, but all values after the first are ignored (as they
2202 have been since 0.2.9). Closes ticket 23354.
2204 o Minor features (continuous integration):
2205 - Log the compiler path and version during Appveyor builds.
2206 Implements ticket 27449.
2207 - Show config.log and test-suite.log after failed Appveyor builds.
2208 Also upload the zipped full logs as a build artifact. Implements
2210 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
2211 - Enable macOS builds in our Travis CI configuration. Closes
2213 - Install libcap-dev and libseccomp2-dev so these optional
2214 dependencies get tested on Travis CI. Closes ticket 26560.
2215 - Only post Appveyor IRC notifications when the build fails.
2216 Implements ticket 27275.
2217 - Run asciidoc during Travis CI. Implements ticket 27087.
2218 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2219 - Add the necessary configuration files for continuous integration
2220 testing on Windows, via the Appveyor platform. Closes ticket
2221 25549. Patches from Marcin Cieślak and Isis Lovecruft.
2223 o Minor features (continuous integration, rust):
2224 - Use cargo cache in our Travis CI configuration. Closes
2227 o Minor features (control port):
2228 - Introduce GETINFO "current-time/{local,utc}" to return the local
2229 and UTC times respectively in ISO format. This helps a controller
2230 like Tor Browser detect a time-related error. Closes ticket 25511.
2231 Patch by Neel Chauhan.
2232 - Introduce new fields to the CIRC_BW event. There are two new
2233 fields in each of the read and written directions. The DELIVERED
2234 fields report the total valid data on the circuit, as measured by
2235 the payload sizes of verified and error-checked relay command
2236 cells. The OVERHEAD fields report the total unused bytes in each
2237 of these cells. Closes ticket 25903.
2239 o Minor features (controller):
2240 - The control port now exposes the list of HTTPTunnelPorts and
2241 ExtOrPorts via GETINFO net/listeners/httptunnel and
2242 net/listeners/extor respectively. Closes ticket 26647.
2244 o Minor features (directory authorities):
2245 - Stop warning about incomplete bw lines before the first complete
2246 bw line has been found, so that additional header lines can be
2247 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
2248 - Authorities no longer vote to make the subprotocol version
2249 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
2250 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
2252 o Minor features (directory authority):
2253 - Directory authorities now open their key-pinning files as O_SYNC,
2254 to limit their chances of accidentally writing partial lines.
2255 Closes ticket 23909.
2257 o Minor features (directory authority, forward compatibility):
2258 - Make the lines of the measured bandwidth file able to contain
2259 their entries in any order. Previously, the node_id entry needed
2260 to come first. Closes ticket 26004.
2262 o Minor features (entry guards):
2263 - Introduce a new torrc option NumPrimaryGuards for controlling the
2264 number of primary guards. Closes ticket 25843.
2266 o Minor features (geoip):
2267 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2268 Country database. Closes ticket 27089.
2270 o Minor features (performance):
2271 - Avoid a needless call to malloc() when processing an incoming
2272 relay cell. Closes ticket 24914.
2273 - Make our timing-wheel code run a tiny bit faster on 32-bit
2274 platforms, by preferring 32-bit math to 64-bit. Closes
2276 - Avoid a needless malloc()/free() pair every time we handle an ntor
2277 handshake. Closes ticket 25150.
2279 o Minor features (Rust, portability):
2280 - Rust cross-compilation is now supported. Closes ticket 25895.
2282 o Minor features (testing):
2283 - Add a unit test for voting_schedule_get_start_of_next_interval().
2284 Closes ticket 26014, and helps make unit test coverage
2286 - A new unittests module specifically for testing the functions in
2287 the (new-ish) bridges.c module has been created with new
2288 unittests, raising the code coverage percentages. Closes 25425.
2289 - We now have improved testing for addressmap_get_virtual_address()
2290 function. This should improve our test coverage, and make our test
2291 coverage more deterministic. Closes ticket 25993.
2293 o Minor features (timekeeping, circuit scheduling):
2294 - When keeping track of how busy each circuit have been recently on
2295 a given connection, use coarse-grained monotonic timers rather
2296 than gettimeofday(). This change should marginally increase
2297 accuracy and performance. Implements part of ticket 25927.
2299 o Minor features (unit tests):
2300 - Test complete bandwidth measurements files, and test that
2301 incomplete bandwidth lines only give warnings when the end of the
2302 header has not been detected. Fixes bug 25947; bugfix
2305 o Minor bugfixes (bandwidth management):
2306 - Consider ourselves "low on write bandwidth" if we have exhausted
2307 our write bandwidth some time in the last second. This was the
2308 documented behavior before, but the actual behavior was to change
2309 this value every TokenBucketRefillInterval. Fixes bug 25828;
2310 bugfix on 0.2.3.5-alpha.
2312 o Minor bugfixes (C correctness):
2313 - Add a missing lock acquisition in the shutdown code of the control
2314 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
2315 Coverity; this is CID 1433643.
2317 o Minor bugfixes (code style):
2318 - Fixed multiple includes of transports.h in src/or/connection.c
2319 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
2320 - Remove the unused variable n_possible from the function
2321 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
2323 o Minor bugfixes (compilation):
2324 - Silence a spurious compiler warning on the GetAdaptersAddresses
2325 function pointer cast. This issue is already fixed by 26481 in
2326 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2327 bugfix on 0.2.3.11-alpha.
2328 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2329 supported, and always fails. Some compilers warn about the
2330 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2332 - Fix a compilation warning on some versions of GCC when building
2333 code that calls routerinfo_get_my_routerinfo() twice, assuming
2334 that the second call will succeed if the first one did. Fixes bug
2335 26269; bugfix on 0.2.8.2-alpha.
2336 - Refrain from compiling unit testing related object files when
2337 --disable-unittests is set to configure script. Fixes bug 24891;
2338 bugfix on 0.2.5.1-alpha.
2339 - The --enable-fatal-warnings flag now affects Rust code as well.
2340 Closes ticket 26245.
2341 - Avoid a compiler warning when casting the return value of
2342 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
2343 26283; bugfix on 0.2.4.10-alpha.
2345 o Minor bugfixes (compilation, windows):
2346 - Don't link or search for pthreads when building for Windows, even
2347 if we are using build environment (like mingw) that provides a
2348 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2350 o Minor bugfixes (continuous integration):
2351 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
2352 - Skip a pair of unreliable key generation tests on Windows, until
2353 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2354 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2356 o Minor bugfixes (control port):
2357 - Respond with more human-readable error messages to GETINFO exit-
2358 policy/* requests. Also, let controller know if an error is
2359 transient (response code 551) or not (response code 552). Fixes
2360 bug 25852; bugfix on 0.2.8.1-alpha.
2361 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
2362 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
2363 on 0.3.3.1-alpha. Patch by "akwizgran".
2364 - Make CIRC_BW event reflect the total of all data sent on a
2365 circuit, including padding and dropped cells. Also fix a mis-
2366 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
2367 bugfix on 0.2.5.2-alpha.
2369 o Minor bugfixes (correctness, flow control):
2370 - Upon receiving a stream-level SENDME cell, verify that our window
2371 has not grown too large. Fixes bug 26214; bugfix on svn
2374 o Minor bugfixes (directory authority):
2375 - When voting for recommended versions, make sure that all of the
2376 versions are well-formed and parsable. Fixes bug 26485; bugfix
2379 o Minor bugfixes (directory client):
2380 - When unverified-consensus is verified, rename it to cached-
2381 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
2382 - Fixed launching a certificate fetch always during the scheduled
2383 periodic consensus fetch by fetching only in those cases when
2384 consensus are waiting for certs. Fixes bug 24740; bugfix
2387 o Minor bugfixes (error reporting):
2388 - Improve tolerance for directory authorities with skewed clocks.
2389 Previously, an authority with a clock more than 60 seconds ahead
2390 could cause a client with a correct clock to warn that the
2391 client's clock was behind. Now the clocks of a majority of
2392 directory authorities have to be ahead of the client before this
2393 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
2395 o Minor bugfixes (in-process restart):
2396 - Always call tor_free_all() when leaving tor_run_main(). When we
2397 did not, restarting tor in-process would cause an assertion
2398 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
2400 o Minor bugfixes (Linux seccomp2 sandbox):
2401 - Fix a bug in our sandboxing rules for the openat() syscall.
2402 Previously, no openat() call would be permitted, which would break
2403 filesystem operations on recent glibc versions. Fixes bug 25440;
2404 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2406 o Minor bugfixes (logging):
2407 - Improve the log message when connection initiators fail to
2408 authenticate direct connections to relays. Fixes bug 26927; bugfix
2411 o Minor bugfixes (onion services):
2412 - Silence a spurious compiler warning in
2413 rend_client_send_introduction(). Fixes bug 27463; bugfix
2415 - Fix bug that causes services to not ever rotate their descriptors
2416 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
2418 - Recompute some consensus information after detecting a clock jump,
2419 or after transitioning from a non-live consensus to a live
2420 consensus. We do this to avoid having an outdated state, and
2421 miscalculating the index for next-generation onion services. Fixes
2422 bug 24977; bugfix on 0.3.2.1-alpha.
2424 o Minor bugfixes (portability):
2425 - Fix compilation of the unit tests on GNU/Hurd, which does not
2426 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
2428 - Work around two different bugs in the OS X 10.10 and later SDKs
2429 that would prevent us from successfully targeting earlier versions
2430 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
2431 - Do not align mmap length, as it is not required by POSIX, and the
2432 getpagesize function is deprecated. Fixes bug 25399; bugfix
2435 o Minor bugfixes (portability, FreeBSD):
2436 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
2437 does not stringify on FreeBSD, so we switch to tor_asprintf().
2438 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
2440 o Minor bugfixes (relay statistics):
2441 - When a relay is collecting internal statistics about how many
2442 create cell requests it has seen of each type, accurately count
2443 the requests from relays that temporarily fall out of the
2444 consensus. (To be extra conservative, we were already ignoring
2445 requests from clients in our counts, and we continue ignoring them
2446 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
2448 o Minor bugfixes (rust):
2449 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
2451 - Protover parsing was accepting the presence of whitespace in
2452 version strings, which the C implementation would choke on, e.g.
2453 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
2454 - Protover parsing was ignoring a 2nd hyphen and everything after
2455 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
2457 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
2458 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
2459 - cd to ${abs_top_builddir}/src/rust before running cargo in
2460 src/test/test_rust.sh. This makes the working directory consistent
2461 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
2463 o Minor bugfixes (single onion services, Tor2web):
2464 - Log a protocol warning when single onion services or Tor2web
2465 clients fail to authenticate direct connections to relays. Fixes
2466 bug 26924; bugfix on 0.2.9.1-alpha.
2468 o Minor bugfixes (test coverage tools):
2469 - Update our "cov-diff" script to handle output from the latest
2470 version of gcov, and to remove extraneous timestamp information
2471 from its output. Fixes bugs 26101 and 26102; bugfix
2474 o Minor bugfixes (testing):
2475 - Disable core dumps in test_bt.sh, to avoid failures in "make
2476 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2477 - When testing workqueue event-cancellation, make sure that we
2478 actually cancel an event, and that cancel each event with equal
2479 probability. (It was previously possible, though extremely
2480 unlikely, for our event-canceling test not to cancel any events.)
2481 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
2482 - Repeat part of the test in test_client_pick_intro() a number of
2483 times, to give it consistent coverage. Fixes bug 25996; bugfix
2485 - Remove randomness from the hs_common/responsible_hsdirs test, so
2486 that it always takes the same path through the function it tests.
2487 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
2488 - Change the behavior of the "channel/outbound" test so that it
2489 never causes a 10-second rollover for the EWMA circuitmux code.
2490 Previously, this behavior would happen randomly, and result in
2491 fluctuating test coverage. Fixes bug 25994; bugfix
2493 - Use X509_new() to allocate certificates that will be freed later
2494 with X509_free(). Previously, some parts of the unit tests had
2495 used tor_malloc_zero(), which is incorrect, and which caused test
2496 failures on Windows when they were built with extra hardening.
2497 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
2499 - While running the circuit_timeout test, fix the PRNG to a
2500 deterministic AES stream, so that the test coverage from this test
2501 will itself be deterministic. Fixes bug 25995; bugfix
2504 o Minor bugfixes (testing, bootstrap):
2505 - When calculating bootstrap progress, check exit policies and the
2506 exit flag. Previously, Tor would only check the exit flag, which
2507 caused race conditions in small and fast networks like chutney.
2508 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
2510 o Minor bugfixes (testing, chutney):
2511 - When running make test-network-all, use the mixed+hs-v2 network.
2512 (A previous fix to chutney removed v3 onion services from the
2513 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
2514 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
2515 - Before running make test-network-all, delete old logs and test
2516 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2519 o Minor bugfixes (testing, openssl compatibility):
2520 - Our "tortls/cert_matches_key" unit test no longer relies on
2521 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2522 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2523 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2525 o Minor bugfixes (v3 onion services):
2526 - Stop sending ed25519 link specifiers in v3 onion service introduce
2527 cells and descriptors, when the rendezvous or introduction point
2528 doesn't support ed25519 link authentication. Fixes bug 26627;
2529 bugfix on 0.3.2.4-alpha.
2531 o Minor bugfixes (vanguards):
2532 - Allow the last hop in a vanguard circuit to be the same as our
2533 first, to prevent the adversary from influencing guard node choice
2534 by choice of last hop. Also prevent the creation of A - B - A
2535 paths, or A - A paths, which are forbidden by relays. Fixes bug
2536 25870; bugfix on 0.3.3.1-alpha.
2538 o Minor bugfixes (Windows, compilation):
2539 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2540 27185; bugfix on 0.2.2.2-alpha.
2542 o Code simplification and refactoring:
2543 - Remove duplicate code in parse_{c,s}method_line and bootstrap
2544 their functionalities into a single function. Fixes bug 6236;
2545 bugfix on 0.2.3.6-alpha.
2546 - We remove the PortForwsrding and PortForwardingHelper options,
2547 related functions, and the port_forwarding tests. These options
2548 were used by the now-deprecated Vidalia to help ordinary users
2549 become Tor relays or bridges. Closes ticket 25409. Patch by
2551 - In order to make the OR and dir checking function in router.c less
2552 confusing we renamed some functions and
2553 consider_testing_reachability() has been split into
2554 router_should_check_reachability() and
2555 router_do_reachability_checks(). Also we improved the documentation
2556 in some functions. Closes ticket 18918.
2557 - Initial work to isolate Libevent usage to a handful of modules in
2558 our codebase, to simplify our call structure, and so that we can
2559 more easily change event loops in the future if needed. Closes
2561 - Introduce a function to call getsockname() and return tor_addr_t,
2562 to save a little complexity throughout the codebase. Closes
2564 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
2565 as hsdir_index is always present. Also, we move hsdir_index_t into
2566 or.h. Closes ticket 23094. Patch by Neel Chauhan.
2567 - Merge functions used for describing nodes and suppress the
2568 functions that do not allocate memory for the output buffer
2569 string. NODE_DESC_BUF_LEN constant and format_node_description()
2570 function cannot be used externally from router.c module anymore.
2571 Closes ticket 25432. Patch by valentecaio.
2572 - Our main loop has been simplified so that all important operations
2573 happen inside events. Previously, some operations had to happen
2574 outside the event loop, to prevent infinite sequences of event
2575 activations. Closes ticket 25374.
2576 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
2577 it in register_intro_circ() and service_intro_point_new(). This
2578 prevents the digest from being re-calculated each time. Closes
2579 ticket 23107. Patch by Neel Chauhan.
2580 - Refactor token-bucket implementations to use a common backend.
2581 Closes ticket 25766.
2582 - Remove extern declaration of stats_n_seconds_working variable from
2583 main, protecting its accesses with get_uptime() and reset_uptime()
2584 functions. Closes ticket 25081, patch by “valentecaio”.
2585 - Remove our previous logic for "cached gettimeofday()" -- our
2586 coarse monotonic timers are fast enough for this purpose, and far
2587 less error-prone. Implements part of ticket 25927.
2588 - Remove the return value for fascist_firewall_choose_address_base(),
2589 and sister functions such as fascist_firewall_choose_address_node()
2590 and fascist_firewall_choose_address_rs(). Also, while we're here,
2591 initialize the ap argument as leaving it uninitialized can pose a
2592 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
2593 - Rename two fields of connection_t struct. timestamp_lastwritten is
2594 renamed to timestamp_last_write_allowed and timestamp_lastread is
2595 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
2597 - Since Tor requires C99, remove our old workaround code for libc
2598 implementations where free(NULL) doesn't work. Closes ticket 24484.
2599 - Use our standard rate-limiting code to deal with excessive
2600 libevent failures, rather than the hand-rolled logic we had
2601 before. Closes ticket 26016.
2602 - We remove the return value of node_get_prim_orport() and
2603 node_get_prim_dirport(), and introduce node_get_prim_orport() in
2604 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
2605 check for a null address. Closes ticket 23873. Patch by
2607 - We switch to should_record_bridge_info() in
2608 geoip_note_client_seen() and options_need_geoip_info() instead of
2609 accessing the configuration values directly. Fixes bug 25290;
2610 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
2612 o Deprecated features:
2613 - As we are not recommending 0.2.5 anymore, we require relays that
2614 once had an ed25519 key associated with their RSA key to always
2615 have that key, instead of allowing them to drop back to a version
2616 that didn't support ed25519. This means they need to use a new RSA
2617 key if they want to downgrade to an older version of tor without
2618 ed25519. Closes ticket 20522.
2621 - Directory authorities will no longer support voting according to
2622 any consensus method before consensus method 25. This keeps
2623 authorities compatible with all authorities running 0.2.9.8 and
2624 later, and does not break any clients or relays. Implements ticket
2625 24378 and proposal 290.
2626 - The PortForwarding and PortForwardingHelper features have been
2627 removed. The reasoning is, given that implementations of NAT
2628 traversal protocols within common consumer grade routers are
2629 frequently buggy, and that the target audience for a NAT punching
2630 feature is a perhaps less-technically-inclined relay operator,
2631 when the helper fails to setup traversal the problems are usually
2632 deep, ugly, and very router specific, making them horrendously
2633 impossible for technical support to reliable assist with, and thus
2634 resulting in frustration all around. Unfortunately, relay
2635 operators who would like to run relays behind NATs will need to
2636 become more familiar with the port forwarding configurations on
2637 their local router. Closes 25409.
2638 - The TestingEnableTbEmptyEvent option has been removed. It was used
2639 in testing simulations to measure how often connection buckets
2640 were emptied, in order to improve our scheduling, but it has not
2641 been actively used in years. Closes ticket 25760.
2642 - The old "round-robin" circuit multiplexer (circuitmux)
2643 implementation has been removed, along with a fairly large set of
2644 code that existed to support it. It has not been the default
2645 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
2646 but it still required an unreasonable amount of memory and CPU.
2647 Closes ticket 25268.
2650 Changes in version 0.3.3.9 - 2018-07-13
2651 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
2652 bridge relays should upgrade.
2654 o Directory authority changes:
2655 - The "Bifroest" bridge authority has been retired; the new bridge
2656 authority is "Serge", and it is operated by George from the
2657 TorBSD project. Closes ticket 26771.
2660 Changes in version 0.3.2.11 - 2018-07-13
2661 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
2662 bridge relays should upgrade. We also take this opportunity to backport
2665 o Directory authority changes:
2666 - The "Bifroest" bridge authority has been retired; the new bridge
2667 authority is "Serge", and it is operated by George from the
2668 TorBSD project. Closes ticket 26771.
2670 o Directory authority changes (backport from 0.3.3.7):
2671 - Add an IPv6 address for the "dannenberg" directory authority.
2672 Closes ticket 26343.
2674 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
2675 - When directory authorities read a zero-byte bandwidth file, they
2676 would previously log a warning with the contents of an
2677 uninitialised buffer. They now log a warning about the empty file
2678 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
2680 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
2681 - Correctly detect when onion services get disabled after HUP. Fixes
2682 bug 25761; bugfix on 0.3.2.1.
2684 o Minor features (sandbox, backport from 0.3.3.4-alpha):
2685 - Explicitly permit the poll() system call when the Linux
2686 seccomp2-based sandbox is enabled: apparently, some versions of
2687 libc use poll() when calling getpwnam(). Closes ticket 25313.
2689 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
2690 - Update the Travis CI configuration to use the stable Rust channel,
2691 now that we have decided to require that. Closes ticket 25714.
2693 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
2694 - Our .travis.yml configuration now includes support for testing the
2695 results of "make distcheck". (It's not uncommon for "make check"
2696 to pass but "make distcheck" to fail.) Closes ticket 25814.
2697 - Our Travis CI configuration now integrates with the Coveralls
2698 coverage analysis tool. Closes ticket 25818.
2700 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
2701 - Add several checks to detect whether Tor relays are uploading
2702 their descriptors without specifying why they regenerated them.
2703 Diagnostic for ticket 25686.
2705 o Minor features (compilation, backport from 0.3.4.4-rc):
2706 - When building Tor, prefer to use Python 3 over Python 2, and more
2707 recent (contemplated) versions over older ones. Closes
2710 o Minor features (geoip):
2711 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2712 Country database. Closes ticket 26674.
2714 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
2715 - Upon receiving a malformed connected cell, stop processing the
2716 cell immediately. Previously we would mark the connection for
2717 close, but continue processing the cell as if the connection were
2718 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
2720 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
2721 - Allow the nanosleep() system call, which glibc uses to implement
2722 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
2724 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
2725 - When running the hs_ntor_ref.py test, make sure only to pass
2726 strings (rather than "bytes" objects) to the Python subprocess
2727 module. Python 3 on Windows seems to require this. Fixes bug
2728 26535; bugfix on 0.3.1.1-alpha.
2729 - When running the ntor_ref.py test, make sure only to pass strings
2730 (rather than "bytes" objects) to the Python subprocess module.
2731 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
2734 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
2735 - Work around a change in OpenSSL 1.1.1 where return values that
2736 would previously indicate "no password" now indicate an empty
2737 password. Without this workaround, Tor instances running with
2738 OpenSSL 1.1.1 would accept descriptors that other Tor instances
2739 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
2741 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
2742 - Document that the PerConnBW{Rate,Burst} options will fall back to
2743 their corresponding consensus parameters only if those parameters
2744 are set. Previously we had claimed that these values would always
2745 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
2747 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
2748 - Fix a compilation warning on some versions of GCC when building
2749 code that calls routerinfo_get_my_routerinfo() twice, assuming
2750 that the second call will succeed if the first one did. Fixes bug
2751 26269; bugfix on 0.2.8.2-alpha.
2753 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
2754 - Don't consider Tor running as a client if the ControlPort is open,
2755 but no actual client ports are open. Fixes bug 26062; bugfix
2758 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
2759 - Prevent a possible out-of-bounds smartlist read in
2760 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
2762 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
2763 - Fix a very unlikely (impossible, we believe) null pointer
2764 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
2765 Coverity; this is CID 1430932.
2767 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
2768 - Fix a memory leak when a v3 onion service is configured and gets a
2769 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
2770 - When parsing the descriptor signature, look for the token plus an
2771 extra white-space at the end. This is more correct but also will
2772 allow us to support new fields that might start with "signature".
2773 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
2775 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
2776 - Relays now correctly block attempts to re-extend to the previous
2777 relay by Ed25519 identity. Previously they would warn in this
2778 case, but not actually reject the attempt. Fixes bug 26158; bugfix
2781 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
2782 - Avoid a crash when running with DirPort set but ORPort turned off.
2783 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
2785 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
2786 - Silence unused-const-variable warnings in zstd.h with some GCC
2787 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
2789 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
2790 - Avoid intermittent test failures due to a test that had relied on
2791 onion service introduction point creation finishing within 5
2792 seconds of real clock time. Fixes bug 25450; bugfix
2795 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
2796 - Fix a C99 compliance issue in our configuration script that caused
2797 compilation issues when compiling Tor with certain versions of
2798 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
2800 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
2801 - Fix a number of small memory leaks identified by coverity. Fixes
2802 bug 26467; bugfix on numerous Tor versions.
2804 o Code simplification and refactoring (backport from 0.3.3.5-rc):
2805 - Move the list of default directory authorities to its own file.
2806 Closes ticket 24854. Patch by "beastr0".
2809 Changes in version 0.2.9.16 - 2018-07-13
2810 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
2811 bridge relays should upgrade. We also take this opportunity to backport
2814 o Directory authority changes:
2815 - The "Bifroest" bridge authority has been retired; the new bridge
2816 authority is "Serge", and it is operated by George from the
2817 TorBSD project. Closes ticket 26771.
2819 o Directory authority changes (backport from 0.3.3.7):
2820 - Add an IPv6 address for the "dannenberg" directory authority.
2821 Closes ticket 26343.
2823 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
2824 - When directory authorities read a zero-byte bandwidth file, they
2825 would previously log a warning with the contents of an
2826 uninitialised buffer. They now log a warning about the empty file
2827 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
2829 o Minor features (sandbox, backport from 0.3.3.4-alpha):
2830 - Explicitly permit the poll() system call when the Linux
2831 seccomp2-based sandbox is enabled: apparently, some versions of
2832 libc use poll() when calling getpwnam(). Closes ticket 25313.
2834 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
2835 - Our .travis.yml configuration now includes support for testing the
2836 results of "make distcheck". (It's not uncommon for "make check"
2837 to pass but "make distcheck" to fail.) Closes ticket 25814.
2838 - Our Travis CI configuration now integrates with the Coveralls
2839 coverage analysis tool. Closes ticket 25818.
2841 o Minor features (compilation, backport from 0.3.4.4-rc):
2842 - When building Tor, prefer to use Python 3 over Python 2, and more
2843 recent (contemplated) versions over older ones. Closes
2846 o Minor features (geoip):
2847 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2848 Country database. Closes ticket 26674.
2850 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
2851 - Upon receiving a malformed connected cell, stop processing the
2852 cell immediately. Previously we would mark the connection for
2853 close, but continue processing the cell as if the connection were
2854 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
2856 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
2857 - Allow the nanosleep() system call, which glibc uses to implement
2858 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
2860 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
2861 - When running the ntor_ref.py test, make sure only to pass strings
2862 (rather than "bytes" objects) to the Python subprocess module.
2863 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
2866 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
2867 - Work around a change in OpenSSL 1.1.1 where return values that
2868 would previously indicate "no password" now indicate an empty
2869 password. Without this workaround, Tor instances running with
2870 OpenSSL 1.1.1 would accept descriptors that other Tor instances
2871 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
2873 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
2874 - Fix a compilation warning on some versions of GCC when building
2875 code that calls routerinfo_get_my_routerinfo() twice, assuming
2876 that the second call will succeed if the first one did. Fixes bug
2877 26269; bugfix on 0.2.8.2-alpha.
2879 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
2880 - Don't consider Tor running as a client if the ControlPort is open,
2881 but no actual client ports are open. Fixes bug 26062; bugfix
2884 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
2885 - Prevent a possible out-of-bounds smartlist read in
2886 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
2888 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
2889 - Fix a very unlikely (impossible, we believe) null pointer
2890 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
2891 Coverity; this is CID 1430932.
2893 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
2894 - Fix a number of small memory leaks identified by coverity. Fixes
2895 bug 26467; bugfix on numerous Tor versions.
2897 o Code simplification and refactoring (backport from 0.3.3.5-rc):
2898 - Move the list of default directory authorities to its own file.
2899 Closes ticket 24854. Patch by "beastr0".
2902 Changes in version 0.3.3.8 - 2018-07-09
2903 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
2904 fixes for a memory leak affecting directory authorities.
2906 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
2907 - Stop leaking memory on directory authorities when planning to
2908 vote. This bug was crashing authorities by exhausting their
2909 memory. Fixes bug 26435; bugfix on 0.3.3.6.
2911 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
2912 - Make sure that failing tests in Rust will actually cause the build
2913 to fail: previously, they were ignored. Fixes bug 26258; bugfix
2916 o Minor features (compilation, backport from 0.3.4.4-rc):
2917 - When building Tor, prefer to use Python 3 over Python 2, and more
2918 recent (contemplated) versions over older ones. Closes
2921 o Minor features (geoip):
2922 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2923 Country database. Closes ticket 26674.
2925 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
2926 - Add several checks to detect whether Tor relays are uploading
2927 their descriptors without specifying why they regenerated them.
2928 Diagnostic for ticket 25686.
2930 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
2931 - Don't count path selection failures as circuit build failures.
2932 This change should eliminate cases where Tor blames its guard or
2933 the network for situations like insufficient microdescriptors
2934 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
2937 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
2938 - Fix a compilation warning on some versions of GCC when building
2939 code that calls routerinfo_get_my_routerinfo() twice, assuming
2940 that the second call will succeed if the first one did. Fixes bug
2941 26269; bugfix on 0.2.8.2-alpha.
2943 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
2944 - Handle the HSADDRESS= argument to the HSPOST command properly.
2945 (Previously, this argument was misparsed and thus ignored.) Fixes
2946 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
2948 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
2949 - Fix a number of small memory leaks identified by coverity. Fixes
2950 bug 26467; bugfix on numerous Tor versions.
2952 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
2953 - Relays now correctly block attempts to re-extend to the previous
2954 relay by Ed25519 identity. Previously they would warn in this
2955 case, but not actually reject the attempt. Fixes bug 26158; bugfix
2958 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
2959 - When shutting down, Tor now clears all the flags in the control.c
2960 module. This should prevent a bug where authentication cookies are
2961 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
2963 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
2964 - When running the hs_ntor_ref.py test, make sure only to pass
2965 strings (rather than "bytes" objects) to the Python subprocess
2966 module. Python 3 on Windows seems to require this. Fixes bug
2967 26535; bugfix on 0.3.1.1-alpha.
2968 - When running the ntor_ref.py test, make sure only to pass strings
2969 (rather than "bytes" objects) to the Python subprocess module.
2970 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
2974 Changes in version 0.3.3.7 - 2018-06-12
2975 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
2976 fixes for bugs affecting compatibility and stability.
2978 o Directory authority changes:
2979 - Add an IPv6 address for the "dannenberg" directory authority.
2980 Closes ticket 26343.
2982 o Minor features (geoip):
2983 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
2984 Country database. Closes ticket 26351.
2986 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
2987 - Work around a change in OpenSSL 1.1.1 where return values that
2988 would previously indicate "no password" now indicate an empty
2989 password. Without this workaround, Tor instances running with
2990 OpenSSL 1.1.1 would accept descriptors that other Tor instances
2991 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
2993 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
2994 - Silence unused-const-variable warnings in zstd.h with some GCC
2995 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
2997 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
2998 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
2999 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
3000 miscounting the total number of circuits for these field values.)
3001 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
3003 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3004 - Prevent a possible out-of-bounds smartlist read in
3005 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3007 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
3008 - Only select relays when they have the descriptors we prefer to use
3009 for them. This change fixes a bug where we could select a relay
3010 because it had _some_ descriptor, but reject it later with a
3011 nonfatal assertion error because it didn't have the exact one we
3012 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
3015 Changes in version 0.3.3.6 - 2018-05-22
3016 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
3017 backports several important fixes from the 0.3.4.1-alpha.
3019 The Tor 0.3.3 series includes controller support and other
3020 improvements for v3 onion services, official support for embedding Tor
3021 within other applications, and our first non-trivial module written in
3022 the Rust programming language. (Rust is still not enabled by default
3023 when building Tor.) And as usual, there are numerous other smaller
3024 bugfixes, features, and improvements.
3026 Below are the changes since 0.3.2.10. For a list of only the changes
3027 since 0.3.3.5-rc, see the ChangeLog file.
3029 o New system requirements:
3030 - When built with Rust, Tor now depends on version 0.2.39 of the
3031 libc crate. Closes tickets 25310 and 25664.
3033 o Major features (embedding):
3034 - There is now a documented stable API for programs that need to
3035 embed Tor. See tor_api.h for full documentation and known bugs.
3036 Closes ticket 23684.
3037 - Tor now has support for restarting in the same process.
3038 Controllers that run Tor using the "tor_api.h" interface can now
3039 restart Tor after Tor has exited. This support is incomplete,
3040 however: we fixed crash bugs that prevented it from working at
3041 all, but many bugs probably remain, including a possibility of
3042 security issues. Implements ticket 24581.
3044 o Major features (IPv6, directory documents):
3045 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
3046 consensus. This information makes it easier for IPv6 clients to
3047 bootstrap and choose reachable entry guards. Implements
3049 - Add consensus method 28, which removes IPv6 ORPorts from
3050 microdescriptors. Now that the consensus contains IPv6 ORPorts,
3051 they are redundant in microdescs. This change will be used by Tor
3052 clients on 0.2.8.x and later. (That is to say, with all Tor
3053 clients that have IPv6 bootstrap and guard support.) Implements
3055 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
3056 set by different numbers of authorities. Fixes 23870
3059 o Major features (onion service v3, control port):
3060 - The control port now supports commands and events for v3 onion
3061 services. It is now possible to create ephemeral v3 services using
3062 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
3063 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
3064 DEL_ONION) have been extended to support v3 onion services. Closes
3065 ticket 20699; implements proposal 284.
3067 o Major features (onion services):
3068 - Provide torrc options to pin the second and third hops of onion
3069 service circuits to a list of nodes. The option HSLayer2Guards
3070 pins the second hop, and the option HSLayer3Guards pins the third
3071 hop. These options are for use in conjunction with experiments
3072 with "vanguards" for preventing guard enumeration attacks. Closes
3074 - When v3 onion service clients send introduce cells, they now
3075 include the IPv6 address of the rendezvous point, if it has one.
3076 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
3077 in future Tor versions, IPv6-only v3 single onion services will be
3078 able to use IPv6 addresses to connect directly to the rendezvous
3079 point. Closes ticket 23577. Patch by Neel Chauhan.
3081 o Major features (relay):
3082 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
3083 operator to use a more reasonable ("reduced") exit policy, rather
3084 than the default one. If you want to run an exit node without
3085 thinking too hard about which ports to allow, this one is for you.
3086 Closes ticket 13605. Patch from Neel Chauhan.
3088 o Major features (rust, portability, experimental):
3089 - Tor now ships with an optional implementation of one of its
3090 smaller modules (protover.c) in the Rust programming language. To
3091 try it out, install a Rust build environment, and configure Tor
3092 with "--enable-rust --enable-cargo-online-mode". This should not
3093 cause any user-visible changes, but should help us gain more
3094 experience with Rust, and plan future Rust integration work.
3095 Implementation by Chelsea Komlo. Closes ticket 22840.
3097 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
3098 - When directory authorities read a zero-byte bandwidth file, they
3099 would previously log a warning with the contents of an
3100 uninitialised buffer. They now log a warning about the empty file
3101 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3103 o Major bugfixes (security, directory authority, denial-of-service):
3104 - Fix a bug that could have allowed an attacker to force a directory
3105 authority to use up all its RAM by passing it a maliciously
3106 crafted protocol versions string. Fixes bug 25517; bugfix on
3107 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
3109 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
3110 - Avoid a rare assertion failure in the circuit build timeout code
3111 if we fail to allow any circuits to actually complete. Fixes bug
3112 25733; bugfix on 0.2.2.2-alpha.
3114 o Major bugfixes (netflow padding):
3115 - Stop adding unneeded channel padding right after we finish
3116 flushing to a connection that has been trying to flush for many
3117 seconds. Instead, treat all partial or complete flushes as
3118 activity on the channel, which will defer the time until we need
3119 to add padding. This fix should resolve confusing and scary log
3120 messages like "Channel padding timeout scheduled 221453ms in the
3121 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
3123 o Major bugfixes (networking):
3124 - Tor will no longer reject IPv6 address strings from Tor Browser
3125 when they are passed as hostnames in SOCKS5 requests. Fixes bug
3126 25036, bugfix on Tor 0.3.1.2.
3128 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
3129 - Correctly detect when onion services get disabled after HUP. Fixes
3130 bug 25761; bugfix on 0.3.2.1.
3132 o Major bugfixes (performance, load balancing):
3133 - Directory authorities no longer vote in favor of the Guard flag
3134 for relays without directory support. Starting in Tor
3135 0.3.0.1-alpha, clients have been avoiding using such relays in the
3136 Guard position, leading to increasingly broken load balancing for
3137 the 5%-or-so of Guards that don't advertise directory support.
3138 Fixes bug 22310; bugfix on 0.3.0.6.
3140 o Major bugfixes (relay):
3141 - If we have failed to connect to a relay and received a connection
3142 refused, timeout, or similar error (at the TCP level), do not try
3143 that same address/port again for 60 seconds after the failure has
3144 occurred. Fixes bug 24767; bugfix on 0.0.6.
3146 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
3147 - Impose a limit on circuit cell queue size. The limit can be
3148 controlled by a consensus parameter. Fixes bug 25226; bugfix
3151 o Minor features (cleanup):
3152 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
3153 when it stops. Closes ticket 23271.
3155 o Minor features (compatibility, backport from 0.3.4.1-alpha):
3156 - Avoid some compilation warnings with recent versions of LibreSSL.
3157 Closes ticket 26006.
3159 o Minor features (config options):
3160 - Change the way the default value for MaxMemInQueues is calculated.
3161 We now use 40% of the hardware RAM if the system has 8 GB RAM or
3162 more. Otherwise we use the former value of 75%. Closes
3165 o Minor features (continuous integration):
3166 - Update the Travis CI configuration to use the stable Rust channel,
3167 now that we have decided to require that. Closes ticket 25714.
3169 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3170 - Our .travis.yml configuration now includes support for testing the
3171 results of "make distcheck". (It's not uncommon for "make check"
3172 to pass but "make distcheck" to fail.) Closes ticket 25814.
3173 - Our Travis CI configuration now integrates with the Coveralls
3174 coverage analysis tool. Closes ticket 25818.
3176 o Minor features (defensive programming):
3177 - Most of the functions in Tor that free objects have been replaced
3178 with macros that free the objects and set the corresponding
3179 pointers to NULL. This change should help prevent a large class of
3180 dangling pointer bugs. Closes ticket 24337.
3181 - Where possible, the tor_free() macro now only evaluates its input
3182 once. Part of ticket 24337.
3183 - Check that microdesc ed25519 ids are non-zero in
3184 node_get_ed25519_id() before returning them. Implements ticket
3185 24001, patch by "aruna1234".
3187 o Minor features (directory authority):
3188 - When directory authorities are unable to add signatures to a
3189 pending consensus, log the reason why. Closes ticket 24849.
3191 o Minor features (embedding):
3192 - Tor can now start with a preauthenticated control connection
3193 created by the process that launched it. This feature is meant for
3194 use by programs that want to launch and manage a Tor process
3195 without allowing other programs to manage it as well. For more
3196 information, see the __OwningControllerFD option documented in
3197 control-spec.txt. Closes ticket 23900.
3198 - On most errors that would cause Tor to exit, it now tries to
3199 return from the tor_main() function, rather than calling the
3200 system exit() function. Most users won't notice a difference here,
3201 but it should be significant for programs that run Tor inside a
3202 separate thread: they should now be able to survive Tor's exit
3203 conditions rather than having Tor shut down the entire process.
3204 Closes ticket 23848.
3205 - Applications that want to embed Tor can now tell Tor not to
3206 register any of its own POSIX signal handlers, using the
3207 __DisableSignalHandlers option. Closes ticket 24588.
3209 o Minor features (fallback directory list):
3210 - Avoid selecting fallbacks that change their IP addresses too
3211 often. Select more fallbacks by ignoring the Guard flag, and
3212 allowing lower cutoffs for the Running and V2Dir flags. Also allow
3213 a lower bandwidth, and a higher number of fallbacks per operator
3214 (5% of the list). Implements ticket 24785.
3215 - Update the fallback whitelist and blacklist based on opt-ins and
3216 relay changes. Closes tickets 22321, 24678, 22527, 24135,
3219 o Minor features (fallback directory mirror configuration):
3220 - Add a nickname to each fallback in a C comment. This makes it
3221 easier for operators to find their relays, and allows stem to use
3222 nicknames to identify fallbacks. Implements ticket 24600.
3223 - Add a type and version header to the fallback directory mirror
3224 file. Also add a delimiter to the end of each fallback entry. This
3225 helps external parsers like stem and Relay Search. Implements
3227 - Add an extrainfo cache flag for each fallback in a C comment. This
3228 allows stem to use fallbacks to fetch extra-info documents, rather
3229 than using authorities. Implements ticket 22759.
3230 - Add the generateFallbackDirLine.py script for automatically
3231 generating fallback directory mirror lines from relay fingerprints.
3232 No more typos! Add the lookupFallbackDirContact.py script for
3233 automatically looking up operator contact info from relay
3234 fingerprints. Implements ticket 24706, patch by teor and atagar.
3235 - Reject any fallback directory mirror that serves an expired
3236 consensus. Implements ticket 20942, patch by "minik".
3237 - Remove commas and equals signs from external string inputs to the
3238 fallback list. This avoids format confusion attacks. Implements
3240 - Remove the "weight=10" line from fallback directory mirror
3241 entries. Ticket 24681 will maintain the current fallback weights
3242 by changing Tor's default fallback weight to 10. Implements
3244 - Stop logging excessive information about fallback netblocks.
3245 Implements ticket 24791.
3247 o Minor features (forward-compatibility):
3248 - If a relay supports some link authentication protocol that we do
3249 not recognize, then include that relay's ed25519 key when telling
3250 other relays to extend to it. Previously, we treated future
3251 versions as if they were too old to support ed25519 link
3252 authentication. Closes ticket 20895.
3254 o Minor features (geoip):
3255 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
3256 database. Closes ticket 26104.
3258 o Minor features (heartbeat):
3259 - Add onion service information to our heartbeat logs, displaying
3260 stats about the activity of configured onion services. Closes
3263 o Minor features (instrumentation, development):
3264 - Add the MainloopStats option to allow developers to get
3265 instrumentation information from the main event loop via the
3266 heartbeat messages. We hope to use this to improve Tor's behavior
3267 when it's trying to sleep. Closes ticket 24605.
3269 o Minor features (IPv6):
3270 - Make IPv6-only clients wait for microdescs for relays, even if we
3271 were previously using descriptors (or were using them as a bridge)
3272 and have a cached descriptor for them. Implements ticket 23827.
3273 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
3274 them, rather than waiting to download microdescriptors. Implements
3277 o Minor features (log messages):
3278 - Improve log message in the out-of-memory handler to include
3279 information about memory usage from the different compression
3280 backends. Closes ticket 25372.
3281 - Improve a warning message that happens when we fail to re-parse an
3282 old router because of an expired certificate. Closes ticket 20020.
3283 - Make the log more quantitative when we hit MaxMemInQueues
3284 threshold exposing some values. Closes ticket 24501.
3286 o Minor features (logging):
3287 - Clarify the log messages produced when getrandom() or a related
3288 entropy-generation mechanism gives an error. Closes ticket 25120.
3289 - Added support for the Android logging subsystem. Closes
3292 o Minor features (performance):
3293 - Support predictive circuit building for onion service circuits
3294 with multiple layers of guards. Closes ticket 23101.
3295 - Use stdatomic.h where available, rather than mutexes, to implement
3296 atomic_counter_t. Closes ticket 23953.
3298 o Minor features (performance, 32-bit):
3299 - Improve performance on 32-bit systems by avoiding 64-bit division
3300 when calculating the timestamp in milliseconds for channel padding
3301 computations. Implements ticket 24613.
3302 - Improve performance on 32-bit systems by avoiding 64-bit division
3303 when timestamping cells and buffer chunks for OOM calculations.
3304 Implements ticket 24374.
3306 o Minor features (performance, OSX, iOS):
3307 - Use the mach_approximate_time() function (when available) to
3308 implement coarse monotonic time. Having a coarse time function
3309 should avoid a large number of system calls, and improve
3310 performance slightly, especially under load. Closes ticket 24427.
3312 o Minor features (performance, windows):
3313 - Improve performance on Windows Vista and Windows 7 by adjusting
3314 TCP send window size according to the recommendation from
3315 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
3318 o Minor features (sandbox):
3319 - Explicitly permit the poll() system call when the Linux
3320 seccomp2-based sandbox is enabled: apparently, some versions of
3321 libc use poll() when calling getpwnam(). Closes ticket 25313.
3323 o Minor features (storage, configuration):
3324 - Users can store cached directory documents somewhere other than
3325 the DataDirectory by using the CacheDirectory option. Similarly,
3326 the storage location for relay's keys can be overridden with the
3327 KeyDirectory option. Closes ticket 22703.
3329 o Minor features (testing):
3330 - Add a "make test-rust" target to run the rust tests only. Closes
3333 o Minor features (testing, debugging, embedding):
3334 - For development purposes, Tor now has a mode in which it runs for
3335 a few seconds, then stops, and starts again without exiting the
3336 process. This mode is meant to help us debug various issues with
3337 ticket 23847. To use this feature, compile with
3338 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
3339 environment variable. This is expected to crash a lot, and is
3340 really meant for developers only. It will likely be removed in a
3341 future release. Implements ticket 24583.
3343 o Minor bugfixes (build, rust):
3344 - Fix output of autoconf checks to display success messages for Rust
3345 dependencies and a suitable rustc compiler version. Fixes bug
3346 24612; bugfix on 0.3.1.3-alpha.
3347 - Don't pass the --quiet option to cargo: it seems to suppress some
3348 errors, which is not what we want to do when building. Fixes bug
3349 24518; bugfix on 0.3.1.7.
3350 - Build correctly when building from outside Tor's source tree with
3351 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
3354 o Minor bugfixes (C correctness):
3355 - Fix a very unlikely (impossible, we believe) null pointer
3356 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3357 Coverity; this is CID 1430932.
3359 o Minor bugfixes (channel, client):
3360 - Better identify client connection when reporting to the geoip
3361 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
3363 o Minor bugfixes (circuit, cannibalization):
3364 - Don't cannibalize preemptively-built circuits if we no longer
3365 recognize their first hop. This situation can happen if our Guard
3366 relay went off the consensus after the circuit was created. Fixes
3367 bug 24469; bugfix on 0.0.6.
3369 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3370 - Don't consider Tor running as a client if the ControlPort is open,
3371 but no actual client ports are open. Fixes bug 26062; bugfix
3374 o Minor bugfixes (compilation):
3375 - Fix a C99 compliance issue in our configuration script that caused
3376 compilation issues when compiling Tor with certain versions of
3377 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
3379 o Minor bugfixes (controller):
3380 - Restore the correct operation of the RESOLVE command, which had
3381 been broken since we added the ability to enable/disable DNS on
3382 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
3383 - Avoid a (nonfatal) assertion failure when extending a one-hop
3384 circuit from the controller to become a multihop circuit. Fixes
3385 bug 24903; bugfix on 0.2.5.2-alpha.
3387 o Minor bugfixes (correctness):
3388 - Remove a nonworking, unnecessary check to see whether a circuit
3389 hop's identity digest was set when the circuit failed. Fixes bug
3390 24927; bugfix on 0.2.4.4-alpha.
3392 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3393 - Upon receiving a malformed connected cell, stop processing the
3394 cell immediately. Previously we would mark the connection for
3395 close, but continue processing the cell as if the connection were
3396 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3398 o Minor bugfixes (directory authorities, IPv6):
3399 - When creating a routerstatus (vote) from a routerinfo (descriptor),
3400 set the IPv6 address to the unspecified IPv6 address, and
3401 explicitly initialize the port to zero. Fixes bug 24488; bugfix
3404 o Minor bugfixes (documentation):
3405 - Document that the PerConnBW{Rate,Burst} options will fall back to
3406 their corresponding consensus parameters only if those parameters
3407 are set. Previously we had claimed that these values would always
3408 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
3410 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
3411 - Stop saying in the manual that clients cache ipv4 dns answers from
3412 exit relays. We haven't used them since 0.2.6.3-alpha, and in
3413 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
3414 we forgot to say so in the man page. Fixes bug 26052; bugfix
3417 o Minor bugfixes (exit relay DNS retries):
3418 - Re-attempt timed-out DNS queries 3 times before failure, since our
3419 timeout is 5 seconds for them, but clients wait 10-15. Also allow
3420 slightly more timeouts per resolver when an exit has multiple
3421 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
3423 o Minor bugfixes (fallback directory mirrors):
3424 - Make updateFallbackDirs.py search harder for python. (Some OSs
3425 don't put it in /usr/bin.) Fixes bug 24708; bugfix
3428 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
3429 - When hibernating, close connections normally and allow them to
3430 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
3432 - Do not attempt to launch self-reachability tests when entering
3433 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
3434 - Resolve several bugs related to descriptor fetching on bridge
3435 clients with bandwidth accounting enabled. (This combination is
3436 not recommended!) Fixes a case of bug 12062; bugfix
3438 - When hibernating, do not attempt to launch DNS checks. Fixes a
3439 case of bug 12062; bugfix on 0.1.2.2-alpha.
3440 - When hibernating, do not try to upload or download descriptors.
3441 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
3443 o Minor bugfixes (IPv6, bridges):
3444 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
3445 bugfix on 0.2.8.2-alpha.
3446 - Tor now sets IPv6 address in the routerstatus as well as in the
3447 router descriptors when updating addresses for a bridge. Closes
3448 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
3450 o Minor bugfixes (Linux seccomp2 sandbox):
3451 - When running with the sandbox enabled, reload configuration files
3452 correctly even when %include was used. Previously we would crash.
3453 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
3455 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3456 - Allow the nanosleep() system call, which glibc uses to implement
3457 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3459 o Minor bugfixes (logging):
3460 - Fix a (mostly harmless) race condition when invoking
3461 LOG_PROTOCOL_WARN message from a subthread while the torrc options
3462 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
3464 o Minor bugfixes (man page, SocksPort):
3465 - Remove dead code from the old "SocksSocket" option, and rename
3466 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old
3467 option still works, but is deprecated. Fixes bug 24343; bugfix
3470 o Minor bugfixes (memory leaks):
3471 - Avoid possible at-exit memory leaks related to use of Libevent's
3472 event_base_once() function. (This function tends to leak memory if
3473 the event_base is closed before the event fires.) Fixes bug 24584;
3474 bugfix on 0.2.8.1-alpha.
3475 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
3478 o Minor bugfixes (network IPv6 test):
3479 - Tor's test scripts now check if "ping -6 ::1" works when the user
3480 runs "make test-network-all". Fixes bug 24677; bugfix on
3481 0.2.9.3-alpha. Patch by "ffmancera".
3483 o Minor bugfixes (networking):
3484 - string_is_valid_hostname() will not consider IP strings to be
3485 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
3487 o Minor bugfixes (onion service v3):
3488 - Avoid an assertion failure when the next onion service descriptor
3489 rotation type is out of sync with the consensus's valid-after
3490 time. Instead, log a warning message with extra information, so we
3491 can better hunt down the cause of this assertion. Fixes bug 25306;
3492 bugfix on 0.3.2.1-alpha.
3494 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
3495 - Fix a memory leak when a v3 onion service is configured and gets a
3496 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
3497 - When parsing the descriptor signature, look for the token plus an
3498 extra white-space at the end. This is more correct but also will
3499 allow us to support new fields that might start with "signature".
3500 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
3502 o Minor bugfixes (onion services):
3503 - If we are configured to offer a single onion service, don't log
3504 long-term established one hop rendezvous points in the heartbeat.
3505 Fixes bug 25116; bugfix on 0.2.9.6-rc.
3507 o Minor bugfixes (performance):
3508 - Reduce the number of circuits that will be opened at once during
3509 the circuit build timeout phase. This is done by increasing the
3510 idle timeout to 3 minutes, and lowering the maximum number of
3511 concurrent learning circuits to 10. Fixes bug 24769; bugfix
3513 - Avoid calling protocol_list_supports_protocol() from inside tight
3514 loops when running with cached routerinfo_t objects. Instead,
3515 summarize the relevant protocols as flags in the routerinfo_t, as
3516 we do for routerstatus_t objects. This change simplifies our code
3517 a little, and saves a large amount of short-term memory allocation
3518 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
3520 o Minor bugfixes (performance, timeouts):
3521 - Consider circuits for timeout as soon as they complete a hop. This
3522 is more accurate than applying the timeout in
3523 circuit_expire_building() because that function is only called
3524 once per second, which is now too slow for typical timeouts on the
3525 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
3526 - Use onion service circuits (and other circuits longer than 3 hops)
3527 to calculate a circuit build timeout. Previously, Tor only
3528 calculated its build timeout based on circuits that planned to be
3529 exactly 3 hops long. With this change, we include measurements
3530 from all circuits at the point where they complete their third
3531 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
3533 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
3534 - Avoid a crash when running with DirPort set but ORPort turned off.
3535 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
3537 o Minor bugfixes (Rust FFI):
3538 - Fix a minor memory leak which would happen whenever the C code
3539 would call the Rust implementation of
3540 protover_get_supported_protocols(). This was due to the C version
3541 returning a static string, whereas the Rust version newly allocated
3542 a CString to pass across the FFI boundary. Consequently, the C
3543 code was not expecting to need to free() what it was given. Fixes
3544 bug 25127; bugfix on 0.3.2.1-alpha.
3546 o Minor bugfixes (spelling):
3547 - Use the "misspell" tool to detect and fix typos throughout the
3548 source code. Fixes bug 23650; bugfix on various versions of Tor.
3549 Patch from Deepesh Pathak.
3551 o Minor bugfixes (testing):
3552 - Avoid intermittent test failures due to a test that had relied on
3553 onion service introduction point creation finishing within 5
3554 seconds of real clock time. Fixes bug 25450; bugfix
3556 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
3557 bugfix on 0.2.3.1-alpha.
3559 o Minor bugfixes (unit test, monotonic time):
3560 - Increase a constant (1msec to 10msec) in the monotonic time test
3561 that makes sure the nsec/usec/msec times read are synchronized.
3562 This change was needed to accommodate slow systems like armel or
3563 when the clock_gettime() is not a VDSO on the running kernel.
3564 Fixes bug 25113; bugfix on 0.2.9.1.
3566 o Code simplification and refactoring:
3567 - Move the list of default directory authorities to its own file.
3568 Closes ticket 24854. Patch by "beastr0".
3569 - Remove the old (deterministic) directory retry logic entirely:
3570 We've used exponential backoff exclusively for some time. Closes
3572 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
3574 - Remove a series of counters used to track circuit extend attempts
3575 and connection status but that in reality we aren't using for
3576 anything other than stats logged by a SIGUSR1 signal. Closes
3578 - Remove /usr/athena from search path in configure.ac. Closes
3580 - Remove duplicate code in node_has_curve25519_onion_key() and
3581 node_get_curve25519_onion_key(), and add a check for a zero
3582 microdesc curve25519 onion key. Closes ticket 23966, patch by
3583 "aruna1234" and teor.
3584 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
3585 memory allocations with large numbers of OR connections (e.g.
3586 relays). Closes ticket 24119.
3587 - Separate the function that deletes ephemeral files when Tor
3589 - Small changes to Tor's buf_t API to make it suitable for use as a
3590 general-purpose safe string constructor. Closes ticket 22342.
3591 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
3592 avoid source code identifier confusion. Closes ticket 24467.
3593 - The tor_git_revision[] constant no longer needs to be redeclared
3594 by everything that links against the rest of Tor. Done as part of
3595 ticket 23845, to simplify our external API.
3596 - We make extend_info_from_node() use node_get_curve25519_onion_key()
3597 introduced in ticket 23577 to access the curve25519 public keys
3598 rather than accessing it directly. Closes ticket 23760. Patch by
3600 - Add a function to log channels' scheduler state changes to aid
3601 debugging efforts. Closes ticket 24531.
3604 - Improved the documentation of AccountingStart parameter. Closes
3606 - Update the documentation for "Log" to include the current list of
3607 logging domains. Closes ticket 25378.
3608 - Add documentation on how to build tor with Rust dependencies
3609 without having to be online. Closes ticket 22907; bugfix
3611 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
3612 traffic. Closes ticket 24318.
3613 - Document that OutboundBindAddress doesn't apply to DNS requests.
3614 Closes ticket 22145. Patch from Aruna Maurya.
3616 o Code simplification and refactoring (channels):
3617 - Remove the incoming and outgoing channel queues. These were never
3618 used, but still took up a step in our fast path.
3619 - The majority of the channel unit tests have been rewritten and the
3620 code coverage has now been raised to 83.6% for channel.c. Closes
3622 - Remove other dead code from the channel subsystem: All together,
3623 this cleanup has removed more than 1500 lines of code overall and
3624 adding very little except for unit test.
3626 o Code simplification and refactoring (circuit rendezvous):
3627 - Split the client-side rendezvous circuit lookup into two
3628 functions: one that returns only established circuits and another
3629 that returns all kinds of circuits. Closes ticket 23459.
3631 o Code simplification and refactoring (controller):
3632 - Make most of the variables in networkstatus_getinfo_by_purpose()
3633 const. Implements ticket 24489.
3635 o Documentation (backport from 0.3.4.1-alpha):
3636 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
3637 ticket 25857. Patch from "CTassisF".
3639 o Documentation (man page):
3640 - The HiddenServiceVersion torrc option accepts only one number:
3641 either version 2 or 3. Closes ticket 25026; bugfix
3644 o Documentation (manpage, denial of service):
3645 - Provide more detail about the denial-of-service options, by
3646 listing each mitigation and explaining how they relate. Closes
3650 Changes in version 0.3.1.10 - 2018-03-03
3651 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
3654 It includes an important security fix for a remote crash attack
3655 against directory authorities, tracked as TROVE-2018-001.
3657 This release also backports our new system for improved resistance to
3658 denial-of-service attacks against relays.
3660 This release also fixes several minor bugs and annoyances from
3663 All directory authorities should upgrade to one of the versions
3664 released today. Relays running 0.3.1.x may wish to update to one of
3665 the versions released today, for the DoS mitigations.
3667 Please note: according to our release calendar, Tor 0.3.1 will no
3668 longer be supported after 1 July 2018. If you will be running Tor
3669 after that date, you should make sure to plan to upgrade to the latest
3670 stable version, or downgrade to 0.2.9 (which will receive long-term
3673 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
3674 - Fix a protocol-list handling bug that could be used to remotely crash
3675 directory authorities with a null-pointer exception. Fixes bug 25074;
3676 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
3679 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
3680 - Give relays some defenses against the recent network overload. We
3681 start with three defenses (default parameters in parentheses).
3682 First: if a single client address makes too many concurrent
3683 connections (>100), hang up on further connections. Second: if a
3684 single client address makes circuits too quickly (more than 3 per
3685 second, with an allowed burst of 90) while also having too many
3686 connections open (3), refuse new create cells for the next while
3687 (1-2 hours). Third: if a client asks to establish a rendezvous
3688 point to you directly, ignore the request. These defenses can be
3689 manually controlled by new torrc options, but relays will also
3690 take guidance from consensus parameters, so there's no need to
3691 configure anything manually. Implements ticket 24902.
3693 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
3694 - Update the sandbox rules so that they should now work correctly
3695 with Glibc 2.26. Closes ticket 24315.
3697 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
3698 - Fix an "off by 2" error in counting rendezvous failures on the
3699 onion service side. While we thought we would stop the rendezvous
3700 attempt after one failed circuit, we were actually making three
3701 circuit attempts before giving up. Now switch to a default of 2,
3702 and allow the consensus parameter "hs_service_max_rdv_failures" to
3703 override. Fixes bug 24895; bugfix on 0.0.6.
3705 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
3706 - Add Link protocol version 5 to the supported protocols list. Fixes
3707 bug 25070; bugfix on 0.3.1.1-alpha.
3709 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
3710 - Fix a set of false positives where relays would consider
3711 connections to other relays as being client-only connections (and
3712 thus e.g. deserving different link padding schemes) if those
3713 relays fell out of the consensus briefly. Now we look only at the
3714 initial handshake and whether the connection authenticated as a
3715 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
3717 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
3718 - Make our OOM handler aware of the geoip client history cache so it
3719 doesn't fill up the memory. This check is important for IPv6 and
3720 our DoS mitigation subsystem. Closes ticket 25122.
3722 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
3723 - Change relay bandwidth reporting stats interval from 4 hours to 24
3724 hours in order to reduce the efficiency of guard discovery
3725 attacks. Fixes ticket 23856.
3727 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
3728 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
3729 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
3730 since they neither disabled TLS 1.3 nor enabled any of the
3731 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
3732 Closes ticket 24978.
3734 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
3735 - The fallback directory list has been re-generated based on the
3736 current status of the network. Tor uses fallback directories to
3737 bootstrap when it doesn't yet have up-to-date directory
3738 information. Closes ticket 24801.
3739 - Make the default DirAuthorityFallbackRate 0.1, so that clients
3740 prefer to bootstrap from fallback directory mirrors. This is a
3741 follow-up to 24679, which removed weights from the default
3742 fallbacks. Implements ticket 24681.
3744 o Minor features (geoip):
3745 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
3748 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
3749 - Use the actual observed address of an incoming relay connection,
3750 not the canonical address of the relay from its descriptor, when
3751 making decisions about how to handle the incoming connection.
3752 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
3754 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
3755 - Directory authorities, when refusing a descriptor from a rejected
3756 relay, now explicitly tell the relay (in its logs) to set a valid
3757 ContactInfo address and contact the bad-relays@ mailing list.
3758 Fixes bug 25170; bugfix on 0.2.9.1.
3760 o Minor bugfixes (address selection, backport from 0.3.2.9):
3761 - When the fascist_firewall_choose_address_ functions don't find a
3762 reachable address, set the returned address to the null address
3763 and port. This is a precautionary measure, because some callers do
3764 not check the return value. Fixes bug 24736; bugfix
3767 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
3768 - Fetch descriptors aggressively whenever we lack enough to build
3769 circuits, regardless of how many descriptors we are missing.
3770 Previously, we would delay launching the fetch when we had fewer
3771 than 15 missing descriptors, even if some of those descriptors
3772 were blocking circuits from building. Fixes bug 23985; bugfix on
3773 0.1.1.11-alpha. The effects of this bug became worse in
3774 0.3.0.3-alpha, when we began treating missing descriptors from our
3775 primary guards as a reason to delay circuits.
3776 - Don't try fetching microdescriptors from relays that have failed
3777 to deliver them in the past. Fixes bug 23817; bugfix
3780 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
3781 - Fix a signed/unsigned comparison warning introduced by our fix to
3782 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
3784 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
3785 - Avoid a crash when attempting to use the seccomp2 sandbox together
3786 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
3789 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
3790 - Fix a possible crash on malformed consensus. If a consensus had
3791 contained an unparseable protocol line, it could have made clients
3792 and relays crash with a null-pointer exception. To exploit this
3793 issue, however, an attacker would need to be able to subvert the
3794 directory authority system. Fixes bug 25251; bugfix on
3795 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
3797 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
3798 - Recover better from empty or corrupt files in the consensus cache
3799 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
3800 - When a consensus diff calculation is only partially successful,
3801 only record the successful parts as having succeeded. Partial
3802 success can happen if (for example) one compression method fails
3803 but the others succeed. Previously we misrecorded all the
3804 calculations as having succeeded, which would later cause a
3805 nonfatal assertion failure. Fixes bug 24086; bugfix
3808 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
3809 - Tor now updates its guard state when it reads a consensus
3810 regardless of whether it's missing descriptors. That makes tor use
3811 its primary guards to fetch descriptors in some edge cases where
3812 it would previously have used fallback directories. Fixes bug
3813 23862; bugfix on 0.3.0.1-alpha.
3815 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
3816 - Don't treat inability to store a cached consensus object as a bug:
3817 it can happen normally when we are out of disk space. Fixes bug
3818 24859; bugfix on 0.3.1.1-alpha.
3820 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
3821 - When queuing DESTROY cells on a channel, only queue the circuit-id
3822 and reason fields: not the entire 514-byte cell. This fix should
3823 help mitigate any bugs or attacks that fill up these queues, and
3824 free more RAM for other uses. Fixes bug 24666; bugfix
3827 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
3828 - When closing a connection via close_connection_immediately(), we
3829 mark it as "not blocked on bandwidth", to prevent later calls from
3830 trying to unblock it, and give it permission to read. This fixes a
3831 backtrace warning that can happen on relays under various
3832 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
3834 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
3835 - When selecting relays by bandwidth, avoid a rounding error that
3836 could sometimes cause load to be imbalanced incorrectly.
3837 Previously, we would always round upwards; now, we round towards
3838 the nearest integer. This had the biggest effect when a relay's
3839 weight adjustments should have given it weight 0, but it got
3840 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
3841 - When calculating the fraction of nodes that have descriptors, and
3842 all nodes in the network have zero bandwidths, count the number of
3843 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
3844 - Actually log the total bandwidth in compute_weighted_bandwidths().
3845 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
3847 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
3848 - Improve the performance of our consensus-diff application code
3849 when Tor is built with the --enable-fragile-hardening option set.
3850 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
3852 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
3853 - Don't exit the Tor process if setrlimit() fails to change the file
3854 limit (which can happen sometimes on some versions of OSX). Fixes
3855 bug 21074; bugfix on 0.0.9pre5.
3857 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
3858 - Fix a bug in the bit-counting parts of our timing-wheel code on
3859 MSVC. (Note that MSVC is still not a supported build platform, due
3860 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
3863 o Minor bugfixes (relay, partial backport):
3864 - Make the internal channel_is_client() function look at what sort
3865 of connection handshake the other side used, rather than whether
3866 the other side ever sent a create_fast cell to us. Backports part
3867 of the fixes from bugs 22805 and 24898.
3869 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
3870 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
3872 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
3873 bugfix on 0.2.9.4-alpha.
3875 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
3876 - Update the "rust dependencies" submodule to be a project-level
3877 repository, rather than a user repository. Closes ticket 25323.
3880 Changes in version 0.2.9.15 - 2018-03-03
3881 Tor 0.2.9.15 backports important security and stability bugfixes from
3884 It includes an important security fix for a remote crash attack
3885 against directory authorities, tracked as TROVE-2018-001.
3887 This release also backports our new system for improved resistance to
3888 denial-of-service attacks against relays.
3890 This release also fixes several minor bugs and annoyances from
3893 All directory authorities should upgrade to one of the versions
3894 released today. Relays running 0.2.9.x may wish to update to one of
3895 the versions released today, for the DoS mitigations.
3897 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
3898 - Fix a protocol-list handling bug that could be used to remotely crash
3899 directory authorities with a null-pointer exception. Fixes bug 25074;
3900 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
3903 o Major features (denial-of-service mitigation):
3904 - Give relays some defenses against the recent network overload. We
3905 start with three defenses (default parameters in parentheses).
3906 First: if a single client address makes too many concurrent
3907 connections (>100), hang up on further connections. Second: if a
3908 single client address makes circuits too quickly (more than 3 per
3909 second, with an allowed burst of 90) while also having too many
3910 connections open (3), refuse new create cells for the next while
3911 (1-2 hours). Third: if a client asks to establish a rendezvous
3912 point to you directly, ignore the request. These defenses can be
3913 manually controlled by new torrc options, but relays will also
3914 take guidance from consensus parameters, so there's no need to
3915 configure anything manually. Implements ticket 24902.
3917 o Major bugfixes (bootstrapping):
3918 - Fetch descriptors aggressively whenever we lack enough to build
3919 circuits, regardless of how many descriptors we are missing.
3920 Previously, we would delay launching the fetch when we had fewer
3921 than 15 missing descriptors, even if some of those descriptors
3922 were blocking circuits from building. Fixes bug 23985; bugfix on
3923 0.1.1.11-alpha. The effects of this bug became worse in
3924 0.3.0.3-alpha, when we began treating missing descriptors from our
3925 primary guards as a reason to delay circuits.
3927 o Major bugfixes (onion services, retry behavior):
3928 - Fix an "off by 2" error in counting rendezvous failures on the
3929 onion service side. While we thought we would stop the rendezvous
3930 attempt after one failed circuit, we were actually making three
3931 circuit attempts before giving up. Now switch to a default of 2,
3932 and allow the consensus parameter "hs_service_max_rdv_failures" to
3933 override. Fixes bug 24895; bugfix on 0.0.6.
3935 o Minor feature (relay statistics):
3936 - Change relay bandwidth reporting stats interval from 4 hours to 24
3937 hours in order to reduce the efficiency of guard discovery
3938 attacks. Fixes ticket 23856.
3940 o Minor features (compatibility, OpenSSL):
3941 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
3942 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
3943 since they neither disabled TLS 1.3 nor enabled any of the
3944 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
3945 Closes ticket 24978.
3947 o Minor features (denial-of-service avoidance):
3948 - Make our OOM handler aware of the geoip client history cache so it
3949 doesn't fill up the memory. This check is important for IPv6 and
3950 our DoS mitigation subsystem. Closes ticket 25122.
3952 o Minor features (fallback directory mirrors):
3953 - The fallback directory list has been re-generated based on the
3954 current status of the network. Tor uses fallback directories to
3955 bootstrap when it doesn't yet have up-to-date directory
3956 information. Closes ticket 24801.
3957 - Make the default DirAuthorityFallbackRate 0.1, so that clients
3958 prefer to bootstrap from fallback directory mirrors. This is a
3959 follow-up to 24679, which removed weights from the default
3960 fallbacks. Implements ticket 24681.
3962 o Minor features (geoip):
3963 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
3966 o Minor features (linux seccomp2 sandbox):
3967 - Update the sandbox rules so that they should now work correctly
3968 with Glibc 2.26. Closes ticket 24315.
3970 o Minor bugfix (channel connection):
3971 - Use the actual observed address of an incoming relay connection,
3972 not the canonical address of the relay from its descriptor, when
3973 making decisions about how to handle the incoming connection.
3974 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
3976 o Minor bugfix (directory authority):
3977 - Directory authorities, when refusing a descriptor from a rejected
3978 relay, now explicitly tell the relay (in its logs) to set a valid
3979 ContactInfo address and contact the bad-relays@ mailing list.
3980 Fixes bug 25170; bugfix on 0.2.9.1.
3982 o Minor bugfixes (address selection):
3983 - When the fascist_firewall_choose_address_ functions don't find a
3984 reachable address, set the returned address to the null address
3985 and port. This is a precautionary measure, because some callers do
3986 not check the return value. Fixes bug 24736; bugfix
3989 o Minor bugfixes (compilation):
3990 - Fix a signed/unsigned comparison warning introduced by our fix to
3991 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
3993 o Minor bugfixes (control port, linux seccomp2 sandbox):
3994 - Avoid a crash when attempting to use the seccomp2 sandbox together
3995 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
3998 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
3999 - Fix a possible crash on malformed consensus. If a consensus had
4000 contained an unparseable protocol line, it could have made clients
4001 and relays crash with a null-pointer exception. To exploit this
4002 issue, however, an attacker would need to be able to subvert the
4003 directory authority system. Fixes bug 25251; bugfix on
4004 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4006 o Minor bugfixes (memory usage):
4007 - When queuing DESTROY cells on a channel, only queue the circuit-id
4008 and reason fields: not the entire 514-byte cell. This fix should
4009 help mitigate any bugs or attacks that fill up these queues, and
4010 free more RAM for other uses. Fixes bug 24666; bugfix
4013 o Minor bugfixes (network layer):
4014 - When closing a connection via close_connection_immediately(), we
4015 mark it as "not blocked on bandwidth", to prevent later calls from
4016 trying to unblock it, and give it permission to read. This fixes a
4017 backtrace warning that can happen on relays under various
4018 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4020 o Minor bugfixes (OSX):
4021 - Don't exit the Tor process if setrlimit() fails to change the file
4022 limit (which can happen sometimes on some versions of OSX). Fixes
4023 bug 21074; bugfix on 0.0.9pre5.
4025 o Minor bugfixes (path selection):
4026 - When selecting relays by bandwidth, avoid a rounding error that
4027 could sometimes cause load to be imbalanced incorrectly.
4028 Previously, we would always round upwards; now, we round towards
4029 the nearest integer. This had the biggest effect when a relay's
4030 weight adjustments should have given it weight 0, but it got
4031 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
4032 - When calculating the fraction of nodes that have descriptors, and
4033 all nodes in the network have zero bandwidths, count the number of
4034 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
4035 - Actually log the total bandwidth in compute_weighted_bandwidths().
4036 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
4038 o Minor bugfixes (portability, msvc):
4039 - Fix a bug in the bit-counting parts of our timing-wheel code on
4040 MSVC. (Note that MSVC is still not a supported build platform, due
4041 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
4044 o Minor bugfixes (relay):
4045 - Make the internal channel_is_client() function look at what sort
4046 of connection handshake the other side used, rather than whether
4047 the other side ever sent a create_fast cell to us. Backports part
4048 of the fixes from bugs 22805 and 24898.
4050 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
4051 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4053 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4054 bugfix on 0.2.9.4-alpha.
4057 Changes in version 0.3.2.10 - 2018-03-03
4058 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
4059 backports a number of bugfixes, including important fixes for security
4062 It includes an important security fix for a remote crash attack
4063 against directory authorities, tracked as TROVE-2018-001.
4065 Additionally, it backports a fix for a bug whose severity we have
4066 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
4067 triggered in order to crash relays with a use-after-free pattern. As
4068 such, we are now tracking that bug as TROVE-2018-002 and
4069 CVE-2018-0491, and backporting it to earlier releases. This bug
4070 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
4073 This release also backports our new system for improved resistance to
4074 denial-of-service attacks against relays.
4076 This release also fixes several minor bugs and annoyances from
4079 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
4080 today, for the fix to TROVE-2018-002. Directory authorities should
4081 also upgrade. (Relays on earlier versions might want to update too for
4082 the DoS mitigations.)
4084 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
4085 - Fix a protocol-list handling bug that could be used to remotely crash
4086 directory authorities with a null-pointer exception. Fixes bug 25074;
4087 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4090 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
4091 - Avoid adding the same channel twice in the KIST scheduler pending
4092 list, which could lead to remote denial-of-service use-after-free
4093 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
4095 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
4096 - Give relays some defenses against the recent network overload. We
4097 start with three defenses (default parameters in parentheses).
4098 First: if a single client address makes too many concurrent
4099 connections (>100), hang up on further connections. Second: if a
4100 single client address makes circuits too quickly (more than 3 per
4101 second, with an allowed burst of 90) while also having too many
4102 connections open (3), refuse new create cells for the next while
4103 (1-2 hours). Third: if a client asks to establish a rendezvous
4104 point to you directly, ignore the request. These defenses can be
4105 manually controlled by new torrc options, but relays will also
4106 take guidance from consensus parameters, so there's no need to
4107 configure anything manually. Implements ticket 24902.
4109 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
4110 - Fix an "off by 2" error in counting rendezvous failures on the
4111 onion service side. While we thought we would stop the rendezvous
4112 attempt after one failed circuit, we were actually making three
4113 circuit attempts before giving up. Now switch to a default of 2,
4114 and allow the consensus parameter "hs_service_max_rdv_failures" to
4115 override. Fixes bug 24895; bugfix on 0.0.6.
4116 - New-style (v3) onion services now obey the "max rendezvous circuit
4117 attempts" logic. Previously they would make as many rendezvous
4118 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
4119 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
4121 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
4122 - Add Link protocol version 5 to the supported protocols list. Fixes
4123 bug 25070; bugfix on 0.3.1.1-alpha.
4125 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
4126 - Fix a set of false positives where relays would consider
4127 connections to other relays as being client-only connections (and
4128 thus e.g. deserving different link padding schemes) if those
4129 relays fell out of the consensus briefly. Now we look only at the
4130 initial handshake and whether the connection authenticated as a
4131 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
4133 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
4134 - The scheduler subsystem was failing to promptly notice changes in
4135 consensus parameters, making it harder to switch schedulers
4136 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
4138 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
4139 - Make our OOM handler aware of the geoip client history cache so it
4140 doesn't fill up the memory. This check is important for IPv6 and
4141 our DoS mitigation subsystem. Closes ticket 25122.
4143 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
4144 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4145 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4146 since they neither disabled TLS 1.3 nor enabled any of the
4147 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4148 Closes ticket 24978.
4150 o Minor features (geoip):
4151 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4154 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
4155 - When logging a failure to create an onion service's descriptor,
4156 also log what the problem with the descriptor was. Diagnostic
4159 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
4160 - Use the actual observed address of an incoming relay connection,
4161 not the canonical address of the relay from its descriptor, when
4162 making decisions about how to handle the incoming connection.
4163 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4165 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
4166 - Fix a possible crash on malformed consensus. If a consensus had
4167 contained an unparseable protocol line, it could have made clients
4168 and relays crash with a null-pointer exception. To exploit this
4169 issue, however, an attacker would need to be able to subvert the
4170 directory authority system. Fixes bug 25251; bugfix on
4171 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4173 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
4174 - Directory authorities, when refusing a descriptor from a rejected
4175 relay, now explicitly tell the relay (in its logs) to set a valid
4176 ContactInfo address and contact the bad-relays@ mailing list.
4177 Fixes bug 25170; bugfix on 0.2.9.1.
4179 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
4180 - When building with Rust on OSX, link against libresolv, to work
4181 around the issue at https://github.com/rust-lang/rust/issues/46797.
4182 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
4184 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
4185 - Remove a BUG() statement when a client fetches an onion descriptor
4186 that has a lower revision counter than the one in its cache. This
4187 can happen in normal circumstances due to HSDir desync. Fixes bug
4188 24976; bugfix on 0.3.2.1-alpha.
4190 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
4191 - Don't treat inability to store a cached consensus object as a bug:
4192 it can happen normally when we are out of disk space. Fixes bug
4193 24859; bugfix on 0.3.1.1-alpha.
4195 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
4196 - Improve the performance of our consensus-diff application code
4197 when Tor is built with the --enable-fragile-hardening option set.
4198 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
4200 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
4201 - Don't exit the Tor process if setrlimit() fails to change the file
4202 limit (which can happen sometimes on some versions of OSX). Fixes
4203 bug 21074; bugfix on 0.0.9pre5.
4205 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
4206 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4208 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4209 bugfix on 0.2.9.4-alpha.
4211 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
4212 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
4213 25005; bugfix on 0.3.2.7-rc.
4215 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
4216 - Look at the "HSRend" protocol version, not the "HSDir" protocol
4217 version, when deciding whether a consensus entry can support the
4218 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
4219 bugfix on 0.3.2.1-alpha.
4221 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
4222 - Update the "rust dependencies" submodule to be a project-level
4223 repository, rather than a user repository. Closes ticket 25323.
4225 o Documentation (backport from 0.3.3.1-alpha)
4226 - Document that operators who run more than one relay or bridge are
4227 expected to set MyFamily and ContactInfo correctly. Closes
4231 Changes in version 0.3.2.9 - 2018-01-09
4232 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
4234 The 0.3.2 series includes our long-anticipated new onion service
4235 design, with numerous security features. (For more information, see
4236 our blog post at https://blog.torproject.org/fall-harvest.) We also
4237 have a new circuit scheduler algorithm for improved performance on
4238 relays everywhere (see https://blog.torproject.org/kist-and-tell),
4239 along with many smaller features and bugfixes.
4241 Per our stable release policy, we plan to support each stable release
4242 series for at least the next nine months, or for three months after
4243 the first stable release of the next series: whichever is longer. If
4244 you need a release with long-term support, we recommend that you stay
4245 with the 0.2.9 series.
4247 Below is a list of the changes since 0.3.1.7. For a list of all
4248 changes since 0.3.2.8-rc, see the ChangeLog file.
4250 o Directory authority changes:
4251 - Add "Bastet" as a ninth directory authority to the default list.
4252 Closes ticket 23910.
4253 - The directory authority "Longclaw" has changed its IP address.
4254 Closes ticket 23592.
4255 - Remove longclaw's IPv6 address, as it will soon change. Authority
4256 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
4257 3/8 directory authorities with IPv6 addresses, but there are also
4258 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
4259 - Add an IPv6 address for the "bastet" directory authority. Closes
4262 o Major features (next-generation onion services):
4263 - Tor now supports the next-generation onion services protocol for
4264 clients and services! As part of this release, the core of
4265 proposal 224 has been implemented and is available for
4266 experimentation and testing by our users. This newer version of
4267 onion services ("v3") features many improvements over the legacy
4270 a) Better crypto (replaced SHA1/DH/RSA1024
4271 with SHA3/ed25519/curve25519)
4273 b) Improved directory protocol, leaking much less information to
4276 c) Improved directory protocol, with smaller surface for
4279 d) Better onion address security against impersonation.
4281 e) More extensible introduction/rendezvous protocol.
4283 f) A cleaner and more modular codebase.
4285 You can identify a next-generation onion address by its length:
4286 they are 56 characters long, as in
4287 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
4289 In the future, we will release more options and features for v3
4290 onion services, but we first need a testing period, so that the
4291 current codebase matures and becomes more robust. Planned features
4292 include: offline keys, advanced client authorization, improved
4293 guard algorithms, and statistics. For full details, see
4296 Legacy ("v2") onion services will still work for the foreseeable
4297 future, and will remain the default until this new codebase gets
4298 tested and hardened. Service operators who want to experiment with
4299 the new system can use the 'HiddenServiceVersion 3' torrc
4300 directive along with the regular onion service configuration
4301 options. For more information, see our blog post at
4302 "https://blog.torproject.org/fall-harvest". Enjoy!
4304 o Major feature (scheduler, channel):
4305 - Tor now uses new schedulers to decide which circuits should
4306 deliver cells first, in order to improve congestion at relays. The
4307 first type is called "KIST" ("Kernel Informed Socket Transport"),
4308 and is only available on Linux-like systems: it uses feedback from
4309 the kernel to prevent the kernel's TCP buffers from growing too
4310 full. The second new scheduler type is called "KISTLite": it
4311 behaves the same as KIST, but runs on systems without kernel
4312 support for inspecting TCP implementation details. The old
4313 scheduler is still available, under the name "Vanilla". To change
4314 the default scheduler preference order, use the new "Schedulers"
4315 option. (The default preference order is "KIST,KISTLite,Vanilla".)
4317 Matt Traudt implemented KIST, based on research by Rob Jansen,
4318 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
4319 more information, see the design paper at
4320 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
4321 followup implementation paper at https://arxiv.org/abs/1709.01044.
4322 Closes ticket 12541. For more information, see our blog post at
4323 "https://blog.torproject.org/kist-and-tell".
4325 o Major bugfixes (security, general):
4326 - Fix a denial of service bug where an attacker could use a
4327 malformed directory object to cause a Tor instance to pause while
4328 OpenSSL would try to read a passphrase from the terminal. (Tor
4329 instances run without a terminal, which is the case for most Tor
4330 packages, are not impacted.) Fixes bug 24246; bugfix on every
4331 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
4332 Found by OSS-Fuzz as testcase 6360145429790720.
4334 o Major bugfixes (security, directory authority):
4335 - Fix a denial of service issue where an attacker could crash a
4336 directory authority using a malformed router descriptor. Fixes bug
4337 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
4340 o Major bugfixes (security, onion service v2):
4341 - Fix a use-after-free error that could crash v2 Tor onion services
4342 when they failed to open circuits while expiring introduction
4343 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
4344 also tracked as TROVE-2017-013 and CVE-2017-8823.
4345 - When checking for replays in the INTRODUCE1 cell data for a
4346 (legacy) onion service, correctly detect replays in the RSA-
4347 encrypted part of the cell. We were previously checking for
4348 replays on the entire cell, but those can be circumvented due to
4349 the malleability of Tor's legacy hybrid encryption. This fix helps
4350 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
4351 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
4354 o Major bugfixes (security, relay):
4355 - When running as a relay, make sure that we never build a path
4356 through ourselves, even in the case where we have somehow lost the
4357 version of our descriptor appearing in the consensus. Fixes part
4358 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
4359 as TROVE-2017-012 and CVE-2017-8822.
4360 - When running as a relay, make sure that we never choose ourselves
4361 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
4362 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
4364 o Major bugfixes (bootstrapping):
4365 - Fetch descriptors aggressively whenever we lack enough to build
4366 circuits, regardless of how many descriptors we are missing.
4367 Previously, we would delay launching the fetch when we had fewer
4368 than 15 missing descriptors, even if some of those descriptors
4369 were blocking circuits from building. Fixes bug 23985; bugfix on
4370 0.1.1.11-alpha. The effects of this bug became worse in
4371 0.3.0.3-alpha, when we began treating missing descriptors from our
4372 primary guards as a reason to delay circuits.
4373 - Don't try fetching microdescriptors from relays that have failed
4374 to deliver them in the past. Fixes bug 23817; bugfix
4377 o Major bugfixes (circuit prediction):
4378 - Fix circuit prediction logic so that a client doesn't treat a port
4379 as being "handled" by a circuit if that circuit already has
4380 isolation settings on it. This change should make Tor clients more
4381 responsive by improving their chances of having a pre-created
4382 circuit ready for use when a request arrives. Fixes bug 18859;
4383 bugfix on 0.2.3.3-alpha.
4385 o Major bugfixes (exit relays, DNS):
4386 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
4387 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
4388 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
4389 identifying and finding a workaround to this bug and to Moritz,
4390 Arthur Edelstein, and Roger for helping to track it down and
4393 o Major bugfixes (relay, crash, assertion failure):
4394 - Fix a timing-based assertion failure that could occur when the
4395 circuit out-of-memory handler freed a connection's output buffer.
4396 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
4398 o Major bugfixes (usability, control port):
4399 - Report trusted clock skew indications as bootstrap errors, so
4400 controllers can more easily alert users when their clocks are
4401 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
4403 o Minor features (bridge):
4404 - Bridge relays can now set the BridgeDistribution config option to
4405 add a "bridge-distribution-request" line to their bridge
4406 descriptor, which tells BridgeDB how they'd like their bridge
4407 address to be given out. (Note that as of Oct 2017, BridgeDB does
4408 not yet implement this feature.) As a side benefit, this feature
4409 provides a way to distinguish bridge descriptors from non-bridge
4410 descriptors. Implements tickets 18329.
4411 - When handling the USERADDR command on an ExtOrPort, warn when the
4412 transports provides a USERADDR with no port. In a future version,
4413 USERADDR commands of this format may be rejected. Detects problems
4414 related to ticket 23080.
4416 o Minor features (bug detection):
4417 - Log a warning message with a stack trace for any attempt to call
4418 get_options() during option validation. This pattern has caused
4419 subtle bugs in the past. Closes ticket 22281.
4421 o Minor features (build, compilation):
4422 - The "check-changes" feature is now part of the "make check" tests;
4423 we'll use it to try to prevent misformed changes files from
4424 accumulating. Closes ticket 23564.
4425 - Tor builds should now fail if there are any mismatches between the
4426 C type representing a configuration variable and the C type the
4427 data-driven parser uses to store a value there. Previously, we
4428 needed to check these by hand, which sometimes led to mistakes.
4429 Closes ticket 23643.
4431 o Minor features (client):
4432 - You can now use Tor as a tunneled HTTP proxy: use the new
4433 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
4434 requests. Closes ticket 22407.
4435 - Add an extra check to make sure that we always use the newer guard
4436 selection code for picking our guards. Closes ticket 22779.
4437 - When downloading (micro)descriptors, don't split the list into
4438 multiple requests unless we want at least 32 descriptors.
4439 Previously, we split at 4, not 32, which led to significant
4440 overhead in HTTP request size and degradation in compression
4441 performance. Closes ticket 23220.
4442 - Improve log messages when missing descriptors for primary guards.
4443 Resolves ticket 23670.
4445 o Minor features (command line):
4446 - Add a new commandline option, --key-expiration, which prints when
4447 the current signing key is going to expire. Implements ticket
4448 17639; patch by Isis Lovecruft.
4450 o Minor features (control port):
4451 - If an application tries to use the control port as an HTTP proxy,
4452 respond with a meaningful "This is the Tor control port" message,
4453 and log the event. Closes ticket 1667. Patch from Ravi
4455 - Provide better error message for GETINFO desc/(id|name) when not
4456 fetching router descriptors. Closes ticket 5847. Patch by
4458 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
4459 whether Tor will try to download router descriptors and
4460 microdescriptors respectively. Closes ticket 22684.
4461 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
4462 so controllers can tell whether the geoip databases are loaded.
4463 Closes ticket 23237.
4464 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
4465 events. Closes ticket 19254. Patch by "DonnchaC".
4467 o Minor features (development support):
4468 - Developers can now generate a call-graph for Tor using the
4469 "calltool" python program, which post-processes object dumps. It
4470 should work okay on many Linux and OSX platforms, and might work
4471 elsewhere too. To run it, install calltool from
4472 https://gitweb.torproject.org/user/nickm/calltool.git and run
4473 "make callgraph". Closes ticket 19307.
4475 o Minor features (directory authority):
4476 - Make the "Exit" flag assignment only depend on whether the exit
4477 policy allows connections to ports 80 and 443. Previously relays
4478 would get the Exit flag if they allowed connections to one of
4479 these ports and also port 6667. Resolves ticket 23637.
4481 o Minor features (ed25519):
4482 - Add validation function to checks for torsion components in
4483 ed25519 public keys, used by prop224 client-side code. Closes
4484 ticket 22006. Math help by Ian Goldberg.
4486 o Minor features (exit relay, DNS):
4487 - Improve the clarity and safety of the log message from evdns when
4488 receiving an apparently spoofed DNS reply. Closes ticket 3056.
4490 o Minor features (fallback directory mirrors):
4491 - The fallback directory list has been re-generated based on the
4492 current status of the network. Tor uses fallback directories to
4493 bootstrap when it doesn't yet have up-to-date directory
4494 information. Closes ticket 24801.
4495 - Make the default DirAuthorityFallbackRate 0.1, so that clients
4496 prefer to bootstrap from fallback directory mirrors. This is a
4497 follow-up to 24679, which removed weights from the default
4498 fallbacks. Implements ticket 24681.
4500 o Minor features (geoip):
4501 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
4504 o Minor features (integration, hardening):
4505 - Add a new NoExec option to prevent Tor from running other
4506 programs. When this option is set to 1, Tor will never try to run
4507 another program, regardless of the settings of
4508 PortForwardingHelper, ClientTransportPlugin, or
4509 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
4510 without restarting Tor. Closes ticket 22976.
4512 o Minor features (linux seccomp2 sandbox):
4513 - Update the sandbox rules so that they should now work correctly
4514 with Glibc 2.26. Closes ticket 24315.
4516 o Minor features (logging):
4517 - Provide better warnings when the getrandom() syscall fails. Closes
4519 - Downgrade a pair of log messages that could occur when an exit's
4520 resolver gave us an unusual (but not forbidden) response. Closes
4522 - Improve the message we log when re-enabling circuit build timeouts
4523 after having received a consensus. Closes ticket 20963.
4524 - Log more circuit information whenever we are about to try to
4525 package a relay cell on a circuit with a nonexistent n_chan.
4526 Attempt to diagnose ticket 8185.
4527 - Improve info-level log identification of particular circuits, to
4528 help with debugging. Closes ticket 23645.
4529 - Improve the warning message for specifying a relay by nickname.
4530 The previous message implied that nickname registration was still
4531 part of the Tor network design, which it isn't. Closes
4533 - If the sandbox filter fails to load, suggest to the user that
4534 their kernel might not support seccomp2. Closes ticket 23090.
4536 o Minor features (onion service, circuit, logging):
4537 - Improve logging of many callsite in the circuit subsystem to print
4538 the circuit identifier(s).
4539 - Log when we cleanup an intro point from a service so we know when
4540 and for what reason it happened. Closes ticket 23604.
4542 o Minor features (portability):
4543 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
4544 (It doesn't yet work with the sandbox enabled.) Closes
4546 - Check at configure time whether uint8_t is the same type as
4547 unsigned char. Lots of existing code already makes this
4548 assumption, and there could be strict aliasing issues if the
4549 assumption is violated. Closes ticket 22410.
4551 o Minor features (relay):
4552 - When choosing which circuits can be expired as unused, consider
4553 circuits from clients even if those clients used regular CREATE
4554 cells to make them; and do not consider circuits from relays even
4555 if they were made with CREATE_FAST. Part of ticket 22805.
4556 - Reject attempts to use relative file paths when RunAsDaemon is
4557 set. Previously, Tor would accept these, but the directory-
4558 changing step of RunAsDaemon would give strange and/or confusing
4559 results. Closes ticket 22731.
4561 o Minor features (relay statistics):
4562 - Change relay bandwidth reporting stats interval from 4 hours to 24
4563 hours in order to reduce the efficiency of guard discovery
4564 attacks. Fixes ticket 23856.
4566 o Minor features (reverted deprecations):
4567 - The ClientDNSRejectInternalAddresses flag can once again be set in
4568 non-testing Tor networks, so long as they do not use the default
4569 directory authorities. This change also removes the deprecation of
4570 this flag from 0.2.9.2-alpha. Closes ticket 21031.
4572 o Minor features (robustness):
4573 - Change several fatal assertions when flushing buffers into non-
4574 fatal assertions, to prevent any recurrence of 23690.
4576 o Minor features (startup, safety):
4577 - When configured to write a PID file, Tor now exits if it is unable
4578 to do so. Previously, it would warn and continue. Closes
4581 o Minor features (static analysis):
4582 - The BUG() macro has been changed slightly so that Coverity no
4583 longer complains about dead code if the bug is impossible. Closes
4586 o Minor features (testing):
4587 - Our fuzzing tests now test the encrypted portions of v3 onion
4588 service descriptors. Implements more of 21509.
4589 - Add a unit test to make sure that our own generated platform
4590 string will be accepted by directory authorities. Closes
4592 - The default chutney network tests now include tests for the v3
4593 onion service design. Make sure you have the latest version of
4594 chutney if you want to run these. Closes ticket 22437.
4595 - Add a unit test to verify that we can parse a hardcoded v2 onion
4596 service descriptor. Closes ticket 15554.
4598 o Minor bugfixes (address selection):
4599 - When the fascist_firewall_choose_address_ functions don't find a
4600 reachable address, set the returned address to the null address
4601 and port. This is a precautionary measure, because some callers do
4602 not check the return value. Fixes bug 24736; bugfix
4605 o Minor bugfixes (bootstrapping):
4606 - When warning about state file clock skew, report the correct
4607 direction for the detected skew. Fixes bug 23606; bugfix
4610 o Minor bugfixes (bridge clients, bootstrap):
4611 - Retry directory downloads when we get our first bridge descriptor
4612 during bootstrap or while reconnecting to the network. Keep
4613 retrying every time we get a bridge descriptor, until we have a
4614 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
4615 - Stop delaying bridge descriptor fetches when we have cached bridge
4616 descriptors. Instead, only delay bridge descriptor fetches when we
4617 have at least one reachable bridge. Fixes part of bug 24367;
4618 bugfix on 0.2.0.3-alpha.
4619 - Stop delaying directory fetches when we have cached bridge
4620 descriptors. Instead, only delay bridge descriptor fetches when
4621 all our bridges are definitely unreachable. Fixes part of bug
4622 24367; bugfix on 0.2.0.3-alpha.
4624 o Minor bugfixes (bridge):
4625 - Overwrite the bridge address earlier in the process of retrieving
4626 its descriptor, to make sure we reach it on the configured
4627 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
4629 o Minor bugfixes (build, compilation):
4630 - Fix a compilation warning when building with zstd support on
4631 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
4632 and fixed by Andreas Stieger.
4633 - When searching for OpenSSL, don't accept any OpenSSL library that
4634 lacks TLSv1_1_method(): Tor doesn't build with those versions.
4635 Additionally, look in /usr/local/opt/openssl, if it's present.
4636 These changes together repair the default build on OSX systems
4637 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
4638 - Fix a signed/unsigned comparison warning introduced by our fix to
4639 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
4640 - Fix a memory leak warning in one of the libevent-related
4641 configuration tests that could occur when manually specifying
4642 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
4643 Found and patched by Alex Xu.
4644 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
4645 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
4647 o Minor bugfixes (certificate handling):
4648 - Fix a time handling bug in Tor certificates set to expire after
4649 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
4650 Coverity as CID 1415728.
4652 o Minor bugfixes (client):
4653 - By default, do not enable storage of client-side DNS values. These
4654 values were unused by default previously, but they should not have
4655 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
4657 o Minor bugfixes (client, usability):
4658 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
4659 SOCKS4a requests that contain IP address strings, even when
4660 SafeSocks in enabled, as this prevents user from connecting to
4661 known IP addresses without relying on DNS for resolving. SafeSocks
4662 still rejects SOCKS connections that connect to IP addresses when
4663 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
4664 bugfix on Tor 0.2.6.2-alpha.
4666 o Minor bugfixes (code correctness):
4667 - Call htons() in extend_cell_format() for encoding a 16-bit value.
4668 Previously we used ntohs(), which happens to behave the same on
4669 all the platforms we support, but which isn't really correct.
4670 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
4671 - For defense-in-depth, make the controller's write_escaped_data()
4672 function robust to extremely long inputs. Fixes bug 19281; bugfix
4673 on 0.1.1.1-alpha. Reported by Guido Vranken.
4674 - Fix several places in our codebase where a C compiler would be
4675 likely to eliminate a check, based on assuming that undefined
4676 behavior had not happened elsewhere in the code. These cases are
4677 usually a sign of redundant checking or dubious arithmetic. Found
4678 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
4679 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
4682 o Minor bugfixes (compression):
4683 - Handle a pathological case when decompressing Zstandard data when
4684 the output buffer size is zero. Fixes bug 23551; bugfix
4687 o Minor bugfixes (consensus expiry):
4688 - Check for adequate directory information correctly. Previously, Tor
4689 would reconsider whether it had sufficient directory information
4690 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
4692 o Minor bugfixes (control port, linux seccomp2 sandbox):
4693 - Avoid a crash when attempting to use the seccomp2 sandbox together
4694 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
4697 o Minor bugfixes (control port, onion services):
4698 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
4699 HS_DESC event when a service is not able to upload a descriptor.
4700 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
4702 o Minor bugfixes (directory cache):
4703 - Recover better from empty or corrupt files in the consensus cache
4704 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
4705 - When a consensus diff calculation is only partially successful,
4706 only record the successful parts as having succeeded. Partial
4707 success can happen if (for example) one compression method fails
4708 but the others succeed. Previously we misrecorded all the
4709 calculations as having succeeded, which would later cause a
4710 nonfatal assertion failure. Fixes bug 24086; bugfix
4713 o Minor bugfixes (directory client):
4714 - On failure to download directory information, delay retry attempts
4715 by a random amount based on the "decorrelated jitter" algorithm.
4716 Our previous delay algorithm tended to produce extra-long delays
4717 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
4719 o Minor bugfixes (directory protocol):
4720 - Directory servers now include a "Date:" http header for response
4721 codes other than 200. Clients starting with a skewed clock and a
4722 recent consensus were getting "304 Not modified" responses from
4723 directory authorities, so without the Date header, the client
4724 would never hear about a wrong clock. Fixes bug 23499; bugfix
4726 - Make clients wait for 6 seconds before trying to download a
4727 consensus from an authority. Fixes bug 17750; bugfix
4730 o Minor bugfixes (documentation):
4731 - Document better how to read gcov, and what our gcov postprocessing
4732 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
4733 - Fix manpage to not refer to the obsolete (and misspelled)
4734 UseEntryGuardsAsDirectoryGuards parameter in the description of
4735 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
4737 o Minor bugfixes (DoS-resistance):
4738 - If future code asks if there are any running bridges, without
4739 checking if bridges are enabled, log a BUG warning rather than
4740 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
4742 o Minor bugfixes (entry guards):
4743 - Tor now updates its guard state when it reads a consensus
4744 regardless of whether it's missing descriptors. That makes tor use
4745 its primary guards to fetch descriptors in some edge cases where
4746 it would previously have used fallback directories. Fixes bug
4747 23862; bugfix on 0.3.0.1-alpha.
4749 o Minor bugfixes (format strictness):
4750 - Restrict several data formats to decimal. Previously, the
4751 BuildTimeHistogram entries in the state file, the "bw=" entries in
4752 the bandwidth authority file, and the process IDs passed to the
4753 __OwningControllerProcess option could all be specified in hex or
4754 octal as well as in decimal. This was not an intentional feature.
4755 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
4758 o Minor bugfixes (heartbeat):
4759 - If we fail to write a heartbeat message, schedule a retry for the
4760 minimum heartbeat interval number of seconds in the future. Fixes
4761 bug 19476; bugfix on 0.2.3.1-alpha.
4763 o Minor bugfixes (logging):
4764 - Suppress a log notice when relay descriptors arrive. We already
4765 have a bootstrap progress for this so no need to log notice
4766 everytime tor receives relay descriptors. Microdescriptors behave
4767 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
4768 - Remove duplicate log messages regarding opening non-local
4769 SocksPorts upon parsing config and opening listeners at startup.
4770 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
4771 - Use a more comprehensible log message when telling the user
4772 they've excluded every running exit node. Fixes bug 7890; bugfix
4774 - When logging the number of descriptors we intend to download per
4775 directory request, do not log a number higher than then the number
4776 of descriptors we're fetching in total. Fixes bug 19648; bugfix
4778 - When warning about a directory owned by the wrong user, log the
4779 actual name of the user owning the directory. Previously, we'd log
4780 the name of the process owner twice. Fixes bug 23487; bugfix
4782 - Fix some messages on unexpected errors from the seccomp2 library.
4783 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
4784 - The tor specification says hop counts are 1-based, so fix two log
4785 messages that mistakenly logged 0-based hop counts. Fixes bug
4786 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
4787 Credit to Xiaofan Li for reporting this issue.
4789 o Minor bugfixes (logging, relay shutdown, annoyance):
4790 - When a circuit is marked for close, do not attempt to package any
4791 cells for channels on that circuit. Previously, we would detect
4792 this condition lower in the call stack, when we noticed that the
4793 circuit had no attached channel, and log an annoying message.
4794 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
4796 o Minor bugfixes (memory safety, defensive programming):
4797 - Clear the target address when node_get_prim_orport() returns
4798 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
4800 o Minor bugfixes (memory usage):
4801 - When queuing DESTROY cells on a channel, only queue the circuit-id
4802 and reason fields: not the entire 514-byte cell. This fix should
4803 help mitigate any bugs or attacks that fill up these queues, and
4804 free more RAM for other uses. Fixes bug 24666; bugfix
4807 o Minor bugfixes (network layer):
4808 - When closing a connection via close_connection_immediately(), we
4809 mark it as "not blocked on bandwidth", to prevent later calls from
4810 trying to unblock it, and give it permission to read. This fixes a
4811 backtrace warning that can happen on relays under various
4812 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4814 o Minor bugfixes (onion services):
4815 - The introduction circuit was being timed out too quickly while
4816 waiting for the rendezvous circuit to complete. Keep the intro
4817 circuit around longer instead of timing out and reopening new ones
4818 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
4819 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
4820 so it matches dir-spec.txt. Fixes bug 24262; bugfix
4822 - When handling multiple SOCKS request for the same .onion address,
4823 only fetch the service descriptor once.
4824 - Avoid a possible double close of a circuit by the intro point on
4825 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
4826 bugfix on 0.3.0.1-alpha.
4827 - When reloading configured onion services, copy all information
4828 from the old service object. Previously, some data was omitted,
4829 causing delays in descriptor upload, and other bugs. Fixes bug
4830 23790; bugfix on 0.2.1.9-alpha.
4832 o Minor bugfixes (path selection):
4833 - When selecting relays by bandwidth, avoid a rounding error that
4834 could sometimes cause load to be imbalanced incorrectly.
4835 Previously, we would always round upwards; now, we round towards
4836 the nearest integer. This had the biggest effect when a relay's
4837 weight adjustments should have given it weight 0, but it got
4838 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
4839 - When calculating the fraction of nodes that have descriptors, and
4840 all nodes in the network have zero bandwidths, count the number of
4841 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
4842 - Actually log the total bandwidth in compute_weighted_bandwidths().
4843 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
4845 o Minor bugfixes (portability):
4846 - Stop using the PATH_MAX variable, which is not defined on GNU
4847 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
4848 - Fix a bug in the bit-counting parts of our timing-wheel code on
4849 MSVC. (Note that MSVC is still not a supported build platform, due
4850 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
4853 o Minor bugfixes (relay):
4854 - When uploading our descriptor for the first time after startup,
4855 report the reason for uploading as "Tor just started" rather than
4856 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
4857 - Avoid unnecessary calls to directory_fetches_from_authorities() on
4858 relays, to prevent spurious address resolutions and descriptor
4859 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
4860 bugfix on in 0.2.8.1-alpha.
4861 - Avoid a crash when transitioning from client mode to bridge mode.
4862 Previously, we would launch the worker threads whenever our
4863 "public server" mode changed, but not when our "server" mode
4864 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
4866 o Minor bugfixes (testing):
4867 - Fix a spurious fuzzing-only use of an uninitialized value. Found
4868 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
4869 - Test that IPv6-only clients can use microdescriptors when running
4870 "make test-network-all". Requires chutney master 61c28b9 or later.
4871 Closes ticket 24109.
4872 - Prevent scripts/test/coverage from attempting to move gcov output
4873 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
4874 - Capture and detect several "Result does not fit" warnings in unit
4875 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
4877 - Fix additional channelpadding unit test failures by using mocked
4878 time instead of actual time for all tests. Fixes bug 23608; bugfix
4880 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
4881 to correctly handle cases where a caller gives it an RSA key of
4882 under 160 bits. (This is not actually a bug in Tor itself, but
4883 rather in our fuzzing code.) Fixes bug 24247; bugfix on
4884 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
4885 - Fix a broken unit test for the OutboundAddress option: the parsing
4886 function was never returning an error on failure. Fixes bug 23366;
4887 bugfix on 0.3.0.3-alpha.
4888 - Fix a signed-integer overflow in the unit tests for
4889 dir/download_status_random_backoff, which was untriggered until we
4890 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
4892 o Minor bugfixes (usability, control port):
4893 - Stop making an unnecessary routerlist check in NETINFO clock skew
4894 detection; this was preventing clients from reporting NETINFO clock
4895 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
4897 o Code simplification and refactoring:
4898 - Remove various ways of testing circuits and connections for
4899 "clientness"; instead, favor channel_is_client(). Part of
4901 - Extract the code for handling newly-open channels into a separate
4902 function from the general code to handle channel state
4903 transitions. This change simplifies our callgraph, reducing the
4904 size of the largest strongly connected component by roughly a
4905 factor of two. Closes ticket 22608.
4906 - Remove dead code for largely unused statistics on the number of
4907 times we've attempted various public key operations. Fixes bug
4908 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
4909 - Remove several now-obsolete functions for asking about old
4910 variants directory authority status. Closes ticket 22311; patch
4912 - Remove some of the code that once supported "Named" and "Unnamed"
4913 routers. Authorities no longer vote for these flags. Closes
4915 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
4916 and old hidden services, to indicate that they aren't suitable for
4917 new protocols or formats. Closes ticket 23026.
4918 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
4919 22521. Patch from Neel Chauhan.
4920 - Split the enormous circuit_send_next_onion_skin() function into
4921 multiple subfunctions. Closes ticket 22804.
4922 - Split the portions of the buffer.c module that handle particular
4923 protocols into separate modules. Part of ticket 23149.
4924 - Use our test macros more consistently, to produce more useful
4925 error messages when our unit tests fail. Add coccinelle patches to
4926 allow us to re-check for test macro uses. Closes ticket 22497.
4928 o Deprecated features:
4929 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
4930 now deprecated; they do not apply to relays, and they have had no
4931 effect on clients since 0.2.8.x. Closes ticket 19704.
4932 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
4933 only applies to direct unencrypted HTTP connections to your
4934 directory server, which your Tor probably isn't using. Closes
4938 - Add notes in man page regarding OS support for the various
4939 scheduler types. Attempt to use less jargon in the scheduler
4940 section. Closes ticket 24254.
4941 - Clarify that the Address option is entirely about setting an
4942 advertised IPv4 address. Closes ticket 18891.
4943 - Clarify the manpage's use of the term "address" to clarify what
4944 kind of address is intended. Closes ticket 21405.
4945 - Document that onion service subdomains are allowed, and ignored.
4946 Closes ticket 18736.
4947 - Clarify in the manual that "Sandbox 1" is only supported on Linux
4948 kernels. Closes ticket 22677.
4949 - Document all values of PublishServerDescriptor in the manpage.
4950 Closes ticket 15645.
4951 - Improve the documentation for the directory port part of the
4952 DirAuthority line. Closes ticket 20152.
4953 - Restore documentation for the authorities' "approved-routers"
4954 file. Closes ticket 21148.
4957 - The AllowDotExit option has been removed as unsafe. It has been
4958 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
4959 - The ClientDNSRejectInternalAddresses flag can no longer be set on
4960 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
4961 Closes ticket 21031.
4962 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
4963 nobody was using it any longer. Closes ticket 22377.
4966 Changes in version 0.3.1.9 - 2017-12-01:
4967 Tor 0.3.1.9 backports important security and stability fixes from the
4968 0.3.2 development series. All Tor users should upgrade to this
4969 release, or to another of the releases coming out today.
4971 o Major bugfixes (security, backport from 0.3.2.6-alpha):
4972 - Fix a denial of service bug where an attacker could use a
4973 malformed directory object to cause a Tor instance to pause while
4974 OpenSSL would try to read a passphrase from the terminal. (Tor
4975 instances run without a terminal, which is the case for most Tor
4976 packages, are not impacted.) Fixes bug 24246; bugfix on every
4977 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
4978 Found by OSS-Fuzz as testcase 6360145429790720.
4979 - Fix a denial of service issue where an attacker could crash a
4980 directory authority using a malformed router descriptor. Fixes bug
4981 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
4983 - When checking for replays in the INTRODUCE1 cell data for a
4984 (legacy) onion service, correctly detect replays in the RSA-
4985 encrypted part of the cell. We were previously checking for
4986 replays on the entire cell, but those can be circumvented due to
4987 the malleability of Tor's legacy hybrid encryption. This fix helps
4988 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
4989 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
4992 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
4993 - Fix a use-after-free error that could crash v2 Tor onion services
4994 when they failed to open circuits while expiring introduction
4995 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
4996 also tracked as TROVE-2017-013 and CVE-2017-8823.
4998 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
4999 - When running as a relay, make sure that we never build a path
5000 through ourselves, even in the case where we have somehow lost the
5001 version of our descriptor appearing in the consensus. Fixes part
5002 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5003 as TROVE-2017-012 and CVE-2017-8822.
5004 - When running as a relay, make sure that we never choose ourselves
5005 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
5006 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
5008 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
5009 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5010 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5011 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5012 identifying and finding a workaround to this bug and to Moritz,
5013 Arthur Edelstein, and Roger for helping to track it down and
5016 o Minor features (bridge):
5017 - Bridges now include notice in their descriptors that they are
5018 bridges, and notice of their distribution status, based on their
5019 publication settings. Implements ticket 18329. For more fine-
5020 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5023 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5024 - Add an IPv6 address for the "bastet" directory authority. Closes
5027 o Minor features (geoip):
5028 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5031 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
5032 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5033 relays, to prevent spurious address resolutions and descriptor
5034 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5035 bugfix on in 0.2.8.1-alpha.
5037 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
5038 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
5039 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5041 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
5042 - When a circuit is marked for close, do not attempt to package any
5043 cells for channels on that circuit. Previously, we would detect
5044 this condition lower in the call stack, when we noticed that the
5045 circuit had no attached channel, and log an annoying message.
5046 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5048 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
5049 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
5050 so it matches dir-spec.txt. Fixes bug 24262; bugfix
5053 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
5054 - Avoid a crash when transitioning from client mode to bridge mode.
5055 Previously, we would launch the worker threads whenever our
5056 "public server" mode changed, but not when our "server" mode
5057 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5060 Changes in version 0.3.0.13 - 2017-12-01
5061 Tor 0.3.0.13 backports important security and stability bugfixes from
5062 later Tor releases. All Tor users should upgrade to this release, or
5063 to another of the releases coming out today.
5065 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
5066 2018. If you need a release with long-term support, please stick with
5067 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5069 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5070 - Fix a denial of service bug where an attacker could use a
5071 malformed directory object to cause a Tor instance to pause while
5072 OpenSSL would try to read a passphrase from the terminal. (Tor
5073 instances run without a terminal, which is the case for most Tor
5074 packages, are not impacted.) Fixes bug 24246; bugfix on every
5075 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5076 Found by OSS-Fuzz as testcase 6360145429790720.
5077 - Fix a denial of service issue where an attacker could crash a
5078 directory authority using a malformed router descriptor. Fixes bug
5079 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5081 - When checking for replays in the INTRODUCE1 cell data for a
5082 (legacy) onion service, correctly detect replays in the RSA-
5083 encrypted part of the cell. We were previously checking for
5084 replays on the entire cell, but those can be circumvented due to
5085 the malleability of Tor's legacy hybrid encryption. This fix helps
5086 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5087 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5090 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5091 - Fix a use-after-free error that could crash v2 Tor onion services
5092 when they failed to open circuits while expiring introduction
5093 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5094 also tracked as TROVE-2017-013 and CVE-2017-8823.
5096 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5097 - When running as a relay, make sure that we never build a path
5098 through ourselves, even in the case where we have somehow lost the
5099 version of our descriptor appearing in the consensus. Fixes part
5100 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5101 as TROVE-2017-012 and CVE-2017-8822.
5102 - When running as a relay, make sure that we never choose ourselves
5103 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
5104 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
5106 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
5107 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5108 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5109 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5110 identifying and finding a workaround to this bug and to Moritz,
5111 Arthur Edelstein, and Roger for helping to track it down and
5114 o Minor features (security, windows, backport from 0.3.1.1-alpha):
5115 - Enable a couple of pieces of Windows hardening: one
5116 (HeapEnableTerminationOnCorruption) that has been on-by-default
5117 since Windows 8, and unavailable before Windows 7; and one
5118 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
5119 affect us, but shouldn't do any harm. Closes ticket 21953.
5121 o Minor features (bridge, backport from 0.3.1.9):
5122 - Bridges now include notice in their descriptors that they are
5123 bridges, and notice of their distribution status, based on their
5124 publication settings. Implements ticket 18329. For more fine-
5125 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5128 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5129 - Add an IPv6 address for the "bastet" directory authority. Closes
5132 o Minor features (geoip):
5133 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5136 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
5137 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5138 relays, to prevent spurious address resolutions and descriptor
5139 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5140 bugfix on in 0.2.8.1-alpha.
5142 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
5143 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
5144 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5146 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
5147 - When a circuit is marked for close, do not attempt to package any
5148 cells for channels on that circuit. Previously, we would detect
5149 this condition lower in the call stack, when we noticed that the
5150 circuit had no attached channel, and log an annoying message.
5151 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5153 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
5154 - Avoid a crash when transitioning from client mode to bridge mode.
5155 Previously, we would launch the worker threads whenever our
5156 "public server" mode changed, but not when our "server" mode
5157 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5159 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
5160 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
5161 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
5164 Changes in version 0.2.9.14 - 2017-12-01
5165 Tor 0.3.0.13 backports important security and stability bugfixes from
5166 later Tor releases. All Tor users should upgrade to this release, or
5167 to another of the releases coming out today.
5169 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
5170 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5171 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5172 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5173 identifying and finding a workaround to this bug and to Moritz,
5174 Arthur Edelstein, and Roger for helping to track it down and
5177 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5178 - Fix a denial of service bug where an attacker could use a
5179 malformed directory object to cause a Tor instance to pause while
5180 OpenSSL would try to read a passphrase from the terminal. (Tor
5181 instances run without a terminal, which is the case for most Tor
5182 packages, are not impacted.) Fixes bug 24246; bugfix on every
5183 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5184 Found by OSS-Fuzz as testcase 6360145429790720.
5185 - Fix a denial of service issue where an attacker could crash a
5186 directory authority using a malformed router descriptor. Fixes bug
5187 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5189 - When checking for replays in the INTRODUCE1 cell data for a
5190 (legacy) onion service, correctly detect replays in the RSA-
5191 encrypted part of the cell. We were previously checking for
5192 replays on the entire cell, but those can be circumvented due to
5193 the malleability of Tor's legacy hybrid encryption. This fix helps
5194 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5195 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5198 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5199 - Fix a use-after-free error that could crash v2 Tor onion services
5200 when they failed to open circuits while expiring introduction
5201 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5202 also tracked as TROVE-2017-013 and CVE-2017-8823.
5204 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5205 - When running as a relay, make sure that we never build a path
5206 through ourselves, even in the case where we have somehow lost the
5207 version of our descriptor appearing in the consensus. Fixes part
5208 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5209 as TROVE-2017-012 and CVE-2017-8822.
5211 o Minor features (bridge, backport from 0.3.1.9):
5212 - Bridges now include notice in their descriptors that they are
5213 bridges, and notice of their distribution status, based on their
5214 publication settings. Implements ticket 18329. For more fine-
5215 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5218 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5219 - Add an IPv6 address for the "bastet" directory authority. Closes
5222 o Minor features (geoip):
5223 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5226 o Minor features (security, windows, backport from 0.3.1.1-alpha):
5227 - Enable a couple of pieces of Windows hardening: one
5228 (HeapEnableTerminationOnCorruption) that has been on-by-default
5229 since Windows 8, and unavailable before Windows 7; and one
5230 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
5231 affect us, but shouldn't do any harm. Closes ticket 21953.
5233 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
5234 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5235 relays, to prevent spurious address resolutions and descriptor
5236 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5237 bugfix on in 0.2.8.1-alpha.
5239 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
5240 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
5241 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5243 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
5244 - When a circuit is marked for close, do not attempt to package any
5245 cells for channels on that circuit. Previously, we would detect
5246 this condition lower in the call stack, when we noticed that the
5247 circuit had no attached channel, and log an annoying message.
5248 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5250 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
5251 - Avoid a crash when transitioning from client mode to bridge mode.
5252 Previously, we would launch the worker threads whenever our
5253 "public server" mode changed, but not when our "server" mode
5254 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5256 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
5257 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
5258 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
5261 Changes in version 0.2.8.17 - 2017-12-01
5262 Tor 0.2.8.17 backports important security and stability bugfixes from
5263 later Tor releases. All Tor users should upgrade to this release, or
5264 to another of the releases coming out today.
5266 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
5267 2018. If you need a release with long-term support, please upgrade with
5268 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5270 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5271 - Fix a denial of service bug where an attacker could use a
5272 malformed directory object to cause a Tor instance to pause while
5273 OpenSSL would try to read a passphrase from the terminal. (Tor
5274 instances run without a terminal, which is the case for most Tor
5275 packages, are not impacted.) Fixes bug 24246; bugfix on every
5276 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5277 Found by OSS-Fuzz as testcase 6360145429790720.
5278 - When checking for replays in the INTRODUCE1 cell data for a
5279 (legacy) onion service, correctly detect replays in the RSA-
5280 encrypted part of the cell. We were previously checking for
5281 replays on the entire cell, but those can be circumvented due to
5282 the malleability of Tor's legacy hybrid encryption. This fix helps
5283 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5284 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5287 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5288 - Fix a use-after-free error that could crash v2 Tor onion services
5289 when they failed to open circuits while expiring introduction
5290 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5291 also tracked as TROVE-2017-013 and CVE-2017-8823.
5293 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5294 - When running as a relay, make sure that we never build a path through
5295 ourselves, even in the case where we have somehow lost the version of
5296 our descriptor appearing in the consensus. Fixes part of bug 21534;
5297 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
5300 o Minor features (bridge, backport from 0.3.1.9):
5301 - Bridges now include notice in their descriptors that they are
5302 bridges, and notice of their distribution status, based on their
5303 publication settings. Implements ticket 18329. For more fine-
5304 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5307 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5308 - Add an IPv6 address for the "bastet" directory authority. Closes
5311 o Minor features (geoip):
5312 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5315 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
5316 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
5317 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
5320 Changes in version 0.2.5.16 - 2017-12-01
5321 Tor 0.2.5.13 backports important security and stability bugfixes from
5322 later Tor releases. All Tor users should upgrade to this release, or
5323 to another of the releases coming out today.
5325 Note: the Tor 0.2.5 series will no longer be supported after 1 May
5326 2018. If you need a release with long-term support, please upgrade to
5327 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5329 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5330 - Fix a denial of service bug where an attacker could use a
5331 malformed directory object to cause a Tor instance to pause while
5332 OpenSSL would try to read a passphrase from the terminal. (Tor
5333 instances run without a terminal, which is the case for most Tor
5334 packages, are not impacted.) Fixes bug 24246; bugfix on every
5335 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5336 Found by OSS-Fuzz as testcase 6360145429790720.
5337 - When checking for replays in the INTRODUCE1 cell data for a
5338 (legacy) onion service, correctly detect replays in the RSA-
5339 encrypted part of the cell. We were previously checking for
5340 replays on the entire cell, but those can be circumvented due to
5341 the malleability of Tor's legacy hybrid encryption. This fix helps
5342 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5343 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5346 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5347 - When running as a relay, make sure that we never build a path
5348 through ourselves, even in the case where we have somehow lost the
5349 version of our descriptor appearing in the consensus. Fixes part
5350 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5351 as TROVE-2017-012 and CVE-2017-8822.
5353 o Minor features (bridge, backport from 0.3.1.9):
5354 - Bridges now include notice in their descriptors that they are
5355 bridges, and notice of their distribution status, based on their
5356 publication settings. Implements ticket 18329. For more fine-
5357 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5360 o Minor features (geoip):
5361 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5365 Changes in version 0.2.5.15 - 2017-10-25
5366 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
5367 series. It also adds a new directory authority, Bastet.
5369 Note: the Tor 0.2.5 series will no longer be supported after 1 May
5370 2018. If you need a release with long-term support, please upgrade to
5371 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5373 o Directory authority changes:
5374 - Add "Bastet" as a ninth directory authority to the default list.
5375 Closes ticket 23910.
5376 - The directory authority "Longclaw" has changed its IP address.
5377 Closes ticket 23592.
5379 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
5380 - Avoid an assertion failure bug affecting our implementation of
5381 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
5382 handling of "0xx" differs from what we had expected. Fixes bug
5383 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
5385 o Minor features (geoip):
5386 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
5389 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
5390 - Fix a memset() off the end of an array when packing cells. This
5391 bug should be harmless in practice, since the corrupted bytes are
5392 still in the same structure, and are always padding bytes,
5393 ignored, or immediately overwritten, depending on compiler
5394 behavior. Nevertheless, because the memset()'s purpose is to make
5395 sure that any other cell-handling bugs can't expose bytes to the
5396 network, we need to fix it. Fixes bug 22737; bugfix on
5397 0.2.4.11-alpha. Fixes CID 1401591.
5399 o Build features (backport from 0.3.1.5-alpha):
5400 - Tor's repository now includes a Travis Continuous Integration (CI)
5401 configuration file (.travis.yml). This is meant to help new
5402 developers and contributors who fork Tor to a Github repository be
5403 better able to test their changes, and understand what we expect
5404 to pass. To use this new build feature, you must fork Tor to your
5405 Github account, then go into the "Integrations" menu in the
5406 repository settings for your fork and enable Travis, then push
5407 your changes. Closes ticket 22636.
5410 Changes in version 0.2.8.16 - 2017-10-25
5411 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
5412 series, including a bugfix for a crash issue that had affected relays
5413 under memory pressure. It also adds a new directory authority, Bastet.
5415 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
5416 2018. If you need a release with long-term support, please stick with
5417 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5419 o Directory authority changes:
5420 - Add "Bastet" as a ninth directory authority to the default list.
5421 Closes ticket 23910.
5422 - The directory authority "Longclaw" has changed its IP address.
5423 Closes ticket 23592.
5425 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
5426 - Fix a timing-based assertion failure that could occur when the
5427 circuit out-of-memory handler freed a connection's output buffer.
5428 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
5430 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
5431 - Remove longclaw's IPv6 address, as it will soon change. Authority
5432 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
5433 3/8 directory authorities with IPv6 addresses, but there are also
5434 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
5436 o Minor features (geoip):
5437 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
5441 Changes in version 0.2.9.13 - 2017-10-25
5442 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
5443 series, including a bugfix for a crash issue that had affected relays
5444 under memory pressure. It also adds a new directory authority, Bastet.
5446 o Directory authority changes:
5447 - Add "Bastet" as a ninth directory authority to the default list.
5448 Closes ticket 23910.
5449 - The directory authority "Longclaw" has changed its IP address.
5450 Closes ticket 23592.
5452 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
5453 - Fix a timing-based assertion failure that could occur when the
5454 circuit out-of-memory handler freed a connection's output buffer.
5455 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
5457 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
5458 - Remove longclaw's IPv6 address, as it will soon change. Authority
5459 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
5460 3/8 directory authorities with IPv6 addresses, but there are also
5461 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
5463 o Minor features (geoip):
5464 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
5467 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
5468 - When a directory authority rejects a descriptor or extrainfo with
5469 a given digest, mark that digest as undownloadable, so that we do
5470 not attempt to download it again over and over. We previously
5471 tried to avoid downloading such descriptors by other means, but we
5472 didn't notice if we accidentally downloaded one anyway. This
5473 behavior became problematic in 0.2.7.2-alpha, when authorities
5474 began pinning Ed25519 keys. Fixes bug 22349; bugfix
5477 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
5478 - Clear the address when node_get_prim_orport() returns early.
5479 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
5481 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
5482 - When running as a Windows service, set the ID of the main thread
5483 correctly. Failure to do so made us fail to send log messages to
5484 the controller in 0.2.1.16-rc, slowed down controller event
5485 delivery in 0.2.7.3-rc and later, and crash with an assertion
5486 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
5487 Patch and diagnosis from "Vort".
5490 Changes in version 0.3.0.12 - 2017-10-25
5491 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
5492 series, including a bugfix for a crash issue that had affected relays
5493 under memory pressure. It also adds a new directory authority, Bastet.
5495 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
5496 2018. If you need a release with long-term support, please stick with
5497 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5499 o Directory authority changes:
5500 - Add "Bastet" as a ninth directory authority to the default list.
5501 Closes ticket 23910.
5502 - The directory authority "Longclaw" has changed its IP address.
5503 Closes ticket 23592.
5505 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
5506 - Fix a timing-based assertion failure that could occur when the
5507 circuit out-of-memory handler freed a connection's output buffer.
5508 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
5510 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
5511 - Remove longclaw's IPv6 address, as it will soon change. Authority
5512 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
5513 3/8 directory authorities with IPv6 addresses, but there are also
5514 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
5516 o Minor features (geoip):
5517 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
5520 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
5521 - When a directory authority rejects a descriptor or extrainfo with
5522 a given digest, mark that digest as undownloadable, so that we do
5523 not attempt to download it again over and over. We previously
5524 tried to avoid downloading such descriptors by other means, but we
5525 didn't notice if we accidentally downloaded one anyway. This
5526 behavior became problematic in 0.2.7.2-alpha, when authorities
5527 began pinning Ed25519 keys. Fixes bug 22349; bugfix
5530 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
5531 - Avoid a possible double close of a circuit by the intro point on
5532 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
5533 bugfix on 0.3.0.1-alpha.
5535 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
5536 - Clear the address when node_get_prim_orport() returns early.
5537 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
5539 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
5540 - When running as a Windows service, set the ID of the main thread
5541 correctly. Failure to do so made us fail to send log messages to
5542 the controller in 0.2.1.16-rc, slowed down controller event
5543 delivery in 0.2.7.3-rc and later, and crash with an assertion
5544 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
5545 Patch and diagnosis from "Vort".
5548 Changes in version 0.3.1.8 - 2017-10-25
5549 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
5550 It includes several bugfixes, including a bugfix for a crash issue
5551 that had affected relays under memory pressure. It also adds
5552 a new directory authority, Bastet.
5554 o Directory authority changes:
5555 - Add "Bastet" as a ninth directory authority to the default list.
5556 Closes ticket 23910.
5557 - The directory authority "Longclaw" has changed its IP address.
5558 Closes ticket 23592.
5560 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
5561 - Fix a timing-based assertion failure that could occur when the
5562 circuit out-of-memory handler freed a connection's output buffer.
5563 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
5565 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
5566 - Remove longclaw's IPv6 address, as it will soon change. Authority
5567 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
5568 3/8 directory authorities with IPv6 addresses, but there are also
5569 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
5571 o Minor features (geoip):
5572 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
5575 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
5576 - Fix a compilation warning when building with zstd support on
5577 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
5578 and fixed by Andreas Stieger.
5580 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
5581 - Handle a pathological case when decompressing Zstandard data when
5582 the output buffer size is zero. Fixes bug 23551; bugfix
5585 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
5586 - Remove the length limit on HTTP status lines that authorities can
5587 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
5589 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
5590 - Avoid a possible double close of a circuit by the intro point on
5591 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
5592 bugfix on 0.3.0.1-alpha.
5594 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
5595 - Clear the address when node_get_prim_orport() returns early.
5596 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
5598 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
5599 - Fix additional channelpadding unit test failures by using mocked
5600 time instead of actual time for all tests. Fixes bug 23608; bugfix
5604 Changes in version 0.2.8.15 - 2017-09-18
5605 Tor 0.2.8.15 backports a collection of bugfixes from later
5608 Most significantly, it includes a fix for TROVE-2017-008, a
5609 security bug that affects hidden services running with the
5610 SafeLogging option disabled. For more information, see
5611 https://trac.torproject.org/projects/tor/ticket/23490
5613 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
5614 2018. We suggest that you upgrade to the latest stable release if
5615 possible. If you can't, we recommend that you upgrade at least to
5616 0.2.9, which will be supported until 2020.
5618 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
5619 - Avoid an assertion failure bug affecting our implementation of
5620 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
5621 handling of "0xx" differs from what we had expected. Fixes bug
5622 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
5625 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
5628 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
5629 - Backport a fix for an "unused variable" warning that appeared
5630 in some versions of mingw. Fixes bug 22838; bugfix on
5633 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
5634 - Fix a memset() off the end of an array when packing cells. This
5635 bug should be harmless in practice, since the corrupted bytes are
5636 still in the same structure, and are always padding bytes,
5637 ignored, or immediately overwritten, depending on compiler
5638 behavior. Nevertheless, because the memset()'s purpose is to make
5639 sure that any other cell-handling bugs can't expose bytes to the
5640 network, we need to fix it. Fixes bug 22737; bugfix on
5641 0.2.4.11-alpha. Fixes CID 1401591.
5643 o Build features (backport from 0.3.1.5-alpha):
5644 - Tor's repository now includes a Travis Continuous Integration (CI)
5645 configuration file (.travis.yml). This is meant to help new
5646 developers and contributors who fork Tor to a Github repository be
5647 better able to test their changes, and understand what we expect
5648 to pass. To use this new build feature, you must fork Tor to your
5649 Github account, then go into the "Integrations" menu in the
5650 repository settings for your fork and enable Travis, then push
5651 your changes. Closes ticket 22636.
5654 Changes in version 0.2.9.12 - 2017-09-18
5655 Tor 0.2.9.12 backports a collection of bugfixes from later
5658 Most significantly, it includes a fix for TROVE-2017-008, a
5659 security bug that affects hidden services running with the
5660 SafeLogging option disabled. For more information, see
5661 https://trac.torproject.org/projects/tor/ticket/23490
5663 o Major features (security, backport from 0.3.0.2-alpha):
5664 - Change the algorithm used to decide DNS TTLs on client and server
5665 side, to better resist DNS-based correlation attacks like the
5666 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
5667 Feamster. Now relays only return one of two possible DNS TTL
5668 values, and clients are willing to believe DNS TTL values up to 3
5669 hours long. Closes ticket 19769.
5671 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
5672 - Fix a rare crash when sending a begin cell on a circuit whose
5673 linked directory connection had already been closed. Fixes bug
5674 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
5676 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
5677 - Fix a bug that prevented exit nodes from caching DNS records for
5678 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
5680 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
5681 - Fix a typo that had prevented TPROXY-based transparent proxying
5682 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
5683 Patch from "d4fq0fQAgoJ".
5685 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
5686 - Avoid an assertion failure bug affecting our implementation of
5687 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
5688 handling of "0xx" differs from what we had expected. Fixes bug
5689 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
5691 o Minor features (code style, backport from 0.3.1.3-alpha):
5692 - Add "Falls through" comments to our codebase, in order to silence
5693 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
5694 Stieger. Closes ticket 22446.
5696 o Minor features (geoip):
5697 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
5700 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
5701 - Roll over monthly accounting at the configured hour and minute,
5702 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
5703 Found by Andrey Karpov with PVS-Studio.
5705 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
5706 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
5707 bugfix on 0.2.8.1-alpha.
5708 - Fix warnings when building with libscrypt and openssl scrypt support
5709 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
5710 - When building with certain versions the mingw C header files, avoid
5711 float-conversion warnings when calling the C functions isfinite(),
5712 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
5714 o Minor bugfixes (compilation, backport from 0.3.1.7):
5715 - Avoid compiler warnings in the unit tests for running tor_sscanf()
5716 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
5718 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
5719 - Backport a fix for an "unused variable" warning that appeared
5720 in some versions of mingw. Fixes bug 22838; bugfix on
5723 o Minor bugfixes (controller, backport from 0.3.1.7):
5724 - Do not crash when receiving a HSPOST command with an empty body.
5725 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
5726 - Do not crash when receiving a POSTDESCRIPTOR command with an
5727 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
5729 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
5730 - Avoid Coverity build warnings related to our BUG() macro. By
5731 default, Coverity treats BUG() as the Linux kernel does: an
5732 instant abort(). We need to override that so our BUG() macro
5733 doesn't prevent Coverity from analyzing functions that use it.
5734 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
5736 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
5737 - Fix a memset() off the end of an array when packing cells. This
5738 bug should be harmless in practice, since the corrupted bytes are
5739 still in the same structure, and are always padding bytes,
5740 ignored, or immediately overwritten, depending on compiler
5741 behavior. Nevertheless, because the memset()'s purpose is to make
5742 sure that any other cell-handling bugs can't expose bytes to the
5743 network, we need to fix it. Fixes bug 22737; bugfix on
5744 0.2.4.11-alpha. Fixes CID 1401591.
5746 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
5747 - When setting the maximum number of connections allowed by the OS,
5748 always allow some extra file descriptors for other files. Fixes
5749 bug 22797; bugfix on 0.2.0.10-alpha.
5751 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
5752 - Avoid a sandbox failure when trying to re-bind to a socket and
5753 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
5755 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
5756 - Permit the fchmod system call, to avoid crashing on startup when
5757 starting with the seccomp2 sandbox and an unexpected set of
5758 permissions on the data directory or its contents. Fixes bug
5759 22516; bugfix on 0.2.5.4-alpha.
5761 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
5762 - Avoid a double-marked-circuit warning that could happen when we
5763 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
5766 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
5767 - Reject version numbers with non-numeric prefixes (such as +, -, or
5768 whitespace). Disallowing whitespace prevents differential version
5769 parsing between POSIX-based and Windows platforms. Fixes bug 21507
5770 and part of 21508; bugfix on 0.0.8pre1.
5772 o Build features (backport from 0.3.1.5-alpha):
5773 - Tor's repository now includes a Travis Continuous Integration (CI)
5774 configuration file (.travis.yml). This is meant to help new
5775 developers and contributors who fork Tor to a Github repository be
5776 better able to test their changes, and understand what we expect
5777 to pass. To use this new build feature, you must fork Tor to your
5778 Github account, then go into the "Integrations" menu in the
5779 repository settings for your fork and enable Travis, then push
5780 your changes. Closes ticket 22636.
5783 Changes in version 0.3.0.11 - 2017-09-18
5784 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
5787 Most significantly, it includes a fix for TROVE-2017-008, a
5788 security bug that affects hidden services running with the
5789 SafeLogging option disabled. For more information, see
5790 https://trac.torproject.org/projects/tor/ticket/23490
5792 o Minor features (code style, backport from 0.3.1.7):
5793 - Add "Falls through" comments to our codebase, in order to silence
5794 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
5795 Stieger. Closes ticket 22446.
5798 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
5801 o Minor bugfixes (compilation, backport from 0.3.1.7):
5802 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
5803 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
5805 o Minor bugfixes (controller, backport from 0.3.1.7):
5806 - Do not crash when receiving a HSPOST command with an empty body.
5807 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
5808 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
5809 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
5811 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
5812 - When setting the maximum number of connections allowed by the OS,
5813 always allow some extra file descriptors for other files. Fixes
5814 bug 22797; bugfix on 0.2.0.10-alpha.
5816 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
5817 - Remove a forgotten debugging message when an introduction point
5818 successfully establishes a hidden service prop224 circuit with
5820 - Change three other log_warn() for an introduction point to
5821 protocol warnings, because they can be failure from the network
5822 and are not relevant to the operator. Fixes bug 23078; bugfix on
5823 0.3.0.1-alpha and 0.3.0.2-alpha.
5826 Changes in version 0.3.1.7 - 2017-09-18
5827 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
5829 With the 0.3.1 series, Tor now serves and downloads directory
5830 information in more compact formats, to save on bandwidth overhead. It
5831 also contains a new padding system to resist netflow-based traffic
5832 analysis, and experimental support for building parts of Tor in Rust
5833 (though no parts of Tor are in Rust yet). There are also numerous
5834 small features, bugfixes on earlier release series, and groundwork for
5835 the hidden services revamp of 0.3.2.
5837 This release also includes a fix for TROVE-2017-008, a security bug
5838 that affects hidden services running with the SafeLogging option
5839 disabled. For more information, see
5840 https://trac.torproject.org/projects/tor/ticket/23490
5842 Per our stable release policy, we plan to support each stable release
5843 series for at least the next nine months, or for three months after
5844 the first stable release of the next series: whichever is longer. If
5845 you need a release with long-term support, we recommend that you stay
5846 with the 0.2.9 series.
5848 Below is a list of the changes since 0.3.0. For a list of all
5849 changes since 0.3.1.6-rc, see the ChangeLog file.
5852 - To build with zstd and lzma support, Tor now requires the
5853 pkg-config tool at build time.
5855 o Major bugfixes (security, hidden services, loggging):
5856 - Fix a bug where we could log uninitialized stack when a certain
5857 hidden service error occurred while SafeLogging was disabled.
5858 Fixes bug #23490; bugfix on 0.2.7.2-alpha.
5859 This is also tracked as TROVE-2017-008 and CVE-2017-0380.
5861 o Major features (build system, continuous integration):
5862 - Tor's repository now includes a Travis Continuous Integration (CI)
5863 configuration file (.travis.yml). This is meant to help new
5864 developers and contributors who fork Tor to a Github repository be
5865 better able to test their changes, and understand what we expect
5866 to pass. To use this new build feature, you must fork Tor to your
5867 Github account, then go into the "Integrations" menu in the
5868 repository settings for your fork and enable Travis, then push
5869 your changes. Closes ticket 22636.
5871 o Major features (directory protocol):
5872 - Tor relays and authorities can now serve clients an abbreviated
5873 version of the consensus document, containing only the changes
5874 since an older consensus document that the client holds. Clients
5875 now request these documents when available. When both client and
5876 server use this new protocol, they will use far less bandwidth (up
5877 to 94% less) to keep the client's consensus up-to-date. Implements
5878 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
5879 - Tor can now compress directory traffic with lzma or with zstd
5880 compression algorithms, which can deliver better bandwidth
5881 performance. Because lzma is computationally expensive, it's only
5882 used for documents that can be compressed once and served many
5883 times. Support for these algorithms requires that tor is built
5884 with the libzstd and/or liblzma libraries available. Implements
5885 proposal 278; closes ticket 21662.
5886 - Relays now perform the more expensive compression operations, and
5887 consensus diff generation, in worker threads. This separation
5888 avoids delaying the main thread when a new consensus arrives.
5890 o Major features (experimental):
5891 - Tor can now build modules written in Rust. To turn this on, pass
5892 the "--enable-rust" flag to the configure script. It's not time to
5893 get excited yet: currently, there is no actual Rust functionality
5894 beyond some simple glue code, and a notice at startup to tell you
5895 that Rust is running. Still, we hope that programmers and
5896 packagers will try building Tor with Rust support, so that we can
5897 find issues and solve portability problems. Closes ticket 22106.
5899 o Major features (traffic analysis resistance):
5900 - Connections between clients and relays now send a padding cell in
5901 each direction every 1.5 to 9.5 seconds (tunable via consensus
5902 parameters). This padding will not resist specialized
5903 eavesdroppers, but it should be enough to make many ISPs' routine
5904 network flow logging less useful in traffic analysis against
5907 Padding is negotiated using Tor's link protocol, so both relays
5908 and clients must upgrade for this to take effect. Clients may
5909 still send padding despite the relay's version by setting
5910 ConnectionPadding 1 in torrc, and may disable padding by setting
5911 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
5912 users with the torrc option ReducedConnectionPadding. Implements
5913 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
5914 - Relays will publish 24 hour totals of padding and non-padding cell
5915 counts to their extra-info descriptors, unless PaddingStatistics 0
5916 is set in torrc. These 24 hour totals are also rounded to
5919 o Major bugfixes (hidden service, relay, security):
5920 - Fix a remotely triggerable assertion failure when a hidden service
5921 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
5922 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
5923 - Fix a remotely triggerable assertion failure caused by receiving a
5924 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
5925 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
5928 o Major bugfixes (path selection, security):
5929 - When choosing which guard to use for a circuit, avoid the exit's
5930 family along with the exit itself. Previously, the new guard
5931 selection logic avoided the exit, but did not consider its family.
5932 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
5933 006 and CVE-2017-0377.
5935 o Major bugfixes (connection usage):
5936 - We use NETINFO cells to try to determine if both relays involved
5937 in a connection will agree on the canonical status of that
5938 connection. We prefer the connections where this is the case for
5939 extend cells, and try to close connections where relays disagree
5940 on their canonical status early. Also, we now prefer the oldest
5941 valid connection for extend cells. These two changes should reduce
5942 the number of long-term connections that are kept open between
5943 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
5944 - Relays now log hourly statistics (look for
5945 "channel_check_for_duplicates" lines) on the total number of
5946 connections to other relays. If the number of connections per
5947 relay is unexpectedly large, this log message is at notice level.
5948 Otherwise it is at info.
5950 o Major bugfixes (entry guards):
5951 - When starting with an old consensus, do not add new entry guards
5952 unless the consensus is "reasonably live" (under 1 day old). Fixes
5953 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
5954 - Don't block bootstrapping when a primary bridge is offline and we
5955 can't get its descriptor. Fixes bug 22325; fixes one case of bug
5956 21969; bugfix on 0.3.0.3-alpha.
5958 o Major bugfixes (linux TPROXY support):
5959 - Fix a typo that had prevented TPROXY-based transparent proxying
5960 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
5961 Patch from "d4fq0fQAgoJ".
5963 o Major bugfixes (openbsd, denial-of-service):
5964 - Avoid an assertion failure bug affecting our implementation of
5965 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
5966 handling of "0xx" differs from what we had expected. Fixes bug
5967 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
5969 o Major bugfixes (relay, link handshake):
5970 - When performing the v3 link handshake on a TLS connection, report
5971 that we have the x509 certificate that we actually used on that
5972 connection, even if we have changed certificates since that
5973 connection was first opened. Previously, we would claim to have
5974 used our most recent x509 link certificate, which would sometimes
5975 make the link handshake fail. Fixes one case of bug 22460; bugfix
5978 o Major bugfixes (relays, key management):
5979 - Regenerate link and authentication certificates whenever the key
5980 that signs them changes; also, regenerate link certificates
5981 whenever the signed key changes. Previously, these processes were
5982 only weakly coupled, and we relays could (for minutes to hours)
5983 wind up with an inconsistent set of keys and certificates, which
5984 other relays would not accept. Fixes two cases of bug 22460;
5985 bugfix on 0.3.0.1-alpha.
5986 - When sending an Ed25519 signing->link certificate in a CERTS cell,
5987 send the certificate that matches the x509 certificate that we
5988 used on the TLS connection. Previously, there was a race condition
5989 if the TLS context rotated after we began the TLS handshake but
5990 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
5993 o Minor features (security, windows):
5994 - Enable a couple of pieces of Windows hardening: one
5995 (HeapEnableTerminationOnCorruption) that has been on-by-default
5996 since Windows 8, and unavailable before Windows 7; and one
5997 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
5998 affect us, but shouldn't do any harm. Closes ticket 21953.
6000 o Minor features (bridge authority):
6001 - Add "fingerprint" lines to the networkstatus-bridges file produced
6002 by bridge authorities. Closes ticket 22207.
6004 o Minor features (code style):
6005 - Add "Falls through" comments to our codebase, in order to silence
6006 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
6007 Stieger. Closes ticket 22446.
6009 o Minor features (config options):
6010 - Allow "%include" directives in torrc configuration files. These
6011 directives import the settings from other files, or from all the
6012 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
6013 - Make SAVECONF return an error when overwriting a torrc that has
6014 includes. Using SAVECONF with the FORCE option will allow it to
6015 overwrite torrc even if includes are used. Related to ticket 1922.
6016 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
6017 will work without the FORCE option. Related to ticket 1922.
6019 o Minor features (controller):
6020 - Warn the first time that a controller requests data in the long-
6021 deprecated 'GETINFO network-status' format. Closes ticket 21703.
6023 o Minor features (defaults):
6024 - The default value for UseCreateFast is now 0: clients which
6025 haven't yet received a consensus document will now use a proper
6026 ntor handshake to talk to their directory servers whenever they
6027 can. Closes ticket 21407.
6028 - Onion key rotation and expiry intervals are now defined as a
6029 network consensus parameter, per proposal 274. The default
6030 lifetime of an onion key is increased from 7 to 28 days. Old onion
6031 keys will expire after 7 days by default. This change will make
6032 consensus diffs much smaller, and save significant bandwidth.
6033 Closes ticket 21641.
6035 o Minor features (defensive programming):
6036 - Create a pair of consensus parameters, nf_pad_tor2web and
6037 nf_pad_single_onion, to disable netflow padding in the consensus
6038 for non-anonymous connections in case the overhead is high. Closes
6041 o Minor features (diagnostic):
6042 - Add a stack trace to the bug warnings that can be logged when
6043 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
6044 attempt for bug 23105.
6045 - Add logging messages to try to diagnose a rare bug that seems to
6046 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
6047 think this is happening because of incorrect system clocks, but
6048 we'd like to know for certain. Diagnostic for bug 22466.
6049 - Avoid an assertion failure, and log a better error message, when
6050 unable to remove a file from the consensus cache on Windows.
6051 Attempts to mitigate and diagnose bug 22752.
6053 o Minor features (directory authority):
6054 - Improve the message that authorities report to relays that present
6055 RSA/Ed25519 keypairs that conflict with previously pinned keys.
6056 Closes ticket 22348.
6058 o Minor features (directory cache, consensus diff):
6059 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
6060 operators with low-resource environments to adjust the number of
6061 consensuses they'll store and generate diffs from. Most cache
6062 operators should leave it unchanged. Helps to work around
6065 o Minor features (fallback directory list):
6066 - Update the fallback directory mirror whitelist and blacklist based
6067 on operator emails. Closes task 21121.
6068 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6069 December 2016 (of which ~126 were still functional) with a list of
6070 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6071 2017. Resolves ticket 21564.
6073 o Minor features (geoip):
6074 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
6077 o Minor features (hidden services, logging):
6078 - Log a message when a hidden service descriptor has fewer
6079 introduction points than specified in
6080 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
6081 - Log a message when a hidden service reaches its introduction point
6082 circuit limit, and when that limit is reset. Follow up to ticket
6083 21594; closes ticket 21622.
6084 - Warn user if multiple entries in EntryNodes and at least one
6085 HiddenService are used together. Pinning EntryNodes along with a
6086 hidden service can be possibly harmful; for instance see ticket
6087 14917 or 21155. Closes ticket 21155.
6089 o Minor features (linux seccomp2 sandbox):
6090 - We now have a document storage backend compatible with the Linux
6091 seccomp2 sandbox. This backend is used for consensus documents and
6092 diffs between them; in the long term, we'd like to use it for
6093 unparseable directory material too. Closes ticket 21645
6094 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
6095 from 1MB to 16MB. This was necessary with the glibc allocator in
6096 order to allow worker threads to allocate more memory -- which in
6097 turn is necessary because of our new use of worker threads for
6098 compression. Closes ticket 22096.
6100 o Minor features (logging):
6101 - Log files are no longer created world-readable by default.
6102 (Previously, most distributors would store the logs in a non-
6103 world-readable location to prevent inappropriate access. This
6104 change is an extra precaution.) Closes ticket 21729; patch
6107 o Minor features (performance):
6108 - Our Keccak (SHA-3) implementation now accesses memory more
6109 efficiently, especially on little-endian systems. Closes
6111 - Add an O(1) implementation of channel_find_by_global_id(), to
6112 speed some controller functions.
6114 o Minor features (relay, configuration):
6115 - The MyFamily option may now be repeated as many times as desired,
6116 for relays that want to configure large families. Closes ticket
6117 4998; patch by Daniel Pinto.
6119 o Minor features (relay, performance):
6120 - Always start relays with at least two worker threads, to prevent
6121 priority inversion on slow tasks. Part of the fix for bug 22883.
6122 - Allow background work to be queued with different priorities, so
6123 that a big pile of slow low-priority jobs will not starve out
6124 higher priority jobs. This lays the groundwork for a fix for
6127 o Minor features (safety):
6128 - Add an explicit check to extrainfo_parse_entry_from_string() for
6129 NULL inputs. We don't believe this can actually happen, but it may
6130 help silence a warning from the Clang analyzer. Closes
6133 o Minor features (testing):
6134 - Add more tests for compression backend initialization. Closes
6136 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
6137 When Tor is compiled with this option, we disable a number of
6138 redundant memory-safety failsafes that are intended to stop bugs
6139 from becoming security issues. This makes it easier to hunt for
6140 bugs that would be security issues without the failsafes turned
6141 on. Closes ticket 21439.
6142 - Add a general event-tracing instrumentation support to Tor. This
6143 subsystem will enable developers and researchers to add fine-
6144 grained instrumentation to their Tor instances, for use when
6145 examining Tor network performance issues. There are no trace
6146 events yet, and event-tracing is off by default unless enabled at
6147 compile time. Implements ticket 13802.
6148 - Improve our version parsing tests: add tests for typical version
6149 components, add tests for invalid versions, including numeric
6150 range and non-numeric prefixes. Unit tests 21278, 21450, and
6151 21507. Partially implements 21470.
6153 o Minor bugfixes (bandwidth accounting):
6154 - Roll over monthly accounting at the configured hour and minute,
6155 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
6156 Found by Andrey Karpov with PVS-Studio.
6158 o Minor bugfixes (code correctness):
6159 - Accurately identify client connections by their lack of peer
6160 authentication. This means that we bail out earlier if asked to
6161 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
6164 o Minor bugfixes (compilation warnings):
6165 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
6166 22915; bugfix on 0.2.8.1-alpha.
6167 - Fix warnings when building with libscrypt and openssl scrypt
6168 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
6169 - When building with certain versions of the mingw C header files,
6170 avoid float-conversion warnings when calling the C functions
6171 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
6174 o Minor bugfixes (compilation):
6175 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
6176 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
6178 o Minor bugfixes (compression):
6179 - When spooling compressed data to an output buffer, don't try to
6180 spool more data when there is no more data to spool and we are not
6181 trying to flush the input. Previously, we would sometimes launch
6182 compression requests with nothing to do, which interferes with our
6183 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
6185 o Minor bugfixes (configuration):
6186 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
6187 bug 22252; bugfix on 0.2.9.3-alpha.
6189 o Minor bugfixes (connection lifespan):
6190 - Allow more control over how long TLS connections are kept open:
6191 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
6192 single option called CircuitsAvailableTimeout. Also, allow the
6193 consensus to control the default values for both this preference
6194 and the lifespan of relay-to-relay connections. Fixes bug 17592;
6195 bugfix on 0.2.5.5-alpha.
6196 - Increase the initial circuit build timeout testing frequency, to
6197 help ensure that ReducedConnectionPadding clients finish learning
6198 a timeout before their orconn would expire. The initial testing
6199 rate was set back in the days of TAP and before the Tor Browser
6200 updater, when we had to be much more careful about new clients
6201 making lots of circuits. With this change, a circuit build timeout
6202 is learned in about 15-20 minutes, instead of 100-120 minutes.
6204 o Minor bugfixes (controller):
6205 - Do not crash when receiving a HSPOST command with an empty body.
6206 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
6207 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
6208 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
6209 - GETINFO onions/current and onions/detached no longer respond with
6210 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
6211 - Trigger HS descriptor events on the control port when the client
6212 fails to pick a hidden service directory for a hidden service.
6213 This can happen if all the hidden service directories are in
6214 ExcludeNodes, or they have all been queried within the last 15
6215 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
6217 o Minor bugfixes (correctness):
6218 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6219 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6221 o Minor bugfixes (coverity build support):
6222 - Avoid Coverity build warnings related to our BUG() macro. By
6223 default, Coverity treats BUG() as the Linux kernel does: an
6224 instant abort(). We need to override that so our BUG() macro
6225 doesn't prevent Coverity from analyzing functions that use it.
6226 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
6228 o Minor bugfixes (defensive programming):
6229 - Detect and break out of infinite loops in our compression code. We
6230 don't think that any such loops exist now, but it's best to be
6231 safe. Closes ticket 22672.
6232 - Fix a memset() off the end of an array when packing cells. This
6233 bug should be harmless in practice, since the corrupted bytes are
6234 still in the same structure, and are always padding bytes,
6235 ignored, or immediately overwritten, depending on compiler
6236 behavior. Nevertheless, because the memset()'s purpose is to make
6237 sure that any other cell-handling bugs can't expose bytes to the
6238 network, we need to fix it. Fixes bug 22737; bugfix on
6239 0.2.4.11-alpha. Fixes CID 1401591.
6241 o Minor bugfixes (directory authority):
6242 - When a directory authority rejects a descriptor or extrainfo with
6243 a given digest, mark that digest as undownloadable, so that we do
6244 not attempt to download it again over and over. We previously
6245 tried to avoid downloading such descriptors by other means, but we
6246 didn't notice if we accidentally downloaded one anyway. This
6247 behavior became problematic in 0.2.7.2-alpha, when authorities
6248 began pinning Ed25519 keys. Fixes bug 22349; bugfix
6250 - When rejecting a router descriptor for running an obsolete version
6251 of Tor without ntor support, warn about the obsolete tor version,
6252 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
6253 - Prevent the shared randomness subsystem from asserting when
6254 initialized by a bridge authority with an incomplete configuration
6255 file. Fixes bug 21586; bugfix on 0.2.9.8.
6257 o Minor bugfixes (error reporting, windows):
6258 - When formatting Windows error messages, use the English format to
6259 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
6262 o Minor bugfixes (exit-side DNS):
6263 - Fix an untriggerable assertion that checked the output of a
6264 libevent DNS error, so that the assertion actually behaves as
6265 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
6266 Karpov using PVS-Studio.
6268 o Minor bugfixes (fallback directories):
6269 - Make the usage example in updateFallbackDirs.py actually work, and
6270 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
6271 - Decrease the guard flag average required to be a fallback. This
6272 allows us to keep relays that have their guard flag removed when
6273 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
6274 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
6275 bugfix on 0.2.8.1-alpha.
6276 - Make sure fallback directory mirrors have the same address, port,
6277 and relay identity key for at least 30 days before they are
6278 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
6280 o Minor bugfixes (file limits, osx):
6281 - When setting the maximum number of connections allowed by the OS,
6282 always allow some extra file descriptors for other files. Fixes
6283 bug 22797; bugfix on 0.2.0.10-alpha.
6285 o Minor bugfixes (hidden services):
6286 - Increase the number of circuits that a service is allowed to
6287 open over a specific period of time. The value was lower than it
6288 should be (8 vs 12) in the normal case of 3 introduction points.
6289 Fixes bug 22159; bugfix on 0.3.0.5-rc.
6290 - Fix a BUG warning during HSv3 descriptor decoding that could be
6291 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
6292 on 0.3.0.1-alpha. Bug found by "haxxpop".
6293 - Stop printing a cryptic warning when a hidden service gets a
6294 request to connect to a virtual port that it hasn't configured.
6295 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
6296 - Simplify hidden service descriptor creation by using an existing
6297 flag to check if an introduction point is established. Fixes bug
6298 21599; bugfix on 0.2.7.2-alpha.
6300 o Minor bugfixes (link handshake):
6301 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
6302 months, and regenerate it when it is within one month of expiring.
6303 Previously, we had generated this certificate at startup with a
6304 ten-year lifetime, but that could lead to weird behavior when Tor
6305 was started with a grossly inaccurate clock. Mitigates bug 22466;
6306 mitigation on 0.3.0.1-alpha.
6308 o Minor bugfixes (linux seccomp2 sandbox):
6309 - Avoid a sandbox failure when trying to re-bind to a socket and
6310 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
6311 - Permit the fchmod system call, to avoid crashing on startup when
6312 starting with the seccomp2 sandbox and an unexpected set of
6313 permissions on the data directory or its contents. Fixes bug
6314 22516; bugfix on 0.2.5.4-alpha.
6316 o Minor bugfixes (logging):
6317 - When decompressing, do not warn if we fail to decompress using a
6318 compression method that we merely guessed. Fixes part of bug
6319 22670; bugfix on 0.1.1.14-alpha.
6320 - When decompressing, treat mismatch between content-encoding and
6321 actual compression type as a protocol warning. Fixes part of bug
6322 22670; bugfix on 0.1.1.9-alpha.
6323 - Downgrade "assigned_to_cpuworker failed" message to info-level
6324 severity. In every case that can reach it, either a better warning
6325 has already been logged, or no warning is warranted. Fixes bug
6326 22356; bugfix on 0.2.6.3-alpha.
6327 - Log a better message when a directory authority replies to an
6328 upload with an unexpected status code. Fixes bug 11121; bugfix
6330 - Downgrade a log statement about unexpected relay cells from "bug"
6331 to "protocol warning", because there is at least one use case
6332 where it can be triggered by a buggy tor implementation. Fixes bug
6333 21293; bugfix on 0.1.1.14-alpha.
6335 o Minor bugfixes (logging, relay):
6336 - Remove a forgotten debugging message when an introduction point
6337 successfully establishes a hidden service prop224 circuit with
6339 - Change three other log_warn() for an introduction point to
6340 protocol warnings, because they can be failure from the network
6341 and are not relevant to the operator. Fixes bug 23078; bugfix on
6342 0.3.0.1-alpha and 0.3.0.2-alpha.
6344 o Minor bugfixes (relay):
6345 - Inform the geoip and rephist modules about all requests, even on
6346 relays that are only fetching microdescriptors. Fixes a bug
6347 related to 21585; bugfix on 0.3.0.1-alpha.
6349 o Minor bugfixes (memory leaks):
6350 - Fix a small memory leak at exit from the backtrace handler code.
6351 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
6352 - When directory authorities reject a router descriptor due to
6353 keypinning, free the router descriptor rather than leaking the
6354 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
6355 - Fix a small memory leak when validating a configuration that uses
6356 two or more AF_UNIX sockets for the same port type. Fixes bug
6357 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
6359 o Minor bugfixes (process behavior):
6360 - When exiting because of an error, always exit with a nonzero exit
6361 status. Previously, we would fail to report an error in our exit
6362 status in cases related to __OwningControllerProcess failure,
6363 lockfile contention, and Ed25519 key initialization. Fixes bug
6364 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
6365 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
6368 o Minor bugfixes (robustness, error handling):
6369 - Improve our handling of the cases where OpenSSL encounters a
6370 memory error while encoding keys and certificates. We haven't
6371 observed these errors in the wild, but if they do happen, we now
6372 detect and respond better. Fixes bug 19418; bugfix on all versions
6373 of Tor. Reported by Guido Vranken.
6375 o Minor bugfixes (testing):
6376 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6377 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6378 - Use unbuffered I/O for utility functions around the
6379 process_handle_t type. This fixes unit test failures reported on
6380 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
6381 - Make display of captured unit test log messages consistent. Fixes
6382 bug 21510; bugfix on 0.2.9.3-alpha.
6383 - Make test-network.sh always call chutney's test-network.sh.
6384 Previously, this only worked on systems which had bash installed,
6385 due to some bash-specific code in the script. Fixes bug 19699;
6386 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
6387 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
6388 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
6389 - The unit tests now pass on systems where localhost is misconfigured
6390 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
6393 o Minor bugfixes (voting consistency):
6394 - Reject version numbers with non-numeric prefixes (such as +, -, or
6395 whitespace). Disallowing whitespace prevents differential version
6396 parsing between POSIX-based and Windows platforms. Fixes bug 21507
6397 and part of 21508; bugfix on 0.0.8pre1.
6399 o Minor bugfixes (Windows service):
6400 - When running as a Windows service, set the ID of the main thread
6401 correctly. Failure to do so made us fail to send log messages to
6402 the controller in 0.2.1.16-rc, slowed down controller event
6403 delivery in 0.2.7.3-rc and later, and crash with an assertion
6404 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
6405 Patch and diagnosis from "Vort".
6407 o Minor bugfixes (windows, relay):
6408 - Resolve "Failure from drain_fd: No error" warnings on Windows
6409 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
6411 o Code simplification and refactoring:
6412 - Break up the 630-line function connection_dir_client_reached_eof()
6413 into a dozen smaller functions. This change should help
6414 maintainability and readability of the client directory code.
6415 - Isolate our use of the openssl headers so that they are only
6416 included from our crypto wrapper modules, and from tests that
6417 examine those modules' internals. Closes ticket 21841.
6418 - Simplify our API to launch directory requests, making it more
6419 extensible and less error-prone. Now it's easier to add extra
6420 headers to directory requests. Closes ticket 21646.
6421 - Our base64 decoding functions no longer overestimate the output
6422 space that they need when parsing unpadded inputs. Closes
6424 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
6425 Resolves ticket 22213.
6426 - The logic that directory caches use to spool request to clients,
6427 serving them one part at a time so as not to allocate too much
6428 memory, has been refactored for consistency. Previously there was
6429 a separate spooling implementation per type of spoolable data. Now
6430 there is one common spooling implementation, with extensible data
6431 types. Closes ticket 21651.
6432 - Tor's compression module now supports multiple backends. Part of
6433 the implementation for proposal 278; closes ticket 21663.
6436 - Add a manpage description for the key-pinning-journal file. Closes
6438 - Correctly note that bandwidth accounting values are stored in the
6439 state file, and the bw_accounting file is now obsolete. Closes
6441 - Document more of the files in the Tor data directory, including
6442 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
6443 approved-routers, sr-random, and diff-cache. Found while fixing
6445 - Clarify the manpage for the (deprecated) torify script. Closes
6447 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
6448 Closes ticket 21873.
6449 - Correct documentation about the default DataDirectory value.
6450 Closes ticket 21151.
6451 - Document the default behavior of NumEntryGuards and
6452 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
6454 - Document key=value pluggable transport arguments for Bridge lines
6455 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
6456 - Note that bandwidth-limiting options don't affect TCP headers or
6457 DNS. Closes ticket 17170.
6459 o Removed features (configuration options, all in ticket 22060):
6460 - These configuration options are now marked Obsolete, and no longer
6461 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
6462 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
6463 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
6464 in 0.2.9.2-alpha and have now been removed. The previous default
6465 behavior is now always chosen; the previous (less secure) non-
6466 default behavior is now unavailable.
6467 - CloseHSClientCircuitsImmediatelyOnTimeout and
6468 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
6469 0.2.9.2-alpha and now have been removed. HS circuits never close
6470 on circuit build timeout; they have a longer timeout period.
6471 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
6472 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
6473 (and others) to configure listen-only and advertise-only addresses.
6475 o Removed features (tools):
6476 - We've removed the tor-checkkey tool from src/tools. Long ago, we
6477 used it to help people detect RSA keys that were generated by
6478 versions of Debian affected by CVE-2008-0166. But those keys have
6479 been out of circulation for ages, and this tool is no longer
6480 required. Closes ticket 21842.
6483 Changes in version 0.3.0.10 - 2017-08-02
6484 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
6485 from the current Tor alpha series. OpenBSD users and TPROXY users
6486 should upgrade; others are probably okay sticking with 0.3.0.9.
6488 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
6489 - Tor's repository now includes a Travis Continuous Integration (CI)
6490 configuration file (.travis.yml). This is meant to help new
6491 developers and contributors who fork Tor to a Github repository be
6492 better able to test their changes, and understand what we expect
6493 to pass. To use this new build feature, you must fork Tor to your
6494 Github account, then go into the "Integrations" menu in the
6495 repository settings for your fork and enable Travis, then push
6496 your changes. Closes ticket 22636.
6498 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
6499 - Fix a typo that had prevented TPROXY-based transparent proxying
6500 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
6501 Patch from "d4fq0fQAgoJ".
6503 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6504 - Avoid an assertion failure bug affecting our implementation of
6505 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6506 handling of "0xbar" differs from what we had expected. Fixes bug
6507 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6509 o Minor features (backport from 0.3.1.5-alpha):
6510 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
6513 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
6514 - Roll over monthly accounting at the configured hour and minute,
6515 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
6516 Found by Andrey Karpov with PVS-Studio.
6518 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
6519 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
6520 bugfix on 0.2.8.1-alpha.
6521 - Fix warnings when building with libscrypt and openssl scrypt
6522 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
6523 - When building with certain versions of the mingw C header files,
6524 avoid float-conversion warnings when calling the C functions
6525 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
6528 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
6529 - Backport a fix for an "unused variable" warning that appeared
6530 in some versions of mingw. Fixes bug 22838; bugfix on
6533 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
6534 - Avoid Coverity build warnings related to our BUG() macro. By
6535 default, Coverity treats BUG() as the Linux kernel does: an
6536 instant abort(). We need to override that so our BUG() macro
6537 doesn't prevent Coverity from analyzing functions that use it.
6538 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
6540 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
6541 - When rejecting a router descriptor for running an obsolete version
6542 of Tor without ntor support, warn about the obsolete tor version,
6543 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
6545 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
6546 - Avoid a sandbox failure when trying to re-bind to a socket and
6547 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
6549 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
6550 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
6551 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
6554 Changes in version 0.3.0.9 - 2017-06-29
6555 Tor 0.3.0.9 fixes a path selection bug that would allow a client
6556 to use a guard that was in the same network family as a chosen exit
6557 relay. This is a security regression; all clients running earlier
6558 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
6561 This release also backports several other bugfixes from the 0.3.1.x
6564 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
6565 - When choosing which guard to use for a circuit, avoid the exit's
6566 family along with the exit itself. Previously, the new guard
6567 selection logic avoided the exit, but did not consider its family.
6568 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
6569 006 and CVE-2017-0377.
6571 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
6572 - Don't block bootstrapping when a primary bridge is offline and we
6573 can't get its descriptor. Fixes bug 22325; fixes one case of bug
6574 21969; bugfix on 0.3.0.3-alpha.
6576 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
6577 - When starting with an old consensus, do not add new entry guards
6578 unless the consensus is "reasonably live" (under 1 day old). Fixes
6579 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
6581 o Minor features (geoip):
6582 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
6585 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
6586 - Reject version numbers with non-numeric prefixes (such as +, -, or
6587 whitespace). Disallowing whitespace prevents differential version
6588 parsing between POSIX-based and Windows platforms. Fixes bug 21507
6589 and part of 21508; bugfix on 0.0.8pre1.
6591 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
6592 - Permit the fchmod system call, to avoid crashing on startup when
6593 starting with the seccomp2 sandbox and an unexpected set of
6594 permissions on the data directory or its contents. Fixes bug
6595 22516; bugfix on 0.2.5.4-alpha.
6597 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
6598 - Fix a memset() off the end of an array when packing cells. This
6599 bug should be harmless in practice, since the corrupted bytes are
6600 still in the same structure, and are always padding bytes,
6601 ignored, or immediately overwritten, depending on compiler
6602 behavior. Nevertheless, because the memset()'s purpose is to make
6603 sure that any other cell-handling bugs can't expose bytes to the
6604 network, we need to fix it. Fixes bug 22737; bugfix on
6605 0.2.4.11-alpha. Fixes CID 1401591.
6608 Changes in version 0.3.0.8 - 2017-06-08
6609 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
6610 remotely crash a hidden service with an assertion failure. Anyone
6611 running a hidden service should upgrade to this version, or to some
6612 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
6614 Tor 0.3.0.8 also includes fixes for several key management bugs
6615 that sometimes made relays unreliable, as well as several other
6616 bugfixes described below.
6618 o Major bugfixes (hidden service, relay, security, backport
6619 from 0.3.1.3-alpha):
6620 - Fix a remotely triggerable assertion failure when a hidden service
6621 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
6622 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
6623 - Fix a remotely triggerable assertion failure caused by receiving a
6624 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6625 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6628 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
6629 - When performing the v3 link handshake on a TLS connection, report
6630 that we have the x509 certificate that we actually used on that
6631 connection, even if we have changed certificates since that
6632 connection was first opened. Previously, we would claim to have
6633 used our most recent x509 link certificate, which would sometimes
6634 make the link handshake fail. Fixes one case of bug 22460; bugfix
6637 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
6638 - Regenerate link and authentication certificates whenever the key
6639 that signs them changes; also, regenerate link certificates
6640 whenever the signed key changes. Previously, these processes were
6641 only weakly coupled, and we relays could (for minutes to hours)
6642 wind up with an inconsistent set of keys and certificates, which
6643 other relays would not accept. Fixes two cases of bug 22460;
6644 bugfix on 0.3.0.1-alpha.
6645 - When sending an Ed25519 signing->link certificate in a CERTS cell,
6646 send the certificate that matches the x509 certificate that we
6647 used on the TLS connection. Previously, there was a race condition
6648 if the TLS context rotated after we began the TLS handshake but
6649 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
6652 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
6653 - Stop rejecting v3 hidden service descriptors because their size
6654 did not match an old padding rule. Fixes bug 22447; bugfix on
6657 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
6658 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6659 December 2016 (of which ~126 were still functional) with a list of
6660 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6661 2017. Resolves ticket 21564.
6663 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
6664 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
6665 bug 22252; bugfix on 0.2.9.3-alpha.
6667 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
6668 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6669 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6671 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
6672 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
6673 months, and regenerate it when it is within one month of expiring.
6674 Previously, we had generated this certificate at startup with a
6675 ten-year lifetime, but that could lead to weird behavior when Tor
6676 was started with a grossly inaccurate clock. Mitigates bug 22466;
6677 mitigation on 0.3.0.1-alpha.
6679 o Minor bugfixes (memory leak, directory authority, backport from
6681 - When directory authorities reject a router descriptor due to
6682 keypinning, free the router descriptor rather than leaking the
6683 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
6686 Changes in version 0.2.9.11 - 2017-06-08
6687 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
6688 remotely crash a hidden service with an assertion failure. Anyone
6689 running a hidden service should upgrade to this version, or to some
6690 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6691 are not affected by TROVE-2017-004.)
6693 Tor 0.2.9.11 also backports fixes for several key management bugs
6694 that sometimes made relays unreliable, as well as several other
6695 bugfixes described below.
6697 o Major bugfixes (hidden service, relay, security, backport
6698 from 0.3.1.3-alpha):
6699 - Fix a remotely triggerable assertion failure caused by receiving a
6700 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6701 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6704 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
6705 - When performing the v3 link handshake on a TLS connection, report
6706 that we have the x509 certificate that we actually used on that
6707 connection, even if we have changed certificates since that
6708 connection was first opened. Previously, we would claim to have
6709 used our most recent x509 link certificate, which would sometimes
6710 make the link handshake fail. Fixes one case of bug 22460; bugfix
6713 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
6714 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6715 December 2016 (of which ~126 were still functional) with a list of
6716 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6717 2017. Resolves ticket 21564.
6719 o Minor features (future-proofing, backport from 0.3.0.7):
6720 - Tor no longer refuses to download microdescriptors or descriptors if
6721 they are listed as "published in the future". This change will
6722 eventually allow us to stop listing meaningful "published" dates
6723 in microdescriptor consensuses, and thereby allow us to reduce the
6724 resources required to download consensus diffs by over 50%.
6725 Implements part of ticket 21642; implements part of proposal 275.
6727 o Minor features (directory authorities, backport from 0.3.0.4-rc)
6728 - Directory authorities now reject relays running versions
6729 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
6730 suffer from bug 20499 and don't keep their consensus cache
6731 up-to-date. Resolves ticket 20509.
6733 o Minor features (geoip):
6734 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6737 o Minor bugfixes (control port, backport from 0.3.0.6):
6738 - The GETINFO extra-info/digest/<digest> command was broken because
6739 of a wrong base16 decode return value check, introduced when
6740 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
6742 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
6743 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6744 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6746 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
6747 - The getpid() system call is now permitted under the Linux seccomp2
6748 sandbox, to avoid crashing with versions of OpenSSL (and other
6749 libraries) that attempt to learn the process's PID by using the
6750 syscall rather than the VDSO code. Fixes bug 21943; bugfix
6753 o Minor bugfixes (memory leak, directory authority, backport
6754 from 0.3.1.2-alpha):
6755 - When directory authorities reject a router descriptor due to
6756 keypinning, free the router descriptor rather than leaking the
6757 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
6759 Changes in version 0.2.8.14 - 2017-06-08
6760 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
6761 remotely crash a hidden service with an assertion failure. Anyone
6762 running a hidden service should upgrade to this version, or to some
6763 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6764 are not affected by TROVE-2017-004.)
6766 o Major bugfixes (hidden service, relay, security):
6767 - Fix a remotely triggerable assertion failure caused by receiving a
6768 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6769 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6772 o Minor features (geoip):
6773 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6776 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
6777 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6778 December 2016 (of which ~126 were still functional) with a list of
6779 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6780 2017. Resolves ticket 21564.
6782 o Minor bugfixes (correctness):
6783 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6784 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6786 Changes in version 0.2.7.8 - 2017-06-08
6787 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
6788 remotely crash a hidden service with an assertion failure. Anyone
6789 running a hidden service should upgrade to this version, or to some
6790 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6791 are not affected by TROVE-2017-004.)
6793 o Major bugfixes (hidden service, relay, security):
6794 - Fix a remotely triggerable assertion failure caused by receiving a
6795 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6796 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6799 o Minor features (geoip):
6800 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6803 o Minor bugfixes (correctness):
6804 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6805 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6808 Changes in version 0.2.6.12 - 2017-06-08
6809 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
6810 remotely crash a hidden service with an assertion failure. Anyone
6811 running a hidden service should upgrade to this version, or to some
6812 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6813 are not affected by TROVE-2017-004.)
6815 o Major bugfixes (hidden service, relay, security):
6816 - Fix a remotely triggerable assertion failure caused by receiving a
6817 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6818 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6821 o Minor features (geoip):
6822 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6825 o Minor bugfixes (correctness):
6826 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6827 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6829 Changes in version 0.2.5.14 - 2017-06-08
6830 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
6831 remotely crash a hidden service with an assertion failure. Anyone
6832 running a hidden service should upgrade to this version, or to some
6833 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6834 are not affected by TROVE-2017-004.)
6836 o Major bugfixes (hidden service, relay, security):
6837 - Fix a remotely triggerable assertion failure caused by receiving a
6838 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6839 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6842 o Minor features (geoip):
6843 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6846 o Minor bugfixes (correctness):
6847 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6848 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6850 Changes in version 0.2.4.29 - 2017-06-08
6851 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
6852 remotely crash a hidden service with an assertion failure. Anyone
6853 running a hidden service should upgrade to this version, or to some
6854 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
6855 are not affected by TROVE-2017-004.)
6857 o Major bugfixes (hidden service, relay, security):
6858 - Fix a remotely triggerable assertion failure caused by receiving a
6859 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6860 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6863 o Minor features (geoip):
6864 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6867 o Minor bugfixes (correctness):
6868 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
6869 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
6872 Changes in version 0.3.0.7 - 2017-05-15
6873 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
6874 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
6875 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
6876 clients are not affected.
6878 o Major bugfixes (hidden service directory, security):
6879 - Fix an assertion failure in the hidden service directory code, which
6880 could be used by an attacker to remotely cause a Tor relay process to
6881 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
6882 should upgrade. This security issue is tracked as TROVE-2017-002.
6883 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
6886 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
6889 o Minor features (future-proofing):
6890 - Tor no longer refuses to download microdescriptors or descriptors
6891 if they are listed as "published in the future". This change will
6892 eventually allow us to stop listing meaningful "published" dates
6893 in microdescriptor consensuses, and thereby allow us to reduce the
6894 resources required to download consensus diffs by over 50%.
6895 Implements part of ticket 21642; implements part of proposal 275.
6897 o Minor bugfixes (Linux seccomp2 sandbox):
6898 - The getpid() system call is now permitted under the Linux seccomp2
6899 sandbox, to avoid crashing with versions of OpenSSL (and other
6900 libraries) that attempt to learn the process's PID by using the
6901 syscall rather than the VDSO code. Fixes bug 21943; bugfix
6905 Changes in version 0.3.0.6 - 2017-04-26
6906 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
6908 With the 0.3.0 series, clients and relays now use Ed25519 keys to
6909 authenticate their link connections to relays, rather than the old
6910 RSA1024 keys that they used before. (Circuit crypto has been
6911 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
6912 the guard selection and replacement algorithm to behave more robustly
6913 in the presence of unreliable networks, and to resist guard-
6916 This series also includes numerous other small features and bugfixes,
6917 along with more groundwork for the upcoming hidden-services revamp.
6919 Per our stable release policy, we plan to support the Tor 0.3.0
6920 release series for at least the next nine months, or for three months
6921 after the first stable release of the 0.3.1 series: whichever is
6922 longer. If you need a release with long-term support, we recommend
6923 that you stay with the 0.2.9 series.
6925 Below are the changes since 0.2.9.10. For a list of only the changes
6926 since 0.3.0.5-rc, see the ChangeLog file.
6928 o Major features (directory authority, security):
6929 - The default for AuthDirPinKeys is now 1: directory authorities
6930 will reject relays where the RSA identity key matches a previously
6931 seen value, but the Ed25519 key has changed. Closes ticket 18319.
6933 o Major features (guard selection algorithm):
6934 - Tor's guard selection algorithm has been redesigned from the
6935 ground up, to better support unreliable networks and restrictive
6936 sets of entry nodes, and to better resist guard-capture attacks by
6937 hostile local networks. Implements proposal 271; closes
6940 o Major features (next-generation hidden services):
6941 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
6942 prop224 aka "Next Generation Hidden Services". Service and clients
6943 don't use this functionality yet. Closes ticket 19043. Based on
6944 initial code by Alec Heifetz.
6945 - Relays now support the HSDir version 3 protocol, so that they can
6946 can store and serve v3 descriptors. This is part of the next-
6947 generation onion service work detailed in proposal 224. Closes
6950 o Major features (protocol, ed25519 identity keys):
6951 - Clients now support including Ed25519 identity keys in the EXTEND2
6952 cells they generate. By default, this is controlled by a consensus
6953 parameter, currently disabled. You can turn this feature on for
6954 testing by setting ExtendByEd25519ID in your configuration. This
6955 might make your traffic appear different than the traffic
6956 generated by other users, however. Implements part of ticket
6957 15056; part of proposal 220.
6958 - Relays now understand requests to extend to other relays by their
6959 Ed25519 identity keys. When an Ed25519 identity key is included in
6960 an EXTEND2 cell, the relay will only extend the circuit if the
6961 other relay can prove ownership of that identity. Implements part
6962 of ticket 15056; part of proposal 220.
6963 - Relays now use Ed25519 to prove their Ed25519 identities and to
6964 one another, and to clients. This algorithm is faster and more
6965 secure than the RSA-based handshake we've been doing until now.
6966 Implements the second big part of proposal 220; Closes
6969 o Major features (security):
6970 - Change the algorithm used to decide DNS TTLs on client and server
6971 side, to better resist DNS-based correlation attacks like the
6972 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
6973 Feamster. Now relays only return one of two possible DNS TTL
6974 values, and clients are willing to believe DNS TTL values up to 3
6975 hours long. Closes ticket 19769.
6977 o Major bugfixes (client, onion service, also in 0.2.9.9):
6978 - Fix a client-side onion service reachability bug, where multiple
6979 socks requests to an onion service (or a single slow request)
6980 could cause us to mistakenly mark some of the service's
6981 introduction points as failed, and we cache that failure so
6982 eventually we run out and can't reach the service. Also resolves a
6983 mysterious "Remote server sent bogus reason code 65021" log
6984 warning. The bug was introduced in ticket 17218, where we tried to
6985 remember the circuit end reason as a uint16_t, which mangled
6986 negative values. Partially fixes bug 21056 and fixes bug 20307;
6987 bugfix on 0.2.8.1-alpha.
6989 o Major bugfixes (crash, directory connections):
6990 - Fix a rare crash when sending a begin cell on a circuit whose
6991 linked directory connection had already been closed. Fixes bug
6992 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
6994 o Major bugfixes (directory authority):
6995 - During voting, when marking a relay as a probable sybil, do not
6996 clear its BadExit flag: sybils can still be bad in other ways
6997 too. (We still clear the other flags.) Fixes bug 21108; bugfix
7000 o Major bugfixes (DNS):
7001 - Fix a bug that prevented exit nodes from caching DNS records for
7002 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
7004 o Major bugfixes (IPv6 Exits):
7005 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
7006 any IPv6 addresses. Instead, only reject a port over IPv6 if the
7007 exit policy rejects that port on more than an IPv6 /16 of
7008 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
7009 which rejected a relay's own IPv6 address by default. Fixes bug
7010 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
7012 o Major bugfixes (parsing):
7013 - Fix an integer underflow bug when comparing malformed Tor
7014 versions. This bug could crash Tor when built with
7015 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7016 0.2.9.8, which were built with -ftrapv by default. In other cases
7017 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7018 on 0.0.8pre1. Found by OSS-Fuzz.
7019 - When parsing a malformed content-length field from an HTTP
7020 message, do not read off the end of the buffer. This bug was a
7021 potential remote denial-of-service attack against Tor clients and
7022 relays. A workaround was released in October 2016, to prevent this
7023 bug from crashing Tor. This is a fix for the underlying issue,
7024 which should no longer matter (if you applied the earlier patch).
7025 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
7026 using AFL (http://lcamtuf.coredump.cx/afl/).
7028 o Major bugfixes (scheduler):
7029 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
7030 caused the channel scheduler to behave more or less randomly,
7031 rather than preferring channels with higher-priority circuits.
7032 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
7034 o Major bugfixes (security, also in 0.2.9.9):
7035 - Downgrade the "-ftrapv" option from "always on" to "only on when
7036 --enable-expensive-hardening is provided." This hardening option,
7037 like others, can turn survivable bugs into crashes--and having it
7038 on by default made a (relatively harmless) integer overflow bug
7039 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
7040 bugfix on 0.2.9.1-alpha.
7042 o Minor feature (client):
7043 - Enable IPv6 traffic on the SocksPort by default. To disable this,
7044 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
7046 o Minor feature (fallback scripts):
7047 - Add a check_existing mode to updateFallbackDirs.py, which checks
7048 if fallbacks in the hard-coded list are working. Closes ticket
7049 20174. Patch by haxxpop.
7051 o Minor feature (protocol versioning):
7052 - Add new protocol version for proposal 224. HSIntro now advertises
7053 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
7055 o Minor features (ciphersuite selection):
7056 - Allow relays to accept a wider range of ciphersuites, including
7057 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
7058 - Clients now advertise a list of ciphersuites closer to the ones
7059 preferred by Firefox. Closes part of ticket 15426.
7061 o Minor features (controller):
7062 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
7063 shared-random values to the controller. Closes ticket 19925.
7064 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
7065 rather than "unrecognized." Closes ticket 20389; patch from
7068 o Minor features (controller, configuration):
7069 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
7070 and so on, now comes with a __*Port variant that will not be saved
7071 to the torrc file by the controller's SAVECONF command. This
7072 change allows TorBrowser to set up a single-use domain socket for
7073 each time it launches Tor. Closes ticket 20956.
7074 - The GETCONF command can now query options that may only be
7075 meaningful in context-sensitive lists. This allows the controller
7076 to query the mixed SocksPort/__SocksPort style options introduced
7077 in feature 20956. Implements ticket 21300.
7079 o Minor features (diagnostic, directory client):
7080 - Warn when we find an unexpected inconsistency in directory
7081 download status objects. Prevents some negative consequences of
7084 o Minor features (directory authorities):
7085 - Directory authorities now reject descriptors that claim to be
7086 malformed versions of Tor. Helps prevent exploitation of
7088 - Reject version numbers with components that exceed INT32_MAX.
7089 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
7090 Fixes bug 21450; bugfix on 0.0.8pre1.
7092 o Minor features (directory authority):
7093 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
7094 default) to control whether authorities should try to probe relays
7095 by their Ed25519 link keys. This option will go away in a few
7096 releases--unless we encounter major trouble in our ed25519 link
7097 protocol rollout, in which case it will serve as a safety option.
7099 o Minor features (directory cache):
7100 - Relays and bridges will now refuse to serve the consensus they
7101 have if they know it is too old for a client to use. Closes
7104 o Minor features (ed25519 link handshake):
7105 - Advertise support for the ed25519 link handshake using the
7106 subprotocol-versions mechanism, so that clients can tell which
7107 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
7109 o Minor features (entry guards):
7110 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
7111 break regression tests.
7112 - Require UseEntryGuards when UseBridges is set, in order to make
7113 sure bridges aren't bypassed. Resolves ticket 20502.
7115 o Minor features (fallback directories):
7116 - Allow 3 fallback relays per operator, which is safe now that we
7117 are choosing 200 fallback relays. Closes ticket 20912.
7118 - Annotate updateFallbackDirs.py with the bandwidth and consensus
7119 weight for each candidate fallback. Closes ticket 20878.
7120 - Display the relay fingerprint when downloading consensuses from
7121 fallbacks. Closes ticket 20908.
7122 - Exclude relays affected by bug 20499 from the fallback list.
7123 Exclude relays from the fallback list if they are running versions
7124 known to be affected by bug 20499, or if in our tests they deliver
7125 a stale consensus (i.e. one that expired more than 24 hours ago).
7126 Closes ticket 20539.
7127 - Make it easier to change the output sort order of fallbacks.
7128 Closes ticket 20822.
7129 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
7131 - Require fallback directories to have the same address and port for
7132 7 days (now that we have enough relays with this stability).
7133 Relays whose OnionOO stability timer is reset on restart by bug
7134 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
7135 this issue. Closes ticket 20880; maintains short-term fix
7137 - Require fallbacks to have flags for 90% of the time (weighted
7138 decaying average), rather than 95%. This allows at least 73% of
7139 clients to bootstrap in the first 5 seconds without contacting an
7140 authority. Part of ticket 18828.
7141 - Select 200 fallback directories for each release. Closes
7144 o Minor features (fingerprinting resistance, authentication):
7145 - Extend the length of RSA keys used for TLS link authentication to
7146 2048 bits. (These weren't used for forward secrecy; for forward
7147 secrecy, we used P256.) Closes ticket 13752.
7149 o Minor features (geoip):
7150 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
7153 o Minor features (geoip, also in 0.2.9.9):
7154 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
7157 o Minor features (infrastructure):
7158 - Implement smartlist_add_strdup() function. Replaces the use of
7159 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
7161 o Minor features (linting):
7162 - Enhance the changes file linter to warn on Tor versions that are
7163 prefixed with "tor-". Closes ticket 21096.
7165 o Minor features (logging):
7166 - In several places, describe unset ed25519 keys as "<unset>",
7167 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
7169 o Minor features (portability, compilation):
7170 - Autoconf now checks to determine if OpenSSL structures are opaque,
7171 instead of explicitly checking for OpenSSL version numbers. Part
7173 - Support building with recent LibreSSL code that uses opaque
7174 structures. Closes ticket 21359.
7176 o Minor features (relay):
7177 - We now allow separation of exit and relay traffic to different
7178 source IP addresses, using the OutboundBindAddressExit and
7179 OutboundBindAddressOR options respectively. Closes ticket 17975.
7180 Written by Michael Sonntag.
7182 o Minor features (reliability, crash):
7183 - Try better to detect problems in buffers where they might grow (or
7184 think they have grown) over 2 GB in size. Diagnostic for
7187 o Minor features (testing):
7188 - During 'make test-network-all', if tor logs any warnings, ask
7189 chutney to output them. Requires a recent version of chutney with
7190 the 21572 patch. Implements 21570.
7192 o Minor bugfix (control protocol):
7193 - The reply to a "GETINFO config/names" request via the control
7194 protocol now spells the type "Dependent" correctly. This is a
7195 breaking change in the control protocol. (The field seems to be
7196 ignored by the most common known controllers.) Fixes bug 18146;
7197 bugfix on 0.1.1.4-alpha.
7198 - The GETINFO extra-info/digest/<digest> command was broken because
7199 of a wrong base16 decode return value check, introduced when
7200 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
7202 o Minor bugfix (logging):
7203 - Don't recommend the use of Tor2web in non-anonymous mode.
7204 Recommending Tor2web is a bad idea because the client loses all
7205 anonymity. Tor2web should only be used in specific cases by users
7206 who *know* and understand the issues. Fixes bug 21294; bugfix
7209 o Minor bugfixes (bug resilience):
7210 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
7211 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
7212 Hans Jerry Illikainen.
7214 o Minor bugfixes (build):
7215 - Replace obsolete Autoconf macros with their modern equivalent and
7216 prevent similar issues in the future. Fixes bug 20990; bugfix
7219 o Minor bugfixes (certificate expiration time):
7220 - Avoid using link certificates that don't become valid till some
7221 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
7223 o Minor bugfixes (client):
7224 - Always recover from failures in extend_info_from_node(), in an
7225 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
7226 bugfix on 0.2.3.1-alpha.
7227 - When clients that use bridges start up with a cached consensus on
7228 disk, they were ignoring it and downloading a new one. Now they
7229 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
7231 o Minor bugfixes (code correctness):
7232 - Repair a couple of (unreachable or harmless) cases of the risky
7233 comparison-by-subtraction pattern that caused bug 21278.
7235 o Minor bugfixes (config):
7236 - Don't assert on startup when trying to get the options list and
7237 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
7238 options so of course they aren't ready yet. Fixes bug 21062;
7239 bugfix on 0.2.9.3-alpha.
7241 o Minor bugfixes (configuration):
7242 - Accept non-space whitespace characters after the severity level in
7243 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
7244 - Support "TByte" and "TBytes" units in options given in bytes.
7245 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
7246 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
7248 o Minor bugfixes (configure, autoconf):
7249 - Rename the configure option --enable-expensive-hardening to
7250 --enable-fragile-hardening. Expensive hardening makes the tor
7251 daemon abort when some kinds of issues are detected. Thus, it
7252 makes tor more at risk of remote crashes but safer against RCE or
7253 heartbleed bug category. We now try to explain this issue in a
7254 message from the configure script. Fixes bug 21290; bugfix
7257 o Minor bugfixes (consensus weight):
7258 - Add new consensus method that initializes bw weights to 1 instead
7259 of 0. This prevents a zero weight from making it all the way to
7260 the end (happens in small testing networks) and causing an error.
7261 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
7263 o Minor bugfixes (crash prevention):
7264 - Fix an (currently untriggerable, but potentially dangerous) crash
7265 bug when base32-encoding inputs whose sizes are not a multiple of
7266 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
7268 o Minor bugfixes (dead code):
7269 - Remove a redundant check for PidFile changes at runtime in
7270 options_transition_allowed(): this check is already performed
7271 regardless of whether the sandbox is active. Fixes bug 21123;
7272 bugfix on 0.2.5.4-alpha.
7274 o Minor bugfixes (descriptors):
7275 - Correctly recognise downloaded full descriptors as valid, even
7276 when using microdescriptors as circuits. This affects clients with
7277 FetchUselessDescriptors set, and may affect directory authorities.
7278 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
7280 o Minor bugfixes (directory mirrors):
7281 - Allow relays to use directory mirrors without a DirPort: these
7282 relays need to be contacted over their ORPorts using a begindir
7283 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
7284 - Clarify the message logged when a remote relay is unexpectedly
7285 missing an ORPort or DirPort: users were confusing this with a
7286 local port. Fixes another case of bug 20711; bugfix
7289 o Minor bugfixes (directory system):
7290 - Bridges and relays now use microdescriptors (like clients do)
7291 rather than old-style router descriptors. Now bridges will blend
7292 in with clients in terms of the circuits they build. Fixes bug
7293 6769; bugfix on 0.2.3.2-alpha.
7294 - Download all consensus flavors, descriptors, and authority
7295 certificates when FetchUselessDescriptors is set, regardless of
7296 whether tor is a directory cache or not. Fixes bug 20667; bugfix
7297 on all recent tor versions.
7299 o Minor bugfixes (documentation):
7300 - Update the tor manual page to document every option that can not
7301 be changed while tor is running. Fixes bug 21122.
7303 o Minor bugfixes (ed25519 certificates):
7304 - Correctly interpret ed25519 certificates that would expire some
7305 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
7307 o Minor bugfixes (fallback directories):
7308 - Avoid checking fallback candidates' DirPorts if they are down in
7309 OnionOO. When a relay operator has multiple relays, this
7310 prioritizes relays that are up over relays that are down. Fixes
7311 bug 20926; bugfix on 0.2.8.3-alpha.
7312 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
7313 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
7314 - Stop failing when a relay has no uptime data in
7315 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
7317 o Minor bugfixes (hidden service):
7318 - Clean up the code for expiring intro points with no associated
7319 circuits. It was causing, rarely, a service with some expiring
7320 introduction points to not open enough additional introduction
7321 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
7322 - Resolve two possible underflows which could lead to creating and
7323 closing a lot of introduction point circuits in a non-stop loop.
7324 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
7325 - Stop setting the torrc option HiddenServiceStatistics to "0" just
7326 because we're not a bridge or relay. Instead, we preserve whatever
7327 value the user set (or didn't set). Fixes bug 21150; bugfix
7330 o Minor bugfixes (hidden services):
7331 - Make hidden services check for failed intro point connections,
7332 even when they have exceeded their intro point creation limit.
7333 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
7334 - Make hidden services with 8 to 10 introduction points check for
7335 failed circuits immediately after startup. Previously, they would
7336 wait for 5 minutes before performing their first checks. Fixes bug
7337 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
7338 - Stop ignoring misconfigured hidden services. Instead, refuse to
7339 start tor until the misconfigurations have been corrected. Fixes
7340 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
7343 o Minor bugfixes (IPv6):
7344 - Make IPv6-using clients try harder to find an IPv6 directory
7345 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
7346 - When IPv6 addresses have not been downloaded yet (microdesc
7347 consensus documents don't list relay IPv6 addresses), use hard-
7348 coded addresses for authorities, fallbacks, and configured
7349 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
7350 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
7352 o Minor bugfixes (memory leak at exit):
7353 - Fix a small harmless memory leak at exit of the previously unused
7354 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
7357 o Minor bugfixes (onion services):
7358 - Allow the number of introduction points to be as low as 0, rather
7359 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
7361 o Minor bugfixes (portability):
7362 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
7363 It is supported by OpenBSD itself, and also by most OpenBSD
7364 variants (such as Bitrig). Fixes bug 20980; bugfix
7367 o Minor bugfixes (portability, also in 0.2.9.9):
7368 - Avoid crashing when Tor is built using headers that contain
7369 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
7370 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
7372 - Fix Libevent detection on platforms without Libevent 1 headers
7373 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
7375 o Minor bugfixes (relay):
7376 - Avoid a double-marked-circuit warning that could happen when we
7377 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
7379 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
7380 initializing the keys would reset the DataDirectory to 0700
7381 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
7382 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
7384 o Minor bugfixes (testing):
7385 - Fix Raspbian build issues related to missing socket errno in
7386 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
7387 - Remove undefined behavior from the backtrace generator by removing
7388 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
7389 - Use bash in src/test/test-network.sh. This ensures we reliably
7390 call chutney's newer tools/test-network.sh when available. Fixes
7391 bug 21562; bugfix on 0.2.9.1-alpha.
7393 o Minor bugfixes (tor-resolve):
7394 - The tor-resolve command line tool now rejects hostnames over 255
7395 characters in length. Previously, it would silently truncate them,
7396 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
7397 Patch by "junglefowl".
7399 o Minor bugfixes (unit tests):
7400 - Allow the unit tests to pass even when DNS lookups of bogus
7401 addresses do not fail as expected. Fixes bug 20862 and 20863;
7402 bugfix on unit tests introduced in 0.2.8.1-alpha
7403 through 0.2.9.4-alpha.
7405 o Minor bugfixes (util):
7406 - When finishing writing a file to disk, if we were about to replace
7407 the file with the temporary file created before and we fail to
7408 replace it, remove the temporary file so it doesn't stay on disk.
7409 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
7411 o Minor bugfixes (Windows services):
7412 - Be sure to initialize the monotonic time subsystem before using
7413 it, even when running as an NT service. Fixes bug 21356; bugfix
7416 o Minor bugfixes (Windows):
7417 - Check for getpagesize before using it to mmap files. This fixes
7418 compilation in some MinGW environments. Fixes bug 20530; bugfix on
7419 0.1.2.1-alpha. Reported by "ice".
7421 o Code simplification and refactoring:
7422 - Abolish all global guard context in entrynodes.c; replace with new
7423 guard_selection_t structure as preparation for proposal 271.
7424 Closes ticket 19858.
7425 - Extract magic numbers in circuituse.c into defined variables.
7426 - Introduce rend_service_is_ephemeral() that tells if given onion
7427 service is ephemeral. Replace unclear NULL-checkings for service
7428 directory with this function. Closes ticket 20526.
7429 - Refactor circuit_is_available_for_use to remove unnecessary check.
7430 - Refactor circuit_predict_and_launch_new for readability and
7431 testability. Closes ticket 18873.
7432 - Refactor code to manipulate global_origin_circuit_list into
7433 separate functions. Closes ticket 20921.
7434 - Refactor large if statement in purpose_needs_anonymity to use
7435 switch statement instead. Closes part of ticket 20077.
7436 - Refactor the hashing API to return negative values for errors, as
7437 is done as throughout the codebase. Closes ticket 20717.
7438 - Remove data structures that were used to index or_connection
7439 objects by their RSA identity digests. These structures are fully
7440 redundant with the similar structures used in the
7441 channel abstraction.
7442 - Remove duplicate code in the channel_write_*cell() functions.
7443 Closes ticket 13827; patch from Pingl.
7444 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
7445 use only purpose_needs_anonymity. Closes part of ticket 20077.
7446 - The code to generate and parse EXTEND and EXTEND2 cells has been
7447 replaced with code automatically generated by the
7450 o Documentation (formatting):
7451 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
7452 blocks were incorrectly appearing. Closes ticket 20885.
7454 o Documentation (man page):
7455 - Clarify many options in tor.1 and add some min/max values for
7456 HiddenService options. Closes ticket 21058.
7459 - Change '1' to 'weight_scale' in consensus bw weights calculation
7460 comments, as that is reality. Closes ticket 20273. Patch
7462 - Clarify that when ClientRejectInternalAddresses is enabled (which
7463 is the default), multicast DNS hostnames for machines on the local
7464 network (of the form *.local) are also rejected. Closes
7466 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
7467 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
7468 - Include the "TBits" unit in Tor's man page. Fixes part of bug
7469 20622; bugfix on 0.2.5.1-alpha.
7470 - Small fixes to the fuzzing documentation. Closes ticket 21472.
7471 - Stop the man page from incorrectly stating that HiddenServiceDir
7472 must already exist. Fixes 20486.
7473 - Update the description of the directory server options in the
7474 manual page, to clarify that a relay no longer needs to set
7475 DirPort in order to be a directory cache. Closes ticket 21720.
7478 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
7479 limit for relays running on a single IP applies to authority IP
7480 addresses as well as to non-authority IP addresses. Closes
7482 - The UseDirectoryGuards torrc option no longer exists: all users
7483 that use entry guards will also use directory guards. Related to
7484 proposal 271; implements part of ticket 20831.
7487 - Add tests for networkstatus_compute_bw_weights_v10.
7488 - Add unit tests circuit_predict_and_launch_new.
7489 - Extract dummy_origin_circuit_new so it can be used by other
7491 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
7492 from "overcaffeinated".
7493 - Perform the coding style checks when running the tests and fail
7494 when coding style violations are found. Closes ticket 5500.
7497 Changes in version 0.2.8.13 - 2017-03-03
7498 Tor 0.2.8.13 backports a security fix from later Tor
7499 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
7500 this release, if for some reason they cannot upgrade to a later
7501 release series, and if they build Tor with the --enable-expensive-hardening
7504 Note that support for Tor 0.2.8.x is ending next year: we will not issue
7505 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
7506 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
7508 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7509 - Fix an integer underflow bug when comparing malformed Tor
7510 versions. This bug could crash Tor when built with
7511 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7512 0.2.9.8, which were built with -ftrapv by default. In other cases
7513 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7514 on 0.0.8pre1. Found by OSS-Fuzz.
7516 o Minor features (geoip):
7517 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7521 Changes in version 0.2.7.7 - 2017-03-03
7522 Tor 0.2.7.7 backports a number of security fixes from later Tor
7523 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
7524 this release, if for some reason they cannot upgrade to a later
7527 Note that support for Tor 0.2.7.x is ending this year: we will not issue
7528 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
7529 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
7531 o Directory authority changes (backport from 0.2.8.5-rc):
7532 - Urras is no longer a directory authority. Closes ticket 19271.
7534 o Directory authority changes (backport from 0.2.9.2-alpha):
7535 - The "Tonga" bridge authority has been retired; the new bridge
7536 authority is "Bifroest". Closes tickets 19728 and 19690.
7538 o Directory authority key updates (backport from 0.2.8.1-alpha):
7539 - Update the V3 identity key for the dannenberg directory authority:
7540 it was changed on 18 November 2015. Closes task 17906. Patch
7543 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7544 - Fix a bug in parsing that could cause clients to read a single
7545 byte past the end of an allocated region. This bug could be used
7546 to cause hardened clients (built with --enable-expensive-hardening)
7547 to crash if they tried to visit a hostile hidden service. Non-
7548 hardened clients are only affected depending on the details of
7549 their platform's memory allocator. Fixes bug 21018; bugfix on
7550 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7551 2016-12-002 and as CVE-2016-1254.
7553 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
7554 - Stop a crash that could occur when a client running with DNSPort
7555 received a query with multiple address types, and the first
7556 address type was not supported. Found and fixed by Scott Dial.
7557 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
7558 - Prevent a class of security bugs caused by treating the contents
7559 of a buffer chunk as if they were a NUL-terminated string. At
7560 least one such bug seems to be present in all currently used
7561 versions of Tor, and would allow an attacker to remotely crash
7562 most Tor instances, especially those compiled with extra compiler
7563 hardening. With this defense in place, such bugs can't crash Tor,
7564 though we should still fix them as they occur. Closes ticket
7565 20384 (TROVE-2016-10-001).
7567 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7568 - Avoid a difficult-to-trigger heap corruption attack when extending
7569 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7570 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7571 Reported by Guido Vranken.
7573 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7574 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7575 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7577 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7578 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7579 pointer to the previous (uninitialized) key value. The impact here
7580 should be limited to a difficult-to-trigger crash, if OpenSSL is
7581 running an engine that makes key generation failures possible, or
7582 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7583 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7586 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7587 - Fix an integer underflow bug when comparing malformed Tor
7588 versions. This bug could crash Tor when built with
7589 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7590 0.2.9.8, which were built with -ftrapv by default. In other cases
7591 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7592 on 0.0.8pre1. Found by OSS-Fuzz.
7594 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7595 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7596 zero size. Check size argument to memwipe() for underflow. Fixes
7597 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7600 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7601 - Make Tor survive errors involving connections without a
7602 corresponding event object. Previously we'd fail with an
7603 assertion; now we produce a log message. Related to bug 16248.
7605 o Minor features (geoip):
7606 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7610 Changes in version 0.2.6.11 - 2017-03-03
7611 Tor 0.2.6.11 backports a number of security fixes from later Tor
7612 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
7613 this release, if for some reason they cannot upgrade to a later
7616 Note that support for Tor 0.2.6.x is ending this year: we will not issue
7617 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
7618 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
7620 o Directory authority changes (backport from 0.2.8.5-rc):
7621 - Urras is no longer a directory authority. Closes ticket 19271.
7623 o Directory authority changes (backport from 0.2.9.2-alpha):
7624 - The "Tonga" bridge authority has been retired; the new bridge
7625 authority is "Bifroest". Closes tickets 19728 and 19690.
7627 o Directory authority key updates (backport from 0.2.8.1-alpha):
7628 - Update the V3 identity key for the dannenberg directory authority:
7629 it was changed on 18 November 2015. Closes task 17906. Patch
7632 o Major features (security fixes, backport from 0.2.9.4-alpha):
7633 - Prevent a class of security bugs caused by treating the contents
7634 of a buffer chunk as if they were a NUL-terminated string. At
7635 least one such bug seems to be present in all currently used
7636 versions of Tor, and would allow an attacker to remotely crash
7637 most Tor instances, especially those compiled with extra compiler
7638 hardening. With this defense in place, such bugs can't crash Tor,
7639 though we should still fix them as they occur. Closes ticket
7640 20384 (TROVE-2016-10-001).
7642 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7643 - Fix a bug in parsing that could cause clients to read a single
7644 byte past the end of an allocated region. This bug could be used
7645 to cause hardened clients (built with --enable-expensive-hardening)
7646 to crash if they tried to visit a hostile hidden service. Non-
7647 hardened clients are only affected depending on the details of
7648 their platform's memory allocator. Fixes bug 21018; bugfix on
7649 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7650 2016-12-002 and as CVE-2016-1254.
7652 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
7653 - Stop a crash that could occur when a client running with DNSPort
7654 received a query with multiple address types, and the first
7655 address type was not supported. Found and fixed by Scott Dial.
7656 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
7658 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
7659 - Fix an error that could cause us to read 4 bytes before the
7660 beginning of an openssl string. This bug could be used to cause
7661 Tor to crash on systems with unusual malloc implementations, or
7662 systems with unusual hardening installed. Fixes bug 17404; bugfix
7665 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7666 - Avoid a difficult-to-trigger heap corruption attack when extending
7667 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7668 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7669 Reported by Guido Vranken.
7671 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7672 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7673 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7675 o Major bugfixes (guard selection, backport from 0.2.7.6):
7676 - Actually look at the Guard flag when selecting a new directory
7677 guard. When we implemented the directory guard design, we
7678 accidentally started treating all relays as if they have the Guard
7679 flag during guard selection, leading to weaker anonymity and worse
7680 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
7683 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7684 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7685 pointer to the previous (uninitialized) key value. The impact here
7686 should be limited to a difficult-to-trigger crash, if OpenSSL is
7687 running an engine that makes key generation failures possible, or
7688 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7689 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7692 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7693 - Fix an integer underflow bug when comparing malformed Tor
7694 versions. This bug could crash Tor when built with
7695 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7696 0.2.9.8, which were built with -ftrapv by default. In other cases
7697 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7698 on 0.0.8pre1. Found by OSS-Fuzz.
7700 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7701 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7702 zero size. Check size argument to memwipe() for underflow. Fixes
7703 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7706 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7707 - Make Tor survive errors involving connections without a
7708 corresponding event object. Previously we'd fail with an
7709 assertion; now we produce a log message. Related to bug 16248.
7711 o Minor features (geoip):
7712 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7715 o Minor bugfixes (compilation, backport from 0.2.7.6):
7716 - Fix a compilation warning with Clang 3.6: Do not check the
7717 presence of an address which can never be NULL. Fixes bug 17781.
7720 Changes in version 0.2.5.13 - 2017-03-03
7721 Tor 0.2.5.13 backports a number of security fixes from later Tor
7722 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
7723 this release, if for some reason they cannot upgrade to a later
7726 Note that support for Tor 0.2.5.x is ending next year: we will not issue
7727 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
7728 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
7730 o Directory authority changes (backport from 0.2.8.5-rc):
7731 - Urras is no longer a directory authority. Closes ticket 19271.
7733 o Directory authority changes (backport from 0.2.9.2-alpha):
7734 - The "Tonga" bridge authority has been retired; the new bridge
7735 authority is "Bifroest". Closes tickets 19728 and 19690.
7737 o Directory authority key updates (backport from 0.2.8.1-alpha):
7738 - Update the V3 identity key for the dannenberg directory authority:
7739 it was changed on 18 November 2015. Closes task 17906. Patch
7742 o Major features (security fixes, backport from 0.2.9.4-alpha):
7743 - Prevent a class of security bugs caused by treating the contents
7744 of a buffer chunk as if they were a NUL-terminated string. At
7745 least one such bug seems to be present in all currently used
7746 versions of Tor, and would allow an attacker to remotely crash
7747 most Tor instances, especially those compiled with extra compiler
7748 hardening. With this defense in place, such bugs can't crash Tor,
7749 though we should still fix them as they occur. Closes ticket
7750 20384 (TROVE-2016-10-001).
7752 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7753 - Fix a bug in parsing that could cause clients to read a single
7754 byte past the end of an allocated region. This bug could be used
7755 to cause hardened clients (built with --enable-expensive-hardening)
7756 to crash if they tried to visit a hostile hidden service. Non-
7757 hardened clients are only affected depending on the details of
7758 their platform's memory allocator. Fixes bug 21018; bugfix on
7759 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7760 2016-12-002 and as CVE-2016-1254.
7762 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
7763 - Stop a crash that could occur when a client running with DNSPort
7764 received a query with multiple address types, and the first
7765 address type was not supported. Found and fixed by Scott Dial.
7766 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
7768 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
7769 - Fix an error that could cause us to read 4 bytes before the
7770 beginning of an openssl string. This bug could be used to cause
7771 Tor to crash on systems with unusual malloc implementations, or
7772 systems with unusual hardening installed. Fixes bug 17404; bugfix
7775 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7776 - Avoid a difficult-to-trigger heap corruption attack when extending
7777 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7778 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7779 Reported by Guido Vranken.
7781 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7782 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7783 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7785 o Major bugfixes (guard selection, backport from 0.2.7.6):
7786 - Actually look at the Guard flag when selecting a new directory
7787 guard. When we implemented the directory guard design, we
7788 accidentally started treating all relays as if they have the Guard
7789 flag during guard selection, leading to weaker anonymity and worse
7790 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
7793 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7794 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7795 pointer to the previous (uninitialized) key value. The impact here
7796 should be limited to a difficult-to-trigger crash, if OpenSSL is
7797 running an engine that makes key generation failures possible, or
7798 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7799 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7802 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7803 - Fix an integer underflow bug when comparing malformed Tor
7804 versions. This bug could crash Tor when built with
7805 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7806 0.2.9.8, which were built with -ftrapv by default. In other cases
7807 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7808 on 0.0.8pre1. Found by OSS-Fuzz.
7810 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7811 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7812 zero size. Check size argument to memwipe() for underflow. Fixes
7813 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7816 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7817 - Make Tor survive errors involving connections without a
7818 corresponding event object. Previously we'd fail with an
7819 assertion; now we produce a log message. Related to bug 16248.
7821 o Minor features (geoip):
7822 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7825 o Minor bugfixes (compilation, backport from 0.2.7.6):
7826 - Fix a compilation warning with Clang 3.6: Do not check the
7827 presence of an address which can never be NULL. Fixes bug 17781.
7829 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
7830 - Check for failures from crypto_early_init, and refuse to continue.
7831 A previous typo meant that we could keep going with an
7832 uninitialized crypto library, and would have OpenSSL initialize
7833 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
7834 when implementing ticket 4900. Patch by "teor".
7836 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
7837 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7838 a client authorized hidden service. Fixes bug 15823; bugfix
7842 Changes in version 0.2.4.28 - 2017-03-03
7843 Tor 0.2.4.28 backports a number of security fixes from later Tor
7844 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
7845 this release, if for some reason they cannot upgrade to a later
7848 Note that support for Tor 0.2.4.x is ending soon: we will not issue
7849 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
7850 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
7852 o Directory authority changes (backport from 0.2.8.5-rc):
7853 - Urras is no longer a directory authority. Closes ticket 19271.
7855 o Directory authority changes (backport from 0.2.9.2-alpha):
7856 - The "Tonga" bridge authority has been retired; the new bridge
7857 authority is "Bifroest". Closes tickets 19728 and 19690.
7859 o Directory authority key updates (backport from 0.2.8.1-alpha):
7860 - Update the V3 identity key for the dannenberg directory authority:
7861 it was changed on 18 November 2015. Closes task 17906. Patch
7864 o Major features (security fixes, backport from 0.2.9.4-alpha):
7865 - Prevent a class of security bugs caused by treating the contents
7866 of a buffer chunk as if they were a NUL-terminated string. At
7867 least one such bug seems to be present in all currently used
7868 versions of Tor, and would allow an attacker to remotely crash
7869 most Tor instances, especially those compiled with extra compiler
7870 hardening. With this defense in place, such bugs can't crash Tor,
7871 though we should still fix them as they occur. Closes ticket
7872 20384 (TROVE-2016-10-001).
7874 o Major bugfixes (parsing, security, backport from 0.2.9.8):
7875 - Fix a bug in parsing that could cause clients to read a single
7876 byte past the end of an allocated region. This bug could be used
7877 to cause hardened clients (built with --enable-expensive-hardening)
7878 to crash if they tried to visit a hostile hidden service. Non-
7879 hardened clients are only affected depending on the details of
7880 their platform's memory allocator. Fixes bug 21018; bugfix on
7881 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
7882 2016-12-002 and as CVE-2016-1254.
7884 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
7885 - Fix an error that could cause us to read 4 bytes before the
7886 beginning of an openssl string. This bug could be used to cause
7887 Tor to crash on systems with unusual malloc implementations, or
7888 systems with unusual hardening installed. Fixes bug 17404; bugfix
7891 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
7892 - Avoid a difficult-to-trigger heap corruption attack when extending
7893 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
7894 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
7895 Reported by Guido Vranken.
7897 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
7898 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
7899 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
7901 o Major bugfixes (guard selection, backport from 0.2.7.6):
7902 - Actually look at the Guard flag when selecting a new directory
7903 guard. When we implemented the directory guard design, we
7904 accidentally started treating all relays as if they have the Guard
7905 flag during guard selection, leading to weaker anonymity and worse
7906 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
7909 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
7910 - If OpenSSL fails to generate an RSA key, do not retain a dangling
7911 pointer to the previous (uninitialized) key value. The impact here
7912 should be limited to a difficult-to-trigger crash, if OpenSSL is
7913 running an engine that makes key generation failures possible, or
7914 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
7915 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
7918 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
7919 - Fix an integer underflow bug when comparing malformed Tor
7920 versions. This bug could crash Tor when built with
7921 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7922 0.2.9.8, which were built with -ftrapv by default. In other cases
7923 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7924 on 0.0.8pre1. Found by OSS-Fuzz.
7926 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
7927 - Make memwipe() do nothing when passed a NULL pointer or buffer of
7928 zero size. Check size argument to memwipe() for underflow. Fixes
7929 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
7932 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
7933 - Make Tor survive errors involving connections without a
7934 corresponding event object. Previously we'd fail with an
7935 assertion; now we produce a log message. Related to bug 16248.
7937 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
7938 - Make it harder for attackers to overload hidden services with
7939 introductions, by blocking multiple introduction requests on the
7940 same circuit. Resolves ticket 15515.
7942 o Minor features (geoip):
7943 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7946 o Minor bugfixes (compilation, backport from 0.2.7.6):
7947 - Fix a compilation warning with Clang 3.6: Do not check the
7948 presence of an address which can never be NULL. Fixes bug 17781.
7950 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
7951 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
7952 a client authorized hidden service. Fixes bug 15823; bugfix
7956 Changes in version 0.2.9.10 - 2017-03-01
7957 Tor 0.2.9.10 backports a security fix from later Tor release. It also
7958 includes fixes for some major issues affecting directory authorities,
7959 LibreSSL compatibility, and IPv6 correctness.
7961 The Tor 0.2.9.x release series is now marked as a long-term-support
7962 series. We intend to backport security fixes to 0.2.9.x until at
7963 least January of 2020.
7965 o Major bugfixes (directory authority, 0.3.0.3-alpha):
7966 - During voting, when marking a relay as a probable sybil, do not
7967 clear its BadExit flag: sybils can still be bad in other ways
7968 too. (We still clear the other flags.) Fixes bug 21108; bugfix
7971 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
7972 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
7973 any IPv6 addresses. Instead, only reject a port over IPv6 if the
7974 exit policy rejects that port on more than an IPv6 /16 of
7975 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
7976 which rejected a relay's own IPv6 address by default. Fixes bug
7977 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
7979 o Major bugfixes (parsing, also in 0.3.0.4-rc):
7980 - Fix an integer underflow bug when comparing malformed Tor
7981 versions. This bug could crash Tor when built with
7982 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7983 0.2.9.8, which were built with -ftrapv by default. In other cases
7984 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7985 on 0.0.8pre1. Found by OSS-Fuzz.
7987 o Minor features (directory authorities, also in 0.3.0.4-rc):
7988 - Directory authorities now reject descriptors that claim to be
7989 malformed versions of Tor. Helps prevent exploitation of
7991 - Reject version numbers with components that exceed INT32_MAX.
7992 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
7993 Fixes bug 21450; bugfix on 0.0.8pre1.
7995 o Minor features (geoip):
7996 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
7999 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
8000 - Autoconf now checks to determine if OpenSSL structures are opaque,
8001 instead of explicitly checking for OpenSSL version numbers. Part
8003 - Support building with recent LibreSSL code that uses opaque
8004 structures. Closes ticket 21359.
8006 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
8007 - Repair a couple of (unreachable or harmless) cases of the risky
8008 comparison-by-subtraction pattern that caused bug 21278.
8010 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
8011 - The tor-resolve command line tool now rejects hostnames over 255
8012 characters in length. Previously, it would silently truncate them,
8013 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
8014 Patch by "junglefowl".
8017 Changes in version 0.2.9.9 - 2017-01-23
8018 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
8019 cause relays and clients to crash, even if they were not built with
8020 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
8021 versions, and also affects 0.3.0.1-alpha: all relays running an affected
8022 version should upgrade.
8024 This release also resolves a client-side onion service reachability
8025 bug, and resolves a pair of small portability issues.
8027 o Major bugfixes (security):
8028 - Downgrade the "-ftrapv" option from "always on" to "only on when
8029 --enable-expensive-hardening is provided." This hardening option,
8030 like others, can turn survivable bugs into crashes -- and having
8031 it on by default made a (relatively harmless) integer overflow bug
8032 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
8033 bugfix on 0.2.9.1-alpha.
8035 o Major bugfixes (client, onion service):
8036 - Fix a client-side onion service reachability bug, where multiple
8037 socks requests to an onion service (or a single slow request)
8038 could cause us to mistakenly mark some of the service's
8039 introduction points as failed, and we cache that failure so
8040 eventually we run out and can't reach the service. Also resolves a
8041 mysterious "Remote server sent bogus reason code 65021" log
8042 warning. The bug was introduced in ticket 17218, where we tried to
8043 remember the circuit end reason as a uint16_t, which mangled
8044 negative values. Partially fixes bug 21056 and fixes bug 20307;
8045 bugfix on 0.2.8.1-alpha.
8047 o Minor features (geoip):
8048 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
8051 o Minor bugfixes (portability):
8052 - Avoid crashing when Tor is built using headers that contain
8053 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
8054 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
8056 - Fix Libevent detection on platforms without Libevent 1 headers
8057 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
8060 Changes in version 0.2.8.12 - 2016-12-19
8061 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
8062 below) where Tor clients could crash when attempting to visit a
8063 hostile hidden service. Clients are recommended to upgrade as packages
8064 become available for their systems.
8066 It also includes an updated list of fallback directories, backported
8069 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
8070 backported to 0.2.8 in the future.
8072 o Major bugfixes (parsing, security, backported from 0.2.9.8):
8073 - Fix a bug in parsing that could cause clients to read a single
8074 byte past the end of an allocated region. This bug could be used
8075 to cause hardened clients (built with --enable-expensive-hardening)
8076 to crash if they tried to visit a hostile hidden service. Non-
8077 hardened clients are only affected depending on the details of
8078 their platform's memory allocator. Fixes bug 21018; bugfix on
8079 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8080 2016-12-002 and as CVE-2016-1254.
8082 o Minor features (fallback directory list, backported from 0.2.9.8):
8083 - Replace the 81 remaining fallbacks of the 100 originally
8084 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
8085 fallbacks (123 new, 54 existing, 27 removed) generated in December
8086 2016. Resolves ticket 20170.
8088 o Minor features (geoip, backported from 0.2.9.7-rc):
8089 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
8093 Changes in version 0.2.9.8 - 2016-12-19
8094 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
8096 The Tor 0.2.9 series makes mandatory a number of security features
8097 that were formerly optional. It includes support for a new shared-
8098 randomness protocol that will form the basis for next generation
8099 hidden services, includes a single-hop hidden service mode for
8100 optimizing .onion services that don't actually want to be hidden,
8101 tries harder not to overload the directory authorities with excessive
8102 downloads, and supports a better protocol versioning scheme for
8103 improved compatibility with other implementations of the Tor protocol.
8105 And of course, there are numerous other bugfixes and improvements.
8107 This release also includes a fix for a medium-severity issue (bug
8108 21018 below) where Tor clients could crash when attempting to visit a
8109 hostile hidden service. Clients are recommended to upgrade as packages
8110 become available for their systems.
8112 Below are listed the changes since Tor 0.2.8.11. For a list of
8113 changes since 0.2.9.7-rc, see the ChangeLog file.
8115 o New system requirements:
8116 - When building with OpenSSL, Tor now requires version 1.0.1 or
8117 later. OpenSSL 1.0.0 and earlier are no longer supported by the
8118 OpenSSL team, and should not be used. Closes ticket 20303.
8119 - Tor now requires Libevent version 2.0.10-stable or later. Older
8120 versions of Libevent have less efficient backends for several
8121 platforms, and lack the DNS code that we use for our server-side
8122 DNS support. This implements ticket 19554.
8123 - Tor now requires zlib version 1.2 or later, for security,
8124 efficiency, and (eventually) gzip support. (Back when we started,
8125 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
8126 released in 2003. We recommend the latest version.)
8128 o Deprecated features:
8129 - A number of DNS-cache-related sub-options for client ports are now
8130 deprecated for security reasons, and may be removed in a future
8131 version of Tor. (We believe that client-side DNS caching is a bad
8132 idea for anonymity, and you should not turn it on.) The options
8133 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
8134 UseIPv4Cache, and UseIPv6Cache.
8135 - A number of options are deprecated for security reasons, and may
8136 be removed in a future version of Tor. The options are:
8137 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
8138 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
8139 CloseHSClientCircuitsImmediatelyOnTimeout,
8140 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
8141 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
8142 UseNTorHandshake, and WarnUnsafeSocks.
8143 - The *ListenAddress options are now deprecated as unnecessary: the
8144 corresponding *Port options should be used instead. These options
8145 may someday be removed. The affected options are:
8146 ControlListenAddress, DNSListenAddress, DirListenAddress,
8147 NATDListenAddress, ORListenAddress, SocksListenAddress,
8148 and TransListenAddress.
8150 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
8151 - Fix a bug in parsing that could cause clients to read a single
8152 byte past the end of an allocated region. This bug could be used
8153 to cause hardened clients (built with --enable-expensive-hardening)
8154 to crash if they tried to visit a hostile hidden service. Non-
8155 hardened clients are only affected depending on the details of
8156 their platform's memory allocator. Fixes bug 21018; bugfix on
8157 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8158 2016-12-002 and as CVE-2016-1254.
8160 o Major features (build, hardening):
8161 - Tor now builds with -ftrapv by default on compilers that support
8162 it. This option detects signed integer overflow (which C forbids),
8163 and turns it into a hard-failure. We do not apply this option to
8164 code that needs to run in constant time to avoid side-channels;
8165 instead, we use -fwrapv in that code. Closes ticket 17983.
8166 - When --enable-expensive-hardening is selected, stop applying the
8167 clang/gcc sanitizers to code that needs to run in constant time.
8168 Although we are aware of no introduced side-channels, we are not
8169 able to prove that there are none. Related to ticket 17983.
8171 o Major features (circuit building, security):
8172 - Authorities, relays, and clients now require ntor keys in all
8173 descriptors, for all hops (except for rare hidden service protocol
8174 cases), for all circuits, and for all other roles. Part of
8176 - Authorities, relays, and clients only use ntor, except for
8177 rare cases in the hidden service protocol. Part of ticket 19163.
8179 o Major features (compilation):
8180 - Our big list of extra GCC warnings is now enabled by default when
8181 building with GCC (or with anything like Clang that claims to be
8182 GCC-compatible). To make all warnings into fatal compilation
8183 errors, pass --enable-fatal-warnings to configure. Closes
8185 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
8186 turn on C and POSIX extensions. (Previously, we attempted to do
8187 this on an ad hoc basis.) Closes ticket 19139.
8189 o Major features (directory authorities, hidden services):
8190 - Directory authorities can now perform the shared randomness
8191 protocol specified by proposal 250. Using this protocol, directory
8192 authorities generate a global fresh random value every day. In the
8193 future, this value will be used by hidden services to select
8194 HSDirs. This release implements the directory authority feature;
8195 the hidden service side will be implemented in the future as part
8196 of proposal 224. Resolves ticket 16943; implements proposal 250.
8198 o Major features (downloading, random exponential backoff):
8199 - When we fail to download an object from a directory service, wait
8200 for an (exponentially increasing) randomized amount of time before
8201 retrying, rather than a fixed interval as we did before. This
8202 prevents a group of Tor instances from becoming too synchronized,
8203 or a single Tor instance from becoming too predictable, in its
8204 download schedule. Closes ticket 15942.
8206 o Major features (resource management):
8207 - Tor can now notice it is about to run out of sockets, and
8208 preemptively close connections of lower priority. (This feature is
8209 off by default for now, since the current prioritizing method is
8210 yet not mature enough. You can enable it by setting
8211 "DisableOOSCheck 0", but watch out: it might close some sockets
8212 you would rather have it keep.) Closes ticket 18640.
8214 o Major features (single-hop "hidden" services):
8215 - Add experimental HiddenServiceSingleHopMode and
8216 HiddenServiceNonAnonymousMode options. When both are set to 1,
8217 every hidden service on that Tor instance becomes a non-anonymous
8218 Single Onion Service. Single Onions make one-hop (direct)
8219 connections to their introduction and rendezvous points. One-hop
8220 circuits make Single Onion servers easily locatable, but clients
8221 remain location-anonymous. This is compatible with the existing
8222 hidden service implementation, and works on the current Tor
8223 network without any changes to older relays or clients. Implements
8224 proposal 260, completes ticket 17178. Patch by teor and asn.
8226 o Major features (subprotocol versions):
8227 - Tor directory authorities now vote on a set of recommended
8228 "subprotocol versions", and on a set of required subprotocol
8229 versions. Clients and relays that lack support for a _required_
8230 subprotocol version will not start; those that lack support for a
8231 _recommended_ subprotocol version will warn the user to upgrade.
8232 This change allows compatible implementations of the Tor protocol(s)
8233 to exist without pretending to be 100% bug-compatible with
8234 particular releases of Tor itself. Closes ticket 19958; implements
8235 part of proposal 264.
8237 o Major bugfixes (circuit building):
8238 - Hidden service client-to-intro-point and service-to-rendezvous-
8239 point circuits use the TAP key supplied by the protocol, to avoid
8240 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
8242 o Major bugfixes (download scheduling):
8243 - Avoid resetting download status for consensuses hourly, since we
8244 already have another, smarter retry mechanism. Fixes bug 8625;
8245 bugfix on 0.2.0.9-alpha.
8246 - If a consensus expires while we are waiting for certificates to
8247 download, stop waiting for certificates.
8248 - If we stop waiting for certificates less than a minute after we
8249 started downloading them, do not consider the certificate download
8250 failure a separate failure. Fixes bug 20533; bugfix
8252 - When using exponential backoff in test networks, use a lower
8253 exponent, so the delays do not vary as much. This helps test
8254 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
8256 o Major bugfixes (exit policies):
8257 - Avoid disclosing exit outbound bind addresses, configured port
8258 bind addresses, and local interface addresses in relay descriptors
8259 by default under ExitPolicyRejectPrivate. Instead, only reject
8260 these (otherwise unlisted) addresses if
8261 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
8262 0.2.7.2-alpha. Patch by teor.
8264 o Major bugfixes (hidden services):
8265 - Allow Tor clients with appropriate controllers to work with
8266 FetchHidServDescriptors set to 0. Previously, this option also
8267 disabled descriptor cache lookup, thus breaking hidden services
8268 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
8269 - Clients now require hidden services to include the TAP keys for
8270 their intro points in the hidden service descriptor. This prevents
8271 an inadvertent upgrade to ntor, which a malicious hidden service
8272 could use to distinguish clients by consensus version. Fixes bug
8273 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
8275 o Major bugfixes (relay, resolver, logging):
8276 - For relays that don't know their own address, avoid attempting a
8277 local hostname resolve for each descriptor we download. This
8278 will cut down on the number of "Success: chose address 'x.x.x.x'"
8279 log lines, and also avoid confusing clock jumps if the resolver
8280 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
8282 o Minor features (port flags):
8283 - Add new flags to the *Port options to give finer control over which
8284 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
8285 and the synthetic flag OnionTrafficOnly, which is equivalent to
8286 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
8287 18693; patch by "teor".
8289 o Minor features (build, hardening):
8290 - Detect and work around a libclang_rt problem that would prevent
8291 clang from finding __mulodi4() on some 32-bit platforms, and thus
8292 keep -ftrapv from linking on those systems. Closes ticket 19079.
8293 - When building on a system without runtime support for the runtime
8294 hardening options, try to log a useful warning at configuration
8295 time, rather than an incomprehensible warning at link time. If
8296 expensive hardening was requested, this warning becomes an error.
8297 Closes ticket 18895.
8299 o Minor features (client, directory):
8300 - Since authorities now omit all routers that lack the Running and
8301 Valid flags, we assume that any relay listed in the consensus must
8302 have those flags. Closes ticket 20001; implements part of
8305 o Minor features (code safety):
8306 - In our integer-parsing functions, ensure that the maximum value we
8307 allow is no smaller than the minimum value. Closes ticket 19063;
8308 patch from "U+039b".
8310 o Minor features (compilation, portability):
8311 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
8314 o Minor features (config):
8315 - Warn users when descriptor and port addresses are inconsistent.
8316 Mitigates bug 13953; patch by teor.
8318 o Minor features (controller):
8319 - Allow controllers to configure basic client authorization on
8320 hidden services when they create them with the ADD_ONION controller
8321 command. Implements ticket 15588. Patch by "special".
8322 - Fire a STATUS_SERVER controller event whenever the hibernation
8323 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
8324 - Implement new GETINFO queries for all downloads that use
8325 download_status_t to schedule retries. This allows controllers to
8326 examine the schedule for pending downloads. Closes ticket 19323.
8328 o Minor features (development tools, etags):
8329 - Teach the "make tags" Makefile target how to correctly find
8330 "MOCK_IMPL" function definitions. Patch from nherring; closes
8333 o Minor features (directory authority):
8334 - After voting, if the authorities decide that a relay is not
8335 "Valid", they no longer include it in the consensus at all. Closes
8336 ticket 20002; implements part of proposal 272.
8337 - Directory authorities now only give the Guard flag to a relay if
8338 they are also giving it the Stable flag. This change allows us to
8339 simplify path selection for clients. It should have minimal effect
8340 in practice, since >99% of Guards already have the Stable flag.
8341 Implements ticket 18624.
8342 - Directory authorities now write their v3-status-votes file out to
8343 disk earlier in the consensus process, so we have a record of the
8344 votes even if we abort the consensus process. Resolves
8347 o Minor features (fallback directory list, new since 0.2.9.7-rc):
8348 - Replace the 81 remaining fallbacks of the 100 originally
8349 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
8350 fallbacks (123 new, 54 existing, 27 removed) generated in December
8351 2016. Resolves ticket 20170.
8353 o Minor features (hidden service):
8354 - Stop being so strict about the payload length of "rendezvous1"
8355 cells. We used to be locked in to the "TAP" handshake length, and
8356 now we can handle better handshakes like "ntor". Resolves
8359 o Minor features (infrastructure, time):
8360 - Tor now includes an improved timer backend, so that we can
8361 efficiently support tens or hundreds of thousands of concurrent
8362 timers, as will be needed for some of our planned anti-traffic-
8363 analysis work. This code is based on William Ahern's "timeout.c"
8364 project, which implements a "tickless hierarchical timing wheel".
8365 Closes ticket 18365.
8366 - Tor now uses the operating system's monotonic timers (where
8367 available) for internal fine-grained timing. Previously we would
8368 look at the system clock, and then attempt to compensate for the
8369 clock running backwards. Closes ticket 18908.
8371 o Minor features (logging):
8372 - Add a set of macros to check nonfatal assertions, for internal
8373 use. Migrating more of our checks to these should help us avoid
8374 needless crash bugs. Closes ticket 18613.
8375 - Provide a more useful warning message when configured with an
8376 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
8377 - When dumping unparseable router descriptors, optionally store them
8378 in separate files, named by digest, up to a configurable size
8379 limit. You can change the size limit by setting the
8380 MaxUnparseableDescSizeToLog option, and disable this feature by
8381 setting that option to 0. Closes ticket 18322.
8383 o Minor features (performance):
8384 - Change the "optimistic data" extension from "off by default" to
8385 "on by default". The default was ordinarily overridden by a
8386 consensus option, but when clients were bootstrapping for the
8387 first time, they would not have a consensus to get the option
8388 from. Changing this default saves a round-trip during startup.
8389 Closes ticket 18815.
8391 o Minor features (relay, usability):
8392 - When the directory authorities refuse a bad relay's descriptor,
8393 encourage the relay operator to contact us. Many relay operators
8394 won't notice this line in their logs, but it's a win if even a few
8395 learn why we don't like what their relay was doing. Resolves
8398 o Minor features (security, TLS):
8399 - Servers no longer support clients that lack AES ciphersuites.
8400 (3DES is no longer considered an acceptable cipher.) We believe
8401 that no such Tor clients currently exist, since Tor has required
8402 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
8404 o Minor features (testing):
8405 - Disable memory protections on OpenBSD when performing our unit
8406 tests for memwipe(). The test deliberately invokes undefined
8407 behavior, and the OpenBSD protections interfere with this. Patch
8408 from "rubiate". Closes ticket 20066.
8409 - Move the test-network.sh script to chutney, and modify tor's test-
8410 network.sh to call the (newer) chutney version when available.
8411 Resolves ticket 19116. Patch by teor.
8412 - Use the lcov convention for marking lines as unreachable, so that
8413 we don't count them when we're generating test coverage data.
8414 Update our coverage tools to understand this convention. Closes
8416 - Our link-handshake unit tests now check that when invalid
8417 handshakes fail, they fail with the error messages we expected.
8418 - Our unit testing code that captures log messages no longer
8419 prevents them from being written out if the user asked for them
8420 (by passing --debug or --info or --notice or --warn to the "test"
8421 binary). This change prevents us from missing unexpected log
8422 messages simply because we were looking for others. Related to
8424 - The unit tests now log all warning messages with the "BUG" flag.
8425 Previously, they only logged errors by default. This change will
8426 help us make our testing code more correct, and make sure that we
8427 only hit this code when we mean to. In the meantime, however,
8428 there will be more warnings in the unit test logs than before.
8429 This is preparatory work for ticket 19999.
8430 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
8431 assertion as a test failure.
8432 - We've done significant work to make the unit tests run faster.
8434 o Minor features (testing, ipv6):
8435 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
8436 tests. Remove bridges+hs, as it's somewhat redundant. This
8437 requires a recent chutney version that supports IPv6 clients,
8438 relays, and authorities. Closes ticket 20069; patch by teor.
8439 - Add the single-onion and single-onion-ipv6 chutney targets to
8440 "make test-network-all". This requires a recent chutney version
8441 with the single onion network flavors (git c72a652 or later).
8442 Closes ticket 20072; patch by teor.
8444 o Minor features (Tor2web):
8445 - Make Tor2web clients respect ReachableAddresses. This feature was
8446 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
8447 0.2.8.7. Implements feature 20034. Patch by teor.
8449 o Minor features (unix domain sockets):
8450 - When configuring a unix domain socket for a SocksPort,
8451 ControlPort, or Hidden service, you can now wrap the address in
8452 quotes, using C-style escapes inside the quotes. This allows unix
8453 domain socket paths to contain spaces. Resolves ticket 18753.
8455 o Minor features (user interface):
8456 - Tor now supports the ability to declare options deprecated, so
8457 that we can recommend that people stop using them. Previously, this
8458 was done in an ad-hoc way. There is a new --list-deprecated-options
8459 command-line option to list all of the deprecated options. Closes
8462 o Minor features (virtual addresses):
8463 - Increase the maximum number of bits for the IPv6 virtual network
8464 prefix from 16 to 104. In this way, the condition for address
8465 allocation is less restrictive. Closes ticket 20151; feature
8468 o Minor bug fixes (circuits):
8469 - Use the CircuitBuildTimeout option whenever
8470 LearnCircuitBuildTimeout is disabled. Previously, we would respect
8471 the option when a user disabled it, but not when it was disabled
8472 because some other option was set. Fixes bug 20073; bugfix on
8473 0.2.4.12-alpha. Patch by teor.
8475 o Minor bugfixes (build):
8476 - The current Git revision when building from a local repository is
8477 now detected correctly when using git worktrees. Fixes bug 20492;
8478 bugfix on 0.2.3.9-alpha.
8480 o Minor bugfixes (relay address discovery):
8481 - Stop reordering IP addresses returned by the OS. This makes it
8482 more likely that Tor will guess the same relay IP address every
8483 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
8484 Reported by René Mayrhofer, patch by "cypherpunks".
8486 o Minor bugfixes (memory allocation):
8487 - Change how we allocate memory for large chunks on buffers, to
8488 avoid a (currently impossible) integer overflow, and to waste less
8489 space when allocating unusually large chunks. Fixes bug 20081;
8490 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
8492 o Minor bugfixes (bootstrap):
8493 - Remember the directory server we fetched the consensus or previous
8494 certificates from, and use it to fetch future authority
8495 certificates. This change improves bootstrapping performance.
8496 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
8498 o Minor bugfixes (circuits):
8499 - Make sure extend_info_from_router() is only called on servers.
8500 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
8502 o Minor bugfixes (client, fascistfirewall):
8503 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
8504 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
8506 o Minor bugfixes (client, unix domain sockets):
8507 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
8508 the client address is meaningless. Fixes bug 20261; bugfix
8511 o Minor bugfixes (code style):
8512 - Fix an integer signedness conversion issue in the case conversion
8513 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
8515 o Minor bugfixes (compilation):
8516 - Build correctly on versions of libevent2 without support for
8517 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
8519 - When building with Clang, use a full set of GCC warnings.
8520 (Previously, we included only a subset, because of the way we
8521 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
8522 - Detect Libevent2 functions correctly on systems that provide
8523 libevent2, but where libevent1 is linked with -levent. Fixes bug
8524 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
8525 - Run correctly when built on Windows build environments that
8526 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
8528 o Minor bugfixes (configuration):
8529 - When parsing quoted configuration values from the torrc file,
8530 handle Windows line endings correctly. Fixes bug 19167; bugfix on
8531 0.2.0.16-alpha. Patch from "Pingl".
8533 o Minor bugfixes (directory authority):
8534 - Authorities now sort the "package" lines in their votes, for ease
8535 of debugging. (They are already sorted in consensus documents.)
8536 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
8537 - Die with a more useful error when the operator forgets to place
8538 the authority_signing_key file into the keys directory. This
8539 avoids an uninformative assert & traceback about having an invalid
8540 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
8541 - When allowing private addresses, mark Exits that only exit to
8542 private locations as such. Fixes bug 20064; bugfix
8544 - When parsing a detached signature, make sure we use the length of
8545 the digest algorithm instead of a hardcoded DIGEST256_LEN in
8546 order to avoid comparing bytes out-of-bounds with a smaller digest
8547 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
8549 o Minor bugfixes (getpass):
8550 - Defensively fix a non-triggerable heap corruption at do_getpass()
8551 to protect ourselves from mistakes in the future. Fixes bug
8552 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
8555 o Minor bugfixes (guard selection):
8556 - Don't mark guards as unreachable if connection_connect() fails.
8557 That function fails for local reasons, so it shouldn't reveal
8558 anything about the status of the guard. Fixes bug 14334; bugfix
8560 - Use a single entry guard even if the NumEntryGuards consensus
8561 parameter is not provided. Fixes bug 17688; bugfix
8564 o Minor bugfixes (hidden services):
8565 - Increase the minimum number of internal circuits we preemptively
8566 build from 2 to 3, so a circuit is available when a client
8567 connects to another onion service. Fixes bug 13239; bugfix
8569 - Allow hidden services to run on IPv6 addresses even when the
8570 IPv6Exit option is not set. Fixes bug 18357; bugfix
8572 - Stop logging intro point details to the client log on certain
8573 error conditions. Fixed as part of bug 20012; bugfix on
8574 0.2.4.8-alpha. Patch by teor.
8575 - When deleting an ephemeral hidden service, close its intro points
8576 even if they are not completely open. Fixes bug 18604; bugfix
8578 - When configuring hidden services, check every hidden service
8579 directory's permissions. Previously, we only checked the last
8580 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
8582 o Minor bugfixes (IPv6, testing):
8583 - Check for IPv6 correctly on Linux when running test networks.
8584 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
8586 o Minor bugfixes (Linux seccomp2 sandbox):
8587 - Add permission to run the sched_yield() and sigaltstack() system
8588 calls, in order to support versions of Tor compiled with asan or
8589 ubsan code that use these calls. Now "sandbox 1" and
8590 "--enable-expensive-hardening" should be compatible on more
8591 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
8593 o Minor bugfixes (logging):
8594 - Downgrade a harmless log message about the
8595 pending_entry_connections list from "warn" to "info". Mitigates
8597 - Log a more accurate message when we fail to dump a microdescriptor.
8598 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
8599 - When logging a directory ownership mismatch, log the owning
8600 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
8601 - When we are unable to remove the bw_accounting file, do not warn
8602 if the reason we couldn't remove it was that it didn't exist.
8603 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
8605 o Minor bugfixes (memory leak):
8606 - Fix a series of slow memory leaks related to parsing torrc files
8607 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
8608 - Avoid a small memory leak when informing worker threads about
8609 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
8610 - Fix a small memory leak when receiving AF_UNIX connections on a
8611 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
8612 - When moving a signed descriptor object from a source to an
8613 existing destination, free the allocated memory inside that
8614 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
8615 - Fix a memory leak and use-after-free error when removing entries
8616 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
8617 0.2.5.5-alpha. Patch from "cypherpunks".
8618 - Fix a small, uncommon memory leak that could occur when reading a
8619 truncated ed25519 key file. Fixes bug 18956; bugfix
8622 o Minor bugfixes (option parsing):
8623 - Count unix sockets when counting client listeners (SOCKS, Trans,
8624 NATD, and DNS). This has no user-visible behavior changes: these
8625 options are set once, and never read. Required for correct
8626 behavior in ticket 17178. Fixes bug 19677; bugfix on
8627 0.2.6.3-alpha. Patch by teor.
8629 o Minor bugfixes (options):
8630 - Check the consistency of UseEntryGuards and EntryNodes more
8631 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
8633 - Stop changing the configured value of UseEntryGuards on
8634 authorities and Tor2web clients. Fixes bug 20074; bugfix on
8635 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
8638 o Minor bugfixes (relay):
8639 - Ensure relays don't make multiple connections during bootstrap.
8640 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
8641 - Do not try to parallelize workers more than 16x without the user
8642 explicitly configuring us to do so, even if we do detect more than
8643 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
8645 o Minor bugfixes (testing):
8646 - The test-stem and test-network makefile targets now depend only on
8647 the tor binary that they are testing. Previously, they depended on
8648 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
8649 patch from "cypherpunks".
8650 - Allow clients to retry HSDirs much faster in test networks. Fixes
8651 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
8652 - Avoid a unit test failure on systems with over 16 detectable CPU
8653 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
8654 - Let backtrace tests work correctly under AddressSanitizer:
8655 disable ASAN's detection of segmentation faults while running
8656 test_bt.sh, so that we can make sure that our own backtrace
8657 generation code works. Fixes bug 18934; bugfix
8658 on 0.2.5.2-alpha. Patch from "cypherpunks".
8659 - Fix the test-network-all target on out-of-tree builds by using the
8660 correct path to the test driver script. Fixes bug 19421; bugfix
8662 - Stop spurious failures in the local interface address discovery
8663 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
8665 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
8666 removed the ECDH ciphers which caused the tests to fail on
8667 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
8668 - The tor_tls_server_info_callback unit test no longer crashes when
8669 debug-level logging is turned on. Fixes bug 20041; bugfix
8672 o Minor bugfixes (time):
8673 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
8674 bugfix on all released tor versions.
8675 - When computing the difference between two times in milliseconds,
8676 we now round to the nearest millisecond correctly. Previously, we
8677 could sometimes round in the wrong direction. Fixes bug 19428;
8678 bugfix on 0.2.2.2-alpha.
8680 o Minor bugfixes (Tor2web):
8681 - Prevent Tor2web clients from running hidden services: these services
8682 are not anonymous due to the one-hop client paths. Fixes bug
8683 19678. Patch by teor.
8685 o Minor bugfixes (user interface):
8686 - Display a more accurate number of suppressed messages in the log
8687 rate-limiter. Previously, there was a potential integer overflow
8688 in the counter. Now, if the number of messages hits a maximum, the
8689 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
8691 - Fix a typo in the passphrase prompt for the ed25519 identity key.
8692 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
8694 o Code simplification and refactoring:
8695 - Remove redundant declarations of the MIN macro. Closes
8697 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
8698 Closes ticket 18462; patch from "icanhasaccount".
8699 - Split the 600-line directory_handle_command_get function into
8700 separate functions for different URL types. Closes ticket 16698.
8703 - Add module-level internal documentation for 36 C files that
8704 previously didn't have a high-level overview. Closes ticket 20385.
8705 - Correct the IPv6 syntax in our documentation for the
8706 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
8707 - Correct the minimum bandwidth value in torrc.sample, and queue a
8708 corresponding change for torrc.minimal. Closes ticket 20085.
8709 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
8710 ticket 19153. Patch from "U+039b".
8711 - Module-level documentation for several more modules. Closes
8712 tickets 19287 and 19290.
8713 - Document the --passphrase-fd option in the tor manpage. Fixes bug
8714 19504; bugfix on 0.2.7.3-rc.
8715 - Document the default PathsNeededToBuildCircuits value that's used
8716 by clients when the directory authorities don't set
8717 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
8718 Patch by teor, reported by Jesse V.
8719 - Fix manual for the User option: it takes a username, not a UID.
8720 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
8722 - Fix the description of the --passphrase-fd option in the
8723 tor-gencert manpage. The option is used to pass the number of a
8724 file descriptor to read the passphrase from, not to read the file
8725 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
8728 - We no longer include the (dead, deprecated) bufferevent code in
8729 Tor. Closes ticket 19450. Based on a patch from "U+039b".
8732 - Remove support for "GET /tor/bytes.txt" DirPort request, and
8733 "GETINFO dir-usage" controller request, which were only available
8734 via a compile-time option in Tor anyway. Feature was added in
8735 0.2.2.1-alpha. Resolves ticket 19035.
8736 - There is no longer a compile-time option to disable support for
8737 TransPort. (If you don't want TransPort, just don't use it.) Patch
8738 from "U+039b". Closes ticket 19449.
8741 - Run more workqueue tests as part of "make check". These had
8742 previously been implemented, but you needed to know special
8743 command-line options to enable them.
8744 - We now have unit tests for our code to reject zlib "compression
8745 bombs". (Fortunately, the code works fine.)
8748 Changes in version 0.2.8.11 - 2016-12-08
8749 Tor 0.2.8.11 backports fixes for additional portability issues that
8750 could prevent Tor from building correctly on OSX Sierra, or with
8751 OpenSSL 1.1. Affected users should upgrade; others can safely stay
8754 o Minor bugfixes (portability):
8755 - Avoid compilation errors when building on OSX Sierra. Sierra began
8756 to support the getentropy() and clock_gettime() APIs, but created
8757 a few problems in doing so. Tor 0.2.9 has a more thorough set of
8758 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
8759 monotonic time interfaces. Fixes bug 20865. Bugfix
8762 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
8763 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
8764 architectures. Closes ticket 20588.
8767 Changes in version 0.2.8.10 - 2016-12-02
8768 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
8769 unusable after they left standby mode. It also backports fixes for
8770 a few portability issues and a small but problematic memory leak.
8772 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
8773 - When Tor leaves standby because of a new application request, open
8774 circuits as needed to serve that request. Previously, we would
8775 potentially wait a very long time. Fixes part of bug 19969; bugfix
8778 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
8779 - Clients now respond to new application stream requests immediately
8780 when they arrive, rather than waiting up to one second before
8781 starting to handle them. Fixes part of bug 19969; bugfix
8784 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
8785 - Work around a bug in the OSX 10.12 SDK that would prevent us from
8786 successfully targeting earlier versions of OSX. Resolves
8789 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
8790 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
8791 20551; bugfix on 0.2.1.1-alpha.
8793 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
8794 - Work around a memory leak in OpenSSL 1.1 when encoding public
8795 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
8797 o Minor features (geoip):
8798 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
8802 Changes in version 0.2.8.9 - 2016-10-17
8803 Tor 0.2.8.9 backports a fix for a security hole in previous versions
8804 of Tor that would allow a remote attacker to crash a Tor client,
8805 hidden service, relay, or authority. All Tor users should upgrade to
8806 this version, or to 0.2.9.4-alpha. Patches will be released for older
8809 o Major features (security fixes, also in 0.2.9.4-alpha):
8810 - Prevent a class of security bugs caused by treating the contents
8811 of a buffer chunk as if they were a NUL-terminated string. At
8812 least one such bug seems to be present in all currently used
8813 versions of Tor, and would allow an attacker to remotely crash
8814 most Tor instances, especially those compiled with extra compiler
8815 hardening. With this defense in place, such bugs can't crash Tor,
8816 though we should still fix them as they occur. Closes ticket
8817 20384 (TROVE-2016-10-001).
8819 o Minor features (geoip):
8820 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
8824 Changes in version 0.2.8.8 - 2016-09-23
8825 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
8826 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
8827 who select public relays as their bridges.
8829 o Major bugfixes (crash):
8830 - Fix a complicated crash bug that could affect Tor clients
8831 configured to use bridges when replacing a networkstatus consensus
8832 in which one of their bridges was mentioned. OpenBSD users saw
8833 more crashes here, but all platforms were potentially affected.
8834 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
8836 o Major bugfixes (relay, OOM handler):
8837 - Fix a timing-dependent assertion failure that could occur when we
8838 tried to flush from a circuit after having freed its cells because
8839 of an out-of-memory condition. Fixes bug 20203; bugfix on
8840 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
8843 o Minor feature (fallback directories):
8844 - Remove broken fallbacks from the hard-coded fallback directory
8845 list. Closes ticket 20190; patch by teor.
8847 o Minor features (geoip):
8848 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
8852 Changes in version 0.2.8.7 - 2016-08-24
8853 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
8854 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
8855 who sets the ReachableAddresses option, and all bridges, are strongly
8856 encouraged to upgrade.
8858 o Directory authority changes:
8859 - The "Tonga" bridge authority has been retired; the new bridge
8860 authority is "Bifroest". Closes tickets 19728 and 19690.
8862 o Major bugfixes (client, security):
8863 - Only use the ReachableAddresses option to restrict the first hop
8864 in a path. In earlier versions of 0.2.8.x, it would apply to
8865 every hop in the path, with a possible degradation in anonymity
8866 for anyone using an uncommon ReachableAddress setting. Fixes bug
8867 19973; bugfix on 0.2.8.2-alpha.
8869 o Minor features (geoip):
8870 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
8873 o Minor bugfixes (compilation):
8874 - Remove an inappropriate "inline" in tortls.c that was causing
8875 warnings on older versions of GCC. Fixes bug 19903; bugfix
8878 o Minor bugfixes (fallback directories):
8879 - Avoid logging a NULL string pointer when loading fallback
8880 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
8881 and 0.2.8.1-alpha. Report and patch by "rubiate".
8884 Changes in version 0.2.8.6 - 2016-08-02
8886 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
8888 The Tor 0.2.8 series improves client bootstrapping performance,
8889 completes the authority-side implementation of improved identity
8890 keys for relays, and includes numerous bugfixes and performance
8891 improvements throughout the program. This release continues to
8892 improve the coverage of Tor's test suite. For a full list of
8893 changes since Tor 0.2.7, see the ReleaseNotes file.
8895 Below is a list of the changes since Tor 0.2.7.
8897 o New system requirements:
8898 - Tor no longer attempts to support platforms where the "time_t"
8899 type is unsigned. (To the best of our knowledge, only OpenVMS does
8900 this, and Tor has never actually built on OpenVMS.) Closes
8902 - Tor no longer supports versions of OpenSSL with a broken
8903 implementation of counter mode. (This bug was present in OpenSSL
8904 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
8905 longer runs with, these versions.
8906 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
8907 later (released in 2008 and 2009 respectively). If you are
8908 building Tor from the git repository instead of from the source
8909 distribution, and your tools are older than this, you will need to
8910 upgrade. Closes ticket 17732.
8912 o Directory authority changes:
8913 - Update the V3 identity key for the dannenberg directory authority:
8914 it was changed on 18 November 2015. Closes task 17906. Patch
8916 - Urras is no longer a directory authority. Closes ticket 19271.
8918 o Major features (directory system):
8919 - Include a trial list of default fallback directories, based on an
8920 opt-in survey of suitable relays. Doing this should make clients
8921 bootstrap more quickly and reliably, and reduce the load on the
8922 directory authorities. Closes ticket 15775. Patch by teor.
8923 Candidates identified using an OnionOO script by weasel, teor,
8924 gsathya, and karsten.
8925 - Previously only relays that explicitly opened a directory port
8926 (DirPort) accepted directory requests from clients. Now all
8927 relays, with and without a DirPort, accept and serve tunneled
8928 directory requests that they receive through their ORPort. You can
8929 disable this behavior using the new DirCache option. Closes
8931 - When bootstrapping multiple consensus downloads at a time, use the
8932 first one that starts downloading, and close the rest. This
8933 reduces failures when authorities or fallback directories are slow
8934 or down. Together with the code for feature 15775, this feature
8935 should reduces failures due to fallback churn. Implements ticket
8936 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
8939 o Major features (security, Linux):
8940 - When Tor starts as root on Linux and is told to switch user ID, it
8941 can now retain the capability to bind to low ports. By default,
8942 Tor will do this only when it's switching user ID and some low
8943 ports have been configured. You can change this behavior with the
8944 new option KeepBindCapabilities. Closes ticket 8195.
8946 o Major bugfixes (client, bootstrapping):
8947 - Check if bootstrap consensus downloads are still needed when the
8948 linked connection attaches. This prevents tor making unnecessary
8949 begindir-style connections, which are the only directory
8950 connections tor clients make since the fix for 18483 was merged.
8951 - Fix some edge cases where consensus download connections may not
8952 have been closed, even though they were not needed. Related to fix
8954 - Make relays retry consensus downloads the correct number of times,
8955 rather than the more aggressive client retry count. Fixes part of
8958 o Major bugfixes (dns proxy mode, crash):
8959 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8960 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8962 o Major bugfixes (ed25519, voting):
8963 - Actually enable support for authorities to match routers by their
8964 Ed25519 identities. Previously, the code had been written, but
8965 some debugging code that had accidentally been left in the
8966 codebase made it stay turned off. Fixes bug 17702; bugfix
8968 - When collating votes by Ed25519 identities, authorities now
8969 include a "NoEdConsensus" flag if the ed25519 value (or lack
8970 thereof) for a server does not reflect the majority consensus.
8971 Related to bug 17668; bugfix on 0.2.7.2-alpha.
8972 - When generating a vote with keypinning disabled, never include two
8973 entries for the same ed25519 identity. This bug was causing
8974 authorities to generate votes that they could not parse when a
8975 router violated key pinning by changing its RSA identity but
8976 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
8977 18318. Bugfix on 0.2.7.2-alpha.
8979 o Major bugfixes (key management):
8980 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8981 pointer to the previous (uninitialized) key value. The impact here
8982 should be limited to a difficult-to-trigger crash, if OpenSSL is
8983 running an engine that makes key generation failures possible, or
8984 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8985 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8988 o Major bugfixes (security, client, DNS proxy):
8989 - Stop a crash that could occur when a client running with DNSPort
8990 received a query with multiple address types, and the first
8991 address type was not supported. Found and fixed by Scott Dial.
8992 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
8994 o Major bugfixes (security, compilation):
8995 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
8996 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
8997 cause a compiler warning, thereby making other checks fail, and
8998 needlessly disabling compiler-hardening support. Fixes one case of
8999 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
9000 - Repair hardened builds under the clang compiler. Previously, our
9001 use of _FORTIFY_SOURCE would conflict with clang's address
9002 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
9004 o Major bugfixes (security, pointers):
9005 - Avoid a difficult-to-trigger heap corruption attack when extending
9006 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9007 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9008 Reported by Guido Vranken.
9010 o Major bugfixes (testing):
9011 - Fix a bug that would block 'make test-network-all' on systems where
9012 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
9014 o Major bugfixes (user interface):
9015 - Correctly give a warning in the cases where a relay is specified
9016 by nickname, and one such relay is found, but it is not officially
9017 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
9019 o Minor features (accounting):
9020 - Added two modes to the AccountingRule option: One for limiting
9021 only the number of bytes sent ("AccountingRule out"), and one for
9022 limiting only the number of bytes received ("AccountingRule in").
9023 Closes ticket 15989; patch from "unixninja92".
9025 o Minor features (bug-resistance):
9026 - Make Tor survive errors involving connections without a
9027 corresponding event object. Previously we'd fail with an
9028 assertion; now we produce a log message. Related to bug 16248.
9029 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
9030 level code, to harden against accidental failures to NUL-
9031 terminate. Part of ticket 17852. Patch from jsturgix. Found
9034 o Minor features (build):
9035 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
9036 as having possible IPFW support. Closes ticket 18448. Patch from
9038 - Since our build process now uses "make distcheck", we no longer
9039 force "make dist" to depend on "make check". Closes ticket 17893;
9040 patch from "cypherpunks".
9041 - Tor now builds once again with the recent OpenSSL 1.1 development
9042 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
9043 tracking OpenSSL 1.1 development as it has progressed, and fixing
9044 numerous compatibility issues as they arose. See tickets
9045 17549, 17921, 17984, 19499, and 18286.
9046 - When building manual pages, set the timezone to "UTC", so that the
9047 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
9048 Patch from intrigeri.
9050 o Minor features (clients):
9051 - Make clients, onion services, and bridge relays always use an
9052 encrypted begindir connection for directory requests. Resolves
9053 ticket 18483. Patch by teor.
9055 o Minor features (controller):
9056 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
9057 controllers can examine the the reject rules added by
9058 ExitPolicyRejectPrivate. This makes it easier for stem to display
9060 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
9061 tickets 16774 and 17817. Patch by George Tankersley.
9062 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
9063 service descriptor from a service's local hidden service
9064 descriptor cache. Closes ticket 14846.
9066 o Minor features (crypto):
9067 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
9068 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
9070 - Improve performance when hashing non-multiple of 8 sized buffers,
9071 based on Andrew Moon's public domain SipHash-2-4 implementation.
9072 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
9073 - Validate the hard-coded Diffie-Hellman parameters and ensure that
9074 p is a safe prime, and g is a suitable generator. Closes
9076 - When allocating a digest state object, allocate no more space than
9077 we actually need. Previously, we would allocate as much space as
9078 the state for the largest algorithm would need. This change saves
9079 up to 672 bytes per circuit. Closes ticket 17796.
9081 o Minor features (directory downloads):
9082 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
9083 directory mirrors. The default is 1; set it to 0 to disable
9084 fallbacks. Implements ticket 17576. Patch by teor.
9085 - Wait for busy authorities and fallback directories to become non-
9086 busy when bootstrapping. (A similar change was made in 6c443e987d
9087 for directory caches chosen from the consensus.) Closes ticket
9088 17864; patch by teor.
9090 o Minor features (geoip):
9091 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
9094 o Minor features (hidden service directory):
9095 - Streamline relay-side hsdir handling: when relays consider whether
9096 to accept an uploaded hidden service descriptor, they no longer
9097 check whether they are one of the relays in the network that is
9098 "supposed" to handle that descriptor. Implements ticket 18332.
9100 o Minor features (IPv6):
9101 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
9102 to 1, tor prefers IPv6 directory addresses.
9103 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
9104 avoids using IPv4 for client OR and directory connections.
9105 - Add address policy assume_action support for IPv6 addresses.
9106 - Add an argument 'ipv6=address:orport' to the DirAuthority and
9107 FallbackDir torrc options, to specify an IPv6 address for an
9108 authority or fallback directory. Add hard-coded ipv6 addresses for
9109 directory authorities that have them. Closes ticket 17327; patch
9110 from Nick Mathewson and teor.
9111 - Allow users to configure directory authorities and fallback
9112 directory servers with IPv6 addresses and ORPorts. Resolves
9114 - Limit IPv6 mask bits to 128.
9115 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
9116 17638; bugfix on 0.0.2pre8. Patch by teor.
9117 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
9118 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
9119 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
9120 - Warn when comparing against an AF_UNSPEC address in a policy, it's
9121 almost always a bug. Closes ticket 17863; patch by teor.
9122 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
9123 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
9125 o Minor features (Linux seccomp2 sandbox):
9126 - Reject attempts to change our Address with "Sandbox 1" enabled.
9127 Changing Address with Sandbox turned on would never actually work,
9128 but previously it would fail in strange and confusing ways. Found
9131 o Minor features (logging):
9132 - When logging to syslog, allow a tag to be added to the syslog
9133 identity (the string prepended to every log message). The tag can
9134 be configured with SyslogIdentityTag and defaults to none. Setting
9135 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
9138 o Minor features (portability):
9139 - Use timingsafe_memcmp() where available. Closes ticket 17944;
9140 patch from <logan@hackers.mu>.
9142 o Minor features (relay, address discovery):
9143 - Add a family argument to get_interface_addresses_raw() and
9144 subfunctions to make network interface address interogation more
9145 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
9146 types of interfaces from the operating system. Resolves
9148 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
9149 fails to enumerate interface addresses using the platform-specific
9150 API, have it rely on the UDP socket fallback technique to try and
9151 find out what IP addresses (both IPv4 and IPv6) our machine has.
9152 Resolves ticket 17951.
9154 o Minor features (replay cache):
9155 - The replay cache now uses SHA256 instead of SHA1. Implements
9156 feature 8961. Patch by teor, issue reported by rransom.
9158 o Minor features (robustness):
9159 - Exit immediately with an error message if the code attempts to use
9160 Libevent without having initialized it. This should resolve some
9161 frequently-made mistakes in our unit tests. Closes ticket 18241.
9163 o Minor features (security, clock):
9164 - Warn when the system clock appears to move back in time (when the
9165 state file was last written in the future). Tor doesn't know that
9166 consensuses have expired if the clock is in the past. Patch by
9167 teor. Implements ticket 17188.
9169 o Minor features (security, exit policies):
9170 - ExitPolicyRejectPrivate now rejects more private addresses by
9171 default. Specifically, it now rejects the relay's outbound bind
9172 addresses (if configured), and the relay's configured port
9173 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
9174 0.2.0.11-alpha. Patch by teor.
9176 o Minor features (security, memory erasure):
9177 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9178 zero size. Check size argument to memwipe() for underflow. Fixes
9179 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9181 - Set the unused entries in a smartlist to NULL. This helped catch
9182 a (harmless) bug, and shouldn't affect performance too much.
9183 Implements ticket 17026.
9184 - Use SecureMemoryWipe() function to securely clean memory on
9185 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
9186 Implements feature 17986.
9187 - Use explicit_bzero or memset_s when present. Previously, we'd use
9188 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
9189 from <logan@hackers.mu> and <selven@hackers.mu>.
9191 o Minor features (security, RNG):
9192 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
9193 positively are not allowed to fail. Previously we depended on
9194 internal details of OpenSSL's behavior. Closes ticket 17686.
9195 - Never use the system entropy output directly for anything besides
9196 seeding the PRNG. When we want to generate important keys, instead
9197 of using system entropy directly, we now hash it with the PRNG
9198 stream. This may help resist certain attacks based on broken OS
9199 entropy implementations. Closes part of ticket 17694.
9200 - Use modern system calls (like getentropy() or getrandom()) to
9201 generate strong entropy on platforms that have them. Closes
9204 o Minor features (security, win32):
9205 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
9206 attack. Fixes bug 18123; bugfix on all tor versions. Patch
9209 o Minor features (unix domain sockets):
9210 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
9211 Unix domain sockets without checking the permissions on the parent
9212 directory. (Tor checks permissions by default because some
9213 operating systems only check permissions on the parent directory.
9214 However, some operating systems do look at permissions on the
9215 socket, and tor's default check is unneeded.) Closes ticket 18458.
9218 o Minor features (unix file permissions):
9219 - Defer creation of Unix sockets until after setuid. This avoids
9220 needing CAP_CHOWN and CAP_FOWNER when using systemd's
9221 CapabilityBoundingSet, or chown and fowner when using SELinux.
9222 Implements part of ticket 17562. Patch from Jamie Nguyen.
9223 - If any directory created by Tor is marked as group readable, the
9224 filesystem group is allowed to be either the default GID or the
9225 root user. Allowing root to read the DataDirectory prevents the
9226 need for CAP_READ_SEARCH when using systemd's
9227 CapabilityBoundingSet, or dac_read_search when using SELinux.
9228 Implements part of ticket 17562. Patch from Jamie Nguyen.
9229 - Introduce a new DataDirectoryGroupReadable option. If it is set to
9230 1, the DataDirectory will be made readable by the default GID.
9231 Implements part of ticket 17562. Patch from Jamie Nguyen.
9233 o Minor bugfixes (accounting):
9234 - The max bandwidth when using 'AccountRule sum' is now correctly
9235 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
9238 o Minor bugfixes (assert, portability):
9239 - Fix an assertion failure in memarea.c on systems where "long" is
9240 shorter than the size of a pointer. Fixes bug 18716; bugfix
9243 o Minor bugfixes (bootstrap):
9244 - Consistently use the consensus download schedule for authority
9245 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
9247 o Minor bugfixes (build):
9248 - Avoid spurious failures from configure files related to calling
9249 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
9250 0.2.0.1-alpha. Patch from "cypherpunks".
9251 - Do not link the unit tests against both the testing and non-
9252 testing versions of the static libraries. Fixes bug 18490; bugfix
9254 - Resolve warnings when building on systems that are concerned with
9255 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
9257 - Silence spurious clang-scan warnings in the ed25519_donna code by
9258 explicitly initializing some objects. Fixes bug 18384; bugfix on
9259 0.2.7.2-alpha. Patch by teor.
9260 - When libscrypt.h is found, but no libscrypt library can be linked,
9261 treat libscrypt as absent. Fixes bug 19161; bugfix
9263 - Cause the unit tests to compile correctly on mingw64 versions that
9264 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
9265 - Don't try to use the pthread_condattr_setclock() function unless
9266 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
9267 17819; bugfix on 0.2.6.3-alpha.
9268 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
9270 - Fix search for libevent libraries on OpenBSD (and other systems
9271 that install libevent 1 and libevent 2 in parallel). Fixes bug
9272 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
9273 - Isolate environment variables meant for tests from the rest of the
9274 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
9275 - Mark all object files that include micro-revision.i as depending
9276 on it, so as to make parallel builds more reliable. Fixes bug
9277 17826; bugfix on 0.2.5.1-alpha.
9278 - Remove config.log only from make distclean, not from make clean.
9279 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
9280 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
9282 - Remove an #endif from configure.ac so that we correctly detect the
9283 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
9286 o Minor bugfixes (client, bootstrap):
9287 - Count receipt of new microdescriptors as progress towards
9288 bootstrapping. Previously, with EntryNodes set, Tor might not
9289 successfully repopulate the guard set on bootstrapping. Fixes bug
9290 16825; bugfix on 0.2.3.1-alpha.
9292 o Minor bugfixes (code correctness):
9293 - Fix a bad memory handling bug that would occur if we had queued a
9294 cell on a channel's incoming queue. Fortunately, we can't actually
9295 queue a cell like that as our code is constructed today, but it's
9296 best to avoid this kind of error, even if there isn't any code
9297 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
9298 - Assert that allocated memory held by the reputation code is freed
9299 according to its internal counters. Fixes bug 17753; bugfix
9301 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
9303 - Update to the latest version of Trunnel, which tries harder to
9304 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
9305 by clang address sanitizer. Fixes bug 18373; bugfix
9307 - When closing an entry connection, generate a warning if we should
9308 have sent an end cell for it but we haven't. Fixes bug 17876;
9309 bugfix on 0.2.3.2-alpha.
9311 o Minor bugfixes (configuration):
9312 - Fix a tiny memory leak when parsing a port configuration ending in
9313 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
9315 o Minor bugfixes (containers):
9316 - If we somehow attempt to construct a heap with more than
9317 1073741822 elements, avoid an integer overflow when maintaining
9318 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
9320 o Minor bugfixes (controller, microdescriptors):
9321 - Make GETINFO dir/status-vote/current/consensus conform to the
9322 control specification by returning "551 Could not open cached
9323 consensus..." when not caching consensuses. Fixes bug 18920;
9324 bugfix on 0.2.2.6-alpha.
9326 o Minor bugfixes (crypto):
9327 - Check the return value of HMAC() and assert on failure. Fixes bug
9328 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
9330 o Minor bugfixes (directories):
9331 - When fetching extrainfo documents, compare their SHA256 digests
9332 and Ed25519 signing key certificates with the routerinfo that led
9333 us to fetch them, rather than with the most recent routerinfo.
9334 Otherwise we generate many spurious warnings about mismatches.
9335 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
9336 - When generating a URL for a directory server on an IPv6 address,
9337 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
9338 on 0.2.3.9-alpha. Patch from Malek.
9340 o Minor bugfixes (downloading):
9341 - Predict more correctly whether we'll be downloading over HTTP when
9342 we determine the maximum length of a URL. This should avoid a
9343 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
9346 o Minor bugfixes (exit policies, security):
9347 - Refresh an exit relay's exit policy when interface addresses
9348 change. Previously, tor only refreshed the exit policy when the
9349 configured external address changed. Fixes bug 18208; bugfix on
9350 0.2.7.3-rc. Patch by teor.
9352 o Minor bugfixes (fallback directories):
9353 - Mark fallbacks as "too busy" when they return a 503 response,
9354 rather than just marking authorities. Fixes bug 17572; bugfix on
9355 0.2.4.7-alpha. Patch by teor.
9356 - When requesting extrainfo descriptors from a trusted directory
9357 server, check whether it is an authority or a fallback directory
9358 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
9359 0.2.4.7-alpha. Reported by atagar, patch by teor.
9361 o Minor bugfixes (hidden service, client):
9362 - Handle the case where the user makes several fast consecutive
9363 requests to the same .onion address. Previously, the first six
9364 requests would each trigger a descriptor fetch, each picking a
9365 directory (there are 6 overall) and the seventh one would fail
9366 because no directories were left, thereby triggering a close on
9367 all current directory connections asking for the hidden service.
9368 The solution here is to not close the connections if we have
9369 pending directory fetches. Fixes bug 15937; bugfix
9372 o Minor bugfixes (hidden service, control port):
9373 - Add the onion address to the HS_DESC event for the UPLOADED action
9374 both on success or failure. It was previously hardcoded with
9375 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
9377 o Minor bugfixes (hidden service, directory):
9378 - Bridges now refuse "rendezvous2" (hidden service descriptor)
9379 publish attempts. Suggested by ticket 18332.
9381 o Minor bugfixes (IPv6):
9382 - Update the limits in max_dl_per_request for IPv6 address length.
9383 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
9385 o Minor bugfixes (Linux seccomp2 sandbox):
9386 - Allow more syscalls when running with "Sandbox 1" enabled:
9387 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
9388 some systems, these are required for Tor to start. Fixes bug
9389 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
9390 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
9391 so that get_interface_address6_via_udp_socket_hack() can work.
9392 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
9393 - Allow the setrlimit syscall, and the prlimit and prlimit64
9394 syscalls, which some libc implementations use under the hood.
9395 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
9396 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
9397 enabled and no DNS resolvers configured. This should help TAILS
9398 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
9399 - Fix a crash when using offline master ed25519 keys with the Linux
9400 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
9401 - Allow statistics to be written to disk when "Sandbox 1" is
9402 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
9403 0.2.6.1-alpha respectively.
9405 o Minor bugfixes (logging):
9406 - In log messages that include a function name, use __FUNCTION__
9407 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
9408 with clang __PRETTY_FUNCTION__ has extra information we don't
9409 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
9411 - Remove needless quotes from a log message about unparseable
9412 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
9413 - Scrub service name in "unrecognized service ID" log messages.
9414 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
9415 - When logging information about an unparsable networkstatus vote or
9416 consensus, do not say "vote" when we mean consensus. Fixes bug
9417 18368; bugfix on 0.2.0.8-alpha.
9418 - When we can't generate a signing key because OfflineMasterKey is
9419 set, do not imply that we should have been able to load it. Fixes
9420 bug 18133; bugfix on 0.2.7.2-alpha.
9421 - When logging a malformed hostname received through socks4, scrub
9422 it if SafeLogging says we should. Fixes bug 17419; bugfix
9425 o Minor bugfixes (memory safety):
9426 - Avoid freeing an uninitialized pointer when opening a socket fails
9427 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
9428 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
9430 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
9431 18672; bugfix on 0.2.5.1-alpha.
9432 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
9435 o Minor bugfixes (pluggable transports):
9436 - Avoid reporting a spurious error when we decide that we don't need
9437 to terminate a pluggable transport because it has already exited.
9438 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
9440 o Minor bugfixes (pointer arithmetic):
9441 - Fix a bug in memarea_alloc() that could have resulted in remote
9442 heap write access, if Tor had ever passed an unchecked size to
9443 memarea_alloc(). Fortunately, all the sizes we pass to
9444 memarea_alloc() are pre-checked to be less than 128 kilobytes.
9445 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
9448 o Minor bugfixes (private directory):
9449 - Prevent a race condition when creating private directories. Fixes
9450 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
9451 Patch from jsturgix. Found with Flawfinder.
9453 o Minor bugfixes (relays):
9454 - Check that both the ORPort and DirPort (if present) are reachable
9455 before publishing a relay descriptor. Otherwise, relays publish a
9456 descriptor with DirPort 0 when the DirPort reachability test takes
9457 longer than the ORPort reachability test. Fixes bug 18050; bugfix
9458 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
9459 - Resolve some edge cases where we might launch an ORPort
9460 reachability check even when DisableNetwork is set. Noticed while
9461 fixing bug 18616; bugfix on 0.2.3.9-alpha.
9463 o Minor bugfixes (relays, hidden services):
9464 - Refuse connection requests to private OR addresses unless
9465 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
9466 then refuse to send any cells to a private address. Fixes bugs
9467 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
9469 o Minor bugfixes (security, hidden services):
9470 - Prevent hidden services connecting to client-supplied rendezvous
9471 addresses that are reserved as internal or multicast. Fixes bug
9472 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
9474 o Minor bugfixes (statistics):
9475 - Consistently check for overflow in round_*_to_next_multiple_of
9476 functions, and add unit tests with additional and maximal values.
9477 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
9478 - Handle edge cases in the laplace functions: avoid division by
9479 zero, avoid taking the log of zero, and silence clang type
9480 conversion warnings using round and trunc. Add unit tests for edge
9481 cases with maximal values. Fixes part of bug 13192; bugfix
9483 - We now include consensus downloads via IPv6 in our directory-
9484 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
9486 o Minor bugfixes (test networks, IPv6):
9487 - Allow internal IPv6 addresses in descriptors in test networks.
9488 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
9491 o Minor bugfixes (testing):
9492 - Check the full results of SHA256 and SHA512 digests in the unit
9493 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
9494 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
9496 - Fix a small memory leak that would occur when the
9497 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
9498 bugfix on 0.2.5.2-alpha.
9499 - Make unit tests pass on IPv6-only systems, and systems without
9500 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
9501 bugfix on 0.2.7.3-rc. Patch by teor.
9502 - The test for log_heartbeat was incorrectly failing in timezones
9503 with non-integer offsets. Instead of comparing the end of the time
9504 string against a constant, compare it to the output of
9505 format_local_iso_time when given the correct input. Fixes bug
9506 18039; bugfix on 0.2.5.4-alpha.
9507 - We no longer disable assertions in the unit tests when coverage is
9508 enabled. Instead, we require you to say --disable-asserts-in-tests
9509 to the configure script if you need assertions disabled in the
9510 unit tests (for example, if you want to perform branch coverage).
9511 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
9513 o Minor bugfixes (time handling):
9514 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
9515 field. Otherwise, our unit tests crash on Windows. Fixes bug
9516 18977; bugfix on 0.2.2.25-alpha.
9517 - Avoid overflow in tor_timegm when parsing dates in and after 2038
9518 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
9519 0.0.2pre14. Patch by teor.
9521 o Minor bugfixes (tor-gencert):
9522 - Correctly handle the case where an authority operator enters a
9523 passphrase but sends an EOF before sending a newline. Fixes bug
9524 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
9526 o Code simplification and refactoring:
9527 - Clean up a little duplicated code in
9528 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
9530 - Decouple the list of streams waiting to be attached to circuits
9531 from the overall connection list. This change makes it possible to
9532 attach streams quickly while simplifying Tor's callgraph and
9533 avoiding O(N) scans of the entire connection list. Closes
9535 - Extract the more complicated parts of circuit_mark_for_close()
9536 into a new function that we run periodically before circuits are
9537 freed. This change removes more than half of the functions
9538 currently in the "blob". Closes ticket 17218.
9539 - Move logging of redundant policy entries in
9540 policies_parse_exit_policy_internal into its own function. Closes
9541 ticket 17608; patch from "juce".
9542 - Quote all the string interpolations in configure.ac -- even those
9543 which we are pretty sure can't contain spaces. Closes ticket
9544 17744. Patch from zerosion.
9545 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
9546 use them. Closes ticket 17926.
9547 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
9548 inplace, so there's no need to have a separate implementation for
9549 the non-inplace code. Closes ticket 18258. Patch from Malek.
9550 - Simplify return types for some crypto functions that can't
9551 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
9552 - When a direct directory request fails immediately on launch,
9553 instead of relaunching that request from inside the code that
9554 launches it, instead mark the connection for teardown. This change
9555 simplifies Tor's callback and prevents the directory-request
9556 launching code from invoking itself recursively. Closes
9560 - Add a description of the correct use of the '--keygen' command-
9561 line option. Closes ticket 17583; based on text by 's7r'.
9562 - Change build messages to refer to "Fedora" instead of "Fedora
9563 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
9564 Patches from "icanhasaccount" and "cypherpunks".
9565 - Document the contents of the 'datadir/keys' subdirectory in the
9566 manual page. Closes ticket 17621.
9567 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
9568 - Explain actual minima for BandwidthRate. Closes ticket 16382.
9569 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
9570 - Mention torspec URL in the manpage and point the reader to it
9571 whenever we mention a document that belongs in torspce. Fixes
9573 - Stop recommending use of nicknames to identify relays in our
9574 MapAddress documentation. Closes ticket 18312.
9577 - Remove client-side support for connecting to Tor relays running
9578 versions of Tor before 0.2.3.6-alpha. These relays didn't support
9579 the v3 TLS handshake protocol, and are no longer allowed on the
9580 Tor network. Implements the client side of ticket 11150. Based on
9581 patches by Tom van der Woerdt.
9582 - We no longer maintain an internal freelist in memarea.c.
9583 Allocators should be good enough to make this code unnecessary,
9584 and it's doubtful that it ever had any performance benefit.
9587 - Add unit tests to check for common RNG failure modes, such as
9588 returning all zeroes, identical values, or incrementing values
9589 (OpenSSL's rand_predictable feature). Patch by teor.
9590 - Always test both ed25519 backends, so that we can be sure that our
9591 batch-open replacement code works. Part of ticket 16794.
9592 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
9593 portion of ticket 16831.
9594 - Fix several warnings from clang's address sanitizer produced in
9596 - Log more information when the backtrace tests fail. Closes ticket
9597 17892. Patch from "cypherpunks."
9598 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
9599 util_format.c, directory.c, and options_validate.c. Closes tickets
9600 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
9602 - Treat backtrace test failures as expected on FreeBSD until we
9603 solve bug 17808. Closes ticket 18204.
9604 - Unit tests for directory_handle_command_get. Closes ticket 17004.
9605 Patch from Reinaldo de Souza Jr.
9608 Changes in version 0.2.7.6 - 2015-12-10
9609 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
9610 well as a minor bug in hidden service reliability.
9612 o Major bugfixes (guard selection):
9613 - Actually look at the Guard flag when selecting a new directory
9614 guard. When we implemented the directory guard design, we
9615 accidentally started treating all relays as if they have the Guard
9616 flag during guard selection, leading to weaker anonymity and worse
9617 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9620 o Minor features (geoip):
9621 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
9624 o Minor bugfixes (compilation):
9625 - When checking for net/pfvar.h, include netinet/in.h if possible.
9626 This fixes transparent proxy detection on OpenBSD. Fixes bug
9627 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
9628 - Fix a compilation warning with Clang 3.6: Do not check the
9629 presence of an address which can never be NULL. Fixes bug 17781.
9631 o Minor bugfixes (correctness):
9632 - When displaying an IPv6 exit policy, include the mask bits
9633 correctly even when the number is greater than 31. Fixes bug
9634 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
9635 - The wrong list was used when looking up expired intro points in a
9636 rend service object, causing what we think could be reachability
9637 issues for hidden services, and triggering a BUG log. Fixes bug
9638 16702; bugfix on 0.2.7.2-alpha.
9639 - Fix undefined behavior in the tor_cert_checksig function. Fixes
9640 bug 17722; bugfix on 0.2.7.2-alpha.
9643 Changes in version 0.2.7.5 - 2015-11-20
9644 The Tor 0.2.7 release series is dedicated to the memory of Tor user
9645 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
9646 tirelessly to advocate human rights regardless of national borders,
9647 and oppose the encroachments of mass surveillance. He opposed national
9648 exceptionalism, he brought clarity to legal and policy debates, he
9649 understood and predicted the impact of mass surveillance on the world,
9650 and he laid the groundwork for resisting it. While serving on the Tor
9651 Project's board of directors, he brought us his uncompromising focus
9652 on technical excellence in the service of humankind. Caspar was an
9653 inimitable force for good and a wonderful friend. He was kind,
9654 humorous, generous, gallant, and believed we should protect one
9655 another without exception. We honor him here for his ideals, his
9656 efforts, and his accomplishments. Please honor his memory with works
9657 that would make him proud.
9659 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
9661 The 0.2.7 series adds a more secure identity key type for relays,
9662 improves cryptography performance, resolves several longstanding
9663 hidden-service performance issues, improves controller support for
9664 hidden services, and includes small bugfixes and performance
9665 improvements throughout the program. This release series also includes
9666 more tests than before, and significant simplifications to which parts
9667 of Tor invoke which others. For a full list of changes, see below.
9669 o New system requirements:
9670 - Tor no longer includes workarounds to support Libevent versions
9671 before 1.3e. Libevent 2.0 or later is recommended. Closes
9673 - Tor no longer supports copies of OpenSSL that are missing support
9674 for Elliptic Curve Cryptography. (We began using ECC when
9675 available in 0.2.4.8-alpha, for more safe and efficient key
9676 negotiation.) In particular, support for at least one of P256 or
9677 P224 is now required, with manual configuration needed if only
9678 P224 is available. Resolves ticket 16140.
9679 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
9680 on an operating system that has not upgraded to OpenSSL 1.0 or
9681 later, and you compile Tor from source, you will need to install a
9682 more recent OpenSSL to link Tor against.) These versions of
9683 OpenSSL are still supported by the OpenSSL, but the numerous
9684 cryptographic improvements in later OpenSSL releases makes them a
9685 clear choice. Resolves ticket 16034.
9687 o Major features (controller):
9688 - Add the ADD_ONION and DEL_ONION commands that allow the creation
9689 and management of hidden services via the controller. Closes
9691 - New "GETINFO onions/current" and "GETINFO onions/detached"
9692 commands to get information about hidden services created via the
9693 controller. Part of ticket 6411.
9694 - New HSFETCH command to launch a request for a hidden service
9695 descriptor. Closes ticket 14847.
9696 - New HSPOST command to upload a hidden service descriptor. Closes
9697 ticket 3523. Patch by "DonnchaC".
9699 o Major features (Ed25519 identity keys, Proposal 220):
9700 - Add support for offline encrypted Ed25519 master keys. To use this
9701 feature on your tor relay, run "tor --keygen" to make a new master
9702 key (or to make a new signing key if you already have a master
9703 key). Closes ticket 13642.
9704 - All relays now maintain a stronger identity key, using the Ed25519
9705 elliptic curve signature format. This master key is designed so
9706 that it can be kept offline. Relays also generate an online
9707 signing key, and a set of other Ed25519 keys and certificates.
9708 These are all automatically regenerated and rotated as needed.
9709 Implements part of ticket 12498.
9710 - Directory authorities now vote on Ed25519 identity keys along with
9711 RSA1024 keys. Implements part of ticket 12498.
9712 - Directory authorities track which Ed25519 identity keys have been
9713 used with which RSA1024 identity keys, and do not allow them to
9714 vary freely. Implements part of ticket 12498.
9715 - Microdescriptors now include Ed25519 identity keys. Implements
9716 part of ticket 12498.
9717 - Add a --newpass option to allow changing or removing the
9718 passphrase of an encrypted key with tor --keygen. Implements part
9720 - Add a new OfflineMasterKey option to tell Tor never to try loading
9721 or generating a secret Ed25519 identity key. You can use this in
9722 combination with tor --keygen to manage offline and/or encrypted
9723 Ed25519 keys. Implements ticket 16944.
9724 - On receiving a HUP signal, check to see whether the Ed25519
9725 signing key has changed, and reload it if so. Closes ticket 16790.
9726 - Significant usability improvements for Ed25519 key management. Log
9727 messages are better, and the code can recover from far more
9728 failure conditions. Thanks to "s7r" for reporting and diagnosing
9731 o Major features (ECC performance):
9732 - Improve the runtime speed of Ed25519 signature verification by
9733 using Ed25519-donna's batch verification support. Implements
9735 - Improve the speed of Ed25519 operations and Curve25519 keypair
9736 generation when built targeting 32 bit x86 platforms with SSE2
9737 available. Implements ticket 16535.
9738 - Improve the runtime speed of Ed25519 operations by using the
9739 public-domain Ed25519-donna by Andrew M. ("floodyberry").
9740 Implements ticket 16467.
9741 - Improve the runtime speed of the ntor handshake by using an
9742 optimized curve25519 basepoint scalarmult implementation from the
9743 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
9744 ideas by Adam Langley. Implements ticket 9663.
9746 o Major features (Hidden services):
9747 - Hidden services, if using the EntryNodes option, are required to
9748 use more than one EntryNode, in order to avoid a guard discovery
9749 attack. (This would only affect people who had configured hidden
9750 services and manually specified the EntryNodes option with a
9751 single entry-node. The impact was that it would be easy to
9752 remotely identify the guard node used by such a hidden service.
9753 See ticket for more information.) Fixes ticket 14917.
9754 - Add the torrc option HiddenServiceNumIntroductionPoints, to
9755 specify a fixed number of introduction points. Its maximum value
9756 is 10 and default is 3. Using this option can increase a hidden
9757 service's reliability under load, at the cost of making it more
9758 visible that the hidden service is facing extra load. Closes
9760 - Remove the adaptive algorithm for choosing the number of
9761 introduction points, which used to change the number of
9762 introduction points (poorly) depending on the number of
9763 connections the HS sees. Closes ticket 4862.
9765 o Major features (onion key cross-certification):
9766 - Relay descriptors now include signatures of their own identity
9767 keys, made using the TAP and ntor onion keys. These signatures
9768 allow relays to prove ownership of their own onion keys. Because
9769 of this change, microdescriptors will no longer need to include
9770 RSA identity keys. Implements proposal 228; closes ticket 12499.
9772 o Major bugfixes (client-side privacy, also in 0.2.6.9):
9773 - Properly separate out each SOCKSPort when applying stream
9774 isolation. The error occurred because each port's session group
9775 was being overwritten by a default value when the listener
9776 connection was initialized. Fixes bug 16247; bugfix on
9777 0.2.6.3-alpha. Patch by "jojelino".
9779 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
9780 - Stop refusing to store updated hidden service descriptors on a
9781 client. This reverts commit 9407040c59218 (which indeed fixed bug
9782 14219, but introduced a major hidden service reachability
9783 regression detailed in bug 16381). This is a temporary fix since
9784 we can live with the minor issue in bug 14219 (it just results in
9785 some load on the network) but the regression of 16381 is too much
9786 of a setback. First-round fix for bug 16381; bugfix
9789 o Major bugfixes (hidden services):
9790 - Revert commit that made directory authorities assign the HSDir
9791 flag to relays without a DirPort; this was bad because such relays
9792 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
9794 - When cannibalizing a circuit for an introduction point, always
9795 extend to the chosen exit node (creating a 4 hop circuit).
9796 Previously Tor would use the current circuit exit node, which
9797 changed the original choice of introduction point, and could cause
9798 the hidden service to skip excluded introduction points or
9799 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
9802 o Major bugfixes (memory leaks):
9803 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
9804 17398; bugfix on 0.2.6.1-alpha.
9806 o Major bugfixes (open file limit):
9807 - The open file limit wasn't checked before calling
9808 tor_accept_socket_nonblocking(), which would make Tor exceed the
9809 limit. Now, before opening a new socket, Tor validates the open
9810 file limit just before, and if the max has been reached, return an
9811 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
9813 o Major bugfixes (security, correctness):
9814 - Fix an error that could cause us to read 4 bytes before the
9815 beginning of an openssl string. This bug could be used to cause
9816 Tor to crash on systems with unusual malloc implementations, or
9817 systems with unusual hardening installed. Fixes bug 17404; bugfix
9820 o Major bugfixes (stability, also in 0.2.6.10):
9821 - Stop crashing with an assertion failure when parsing certain kinds
9822 of malformed or truncated microdescriptors. Fixes bug 16400;
9823 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
9824 by "cypherpunks_backup".
9825 - Stop random client-side assertion failures that could occur when
9826 connecting to a busy hidden service, or connecting to a hidden
9827 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
9830 o Minor features (client, SOCKS):
9831 - Add GroupWritable and WorldWritable options to unix-socket based
9832 SocksPort and ControlPort options. These options apply to a single
9833 socket, and override {Control,Socks}SocketsGroupWritable. Closes
9835 - Relax the validation done to hostnames in SOCKS5 requests, and
9836 allow a single trailing '.' to cope with clients that pass FQDNs
9837 using that syntax to explicitly indicate that the domain name is
9838 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
9839 - Relax the validation of hostnames in SOCKS5 requests, allowing the
9840 character '_' to appear, in order to cope with domains observed in
9841 the wild that are serving non-RFC compliant records. Resolves
9844 o Minor features (client-side privacy):
9845 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
9846 lifespan when IsolateSOCKSAuth and streams with SOCKS
9847 authentication are attached to the circuit. This allows
9848 applications like TorBrowser to manage circuit lifetime on their
9849 own. Implements feature 15482.
9850 - When logging malformed hostnames from SOCKS5 requests, respect
9851 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
9853 o Minor features (clock-jump tolerance):
9854 - Recover better when our clock jumps back many hours, like might
9855 happen for Tails or Whonix users who start with a very wrong
9856 hardware clock, use Tor to discover a more accurate time, and then
9857 fix their clock. Resolves part of ticket 8766.
9859 o Minor features (command-line interface):
9860 - Make --hash-password imply --hush to prevent unnecessary noise.
9861 Closes ticket 15542. Patch from "cypherpunks".
9862 - Print a warning whenever we find a relative file path being used
9863 as torrc option. Resolves issue 14018.
9865 o Minor features (compilation):
9866 - Give a warning as early as possible when trying to build with an
9867 unsupported OpenSSL version. Closes ticket 16901.
9868 - Use C99 variadic macros when the compiler is not GCC. This avoids
9869 failing compilations on MSVC, and fixes a log-file-based race
9870 condition in our old workarounds. Original patch from Gisle Vanem.
9872 o Minor features (control protocol):
9873 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
9874 the control protocol. Resolves ticket 15358.
9876 o Minor features (controller):
9877 - Add DirAuthority lines for default directory authorities to the
9878 output of the "GETINFO config/defaults" command if not already
9879 present. Implements ticket 14840.
9880 - Controllers can now use "GETINFO hs/client/desc/id/..." to
9881 retrieve items from the client's hidden service descriptor cache.
9882 Closes ticket 14845.
9883 - Implement a new controller command "GETINFO status/fresh-relay-
9884 descs" to fetch a descriptor/extrainfo pair that was generated on
9885 demand just for the controller's use. Implements ticket 14784.
9887 o Minor features (directory authorities):
9888 - Directory authorities no longer vote against the "Fast", "Stable",
9889 and "HSDir" flags just because they were going to vote against
9890 "Running": if the consensus turns out to be that the router was
9891 running, then the authority's vote should count. Patch from Peter
9892 Retzlaff; closes issue 8712.
9894 o Minor features (directory authorities, security, also in 0.2.6.9):
9895 - The HSDir flag given by authorities now requires the Stable flag.
9896 For the current network, this results in going from 2887 to 2806
9897 HSDirs. Also, it makes it harder for an attacker to launch a sybil
9898 attack by raising the effort for a relay to become Stable to
9899 require at the very least 7 days, while maintaining the 96 hours
9900 uptime requirement for HSDir. Implements ticket 8243.
9902 o Minor features (DoS-resistance):
9903 - Make it harder for attackers to overload hidden services with
9904 introductions, by blocking multiple introduction requests on the
9905 same circuit. Resolves ticket 15515.
9907 o Minor features (geoip):
9908 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
9911 o Minor features (hidden services):
9912 - Add the new options "HiddenServiceMaxStreams" and
9913 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
9914 limit the maximum number of simultaneous streams per circuit, and
9915 optionally tear down the circuit when the limit is exceeded. Part
9917 - Client now uses an introduction point failure cache to know when
9918 to fetch or keep a descriptor in their cache. Previously, failures
9919 were recorded implicitly, but not explicitly remembered. Closes
9921 - Relays need to have the Fast flag to get the HSDir flag. As this
9922 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
9923 drop. This change should make some attacks against the hidden
9924 service directory system harder. Fixes ticket 15963.
9925 - Turn on hidden service statistics collection by setting the torrc
9926 option HiddenServiceStatistics to "1" by default. (This keeps
9927 track only of the fraction of traffic used by hidden services, and
9928 the total number of hidden services in existence.) Closes
9930 - To avoid leaking HS popularity, don't cycle the introduction point
9931 when we've handled a fixed number of INTRODUCE2 cells but instead
9932 cycle it when a random number of introductions is reached, thus
9933 making it more difficult for an attacker to find out the amount of
9934 clients that have used the introduction point for a specific HS.
9935 Closes ticket 15745.
9937 o Minor features (logging):
9938 - Include the Tor version in all LD_BUG log messages, since people
9939 tend to cut and paste those into the bugtracker. Implements
9942 o Minor features (pluggable transports):
9943 - When launching managed pluggable transports on Linux systems,
9944 attempt to have the kernel deliver a SIGTERM on tor exit if the
9945 pluggable transport process is still running. Resolves
9947 - When launching managed pluggable transports, setup a valid open
9948 stdin in the child process that can be used to detect if tor has
9949 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
9950 can be used by implementations to detect this new behavior.
9951 Resolves ticket 15435.
9953 o Minor bugfixes (torrc exit policies):
9954 - In each instance above, usage advice is provided to avoid the
9955 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
9956 16069; bugfix on 0.2.4.7-alpha.
9957 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
9958 produce IPv6 wildcard addresses. Previously they would produce
9959 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
9960 of bug 16069; bugfix on 0.2.4.7-alpha.
9961 - When parsing torrc ExitPolicies, we now issue an info-level
9962 message when expanding an "accept/reject *" line to include both
9963 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
9964 - When parsing torrc ExitPolicies, we now warn for a number of cases
9965 where the user's intent is likely to differ from Tor's actual
9966 behavior. These include: using an IPv4 address with an accept6 or
9967 reject6 line; using "private" on an accept6 or reject6 line; and
9968 including any ExitPolicy lines after accept *:* or reject *:*.
9969 Related to ticket 16069.
9971 o Minor bugfixes (command-line interface):
9972 - When "--quiet" is provided along with "--validate-config", do not
9973 write anything to stdout on success. Fixes bug 14994; bugfix
9975 - When complaining about bad arguments to "--dump-config", use
9977 - Print usage information for --dump-config when it is used without
9978 an argument. Also, fix the error message to use different wording
9979 and add newline at the end. Fixes bug 15541; bugfix
9982 o Minor bugfixes (compilation):
9983 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
9984 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
9985 - Repair compilation with the most recent (unreleased, alpha)
9986 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
9988 o Minor bugfixes (compilation, also in 0.2.6.9):
9989 - Build with --enable-systemd correctly when libsystemd is
9990 installed, but systemd is not. Fixes bug 16164; bugfix on
9991 0.2.6.3-alpha. Patch from Peter Palfrader.
9993 o Minor bugfixes (configuration, unit tests):
9994 - Only add the default fallback directories when the DirAuthorities,
9995 AlternateDirAuthority, and FallbackDir directory config options
9996 are set to their defaults. The default fallback directory list is
9997 currently empty, this fix will only change tor's behavior when it
9998 has default fallback directories. Includes unit tests for
9999 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
10000 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
10002 o Minor bugfixes (controller):
10003 - Add the descriptor ID in each HS_DESC control event. It was
10004 missing, but specified in control-spec.txt. Fixes bug 15881;
10005 bugfix on 0.2.5.2-alpha.
10007 o Minor bugfixes (correctness):
10008 - For correctness, avoid modifying a constant string in
10009 handle_control_postdescriptor. Fixes bug 15546; bugfix
10011 - Remove side-effects from tor_assert() calls. This was harmless,
10012 because we never disable assertions, but it is bad style and
10013 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
10015 - When calling channel_free_list(), avoid calling smartlist_remove()
10016 while inside a FOREACH loop. This partially reverts commit
10017 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
10018 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
10020 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
10021 - Check for failures from crypto_early_init, and refuse to continue.
10022 A previous typo meant that we could keep going with an
10023 uninitialized crypto library, and would have OpenSSL initialize
10024 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
10025 when implementing ticket 4900. Patch by "teor".
10027 o Minor bugfixes (hidden service):
10028 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
10029 a client authorized hidden service. Fixes bug 15823; bugfix
10031 - Remove an extraneous newline character from the end of hidden
10032 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
10034 o Minor bugfixes (Linux seccomp2 sandbox):
10035 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
10036 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
10037 - Allow bridge authorities to run correctly under the seccomp2
10038 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
10039 - Add the "hidserv-stats" filename to our sandbox filter for the
10040 HiddenServiceStatistics option to work properly. Fixes bug 17354;
10041 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
10043 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
10044 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
10045 these when eventfd2() support is missing. Fixes bug 16363; bugfix
10046 on 0.2.6.3-alpha. Patch from "teor".
10048 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
10049 - Allow systemd connections to work with the Linux seccomp2 sandbox
10050 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
10052 - Fix sandboxing to work when running as a relay, by allowing the
10053 renaming of secret_id_key, and allowing the eventfd2 and futex
10054 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
10057 o Minor bugfixes (logging):
10058 - When building Tor under Clang, do not include an extra set of
10059 parentheses in log messages that include function names. Fixes bug
10060 15269; bugfix on every released version of Tor when compiled with
10061 recent enough Clang.
10063 o Minor bugfixes (network):
10064 - When attempting to use fallback technique for network interface
10065 lookup, disregard loopback and multicast addresses since they are
10066 unsuitable for public communications.
10068 o Minor bugfixes (open file limit):
10069 - Fix set_max_file_descriptors() to set by default the max open file
10070 limit to the current limit when setrlimit() fails. Fixes bug
10071 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
10073 o Minor bugfixes (portability):
10074 - Check correctly for Windows socket errors in the workqueue
10075 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
10076 - Try harder to normalize the exit status of the Tor process to the
10077 standard-provided range. Fixes bug 16975; bugfix on every version
10079 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
10080 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
10082 o Minor bugfixes (relay):
10083 - Ensure that worker threads actually exit when a fatal error or
10084 shutdown is indicated. This fix doesn't currently affect the
10085 behavior of Tor, because Tor workers never indicates fatal error
10086 or shutdown except in the unit tests. Fixes bug 16868; bugfix
10088 - Fix a rarely-encountered memory leak when failing to initialize
10089 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
10090 from "cypherpunks".
10091 - Unblock threads before releasing the work queue mutex to ensure
10092 predictable scheduling behavior. Fixes bug 16644; bugfix
10095 o Minor bugfixes (security, exit policies):
10096 - ExitPolicyRejectPrivate now also rejects the relay's published
10097 IPv6 address (if any), and any publicly routable IPv4 or IPv6
10098 addresses on any local interfaces. ticket 17027. Patch by "teor".
10099 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
10101 o Minor bugfixes (statistics):
10102 - Disregard the ConnDirectionStatistics torrc options when Tor is
10103 not a relay since in that mode of operation no sensible data is
10104 being collected and because Tor might run into measurement hiccups
10105 when running as a client for some time, then becoming a relay.
10106 Fixes bug 15604; bugfix on 0.2.2.35.
10108 o Minor bugfixes (systemd):
10109 - Tor's systemd unit file no longer contains extraneous spaces.
10110 These spaces would sometimes confuse tools like deb-systemd-
10111 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
10113 o Minor bugfixes (test networks):
10114 - When self-testing reachability, use ExtendAllowPrivateAddresses to
10115 determine if local/private addresses imply reachability. The
10116 previous fix used TestingTorNetwork, which implies
10117 ExtendAllowPrivateAddresses, but this excluded rare configurations
10118 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
10119 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
10120 issue discovered by CJ Ess.
10122 o Minor bugfixes (tests, also in 0.2.6.9):
10123 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
10124 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
10126 o Code simplification and refactoring:
10127 - Change the function that's called when we need to retry all
10128 downloads so that it only reschedules the downloads to happen
10129 immediately, rather than launching them all at once itself. This
10130 further simplifies Tor's callgraph.
10131 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
10132 to ensure they remain consistent and visible everywhere.
10133 - Move some format-parsing functions out of crypto.c and
10134 crypto_curve25519.c into crypto_format.c and/or util_format.c.
10135 - Move the client-only parts of init_keys() into a separate
10136 function. Closes ticket 16763.
10137 - Move the hacky fallback code out of get_interface_address6() into
10138 separate function and get it covered with unit-tests. Resolves
10140 - Refactor hidden service client-side cache lookup to intelligently
10141 report its various failure cases, and disentangle failure cases
10142 involving a lack of introduction points. Closes ticket 14391.
10143 - Remove some vestigial workarounds for the MSVC6 compiler. We
10144 haven't supported that in ages.
10145 - Remove the unused "nulterminate" argument from buf_pullup().
10146 - Simplify the microdesc_free() implementation so that it no longer
10147 appears (to code analysis tools) to potentially invoke a huge
10148 suite of other microdesc functions.
10149 - Simply the control graph further by deferring the inner body of
10150 directory_all_unreachable() into a callback. Closes ticket 16762.
10151 - The link authentication code has been refactored for better
10152 testability and reliability. It now uses code generated with the
10153 "trunnel" binary encoding generator, to reduce the risk of bugs
10154 due to programmer error. Done as part of ticket 12498.
10155 - Treat the loss of an owning controller as equivalent to a SIGTERM
10156 signal. This removes a tiny amount of duplicated code, and
10157 simplifies our callgraph. Closes ticket 16788.
10158 - Use our own Base64 encoder instead of OpenSSL's, to allow more
10159 control over the output. Part of ticket 15652.
10160 - When generating an event to send to the controller, we no longer
10161 put the event over the network immediately. Instead, we queue
10162 these events, and use a Libevent callback to deliver them. This
10163 change simplifies Tor's callgraph by reducing the number of
10164 functions from which all other Tor functions are reachable. Closes
10166 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
10167 that try to scan or compile every file on Unix won't decide that
10171 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
10172 - Improve the descriptions of statistics-related torrc options in
10173 the manpage to describe rationale and possible uses cases. Fixes
10175 - Improve the layout and formatting of ./configure --help messages.
10176 Closes ticket 15024. Patch from "cypherpunks".
10177 - Include a specific and (hopefully) accurate documentation of the
10178 torrc file's meta-format in doc/torrc_format.txt. This is mainly
10179 of interest to people writing programs to parse or generate torrc
10180 files. This document is not a commitment to long-term
10181 compatibility; some aspects of the current format are a bit
10182 ridiculous. Closes ticket 2325.
10183 - Include the TUNING document in our source tarball. It is referred
10184 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
10186 - Note that HiddenServicePorts can take a unix domain socket. Closes
10188 - Recommend a 40 GB example AccountingMax in torrc.sample rather
10189 than a 4 GB max. Closes ticket 16742.
10190 - Standardize on the term "server descriptor" in the manual page.
10191 Previously, we had used "router descriptor", "server descriptor",
10192 and "relay descriptor" interchangeably. Part of ticket 14987.
10193 - Advise users on how to configure separate IPv4 and IPv6 exit
10194 policies in the manpage and sample torrcs. Related to ticket 16069.
10195 - Fix an error in the manual page and comments for
10196 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
10197 required "ORPort connectivity". While this is true, it is in no
10198 way unique to the HSDir flag. Of all the flags, only HSDirs need a
10199 DirPort configured in order for the authorities to assign that
10200 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
10202 - Fix the usage message of tor-resolve(1) so that it no longer lists
10203 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
10206 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
10207 and always use the internal Base64 decoder. The internal decoder
10208 has been part of tor since 0.2.0.10-alpha, and no one should
10209 be using the OpenSSL one. Part of ticket 15652.
10210 - Remove the 'tor_strclear()' function; use memwipe() instead.
10211 Closes ticket 14922.
10212 - Remove the code that would try to aggressively flush controller
10213 connections while writing to them. This code was introduced in
10214 0.1.2.7-alpha, in order to keep output buffers from exceeding
10215 their limits. But there is no longer a maximum output buffer size,
10216 and flushing data in this way caused some undesirable recursions
10217 in our call graph. Closes ticket 16480.
10218 - The internal pure-C tor-fw-helper tool is now removed from the Tor
10219 distribution, in favor of the pure-Go clone available from
10220 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
10221 used by the C tor-fw-helper are not, in our opinion, very
10222 confidence- inspiring in their secure-programming techniques.
10223 Closes ticket 13338.
10225 o Removed features:
10226 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
10227 fingerprinting we now recommend pluggable transports; for forward-
10228 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
10229 - Remove the HidServDirectoryV2 option. Now all relays offer to
10230 store hidden service descriptors. Related to 16543.
10231 - Remove the VoteOnHidServDirectoriesV2 option, since all
10232 authorities have long set it to 1. Closes ticket 16543.
10233 - Remove the undocumented "--digests" command-line option. It
10234 complicated our build process, caused subtle build issues on
10235 multiple platforms, and is now redundant since we started
10236 including git version identifiers. Closes ticket 14742.
10237 - Tor no longer contains checks for ancient directory cache versions
10238 that didn't know about microdescriptors.
10239 - Tor no longer contains workarounds for stat files generated by
10240 super-old versions of Tor that didn't choose guards sensibly.
10243 - The test-network.sh script now supports performance testing.
10244 Requires corresponding chutney performance testing changes. Patch
10245 by "teor". Closes ticket 14175.
10246 - Add a new set of callgraph analysis scripts that use clang to
10247 produce a list of which Tor functions are reachable from which
10248 other Tor functions. We're planning to use these to help simplify
10249 our code structure by identifying illogical dependencies.
10250 - Add new 'test-full' and 'test-full-online' targets to run all
10251 tests, including integration tests with stem and chutney.
10252 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
10253 by-side in the same parent directory. Closes ticket 16903. Patch
10255 - Document use of coverity, clang static analyzer, and clang dynamic
10256 undefined behavior and address sanitizers in doc/HACKING. Include
10257 detailed usage instructions in the blacklist. Patch by "teor".
10258 Closes ticket 15817.
10259 - Make "bridges+hs" the default test network. This tests almost all
10260 tor functionality during make test-network, while allowing tests
10261 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
10262 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
10263 (chutney). Patches by "teor".
10264 - Make the test-workqueue test work on Windows by initializing the
10265 network before we begin.
10266 - New make target (make test-network-all) to run multiple applicable
10267 chutney test cases. Patch from Teor; closes 16953.
10268 - Now that OpenSSL has its own scrypt implementation, add an unit
10269 test that checks for interoperability between libscrypt_scrypt()
10270 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
10271 and rely on EVP_PBE_scrypt() whenever possible. Resolves
10273 - The link authentication protocol code now has extensive tests.
10274 - The relay descriptor signature testing code now has
10276 - The test_workqueue program now runs faster, and is enabled by
10277 default as a part of "make check".
10278 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
10279 functions in dns.c. Implements a portion of ticket 16831.
10280 - Use environment variables rather than autoconf substitutions to
10281 send variables from the build system to the test scripts. This
10282 change should be easier to maintain, and cause 'make distcheck' to
10283 work better than before. Fixes bug 17148.
10284 - When building Tor with testing coverage enabled, run Chutney tests
10285 (if any) using the 'tor-cov' coverage binary.
10286 - When running test-network or test-stem, check for the absence of
10287 stem/chutney before doing any build operations.
10288 - Add a test to verify that the compiler does not eliminate our
10289 memwipe() implementation. Closes ticket 15377.
10290 - Add make rule `check-changes` to verify the format of changes
10291 files. Closes ticket 15180.
10292 - Add unit tests for control_event_is_interesting(). Add a compile-
10293 time check that the number of events doesn't exceed the capacity
10294 of control_event_t.event_mask. Closes ticket 15431, checks for
10295 bugs similar to 13085. Patch by "teor".
10296 - Command-line argument tests moved to Stem. Resolves ticket 14806.
10297 - Integrate the ntor, backtrace, and zero-length keys tests into the
10298 automake test suite. Closes ticket 15344.
10299 - Remove assertions during builds to determine Tor's test coverage.
10300 We don't want to trigger these even in assertions, so including
10301 them artificially makes our branch coverage look worse than it is.
10302 This patch provides the new test-stem-full and coverage-html-full
10303 configure options. Implements ticket 15400.
10304 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
10305 explicitly manage consensus flags in testing networks. Patch by
10306 "robgjansen", modified by "teor". Implements part of ticket 14882.
10307 - Check for matching value in server response in ntor_ref.py. Fixes
10308 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
10310 - Set the severity correctly when testing
10311 get_interface_addresses_ifaddrs() and
10312 get_interface_addresses_win32(), so that the tests fail gracefully
10313 instead of triggering an assertion. Fixes bug 15759; bugfix on
10314 0.2.6.3-alpha. Reported by Nicolas Derive.
10316 Changes in version 0.2.6.10 - 2015-07-12
10317 Tor version 0.2.6.10 fixes some significant stability and hidden
10318 service client bugs, bulletproofs the cryptography init process, and
10319 fixes a bug when using the sandbox code with some older versions of
10320 Linux. Everyone running an older version, especially an older version
10321 of 0.2.6, should upgrade.
10323 o Major bugfixes (hidden service clients, stability):
10324 - Stop refusing to store updated hidden service descriptors on a
10325 client. This reverts commit 9407040c59218 (which indeed fixed bug
10326 14219, but introduced a major hidden service reachability
10327 regression detailed in bug 16381). This is a temporary fix since
10328 we can live with the minor issue in bug 14219 (it just results in
10329 some load on the network) but the regression of 16381 is too much
10330 of a setback. First-round fix for bug 16381; bugfix
10333 o Major bugfixes (stability):
10334 - Stop crashing with an assertion failure when parsing certain kinds
10335 of malformed or truncated microdescriptors. Fixes bug 16400;
10336 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
10337 by "cypherpunks_backup".
10338 - Stop random client-side assertion failures that could occur when
10339 connecting to a busy hidden service, or connecting to a hidden
10340 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
10343 o Minor features (geoip):
10344 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
10345 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
10347 o Minor bugfixes (crypto error-handling):
10348 - Check for failures from crypto_early_init, and refuse to continue.
10349 A previous typo meant that we could keep going with an
10350 uninitialized crypto library, and would have OpenSSL initialize
10351 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
10352 when implementing ticket 4900. Patch by "teor".
10354 o Minor bugfixes (Linux seccomp2 sandbox):
10355 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
10356 these when eventfd2() support is missing. Fixes bug 16363; bugfix
10357 on 0.2.6.3-alpha. Patch from "teor".
10360 Changes in version 0.2.6.9 - 2015-06-11
10361 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
10362 requirements for receiving an HSDir flag, and addresses some other small
10363 bugs in the systemd and sandbox code. Clients using circuit isolation
10364 should upgrade; all directory authorities should upgrade.
10366 o Major bugfixes (client-side privacy):
10367 - Properly separate out each SOCKSPort when applying stream
10368 isolation. The error occurred because each port's session group was
10369 being overwritten by a default value when the listener connection
10370 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
10373 o Minor feature (directory authorities, security):
10374 - The HSDir flag given by authorities now requires the Stable flag.
10375 For the current network, this results in going from 2887 to 2806
10376 HSDirs. Also, it makes it harder for an attacker to launch a sybil
10377 attack by raising the effort for a relay to become Stable which
10378 takes at the very least 7 days to do so and by keeping the 96
10379 hours uptime requirement for HSDir. Implements ticket 8243.
10381 o Minor bugfixes (compilation):
10382 - Build with --enable-systemd correctly when libsystemd is
10383 installed, but systemd is not. Fixes bug 16164; bugfix on
10384 0.2.6.3-alpha. Patch from Peter Palfrader.
10386 o Minor bugfixes (Linux seccomp2 sandbox):
10387 - Fix sandboxing to work when running as a relaymby renaming of
10388 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
10389 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
10390 - Allow systemd connections to work with the Linux seccomp2 sandbox
10391 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
10394 o Minor bugfixes (tests):
10395 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
10396 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
10399 Changes in version 0.2.6.8 - 2015-05-21
10400 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
10401 fixes an authority-side bug in assigning the HSDir flag. All directory
10402 authorities should upgrade.
10404 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
10405 - Revert commit that made directory authorities assign the HSDir
10406 flag to relays without a DirPort; this was bad because such relays
10407 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
10410 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
10411 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
10412 a client authorized hidden service. Fixes bug 15823; bugfix
10415 o Minor features (geoip):
10416 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
10417 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
10421 Changes in version 0.2.6.7 - 2015-04-06
10422 Tor 0.2.6.7 fixes two security issues that could be used by an
10423 attacker to crash hidden services, or crash clients visiting hidden
10424 services. Hidden services should upgrade as soon as possible; clients
10425 should upgrade whenever packages become available.
10427 This release also contains two simple improvements to make hidden
10428 services a bit less vulnerable to denial-of-service attacks.
10430 o Major bugfixes (security, hidden service):
10431 - Fix an issue that would allow a malicious client to trigger an
10432 assertion failure and halt a hidden service. Fixes bug 15600;
10433 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
10434 - Fix a bug that could cause a client to crash with an assertion
10435 failure when parsing a malformed hidden service descriptor. Fixes
10436 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
10438 o Minor features (DoS-resistance, hidden service):
10439 - Introduction points no longer allow multiple INTRODUCE1 cells to
10440 arrive on the same circuit. This should make it more expensive for
10441 attackers to overwhelm hidden services with introductions.
10442 Resolves ticket 15515.
10443 - Decrease the amount of reattempts that a hidden service performs
10444 when its rendezvous circuits fail. This reduces the computational
10445 cost for running a hidden service under heavy load. Resolves
10449 Changes in version 0.2.5.12 - 2015-04-06
10450 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
10451 could be used by an attacker to crash hidden services, or crash clients
10452 visiting hidden services. Hidden services should upgrade as soon as
10453 possible; clients should upgrade whenever packages become available.
10455 This release also backports a simple improvement to make hidden
10456 services a bit less vulnerable to denial-of-service attacks.
10458 o Major bugfixes (security, hidden service):
10459 - Fix an issue that would allow a malicious client to trigger an
10460 assertion failure and halt a hidden service. Fixes bug 15600;
10461 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
10462 - Fix a bug that could cause a client to crash with an assertion
10463 failure when parsing a malformed hidden service descriptor. Fixes
10464 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
10466 o Minor features (DoS-resistance, hidden service):
10467 - Introduction points no longer allow multiple INTRODUCE1 cells to
10468 arrive on the same circuit. This should make it more expensive for
10469 attackers to overwhelm hidden services with introductions.
10470 Resolves ticket 15515.
10473 Changes in version 0.2.4.27 - 2015-04-06
10474 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
10475 could be used by an attacker to crash hidden services, or crash clients
10476 visiting hidden services. Hidden services should upgrade as soon as
10477 possible; clients should upgrade whenever packages become available.
10479 This release also backports a simple improvement to make hidden
10480 services a bit less vulnerable to denial-of-service attacks.
10482 o Major bugfixes (security, hidden service):
10483 - Fix an issue that would allow a malicious client to trigger an
10484 assertion failure and halt a hidden service. Fixes bug 15600;
10485 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
10486 - Fix a bug that could cause a client to crash with an assertion
10487 failure when parsing a malformed hidden service descriptor. Fixes
10488 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
10490 o Minor features (DoS-resistance, hidden service):
10491 - Introduction points no longer allow multiple INTRODUCE1 cells to
10492 arrive on the same circuit. This should make it more expensive for
10493 attackers to overwhelm hidden services with introductions.
10494 Resolves ticket 15515.
10497 Changes in version 0.2.6.6 - 2015-03-24
10498 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
10500 It adds numerous safety, security, correctness, and performance
10501 improvements. Client programs can be configured to use more kinds of
10502 sockets, AutomapHosts works better, the multithreading backend is
10503 improved, cell transmission is refactored, test coverage is much
10504 higher, more denial-of-service attacks are handled, guard selection is
10505 improved to handle long-term guards better, pluggable transports
10506 should work a bit better, and some annoying hidden service performance
10507 bugs should be addressed.
10509 o New compiler and system requirements:
10510 - Tor 0.2.6.x requires that your compiler support more of the C99
10511 language standard than before. The 'configure' script now detects
10512 whether your compiler supports C99 mid-block declarations and
10513 designated initializers. If it does not, Tor will not compile.
10515 We may revisit this requirement if it turns out that a significant
10516 number of people need to build Tor with compilers that don't
10517 bother implementing a 15-year-old standard. Closes ticket 13233.
10518 - Tor no longer supports systems without threading support. When we
10519 began working on Tor, there were several systems that didn't have
10520 threads, or where the thread support wasn't able to run the
10521 threads of a single process on multiple CPUs. That no longer
10522 holds: every system where Tor needs to run well now has threading
10523 support. Resolves ticket 12439.
10525 o Deprecated versions and removed support:
10526 - Tor relays older than 0.2.4.18-rc are no longer allowed to
10527 advertise themselves on the network. Closes ticket 13555.
10528 - Tor clients no longer support connecting to hidden services
10529 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
10530 option has been removed. (There shouldn't be any hidden services
10531 running these versions on the network.) Closes ticket 7803.
10533 o Directory authority changes:
10534 - The directory authority Faravahar has a new IP address. This
10535 closes ticket 14487.
10536 - Remove turtles as a directory authority.
10537 - Add longclaw as a new (v3) directory authority. This implements
10538 ticket 13296. This keeps the directory authority count at 9.
10540 o Major features (bridges):
10541 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
10542 transports if they are configured via the "TOR_PT_PROXY"
10543 environment variable. Implements proposal 232. Resolves
10546 o Major features (changed defaults):
10547 - Prevent relay operators from unintentionally running exits: When a
10548 relay is configured as an exit node, we now warn the user unless
10549 the "ExitRelay" option is set to 1. We warn even more loudly if
10550 the relay is configured with the default exit policy, since this
10551 can indicate accidental misconfiguration. Setting "ExitRelay 0"
10552 stops Tor from running as an exit relay. Closes ticket 10067.
10554 o Major features (client performance, hidden services):
10555 - Allow clients to use optimistic data when connecting to a hidden
10556 service, which should remove a round-trip from hidden service
10557 initialization. See proposal 181 for details. Implements
10560 o Major features (directory system):
10561 - Upon receiving an unparseable directory object, if its digest
10562 matches what we expected, then don't try to download it again.
10563 Previously, when we got a descriptor we didn't like, we would keep
10564 trying to download it over and over. Closes ticket 11243.
10565 - When downloading server- or microdescriptors from a directory
10566 server, we no longer launch multiple simultaneous requests to the
10567 same server. This reduces load on the directory servers,
10568 especially when directory guards are in use. Closes ticket 9969.
10569 - When downloading server- or microdescriptors over a tunneled
10570 connection, do not limit the length of our requests to what the
10571 Squid proxy is willing to handle. Part of ticket 9969.
10572 - Authorities can now vote on the correct digests and latest
10573 versions for different software packages. This allows packages
10574 that include Tor to use the Tor authority system as a way to get
10575 notified of updates and their correct digests. Implements proposal
10576 227. Closes ticket 10395.
10578 o Major features (guards):
10579 - Introduce the Guardfraction feature to improves load balancing on
10580 guard nodes. Specifically, it aims to reduce the traffic gap that
10581 guard nodes experience when they first get the Guard flag. This is
10582 a required step if we want to increase the guard lifetime to 9
10583 months or greater. Closes ticket 9321.
10585 o Major features (hidden services):
10586 - Make HS port scanning more difficult by immediately closing the
10587 circuit when a user attempts to connect to a nonexistent port.
10588 Closes ticket 13667.
10589 - Add a HiddenServiceStatistics option that allows Tor relays to
10590 gather and publish statistics about the overall size and volume of
10591 hidden service usage. Specifically, when this option is turned on,
10592 an HSDir will publish an approximate number of hidden services
10593 that have published descriptors to it the past 24 hours. Also, if
10594 a relay has acted as a hidden service rendezvous point, it will
10595 publish the approximate amount of rendezvous cells it has relayed
10596 the past 24 hours. The statistics themselves are obfuscated so
10597 that the exact values cannot be derived. For more details see
10598 proposal 238, "Better hidden service stats from Tor relays". This
10599 feature is currently disabled by default. Implements feature 13192.
10601 o Major features (performance):
10602 - Make the CPU worker implementation more efficient by avoiding the
10603 kernel and lengthening pipelines. The original implementation used
10604 sockets to transfer data from the main thread to the workers, and
10605 didn't allow any thread to be assigned more than a single piece of
10606 work at once. The new implementation avoids communications
10607 overhead by making requests in shared memory, avoiding kernel IO
10608 where possible, and keeping more requests in flight at once.
10609 Implements ticket 9682.
10611 o Major features (relay):
10612 - Raise the minimum acceptable configured bandwidth rate for bridges
10613 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
10614 20 KiB/sec.) Closes ticket 13822.
10615 - Complete revision of the code that relays use to decide which cell
10616 to send next. Formerly, we selected the best circuit to write on
10617 each channel, but we didn't select among channels in any
10618 sophisticated way. Now, we choose the best circuits globally from
10619 among those whose channels are ready to deliver traffic.
10621 This patch implements a new inter-cmux comparison API, a global
10622 high/low watermark mechanism and a global scheduler loop for
10623 transmission prioritization across all channels as well as among
10624 circuits on one channel. This schedule is currently tuned to
10625 (tolerantly) avoid making changes in network performance, but it
10626 should form the basis for major circuit performance increases in
10627 the future. Code by Andrea; tuning by Rob Jansen; implements
10630 o Major features (sample torrc):
10631 - Add a new, infrequently-changed "torrc.minimal". This file is
10632 similar to torrc.sample, but it will change as infrequently as
10633 possible, for the benefit of users whose systems prompt them for
10634 intervention whenever a default configuration file is changed.
10635 Making this change allows us to update torrc.sample to be a more
10636 generally useful "sample torrc".
10638 o Major features (security, unix domain sockets):
10639 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
10640 applications can reach Tor without having to create AF_INET or
10641 AF_INET6 sockets, meaning they can completely disable their
10642 ability to make non-Tor network connections. To create a socket of
10643 this type, use "SocksPort unix:/path/to/socket". Implements
10645 - Support mapping hidden service virtual ports to AF_UNIX sockets.
10646 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
10647 Implements ticket 11485.
10649 o Major bugfixes (client, automap):
10650 - Repair automapping with IPv6 addresses. This automapping should
10651 have worked previously, but one piece of debugging code that we
10652 inserted to detect a regression actually caused the regression to
10653 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
10654 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
10657 o Major bugfixes (crash, OSX, security):
10658 - Fix a remote denial-of-service opportunity caused by a bug in
10659 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
10662 o Major bugfixes (directory authorities):
10663 - Do not assign the HSDir flag to relays if they are not Valid, or
10664 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
10666 o Major bugfixes (directory bandwidth performance):
10667 - Don't flush the zlib buffer aggressively when compressing
10668 directory information for clients. This should save about 7% of
10669 the bandwidth currently used for compressed descriptors and
10670 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
10672 o Major bugfixes (exit node stability):
10673 - Fix an assertion failure that could occur under high DNS load.
10674 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
10675 diagnosed and fixed by "cypherpunks".
10677 o Major bugfixes (FreeBSD IPFW transparent proxy):
10678 - Fix address detection with FreeBSD transparent proxies, when
10679 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
10682 o Major bugfixes (hidden services):
10683 - When closing an introduction circuit that was opened in parallel
10684 with others, don't mark the introduction point as unreachable.
10685 Previously, the first successful connection to an introduction
10686 point would make the other introduction points get marked as
10687 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
10689 o Major bugfixes (Linux seccomp2 sandbox):
10690 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
10691 crash during attempts to call wait4. Fixes bug 15088; bugfix on
10692 0.2.5.1-alpha. Patch from "sanic".
10694 o Major bugfixes (mixed relay-client operation):
10695 - When running as a relay and client at the same time (not
10696 recommended), if we decide not to use a new guard because we want
10697 to retry older guards, only close the locally-originating circuits
10698 passing through that guard. Previously we would close all the
10699 circuits through that guard. Fixes bug 9819; bugfix on
10700 0.2.1.1-alpha. Reported by "skruffy".
10702 o Major bugfixes (pluggable transports):
10703 - Initialize the extended OR Port authentication cookie before
10704 launching pluggable transports. This prevents a race condition
10705 that occurred when server-side pluggable transports would cache the
10706 authentication cookie before it has been (re)generated. Fixes bug
10707 15240; bugfix on 0.2.5.1-alpha.
10709 o Major bugfixes (relay, stability, possible security):
10710 - Fix a bug that could lead to a relay crashing with an assertion
10711 failure if a buffer of exactly the wrong layout is passed to
10712 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
10713 0.2.0.10-alpha. Patch from "cypherpunks".
10714 - Do not assert if the 'data' pointer on a buffer is advanced to the
10715 very end of the buffer; log a BUG message instead. Only assert if
10716 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
10718 o Minor features (build):
10719 - New --disable-system-torrc compile-time option to prevent Tor from
10720 looking for the system-wide torrc or torrc-defaults files.
10721 Resolves ticket 13037.
10723 o Minor features (client):
10724 - Clients are now willing to send optimistic data (before they
10725 receive a 'connected' cell) to relays of any version. (Relays
10726 without support for optimistic data are no longer supported on the
10727 Tor network.) Resolves ticket 13153.
10729 o Minor features (client):
10730 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
10731 is enabled, reject requests with IP addresses as hostnames.
10732 Resolves ticket 13315.
10734 o Minor features (controller):
10735 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
10736 write an unscheduled heartbeat message to the log. Implements
10738 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
10739 events so controllers can observe circuit isolation inputs. Closes
10741 - ControlPort now supports the unix:/path/to/socket syntax as an
10742 alternative to the ControlSocket option, for consistency with
10743 SocksPort and HiddenServicePort. Closes ticket 14451.
10744 - New "GETINFO bw-event-cache" to get information about recent
10745 bandwidth events. Closes ticket 14128. Useful for controllers to
10746 get recent bandwidth history after the fix for ticket 13988.
10747 - Messages about problems in the bootstrap process now include
10748 information about the server we were trying to connect to when we
10749 noticed the problem. Closes ticket 15006.
10751 o Minor features (Denial of service resistance):
10752 - Count the total number of bytes used storing hidden service
10753 descriptors against the value of MaxMemInQueues. If we're low on
10754 memory, and more than 20% of our memory is used holding hidden
10755 service descriptors, free them until no more than 10% of our
10756 memory holds hidden service descriptors. Free the least recently
10757 fetched descriptors first. Resolves ticket 13806.
10758 - When we have recently been under memory pressure (over 3/4 of
10759 MaxMemInQueues is allocated), then allocate smaller zlib objects
10760 for small requests. Closes ticket 11791.
10762 o Minor features (directory authorities):
10763 - Don't list relays with a bandwidth estimate of 0 in the consensus.
10764 Implements a feature proposed during discussion of bug 13000.
10765 - In tor-gencert, report an error if the user provides the same
10766 argument more than once.
10767 - If a directory authority can't find a best consensus method in the
10768 votes that it holds, it now falls back to its favorite consensus
10769 method. Previously, it fell back to method 1. Neither of these is
10770 likely to get enough signatures, but "fall back to favorite"
10771 doesn't require us to maintain support an obsolete consensus
10772 method. Implements part of proposal 215.
10774 o Minor features (geoip):
10775 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
10776 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
10779 o Minor features (guard nodes):
10780 - Reduce the time delay before saving guard status to disk from 10
10781 minutes to 30 seconds (or from one hour to 10 minutes if
10782 AvoidDiskWrites is set). Closes ticket 12485.
10784 o Minor features (heartbeat):
10785 - On relays, report how many connections we negotiated using each
10786 version of the Tor link protocols. This information will let us
10787 know if removing support for very old versions of the Tor
10788 protocols is harming the network. Closes ticket 15212.
10790 o Minor features (hidden service):
10791 - Make Sybil attacks against hidden services harder by changing the
10792 minimum time required to get the HSDir flag from 25 hours up to 96
10793 hours. Addresses ticket 14149.
10794 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
10795 services to disable the anti-scanning feature introduced in
10796 0.2.6.2-alpha. With this option not set, a connection to an
10797 unlisted port closes the circuit. With this option set, only a
10798 RELAY_DONE cell is sent. Closes ticket 14084.
10799 - When re-enabling the network, don't try to build introduction
10800 circuits until we have successfully built a circuit. This makes
10801 hidden services come up faster when the network is re-enabled.
10802 Patch from "akwizgran". Closes ticket 13447.
10803 - When we fail to retrieve a hidden service descriptor, send the
10804 controller an "HS_DESC FAILED" controller event. Implements
10806 - New HiddenServiceDirGroupReadable option to cause hidden service
10807 directories and hostname files to be created group-readable. Patch
10808 from "anon", David Stainton, and "meejah". Closes ticket 11291.
10810 o Minor features (interface):
10811 - Implement "-f -" command-line option to read torrc configuration
10812 from standard input, if you don't want to store the torrc file in
10813 the file system. Implements feature 13865.
10815 o Minor features (logging):
10816 - Add a count of unique clients to the bridge heartbeat message.
10817 Resolves ticket 6852.
10818 - Suppress "router info incompatible with extra info" message when
10819 reading extrainfo documents from cache. (This message got loud
10820 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
10822 - Elevate hidden service authorized-client message from DEBUG to
10823 INFO. Closes ticket 14015.
10824 - On Unix-like systems, you can now use named pipes as the target of
10825 the Log option, and other options that try to append to files.
10826 Closes ticket 12061. Patch from "carlo von lynX".
10827 - When opening a log file at startup, send it every log message that
10828 we generated between startup and opening it. Previously, log
10829 messages that were generated before opening the log file were only
10830 logged to stdout. Closes ticket 6938.
10831 - Add a TruncateLogFile option to overwrite logs instead of
10832 appending to them. Closes ticket 5583.
10833 - Quiet some log messages in the heartbeat and at startup. Closes
10836 o Minor features (portability, Solaris):
10837 - Threads are no longer disabled by default on Solaris; we believe
10838 that the versions of Solaris with broken threading support are all
10839 obsolete by now. Resolves ticket 9495.
10841 o Minor features (relay):
10842 - Re-check our address after we detect a changed IP address from
10843 getsockname(). This ensures that the controller command "GETINFO
10844 address" will report the correct value. Resolves ticket 11582.
10846 - A new AccountingRule option lets Relays set whether they'd like
10847 AccountingMax to be applied separately to inbound and outbound
10848 traffic, or applied to the sum of inbound and outbound traffic.
10849 Resolves ticket 961. Patch by "chobe".
10850 - When identity keypair is generated for first time, log a
10851 congratulatory message that links to the new relay lifecycle
10852 document. Implements feature 10427.
10854 o Minor features (security, memory wiping):
10855 - Ensure we securely wipe keys from memory after
10856 crypto_digest_get_digest and init_curve25519_keypair_from_file
10857 have finished using them. Resolves ticket 13477.
10859 o Minor features (security, out-of-memory handling):
10860 - When handling an out-of-memory condition, allocate less memory for
10861 temporary data structures. Fixes issue 10115.
10862 - When handling an out-of-memory condition, consider more types of
10863 buffers, including those on directory connections, and zlib
10864 buffers. Resolves ticket 11792.
10866 o Minor features (stability):
10867 - Add assertions in our hash-table iteration code to check for
10868 corrupted values that could cause infinite loops. Closes
10871 o Minor features (systemd):
10872 - Various improvements and modernizations in systemd hardening
10873 support. Closes ticket 13805. Patch from Craig Andrews.
10874 - Where supported, when running with systemd, report successful
10875 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
10876 - When running with systemd, support systemd watchdog messages. Part
10877 of ticket 11016. Patch by Michael Scherer.
10879 o Minor features (testing networks):
10880 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
10881 the "Exit" flag regardless of their uptime, bandwidth, or exit
10882 policy. TestingTorNetwork must be set for this option to have any
10883 effect. Previously, authorities would take up to 35 minutes to
10884 give nodes the Exit flag in a test network. Partially implements
10886 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
10887 and the default on a testing network to 2 minutes. Drop the
10888 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
10889 keep the default on a testing network at 30 seconds. This reduces
10890 HS bootstrap time to around 25 seconds. Also, change the default
10891 time in test-network.sh to match. Closes ticket 13401. Patch
10893 - Create TestingDirAuthVoteHSDir to correspond to
10894 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
10895 HSDir flag for the listed relays regardless of uptime or ORPort
10896 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
10897 Partial implementation for ticket 14067. Patch by "teor".
10899 o Minor features (tor2web mode):
10900 - Introduce the config option Tor2webRendezvousPoints, which allows
10901 clients in Tor2webMode to select a specific Rendezvous Point to be
10902 used in HS circuits. This might allow better performance for
10903 Tor2Web nodes. Implements ticket 12844.
10905 o Minor features (transparent proxy):
10906 - Update the transparent proxy option checks to allow for both ipfw
10907 and pf on OS X. Closes ticket 14002.
10908 - Use the correct option when using IPv6 with transparent proxy
10909 support on Linux. Resolves 13808. Patch by Francisco Blas
10912 o Minor features (validation):
10913 - Check all date/time values passed to tor_timegm and
10914 parse_rfc1123_time for validity, taking leap years into account.
10915 Improves HTTP header validation. Implemented with bug 13476.
10916 - In correct_tm(), limit the range of values returned by system
10917 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
10918 This means we don't have to deal with negative or too large dates,
10919 even if a clock is wrong. Otherwise we might fail to read a file
10920 written by us which includes such a date. Fixes bug 13476.
10921 - Stop allowing invalid address patterns like "*/24" that contain
10922 both a wildcard address and a bit prefix length. This affects all
10923 our address-range parsing code. Fixes bug 7484; bugfix
10926 o Minor bugfixes (bridge clients):
10927 - When configured to use a bridge without an identity digest (not
10928 recommended), avoid launching an extra channel to it when
10929 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
10931 o Minor bugfixes (bridges):
10932 - When DisableNetwork is set, do not launch pluggable transport
10933 plugins, and if any are running, terminate them. Fixes bug 13213;
10934 bugfix on 0.2.3.6-alpha.
10936 o Minor bugfixes (C correctness):
10937 - Fix several instances of possible integer overflow/underflow/NaN.
10938 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
10940 - In circuit_build_times_calculate_timeout() in circuitstats.c,
10941 avoid dividing by zero in the pareto calculations. This traps
10942 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
10944 - Fix an integer overflow in format_time_interval(). Fixes bug
10945 13393; bugfix on 0.2.0.10-alpha.
10946 - Set the correct day of year value when the system's localtime(_r)
10947 or gmtime(_r) functions fail to set struct tm. Not externally
10948 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
10949 - Avoid unlikely signed integer overflow in tor_timegm on systems
10950 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
10952 o Minor bugfixes (certificate handling):
10953 - If an authority operator accidentally makes a signing certificate
10954 with a future publication time, do not discard its real signing
10955 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
10956 - Remove any old authority certificates that have been superseded
10957 for at least two days. Previously, we would keep superseded
10958 certificates until they expired, if they were published close in
10959 time to the certificate that superseded them. Fixes bug 11454;
10960 bugfix on 0.2.1.8-alpha.
10962 o Minor bugfixes (client):
10963 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
10964 BadExit flag are not considered worthy candidates. Fixes bug
10965 13066; bugfix on 0.1.2.3-alpha.
10966 - Use the consensus schedule for downloading consensuses, and not
10967 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
10968 - Handle unsupported or malformed SOCKS5 requests properly by
10969 responding with the appropriate error message before closing the
10970 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
10972 o Minor bugfixes (client, automapping):
10973 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
10974 no value follows the option. Fixes bug 14142; bugfix on
10975 0.2.4.7-alpha. Patch by "teor".
10976 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
10977 14195; bugfix on 0.1.0.1-rc.
10978 - Prevent changes to other options from removing the wildcard value
10979 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
10981 - Allow MapAddress and AutomapHostsOnResolve to work together when
10982 an address is mapped into another address type (like .onion) that
10983 must be automapped at resolve time. Fixes bug 7555; bugfix
10986 o Minor bugfixes (client, bridges):
10987 - When we are using bridges and we had a network connectivity
10988 problem, only retry connecting to our currently configured
10989 bridges, not all bridges we know about and remember using. Fixes
10990 bug 14216; bugfix on 0.2.2.17-alpha.
10992 o Minor bugfixes (client, DNS):
10993 - Report the correct cached DNS expiration times on SOCKS port or in
10994 DNS replies. Previously, we would report everything as "never
10995 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
10996 - Avoid a small memory leak when we find a cached answer for a
10997 reverse DNS lookup in a client-side DNS cache. (Remember, client-
10998 side DNS caching is off by default, and is not recommended.) Fixes
10999 bug 14259; bugfix on 0.2.0.1-alpha.
11001 o Minor bugfixes (client, IPv6):
11002 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
11003 flag is not set; and not because the NoIPv4Traffic flag was set.
11004 Previously we'd looked at the NoIPv4Traffic flag for both types of
11005 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
11007 o Minor bugfixes (client, microdescriptors):
11008 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
11009 computing which microdescriptors to download. This keeps us from
11010 erroneous download behavior if two microdescriptor digests ever
11011 have the same first 160 bits. Fixes part of bug 13399; bugfix
11013 - Reset a router's status if its microdescriptor digest changes,
11014 even if the first 160 bits remain the same. Fixes part of bug
11015 13399; bugfix on 0.2.3.1-alpha.
11017 o Minor bugfixes (client, torrc):
11018 - Stop modifying the value of our DirReqStatistics torrc option just
11019 because we're not a bridge or relay. This bug was causing Tor
11020 Browser users to write "DirReqStatistics 0" in their torrc files
11021 as if they had chosen to change the config. Fixes bug 4244; bugfix
11023 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
11024 that our options have changed every time we SIGHUP. Fixes bug
11025 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
11027 o Minor bugfixes (compilation):
11028 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
11030 - Silence clang warnings under --enable-expensive-hardening,
11031 including implicit truncation of 64 bit values to 32 bit, const
11032 char assignment to self, tautological compare, and additional
11033 parentheses around equality tests. Fixes bug 13577; bugfix
11035 - Fix a clang warning about checking whether an address in the
11036 middle of a structure is NULL. Fixes bug 14001; bugfix
11038 - The address of an array in the middle of a structure will always
11039 be non-NULL. clang recognises this and complains. Disable the
11040 tautologous and redundant check to silence this warning. Fixes bug
11041 14001; bugfix on 0.2.1.2-alpha.
11042 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
11043 Addresses ticket 14188.
11044 - Build without warnings with the stock OpenSSL srtp.h header, which
11045 has a duplicate declaration of SSL_get_selected_srtp_profile().
11046 Fixes bug 14220; this is OpenSSL's bug, not ours.
11047 - Do not compile any code related to Tor2Web mode when Tor2Web mode
11048 is not enabled at compile time. Previously, this code was included
11049 in a disabled state. See discussion on ticket 12844.
11050 - Allow our configure script to build correctly with autoconf 2.62
11051 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
11052 - Improve the error message from ./configure to make it clear that
11053 when asciidoc has not been found, the user will have to either add
11054 --disable-asciidoc argument or install asciidoc. Resolves
11057 o Minor bugfixes (controller):
11058 - Report "down" in response to the "GETINFO entry-guards" command
11059 when relays are down with an unreachable_since value. Previously,
11060 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
11061 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
11062 14116; bugfix on 0.2.2.9-alpha.
11064 o Minor bugfixes (controller):
11065 - Return an error when the second or later arguments of the
11066 "setevents" controller command are invalid events. Previously we
11067 would return success while silently skipping invalid events. Fixes
11068 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
11070 o Minor bugfixes (directory authority):
11071 - Allow directory authorities to fetch more data from one another if
11072 they find themselves missing lots of votes. Previously, they had
11073 been bumping against the 10 MB queued data limit. Fixes bug 14261;
11074 bugfix on 0.1.2.5-alpha.
11075 - Do not attempt to download extrainfo documents which we will be
11076 unable to validate with a matching server descriptor. Fixes bug
11077 13762; bugfix on 0.2.0.1-alpha.
11078 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
11079 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
11080 - Enlarge the buffer to read bwauth generated files to avoid an
11081 issue when parsing the file in dirserv_read_measured_bandwidths().
11082 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
11083 - When running as a v3 directory authority, advertise that you serve
11084 extra-info documents so that clients who want them can find them
11085 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
11087 o Minor bugfixes (directory system):
11088 - Always believe that v3 directory authorities serve extra-info
11089 documents, whether they advertise "caches-extra-info" or not.
11090 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
11091 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
11092 Previously, directories offering BRIDGE_DIRINFO and some other
11093 flag (i.e. microdescriptors or extrainfo) would be ignored when
11094 looking for bridges. Partially fixes bug 13163; bugfix
11097 o Minor bugfixes (file handling):
11098 - Stop failing when key files are zero-length. Instead, generate new
11099 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
11100 on all versions of Tor. Patch by "teor".
11101 - Stop generating a fresh .old RSA onion key file when the .old file
11102 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
11103 - Avoid overwriting .old key files with empty key files.
11104 - Skip loading zero-length extrainfo store, router store, stats,
11105 state, and key files.
11106 - Avoid crashing when trying to reload a torrc specified as a
11107 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
11110 o Minor bugfixes (hidden services):
11111 - Close the introduction circuit when we have no more usable intro
11112 points, instead of waiting for it to time out. This also ensures
11113 that no follow-up HS descriptor fetch is triggered when the
11114 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
11115 - When fetching a hidden service descriptor for a down service that
11116 was recently up, do not keep refetching until we try the same
11117 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
11118 - Correctly send a controller event when we find that a rendezvous
11119 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
11120 - Pre-check directory permissions for new hidden-services to avoid
11121 at least one case of "Bug: Acting on config options left us in a
11122 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
11123 - When fetching hidden service descriptors, we now check not only
11124 for whether we got the hidden service we had in mind, but also
11125 whether we got the particular descriptors we wanted. This prevents
11126 a class of inefficient but annoying DoS attacks by hidden service
11127 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
11130 o Minor bugfixes (Linux seccomp2 sandbox):
11131 - Make transparent proxy support work along with the seccomp2
11132 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
11133 by Francisco Blas Izquierdo Riera.
11134 - Fix a memory leak in tor-resolve when running with the sandbox
11135 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
11136 - Allow glibc fatal errors to be sent to stderr before Tor exits.
11137 Previously, glibc would try to write them to /dev/tty, and the
11138 sandbox would trap the call and make Tor exit prematurely. Fixes
11139 bug 14759; bugfix on 0.2.5.1-alpha.
11141 o Minor bugfixes (logging):
11142 - Avoid crashing when there are more log domains than entries in
11143 domain_list. Bugfix on 0.2.3.1-alpha.
11144 - Downgrade warnings about RSA signature failures to info log level.
11145 Emit a warning when an extra info document is found incompatible
11146 with a corresponding router descriptor. Fixes bug 9812; bugfix
11148 - Make connection_ap_handshake_attach_circuit() log the circuit ID
11149 correctly. Fixes bug 13701; bugfix on 0.0.6.
11151 o Minor bugfixes (networking):
11152 - Check for orconns and use connection_or_close_for_error() rather
11153 than connection_mark_for_close() directly in the getsockopt()
11154 failure case of connection_handle_write_impl(). Fixes bug 11302;
11155 bugfix on 0.2.4.4-alpha.
11157 o Minor bugfixes (parsing):
11158 - Stop accepting milliseconds (or other junk) at the end of
11159 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
11160 - Support two-number and three-number version numbers correctly, in
11161 case we change the Tor versioning system in the future. Fixes bug
11162 13661; bugfix on 0.0.8pre1.
11164 o Minor bugfixes (portability):
11165 - Fix the ioctl()-based network interface lookup code so that it
11166 will work on systems that have variable-length struct ifreq, for
11168 - Use the correct datatype in the SipHash-2-4 function to prevent
11169 compilers from assuming any sort of alignment. Fixes bug 15436;
11170 bugfix on 0.2.5.3-alpha.
11172 o Minor bugfixes (preventative security, C safety):
11173 - When reading a hexadecimal, base-32, or base-64 encoded value from
11174 a string, always overwrite the whole output buffer. This prevents
11175 some bugs where we would look at (but fortunately, not reveal)
11176 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
11178 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
11179 just the part that's used. This makes it harder for data leak bugs
11180 to occur in the event of other programming failures. Resolves
11183 o Minor bugfixes (relay):
11184 - When generating our family list, remove spaces from around the
11185 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
11186 - If our previous bandwidth estimate was 0 bytes, allow publishing a
11187 new relay descriptor immediately. Fixes bug 13000; bugfix
11190 o Minor bugfixes (shutdown):
11191 - When shutting down, always call event_del() on lingering read or
11192 write events before freeing them. Otherwise, we risk double-frees
11193 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
11196 o Minor bugfixes (small memory leaks):
11197 - Avoid leaking memory when using IPv6 virtual address mappings.
11198 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
11201 o Minor bugfixes (statistics):
11202 - Increase period over which bandwidth observations are aggregated
11203 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
11205 o Minor bugfixes (systemd support):
11206 - Run correctly under systemd with the RunAsDaemon option set. Fixes
11207 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
11208 - Inform the systemd supervisor about more changes in the Tor
11209 process status. Implements part of ticket 14141. Patch from
11212 o Minor bugfixes (testing networks):
11213 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
11214 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
11215 - Stop using the default authorities in networks which provide both
11216 AlternateDirAuthority and AlternateBridgeAuthority. Partially
11217 fixes bug 13163; bugfix on 0.2.0.13-alpha.
11219 o Minor bugfixes (testing networks, fast startup):
11220 - Allow Tor to build circuits using a consensus with no exits. If
11221 the consensus has no exits (typical of a bootstrapping test
11222 network), allow Tor to build circuits once enough descriptors have
11223 been downloaded. This assists in bootstrapping a testing Tor
11224 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
11226 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
11227 header to directory servers. This allows us to obtain consensuses
11228 promptly when the consensus interval is very short. This assists
11229 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
11230 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
11231 - Stop assuming that private addresses are local when checking
11232 reachability in a TestingTorNetwork. Instead, when testing, assume
11233 all OR connections are remote. (This is necessary due to many test
11234 scenarios running all relays on localhost.) This assists in
11235 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
11236 0.1.0.1-rc. Patch by "teor".
11237 - Avoid building exit circuits from a consensus with no exits. Now
11238 thanks to our fix for 13718, we accept a no-exit network as not
11239 wholly lost, but we need to remember not to try to build exit
11240 circuits on it. Closes ticket 13814; patch by "teor".
11241 - Stop requiring exits to have non-zero bandwithcapacity in a
11242 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
11243 ignore exit bandwidthcapacity. This assists in bootstrapping a
11244 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
11245 on 0.2.0.3-alpha. Patch by "teor".
11246 - Add "internal" to some bootstrap statuses when no exits are
11247 available. If the consensus does not contain Exits, Tor will only
11248 build internal circuits. In this case, relevant statuses will
11249 contain the word "internal" as indicated in the Tor control-
11250 spec.txt. When bootstrap completes, Tor will be ready to build
11251 internal circuits. If a future consensus contains Exits, exit
11252 circuits may become available. Fixes part of bug 13718; bugfix on
11253 0.2.4.10-alpha. Patch by "teor".
11254 - Decrease minimum consensus interval to 10 seconds when
11255 TestingTorNetwork is set, or 5 seconds for the first consensus.
11256 Fix assumptions throughout the code that assume larger intervals.
11257 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
11259 - Avoid excluding guards from path building in minimal test
11260 networks, when we're in a test network and excluding guards would
11261 exclude all relays. This typically occurs in incredibly small tor
11262 networks, and those using "TestingAuthVoteGuard *". Fixes part of
11263 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
11265 o Minor bugfixes (testing):
11266 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
11267 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
11268 - Stop spawn test failures due to a race condition between the
11269 SIGCHLD handler updating the process status, and the test reading
11270 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
11271 - Avoid passing an extra backslash when creating a temporary
11272 directory for running the unit tests on Windows. Fixes bug 12392;
11273 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
11275 o Minor bugfixes (TLS):
11276 - Check more thoroughly throughout the TLS code for possible
11277 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
11279 o Minor bugfixes (transparent proxy):
11280 - Use getsockname, not getsockopt, to retrieve the address for a
11281 TPROXY-redirected connection. Fixes bug 13796; bugfix
11284 o Minor bugfixes (windows):
11285 - Remove code to special-case handling of NTE_BAD_KEYSET when
11286 acquiring windows CryptoAPI context. This error can't actually
11287 occur for the parameters we're providing. Fixes bug 10816; bugfix
11290 o Minor bugfixes (zlib):
11291 - Avoid truncating a zlib stream when trying to finalize it with an
11292 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
11294 o Code simplification and refactoring:
11295 - Change the entry_is_live() function to take named bitfield
11296 elements instead of an unnamed list of booleans. Closes
11298 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
11299 Resolves ticket 12205.
11300 - Use calloc and reallocarray functions instead of multiply-
11301 then-malloc. This makes it less likely for us to fall victim to an
11302 integer overflow attack when allocating. Resolves ticket 12855.
11303 - Use the standard macro name SIZE_MAX, instead of our
11305 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
11306 functions which take them as arguments. Replace 0 with NO_DIRINFO
11307 in a function call for clarity. Seeks to prevent future issues
11309 - Avoid 4 null pointer errors under clang static analysis by using
11310 tor_assert() to prove that the pointers aren't null. Fixes
11312 - Rework the API of policies_parse_exit_policy() to use a bitmask to
11313 represent parsing options, instead of a confusing mess of
11314 booleans. Resolves ticket 8197.
11315 - Introduce a helper function to parse ExitPolicy in
11316 or_options_t structure.
11317 - Move fields related to isolating and configuring client ports into
11318 a shared structure. Previously, they were duplicated across
11319 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
11320 to copy them correctly had been the cause of at least one bug in
11321 the past. Closes ticket 8546.
11322 - Refactor the get_interface_addresses_raw() doom-function into
11323 multiple smaller and simpler subfunctions. Cover the resulting
11324 subfunctions with unit-tests. Fixes a significant portion of
11326 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
11327 only for version <= 0.2.2.24 which is now deprecated. Closes
11329 - Remove a test for a long-defunct broken version-one
11331 - Refactor main loop to extract the 'loop' part. This makes it
11332 easier to run Tor under Shadow. Closes ticket 15176.
11333 - Stop using can_complete_circuits as a global variable; access it
11334 with a function instead.
11335 - Avoid using operators directly as macro arguments: this lets us
11336 apply coccinelle transformations to our codebase more directly.
11337 Closes ticket 13172.
11338 - Combine the functions used to parse ClientTransportPlugin and
11339 ServerTransportPlugin into a single function. Closes ticket 6456.
11340 - Add inline functions and convenience macros for inspecting channel
11341 state. Refactor the code to use convenience macros instead of
11342 checking channel state directly. Fixes issue 7356.
11343 - Document all members of was_router_added_t and rename
11344 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
11345 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
11346 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
11347 constant instead of hardcoded value. Fixes issue 13840.
11348 - Refactor our generic strmap and digestmap types into a single
11349 implementation, so that we can add a new digest256map
11353 - Add a doc/TUNING document with tips for handling large numbers of
11354 TCP connections when running busy Tor relay. Update the warning
11355 message to point to this file when running out of sockets
11356 operating system is allowing to use simultaneously. Resolves
11358 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
11359 for writing the OpenBSD-specific tips. Resolves ticket 13702.
11360 - Make the tor-resolve documentation match its help string and its
11361 options. Resolves part of ticket 14325.
11362 - Log a more useful error message from tor-resolve when failing to
11363 look up a hidden service address. Resolves part of ticket 14325.
11364 - Document the bridge-authority-only 'networkstatus-bridges' file.
11365 Closes ticket 13713; patch from "tom".
11366 - Fix typo in PredictedPortsRelevanceTime option description in
11367 manpage. Resolves issue 13707.
11368 - Stop suggesting that users specify relays by nickname: it isn't a
11369 good idea. Also, properly cross-reference how to specify relays in
11370 all parts of manual documenting options that take a list of
11371 relays. Closes ticket 13381.
11372 - Clarify the HiddenServiceDir option description in manpage to make
11373 it clear that relative paths are taken with respect to the current
11374 working directory. Also clarify that this behavior is not
11375 guaranteed to remain indefinitely. Fixes issue 13913.
11377 o Distribution (systemd):
11378 - systemd unit file: only allow tor to write to /var/lib/tor and
11379 /var/log/tor. The rest of the filesystem is accessible for reading
11380 only. Patch by intrigeri; resolves ticket 12751.
11381 - systemd unit file: ensure that the process and all its children
11382 can never gain new privileges. Patch by intrigeri; resolves
11384 - systemd unit file: set up /var/run/tor as writable for the Tor
11385 service. Patch by intrigeri; resolves ticket 13196.
11387 o Downgraded warnings:
11388 - Don't warn when we've attempted to contact a relay using the wrong
11389 ntor onion key. Closes ticket 9635.
11392 - Remove some lingering dead code that once supported mempools.
11393 Mempools were disabled by default in 0.2.5, and removed entirely
11394 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
11397 o Removed features (directory authorities):
11398 - Remove code that prevented authorities from listing Tor relays
11399 affected by CVE-2011-2769 as guards. These relays are already
11400 rejected altogether due to the minimum version requirement of
11401 0.2.3.16-alpha. Closes ticket 13152.
11402 - The "AuthDirRejectUnlisted" option no longer has any effect, as
11403 the fingerprints file (approved-routers) has been deprecated.
11404 - Directory authorities do not support being Naming dirauths anymore.
11405 The "NamingAuthoritativeDir" config option is now obsolete.
11406 - Directory authorities do not support giving out the BadDirectory
11408 - Directory authorities no longer advertise or support consensus
11409 methods 1 through 12 inclusive. These consensus methods were
11410 obsolete and/or insecure: maintaining the ability to support them
11411 served no good purpose. Implements part of proposal 215; closes
11414 o Removed features:
11415 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
11416 longer silently accepted as an alias for "ExitNodes".
11417 - The --enable-mempool and --enable-buf-freelists options, which
11418 were originally created to work around bad malloc implementations,
11419 no longer exist. They were off-by-default in 0.2.5. Closes
11421 - We no longer remind the user about configuration options that have
11422 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
11423 - Remove our old, non-weighted bandwidth-based node selection code.
11424 Previously, we used it as a fallback when we couldn't perform
11425 weighted bandwidth-based node selection. But that would only
11426 happen in the cases where we had no consensus, or when we had a
11427 consensus generated by buggy or ancient directory authorities. In
11428 either case, it's better to use the more modern, better maintained
11429 algorithm, with reasonable defaults for the weights. Closes
11431 - Remove the --disable-curve25519 configure option. Relays and
11432 clients now are required to support curve25519 and the
11434 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
11435 used to be deprecated synonyms for "StrictNodes", are now marked
11436 obsolete. Resolves ticket 12226.
11437 - Clients don't understand the BadDirectory flag in the consensus
11438 anymore, and ignore it.
11440 o Removed platform support:
11441 - We no longer include special code to build on Windows CE; as far
11442 as we know, nobody has used Tor on Windows CE in a very long time.
11443 Closes ticket 11446.
11445 o Testing (test-network.sh):
11446 - Stop using "echo -n", as some shells' built-in echo doesn't
11447 support "-n". Instead, use "/bin/echo -n". Partially fixes
11449 - Stop an apparent test-network hang when used with make -j2. Fixes
11451 - Add a --delay option to test-network.sh, which configures the
11452 delay before the chutney network tests for data transmission.
11453 Partially implements ticket 13161.
11456 - Test that tor does not fail when key files are zero-length. Check
11457 that tor generates new keys, and overwrites the empty key files.
11458 - Test that tor generates new keys when keys are missing
11459 (existing behavior).
11460 - Test that tor does not overwrite key files that already contain
11461 data (existing behavior). Tests bug 13111. Patch by "teor".
11462 - New "make test-stem" target to run stem integration tests.
11463 Requires that the "STEM_SOURCE_DIR" environment variable be set.
11464 Closes ticket 14107.
11465 - Make the test_cmdline_args.py script work correctly on Windows.
11466 Patch from Gisle Vanem.
11467 - Move the slower unit tests into a new "./src/test/test-slow"
11468 binary that can be run independently of the other tests. Closes
11470 - New tests for many parts of channel, relay, and circuitmux
11471 functionality. Code by Andrea; part of 9262.
11472 - New tests for parse_transport_line(). Part of ticket 6456.
11473 - In the unit tests, use chgrp() to change the group of the unit
11474 test temporary directory to the current user, so that the sticky
11475 bit doesn't interfere with tests that check directory groups.
11477 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
11479 - Refactor the function that chooses guard nodes so that it can more
11480 easily be tested; write some tests for it.
11481 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
11482 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
11483 - Create unit tests for format_time_interval(). With bug 13393.
11484 - Add unit tests for tor_timegm signed overflow, tor_timegm and
11485 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
11486 tests (visible) fixes in bug 13476.
11487 - Add a "coverage-html" make target to generate HTML-visualized
11488 coverage results when building with --enable-coverage. (Requires
11489 lcov.) Patch from Kevin Murray.
11490 - Enable the backtrace handler (where supported) when running the
11492 - Revise all unit tests that used the legacy test_* macros to
11493 instead use the recommended tt_* macros. This patch was generated
11494 with coccinelle, to avoid manual errors. Closes ticket 13119.
11496 Changes in version 0.2.5.11 - 2015-03-17
11497 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
11499 It backports several bugfixes from the 0.2.6 branch, including a
11500 couple of medium-level security fixes for relays and exit nodes.
11501 It also updates the list of directory authorities.
11503 o Directory authority changes:
11504 - Remove turtles as a directory authority.
11505 - Add longclaw as a new (v3) directory authority. This implements
11506 ticket 13296. This keeps the directory authority count at 9.
11507 - The directory authority Faravahar has a new IP address. This
11508 closes ticket 14487.
11510 o Major bugfixes (crash, OSX, security):
11511 - Fix a remote denial-of-service opportunity caused by a bug in
11512 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
11515 o Major bugfixes (relay, stability, possible security):
11516 - Fix a bug that could lead to a relay crashing with an assertion
11517 failure if a buffer of exactly the wrong layout was passed to
11518 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
11519 0.2.0.10-alpha. Patch from 'cypherpunks'.
11520 - Do not assert if the 'data' pointer on a buffer is advanced to the
11521 very end of the buffer; log a BUG message instead. Only assert if
11522 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
11524 o Major bugfixes (exit node stability):
11525 - Fix an assertion failure that could occur under high DNS load.
11526 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
11527 diagnosed and fixed by "cypherpunks".
11529 o Major bugfixes (Linux seccomp2 sandbox):
11530 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
11531 crash during attempts to call wait4. Fixes bug 15088; bugfix on
11532 0.2.5.1-alpha. Patch from "sanic".
11534 o Minor features (controller):
11535 - New "GETINFO bw-event-cache" to get information about recent
11536 bandwidth events. Closes ticket 14128. Useful for controllers to
11537 get recent bandwidth history after the fix for ticket 13988.
11539 o Minor features (geoip):
11540 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
11541 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
11544 o Minor bugfixes (client, automapping):
11545 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
11546 no value follows the option. Fixes bug 14142; bugfix on
11547 0.2.4.7-alpha. Patch by "teor".
11548 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
11549 14195; bugfix on 0.1.0.1-rc.
11551 o Minor bugfixes (compilation):
11552 - Build without warnings with the stock OpenSSL srtp.h header, which
11553 has a duplicate declaration of SSL_get_selected_srtp_profile().
11554 Fixes bug 14220; this is OpenSSL's bug, not ours.
11556 o Minor bugfixes (directory authority):
11557 - Allow directory authorities to fetch more data from one another if
11558 they find themselves missing lots of votes. Previously, they had
11559 been bumping against the 10 MB queued data limit. Fixes bug 14261;
11560 bugfix on 0.1.2.5-alpha.
11561 - Enlarge the buffer to read bwauth generated files to avoid an
11562 issue when parsing the file in dirserv_read_measured_bandwidths().
11563 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
11565 o Minor bugfixes (statistics):
11566 - Increase period over which bandwidth observations are aggregated
11567 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
11569 o Minor bugfixes (preventative security, C safety):
11570 - When reading a hexadecimal, base-32, or base-64 encoded value from
11571 a string, always overwrite the whole output buffer. This prevents
11572 some bugs where we would look at (but fortunately, not reveal)
11573 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
11577 Changes in version 0.2.4.26 - 2015-03-17
11578 Tor 0.2.4.26 includes an updated list of directory authorities. It
11579 also backports a couple of stability and security bugfixes from 0.2.5
11582 o Directory authority changes:
11583 - Remove turtles as a directory authority.
11584 - Add longclaw as a new (v3) directory authority. This implements
11585 ticket 13296. This keeps the directory authority count at 9.
11586 - The directory authority Faravahar has a new IP address. This
11587 closes ticket 14487.
11589 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
11590 - Fix an assertion failure that could occur under high DNS load.
11591 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
11592 diagnosed and fixed by "cypherpunks".
11594 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
11595 - Fix a bug that could lead to a relay crashing with an assertion
11596 failure if a buffer of exactly the wrong layout was passed to
11597 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
11598 0.2.0.10-alpha. Patch from 'cypherpunks'.
11599 - Do not assert if the 'data' pointer on a buffer is advanced to the
11600 very end of the buffer; log a BUG message instead. Only assert if
11601 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
11603 o Minor features (geoip):
11604 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
11605 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
11608 Changes in version 0.2.5.10 - 2014-10-24
11609 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
11611 It adds several new security features, including improved
11612 denial-of-service resistance for relays, new compiler hardening
11613 options, and a system-call sandbox for hardened installations on Linux
11614 (requires seccomp2). The controller protocol has several new features,
11615 resolving IPv6 addresses should work better than before, and relays
11616 should be a little more CPU-efficient. We've added support for more
11617 OpenBSD and FreeBSD transparent proxy types. We've improved the build
11618 system and testing infrastructure to allow unit testing of more parts
11619 of the Tor codebase. Finally, we've addressed several nagging pluggable
11620 transport usability issues, and included numerous other small bugfixes
11621 and features mentioned below.
11623 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
11624 have accumulated many known flaws; everyone should upgrade.
11626 o Major features (security):
11627 - The ntor handshake is now on-by-default, no matter what the
11628 directory authorities recommend. Implements ticket 8561.
11629 - Make the "tor-gencert" tool used by directory authority operators
11630 create 2048-bit signing keys by default (rather than 1024-bit, since
11631 1024-bit is uncomfortably small these days). Addresses ticket 10324.
11632 - Warn about attempts to run hidden services and relays in the same
11633 process: that's probably not a good idea. Closes ticket 12908.
11634 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
11635 today support TLS 1.0 or later, so we can safely turn off support
11636 for this old (and insecure) protocol. Fixes bug 13426.
11638 o Major features (relay security, DoS-resistance):
11639 - When deciding whether we have run out of memory and we need to
11640 close circuits, also consider memory allocated in buffers for
11641 streams attached to each circuit.
11643 This change, which extends an anti-DoS feature introduced in
11644 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
11645 better resist more memory-based DoS attacks than before. Since the
11646 MaxMemInCellQueues option now applies to all queues, it is renamed
11647 to MaxMemInQueues. This feature fixes bug 10169.
11648 - Avoid hash-flooding denial-of-service attacks by using the secure
11649 SipHash-2-4 hash function for our hashtables. Without this
11650 feature, an attacker could degrade performance of a targeted
11651 client or server by flooding their data structures with a large
11652 number of entries to be stored at the same hash table position,
11653 thereby slowing down the Tor instance. With this feature, hash
11654 table positions are derived from a randomized cryptographic key,
11655 and an attacker cannot predict which entries will collide. Closes
11657 - If you don't specify MaxMemInQueues yourself, Tor now tries to
11658 pick a good value based on your total system memory. Previously,
11659 the default was always 8 GB. You can still override the default by
11660 setting MaxMemInQueues yourself. Resolves ticket 11396.
11662 o Major features (bridges and pluggable transports):
11663 - Add support for passing arguments to managed pluggable transport
11664 proxies. Implements ticket 3594.
11665 - Bridges now track GeoIP information and the number of their users
11666 even when pluggable transports are in use, and report usage
11667 statistics in their extra-info descriptors. Resolves tickets 4773
11669 - Don't launch pluggable transport proxies if we don't have any
11670 bridges configured that would use them. Now we can list many
11671 pluggable transports, and Tor will dynamically start one when it
11672 hears a bridge address that needs it. Resolves ticket 5018.
11673 - The bridge directory authority now assigns status flags (Stable,
11674 Guard, etc) to bridges based on thresholds calculated over all
11675 Running bridges. Now bridgedb can finally make use of its features
11676 to e.g. include at least one Stable bridge in its answers. Fixes
11679 o Major features (controller):
11680 - Extend ORCONN controller event to include an "ID" parameter,
11681 and add four new controller event types CONN_BW, CIRC_BW,
11682 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
11683 The new events are emitted in private Tor networks only, with the
11684 goal of being able to better track performance and load during
11685 full-network simulations. Implements proposal 218 and ticket 7359.
11687 o Major features (relay performance):
11688 - Speed up server-side lookups of rendezvous and introduction point
11689 circuits by using hashtables instead of linear searches. These
11690 functions previously accounted between 3 and 7% of CPU usage on
11691 some busy relays. Resolves ticket 9841.
11692 - Avoid wasting CPU when extending a circuit over a channel that is
11693 nearly out of circuit IDs. Previously, we would do a linear scan
11694 over possible circuit IDs before finding one or deciding that we
11695 had exhausted our possibilities. Now, we try at most 64 random
11696 circuit IDs before deciding that we probably won't succeed. Fixes
11697 a possible root cause of ticket 11553.
11699 o Major features (seccomp2 sandbox, Linux only):
11700 - Use the seccomp2 syscall filtering facility on Linux to limit
11701 which system calls Tor can invoke. This is an experimental,
11702 Linux-only feature to provide defense-in-depth against unknown
11703 attacks. To try turning it on, set "Sandbox 1" in your torrc
11704 file. Please be ready to report bugs. We hope to add support
11705 for better sandboxing in the future, including more fine-grained
11706 filters, better division of responsibility, and support for more
11707 platforms. This work has been done by Cristian-Matei Toader for
11708 Google Summer of Code. Resolves tickets 11351 and 11465.
11710 o Major features (testing networks):
11711 - Make testing Tor networks bootstrap better: lower directory fetch
11712 retry schedules and maximum interval without directory requests,
11713 and raise maximum download tries. Implements ticket 6752.
11714 - Add make target 'test-network' to run tests on a Chutney network.
11715 Implements ticket 8530.
11717 o Major features (other):
11718 - On some platforms (currently: recent OSX versions, glibc-based
11719 platforms that support the ELF format, and a few other
11720 Unix-like operating systems), Tor can now dump stack traces
11721 when a crash occurs or an assertion fails. By default, traces
11722 are dumped to stderr (if possible) and to any logs that are
11723 reporting errors. Implements ticket 9299.
11725 o Deprecated versions:
11726 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
11727 attention for some while.
11729 o Major bugfixes (security, directory authorities):
11730 - Directory authorities now include a digest of each relay's
11731 identity key as a part of its microdescriptor.
11733 This is a workaround for bug 11743 (reported by "cypherpunks"),
11734 where Tor clients do not support receiving multiple
11735 microdescriptors with the same SHA256 digest in the same
11736 consensus. When clients receive a consensus like this, they only
11737 use one of the relays. Without this fix, a hostile relay could
11738 selectively disable some client use of target relays by
11739 constructing a router descriptor with a different identity and the
11740 same microdescriptor parameters and getting the authorities to
11741 list it in a microdescriptor consensus. This fix prevents an
11742 attacker from causing a microdescriptor collision, because the
11743 router's identity is not forgeable.
11745 o Major bugfixes (openssl bug workaround):
11746 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
11747 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
11748 bug 13471. This is a workaround for an OpenSSL bug.
11750 o Major bugfixes (client):
11751 - Perform circuit cleanup operations even when circuit
11752 construction operations are disabled (because the network is
11753 disabled, or because there isn't enough directory information).
11754 Previously, when we were not building predictive circuits, we
11755 were not closing expired circuits either. Fixes bug 8387; bugfix on
11756 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
11757 became more strict about when we have "enough directory information
11758 to build circuits".
11760 o Major bugfixes (client, pluggable transports):
11761 - When managing pluggable transports, use OS notification facilities
11762 to learn if they have crashed, and don't attempt to kill any
11763 process that has already exited. Fixes bug 8746; bugfix
11766 o Major bugfixes (relay denial of service):
11767 - Instead of writing destroy cells directly to outgoing connection
11768 buffers, queue them and intersperse them with other outgoing cells.
11769 This can prevent a set of resource starvation conditions where too
11770 many pending destroy cells prevent data cells from actually getting
11771 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
11772 bugfix on 0.2.0.1-alpha.
11774 o Major bugfixes (relay):
11775 - Avoid queuing or sending destroy cells for circuit ID zero when we
11776 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
11777 Found and fixed by "cypherpunks".
11778 - Fix ORPort reachability detection on relays running behind a
11779 proxy, by correctly updating the "local" mark on the controlling
11780 channel when changing the address of an or_connection_t after the
11781 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
11782 - Use a direct dirport connection when uploading non-anonymous
11783 descriptors to the directory authorities. Previously, relays would
11784 incorrectly use tunnel connections under a fairly wide variety of
11785 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
11786 - When a circuit accidentally has the same circuit ID for its
11787 forward and reverse direction, correctly detect the direction of
11788 cells using that circuit. Previously, this bug made roughly one
11789 circuit in a million non-functional. Fixes bug 12195; this is a
11790 bugfix on every version of Tor.
11792 o Minor features (security):
11793 - New --enable-expensive-hardening option to enable security
11794 hardening options that consume nontrivial amounts of CPU and
11795 memory. Right now, this includes AddressSanitizer and UbSan, which
11796 are supported in newer versions of GCC and Clang. Closes ticket
11798 - Authorities now assign the Guard flag to the fastest 25% of the
11799 network (it used to be the fastest 50%). Also raise the consensus
11800 weight that guarantees the Guard flag from 250 to 2000. For the
11801 current network, this results in about 1100 guards, down from 2500.
11802 This step paves the way for moving the number of entry guards
11803 down to 1 (proposal 236) while still providing reasonable expected
11804 performance for most users. Implements ticket 12690.
11806 o Minor features (security, memory management):
11807 - Memory allocation tricks (mempools and buffer freelists) are now
11808 disabled by default. You can turn them back on with
11809 --enable-mempools and --enable-buf-freelists respectively. We're
11810 disabling these features because malloc performance is good enough
11811 on most platforms, and a similar feature in OpenSSL exacerbated
11812 exploitation of the Heartbleed attack. Resolves ticket 11476.
11814 o Minor features (bridge client):
11815 - Report a more useful failure message when we can't connect to a
11816 bridge because we don't have the right pluggable transport
11817 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
11819 o Minor features (bridge):
11820 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
11821 cookie file for the ExtORPort g+r by default.
11823 o Minor features (bridges, pluggable transports):
11824 - Bridges now write the SHA1 digest of their identity key
11825 fingerprint (that is, a hash of a hash of their public key) to
11826 notice-level logs, and to a new hashed-fingerprint file. This
11827 information will help bridge operators look up their bridge in
11828 Globe and similar tools. Resolves ticket 10884.
11829 - Improve the message that Tor displays when running as a bridge
11830 using pluggable transports without an Extended ORPort listener.
11831 Also, log the message in the log file too. Resolves ticket 11043.
11832 - Add threshold cutoffs to the networkstatus document created by
11833 the Bridge Authority. Fixes bug 1117.
11834 - On Windows, spawn background processes using the CREATE_NO_WINDOW
11835 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
11836 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
11837 Vidalia set this option for us.) Implements ticket 10297.
11839 o Minor features (build):
11840 - The configure script has a --disable-seccomp option to turn off
11841 support for libseccomp on systems that have it, in case it (or
11842 Tor's use of it) is broken. Resolves ticket 11628.
11843 - Assume that a user using ./configure --host wants to cross-compile,
11844 and give an error if we cannot find a properly named
11845 tool-chain. Add a --disable-tool-name-check option to proceed
11846 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
11847 - If we run ./configure and the compiler recognizes -fstack-protector
11848 but the linker rejects it, warn the user about a potentially missing
11849 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
11850 - Add support for `--library-versions` flag. Implements ticket 6384.
11851 - Return the "unexpected sendme" warnings to a warn severity, but make
11852 them rate limited, to help diagnose ticket 8093.
11853 - Detect a missing asciidoc, and warn the user about it, during
11854 configure rather than at build time. Fixes issue 6506. Patch from
11857 o Minor features (client):
11858 - Add a new option, PredictedPortsRelevanceTime, to control how long
11859 after having received a request to connect to a given port Tor
11860 will try to keep circuits ready in anticipation of future requests
11861 for that port. Patch from "unixninja92"; implements ticket 9176.
11863 o Minor features (config options and command line):
11864 - Add an --allow-missing-torrc commandline option that tells Tor to
11865 run even if the configuration file specified by -f is not available.
11866 Implements ticket 10060.
11867 - Add support for the TPROXY transparent proxying facility on Linux.
11868 See documentation for the new TransProxyType option for more
11869 details. Implementation by "thomo". Closes ticket 10582.
11871 o Minor features (config options):
11872 - Config (torrc) lines now handle fingerprints which are missing
11873 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
11874 - Support a --dump-config option to print some or all of the
11875 configured options. Mainly useful for debugging the command-line
11876 option parsing code. Helps resolve ticket 4647.
11877 - Raise awareness of safer logging: notify user of potentially
11878 unsafe config options, like logging more verbosely than severity
11879 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
11880 - Add a new configuration option TestingV3AuthVotingStartOffset
11881 that bootstraps a network faster by changing the timing for
11882 consensus votes. Addresses ticket 8532.
11883 - Add a new torrc option "ServerTransportOptions" that allows
11884 bridge operators to pass configuration parameters to their
11885 pluggable transports. Resolves ticket 8929.
11886 - The config (torrc) file now accepts bandwidth and space limits in
11887 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
11888 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
11891 o Minor features (controller):
11892 - Make the entire exit policy available from the control port via
11893 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
11895 - Because of the fix for ticket 11396, the real limit for memory
11896 usage may no longer match the configured MaxMemInQueues value. The
11897 real limit is now exposed via GETINFO limits/max-mem-in-queues.
11898 - Add a new "HS_DESC" controller event that reports activities
11899 related to hidden service descriptors. Resolves ticket 8510.
11900 - New "DROPGUARDS" controller command to forget all current entry
11901 guards. Not recommended for ordinary use, since replacing guards
11902 too frequently makes several attacks easier. Resolves ticket 9934;
11904 - Implement the TRANSPORT_LAUNCHED control port event that
11905 notifies controllers about new launched pluggable
11906 transports. Resolves ticket 5609.
11908 o Minor features (diagnostic):
11909 - When logging a warning because of bug 7164, additionally check the
11910 hash table for consistency (as proposed on ticket 11737). This may
11911 help diagnose bug 7164.
11912 - When we log a heartbeat, log how many one-hop circuits we have
11913 that are at least 30 minutes old, and log status information about
11914 a few of them. This is an attempt to track down bug 8387.
11915 - When encountering an unexpected CR while writing text to a file on
11916 Windows, log the name of the file. Should help diagnosing
11918 - Give more specific warnings when a client notices that an onion
11919 handshake has failed. Fixes ticket 9635.
11920 - Add significant new logging code to attempt to diagnose bug 12184,
11921 where relays seem to run out of available circuit IDs.
11922 - Improve the diagnostic log message for bug 8387 even further to
11923 try to improve our odds of figuring out why one-hop directory
11924 circuits sometimes do not get closed.
11925 - Add more log messages to diagnose bug 7164, which causes
11926 intermittent "microdesc_free() called but md was still referenced"
11927 warnings. We now include more information, to figure out why we
11928 might be cleaning a microdescriptor for being too old if it's
11929 still referenced by a live node_t object.
11930 - Log current accounting state (bytes sent and received + remaining
11931 time for the current accounting period) in the relay's heartbeat
11932 message. Implements ticket 5526; patch from Peter Retzlaff.
11934 o Minor features (geoip):
11935 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
11938 o Minor features (interface):
11939 - Generate a warning if any ports are listed in the SocksPolicy,
11940 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
11941 AuthDirBadExit options. (These options only support address
11942 ranges.) Fixes part of ticket 11108.
11944 o Minor features (kernel API usage):
11945 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
11946 sockets in a single system call. Implements ticket 5129.
11948 o Minor features (log messages):
11949 - When ServerTransportPlugin is set on a bridge, Tor can write more
11950 useful statistics about bridge use in its extrainfo descriptors,
11951 but only if the Extended ORPort ("ExtORPort") is set too. Add a
11952 log message to inform the user in this case. Resolves ticket 9651.
11953 - When receiving a new controller connection, log the origin address.
11954 Resolves ticket 9698; patch from "sigpipe".
11955 - When logging OpenSSL engine status at startup, log the status of
11956 more engines. Fixes ticket 10043; patch from Joshua Datko.
11958 o Minor features (log verbosity):
11959 - Demote the message that we give when a flushing connection times
11960 out for too long from NOTICE to INFO. It was usually meaningless.
11961 Resolves ticket 5286.
11962 - Don't log so many notice-level bootstrapping messages at startup
11963 about downloading descriptors. Previously, we'd log a notice
11964 whenever we learned about more routers. Now, we only log a notice
11965 at every 5% of progress. Fixes bug 9963.
11966 - Warn less verbosely when receiving a malformed
11967 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
11969 o Minor features (performance):
11970 - If we're using the pure-C 32-bit curve25519_donna implementation
11971 of curve25519, build it with the -fomit-frame-pointer option to
11972 make it go faster on register-starved hosts. This improves our
11973 handshake performance by about 6% on i386 hosts without nacl.
11974 Closes ticket 8109.
11976 o Minor features (relay):
11977 - If a circuit timed out for at least 3 minutes, check if we have a
11978 new external IP address, and publish a new descriptor with the new
11979 IP address if it changed. Resolves ticket 2454.
11981 o Minor features (testing):
11982 - If Python is installed, "make check" now runs extra tests beyond
11983 the unit test scripts.
11984 - When bootstrapping a test network, sometimes very few relays get
11985 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
11986 specify a set of relays which should be voted Guard regardless of
11987 their uptime or bandwidth. Addresses ticket 9206.
11989 o Minor features (transparent proxy, *BSD):
11990 - Support FreeBSD's ipfw firewall interface for TransPort ports on
11991 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
11992 10267; patch from "yurivict".
11993 - Support OpenBSD's divert-to rules with the pf firewall for
11994 transparent proxy ports. To enable it, set "TransProxyType
11995 pf-divert". This allows Tor to run a TransPort transparent proxy
11996 port on OpenBSD 4.4 or later without root privileges. See the
11997 pf.conf(5) manual page for information on configuring pf to use
11998 divert-to rules. Closes ticket 10896; patch from Dana Koch.
12000 o Minor bugfixes (bridge client):
12001 - Stop accepting bridge lines containing hostnames. Doing so would
12002 cause clients to perform DNS requests on the hostnames, which was
12003 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
12005 o Minor bugfixes (bridges):
12006 - Avoid potential crashes or bad behavior when launching a
12007 server-side managed proxy with ORPort or ExtORPort temporarily
12008 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
12009 - Fix a bug where the first connection works to a bridge that uses a
12010 pluggable transport with client-side parameters, but we don't send
12011 the client-side parameters on subsequent connections. (We don't
12012 use any pluggable transports with client-side parameters yet,
12013 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
12014 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
12016 o Minor bugfixes (build, auxiliary programs):
12017 - Stop preprocessing the "torify" script with autoconf, since
12018 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
12020 - The tor-fw-helper program now follows the standard convention and
12021 exits with status code "0" on success. Fixes bug 9030; bugfix on
12022 0.2.3.1-alpha. Patch by Arlo Breault.
12023 - Corrected ./configure advice for what openssl dev package you should
12024 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
12026 o Minor bugfixes (client):
12027 - Avoid "Tried to open a socket with DisableNetwork set" warnings
12028 when starting a client with bridges configured and DisableNetwork
12029 set. (Tor launcher starts Tor with DisableNetwork set the first
12030 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
12031 - Improve the log message when we can't connect to a hidden service
12032 because all of the hidden service directory nodes hosting its
12033 descriptor are excluded. Improves on our fix for bug 10722, which
12034 was a bugfix on 0.2.0.10-alpha.
12035 - Raise a control port warning when we fail to connect to all of
12036 our bridges. Previously, we didn't inform the controller, and
12037 the bootstrap process would stall. Fixes bug 11069; bugfix on
12039 - Exit immediately when a process-owning controller exits.
12040 Previously, tor relays would wait for a little while after their
12041 controller exited, as if they had gotten an INT signal -- but this
12042 was problematic, since there was no feedback for the user. To do a
12043 clean shutdown, controllers should send an INT signal and give Tor
12044 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
12045 - Stop attempting to connect to bridges before our pluggable
12046 transports are configured (harmless but resulted in some erroneous
12047 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
12048 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
12049 generating incorrect SOCKS5 responses, and confusing client
12050 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
12052 o Minor bugfixes (client, DNSPort):
12053 - When using DNSPort, try to respond to AAAA requests with AAAA
12054 answers. Previously, we hadn't looked at the request type when
12055 deciding which answer type to prefer. Fixes bug 10468; bugfix on
12057 - When receiving a DNS query for an unsupported record type, reply
12058 with no answer rather than with a NOTIMPL error. This behavior
12059 isn't correct either, but it will break fewer client programs, we
12060 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
12063 o Minor bugfixes (client, logging during bootstrap):
12064 - Only report the first fatal bootstrap error on a given OR
12065 connection. This stops us from telling the controller bogus error
12066 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
12067 - Avoid generating spurious warnings when starting with
12068 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
12071 o Minor bugfixes (closing OR connections):
12072 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
12073 check if it's an or_connection_t and correctly call
12074 connection_or_close_for_error() rather than
12075 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
12077 - When closing all connections on setting DisableNetwork to 1, use
12078 connection_or_close_normally() rather than closing OR connections
12079 out from under the channel layer. Fixes bug 11306; bugfix on
12082 o Minor bugfixes (code correctness):
12083 - Previously we used two temporary files when writing descriptors to
12084 disk; now we only use one. Fixes bug 1376.
12085 - Remove an erroneous (but impossible and thus harmless) pointer
12086 comparison that would have allowed compilers to skip a bounds
12087 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
12088 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
12089 - Fix an always-true assertion in pluggable transports code so it
12090 actually checks what it was trying to check. Fixes bug 10046;
12091 bugfix on 0.2.3.9-alpha. Found by "dcb".
12093 o Minor bugfixes (command line):
12094 - Use a single command-line parser for parsing torrc options on the
12095 command line and for finding special command-line options to avoid
12096 inconsistent behavior for torrc option arguments that have the same
12097 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
12099 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
12100 9573; bugfix on 0.0.9pre5.
12102 o Minor bugfixes (compilation):
12103 - Compile correctly with builds and forks of OpenSSL (such as
12104 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
12105 0.2.1.1-alpha. Patch from "dhill".
12106 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
12107 turned off (that is, without support for v2 link handshakes). Fixes
12108 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
12109 - In routerlist_assert_ok(), don't take the address of a
12110 routerinfo's cache_info member unless that routerinfo is non-NULL.
12111 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
12112 - Fix a large number of false positive warnings from the clang
12113 analyzer static analysis tool. This should make real warnings
12114 easier for clang analyzer to find. Patch from "teor". Closes
12116 - Resolve GCC complaints on OpenBSD about discarding constness in
12117 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
12118 on 0.1.1.23. Patch from Dana Koch.
12119 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
12120 treatment of long and time_t as comparable types. Fixes part of
12121 bug 11633. Patch from Dana Koch.
12122 - When deciding whether to build the 64-bit curve25519
12123 implementation, detect platforms where we can compile 128-bit
12124 arithmetic but cannot link it. Fixes bug 11729; bugfix on
12125 0.2.4.8-alpha. Patch from "conradev".
12126 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
12127 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
12128 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
12130 - Build and run correctly on systems like OpenBSD-current that have
12131 patched OpenSSL to remove get_cipher_by_char and/or its
12132 implementations. Fixes issue 13325.
12134 o Minor bugfixes (controller and command-line):
12135 - If changing a config option via "setconf" fails in a recoverable
12136 way, we used to nonetheless write our new control ports to the
12137 file described by the "ControlPortWriteToFile" option. Now we only
12138 write out that file if we successfully switch to the new config
12139 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
12141 o Minor bugfixes (directory server):
12142 - No longer accept malformed http headers when parsing urls from
12143 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
12144 bugfix on 0.0.6pre1.
12145 - When sending a compressed set of descriptors or microdescriptors,
12146 make sure to finalize the zlib stream. Previously, we would write
12147 all the compressed data, but if the last descriptor we wanted to
12148 send was missing or too old, we would not mark the stream as
12149 finished. This caused problems for decompression tools. Fixes bug
12150 11648; bugfix on 0.1.1.23.
12152 o Minor bugfixes (hidden service):
12153 - Only retry attempts to connect to a chosen rendezvous point 8
12154 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
12156 o Minor bugfixes (interface):
12157 - Reject relative control socket paths and emit a warning. Previously,
12158 single-component control socket paths would be rejected, but Tor
12159 would not log why it could not validate the config. Fixes bug 9258;
12160 bugfix on 0.2.3.16-alpha.
12162 o Minor bugfixes (log messages):
12163 - Fix a bug where clients using bridges would report themselves
12164 as 50% bootstrapped even without a live consensus document.
12165 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
12166 - Suppress a warning where, if there's only one directory authority
12167 in the network, we would complain that votes and signatures cannot
12168 be uploaded to other directory authorities. Fixes bug 10842;
12169 bugfix on 0.2.2.26-beta.
12170 - Report bootstrapping progress correctly when we're downloading
12171 microdescriptors. We had updated our "do we have enough microdescs
12172 to begin building circuits?" logic most recently in 0.2.4.10-alpha
12173 (see bug 5956), but we left the bootstrap status event logic at
12174 "how far through getting 1/4 of them are we?" Fixes bug 9958;
12175 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
12177 o Minor bugfixes (logging):
12178 - Downgrade "Unexpected onionskin length after decryption" warning
12179 to a protocol-warn, since there's nothing relay operators can do
12180 about a client that sends them a malformed create cell. Resolves
12181 bug 12996; bugfix on 0.0.6rc1.
12182 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
12183 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
12184 - When logging information about an EXTEND2 or EXTENDED2 cell, log
12185 their names correctly. Fixes part of bug 12700; bugfix
12187 - When logging information about a relay cell whose command we don't
12188 recognize, log its command as an integer. Fixes part of bug 12700;
12189 bugfix on 0.2.1.10-alpha.
12190 - Escape all strings from the directory connection before logging
12191 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
12192 - Squelch a spurious LD_BUG message "No origin circuit for
12193 successful SOCKS stream" in certain hidden service failure cases;
12195 - Downgrade the severity of the 'unexpected sendme cell from client'
12196 from 'warn' to 'protocol warning'. Closes ticket 8093.
12198 o Minor bugfixes (misc code correctness):
12199 - In munge_extrainfo_into_routerinfo(), check the return value of
12200 memchr(). This would have been a serious issue if we ever passed
12201 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
12203 - On the chance that somebody manages to build Tor on a
12204 platform where time_t is unsigned, correct the way that
12205 microdesc_add_to_cache() handles negative time arguments.
12206 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
12207 - Fix various instances of undefined behavior in channeltls.c,
12208 tor_memmem(), and eventdns.c that would cause us to construct
12209 pointers to memory outside an allocated object. (These invalid
12210 pointers were not accessed, but C does not even allow them to
12211 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
12212 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
12213 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
12214 fix some miscellaneous errors in our tests and codebase. Fixes bug
12215 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
12216 - Always check return values for unlink, munmap, UnmapViewOfFile;
12217 check strftime return values more often. In some cases all we can
12218 do is report a warning, but this may help prevent deeper bugs from
12219 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
12221 - Fix numerous warnings from the clang "scan-build" static analyzer.
12222 Some of these are programming style issues; some of them are false
12223 positives that indicated awkward code; some are undefined behavior
12224 cases related to constructing (but not using) invalid pointers;
12225 some are assumptions about API behavior; some are (harmlessly)
12226 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
12227 correct; and one or two are genuine bugs that weren't reachable
12228 from the rest of the program. Fixes bug 8793; bugfixes on many,
12231 o Minor bugfixes (node selection):
12232 - If ExcludeNodes is set, consider non-excluded hidden service
12233 directory servers before excluded ones. Do not consider excluded
12234 hidden service directory servers at all if StrictNodes is
12235 set. (Previously, we would sometimes decide to connect to those
12236 servers, and then realize before we initiated a connection that
12237 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
12238 Reported by "mr-4".
12239 - If we set the ExitNodes option but it doesn't include any nodes
12240 that have the Exit flag, we would choose not to bootstrap. Now we
12241 bootstrap so long as ExitNodes includes nodes which can exit to
12242 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
12244 o Minor bugfixes (performance):
12245 - Avoid a bug where every successful connection made us recompute
12246 the flag telling us whether we have sufficient information to
12247 build circuits. Previously, we would forget our cached value
12248 whenever we successfully opened a channel (or marked a router as
12249 running or not running for any other reason), regardless of
12250 whether we had previously believed the router to be running. This
12251 forced us to run an expensive update operation far too often.
12252 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
12253 - Avoid using tor_memeq() for checking relay cell integrity. This
12254 removes a possible performance bottleneck. Fixes part of bug
12255 12169; bugfix on 0.2.1.31.
12257 o Minor bugfixes (platform-specific):
12258 - When dumping a malformed directory object to disk, save it in
12259 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
12261 - Don't report failures from make_socket_reuseable() on incoming
12262 sockets on OSX: this can happen when incoming connections close
12263 early. Fixes bug 10081.
12265 o Minor bugfixes (pluggable transports):
12266 - Avoid another 60-second delay when starting Tor in a pluggable-
12267 transport-using configuration when we already have cached
12268 descriptors for our bridges. Fixes bug 11965; bugfix
12271 o Minor bugfixes (protocol correctness):
12272 - When receiving a VERSIONS cell with an odd number of bytes, close
12273 the connection immediately since the cell is malformed. Fixes bug
12274 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
12277 o Minor bugfixes (relay, other):
12278 - We now drop CREATE cells for already-existent circuit IDs and for
12279 zero-valued circuit IDs, regardless of other factors that might
12280 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
12282 - When rejecting DATA cells for stream_id zero, still count them
12283 against the circuit's deliver window so that we don't fail to send
12284 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
12286 o Minor bugfixes (relay, threading):
12287 - Check return code on spawn_func() in cpuworker code, so that we
12288 don't think we've spawned a nonworking cpuworker and write junk to
12289 it forever. Fix related to bug 4345; bugfix on all released Tor
12290 versions. Found by "skruffy".
12291 - Use a pthread_attr to make sure that spawn_func() cannot return an
12292 error while at the same time launching a thread. Fix related to
12293 bug 4345; bugfix on all released Tor versions. Reported
12296 o Minor bugfixes (relays and bridges):
12297 - Avoid crashing on a malformed resolv.conf file when running a
12298 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
12299 - Non-exit relays no longer launch mock DNS requests to check for
12300 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
12301 non-exit relays stopped servicing DNS requests. Fixes bug 965;
12302 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
12303 - Bridges now report complete directory request statistics. Related
12304 to bug 5824; bugfix on 0.2.2.1-alpha.
12305 - Bridges now never collect statistics that were designed for
12306 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
12308 o Minor bugfixes (testing):
12309 - Fix all valgrind warnings produced by the unit tests. There were
12310 over a thousand memory leak warnings previously, mostly produced
12311 by forgetting to free things in the unit test code. Fixes bug
12312 11618, bugfixes on many versions of Tor.
12314 o Minor bugfixes (tor-fw-helper):
12315 - Give a correct log message when tor-fw-helper fails to launch.
12316 (Previously, we would say something like "tor-fw-helper sent us a
12317 string we could not parse".) Fixes bug 9781; bugfix
12320 o Minor bugfixes (trivial memory leaks):
12321 - Fix a small memory leak when signing a directory object. Fixes bug
12322 11275; bugfix on 0.2.4.13-alpha.
12323 - Resolve some memory leaks found by coverity in the unit tests, on
12324 exit in tor-gencert, and on a failure to compute digests for our
12325 own keys when generating a v3 networkstatus vote. These leaks
12326 should never have affected anyone in practice.
12328 o Code simplification and refactoring:
12329 - Remove some old fallback code designed to keep Tor clients working
12330 in a network with only two working relays. Elsewhere in the code we
12331 have long since stopped supporting such networks, so there wasn't
12332 much point in keeping it around. Addresses ticket 9926.
12333 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
12334 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
12335 - Extract the common duplicated code for creating a subdirectory
12336 of the data directory and writing to a file in it. Fixes ticket
12337 4282; patch from Peter Retzlaff.
12338 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
12339 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
12340 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
12341 - Add a set of accessor functions for the circuit timeout data
12342 structure. Fixes ticket 6153; patch from "piet".
12343 - Clean up exit paths from connection_listener_new(). Closes ticket
12344 8789. Patch from Arlo Breault.
12345 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
12346 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
12347 - Use a doubly-linked list to implement the global circuit list.
12348 Resolves ticket 9108. Patch from Marek Majkowski.
12349 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
12350 - Remove constants and tests for PKCS1 padding; it's insecure and
12351 shouldn't be used for anything new. Fixes bug 8792; patch
12353 - Remove instances of strcpy() from the unit tests. They weren't
12354 hurting anything, since they were only in the unit tests, but it's
12355 embarrassing to have strcpy() in the code at all, and some analysis
12356 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
12357 0.2.3.8-alpha. Patch from Arlo Breault.
12358 - Remove is_internal_IP() function. Resolves ticket 4645.
12359 - Remove unused function circuit_dump_by_chan from circuitlist.c.
12360 Closes issue 9107; patch from "marek".
12361 - Change our use of the ENUM_BF macro to avoid declarations that
12363 - Get rid of router->address, since in all cases it was just the
12364 string representation of router->addr. Resolves ticket 5528.
12367 - Adjust the URLs in the README to refer to the new locations of
12368 several documents on the website. Fixes bug 12830. Patch from
12370 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
12372 - Update manpage to describe some of the files you can expect to
12373 find in Tor's DataDirectory. Addresses ticket 9839.
12374 - Clean up several option names in the manpage to match their real
12375 names, add the missing documentation for a couple of testing and
12376 directory authority options, remove the documentation for a
12377 V2-directory fetching option that no longer exists. Resolves
12379 - Correct the documentation so that it lists the correct directory
12380 for the stats files. (They are in a subdirectory called "stats",
12382 - In the manpage, move more authority-only options into the
12383 directory authority section so that operators of regular directory
12384 caches don't get confused.
12385 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
12386 11061; bugfix on 0.2.4.7-alpha.
12387 - Resolve warnings from Doxygen.
12388 - Document in the manpage that "KBytes" may also be written as
12389 "kilobytes" or "KB", that "Kbits" may also be written as
12390 "kilobits", and so forth. Closes ticket 9222.
12391 - Document that the ClientOnly config option overrides ORPort.
12392 Our old explanation made ClientOnly sound as though it did
12393 nothing at all. Resolves bug 9059.
12394 - Explain that SocksPolicy, DirPolicy, and similar options don't
12395 take port arguments. Fixes the other part of ticket 11108.
12396 - Fix a comment about the rend_server_descriptor_t.protocols field
12397 to more accurately describe its range. Also, make that field
12398 unsigned, to more accurately reflect its usage. Fixes bug 9099;
12399 bugfix on 0.2.1.5-alpha.
12400 - Fix the manpage's description of HiddenServiceAuthorizeClient:
12401 the maximum client name length is 16, not 19. Fixes bug 11118;
12402 bugfix on 0.2.1.6-alpha.
12405 - The contrib directory has been sorted and tidied. Before, it was
12406 an unsorted dumping ground for useful and not-so-useful things.
12407 Now, it is divided based on functionality, and the items which
12408 seemed to be nonfunctional or useless have been removed. Resolves
12409 ticket 8966; based on patches from "rl1987".
12411 o Removed code and features:
12412 - Clients now reject any directory authority certificates lacking
12413 a dir-key-crosscert element. These have been included since
12414 0.2.1.9-alpha, so there's no real reason for them to be optional
12415 any longer. Completes proposal 157. Resolves ticket 10162.
12416 - Remove all code that existed to support the v2 directory system,
12417 since there are no longer any v2 directory authorities. Resolves
12419 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
12420 options, which were used for designating authorities as "Hidden
12421 service authorities". There has been no use of hidden service
12422 authorities since 0.2.2.1-alpha, when we stopped uploading or
12423 downloading v0 hidden service descriptors. Fixes bug 10881; also
12424 part of a fix for bug 10841.
12425 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
12426 and MTBF calculations, but that nobody was using. Fixes bug 11742.
12427 - The TunnelDirConns and PreferTunnelledDirConns options no longer
12428 exist; tunneled directory connections have been available since
12429 0.1.2.5-alpha, and turning them off is not a good idea. This is a
12430 brute-force fix for 10849, where "TunnelDirConns 0" would break
12432 - Remove all code for the long unused v1 directory protocol.
12433 Resolves ticket 11070.
12434 - Remove all remaining code related to version-0 hidden service
12435 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
12436 the rest of bug 10841.
12437 - Remove migration code from when we renamed the "cached-routers"
12438 file to "cached-descriptors" back in 0.2.0.8-alpha. This
12439 incidentally resolves ticket 6502 by cleaning up the related code
12440 a bit. Patch from Akshay Hebbar.
12442 o Test infrastructure:
12443 - Tor now builds each source file in two modes: a mode that avoids
12444 exposing identifiers needlessly, and another mode that exposes
12445 more identifiers for testing. This lets the compiler do better at
12446 optimizing the production code, while enabling us to take more
12447 radical measures to let the unit tests test things.
12448 - The production builds no longer include functions used only in
12449 the unit tests; all functions exposed from a module only for
12450 unit-testing are now static in production builds.
12451 - Add an --enable-coverage configuration option to make the unit
12452 tests (and a new src/or/tor-cov target) to build with gcov test
12454 - Update to the latest version of tinytest.
12455 - Improve the tinytest implementation of string operation tests so
12456 that comparisons with NULL strings no longer crash the tests; they
12457 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
12458 - New macros in test.h to simplify writing mock-functions for unit
12459 tests. Part of ticket 11507. Patch from Dana Koch.
12460 - We now have rudimentary function mocking support that our unit
12461 tests can use to test functions in isolation. Function mocking
12462 lets the tests temporarily replace a function's dependencies with
12463 stub functions, so that the tests can check the function without
12464 invoking the other functions it calls.
12467 - Complete tests for the status.c module. Resolves ticket 11507.
12468 Patch from Dana Koch.
12469 - Add more unit tests for the <circid,channel>->circuit map, and
12470 the destroy-cell-tracking code to fix bug 7912.
12471 - Unit tests for failing cases of the TAP onion handshake.
12472 - More unit tests for address-manipulation functions.
12474 o Distribution (systemd):
12475 - Include a tor.service file in contrib/dist for use with systemd.
12476 Some distributions will be able to use this file unmodified;
12477 others will need to tweak it, or write their own. Patch from Jamie
12478 Nguyen; resolves ticket 8368.
12479 - Verify configuration file via ExecStartPre in the systemd unit
12480 file. Patch from intrigeri; resolves ticket 12730.
12481 - Explicitly disable RunAsDaemon in the systemd unit file. Our
12482 current systemd unit uses "Type = simple", so systemd does not
12483 expect tor to fork. If the user has "RunAsDaemon 1" in their
12484 torrc, then things won't work as expected. This is e.g. the case
12485 on Debian (and derivatives), since there we pass "--defaults-torrc
12486 /usr/share/tor/tor-service-defaults-torrc" (that contains
12487 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
12491 Changes in version 0.2.4.25 - 2014-10-20
12492 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
12493 (even though POODLE does not affect Tor). It also works around a crash
12494 bug caused by some operating systems' response to the "POODLE" attack
12495 (which does affect Tor).
12497 o Major security fixes (also in 0.2.5.9-rc):
12498 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
12499 today support TLS 1.0 or later, so we can safely turn off support
12500 for this old (and insecure) protocol. Fixes bug 13426.
12502 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
12503 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
12504 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
12505 13471. This is a workaround for an OpenSSL bug.
12508 Changes in version 0.2.4.24 - 2014-09-22
12509 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
12510 connecting to hidden services, and it updates the location of one of
12511 the directory authorities.
12514 - Clients now send the correct address for their chosen rendezvous
12515 point when trying to access a hidden service. They used to send
12516 the wrong address, which would still work some of the time because
12517 they also sent the identity digest of the rendezvous point, and if
12518 the hidden service happened to try connecting to the rendezvous
12519 point from a relay that already had a connection open to it,
12520 the relay would reuse that connection. Now connections to hidden
12521 services should be more robust and faster. Also, this bug meant
12522 that clients were leaking to the hidden service whether they were
12523 on a little-endian (common) or big-endian (rare) system, which for
12524 some users might have reduced their anonymity. Fixes bug 13151;
12525 bugfix on 0.2.1.5-alpha.
12527 o Directory authority changes:
12528 - Change IP address for gabelmoo (v3 directory authority).
12530 o Minor features (geoip):
12531 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
12535 Changes in version 0.2.4.23 - 2014-07-28
12536 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
12537 guard rotation, and also backports several important fixes from the
12538 Tor 0.2.5 alpha release series.
12541 - Clients now look at the "usecreatefast" consensus parameter to
12542 decide whether to use CREATE_FAST or CREATE cells for the first hop
12543 of their circuit. This approach can improve security on connections
12544 where Tor's circuit handshake is stronger than the available TLS
12545 connection security levels, but the tradeoff is more computational
12546 load on guard relays. Implements proposal 221. Resolves ticket 9386.
12547 - Make the number of entry guards configurable via a new
12548 NumEntryGuards consensus parameter, and the number of directory
12549 guards configurable via a new NumDirectoryGuards consensus
12550 parameter. Implements ticket 12688.
12553 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
12554 implementation that caused incorrect results on 32-bit
12555 implementations when certain malformed inputs were used along with
12556 a small class of private ntor keys. This bug does not currently
12557 appear to allow an attacker to learn private keys or impersonate a
12558 Tor server, but it could provide a means to distinguish 32-bit Tor
12559 implementations from 64-bit Tor implementations. Fixes bug 12694;
12560 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
12564 - Warn and drop the circuit if we receive an inbound 'relay early'
12565 cell. Those used to be normal to receive on hidden service circuits
12566 due to bug 1038, but the buggy Tor versions are long gone from
12567 the network so we can afford to resume watching for them. Resolves
12568 the rest of bug 1038; bugfix on 0.2.1.19.
12569 - Correct a confusing error message when trying to extend a circuit
12570 via the control protocol but we don't know a descriptor or
12571 microdescriptor for one of the specified relays. Fixes bug 12718;
12572 bugfix on 0.2.3.1-alpha.
12573 - Avoid an illegal read from stack when initializing the TLS
12574 module using a version of OpenSSL without all of the ciphers
12575 used by the v2 link handshake. Fixes bug 12227; bugfix on
12576 0.2.4.8-alpha. Found by "starlight".
12579 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
12583 Changes in version 0.2.4.22 - 2014-05-16
12584 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
12585 alpha release series. These include blocking all authority signing
12586 keys that may have been affected by the OpenSSL "heartbleed" bug,
12587 choosing a far more secure set of TLS ciphersuites by default, closing
12588 a couple of memory leaks that could be used to run a target relay out
12589 of RAM, and several others.
12591 o Major features (security, backport from 0.2.5.4-alpha):
12592 - Block authority signing keys that were used on authorities
12593 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
12594 don't have any evidence that these keys _were_ compromised; we're
12595 doing this to be prudent.) Resolves ticket 11464.
12597 o Major bugfixes (security, OOM):
12598 - Fix a memory leak that could occur if a microdescriptor parse
12599 fails during the tokenizing step. This bug could enable a memory
12600 exhaustion attack by directory servers. Fixes bug 11649; bugfix
12603 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
12604 - The relay ciphersuite list is now generated automatically based on
12605 uniform criteria, and includes all OpenSSL ciphersuites with
12606 acceptable strength and forward secrecy. Previously, we had left
12607 some perfectly fine ciphersuites unsupported due to omission or
12608 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
12609 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
12610 - Relays now trust themselves to have a better view than clients of
12611 which TLS ciphersuites are better than others. (Thanks to bug
12612 11513, the relay list is now well-considered, whereas the client
12613 list has been chosen mainly for anti-fingerprinting purposes.)
12614 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
12615 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
12616 AES128. Resolves ticket 11528.
12617 - Clients now try to advertise the same list of ciphersuites as
12618 Firefox 28. This change enables selection of (fast) GCM
12619 ciphersuites, disables some strange old ciphers, and stops
12620 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
12621 Resolves ticket 11438.
12623 o Minor bugfixes (configuration, security):
12624 - When running a hidden service, do not allow TunneledDirConns 0:
12625 trying to set that option together with a hidden service would
12626 otherwise prevent the hidden service from running, and also make
12627 it publish its descriptors directly over HTTP. Fixes bug 10849;
12628 bugfix on 0.2.1.1-alpha.
12630 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
12631 - Avoid sending a garbage value to the controller when a circuit is
12632 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
12634 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
12635 - Stop leaking memory when we successfully resolve a PTR record.
12636 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
12638 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
12639 - Avoid 60-second delays in the bootstrapping process when Tor is
12640 launching for a second time while using bridges. Fixes bug 9229;
12641 bugfix on 0.2.0.3-alpha.
12643 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
12644 - Give the correct URL in the warning message when trying to run a
12645 relay on an ancient version of Windows. Fixes bug 9393.
12647 o Minor bugfixes (compilation):
12648 - Fix a compilation error when compiling with --disable-curve25519.
12649 Fixes bug 9700; bugfix on 0.2.4.17-rc.
12652 - Downgrade the warning severity for the the "md was still
12653 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
12654 for trying to diagnose this bug, and the current warning in
12655 earlier versions of tor achieves nothing useful. Addresses warning
12658 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
12659 - When we run out of usable circuit IDs on a channel, log only one
12660 warning for the whole channel, and describe how many circuits
12661 there were on the channel. Fixes part of ticket 11553.
12663 o Minor features (security, backport from 0.2.5.4-alpha):
12664 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
12665 leave the default at 8GBytes), to better support Raspberry Pi
12666 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
12668 o Documentation (backport from 0.2.5.4-alpha):
12669 - Correctly document that we search for a system torrc file before
12670 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
12674 Changes in version 0.2.4.21 - 2014-02-28
12675 Tor 0.2.4.21 further improves security against potential adversaries who
12676 find breaking 1024-bit crypto doable, and backports several stability
12677 and robustness patches from the 0.2.5 branch.
12679 o Major features (client security):
12680 - When we choose a path for a 3-hop circuit, make sure it contains
12681 at least one relay that supports the NTor circuit extension
12682 handshake. Otherwise, there is a chance that we're building
12683 a circuit that's worth attacking by an adversary who finds
12684 breaking 1024-bit crypto doable, and that chance changes the game
12685 theory. Implements ticket 9777.
12688 - Do not treat streams that fail with reason
12689 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
12690 since it could also indicate an ENETUNREACH connection error. Fixes
12691 part of bug 10777; bugfix on 0.2.4.8-alpha.
12693 o Code simplification and refactoring:
12694 - Remove data structures which were introduced to implement the
12695 CellStatistics option: they are now redundant with the new timestamp
12696 field in the regular packed_cell_t data structure, which we did
12697 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
12700 - Always clear OpenSSL bignums before freeing them -- even bignums
12701 that don't contain secrets. Resolves ticket 10793. Patch by
12703 - Build without warnings under clang 3.4. (We have some macros that
12704 define static functions only some of which will get used later in
12705 the module. Starting with clang 3.4, these give a warning unless the
12706 unused attribute is set on them.) Resolves ticket 10904.
12707 - Update geoip and geoip6 files to the February 7 2014 Maxmind
12708 GeoLite2 Country database.
12711 - Set the listen() backlog limit to the largest actually supported
12712 on the system, not to the value in a header file. Fixes bug 9716;
12713 bugfix on every released Tor.
12714 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
12715 exit node as a NOROUTE error, not an INTERNAL error, since they
12716 can apparently happen when trying to connect to the wrong sort
12717 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
12718 - Fix build warnings about missing "a2x" comment when building the
12719 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
12720 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
12721 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
12722 not entirely remove it from the connection lists. Fixes bug 9602;
12723 bugfix on 0.2.4.4-alpha.
12724 - Fix a segmentation fault in our benchmark code when running with
12725 Fedora's OpenSSL package, or any other OpenSSL that provides
12726 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
12727 - Turn "circuit handshake stats since last time" log messages into a
12728 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
12730 o Documentation fixes:
12731 - Document that all but one DirPort entry must have the NoAdvertise
12732 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
12735 Changes in version 0.2.4.20 - 2013-12-22
12736 Tor 0.2.4.20 fixes potentially poor random number generation for users
12737 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
12738 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
12739 and 4) have no state file in their DataDirectory (as would happen on
12740 first start). Users who generated relay or hidden service identity
12741 keys in such a situation should discard them and generate new ones.
12743 This release also fixes a logic error that caused Tor clients to build
12744 many more preemptive circuits than they actually need.
12747 - Do not allow OpenSSL engines to replace the PRNG, even when
12748 HardwareAccel is set. The only default builtin PRNG engine uses
12749 the Intel RDRAND instruction to replace the entire PRNG, and
12750 ignores all attempts to seed it with more entropy. That's
12751 cryptographically stupid: the right response to a new alleged
12752 entropy source is never to discard all previously used entropy
12753 sources. Fixes bug 10402; works around behavior introduced in
12754 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
12756 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
12757 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
12758 - Avoid launching spurious extra circuits when a stream is pending.
12759 This fixes a bug where any circuit that _wasn't_ unusable for new
12760 streams would be treated as if it were, causing extra circuits to
12761 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
12764 - Avoid a crash bug when starting with a corrupted microdescriptor
12765 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
12766 - If we fail to dump a previously cached microdescriptor to disk, avoid
12767 freeing duplicate data later on. Fixes bug 10423; bugfix on
12768 0.2.4.13-alpha. Spotted by "bobnomnom".
12771 Changes in version 0.2.4.19 - 2013-12-11
12772 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
12773 (1986-2013). Aaron worked on diverse projects including helping to guide
12774 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
12775 transparency to the U.S government's PACER documents, and contributing
12776 design and development for Tor and Tor2Web. Aaron was one of the latest
12777 martyrs in our collective fight for civil liberties and human rights,
12778 and his death is all the more painful because he was one of us.
12780 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
12781 a new circuit handshake and link encryption that use ECC to provide
12782 better security and efficiency; makes relays better manage circuit
12783 creation requests; uses "directory guards" to reduce client enumeration
12784 risks; makes bridges collect and report statistics about the pluggable
12785 transports they support; cleans up and improves our geoip database;
12786 gets much closer to IPv6 support for clients, bridges, and relays; makes
12787 directory authorities use measured bandwidths rather than advertised
12788 ones when computing flags and thresholds; disables client-side DNS
12789 caching to reduce tracking risks; and fixes a big bug in bridge
12790 reachability testing. This release introduces two new design
12791 abstractions in the code: a new "channel" abstraction between circuits
12792 and or_connections to allow for implementing alternate relay-to-relay
12793 transports, and a new "circuitmux" abstraction storing the queue of
12794 circuits for a channel. The release also includes many stability,
12795 security, and privacy fixes.
12797 o Major features (new circuit handshake):
12798 - Tor now supports a new circuit extension handshake designed by Ian
12799 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
12800 circuit extension handshake, later called "TAP", was a bit slow
12801 (especially on the relay side), had a fragile security proof, and
12802 used weaker keys than we'd now prefer. The new circuit handshake
12803 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
12804 function, making it significantly more secure than the older
12805 handshake, and significantly faster. Tor can use one of two built-in
12806 pure-C curve25519-donna implementations by Adam Langley, or it
12807 can link against the "nacl" library for a tuned version if present.
12809 The built-in version is very fast for 64-bit systems when building
12810 with GCC. The built-in 32-bit version is still faster than the
12811 old TAP protocol, but using libnacl is better on most such hosts.
12813 Implements proposal 216; closes ticket 7202.
12815 o Major features (better link encryption):
12816 - Relays can now enable the ECDHE TLS ciphersuites when available
12817 and appropriate. These ciphersuites let us negotiate forward-secure
12818 TLS secret keys more safely and more efficiently than with our
12819 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
12820 public relays prefer the (faster) P224 group, and bridges prefer
12821 the (more common) P256 group; you can override this with the
12824 This feature requires clients running 0.2.3.17-beta or later,
12825 and requires both sides to be running OpenSSL 1.0.0 or later
12826 with ECC support. OpenSSL 1.0.1, with the compile-time option
12827 "enable-ec_nistp_64_gcc_128", is highly recommended.
12829 Implements the relay side of proposal 198; closes ticket 7200.
12831 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
12832 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
12833 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
12834 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
12835 them to solve bug 6033.)
12837 o Major features (relay performance):
12838 - Instead of limiting the number of queued onionskins (aka circuit
12839 create requests) to a fixed, hard-to-configure number, we limit
12840 the size of the queue based on how many we expect to be able to
12841 process in a given amount of time. We estimate the time it will
12842 take to process an onionskin based on average processing time
12843 of previous onionskins. Closes ticket 7291. You'll never have to
12844 configure MaxOnionsPending again.
12845 - Relays process the new "NTor" circuit-level handshake requests
12846 with higher priority than the old "TAP" circuit-level handshake
12847 requests. We still process some TAP requests to not totally starve
12848 0.2.3 clients when NTor becomes popular. A new consensus parameter
12849 "NumNTorsPerTAP" lets us tune the balance later if we need to.
12850 Implements ticket 9574.
12852 o Major features (client bootstrapping resilience):
12853 - Add a new "FallbackDir" torrc option to use when we can't use
12854 a directory mirror from the consensus (either because we lack a
12855 consensus, or because they're all down). Currently, all authorities
12856 are fallbacks by default, and there are no other default fallbacks,
12857 but that will change. This option will allow us to give clients a
12858 longer list of servers to try to get a consensus from when first
12859 connecting to the Tor network, and thereby reduce load on the
12860 directory authorities. Implements proposal 206, "Preconfigured
12861 directory sources for bootstrapping". We also removed the old
12862 "FallbackNetworkstatus" option, since we never got it working well
12863 enough to use it. Closes bug 572.
12864 - If we have no circuits open, use a relaxed timeout (the
12865 95th-percentile cutoff) until a circuit succeeds. This heuristic
12866 should allow Tor to succeed at building circuits even when the
12867 network connection drastically changes. Should help with bug 3443.
12869 o Major features (use of guards):
12870 - Support directory guards (proposal 207): when possible, clients now
12871 use their entry guards for non-anonymous directory requests. This
12872 can help prevent client enumeration. Note that this behavior only
12873 works when we have a usable consensus directory, and when options
12874 about what to download are more or less standard. In the future we
12875 should re-bootstrap from our guards, rather than re-bootstrapping
12876 from the preconfigured list of directory sources that ships with
12877 Tor. Resolves ticket 6526.
12878 - Raise the default time that a client keeps an entry guard from
12879 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
12880 2012 paper. (We would make it even longer, but we need better client
12881 load balancing first.) Also, make the guard lifetime controllable
12882 via a new GuardLifetime torrc option and a GuardLifetime consensus
12883 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
12885 o Major features (bridges with pluggable transports):
12886 - Bridges now report the pluggable transports they support to the
12887 bridge authority, so it can pass the supported transports on to
12888 bridgedb and/or eventually do reachability testing. Implements
12890 - Automatically forward the TCP ports of pluggable transport
12891 proxies using tor-fw-helper if PortForwarding is enabled. Implements
12894 o Major features (geoip database):
12895 - Maxmind began labelling Tor relays as being in country "A1",
12896 which breaks by-country node selection inside Tor. Now we use a
12897 script to replace "A1" ("Anonymous Proxy") entries in our geoip
12898 file with real country codes. This script fixes about 90% of "A1"
12899 entries automatically and uses manual country code assignments to
12900 fix the remaining 10%. See src/config/README.geoip for details.
12902 - Add GeoIP database for IPv6 addresses. The new config option
12904 - Update to the October 2 2013 Maxmind GeoLite Country database.
12906 o Major features (IPv6):
12907 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
12908 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
12909 to happen. Implements ticket 5535.
12910 - All kind of relays, not just bridges, can now advertise an IPv6
12911 OR port. Implements ticket 6362.
12912 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
12913 connectivity, then set the IPv6Exit flag to 1. Also make sure your
12914 exit policy reads as you would like: the address * applies to all
12915 address families, whereas *4 is IPv4 address only, and *6 is IPv6
12916 addresses only. On the client side, you'll need to wait for enough
12917 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
12918 and use Socks5. Closes ticket 5547, implements proposal 117 as
12919 revised in proposal 208.
12920 - Bridge authorities now accept IPv6 bridge addresses and include
12921 them in network status documents. Implements ticket 5534.
12922 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
12924 o Major features (directory authorities):
12925 - Directory authorities now prefer using measured bandwidths to
12926 advertised ones when computing flags and thresholds. Resolves
12928 - Directory authorities that vote measured bandwidths about more
12929 than a threshold number of relays now treat relays with
12930 unmeasured bandwidths as having bandwidth 0 when computing their
12931 flags. Resolves ticket 8435.
12932 - Directory authorities now support a new consensus method (17)
12933 where they cap the published bandwidth of relays for which
12934 insufficient bandwidth measurements exist. Fixes part of bug 2286.
12935 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
12936 serve any v2 directory information. Now we can test disabling the
12937 old deprecated v2 directory format, and see whether doing so has
12938 any effect on network load. Begins to fix bug 6783.
12940 o Major features (build and portability):
12941 - Switch to a nonrecursive Makefile structure. Now instead of each
12942 Makefile.am invoking other Makefile.am's, there is a master
12943 Makefile.am that includes the others. This change makes our build
12944 process slightly more maintainable, and improves parallelism for
12945 building with make -j. Original patch by Stewart Smith; various
12946 fixes by Jim Meyering.
12947 - Where available, we now use automake's "silent" make rules by
12948 default, so that warnings are easier to spot. You can get the old
12949 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
12950 - Resume building correctly with MSVC and Makefile.nmake. This patch
12951 resolves numerous bugs and fixes reported by ultramage, including
12952 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
12954 o Security features:
12955 - Switch to a completely time-invariant approach for picking nodes
12956 weighted by bandwidth. Our old approach would run through the
12957 part of the loop after it had made its choice slightly slower
12958 than it ran through the part of the loop before it had made its
12959 choice. Addresses ticket 6538.
12960 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
12961 by tor2web clients allows hidden services to identify tor2web
12962 clients through their repeated selection of the same rendezvous
12963 and introduction point circuit endpoints (their guards). Resolves
12966 o Major bugfixes (relay denial of service):
12967 - When we have too much memory queued in circuits (according to a new
12968 MaxMemInCellQueues option), close the circuits that have the oldest
12969 queued cells, on the theory that those are most responsible for
12970 us running low on memory. This prevents us from running out of
12971 memory as a relay if circuits fill up faster than they can be
12972 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
12973 Tor. This bug is a further fix beyond bug 6252, whose fix was
12974 merged into 0.2.3.21-rc.
12975 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
12976 ID: these could be used to create unexpected streams and circuits
12977 which would count as "present" to some parts of Tor but "absent"
12978 to others, leading to zombie circuits and streams or to a bandwidth
12979 denial-of-service. Fixes bug 7889; bugfix on every released version
12980 of Tor. Reported by "oftc_must_be_destroyed".
12981 - Avoid a bug where our response to TLS renegotiation under certain
12982 network conditions could lead to a busy-loop, with 100% CPU
12983 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
12985 o Major bugfixes (asserts, crashes, leaks):
12986 - Prevent the get_freelists() function from running off the end of
12987 the list of freelists if it somehow gets an unrecognized
12988 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
12990 - Avoid a memory leak where we would leak a consensus body when we
12991 find that a consensus which we couldn't previously verify due to
12992 missing certificates is now verifiable. Fixes bug 8719; bugfix
12994 - If we are unable to save a microdescriptor to the journal, do not
12995 drop it from memory and then reattempt downloading it. Fixes bug
12996 9645; bugfix on 0.2.2.6-alpha.
12997 - Fix an assertion failure that would occur when disabling the
12998 ORPort setting on a running Tor process while accounting was
12999 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
13000 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
13001 when an exit connection with optimistic data succeeds immediately
13002 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
13004 - Fix a memory leak that would occur whenever a configuration
13005 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
13007 o Major bugfixes (relay rate limiting):
13008 - When a TLS write is partially successful but incomplete, remember
13009 that the flushed part has been flushed, and notice that bytes were
13010 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
13011 bugfix on Tor 0.1.0.5-rc.
13012 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
13013 to 1GB/1GB. The previous defaults were intended to be "basically
13014 infinite", but it turns out they're now limiting our 100mbit+
13015 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
13016 last time we raised it).
13017 - No longer stop reading or writing on cpuworker connections when
13018 our rate limiting buckets go empty. Now we should handle circuit
13019 handshake requests more promptly. Resolves bug 9731.
13021 o Major bugfixes (client-side privacy):
13022 - When we mark a circuit as unusable for new circuits, have it
13023 continue to be unusable for new circuits even if MaxCircuitDirtiness
13024 is increased too much at the wrong time, or the system clock jumps
13025 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
13026 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
13027 which have resolved to internal addresses") is set, apply that
13028 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
13029 - When an exit relay rejects a stream with reason "exit policy", but
13030 we only know an exit policy summary (e.g. from the microdesc
13031 consensus) for it, do not mark the relay as useless for all exiting.
13032 Instead, mark just the circuit as unsuitable for that particular
13033 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
13035 o Major bugfixes (stream isolation):
13036 - Allow applications to get proper stream isolation with
13037 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
13038 username/password authentication also offer "no authentication". Tor
13039 had previously preferred "no authentication", so the applications
13040 never actually sent Tor their auth details. Now Tor selects
13041 username/password authentication if it's offered. You can disable
13042 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
13043 bug 8117; bugfix on 0.2.3.3-alpha.
13044 - Follow the socks5 protocol when offering username/password
13045 authentication. The fix for bug 8117 exposed this bug, and it
13046 turns out real-world applications like Pidgin do care. Bugfix on
13047 0.2.3.2-alpha; fixes bug 8879.
13049 o Major bugfixes (client circuit building):
13050 - Alter circuit build timeout measurement to start at the point
13051 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
13052 initialization). This should make our timeout measurements more
13053 uniform. Previously, we were sometimes including ORconn setup time
13054 in our circuit build time measurements. Should resolve bug 3443.
13055 - If the circuit build timeout logic is disabled (via the consensus,
13056 or because we are an authority), then don't build testing circuits.
13057 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
13059 o Major bugfixes (client-side DNS):
13060 - Turn off the client-side DNS cache by default. Updating and using
13061 the DNS cache is now configurable on a per-client-port
13062 level. SOCKSPort, DNSPort, etc lines may now contain
13063 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
13064 cache these types of DNS answers when we receive them from an
13065 exit node in response to an application request on this port, and
13066 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
13067 cached DNS answers of these types, we shouldn't use them. It's
13068 potentially risky to use cached DNS answers at the client, since
13069 doing so can indicate to one exit what answers we've gotten
13070 for DNS lookups in the past. With IPv6, this becomes especially
13071 problematic. Using cached DNS answers for requests on the same
13072 circuit would present less linkability risk, since all traffic
13073 on a circuit is already linkable, but it would also provide
13074 little performance benefit: the exit node caches DNS replies
13075 too. Implements a simplified version of Proposal 205. Implements
13078 o Major bugfixes (hidden service privacy):
13079 - Limit hidden service descriptors to at most ten introduction
13080 points, to slow one kind of guard enumeration. Fixes bug 9002;
13081 bugfix on 0.1.1.11-alpha.
13083 o Major bugfixes (directory fetching):
13084 - If the time to download the next old-style networkstatus is in
13085 the future, do not decline to consider whether to download the
13086 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
13088 - We used to always request authority certificates by identity digest,
13089 meaning we'd get the newest one even when we wanted one with a
13090 different signing key. Then we would complain about being given
13091 a certificate we already had, and never get the one we really
13092 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
13093 resource to request the one we want. Fixes bug 5595; bugfix on
13096 o Major bugfixes (bridge reachability):
13097 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
13098 previously they did not, which prevented them from receiving
13099 successful connections from relays for self-test or bandwidth
13100 testing. Also, when a relay is extending a circuit to a bridge,
13101 it needs to send a NETINFO cell, even when the bridge hasn't sent
13102 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
13104 o Major bugfixes (control interface):
13105 - When receiving a new configuration file via the control port's
13106 LOADCONF command, do not treat the defaults file as absent.
13107 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
13109 o Major bugfixes (directory authorities):
13110 - Stop marking every relay as having been down for one hour every
13111 time we restart a directory authority. These artificial downtimes
13112 were messing with our Stable and Guard flag calculations. Fixes
13113 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
13114 - When computing directory thresholds, ignore any rejected-as-sybil
13115 nodes during the computation so that they can't influence Fast,
13116 Guard, etc. (We should have done this for proposal 109.) Fixes
13118 - When marking a node as a likely sybil, reset its uptime metrics
13119 to zero, so that it cannot time towards getting marked as Guard,
13120 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
13122 - Fix a bug in the voting algorithm that could yield incorrect results
13123 when a non-naming authority declared too many flags. Fixes bug 9200;
13124 bugfix on 0.2.0.3-alpha.
13126 o Internal abstraction features:
13127 - Introduce new channel_t abstraction between circuits and
13128 or_connection_t to allow for implementing alternate OR-to-OR
13129 transports. A channel_t is an abstract object which can either be a
13130 cell-bearing channel, which is responsible for authenticating and
13131 handshaking with the remote OR and transmitting cells to and from
13132 it, or a listening channel, which spawns new cell-bearing channels
13133 at the request of remote ORs. Implements part of ticket 6465.
13134 - Make a channel_tls_t subclass of channel_t, adapting it to the
13135 existing or_connection_t code. The V2/V3 protocol handshaking
13136 code which formerly resided in command.c has been moved below the
13137 channel_t abstraction layer and may be found in channeltls.c now.
13138 Implements the rest of ticket 6465.
13139 - Introduce new circuitmux_t storing the queue of circuits for
13140 a channel; this encapsulates and abstracts the queue logic and
13141 circuit selection policy, and allows the latter to be overridden
13142 easily by switching out a policy object. The existing EWMA behavior
13143 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
13145 o New build requirements:
13146 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
13147 strongly recommended.
13148 - Tor maintainers now require Automake version 1.9 or later to build
13149 Tor from the Git repository. (Automake is not required when building
13150 from a source distribution.)
13152 o Minor features (protocol):
13153 - No longer include the "opt" prefix when generating routerinfos
13154 or v2 directories: it has been needless since Tor 0.1.2. Closes
13156 - Reject EXTEND cells sent to nonexistent streams. According to the
13157 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
13158 we were only checking for stream IDs that were currently in use.
13159 Found while hunting for more instances of bug 6271. Bugfix on
13160 0.0.2pre8, which introduced incremental circuit construction.
13161 - Tor relays and clients now support a better CREATE/EXTEND cell
13162 format, allowing the sender to specify multiple address, identity,
13163 and handshake types. Implements Robert Ransom's proposal 200;
13164 closes ticket 7199.
13165 - Reject as invalid most directory objects containing a NUL.
13166 Belt-and-suspender fix for bug 8037.
13168 o Minor features (security):
13169 - Clear keys and key-derived material left on the stack in
13170 rendservice.c and rendclient.c. Check return value of
13171 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
13172 These fixes should make us more forward-secure against cold-boot
13173 attacks and the like. Fixes bug 2385.
13174 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
13175 Irix's random() only return 15 bits; Solaris's random() returns more
13176 bits but its RAND_MAX says it only returns 15, and so on. Motivated
13177 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
13179 o Minor features (control protocol):
13180 - Add a "GETINFO signal/names" control port command. Implements
13182 - Provide default values for all options via "GETINFO config/defaults".
13183 Implements ticket 4971.
13184 - Allow an optional $ before the node identity digest in the
13185 controller command GETINFO ns/id/<identity>, for consistency with
13186 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
13187 - Add CACHED keyword to ADDRMAP events in the control protocol
13188 to indicate whether a DNS result will be cached or not. Resolves
13190 - Generate bootstrapping status update events correctly when fetching
13191 microdescriptors. Fixes bug 9927.
13193 o Minor features (path selection):
13194 - When deciding whether we have enough descriptors to build circuits,
13195 instead of looking at raw relay counts, look at which fraction
13196 of (bandwidth-weighted) paths we're able to build. This approach
13197 keeps clients from building circuits if their paths are likely to
13198 stand out statistically. The default fraction of paths needed is
13199 taken from the consensus directory; you can override it with the
13200 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
13201 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
13202 and we have GeoIP information, also exclude all nodes with unknown
13203 countries "??" and "A1". This behavior is controlled by the
13204 new GeoIPExcludeUnknown option: you can make such nodes always
13205 excluded with "GeoIPExcludeUnknown 1", and disable the feature
13206 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
13207 gets you the default behavior. Implements feature 7706.
13209 o Minor features (hidden services):
13210 - Improve circuit build timeout handling for hidden services.
13211 In particular: adjust build timeouts more accurately depending
13212 upon the number of hop-RTTs that a particular circuit type
13213 undergoes. Additionally, launch intro circuits in parallel
13214 if they timeout, and take the first one to reply as valid.
13215 - The Tor client now ignores sub-domain components of a .onion
13216 address. This change makes HTTP "virtual" hosting
13217 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
13218 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
13219 hosted on the same hidden service. Implements proposal 204.
13220 - Enable Tor to read configuration, state, and key information from
13221 a FIFO. Previously Tor would only read from files with a positive
13222 stat.st_size. Code from meejah; fixes bug 6044.
13224 o Minor features (clients):
13225 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
13226 microdescriptor-related dir requests, and only fall back to normal
13227 descriptors if none of their bridges can handle microdescriptors
13228 (as opposed to the fix in ticket 4013, which caused them to fall
13229 back to normal descriptors if *any* of their bridges preferred
13230 them). Resolves ticket 4994.
13231 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
13232 TCP ports to forward. In the past it only accepted two ports:
13233 the ORPort and the DirPort.
13235 o Minor features (protecting client timestamps):
13236 - Clients no longer send timestamps in their NETINFO cells. These were
13237 not used for anything, and they provided one small way for clients
13238 to be distinguished from each other as they moved from network to
13239 network or behind NAT. Implements part of proposal 222.
13240 - Clients now round timestamps in INTRODUCE cells down to the nearest
13241 10 minutes. If a new Support022HiddenServices option is set to 0, or
13242 if it's set to "auto" and the feature is disabled in the consensus,
13243 the timestamp is sent as 0 instead. Implements part of proposal 222.
13244 - Stop sending timestamps in AUTHENTICATE cells. This is not such
13245 a big deal from a security point of view, but it achieves no actual
13246 good purpose, and isn't needed. Implements part of proposal 222.
13247 - Reduce down accuracy of timestamps in hidden service descriptors.
13248 Implements part of proposal 222.
13250 o Minor features (bridges):
13251 - Make bridge relays check once a minute for whether their IP
13252 address has changed, rather than only every 15 minutes. Resolves
13253 bugs 1913 and 1992.
13254 - Bridge statistics now count bridge clients connecting over IPv6:
13255 bridge statistics files now list "bridge-ip-versions" and
13256 extra-info documents list "geoip6-db-digest". The control protocol
13257 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
13258 implementation by "shkoo", addressing ticket 5055.
13259 - Add a new torrc option "ServerTransportListenAddr" to let bridge
13260 operators select the address where their pluggable transports will
13261 listen for connections. Resolves ticket 7013.
13262 - Randomize the lifetime of our SSL link certificate, so censors can't
13263 use the static value for filtering Tor flows. Resolves ticket 8443;
13264 related to ticket 4014 which was included in 0.2.2.33.
13266 o Minor features (relays):
13267 - Option OutboundBindAddress can be specified multiple times and
13268 accepts IPv6 addresses. Resolves ticket 6876.
13270 o Minor features (IPv6, client side):
13271 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
13272 prefer to hand out virtual IPv6 addresses, since there are more of
13273 them and we can't run out. To override this behavior and make IPv4
13274 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
13275 or DNSPort you're using for resolving. Implements ticket 7571.
13276 - AutomapHostsOnResolve responses are now randomized, to avoid
13277 annoying situations where Tor is restarted and applications
13278 connect to the wrong addresses.
13279 - Never try more than 1000 times to pick a new virtual address when
13280 AutomapHostsOnResolve is set. That's good enough so long as we
13281 aren't close to handing out our entire virtual address space;
13282 if you're getting there, it's best to switch to IPv6 virtual
13285 o Minor features (IPv6, relay/authority side):
13286 - New config option "AuthDirHasIPv6Connectivity 1" that directory
13287 authorities should set if they have IPv6 connectivity and want to
13288 do reachability tests for IPv6 relays. Implements feature 5974.
13289 - A relay with an IPv6 OR port now sends that address in NETINFO
13290 cells (in addition to its other address). Implements ticket 6364.
13292 o Minor features (directory authorities):
13293 - Directory authorities no long accept descriptors for any version of
13294 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
13295 These versions are insecure, unsupported, or both. Implements
13297 - When directory authorities are computing thresholds for flags,
13298 never let the threshold for the Fast flag fall below 4096
13299 bytes. Also, do not consider nodes with extremely low bandwidths
13300 when deciding thresholds for various directory flags. This change
13301 should raise our threshold for Fast relays, possibly in turn
13302 improving overall network performance; see ticket 1854. Resolves
13304 - Directory authorities now include inside each vote a statement of
13305 the performance thresholds they used when assigning flags.
13306 Implements ticket 8151.
13307 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
13308 in directory authority votes to describe whether they have enough
13309 measured bandwidths to ignore advertised (relay descriptor)
13310 bandwidth claims. Resolves ticket 8711.
13312 o Minor features (path bias detection):
13313 - Path Use Bias: Perform separate accounting for successful circuit
13314 use. Keep separate statistics on stream attempt rates versus stream
13315 success rates for each guard. Provide configurable thresholds to
13316 determine when to emit log messages or disable use of guards that
13317 fail too many stream attempts. Resolves ticket 7802.
13318 - Create three levels of Path Bias log messages, as opposed to just
13319 two. These are configurable via consensus as well as via the torrc
13320 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
13321 The default values are 0.70, 0.50, and 0.30 respectively.
13322 - Separate the log message levels from the decision to drop guards,
13323 which also is available via torrc option PathBiasDropGuards.
13324 PathBiasDropGuards still defaults to 0 (off).
13325 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
13326 in combination with PathBiasExtremeRate.
13327 - Increase the default values for PathBiasScaleThreshold and
13328 PathBiasCircThreshold from (200, 20) to (300, 150).
13329 - Add in circuit usage accounting to path bias. If we try to use a
13330 built circuit but fail for any reason, it counts as path bias.
13331 Certain classes of circuits where the adversary gets to pick your
13332 destination node are exempt from this accounting. Usage accounting
13333 can be specifically disabled via consensus parameter or torrc.
13334 - Convert all internal path bias state to double-precision floating
13335 point, to avoid roundoff error and other issues.
13336 - Only record path bias information for circuits that have completed
13337 *two* hops. Assuming end-to-end tagging is the attack vector, this
13338 makes us more resilient to ambient circuit failure without any
13339 detection capability loss.
13341 o Minor features (build):
13342 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
13343 dhill. Resolves ticket 6982.
13344 - Compile on win64 using mingw64. Fixes bug 7260; patches from
13346 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
13347 separate error codes; or at least, don't break for that reason.
13348 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
13350 o Build improvements (autotools):
13351 - Warn if building on a platform with an unsigned time_t: there
13352 are too many places where Tor currently assumes that time_t can
13353 hold negative values. We'd like to fix them all, but probably
13355 - Do not report status verbosely from autogen.sh unless the -v flag
13356 is specified. Fixes issue 4664. Patch from Onizuka.
13357 - Detect and reject attempts to build Tor with threading support
13358 when OpenSSL has been compiled without threading support.
13360 - Try to detect if we are ever building on a platform where
13361 memset(...,0,...) does not set the value of a double to 0.0. Such
13362 platforms are permitted by the C standard, though in practice
13363 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
13364 currently support them, but it's better to detect them and fail
13365 than to perform erroneously.
13366 - We no longer warn so much when generating manpages from their
13368 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
13369 the signs of types during autoconf. This is better than our old
13370 approach, which didn't work when cross-compiling.
13372 o Minor features (log messages, warnings):
13373 - Detect when we're running with a version of OpenSSL other than the
13374 one we compiled with. This conflict has occasionally given people
13375 hard-to-track-down errors.
13376 - Warn users who run hidden services on a Tor client with
13377 UseEntryGuards disabled that their hidden services will be
13378 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
13379 attack which motivated Tor to support entry guards in the first
13380 place). Resolves ticket 6889.
13381 - Warn when we are binding low ports when hibernation is enabled;
13382 previously we had warned when we were _advertising_ low ports with
13383 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
13384 - Issue a warning when running with the bufferevents backend enabled.
13385 It's still not stable, and people should know that they're likely
13386 to hit unexpected problems. Closes ticket 9147.
13388 o Minor features (log messages, notices):
13389 - Refactor resolve_my_address() so it returns the method by which we
13390 decided our public IP address (explicitly configured, resolved from
13391 explicit hostname, guessed from interfaces, learned by gethostname).
13392 Now we can provide more helpful log messages when a relay guesses
13393 its IP address incorrectly (e.g. due to unexpected lines in
13394 /etc/hosts). Resolves ticket 2267.
13395 - Track how many "TAP" and "NTor" circuit handshake requests we get,
13396 and how many we complete, and log it every hour to help relay
13397 operators follow trends in network load. Addresses ticket 9658.
13399 o Minor features (log messages, diagnostics):
13400 - If we fail to free a microdescriptor because of bug 7164, log
13401 the filename and line number from which we tried to free it.
13402 - We compute the overhead from passing onionskins back and forth to
13403 cpuworkers, and report it when dumping statistics in response to
13404 SIGUSR1. Supports ticket 7291.
13405 - Add another diagnostic to the heartbeat message: track and log
13406 overhead that TLS is adding to the data we write. If this is
13407 high, we are sending too little data to SSL_write at a time.
13408 Diagnostic for bug 7707.
13409 - Log packaged cell fullness as part of the heartbeat message.
13410 Diagnosis to try to determine the extent of bug 7743.
13411 - Add more detail to a log message about relaxed timeouts, to help
13413 - When learning a fingerprint for a bridge, log its corresponding
13414 transport type. Implements ticket 7896.
13415 - Warn more aggressively when flushing microdescriptors to a
13416 microdescriptor cache fails, in an attempt to mitigate bug 8031,
13417 or at least make it more diagnosable.
13418 - Improve the log message when "Bug/attack: unexpected sendme cell
13419 from client" occurs, to help us track bug 8093.
13420 - Improve debugging output to help track down bug 8185 ("Bug:
13421 outgoing relay cell has n_chan==NULL. Dropping.")
13423 o Minor features (log messages, quieter bootstrapping):
13424 - Log fewer lines at level "notice" about our OpenSSL and Libevent
13425 versions and capabilities when everything is going right. Resolves
13426 part of ticket 6736.
13427 - Omit the first heartbeat log message, because it never has anything
13428 useful to say, and it clutters up the bootstrapping messages.
13429 Resolves ticket 6758.
13430 - Don't log about reloading the microdescriptor cache at startup. Our
13431 bootstrap warnings are supposed to tell the user when there's a
13432 problem, and our bootstrap notices say when there isn't. Resolves
13433 ticket 6759; bugfix on 0.2.2.6-alpha.
13434 - Don't log "I learned some more directory information" when we're
13435 reading cached directory information. Reserve it for when new
13436 directory information arrives in response to a fetch. Resolves
13438 - Don't complain about bootstrapping problems while hibernating.
13439 These complaints reflect a general code problem, but not one
13440 with any problematic effects (no connections are actually
13441 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
13443 o Minor features (testing):
13444 - In our testsuite, create temporary directories with a bit more
13445 entropy in their name to make name collisions less likely. Fixes
13447 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
13448 (P-256) Diffie-Hellman handshakes to src/or/bench.
13449 - Add benchmark functions to test onion handshake performance.
13452 - The DirServer option is now DirAuthority, for consistency with
13453 current naming patterns. You can still use the old DirServer form.
13455 o Minor bugfixes (protocol):
13456 - Fix the handling of a TRUNCATE cell when it arrives while the
13457 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
13458 - When a Tor client gets a "truncated" relay cell, the first byte of
13459 its payload specifies why the circuit was truncated. We were
13460 ignoring this 'reason' byte when tearing down the circuit, resulting
13461 in the controller not being told why the circuit closed. Now we
13462 pass the reason from the truncated cell to the controller. Bugfix
13463 on 0.1.2.3-alpha; fixes bug 7039.
13464 - Fix a misframing issue when reading the version numbers in a
13465 VERSIONS cell. Previously we would recognize [00 01 00 02] as
13466 'version 1, version 2, and version 0x100', when it should have
13467 only included versions 1 and 2. Fixes bug 8059; bugfix on
13468 0.2.0.10-alpha. Reported pseudonymously.
13469 - Make the format and order of STREAM events for DNS lookups
13470 consistent among the various ways to launch DNS lookups. Fixes
13471 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
13473 o Minor bugfixes (syscalls and disk interaction):
13474 - Always check the return values of functions fcntl() and
13475 setsockopt(). We don't believe these are ever actually failing in
13476 practice, but better safe than sorry. Also, checking these return
13477 values should please analysis tools like Coverity. Patch from
13478 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
13479 - Avoid double-closing the listener socket in our socketpair()
13480 replacement (used on Windows) in the case where the addresses on
13481 our opened sockets don't match what we expected. Fixes bug 9400;
13482 bugfix on 0.0.2pre7. Found by Coverity.
13483 - Correctly store microdescriptors and extrainfo descriptors that
13484 include an internal NUL byte. Fixes bug 8037; bugfix on
13485 0.2.0.1-alpha. Bug reported by "cypherpunks".
13486 - If for some reason we fail to write a microdescriptor while
13487 rebuilding the cache, do not let the annotations from that
13488 microdescriptor linger in the cache file, and do not let the
13489 microdescriptor stay recorded as present in its old location.
13490 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
13491 - Use direct writes rather than stdio when building microdescriptor
13492 caches, in an attempt to mitigate bug 8031, or at least make it
13495 o Minor fixes (config options):
13496 - Warn and fail if a server is configured not to advertise any
13497 ORPorts at all. (We need *something* to put in our descriptor,
13498 or we just won't work.)
13499 - Behave correctly when the user disables LearnCircuitBuildTimeout
13500 but doesn't tell us what they would like the timeout to be. Fixes
13501 bug 6304; bugfix on 0.2.2.14-alpha.
13502 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
13503 to start with a triple-underscore so the controller won't touch it.
13504 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
13505 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
13506 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
13507 - When autodetecting the number of CPUs, use the number of available
13508 CPUs in preference to the number of configured CPUs. Inform the
13509 user if this reduces the number of available CPUs. Fixes bug 8002;
13510 bugfix on 0.2.3.1-alpha.
13511 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
13512 - Make it an error when you set EntryNodes but disable UseGuardNodes,
13513 since it will (surprisingly to some users) ignore EntryNodes. Fixes
13514 bug 8180; bugfix on 0.2.3.11-alpha.
13515 - Avoid overflows when the user sets MaxCircuitDirtiness to a
13516 ridiculously high value, by imposing a (ridiculously high) 30-day
13517 maximum on MaxCircuitDirtiness.
13519 o Minor bugfixes (control protocol):
13520 - Stop sending a stray "(null)" in some cases for the server status
13521 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
13523 - The ADDRMAP command can no longer generate an ill-formed error
13524 code on a failed MAPADDRESS. It now says "internal" rather than
13525 an English sentence fragment with spaces in the middle. Bugfix on
13526 Tor 0.2.0.19-alpha.
13528 o Minor bugfixes (clients / edges):
13529 - When we receive a RELAY_END cell with the reason DONE, or with no
13530 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
13531 status as "connection refused". Previously we reported these cases
13532 as success but then immediately closed the connection. Fixes bug
13533 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
13534 - If the guard we choose first doesn't answer, we would try the
13535 second guard, but once we connected to the second guard we would
13536 abandon it and retry the first one, slowing down bootstrapping.
13537 The fix is to treat all our initially chosen guards as acceptable
13538 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
13539 - When choosing which stream on a formerly stalled circuit to wake
13540 first, make better use of the platform's weak RNG. Previously,
13541 we had been using the % ("modulo") operator to try to generate a
13542 1/N chance of picking each stream, but this behaves badly with
13543 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
13546 o Minor bugfixes (path bias detection):
13547 - If the state file's path bias counts are invalid (presumably from a
13548 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
13549 additional checks and log messages to the scaling of Path Bias
13550 counts, in case there still are remaining issues with scaling.
13551 Should help resolve bug 8235.
13552 - Prevent rounding error in path bias counts when scaling
13553 them down, and use the correct scale factor default. Also demote
13554 some path bias related log messages down a level and make others
13555 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
13556 - Remove a source of rounding error during path bias count scaling;
13557 don't count cannibalized circuits as used for path bias until we
13558 actually try to use them; and fix a circuit_package_relay_cell()
13559 warning message about n_chan==NULL. Fixes bug 7802.
13560 - Paste the description for PathBias parameters from the man
13561 page into or.h, so the code documents them too. Fixes bug 7982;
13562 bugfix on 0.2.3.17-beta.
13564 o Minor bugfixes (relays):
13565 - Stop trying to resolve our hostname so often (e.g. every time we
13566 think about doing a directory fetch). Now we reuse the cached
13567 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
13568 and 2410 (bugfix on 0.1.2.2-alpha).
13569 - When examining the list of network interfaces to find our address,
13570 do not consider non-running or disabled network interfaces. Fixes
13571 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
13573 o Minor bugfixes (blocking resistance):
13574 - Only disable TLS session ticket support when running as a TLS
13575 server. Now clients will blend better with regular Firefox
13576 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
13578 o Minor bugfixes (IPv6):
13579 - Use square brackets around IPv6 addresses in numerous places
13580 that needed them, including log messages, HTTPS CONNECT proxy
13581 requests, TransportProxy statefile entries, and pluggable transport
13582 extra-info lines. Fixes bug 7011; patch by David Fifield.
13584 o Minor bugfixes (directory authorities):
13585 - Reject consensus votes with more than 64 known-flags. We aren't even
13586 close to that limit yet, and our code doesn't handle it correctly.
13587 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
13588 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
13589 bugfix on 0.2.0.3-alpha.
13591 o Minor bugfixes (memory leaks):
13592 - Avoid leaking memory if we fail to compute a consensus signature
13593 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
13594 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
13595 on 0.2.1.1-alpha; fixes bug 7816.
13596 - Fix a memory leak during safe-cookie controller authentication.
13597 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
13598 - Free some more still-in-use memory at exit, to make hunting for
13599 memory leaks easier. Resolves bug 7029.
13601 o Minor bugfixes (code correctness):
13602 - Increase the width of the field used to remember a connection's
13603 link protocol version to two bytes. Harmless for now, since the
13604 only currently recognized versions are one byte long. Reported
13605 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
13606 - Fix a crash when debugging unit tests on Windows: deallocate a
13607 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
13608 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
13609 - When detecting the largest possible file descriptor (in order to
13610 close all file descriptors when launching a new program), actually
13611 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
13612 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
13614 - Avoid a crash if we fail to generate an extrainfo descriptor.
13615 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
13616 this is CID 718634.
13617 - Avoid an off-by-one error when checking buffer boundaries when
13618 formatting the exit status of a pluggable transport helper.
13619 This is probably not an exploitable bug, but better safe than
13620 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
13622 - Get rid of a couple of harmless clang warnings, where we compared
13623 enums to ints. These warnings are newly introduced in clang 3.2.
13625 o Minor bugfixes (code cleanliness):
13626 - Avoid use of reserved identifiers in our C code. The C standard
13627 doesn't like us declaring anything that starts with an
13628 underscore, so let's knock it off before we get in trouble. Fix
13629 for bug 1031; bugfix on the first Tor commit.
13630 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
13631 with large values. This situation was untriggered, but nevertheless
13632 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
13633 - Fix an impossible buffer overrun in the AES unit tests. Fixes
13634 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
13635 - Fix handling of rendezvous client authorization types over 8.
13636 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
13637 - Remove a couple of extraneous semicolons that were upsetting the
13638 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
13639 bugfix on 0.2.2.1-alpha.
13640 - When complaining about a client port on a public address, log
13641 which address we're complaining about. Fixes bug 4020; bugfix on
13642 0.2.3.3-alpha. Patch by Tom Fitzhenry.
13644 o Minor bugfixes (log messages, warnings):
13645 - If we encounter a write failure on a SOCKS connection before we
13646 finish our SOCKS handshake, don't warn that we closed the
13647 connection before we could send a SOCKS reply. Fixes bug 8427;
13648 bugfix on 0.1.0.1-rc.
13649 - Fix a directory authority warn caused when we have a large amount
13650 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
13651 - Downgrade "Failed to hand off onionskin" messages to "debug"
13652 severity, since they're typically redundant with the "Your computer
13653 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
13654 - Avoid spurious warnings when configuring multiple client ports of
13655 which only some are nonlocal. Previously, we had claimed that some
13656 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
13659 o Minor bugfixes (log messages, other):
13660 - Fix log messages and comments to avoid saying "GMT" when we mean
13661 "UTC". Fixes bug 6113.
13662 - When rejecting a configuration because we were unable to parse a
13663 quoted string, log an actual error message. Fixes bug 7950; bugfix
13665 - Correctly recognize that [::1] is a loopback address. Fixes
13666 bug 8377; bugfix on 0.2.1.3-alpha.
13667 - Don't log inappropriate heartbeat messages when hibernating: a
13668 hibernating node is _expected_ to drop out of the consensus,
13669 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
13670 bugfix on 0.2.3.1-alpha.
13671 - Eliminate several instances where we use "Nickname=ID" to refer to
13672 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
13673 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
13676 o Minor bugfixes (build):
13677 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
13678 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
13679 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
13681 o Documentation fixes:
13682 - Make the torify manpage no longer refer to tsocks; torify hasn't
13683 supported tsocks since 0.2.3.14-alpha.
13684 - Make the tor manpage no longer reference tsocks.
13685 - Fix the GeoIPExcludeUnknown documentation to refer to
13686 ExcludeExitNodes rather than the currently nonexistent
13687 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
13688 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
13690 - Say "KBytes" rather than "KB" in the man page (for various values
13691 of K), to further reduce confusion about whether Tor counts in
13692 units of memory or fractions of units of memory. Resolves ticket 7054.
13693 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
13694 names match. Fixes bug 7768.
13695 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
13696 message is logged at notice, not at info.
13697 - Clarify the usage and risks of setting the ContactInfo torrc line
13698 for your relay or bridge. Resolves ticket 9854.
13699 - Add anchors to the manpage so we can link to the html version of
13700 the documentation for specific options. Resolves ticket 9866.
13701 - Replace remaining references to DirServer in man page and
13702 log entries. Resolves ticket 10124.
13704 o Removed features:
13705 - Stop exporting estimates of v2 and v3 directory traffic shares
13706 in extrainfo documents. They were unneeded and sometimes inaccurate.
13707 Also stop exporting any v2 directory request statistics. Resolves
13709 - Drop support for detecting and warning about versions of Libevent
13710 before 1.3e. Nothing reasonable ships with them any longer; warning
13711 the user about them shouldn't be needed. Resolves ticket 6826.
13712 - Now that all versions before 0.2.2.x are disallowed, we no longer
13713 need to work around their missing features. Remove a bunch of
13714 compatibility code.
13717 - The tor-tsocks.conf is no longer distributed or installed. We
13718 recommend that tsocks users use torsocks instead. Resolves
13720 - Remove some of the older contents of doc/ as obsolete; move others
13721 to torspec.git. Fixes bug 8965.
13723 o Code simplification:
13724 - Avoid using character buffers when constructing most directory
13725 objects: this approach was unwieldy and error-prone. Instead,
13726 build smartlists of strings, and concatenate them when done.
13727 - Rename "isin" functions to "contains", for grammar. Resolves
13729 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
13730 with the natural logarithm function from the system libm. Resolves
13732 - Start using OpenBSD's implementation of queue.h, so that we don't
13733 need to hand-roll our own pointer and list structures whenever we
13734 need them. (We can't rely on a sys/queue.h, since some operating
13735 systems don't have them, and the ones that do have them don't all
13736 present the same extensions.)
13737 - Start using OpenBSD's implementation of queue.h (originally by
13739 - Enhance our internal sscanf replacement so that we can eliminate
13740 the last remaining uses of the system sscanf. (Though those uses
13741 of sscanf were safe, sscanf itself is generally error prone, so
13742 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
13744 - Replace all calls to snprintf() outside of src/ext with
13745 tor_snprintf(). Also remove the #define to replace snprintf with
13746 _snprintf on Windows; they have different semantics, and all of
13747 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
13750 - Add a wrapper function for the common "log a message with a
13752 - Split the onion.c file into separate modules for the onion queue
13753 and the different handshakes it supports.
13754 - Move the client-side address-map/virtual-address/DNS-cache code
13755 out of connection_edge.c into a new addressmap.c module.
13756 - Move the entry node code from circuitbuild.c to its own file.
13757 - Move the circuit build timeout tracking code from circuitbuild.c
13759 - Source files taken from other packages now reside in src/ext;
13760 previously they were scattered around the rest of Tor.
13761 - Move the generic "config" code into a new file, and have "config.c"
13762 hold only torrc- and state-related code. Resolves ticket 6823.
13763 - Move the core of our "choose a weighted element at random" logic
13764 into its own function, and give it unit tests. Now the logic is
13765 testable, and a little less fragile too.
13766 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
13767 - Move last_reachable and testing_since from routerinfo_t to node_t.
13768 Implements ticket 5529.
13769 - Add replaycache_t structure, functions and unit tests, then refactor
13770 rend_service_introduce() to be more clear to read, improve, debug,
13771 and test. Resolves bug 6177.
13774 - Remove some now-needless code that tried to aggressively flush
13775 OR connections as data was added to them. Since 0.2.0.1-alpha, our
13776 cell queue logic has saved us from the failure mode that this code
13777 was supposed to prevent. Removing this code will limit the number
13778 of baroque control flow paths through Tor's network logic. Reported
13779 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
13780 - Remove unused code for parsing v1 directories and "running routers"
13781 documents. Fixes bug 6887.
13782 - Remove the marshalling/unmarshalling code for sending requests to
13783 cpuworkers over a socket, and instead just send structs. The
13784 recipient will always be the same Tor binary as the sender, so
13785 any encoding is overkill.
13786 - Remove the testing_since field of node_t, which hasn't been used
13787 for anything since 0.2.0.9-alpha.
13788 - Finally remove support for malloc_good_size and malloc_usable_size.
13789 We had hoped that these functions would let us eke a little more
13790 memory out of our malloc implementation. Unfortunately, the only
13791 implementations that provided these functions are also ones that
13792 are already efficient about not overallocation: they never got us
13793 more than 7 or so bytes per allocation. Removing them saves us a
13794 little code complexity and a nontrivial amount of build complexity.
13797 Changes in version 0.2.3.25 - 2012-11-19
13798 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
13799 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
13800 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
13801 programmer, and friend. Unstinting in his dedication to the cause of
13802 freedom, he inspired and helped many of us as we began our work on
13803 anonymity, and inspires us still. Please honor his memory by writing
13804 software to protect people's freedoms, and by helping others to do so.
13806 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
13807 significantly reduced directory overhead (via microdescriptors),
13808 enormous crypto performance improvements for fast relays on new
13809 enough hardware, a new v3 TLS handshake protocol that can better
13810 resist fingerprinting, support for protocol obfuscation plugins (aka
13811 pluggable transports), better scalability for hidden services, IPv6
13812 support for bridges, performance improvements like allowing clients
13813 to skip the first round-trip on the circuit ("optimistic data") and
13814 refilling token buckets more often, a new "stream isolation" design
13815 to isolate different applications on different circuits, and many
13816 stability, security, and privacy fixes.
13818 Major features (v3 directory protocol):
13819 - Clients now use microdescriptors instead of regular descriptors
13820 to build circuits. Microdescriptors are authority-generated
13821 summaries of regular descriptors' contents, designed to change very
13822 rarely (see proposal 158 for details). This feature is designed
13823 to save bandwidth, especially for clients on slow internet
13824 connections. Use "UseMicrodescriptors 0" to disable it.
13825 - Caches now download, cache, and serve microdescriptors, as well
13826 as multiple "flavors" of the consensus, including a flavor that
13827 describes microdescriptors.
13829 o Major features (build hardening):
13830 - Enable gcc and ld hardening by default. Resolves ticket 5210.
13832 o Major features (relay scaling):
13833 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
13834 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
13835 vectorized AES implementations as appropriate. These can be much,
13836 much faster than other AES implementations.
13837 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
13838 implementation. It makes AES_CTR about 7% faster than our old one
13839 (which was about 10% faster than the one OpenSSL used to provide).
13840 Resolves ticket 4526.
13841 - Use OpenSSL's EVP interface for AES encryption, so that all AES
13842 operations can use hardware acceleration (if present). Resolves
13844 - Unconditionally use OpenSSL's AES implementation instead of our
13845 old built-in one. OpenSSL's AES has been better for a while, and
13846 relatively few servers should still be on any version of OpenSSL
13847 that doesn't have good optimized assembly AES.
13849 o Major features (blocking resistance):
13850 - Update TLS cipher list to match Firefox 8 and later. Resolves
13852 - Remove support for clients falsely claiming to support standard
13853 ciphersuites that they can actually provide. As of modern OpenSSL
13854 versions, it's not necessary to fake any standard ciphersuite,
13855 and doing so prevents us from using better ciphersuites in the
13856 future, since servers can't know whether an advertised ciphersuite
13857 is really supported or not. Some hosts -- notably, ones with very
13858 old versions of OpenSSL or where OpenSSL has been built with ECC
13859 disabled -- will stand out because of this change; TBB users should
13860 not be affected. Implements the client side of proposal 198.
13861 - Implement a new handshake protocol (v3) for authenticating Tors to
13862 each other over TLS. It should be more resistant to fingerprinting
13863 than previous protocols, and should require less TLS hacking for
13864 future Tor implementations. Implements proposal 176.
13865 - Allow variable-length padding cells, to disguise the length of
13866 Tor's TLS records. Implements part of proposal 184.
13867 - While we're trying to bootstrap, record how many TLS connections
13868 fail in each state, and report which states saw the most failures
13869 in response to any bootstrap failures. This feature may speed up
13870 diagnosis of censorship events. Implements ticket 3116.
13872 o Major features (pluggable transports):
13873 - Clients and bridges can now be configured to use a separate
13874 "transport" proxy. This approach makes the censorship arms race
13875 easier by allowing bridges to use protocol obfuscation plugins.
13876 Implements proposal 180 (tickets 2841 and 3472).
13878 o Major features (DoS resistance):
13879 - Now that Tor 0.2.0.x is completely deprecated, enable the final
13880 part of "Proposal 110: Avoiding infinite length circuits" by
13881 refusing all circuit-extend requests that do not use a relay_early
13882 cell. This change helps Tor resist a class of denial-of-service
13883 attacks by limiting the maximum circuit length.
13884 - Tear down the circuit if we get an unexpected SENDME cell. Clients
13885 could use this trick to make their circuits receive cells faster
13886 than our flow control would have allowed, or to gum up the network,
13887 or possibly to do targeted memory denial-of-service attacks on
13888 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
13889 from July 2002, before the release of Tor 0.0.0.
13891 o Major features (hidden services):
13892 - Adjust the number of introduction points that a hidden service
13893 will try to maintain based on how long its introduction points
13894 remain in use and how many introductions they handle. Fixes
13896 - Add a "tor2web mode" for clients that want to connect to hidden
13897 services non-anonymously (and possibly more quickly). As a safety
13898 measure to try to keep users from turning this on without knowing
13899 what they are doing, tor2web mode must be explicitly enabled at
13900 compile time, and a copy of Tor compiled to run in tor2web mode
13901 cannot be used as a normal Tor client. Implements feature 2553.
13903 o Major features (IPv6):
13904 - Clients can now connect to private bridges over IPv6. Bridges
13905 still need at least one IPv4 address in order to connect to
13906 other relays. Note that we don't yet handle the case where the
13907 user has two bridge lines for the same bridge (one IPv4, one
13908 IPv6). Implements parts of proposal 186.
13910 o Major features (directory authorities):
13911 - Use a more secure consensus parameter voting algorithm. Now at
13912 least three directory authorities or a majority of them must
13913 vote on a given parameter before it will be included in the
13914 consensus. Implements proposal 178.
13915 - Remove the artificially low cutoff of 20KB to guarantee the Fast
13916 flag. In the past few years the average relay speed has picked
13917 up, and while the "top 7/8 of the network get the Fast flag" and
13918 "all relays with 20KB or more of capacity get the Fast flag" rules
13919 used to have the same result, now the top 7/8 of the network has
13920 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
13922 o Major features (performance):
13923 - Exit nodes now accept and queue data on not-yet-connected streams.
13924 Previously, the client wasn't allowed to send data until the
13925 stream was connected, which slowed down all connections. This
13926 change will enable clients to perform a "fast-start" on streams
13927 and send data without having to wait for a confirmation that the
13928 stream has opened. Patch from Ian Goldberg; implements the server
13929 side of Proposal 174.
13930 - When using an exit relay running 0.2.3.x, clients can now
13931 "optimistically" send data before the exit relay reports that
13932 the stream has opened. This saves a round trip when starting
13933 connections where the client speaks first (such as web browsing).
13934 This behavior is controlled by a consensus parameter (currently
13935 disabled). To turn it on or off manually, use the "OptimisticData"
13936 torrc option. Implements proposal 181; code by Ian Goldberg.
13937 - Add a new TokenBucketRefillInterval option to refill token buckets
13938 more frequently than once per second. This should improve network
13939 performance, alleviate queueing problems, and make traffic less
13940 bursty. Implements proposal 183; closes ticket 3630. Design by
13941 Florian Tschorsch and Björn Scheuermann; implementation by
13943 - Raise the threshold of server descriptors needed (75%) and exit
13944 server descriptors needed (50%) before we will declare ourselves
13945 bootstrapped. This will make clients start building circuits a
13946 little later, but makes the initially constructed circuits less
13947 skewed and less in conflict with further directory fetches. Fixes
13950 o Major features (relays):
13951 - Relays now try regenerating and uploading their descriptor more
13952 frequently if they are not listed in the consensus, or if the
13953 version of their descriptor listed in the consensus is too
13954 old. This fix should prevent situations where a server declines
13955 to re-publish itself because it has done so too recently, even
13956 though the authorities decided not to list its recent-enough
13957 descriptor. Fix for bug 3327.
13959 o Major features (stream isolation):
13960 - You can now configure Tor so that streams from different
13961 applications are isolated on different circuits, to prevent an
13962 attacker who sees your streams as they leave an exit node from
13963 linking your sessions to one another. To do this, choose some way
13964 to distinguish the applications: have them connect to different
13965 SocksPorts, or have one of them use SOCKS4 while the other uses
13966 SOCKS5, or have them pass different authentication strings to the
13967 SOCKS proxy. Then, use the new SocksPort syntax to configure the
13968 degree of isolation you need. This implements Proposal 171.
13969 - There's a new syntax for specifying multiple client ports (such as
13970 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
13971 multiple *Port entries with full addr:port syntax on each.
13972 The old *ListenAddress format is still supported, but you can't
13973 mix it with the new *Port syntax.
13975 o Major features (bufferevents):
13976 - Tor can now optionally build with the "bufferevents" buffered IO
13977 backend provided by Libevent 2. To use this feature, make sure you
13978 have the latest possible version of Libevent, and pass the
13979 --enable-bufferevents flag to configure when building Tor from
13980 source. This feature will make our networking code more flexible,
13981 let us stack layers on each other, and let us use more efficient
13982 zero-copy transports where available.
13983 - Add experimental support for running on Windows with IOCP and no
13984 kernel-space socket buffers. This feature is controlled by a new
13985 "UserspaceIOCPBuffers" config option (off by default), which has
13986 no effect unless Tor has been built with bufferevents enabled,
13987 you're running on Windows, and you've set "DisableIOCP 0". In the
13988 long run, this may help solve or mitigate bug 98.
13990 o Major features (path selection):
13991 - The EntryNodes option can now include country codes like {de} or IP
13992 addresses or network masks. Previously we had disallowed these
13993 options because we didn't have an efficient way to keep the list up
13994 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
13997 o Major features (port forwarding):
13998 - Add support for automatic port mapping on the many home routers
13999 that support NAT-PMP or UPnP. To build the support code, you'll
14000 need to have the libnatpnp library and/or the libminiupnpc library,
14001 and you'll need to enable the feature specifically by passing
14002 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
14003 it on, use the new PortForwarding option.
14005 o Major features (logging):
14006 - Add a new 'Heartbeat' log message type to periodically log a message
14007 describing Tor's status at level Notice. This feature is meant for
14008 operators who log at notice, and want to make sure that their Tor
14009 server is still working. Implementation by George Kadianakis.
14010 - Make logging resolution configurable with a new LogTimeGranularity
14011 option, and change the default from 1 millisecond to 1 second.
14012 Implements enhancement 1668.
14014 o Major features (other):
14015 - New "DisableNetwork" config option to prevent Tor from launching any
14016 connections or accepting any connections except on a control port.
14017 Bundles and controllers can set this option before letting Tor talk
14018 to the rest of the network, for example to prevent any connections
14019 to a non-bridge address. Packages like Orbot can also use this
14020 option to instruct Tor to save power when the network is off.
14021 - Try to use system facilities for enumerating local interface
14022 addresses, before falling back to our old approach (which was
14023 binding a UDP socket, and calling getsockname() on it). That
14024 approach was scaring OS X users whose draconian firewall
14025 software warned about binding to UDP sockets regardless of
14026 whether packets were sent. Now we try to use getifaddrs(),
14027 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
14028 system supports. Resolves ticket 1827.
14029 - Add experimental support for a "defaults" torrc file to be parsed
14030 before the regular torrc. Torrc options override the defaults file's
14031 options in the same way that the command line overrides the torrc.
14032 The SAVECONF controller command saves only those options which
14033 differ between the current configuration and the defaults file. HUP
14034 reloads both files. Implements task 4552.
14036 o New directory authorities:
14037 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
14038 authority. Closes ticket 5749.
14040 o Security/privacy fixes:
14041 - Avoid read-from-freed-memory and double-free bugs that could occur
14042 when a DNS request fails while launching it. Fixes bug 6480;
14043 bugfix on 0.2.0.1-alpha.
14044 - Reject any attempt to extend to an internal address. Without
14045 this fix, a router could be used to probe addresses on an internal
14046 network to see whether they were accepting connections. Fixes bug
14047 6710; bugfix on 0.0.8pre1.
14048 - Close any connection that sends unrecognized junk before the TLS
14049 handshake. Solves an issue noted in bug 4369.
14050 - The advertised platform of a relay now includes only its operating
14051 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
14052 its service pack level (for Windows) or its CPU architecture
14053 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
14054 can insert an extra string in the platform line by setting the
14055 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
14056 - Disable TLS session tickets. OpenSSL's implementation was giving
14057 our TLS session keys the lifetime of our TLS context objects, when
14058 perfect forward secrecy would want us to discard anything that
14059 could decrypt a link connection as soon as the link connection
14060 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
14061 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
14062 - Tor tries to wipe potentially sensitive data after using it, so
14063 that if some subsequent security failure exposes Tor's memory,
14064 the damage will be limited. But we had a bug where the compiler
14065 was eliminating these wipe operations when it decided that the
14066 memory was no longer visible to a (correctly running) program,
14067 hence defeating our attempt at defense in depth. We fix that
14068 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
14069 is unlikely to optimize away. Future versions of Tor may use
14070 a less ridiculously heavy approach for this. Fixes bug 7352.
14071 Reported in an article by Andrey Karpov.
14073 o Major bugfixes (crashes and asserts):
14074 - Avoid a pair of double-free and use-after-mark bugs that can
14075 occur with certain timings in canceled and re-received DNS
14076 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
14077 - Fix a denial of service attack by which any directory authority
14078 could crash all the others, or by which a single v2 directory
14079 authority could crash everybody downloading v2 directory
14080 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
14081 - Fix an assert that directory authorities could trigger on sighup
14082 during some configuration state transitions. We now don't treat
14083 it as a fatal error when the new descriptor we just generated in
14084 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
14085 - Avoid segfault when starting up having run with an extremely old
14086 version of Tor and parsing its state file. Fixes bug 6801; bugfix
14089 o Major bugfixes (clients):
14090 - If we are unable to find any exit that supports our predicted ports,
14091 stop calling them predicted, so that we don't loop and build
14092 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
14093 which introduced predicted ports.
14094 - Check at each new consensus whether our entry guards were picked
14095 long enough ago that we should rotate them. Previously, we only
14096 did this check at startup, which could lead to us holding a guard
14097 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
14098 - When fetching a bridge descriptor from a bridge authority,
14099 always do so anonymously, whether we have been able to open
14100 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
14101 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
14102 but we'll need to wait for bug 6010 before it's actually usable.
14104 o Major bugfixes (directory voting):
14105 - Check more thoroughly to prevent a rogue authority from
14106 double-voting on any consensus directory parameter. Previously,
14107 authorities would crash in this case if the total number of
14108 votes for any parameter exceeded the number of active voters,
14109 but would let it pass otherwise. Partially fixes bug 5786; bugfix
14111 - When computing weight parameters, behave more robustly in the
14112 presence of a bad bwweightscale value. Previously, the authorities
14113 would crash if they agreed on a sufficiently broken weight_scale
14114 value; now, they use a reasonable default and carry on. Fixes the
14115 rest of bug 5786; bugfix on 0.2.2.17-alpha.
14116 - If authorities are unable to get a v2 consensus document from other
14117 directory authorities, they no longer fall back to fetching
14118 them from regular directory caches. Fixes bug 5635; bugfix on
14119 0.2.2.26-beta, where routers stopped downloading v2 consensus
14120 documents entirely.
14122 o Major bugfixes (relays):
14123 - Fix a bug handling SENDME cells on nonexistent streams that could
14124 result in bizarre window values. Report and patch contributed
14125 pseudonymously. Fixes part of bug 6271. This bug was introduced
14126 before the first Tor release, in svn commit r152.
14127 - Don't update the AccountingSoftLimitHitAt state file entry whenever
14128 tor gets started. This prevents a wrong average bandwidth
14129 estimate, which would cause relays to always start a new accounting
14130 interval at the earliest possible moment. Fixes bug 2003; bugfix
14131 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
14132 immensely in tracking this bug down.
14133 - Fix a possible crash bug when checking for deactivated circuits
14134 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
14135 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
14136 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
14137 connections. This change should allow busy exit relays to stop
14138 running out of available sockets as quickly. Fixes bug 4950;
14139 bugfix on 0.2.2.26-beta.
14141 o Major bugfixes (blocking resistance):
14142 - Bridges no longer include their address in NETINFO cells on outgoing
14143 OR connections, to allow them to blend in better with clients.
14144 Removes another avenue for enumerating bridges. Reported by
14145 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
14146 cells were introduced.
14147 - Warn the user when HTTPProxy, but no other proxy type, is
14148 configured. This can cause surprising behavior: it doesn't send
14149 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
14150 directory traffic only. Resolves ticket 4663.
14152 o Major bugfixes (hidden services):
14153 - Improve hidden service robustness: when an attempt to connect to
14154 a hidden service ends, be willing to refetch its hidden service
14155 descriptors from each of the HSDir relays responsible for them
14156 immediately. Previously, we would not consider refetching the
14157 service's descriptors from each HSDir for 15 minutes after the last
14158 fetch, which was inconvenient if the hidden service was not running
14159 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
14160 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
14161 They used to check that the timestamp was within 30 minutes
14162 of their system clock, so they could cap the size of their
14163 replay-detection cache, but that approach unnecessarily refused
14164 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
14165 the v3 intro-point protocol (the first one which sent a timestamp
14166 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
14167 - When one of a hidden service's introduction points appears to be
14168 unreachable, stop trying it. Previously, we would keep trying
14169 to build circuits to the introduction point until we lost the
14170 descriptor, usually because the user gave up and restarted Tor.
14171 Fixes part of bug 3825.
14173 o Changes to default torrc file:
14174 - Stop listing "socksport 9050" in torrc.sample. We open a socks
14175 port on 9050 by default anyway, so this should not change anything
14177 - Stop mentioning the deprecated *ListenAddress options in
14178 torrc.sample. Fixes bug 5438.
14179 - Document unit of bandwidth-related options in sample torrc.
14181 - Fix broken URLs in the sample torrc file, and tell readers about
14182 the OutboundBindAddress, ExitPolicyRejectPrivate, and
14183 PublishServerDescriptor options. Addresses bug 4652.
14185 o Minor features (directory authorities):
14186 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
14187 change when the authority is deciding whether to accept a newly
14188 uploaded descriptor. Implements ticket 6423.
14189 - Directory authorities are now a little more lenient at accepting
14190 older router descriptors, or newer router descriptors that don't
14191 make big changes. This should help ameliorate past and future
14192 issues where routers think they have uploaded valid descriptors,
14193 but the authorities don't think so. Fix for ticket 2479.
14194 - Authority operators can now vote for all relays in a given
14195 set of countries to be BadDir/BadExit/Invalid/Rejected.
14196 - Provide two consensus parameters (FastFlagMinThreshold and
14197 FastFlagMaxThreshold) to control the range of allowable bandwidths
14198 for the Fast directory flag. These allow authorities to run
14199 experiments on appropriate requirements for being a "Fast" node.
14200 The AuthDirFastGuarantee config value still applies. Implements
14203 o Minor features (bridges / bridge authorities):
14204 - Make bridge SSL certificates a bit more stealthy by using random
14205 serial numbers, in the same fashion as OpenSSL when generating
14206 self-signed certificates. Implements ticket 4584.
14207 - Tag a bridge's descriptor as "never to be sent unencrypted".
14208 This shouldn't matter, since bridges don't open non-anonymous
14209 connections to the bridge authority and don't allow unencrypted
14210 directory connections from clients, but we might as well make
14211 sure. Closes bug 5139.
14212 - The Bridge Authority now writes statistics on how many bridge
14213 descriptors it gave out in total, and how many unique descriptors
14214 it gave out. It also lists how often the most and least commonly
14215 fetched descriptors were given out, as well as the median and
14216 25th/75th percentile. Implements tickets 4200 and 4294.
14218 o Minor features (IPv6):
14219 - Make the code that clients use to detect an address change be
14220 IPv6-aware, so that it won't fill clients' logs with error
14221 messages when trying to get the IPv4 address of an IPv6
14222 connection. Implements ticket 5537.
14223 - Relays now understand an IPv6 address when they get one from a
14224 directory server. Resolves ticket 4875.
14226 o Minor features (hidden services):
14227 - Expire old or over-used hidden service introduction points.
14228 Required by fix for bug 3460.
14229 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
14230 public key replay-detection cache from 60 minutes to 5 minutes. This
14231 replay-detection cache is now used only to detect multiple
14232 INTRODUCE2 cells specifying the same rendezvous point, so we can
14233 avoid launching multiple simultaneous attempts to connect to it.
14234 - When a hidden service's introduction point times out, consider
14235 trying it again during the next attempt to connect to the
14236 HS. Previously, we would not try it again unless a newly fetched
14237 descriptor contained it. Required by fixes for bugs 1297 and 3825.
14239 o Minor features (relays):
14240 - Relays now include a reason for regenerating their descriptors
14241 in an HTTP header when uploading to the authorities. This will
14242 make it easier to debug descriptor-upload issues in the future.
14243 - Turn on directory request statistics by default and include them in
14244 extra-info descriptors. Don't break if we have no GeoIP database.
14245 - Replace files in stats/ rather than appending to them. Now that we
14246 include statistics in extra-info descriptors, it makes no sense to
14247 keep old statistics forever. Implements ticket 2930.
14248 - Relays that set "ConnDirectionStatistics 1" write statistics on the
14249 bidirectional use of connections to disk every 24 hours.
14250 - Add a GeoIP file digest to the extra-info descriptor. Implements
14253 o Minor features (new config options):
14254 - New config option "DynamicDHGroups" (disabled by default) provides
14255 each bridge with a unique prime DH modulus to be used during
14256 SSL handshakes. This option attempts to help against censors
14257 who might use the Apache DH modulus as a static identifier for
14258 bridges. Addresses ticket 4548.
14259 - New config option "DisableDebuggerAttachment" (on by default)
14260 to prevent basic debugging attachment attempts by other processes.
14261 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
14262 - Ordinarily, Tor does not count traffic from private addresses (like
14263 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
14264 There is now a new option, CountPrivateBandwidth, to disable this
14265 behavior. Patch from Daniel Cagara.
14267 o Minor features (different behavior for old config options):
14268 - Allow MapAddress directives to specify matches against super-domains,
14269 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
14270 Implements issue 933.
14271 - Don't disable the DirPort when we cannot exceed our AccountingMax
14272 limit during this interval because the effective bandwidthrate is
14273 low enough. This is useful in a situation where AccountMax is only
14274 used as an additional safeguard or to provide statistics.
14275 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
14276 implements ticket 3439.
14277 - When configuring a large set of nodes in EntryNodes, and there are
14278 enough of them listed as Guard so that we don't need to consider
14279 the non-guard entries, prefer the ones listed with the Guard flag.
14280 - If you set the NumCPUs option to 0, Tor will now try to detect how
14281 many CPUs you have. This is the new default behavior.
14282 - The NodeFamily option -- which let you declare that you want to
14283 consider nodes to be part of a family whether they list themselves
14284 that way or not -- now allows IP address ranges and country codes.
14286 o Minor features (new command-line config behavior):
14287 - Slightly change behavior of "list" options (that is, config
14288 options that can appear more than once) when they appear both in
14289 torrc and on the command line. Previously, the command-line options
14290 would be appended to the ones from torrc. Now, the command-line
14291 options override the torrc options entirely. This new behavior
14292 allows the user to override list options (like exit policies and
14293 ports to listen on) from the command line, rather than simply
14294 appending to the list.
14295 - You can get the old (appending) command-line behavior for "list"
14296 options by prefixing the option name with a "+".
14297 - You can remove all the values for a "list" option from the command
14298 line without adding any new ones by prefixing the option name
14301 o Minor features (controller, new events):
14302 - Extend the control protocol to report flags that control a circuit's
14303 path selection in CIRC events and in replies to 'GETINFO
14304 circuit-status'. Implements part of ticket 2411.
14305 - Extend the control protocol to report the hidden service address
14306 and current state of a hidden-service-related circuit in CIRC
14307 events and in replies to 'GETINFO circuit-status'. Implements part
14309 - Include the creation time of a circuit in CIRC and CIRC2
14310 control-port events and the list produced by the 'GETINFO
14311 circuit-status' control-port command.
14312 - Add a new CONF_CHANGED event so that controllers can be notified
14313 of any configuration changes made by other controllers, or by the
14314 user. Implements ticket 1692.
14315 - Add a new SIGNAL event to the controller interface so that
14316 controllers can be notified when Tor handles a signal. Resolves
14317 issue 1955. Patch by John Brooks.
14319 o Minor features (controller, new getinfo options):
14320 - Expose our view of whether we have gone dormant to the controller,
14321 via a new "GETINFO dormant" value. Torbutton and other controllers
14322 can use this to avoid doing periodic requests through Tor while
14323 it's dormant (bug 4718). Resolves ticket 5954.
14324 - Add a new GETINFO option to get total bytes read and written. Patch
14325 from pipe, revised by atagar. Resolves ticket 2345.
14326 - Implement new GETINFO controller fields to provide information about
14327 the Tor process's pid, euid, username, and resource limits.
14329 o Minor features (controller, other):
14330 - Allow controllers to request an event notification whenever a
14331 circuit is cannibalized or its purpose is changed. Implements
14332 part of ticket 3457.
14333 - Use absolute path names when reporting the torrc filename in the
14334 control protocol, so a controller can more easily find the torrc
14335 file. Resolves bug 1101.
14336 - When reporting the path to the cookie file to the controller,
14337 give an absolute path. Resolves ticket 4881.
14339 o Minor features (log messages):
14340 - Add more information to a log statement that might help track down
14341 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
14342 non-IP address" messages (or any Bug messages, for that matter!),
14343 please let us know about it.
14344 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
14345 EntryNodes will have no effect. Resolves issue 2571.
14346 - Try to make the introductory warning message that Tor prints on
14347 startup more useful for actually finding help and information.
14348 Resolves ticket 2474.
14349 - When the system call to create a listener socket fails, log the
14350 error message explaining why. This may help diagnose bug 4027.
14352 o Minor features (other):
14353 - When we fail to initialize Libevent, retry with IOCP disabled so we
14354 don't need to turn on multi-threading support in Libevent, which in
14355 turn requires a working socketpair(). This is a workaround for bug
14356 4457, which affects Libevent versions from 2.0.1-alpha through
14358 - When starting as root and then changing our UID via the User
14359 control option, and we have a ControlSocket configured, make sure
14360 that the ControlSocket is owned by the same account that Tor will
14361 run under. Implements ticket 3421; fix by Jérémy Bobbio.
14362 - Accept attempts to include a password authenticator in the
14363 handshake, as supported by SOCKS5. This handles SOCKS clients that
14364 don't know how to omit a password when authenticating. Resolves
14366 - Check for and recover from inconsistency in the microdescriptor
14367 cache. This will make it harder for us to accidentally free a
14368 microdescriptor without removing it from the appropriate data
14369 structures. Fixes issue 3135; issue noted by "wanoskarnet".
14370 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
14372 o Minor bugfixes (code security):
14373 - Prevent a null-pointer dereference when receiving a data cell
14374 for a nonexistent stream when the circuit in question has an
14375 empty deliver window. We don't believe this is triggerable,
14376 since we don't currently allow deliver windows to become empty,
14377 but the logic is tricky enough that it's better to make the code
14378 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
14379 - Fix a (harmless) integer overflow in cell statistics reported by
14380 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
14381 - Fix our implementation of crypto_random_hostname() so it can't
14382 overflow on ridiculously large inputs. (No Tor version has ever
14383 provided this kind of bad inputs, but let's be correct in depth.)
14384 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
14385 - Add a (probably redundant) memory clear between iterations of
14386 the router status voting loop, to prevent future coding errors
14387 where data might leak between iterations of the loop. Resolves
14390 o Minor bugfixes (wrapper functions):
14391 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
14392 utility function used in the control-port code). This shouldn't
14393 ever happen unless Tor is completely out of memory, but if it did
14394 happen and Tor somehow recovered from it, Tor could have sent a log
14395 message to a control port in the middle of a reply to a controller
14396 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
14397 - Fix some (not actually triggerable) buffer size checks in usage of
14398 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
14400 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
14401 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
14402 - Enforce correct return behavior of tor_vsscanf() when the '%%'
14403 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
14404 - Make our replacement implementation of strtok_r() compatible with
14405 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
14406 bugfix on 0.2.2.1-alpha.
14407 - Find more places in the code that should have been testing for
14408 invalid sockets using the SOCKET_OK macro. Required for a fix
14409 for bug 4533. Bugfix on 0.2.2.28-beta.
14411 o Minor bugfixes (code correctness):
14412 - Check return value of fputs() when writing authority certificate
14413 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
14414 - When building Tor on Windows with -DUNICODE (not default), ensure
14415 that error messages, filenames, and DNS server names are always
14416 NUL-terminated when we convert them to a single-byte encoding.
14417 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
14418 - Fix a memory leak when trying to launch a DNS request when the
14419 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
14421 - Correct file sizes when reading binary files on Cygwin, to avoid
14422 a bug where Tor would fail to read its state file. Fixes bug 6844;
14423 bugfix on 0.1.2.7-alpha.
14424 - Make sure to set *socket_error in all error cases in
14425 connection_connect(), so it can't produce a warning about
14426 errno being zero from errno_to_orconn_end_reason(). Bugfix on
14427 0.2.1.1-alpha; resolves ticket 6028.
14428 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
14429 bug 4532; found by "troll_un".
14431 o Minor bugfixes (clients):
14432 - Allow one-hop directory-fetching circuits the full "circuit build
14433 timeout" period, rather than just half of it, before failing them
14434 and marking the relay down. This fix should help reduce cases where
14435 clients declare relays (or worse, bridges) unreachable because
14436 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
14437 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
14439 - Ensure we don't cannibalize circuits that are longer than three hops
14440 already, so we don't end up making circuits with 5 or more
14441 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
14442 0.1.0.1-rc which introduced cannibalization.
14444 o Minor bugfixes (relays):
14445 - Don't publish a new relay descriptor when we reload our onion key,
14446 unless the onion key has actually changed. Fixes bug 3263 and
14447 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
14448 - When relays refuse a "create" cell because their queue of pending
14449 create cells is too big (typically because their cpu can't keep up
14450 with the arrival rate), send back reason "resource limit" rather
14451 than reason "internal", so network measurement scripts can get a
14452 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
14453 - Exit nodes don't need to fetch certificates for authorities that
14454 they don't recognize; only directory authorities, bridges,
14455 and caches need to do that. Fixes part of bug 2297; bugfix on
14458 o Minor bugfixes (directory authority / mirrors):
14459 - Avoid O(n^2) performance characteristics when parsing a large
14460 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
14461 - Authorities no longer include any router in their microdescriptor
14462 consensuses for which they couldn't generate or agree on a
14463 microdescriptor. Fixes the second piece of bug 6404; fix on
14465 - When checking for requested signatures on the latest consensus
14466 before serving it to a client, make sure to check the right
14467 consensus flavor. Bugfix on 0.2.2.6-alpha.
14468 - Fix an edge case where TestingTorNetwork is set but the authorities
14469 and relays all have an uptime of zero, so the private Tor network
14470 could briefly lack support for hidden services. Fixes bug 3886;
14471 bugfix on 0.2.2.18-alpha.
14472 - Directory caches no longer refuse to clean out descriptors because
14473 of missing v2 networkstatus documents, unless they're configured
14474 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
14475 0.2.2.26-beta. Patch by Daniel Bryg.
14476 - Don't serve or accept v2 hidden service descriptors over a relay's
14477 DirPort. It's never correct to do so, and disabling it might
14478 make it more annoying to exploit any bugs that turn up in the
14479 descriptor-parsing code. Fixes bug 7149.
14481 o Minor bugfixes (hidden services, client-side):
14482 - Assert that hidden-service-related operations are not performed
14483 using single-hop circuits. Previously, Tor would assert that
14484 client-side streams are not attached to single-hop circuits,
14485 but not that other sensitive operations on the client and service
14486 side are not performed using single-hop circuits. Fixes bug 3332;
14488 - Avoid undefined behavior when parsing the list of supported
14489 rendezvous/introduction protocols in a hidden service descriptor.
14490 Previously, Tor would have confused (as-yet-unused) protocol version
14491 numbers greater than 32 with lower ones on many platforms. Fixes
14492 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
14493 - Don't close hidden service client circuits which have almost
14494 finished connecting to their destination when they reach
14495 the normal circuit-build timeout. Previously, we would close
14496 introduction circuits which are waiting for an acknowledgement
14497 from the introduction point, and rendezvous circuits which have
14498 been specified in an INTRODUCE1 cell sent to a hidden service,
14499 after the normal CBT. Now, we mark them as 'timed out', and launch
14500 another rendezvous attempt in parallel. This behavior change can
14501 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
14502 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
14504 o Minor bugfixes (hidden services, service-side):
14505 - Don't close hidden-service-side rendezvous circuits when they
14506 reach the normal circuit-build timeout. This behavior change can
14507 be disabled using the new
14508 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
14509 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
14510 - Don't launch more than 10 service-side introduction-point circuits
14511 for a hidden service in five minutes. Previously, we would consider
14512 launching more introduction-point circuits if at least one second
14513 had passed without any introduction-point circuits failing. Fixes
14514 bug 4607; bugfix on 0.0.7pre1.
14516 o Minor bugfixes (config option behavior):
14517 - If the user tries to set MyFamily on a bridge, refuse to
14518 do so, and warn about the security implications. Fixes bug 4657;
14519 bugfix on 0.2.0.3-alpha.
14520 - The "--quiet" and "--hush" options now apply not only to Tor's
14521 behavior before logs are configured, but also to Tor's behavior in
14522 the absence of configured logs. Fixes bug 3550; bugfix on
14524 - Change the AllowDotExit rules so they should actually work.
14525 We now enforce AllowDotExit only immediately after receiving an
14526 address via SOCKS or DNSPort: other sources are free to provide
14527 .exit addresses after the resolution occurs. Fixes bug 3940;
14528 bugfix on 0.2.2.1-alpha.
14529 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
14530 don't depend on the consensus parameters or compute adaptive
14531 timeouts when it is disabled. Fixes bug 5049; bugfix on
14533 - After we pick a directory mirror, we would refuse to use it if
14534 it's in our ExcludeExitNodes list, resulting in mysterious failures
14535 to bootstrap for people who just wanted to avoid exiting from
14536 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
14537 - When told to add a bridge with the same digest as a preexisting
14538 bridge but a different addr:port, change the addr:port as
14539 requested. Previously we would not notice the change. Fixes half
14540 of bug 5603; fix on 0.2.2.26-beta.
14542 o Minor bugfixes (controller):
14543 - Allow manual 'authenticate' commands to the controller interface
14544 from netcat (nc) as well as telnet. We were rejecting them because
14545 they didn't come with the expected whitespace at the end of the
14546 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
14547 - Report a real bootstrap problem to the controller on router
14548 identity mismatch. Previously we just said "foo", which probably
14549 made a lot of sense at the time. Fixes bug 4169; bugfix on
14551 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
14552 option is set to 0 (which Vidalia version 0.2.16 now does when
14553 a SAVECONF attempt fails), perform other actions that SIGHUP
14554 usually causes (like reopening the logs). Fixes bug 5095; bugfix
14556 - Correctly handle checking the permissions on the parent
14557 directory of a control socket in the root directory. Bug found
14558 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
14560 - End AUTHCHALLENGE error messages (in the control protocol) with
14561 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
14563 o Minor bugfixes (network reading/writing):
14564 - Disable writing on marked-for-close connections when they are
14565 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
14566 bug 5263; bugfix on 0.0.2pre13, where we first added a special
14567 case for flushing marked connections.
14568 - Make sure that there are no unhandled pending TLS errors before
14569 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
14570 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
14571 Bugfix on 0.1.0.5-rc; fixes bug 4528.
14572 - Detect SSL handshake even when the initial attempt to write the
14573 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
14574 - If the client fails to set a reasonable set of ciphersuites
14575 during its v2 handshake renegotiation, allow the renegotiation to
14576 continue nevertheless (i.e. send all the required certificates).
14577 Fixes bug 4591; bugfix on 0.2.0.20-rc.
14579 o Minor bugfixes (other):
14580 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
14581 resource exhaustion, so that clients can adjust their load to
14582 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
14583 started using END_STREAM_REASON_RESOURCELIMIT.
14584 - Don't check for whether the address we're using for outbound
14585 connections has changed until after the outbound connection has
14586 completed. On Windows, getsockname() doesn't succeed until the
14587 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
14588 - Don't hold a Windows file handle open for every file mapping;
14589 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
14591 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
14592 bugfix on 0.2.1.10-alpha.
14593 - If we fail to write a microdescriptor to the disk cache, do not
14594 continue replacing the old microdescriptor file. Fixes bug 2954;
14595 bugfix on 0.2.2.6-alpha.
14597 o Minor bugfixes (log messages, path selection):
14598 - Downgrade "set buildtimeout to low value" messages to "info"
14599 severity; they were never an actual problem, there was never
14600 anything reasonable to do about them, and they tended to spam logs
14601 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
14602 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
14603 more information to it, so that we can track it down in case it
14604 returns again. Mitigates bug 5235.
14605 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
14606 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
14607 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
14608 - Issue a log message if a guard completes less than 40% of your
14609 circuits. Threshold is configurable by torrc option
14610 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
14611 additional, off-by-default code to disable guards which fail too
14612 many circuits. Addresses ticket 5458.
14614 o Minor bugfixes (log messages, client):
14615 - Downgrade "Got a certificate, but we already have it" log messages
14616 from warning to info, except when we're a dirauth. Fixes bug 5238;
14617 bugfix on 0.2.1.7-alpha.
14618 - Fix the log message describing how we work around discovering
14619 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
14620 4837; bugfix on 0.2.2.9-alpha.
14621 - When logging about a disallowed .exit name, do not also call it
14622 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
14623 - Fix a log message suggesting that people contact a non-existent
14624 email address. Fixes bug 3448.
14625 - Rephrase the log message emitted if the TestSocks check is
14626 successful. Patch from Fabian Keil; fixes bug 4094.
14627 - Log (at debug level) whenever a circuit's purpose is changed.
14628 - Log SSL state transitions at log level DEBUG, log domain
14629 HANDSHAKE. This can be useful for debugging censorship events.
14630 Implements ticket 3264.
14631 - We now log which torrc file we're using on startup. Implements
14633 - Rate-limit log messages when asked to connect anonymously to
14634 a private address. When these hit, they tended to hit fast and
14635 often. Also, don't bother trying to connect to addresses that we
14636 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
14637 reply makes us think we have been lied to, even when the address the
14638 client tried to connect to was "localhost." Resolves ticket 2822.
14640 o Minor bugfixes (log messages, non-client):
14641 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
14642 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
14643 - Don't log that we have "decided to publish new relay descriptor"
14644 unless we are actually publishing a descriptor. Fixes bug 3942;
14645 bugfix on 0.2.2.28-beta.
14646 - Log which authority we're missing votes from when we go to fetch
14647 them from the other auths.
14648 - Replace "Sending publish request" log messages with "Launching
14649 upload", so that they no longer confusingly imply that we're
14650 sending something to a directory we might not even be connected
14651 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
14652 - Warn when Tor is configured to use accounting in a way that can
14653 link a hidden service to some other hidden service or public
14654 address. Resolves ticket 6490.
14655 - Fix a minor formatting issue in one of tor-gencert's error messages.
14659 - Update to the latest version of the tinytest unit testing framework.
14660 This includes a couple of bugfixes that can be relevant for
14661 running forked unit tests on Windows, and removes all reserved
14663 - Avoid a false positive in the util/threads unit test by increasing
14664 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
14665 - Make it possible to set the TestingTorNetwork configuration
14666 option using AlternateDirAuthority and AlternateBridgeAuthority
14667 as an alternative to setting DirServer. Addresses ticket 6377.
14668 - Add a unit test for the environment_variable_names_equal() function.
14669 - A wide variety of new unit tests by Esteban Manchado Velázquez.
14670 - Numerous new unit tests for functions in util.c and address.c by
14672 - The long-disabled benchmark tests are now split into their own
14673 ./src/test/bench binary.
14674 - The benchmark tests can now use more accurate timers than
14675 gettimeofday() when such timers are available.
14676 - Use tt_assert(), not tor_assert(), for checking for test failures.
14677 This makes the unit tests more able to go on in the event that
14680 o Build improvements:
14681 - Use the dead_strip option when building Tor on OS X. This reduces
14682 binary size by almost 19% when linking openssl and libevent
14683 statically, which we do for Tor Browser Bundle.
14684 - Provide a better error message about possible OSX Asciidoc failure
14685 reasons. Fixes bug 6436.
14686 - Detect attempts to build Tor on (as yet hypothetical) versions
14687 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
14688 fix for bug 4533. Bugfix on 0.2.2.28-beta.
14689 - On Windows, we now define the _WIN32_WINNT macros only if they
14690 are not already defined. This lets the person building Tor decide,
14691 if they want, to require a later version of Windows.
14692 - Our autogen.sh script now uses autoreconf to launch autoconf,
14693 automake, and so on. This is more robust against some of the failure
14694 modes associated with running the autotools pieces on their own.
14695 - Running "make version" now displays the version of Tor that
14696 we're about to build. Idea from katmagic; resolves issue 4400.
14697 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
14698 on 0.2.2.4-alpha; fixes bug 3427.
14699 - New --enable-static-tor configure option for building Tor as
14700 statically as possible. Idea, general hackery and thoughts from
14701 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
14703 - Limited, experimental support for building with nmake and MSVC.
14705 o Build requirements:
14706 - Building Tor with bufferevent support now requires Libevent
14707 2.0.13-stable or later. Previous versions of Libevent had bugs in
14708 SSL-related bufferevents and related issues that would make Tor
14709 work badly with bufferevents. Requiring 2.0.13-stable also allows
14710 Tor with bufferevents to take advantage of Libevent APIs
14711 introduced after 2.0.8-rc.
14712 - Our build system requires automake 1.6 or later to create the
14713 Makefile.in files. Previously, you could have used 1.4.
14714 This only affects developers and people building Tor from git;
14715 people who build Tor from the source distribution without changing
14716 the Makefile.am files should be fine.
14717 - Detect when we try to build on a platform that doesn't define
14718 AF_UNSPEC to 0. We don't work there, so refuse to compile.
14720 o Build fixes (compile/link):
14721 - Format more doubles with %f, not %lf. Patch from grarpamp to make
14722 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
14724 - When building with --enable-static-tor on OpenBSD, do not
14725 erroneously attempt to link -lrt. Fixes bug 5103.
14726 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
14727 that IPv6 stuff will compile on MSVC, and compilation issues
14728 will be easier to track down. Fixes bug 5861.
14729 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
14730 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
14731 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
14732 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
14734 o Build fixes (other):
14735 - Use the _WIN32 macro throughout our code to detect Windows.
14736 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
14738 - Properly handle the case where the build-tree is not the same
14739 as the source tree when generating src/common/common_sha1.i,
14740 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
14741 bugfix on 0.2.0.1-alpha.
14742 - During configure, search for library containing cos function as
14743 libm lives in libcore on some platforms (BeOS/Haiku). Linking
14744 against libm was hard-coded before. Fixes the first part of bug
14745 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
14747 - Prevent a false positive from the check-spaces script, by disabling
14748 the "whitespace between function name and (" check for functions
14751 o Packaging (RPM) changes:
14752 - Update our default RPM spec files to work with mock and rpmbuild
14753 on RHEL/Fedora. They have an updated set of dependencies and
14754 conflicts, a fix for an ancient typo when creating the "_tor"
14755 user, and better instructions. Thanks to Ondrej Mikle for the
14756 patch series. Fixes bug 6043.
14757 - On OpenSUSE, create the /var/run/tor directory on startup if it
14758 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
14760 o Code refactoring (safety):
14761 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
14762 10 lines. Also, don't nest them. Doing so in the past has
14763 led to hard-to-debug code. The new style is to use the
14764 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
14765 - Use macros to indicate OpenSSL versions, so we don't need to worry
14766 about accidental hexadecimal bit shifts.
14767 - Use tor_sscanf() in place of scanf() in more places through the
14768 code. This makes us a little more locale-independent, and
14769 should help shut up code-analysis tools that can't tell
14770 a safe sscanf string from a dangerous one.
14771 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
14772 - Use the smartlist_add_asprintf() alias more consistently.
14774 o Code refactoring (consolidate):
14775 - A major revision to our internal node-selecting and listing logic.
14776 Tor already had at least two major ways to look at the question of
14777 "which Tor servers do we know about": a list of router descriptors,
14778 and a list of entries in the current consensus. With
14779 microdescriptors, we're adding a third. Having so many systems
14780 without an abstraction layer over them was hurting the codebase.
14781 Now, we have a new "node_t" abstraction that presents a consistent
14782 interface to a client's view of a Tor node, and holds (nearly) all
14783 of the mutable state formerly in routerinfo_t and routerstatus_t.
14784 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
14785 Libevent's notion of cached time when possible.
14786 - Remove duplicate code for invoking getrlimit() from control.c.
14787 - Use OpenSSL's built-in SSL_state_string_long() instead of our
14788 own homebrewed ssl_state_to_string() replacement. Patch from
14789 Emile Snyder. Fixes bug 4653.
14790 - Change the symmetric cipher interface so that creating and
14791 initializing a stream cipher are no longer separate functions.
14793 o Code refactoring (separate):
14794 - Make a new "entry connection" struct as an internal subtype of "edge
14795 connection", to simplify the code and make exit connections smaller.
14796 - Split connection_about_to_close() into separate functions for each
14798 - Rewrite the listener-selection logic so that parsing which ports
14799 we want to listen on is now separate from binding to the ports
14802 o Code refactoring (name changes):
14803 - Rename a handful of old identifiers, mostly related to crypto
14804 structures and crypto functions. By convention, our "create an
14805 object" functions are called "type_new()", our "free an object"
14806 functions are called "type_free()", and our types indicate that
14807 they are types only with a final "_t". But a handful of older
14808 types and functions broke these rules, with function names like
14809 "type_create" or "subsystem_op_type", or with type names like
14811 - Rename Tor functions that turn strings into addresses, so that
14812 "parse" indicates that no hostname resolution occurs, and
14813 "lookup" indicates that hostname resolution may occur. This
14814 should help prevent mistakes in the future. Fixes bug 3512.
14815 - Use the name "CERTS" consistently to refer to the new cell type;
14816 we were calling it CERT in some places and CERTS in others.
14817 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
14818 invalid value, rather than just -1.
14819 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
14820 can pick them up when the tests aren't disabled. Bugfix on
14821 0.2.2.4-alpha which introduced tinytest.
14823 o Code refactoring (other):
14824 - Defensively refactor rend_mid_rendezvous() so that protocol
14825 violations and length checks happen in the beginning. Fixes
14827 - Remove the pure attribute from all functions that used it
14828 previously. In many cases we assigned it incorrectly, because the
14829 functions might assert or call impure functions, and we don't have
14830 evidence that keeping the pure attribute is worthwhile. Implements
14831 changes suggested in ticket 4421.
14832 - Move the replay-detection cache for the RSA-encrypted parts of
14833 INTRODUCE2 cells to the introduction point data structures.
14834 Previously, we would use one replay-detection cache per hidden
14835 service. Required by fix for bug 3460.
14836 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
14837 no longer link against Libevent: they never used it, but
14838 our library structure used to force them to link it.
14840 o Removed features and files:
14841 - Remove all internal support for unpadded RSA. We never used it, and
14842 it would be a bad idea to start.
14843 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
14845 - Remove some redundant #include directives throughout the code.
14846 Patch from Andrea Gelmini.
14847 - Remove some old code to remember statistics about which descriptors
14848 we've served as a directory mirror. The feature wasn't used and
14849 is outdated now that microdescriptors are around.
14850 - Remove some old code to work around even older versions of Tor that
14851 used forked processes to handle DNS requests. Such versions of Tor
14852 are no longer in use as relays.
14853 - The "torify" script no longer supports the "tsocks" socksifier
14854 tool, since tsocks doesn't support DNS and UDP right for Tor.
14855 Everyone should be using torsocks instead. Fixes bugs 3530 and
14856 5180. Based on a patch by "ugh".
14857 - Remove the torrc.bridge file: we don't use it for anything, and
14858 it had become badly desynchronized from torrc.sample. Resolves
14862 - Begin a doc/state-contents.txt file to explain the contents of
14863 the Tor state file. Fixes bug 2987.
14864 - Clarify the documentation for the Alternate*Authority options.
14866 - Document the --defaults-torrc option, and the new semantics for
14867 overriding, extending, and clearing lists of options. Closes
14869 - Add missing man page documentation for consensus and microdesc
14870 files. Resolves ticket 6732.
14871 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
14873 o Documentation fixes:
14874 - Improve the manual's documentation for the NT Service command-line
14875 options. Addresses ticket 3964.
14876 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
14877 - Document the changes to the ORPort and DirPort options, and the
14878 fact that {OR/Dir}ListenAddress is now unnecessary (and
14879 therefore deprecated). Resolves ticket 5597.
14880 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
14881 - Clarify that hidden services are TCP only. Fixes bug 6024.
14884 Changes in version 0.2.2.39 - 2012-09-11
14885 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
14889 - Fix an assertion failure in tor_timegm() that could be triggered
14890 by a badly formatted directory object. Bug found by fuzzing with
14891 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
14892 - Do not crash when comparing an address with port value 0 to an
14893 address policy. This bug could have been used to cause a remote
14894 assertion failure by or against directory authorities, or to
14895 allow some applications to crash clients. Fixes bug 6690; bugfix
14899 Changes in version 0.2.2.38 - 2012-08-12
14900 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
14901 attack that could in theory leak path information.
14904 - Avoid an uninitialized memory read when reading a vote or consensus
14905 document that has an unrecognized flavor name. This read could
14906 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
14907 - Try to leak less information about what relays a client is
14908 choosing to a side-channel attacker. Previously, a Tor client would
14909 stop iterating through the list of available relays as soon as it
14910 had chosen one, thus finishing a little earlier when it picked
14911 a router earlier in the list. If an attacker can recover this
14912 timing information (nontrivial but not proven to be impossible),
14913 they could learn some coarse-grained information about which relays
14914 a client was picking (middle nodes in particular are likelier to
14915 be affected than exits). The timing attack might be mitigated by
14916 other factors (see bug 6537 for some discussion), but it's best
14917 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
14920 Changes in version 0.2.2.37 - 2012-06-06
14921 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
14922 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
14926 - Work around a bug in OpenSSL that broke renegotiation with TLS
14927 1.1 and TLS 1.2. Without this workaround, all attempts to speak
14928 the v2 Tor connection protocol when both sides were using OpenSSL
14929 1.0.1 would fail. Resolves ticket 6033.
14930 - When waiting for a client to renegotiate, don't allow it to add
14931 any bytes to the input buffer. This fixes a potential DoS issue.
14932 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
14933 - Fix an edge case where if we fetch or publish a hidden service
14934 descriptor, we might build a 4-hop circuit and then use that circuit
14935 for exiting afterwards -- even if the new last hop doesn't obey our
14936 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
14939 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
14940 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
14943 - Tell GCC and Clang to check for any errors in format strings passed
14944 to the tor_v*(print|scan)f functions.
14947 Changes in version 0.2.2.36 - 2012-05-24
14948 Tor 0.2.2.36 updates the addresses for two of the eight directory
14949 authorities, fixes some potential anonymity and security issues,
14950 and fixes several crash bugs.
14952 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
14953 known flaws, and nobody should be using them. You should upgrade. If
14954 you're using a Linux or BSD and its packages are obsolete, stop using
14955 those packages and upgrade anyway.
14957 o Directory authority changes:
14958 - Change IP address for maatuska (v3 directory authority).
14959 - Change IP address for ides (v3 directory authority), and rename
14963 - When building or running with any version of OpenSSL earlier
14964 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
14965 versions have a bug (CVE-2011-4576) in which their block cipher
14966 padding includes uninitialized data, potentially leaking sensitive
14967 information to any peer with whom they make a SSLv3 connection. Tor
14968 does not use SSL v3 by default, but a hostile client or server
14969 could force an SSLv3 connection in order to gain information that
14970 they shouldn't have been able to get. The best solution here is to
14971 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
14972 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
14973 to make sure that the bug can't happen.
14974 - Never use a bridge or a controller-supplied node as an exit, even
14975 if its exit policy allows it. Found by wanoskarnet. Fixes bug
14976 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
14977 and 0.2.0.3-alpha (for bridge-purpose descriptors).
14978 - Only build circuits if we have a sufficient threshold of the total
14979 descriptors that are marked in the consensus with the "Exit"
14980 flag. This mitigates an attack proposed by wanoskarnet, in which
14981 all of a client's bridges collude to restrict the exit nodes that
14982 the client knows about. Fixes bug 5343.
14983 - Provide controllers with a safer way to implement the cookie
14984 authentication mechanism. With the old method, if another locally
14985 running program could convince a controller that it was the Tor
14986 process, then that program could trick the controller into telling
14987 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
14988 authentication method uses a challenge-response approach to prevent
14989 this attack. Fixes bug 5185; implements proposal 193.
14992 - Avoid logging uninitialized data when unable to decode a hidden
14993 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
14994 - Avoid a client-side assertion failure when receiving an INTRODUCE2
14995 cell on a general purpose circuit. Fixes bug 5644; bugfix on
14997 - Fix builds when the path to sed, openssl, or sha1sum contains
14998 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
15000 - Correct our replacements for the timeradd() and timersub() functions
15001 on platforms that lack them (for example, Windows). The timersub()
15002 function is used when expiring circuits, while timeradd() is
15003 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
15004 bugfix on 0.2.2.24-alpha.
15005 - Fix the SOCKET_OK test that we use to tell when socket
15006 creation fails so that it works on Win64. Fixes part of bug 4533;
15007 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
15010 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
15011 Fixes bug 5346; bugfix on 0.0.8pre3.
15012 - Make our number-parsing functions always treat too-large values
15013 as an error, even when those values exceed the width of the
15014 underlying type. Previously, if the caller provided these
15015 functions with minima or maxima set to the extreme values of the
15016 underlying integer type, these functions would return those
15017 values on overflow rather than treating overflow as an error.
15018 Fixes part of bug 5786; bugfix on 0.0.9.
15019 - Older Linux kernels erroneously respond to strange nmap behavior
15020 by having accept() return successfully with a zero-length
15021 socket. When this happens, just close the connection. Previously,
15022 we would try harder to learn the remote address: but there was
15023 no such remote address to learn, and our method for trying to
15024 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
15025 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
15026 - Correct parsing of certain date types in parse_http_time().
15027 Without this patch, If-Modified-Since would behave
15028 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
15029 Esteban Manchado Velázques.
15030 - Change the BridgePassword feature (part of the "bridge community"
15031 design, which is not yet implemented) to use a time-independent
15032 comparison. The old behavior might have allowed an adversary
15033 to use timing to guess the BridgePassword value. Fixes bug 5543;
15034 bugfix on 0.2.0.14-alpha.
15035 - Detect and reject certain misformed escape sequences in
15036 configuration values. Previously, these values would cause us
15037 to crash if received in a torrc file or over an authenticated
15038 control port. Bug found by Esteban Manchado Velázquez, and
15039 independently by Robert Connolly from Matta Consulting who further
15040 noted that it allows a post-authentication heap overflow. Patch
15041 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
15042 bugfix on 0.2.0.16-alpha.
15043 - Fix a compile warning when using the --enable-openbsd-malloc
15044 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
15045 - During configure, detect when we're building with clang version
15046 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
15047 CFLAGS. clang doesn't support them yet.
15048 - When sending an HTTP/1.1 proxy request, include a Host header.
15049 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
15050 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
15051 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
15052 - If we hit the error case where routerlist_insert() replaces an
15053 existing (old) server descriptor, make sure to remove that
15054 server descriptor from the old_routers list. Fix related to bug
15055 1776. Bugfix on 0.2.2.18-alpha.
15057 o Minor bugfixes (documentation and log messages):
15058 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
15059 Fixes bug 4856; bugfix on Tor 0.0.6.
15060 - Update "ClientOnly" man page entry to explain that there isn't
15061 really any point to messing with it. Resolves ticket 5005.
15062 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
15063 directory authority option (introduced in Tor 0.2.2.34).
15064 - Downgrade the "We're missing a certificate" message from notice
15065 to info: people kept mistaking it for a real problem, whereas it
15066 is seldom the problem even when we are failing to bootstrap. Fixes
15067 bug 5067; bugfix on 0.2.0.10-alpha.
15068 - Correctly spell "connect" in a log message on failure to create a
15069 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
15070 - Clarify the behavior of MaxCircuitDirtiness with hidden service
15071 circuits. Fixes issue 5259.
15074 - Directory authorities now reject versions of Tor older than
15075 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
15076 inclusive. These versions accounted for only a small fraction of
15077 the Tor network, and have numerous known security issues. Resolves
15079 - Update to the May 1 2012 Maxmind GeoLite Country database.
15082 - When sending or relaying a RELAY_EARLY cell, we used to convert
15083 it to a RELAY cell if the connection was using the v1 link
15084 protocol. This was a workaround for older versions of Tor, which
15085 didn't handle RELAY_EARLY cells properly. Now that all supported
15086 versions can handle RELAY_EARLY cells, and now that we're enforcing
15087 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
15088 remove this workaround. Addresses bug 4786.
15091 Changes in version 0.2.2.35 - 2011-12-16
15092 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
15093 buffers code. Absolutely everybody should upgrade.
15095 The bug relied on an incorrect calculation when making data continuous
15096 in one of our IO buffers, if the first chunk of the buffer was
15097 misaligned by just the wrong amount. The miscalculation would allow an
15098 attacker to overflow a piece of heap-allocated memory. To mount this
15099 attack, the attacker would need to either open a SOCKS connection to
15100 Tor's SocksPort (usually restricted to localhost), or target a Tor
15101 instance configured to make its connections through a SOCKS proxy
15102 (which Tor does not do by default).
15104 Good security practice requires that all heap-overflow bugs should be
15105 presumed to be exploitable until proven otherwise, so we are treating
15106 this as a potential code execution attack. Please upgrade immediately!
15107 This bug does not affect bufferevents-based builds of Tor. Special
15108 thanks to "Vektor" for reporting this issue to us!
15110 Tor 0.2.2.35 also fixes several bugs in previous versions, including
15111 crash bugs for unusual configurations, and a long-term bug that
15112 would prevent Tor from starting on Windows machines with draconian
15115 With this release, we remind everyone that 0.2.0.x has reached its
15116 formal end-of-life. Those Tor versions have many known flaws, and
15117 nobody should be using them. You should upgrade -- ideally to the
15118 0.2.2.x series. If you're using a Linux or BSD and its packages are
15119 obsolete, stop using those packages and upgrade anyway.
15121 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
15122 longer receive support after some time in early 2012.
15125 - Fix a heap overflow bug that could occur when trying to pull
15126 data into the first chunk of a buffer, when that chunk had
15127 already had some data drained from it. Fixes CVE-2011-2778;
15128 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
15129 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
15130 that it doesn't attempt to allocate a socketpair. This could cause
15131 some problems on Windows systems with overzealous firewalls. Fix for
15132 bug 4457; workaround for Libevent versions 2.0.1-alpha through
15134 - If we mark an OR connection for close based on a cell we process,
15135 don't process any further cells on it. We already avoid further
15136 reads on marked-for-close connections, but now we also discard the
15137 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
15138 which was the first version where we might mark a connection for
15139 close based on processing a cell on it.
15140 - Correctly sanity-check that we don't underflow on a memory
15141 allocation (and then assert) for hidden service introduction
15142 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
15143 bugfix on 0.2.1.5-alpha.
15144 - Fix a memory leak when we check whether a hidden service
15145 descriptor has any usable introduction points left. Fixes bug
15146 4424. Bugfix on 0.2.2.25-alpha.
15147 - Don't crash when we're running as a relay and don't have a GeoIP
15148 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
15149 we've had in the 0.2.3.x branch already.
15150 - When running as a client, do not print a misleading (and plain
15151 wrong) log message that we're collecting "directory request"
15152 statistics: clients don't collect statistics. Also don't create a
15153 useless (because empty) stats file in the stats/ directory. Fixes
15154 bug 4353; bugfix on 0.2.2.34.
15157 - Detect failure to initialize Libevent. This fix provides better
15158 detection for future instances of bug 4457.
15159 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
15160 function. This was eating up hideously large amounts of time on some
15161 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
15162 - Resolve an integer overflow bug in smartlist_ensure_capacity().
15163 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
15165 - Don't warn about unused log_mutex in log.c when building with
15166 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
15167 0.1.0.6-rc which introduced --disable-threads.
15168 - When configuring, starting, or stopping an NT service, stop
15169 immediately after the service configuration attempt has succeeded
15170 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
15171 - When sending a NETINFO cell, include the original address
15172 received for the other side, not its canonical address. Found
15173 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
15174 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
15175 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
15176 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
15177 occurred when a client tried to fetch a descriptor for a bridge
15178 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
15179 - Backport fixes for a pair of compilation warnings on Windows.
15180 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
15181 - If we had ever tried to call tor_addr_to_str on an address of
15182 unknown type, we would have done a strdup on an uninitialized
15183 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
15184 Reported by "troll_un".
15185 - Correctly detect and handle transient lookup failures from
15186 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
15187 Reported by "troll_un".
15188 - Fix null-pointer access that could occur if TLS allocation failed.
15189 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
15190 - Use tor_socket_t type for listener argument to accept(). Fixes bug
15191 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
15194 - Add two new config options for directory authorities:
15195 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
15196 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
15197 that is always sufficient to satisfy the bandwidth requirement for
15198 the Guard flag. Now it will be easier for researchers to simulate
15199 Tor networks with different values. Resolves ticket 4484.
15200 - When Tor ignores a hidden service specified in its configuration,
15201 include the hidden service's directory in the warning message.
15202 Previously, we would only tell the user that some hidden service
15203 was ignored. Bugfix on 0.0.6; fixes bug 4426.
15204 - Update to the December 6 2011 Maxmind GeoLite Country database.
15206 o Packaging changes:
15207 - Make it easier to automate expert package builds on Windows,
15208 by removing an absolute path from makensis.exe command.
15211 Changes in version 0.2.1.32 - 2011-12-16
15212 Tor 0.2.1.32 backports important security and privacy fixes for
15213 oldstable. This release is intended only for package maintainers and
15214 others who cannot use the 0.2.2 stable series. All others should be
15215 using Tor 0.2.2.x or newer.
15217 The Tor 0.2.1.x series will reach formal end-of-life some time in
15218 early 2012; we will stop releasing patches for it then.
15220 o Major bugfixes (also included in 0.2.2.x):
15221 - Correctly sanity-check that we don't underflow on a memory
15222 allocation (and then assert) for hidden service introduction
15223 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
15224 bugfix on 0.2.1.5-alpha.
15225 - Fix a heap overflow bug that could occur when trying to pull
15226 data into the first chunk of a buffer, when that chunk had
15227 already had some data drained from it. Fixes CVE-2011-2778;
15228 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
15231 - Update to the December 6 2011 Maxmind GeoLite Country database.
15234 Changes in version 0.2.2.34 - 2011-10-26
15235 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
15236 can deanonymize Tor users. Everybody should upgrade.
15238 The attack relies on four components: 1) Clients reuse their TLS cert
15239 when talking to different relays, so relays can recognize a user by
15240 the identity key in her cert. 2) An attacker who knows the client's
15241 identity key can probe each guard relay to see if that identity key
15242 is connected to that guard relay right now. 3) A variety of active
15243 attacks in the literature (starting from "Low-Cost Traffic Analysis
15244 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
15245 discover the guard relays that a Tor user visiting the website is using.
15246 4) Clients typically pick three guards at random, so the set of guards
15247 for a given user could well be a unique fingerprint for her. This
15248 release fixes components #1 and #2, which is enough to block the attack;
15249 the other two remain as open research problems. Special thanks to
15250 "frosty_un" for reporting the issue to us!
15252 Clients should upgrade so they are no longer recognizable by the TLS
15253 certs they present. Relays should upgrade so they no longer allow a
15254 remote attacker to probe them to test whether unpatched clients are
15255 currently connected to them.
15257 This release also fixes several vulnerabilities that allow an attacker
15258 to enumerate bridge relays. Some bridge enumeration attacks still
15259 remain; see for example proposal 188.
15261 o Privacy/anonymity fixes (clients):
15262 - Clients and bridges no longer send TLS certificate chains on
15263 outgoing OR connections. Previously, each client or bridge would
15264 use the same cert chain for all outgoing OR connections until
15265 its IP address changes, which allowed any relay that the client
15266 or bridge contacted to determine which entry guards it is using.
15267 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
15268 - If a relay receives a CREATE_FAST cell on a TLS connection, it
15269 no longer considers that connection as suitable for satisfying a
15270 circuit EXTEND request. Now relays can protect clients from the
15271 CVE-2011-2768 issue even if the clients haven't upgraded yet.
15272 - Directory authorities no longer assign the Guard flag to relays
15273 that haven't upgraded to the above "refuse EXTEND requests
15274 to client connections" fix. Now directory authorities can
15275 protect clients from the CVE-2011-2768 issue even if neither
15276 the clients nor the relays have upgraded yet. There's a new
15277 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
15278 to let us transition smoothly, else tomorrow there would be no
15281 o Privacy/anonymity fixes (bridge enumeration):
15282 - Bridge relays now do their directory fetches inside Tor TLS
15283 connections, like all the other clients do, rather than connecting
15284 directly to the DirPort like public relays do. Removes another
15285 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
15286 - Bridges relays now build circuits for themselves in a more similar
15287 way to how clients build them. Removes another avenue for
15288 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
15289 when bridges were introduced.
15290 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
15291 that they initiated. Relays could distinguish incoming bridge
15292 connections from client connections, creating another avenue for
15293 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
15294 Found by "frosty_un".
15297 - Fix a crash bug when changing node restrictions while a DNS lookup
15298 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
15300 - Don't launch a useless circuit after failing to use one of a
15301 hidden service's introduction points. Previously, we would
15302 launch a new introduction circuit, but not set the hidden service
15303 which that circuit was intended to connect to, so it would never
15304 actually be used. A different piece of code would then create a
15305 new introduction circuit correctly. Bug reported by katmagic and
15306 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
15309 - Change an integer overflow check in the OpenBSD_Malloc code so
15310 that GCC is less likely to eliminate it as impossible. Patch
15311 from Mansour Moufid. Fixes bug 4059.
15312 - When a hidden service turns an extra service-side introduction
15313 circuit into a general-purpose circuit, free the rend_data and
15314 intro_key fields first, so we won't leak memory if the circuit
15315 is cannibalized for use as another service-side introduction
15316 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
15317 - Bridges now skip DNS self-tests, to act a little more stealthily.
15318 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
15319 bridges. Patch by "warms0x".
15320 - Fix internal bug-checking logic that was supposed to catch
15321 failures in digest generation so that it will fail more robustly
15322 if we ask for a nonexistent algorithm. Found by Coverity Scan.
15323 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
15324 - Report any failure in init_keys() calls launched because our
15325 IP address has changed. Spotted by Coverity Scan. Bugfix on
15326 0.1.1.4-alpha; fixes CID 484.
15328 o Minor bugfixes (log messages and documentation):
15329 - Remove a confusing dollar sign from the example fingerprint in the
15330 man page, and also make the example fingerprint a valid one. Fixes
15331 bug 4309; bugfix on 0.2.1.3-alpha.
15332 - The next version of Windows will be called Windows 8, and it has
15333 a major version of 6, minor version of 2. Correctly identify that
15334 version instead of calling it "Very recent version". Resolves
15335 ticket 4153; reported by funkstar.
15336 - Downgrade log messages about circuit timeout calibration from
15337 "notice" to "info": they don't require or suggest any human
15338 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
15339 bugfix on 0.2.2.14-alpha.
15342 - Turn on directory request statistics by default and include them in
15343 extra-info descriptors. Don't break if we have no GeoIP database.
15344 Backported from 0.2.3.1-alpha; implements ticket 3951.
15345 - Update to the October 4 2011 Maxmind GeoLite Country database.
15348 Changes in version 0.2.1.31 - 2011-10-26
15349 Tor 0.2.1.31 backports important security and privacy fixes for
15350 oldstable. This release is intended only for package maintainers and
15351 others who cannot use the 0.2.2 stable series. All others should be
15352 using Tor 0.2.2.x or newer.
15354 o Security fixes (also included in 0.2.2.x):
15355 - Replace all potentially sensitive memory comparison operations
15356 with versions whose runtime does not depend on the data being
15357 compared. This will help resist a class of attacks where an
15358 adversary can use variations in timing information to learn
15359 sensitive data. Fix for one case of bug 3122. (Safe memcmp
15360 implementation by Robert Ransom based partially on code by DJB.)
15361 - Fix an assert in parsing router descriptors containing IPv6
15362 addresses. This one took down the directory authorities when
15363 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
15365 o Privacy/anonymity fixes (also included in 0.2.2.x):
15366 - Clients and bridges no longer send TLS certificate chains on
15367 outgoing OR connections. Previously, each client or bridge would
15368 use the same cert chain for all outgoing OR connections until
15369 its IP address changes, which allowed any relay that the client
15370 or bridge contacted to determine which entry guards it is using.
15371 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
15372 - If a relay receives a CREATE_FAST cell on a TLS connection, it
15373 no longer considers that connection as suitable for satisfying a
15374 circuit EXTEND request. Now relays can protect clients from the
15375 CVE-2011-2768 issue even if the clients haven't upgraded yet.
15376 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
15377 that they initiated. Relays could distinguish incoming bridge
15378 connections from client connections, creating another avenue for
15379 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
15380 Found by "frosty_un".
15381 - When receiving a hidden service descriptor, check that it is for
15382 the hidden service we wanted. Previously, Tor would store any
15383 hidden service descriptors that a directory gave it, whether it
15384 wanted them or not. This wouldn't have let an attacker impersonate
15385 a hidden service, but it did let directories pre-seed a client
15386 with descriptors that it didn't want. Bugfix on 0.0.6.
15387 - Avoid linkability based on cached hidden service descriptors: forget
15388 all hidden service descriptors cached as a client when processing a
15389 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
15390 - Make the bridge directory authority refuse to answer directory
15391 requests for "all" descriptors. It used to include bridge
15392 descriptors in its answer, which was a major information leak.
15393 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
15394 - Don't attach new streams to old rendezvous circuits after SIGNAL
15395 NEWNYM. Previously, we would keep using an existing rendezvous
15396 circuit if it remained open (i.e. if it were kept open by a
15397 long-lived stream, or if a new stream were attached to it before
15398 Tor could notice that it was old and no longer in use). Bugfix on
15399 0.1.1.15-rc; fixes bug 3375.
15401 o Minor bugfixes (also included in 0.2.2.x):
15402 - When we restart our relay, we might get a successful connection
15403 from the outside before we've started our reachability tests,
15404 triggering a warning: "ORPort found reachable, but I have no
15405 routerinfo yet. Failing to inform controller of success." This
15406 bug was harmless unless Tor is running under a controller
15407 like Vidalia, in which case the controller would never get a
15408 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
15410 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
15411 enabled. Fixes bug 1526.
15412 - Remove undocumented option "-F" from tor-resolve: it hasn't done
15413 anything since 0.2.1.16-rc.
15414 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
15415 None of the cases where we did this before were wrong, but by making
15416 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
15417 - Fix a rare crash bug that could occur when a client was configured
15418 with a large number of bridges. Fixes bug 2629; bugfix on
15419 0.2.1.2-alpha. Bugfix by trac user "shitlei".
15420 - Correct the warning displayed when a rendezvous descriptor exceeds
15421 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
15423 - Fix an uncommon assertion failure when running with DNSPort under
15424 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
15425 - When warning about missing zlib development packages during compile,
15426 give the correct package names. Bugfix on 0.2.0.1-alpha.
15427 - Require that introduction point keys and onion keys have public
15428 exponent 65537. Bugfix on 0.2.0.10-alpha.
15429 - Do not crash when our configuration file becomes unreadable, for
15430 example due to a permissions change, between when we start up
15431 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
15433 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
15435 - Always NUL-terminate the sun_path field of a sockaddr_un before
15436 passing it to the kernel. (Not a security issue: kernels are
15437 smart enough to reject bad sockaddr_uns.) Found by Coverity;
15438 CID #428. Bugfix on Tor 0.2.0.3-alpha.
15439 - Don't stack-allocate the list of supplementary GIDs when we're
15440 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
15441 could take up to 256K, which is way too much stack. Found by
15442 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
15444 o Minor bugfixes (only in 0.2.1.x):
15445 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
15446 rely on them. Bugfix on 0.2.1.30.
15447 - Use git revisions instead of svn revisions when generating our
15448 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
15450 o Minor features (also included in 0.2.2.x):
15451 - Adjust the expiration time on our SSL session certificates to
15452 better match SSL certs seen in the wild. Resolves ticket 4014.
15453 - Allow nameservers with IPv6 address. Resolves bug 2574.
15454 - Update to the October 4 2011 Maxmind GeoLite Country database.
15457 Changes in version 0.2.2.33 - 2011-09-13
15458 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
15459 TLS handshake that makes relays and bridges that run this new version
15460 reachable from Iran again.
15463 - Avoid an assertion failure when reloading a configuration with
15464 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
15465 3923; bugfix on 0.2.2.25-alpha.
15467 o Minor features (security):
15468 - Check for replays of the public-key encrypted portion of an
15469 INTRODUCE1 cell, in addition to the current check for replays of
15470 the g^x value. This prevents a possible class of active attacks
15471 by an attacker who controls both an introduction point and a
15472 rendezvous point, and who uses the malleability of AES-CTR to
15473 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
15474 that these attacks are infeasible (requiring the attacker to send
15475 on the order of zettabytes of altered cells in a short interval),
15476 but we'd rather block them off in case there are any classes of
15477 this attack that we missed. Reported by Willem Pinckaers.
15480 - Adjust the expiration time on our SSL session certificates to
15481 better match SSL certs seen in the wild. Resolves ticket 4014.
15482 - Change the default required uptime for a relay to be accepted as
15483 a HSDir (hidden service directory) from 24 hours to 25 hours.
15484 Improves on 0.2.0.10-alpha; resolves ticket 2649.
15485 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
15486 authorities to abstain from voting on assignment of the HSDir
15487 consensus flag. Related to bug 2649.
15488 - Update to the September 6 2011 Maxmind GeoLite Country database.
15490 o Minor bugfixes (documentation and log messages):
15491 - Correct the man page to explain that HashedControlPassword and
15492 CookieAuthentication can both be set, in which case either method
15493 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
15494 when we decided to allow these config options to both be set. Issue
15495 raised by bug 3898.
15496 - Demote the 'replay detected' log message emitted when a hidden
15497 service receives the same Diffie-Hellman public key in two different
15498 INTRODUCE2 cells to info level. A normal Tor client can cause that
15499 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
15500 fixes part of bug 2442.
15501 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
15502 level. There is nothing that a hidden service's operator can do
15503 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
15505 - Clarify a log message specifying the characters permitted in
15506 HiddenServiceAuthorizeClient client names. Previously, the log
15507 message said that "[A-Za-z0-9+-_]" were permitted; that could have
15508 given the impression that every ASCII character between "+" and "_"
15509 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
15512 - Provide a substitute implementation of lround() for MSVC, which
15513 apparently lacks it. Patch from Gisle Vanem.
15514 - Clean up some code issues that prevented Tor from building on older
15515 BSDs. Fixes bug 3894; reported by "grarpamp".
15516 - Search for a platform-specific version of "ar" when cross-compiling.
15517 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
15520 Changes in version 0.2.2.32 - 2011-08-27
15521 The Tor 0.2.2 release series is dedicated to the memory of Andreas
15522 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
15523 a founder of the PETS community, a leader in our field, a mentor,
15524 and a friend. He left us with these words: "I had the possibility
15525 to contribute to this world that is not as it should be. I hope I
15526 could help in some areas to make the world a better place, and that
15527 I could also encourage other people to be engaged in improving the
15528 world. Please, stay engaged. This world needs you, your love, your
15529 initiative -- now I cannot be part of that anymore."
15531 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
15532 ready. More than two years in the making, this release features improved
15533 client performance and hidden service reliability, better compatibility
15534 for Android, correct behavior for bridges that listen on more than
15535 one address, more extensible and flexible directory object handling,
15536 better reporting of network statistics, improved code security, and
15537 many many other features and bugfixes.
15539 o Major features (client performance):
15540 - When choosing which cells to relay first, relays now favor circuits
15541 that have been quiet recently, to provide lower latency for
15542 low-volume circuits. By default, relays enable or disable this
15543 feature based on a setting in the consensus. They can override
15544 this default by using the new "CircuitPriorityHalflife" config
15545 option. Design and code by Ian Goldberg, Can Tang, and Chris
15547 - Directory authorities now compute consensus weightings that instruct
15548 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
15549 and no flag. Clients use these weightings to distribute network load
15550 more evenly across these different relay types. The weightings are
15551 in the consensus so we can change them globally in the future. Extra
15552 thanks to "outofwords" for finding some nasty security bugs in
15553 the first implementation of this feature.
15555 o Major features (client performance, circuit build timeout):
15556 - Tor now tracks how long it takes to build client-side circuits
15557 over time, and adapts its timeout to local network performance.
15558 Since a circuit that takes a long time to build will also provide
15559 bad performance, we get significant latency improvements by
15560 discarding the slowest 20% of circuits. Specifically, Tor creates
15561 circuits more aggressively than usual until it has enough data
15562 points for a good timeout estimate. Implements proposal 151.
15563 - Circuit build timeout constants can be controlled by consensus
15564 parameters. We set good defaults for these parameters based on
15565 experimentation on broadband and simulated high-latency links.
15566 - Circuit build time learning can be disabled via consensus parameter
15567 or by the client via a LearnCircuitBuildTimeout config option. We
15568 also automatically disable circuit build time calculation if either
15569 AuthoritativeDirectory is set, or if we fail to write our state
15570 file. Implements ticket 1296.
15572 o Major features (relays use their capacity better):
15573 - Set SO_REUSEADDR socket option on all sockets, not just
15574 listeners. This should help busy exit nodes avoid running out of
15575 useable ports just because all the ports have been used in the
15576 near past. Resolves issue 2850.
15577 - Relays now save observed peak bandwidth throughput rates to their
15578 state file (along with total usage, which was already saved),
15579 so that they can determine their correct estimated bandwidth on
15580 restart. Resolves bug 1863, where Tor relays would reset their
15581 estimated bandwidth to 0 after restarting.
15582 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
15583 should give us approximately 40-50% more Guard-flagged nodes,
15584 improving the anonymity the Tor network can provide and also
15585 decreasing the dropoff in throughput that relays experience when
15586 they first get the Guard flag.
15587 - Directory authorities now take changes in router IP address and
15588 ORPort into account when determining router stability. Previously,
15589 if a router changed its IP or ORPort, the authorities would not
15590 treat it as having any downtime for the purposes of stability
15591 calculation, whereas clients would experience downtime since the
15592 change would take a while to propagate to them. Resolves issue 1035.
15593 - New AccelName and AccelDir options add support for dynamic OpenSSL
15594 hardware crypto acceleration engines.
15596 o Major features (relays control their load better):
15597 - Exit relays now try harder to block exit attempts from unknown
15598 relays, to make it harder for people to use them as one-hop proxies
15599 a la tortunnel. Controlled by the refuseunknownexits consensus
15600 parameter (currently enabled), or you can override it on your
15601 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
15602 based on a variant of proposal 163.
15603 - Add separate per-conn write limiting to go with the per-conn read
15604 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
15605 but never per-conn write limits.
15606 - New consensus params "bwconnrate" and "bwconnburst" to let us
15607 rate-limit client connections as they enter the network. It's
15608 controlled in the consensus so we can turn it on and off for
15609 experiments. It's starting out off. Based on proposal 163.
15611 o Major features (controllers):
15612 - Export GeoIP information on bridge usage to controllers even if we
15613 have not yet been running for 24 hours. Now Vidalia bridge operators
15614 can get more accurate and immediate feedback about their
15615 contributions to the network.
15616 - Add an __OwningControllerProcess configuration option and a
15617 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
15618 that when it exits, Tor will shut down. Implements feature 3049.
15620 o Major features (directory authorities):
15621 - Directory authorities now create, vote on, and serve multiple
15622 parallel formats of directory data as part of their voting process.
15623 Partially implements Proposal 162: "Publish the consensus in
15625 - Directory authorities now agree on and publish small summaries
15626 of router information that clients can use in place of regular
15627 server descriptors. This transition will allow Tor 0.2.3 clients
15628 to use far less bandwidth for downloading information about the
15629 network. Begins the implementation of Proposal 158: "Clients
15630 download consensus + microdescriptors".
15631 - The directory voting system is now extensible to use multiple hash
15632 algorithms for signatures and resource selection. Newer formats
15633 are signed with SHA256, with a possibility for moving to a better
15634 hash algorithm in the future.
15635 - Directory authorities can now vote on arbitrary integer values as
15636 part of the consensus process. This is designed to help set
15637 network-wide parameters. Implements proposal 167.
15639 o Major features and bugfixes (node selection):
15640 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
15641 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
15642 options. Previously, we had been ambiguous in describing what
15643 counted as an "exit" node, and what operations exactly "StrictNodes
15644 0" would permit. This created confusion when people saw nodes built
15645 through unexpected circuits, and made it hard to tell real bugs from
15646 surprises. Now the intended behavior is:
15647 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
15648 a node that delivers user traffic outside the Tor network.
15649 . "Entry", in the context of EntryNodes, means a node used as the
15650 first hop of a multihop circuit. It doesn't include direct
15651 connections to directory servers.
15652 . "ExcludeNodes" applies to all nodes.
15653 . "StrictNodes" changes the behavior of ExcludeNodes only. When
15654 StrictNodes is set, Tor should avoid all nodes listed in
15655 ExcludeNodes, even when it will make user requests fail. When
15656 StrictNodes is *not* set, then Tor should follow ExcludeNodes
15657 whenever it can, except when it must use an excluded node to
15658 perform self-tests, connect to a hidden service, provide a
15659 hidden service, fulfill a .exit request, upload directory
15660 information, or fetch directory information.
15661 Collectively, the changes to implement the behavior fix bug 1090.
15662 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
15663 change during a config reload, mark and discard all our origin
15664 circuits. This fix should address edge cases where we change the
15665 config options and but then choose a circuit that we created before
15667 - Make EntryNodes config option much more aggressive even when
15668 StrictNodes is not set. Before it would prepend your requested
15669 entrynodes to your list of guard nodes, but feel free to use others
15670 after that. Now it chooses only from your EntryNodes if any of
15671 those are available, and only falls back to others if a) they're
15672 all down and b) StrictNodes is not set.
15673 - Now we refresh your entry guards from EntryNodes at each consensus
15674 fetch -- rather than just at startup and then they slowly rot as
15675 the network changes.
15676 - Add support for the country code "{??}" in torrc options like
15677 ExcludeNodes, to indicate all routers of unknown country. Closes
15679 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
15680 a node is listed in both, it's treated as excluded.
15681 - ExcludeNodes now applies to directory nodes -- as a preference if
15682 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
15683 Don't exclude all the directory authorities and set StrictNodes to 1
15684 unless you really want your Tor to break.
15685 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
15686 - ExcludeExitNodes now overrides .exit requests.
15687 - We don't use bridges listed in ExcludeNodes.
15688 - When StrictNodes is 1:
15689 . We now apply ExcludeNodes to hidden service introduction points
15690 and to rendezvous points selected by hidden service users. This
15691 can make your hidden service less reliable: use it with caution!
15692 . If we have used ExcludeNodes on ourself, do not try relay
15693 reachability self-tests.
15694 . If we have excluded all the directory authorities, we will not
15695 even try to upload our descriptor if we're a relay.
15696 . Do not honor .exit requests to an excluded node.
15697 - When the set of permitted nodes changes, we now remove any mappings
15698 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
15700 - We never cannibalize a circuit that had excluded nodes on it, even
15701 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
15702 - Improve log messages related to excluded nodes.
15704 o Major features (misc):
15705 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
15706 to help Tor build correctly for Android phones.
15707 - The options SocksPort, ControlPort, and so on now all accept a
15708 value "auto" that opens a socket on an OS-selected port. A
15709 new ControlPortWriteToFile option tells Tor to write its
15710 actual control port or ports to a chosen file. If the option
15711 ControlPortFileGroupReadable is set, the file is created as
15712 group-readable. Now users can run two Tor clients on the same
15713 system without needing to manually mess with parameters. Resolves
15714 part of ticket 3076.
15715 - Tor now supports tunneling all of its outgoing connections over
15716 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
15717 configuration options. Code by Christopher Davis.
15719 o Code security improvements:
15720 - Replace all potentially sensitive memory comparison operations
15721 with versions whose runtime does not depend on the data being
15722 compared. This will help resist a class of attacks where an
15723 adversary can use variations in timing information to learn
15724 sensitive data. Fix for one case of bug 3122. (Safe memcmp
15725 implementation by Robert Ransom based partially on code by DJB.)
15726 - Enable Address Space Layout Randomization (ASLR) and Data Execution
15727 Prevention (DEP) by default on Windows to make it harder for
15728 attackers to exploit vulnerabilities. Patch from John Brooks.
15729 - New "--enable-gcc-hardening" ./configure flag (off by default)
15730 to turn on gcc compile time hardening options. It ensures
15731 that signed ints have defined behavior (-fwrapv), enables
15732 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
15733 with canaries (-fstack-protector-all), turns on ASLR protection if
15734 supported by the kernel (-fPIE, -pie), and adds additional security
15735 related warnings. Verified to work on Mac OS X and Debian Lenny.
15736 - New "--enable-linker-hardening" ./configure flag (off by default)
15737 to turn on ELF specific hardening features (relro, now). This does
15738 not work with Mac OS X or any other non-ELF binary format.
15739 - Always search the Windows system directory for system DLLs, and
15740 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
15741 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
15742 current and future memory pages via mlockall(). On supported
15743 platforms (modern Linux and probably BSD but not Windows or OS X),
15744 this should effectively disable any and all attempts to page out
15745 memory. This option requires that you start your Tor as root --
15746 if you use DisableAllSwap, please consider using the User option
15747 to properly reduce the privileges of your Tor.
15749 o Major bugfixes (crashes):
15750 - Fix crash bug on platforms where gmtime and localtime can return
15751 NULL. Windows 7 users were running into this one. Fixes part of bug
15752 2077. Bugfix on all versions of Tor. Found by boboper.
15753 - Introduce minimum/maximum values that clients will believe
15754 from the consensus. Now we'll have a better chance to avoid crashes
15755 or worse when a consensus param has a weird value.
15756 - Fix a rare crash bug that could occur when a client was configured
15757 with a large number of bridges. Fixes bug 2629; bugfix on
15758 0.2.1.2-alpha. Bugfix by trac user "shitlei".
15759 - Do not crash when our configuration file becomes unreadable, for
15760 example due to a permissions change, between when we start up
15761 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
15763 - If we're in the pathological case where there's no exit bandwidth
15764 but there is non-exit bandwidth, or no guard bandwidth but there
15765 is non-guard bandwidth, don't crash during path selection. Bugfix
15767 - Fix a crash bug when trying to initialize the evdns module in
15768 Libevent 2. Bugfix on 0.2.1.16-rc.
15770 o Major bugfixes (stability):
15771 - Fix an assert in parsing router descriptors containing IPv6
15772 addresses. This one took down the directory authorities when
15773 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
15774 - Fix an uncommon assertion failure when running with DNSPort under
15775 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
15776 - Treat an unset $HOME like an empty $HOME rather than triggering an
15777 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
15778 - More gracefully handle corrupt state files, removing asserts
15779 in favor of saving a backup and resetting state.
15780 - Instead of giving an assertion failure on an internal mismatch
15781 on estimated freelist size, just log a BUG warning and try later.
15782 Mitigates but does not fix bug 1125.
15783 - Fix an assert that got triggered when using the TestingTorNetwork
15784 configuration option and then issuing a GETINFO config-text control
15785 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
15786 - If the cached cert file is unparseable, warn but don't exit.
15788 o Privacy fixes (relays/bridges):
15789 - Don't list Windows capabilities in relay descriptors. We never made
15790 use of them, and maybe it's a bad idea to publish them. Bugfix
15792 - If the Nickname configuration option isn't given, Tor would pick a
15793 nickname based on the local hostname as the nickname for a relay.
15794 Because nicknames are not very important in today's Tor and the
15795 "Unnamed" nickname has been implemented, this is now problematic
15796 behavior: It leaks information about the hostname without being
15797 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
15798 introduced the Unnamed nickname. Reported by tagnaq.
15799 - Maintain separate TLS contexts and certificates for incoming and
15800 outgoing connections in bridge relays. Previously we would use the
15801 same TLS contexts and certs for incoming and outgoing connections.
15802 Bugfix on 0.2.0.3-alpha; addresses bug 988.
15803 - Maintain separate identity keys for incoming and outgoing TLS
15804 contexts in bridge relays. Previously we would use the same
15805 identity keys for incoming and outgoing TLS contexts. Bugfix on
15806 0.2.0.3-alpha; addresses the other half of bug 988.
15807 - Make the bridge directory authority refuse to answer directory
15808 requests for "all descriptors". It used to include bridge
15809 descriptors in its answer, which was a major information leak.
15810 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
15812 o Privacy fixes (clients):
15813 - When receiving a hidden service descriptor, check that it is for
15814 the hidden service we wanted. Previously, Tor would store any
15815 hidden service descriptors that a directory gave it, whether it
15816 wanted them or not. This wouldn't have let an attacker impersonate
15817 a hidden service, but it did let directories pre-seed a client
15818 with descriptors that it didn't want. Bugfix on 0.0.6.
15819 - Start the process of disabling ".exit" address notation, since it
15820 can be used for a variety of esoteric application-level attacks
15821 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
15823 - Reject attempts at the client side to open connections to private
15824 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
15825 a randomly chosen exit node. Attempts to do so are always
15826 ill-defined, generally prevented by exit policies, and usually
15827 in error. This will also help to detect loops in transparent
15828 proxy configurations. You can disable this feature by setting
15829 "ClientRejectInternalAddresses 0" in your torrc.
15830 - Log a notice when we get a new control connection. Now it's easier
15831 for security-conscious users to recognize when a local application
15832 is knocking on their controller door. Suggested by bug 1196.
15834 o Privacy fixes (newnym):
15835 - Avoid linkability based on cached hidden service descriptors: forget
15836 all hidden service descriptors cached as a client when processing a
15837 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
15838 - On SIGHUP, do not clear out all TrackHostExits mappings, client
15839 DNS cache entries, and virtual address mappings: that's what
15840 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
15841 - Don't attach new streams to old rendezvous circuits after SIGNAL
15842 NEWNYM. Previously, we would keep using an existing rendezvous
15843 circuit if it remained open (i.e. if it were kept open by a
15844 long-lived stream, or if a new stream were attached to it before
15845 Tor could notice that it was old and no longer in use). Bugfix on
15846 0.1.1.15-rc; fixes bug 3375.
15848 o Major bugfixes (relay bandwidth accounting):
15849 - Fix a bug that could break accounting on 64-bit systems with large
15850 time_t values, making them hibernate for impossibly long intervals.
15851 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
15852 - Fix a bug in bandwidth accounting that could make us use twice
15853 the intended bandwidth when our interval start changes due to
15854 daylight saving time. Now we tolerate skew in stored vs computed
15855 interval starts: if the start of the period changes by no more than
15856 50% of the period's duration, we remember bytes that we transferred
15857 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
15859 o Major bugfixes (bridges):
15860 - Bridges now use "reject *:*" as their default exit policy. Bugfix
15861 on 0.2.0.3-alpha. Fixes bug 1113.
15862 - If you configure your bridge with a known identity fingerprint,
15863 and the bridge authority is unreachable (as it is in at least
15864 one country now), fall back to directly requesting the descriptor
15865 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
15867 - Fix a bug where bridge users who configure the non-canonical
15868 address of a bridge automatically switch to its canonical
15869 address. If a bridge listens at more than one address, it
15870 should be able to advertise those addresses independently and
15871 any non-blocked addresses should continue to work. Bugfix on Tor
15872 0.2.0.3-alpha. Fixes bug 2510.
15873 - If you configure Tor to use bridge A, and then quit and
15874 configure Tor to use bridge B instead (or if you change Tor
15875 to use bridge B via the controller), it would happily continue
15876 to use bridge A if it's still reachable. While this behavior is
15877 a feature if your goal is connectivity, in some scenarios it's a
15878 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
15879 - When the controller configures a new bridge, don't wait 10 to 60
15880 seconds before trying to fetch its descriptor. Bugfix on
15881 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
15883 o Major bugfixes (directory authorities):
15884 - Many relays have been falling out of the consensus lately because
15885 not enough authorities know about their descriptor for them to get
15886 a majority of votes. When we deprecated the v2 directory protocol,
15887 we got rid of the only way that v3 authorities can hear from each
15888 other about other descriptors. Now authorities examine every v3
15889 vote for new descriptors, and fetch them from that authority. Bugfix
15891 - Authorities could be tricked into giving out the Exit flag to relays
15892 that didn't allow exiting to any ports. This bug could screw
15893 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
15894 1238. Bug discovered by Martin Kowalczyk.
15895 - If all authorities restart at once right before a consensus vote,
15896 nobody will vote about "Running", and clients will get a consensus
15897 with no usable relays. Instead, authorities refuse to build a
15898 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
15900 o Major bugfixes (stream-level fairness):
15901 - When receiving a circuit-level SENDME for a blocked circuit, try
15902 to package cells fairly from all the streams that had previously
15903 been blocked on that circuit. Previously, we had started with the
15904 oldest stream, and allowed each stream to potentially exhaust
15905 the circuit's package window. This gave older streams on any
15906 given circuit priority over newer ones. Fixes bug 1937. Detected
15907 originally by Camilo Viecco. This bug was introduced before the
15908 first Tor release, in svn commit r152: it is the new winner of
15909 the longest-lived bug prize.
15910 - Fix a stream fairness bug that would cause newer streams on a given
15911 circuit to get preference when reading bytes from the origin or
15912 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
15913 introduced before the first Tor release, in svn revision r152.
15914 - When the exit relay got a circuit-level sendme cell, it started
15915 reading on the exit streams, even if had 500 cells queued in the
15916 circuit queue already, so the circuit queue just grew and grew in
15917 some cases. We fix this by not re-enabling reading on receipt of a
15918 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
15919 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
15921 - Newly created streams were allowed to read cells onto circuits,
15922 even if the circuit's cell queue was blocked and waiting to drain.
15923 This created potential unfairness, as older streams would be
15924 blocked, but newer streams would gladly fill the queue completely.
15925 We add code to detect this situation and prevent any stream from
15926 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
15929 o Major bugfixes (hidden services):
15930 - Apply circuit timeouts to opened hidden-service-related circuits
15931 based on the correct start time. Previously, we would apply the
15932 circuit build timeout based on time since the circuit's creation;
15933 it was supposed to be applied based on time since the circuit
15934 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
15935 - Improve hidden service robustness: When we find that we have
15936 extended a hidden service's introduction circuit to a relay not
15937 listed as an introduction point in the HS descriptor we currently
15938 have, retry with an introduction point from the current
15939 descriptor. Previously we would just give up. Fixes bugs 1024 and
15940 1930; bugfix on 0.2.0.10-alpha.
15941 - Directory authorities now use data collected from their own
15942 uptime observations when choosing whether to assign the HSDir flag
15943 to relays, instead of trusting the uptime value the relay reports in
15944 its descriptor. This change helps prevent an attack where a small
15945 set of nodes with frequently-changing identity keys can blackhole
15946 a hidden service. (Only authorities need upgrade; others will be
15947 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
15948 - Stop assigning the HSDir flag to relays that disable their
15949 DirPort (and thus will refuse to answer directory requests). This
15950 fix should dramatically improve the reachability of hidden services:
15951 hidden services and hidden service clients pick six HSDir relays
15952 to store and retrieve the hidden service descriptor, and currently
15953 about half of the HSDir relays will refuse to work. Bugfix on
15954 0.2.0.10-alpha; fixes part of bug 1693.
15956 o Major bugfixes (misc):
15957 - Clients now stop trying to use an exit node associated with a given
15958 destination by TrackHostExits if they fail to reach that exit node.
15959 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
15960 - Fix a regression that caused Tor to rebind its ports if it receives
15961 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
15962 - Remove an extra pair of quotation marks around the error
15963 message in control-port STATUS_GENERAL BUG events. Bugfix on
15964 0.1.2.6-alpha; fixes bug 3732.
15966 o Minor features (relays):
15967 - Ensure that no empty [dirreq-](read|write)-history lines are added
15968 to an extrainfo document. Implements ticket 2497.
15969 - When bandwidth accounting is enabled, be more generous with how
15970 much bandwidth we'll use up before entering "soft hibernation".
15971 Previously, we'd refuse new connections and circuits once we'd
15972 used up 95% of our allotment. Now, we use up 95% of our allotment,
15973 AND make sure that we have no more than 500MB (or 3 hours of
15974 expected traffic, whichever is lower) remaining before we enter
15976 - Relays now log the reason for publishing a new relay descriptor,
15977 so we have a better chance of hunting down instances of bug 1810.
15978 Resolves ticket 3252.
15979 - Log a little more clearly about the times at which we're no longer
15980 accepting new connections (e.g. due to hibernating). Resolves
15982 - When AllowSingleHopExits is set, print a warning to explain to the
15983 relay operator why most clients are avoiding her relay.
15984 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
15985 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
15986 clients are already deprecated because of security bugs.
15988 o Minor features (network statistics):
15989 - Directory mirrors that set "DirReqStatistics 1" write statistics
15990 about directory requests to disk every 24 hours. As compared to the
15991 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
15992 improvements: 1) stats are written to disk exactly every 24 hours;
15993 2) estimated shares of v2 and v3 requests are determined as mean
15994 values, not at the end of a measurement period; 3) unresolved
15995 requests are listed with country code '??'; 4) directories also
15996 measure download times.
15997 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
15998 number of exit streams and transferred bytes per port to disk every
16000 - Relays that set "CellStatistics 1" write statistics on how long
16001 cells spend in their circuit queues to disk every 24 hours.
16002 - Entry nodes that set "EntryStatistics 1" write statistics on the
16003 rough number and origins of connecting clients to disk every 24
16005 - Relays that write any of the above statistics to disk and set
16006 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
16007 their extra-info documents. Implements proposal 166.
16009 o Minor features (GeoIP and statistics):
16010 - Provide a log message stating which geoip file we're parsing
16011 instead of just stating that we're parsing the geoip file.
16012 Implements ticket 2432.
16013 - Make sure every relay writes a state file at least every 12 hours.
16014 Previously, a relay could go for weeks without writing its state
16015 file, and on a crash could lose its bandwidth history, capacity
16016 estimates, client country statistics, and so on. Addresses bug 3012.
16017 - Relays report the number of bytes spent on answering directory
16018 requests in extra-info descriptors similar to {read,write}-history.
16019 Implements enhancement 1790.
16020 - Report only the top 10 ports in exit-port stats in order not to
16021 exceed the maximum extra-info descriptor length of 50 KB. Implements
16023 - If writing the state file to disk fails, wait up to an hour before
16024 retrying again, rather than trying again each second. Fixes bug
16025 2346; bugfix on Tor 0.1.1.3-alpha.
16026 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
16027 when we switch from being a public relay to a bridge. Otherwise
16028 there will still be clients that see the relay in their consensus,
16029 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
16031 - Update to the August 2 2011 Maxmind GeoLite Country database.
16033 o Minor features (clients):
16034 - When expiring circuits, use microsecond timers rather than
16035 one-second timers. This can avoid an unpleasant situation where a
16036 circuit is launched near the end of one second and expired right
16037 near the beginning of the next, and prevent fluctuations in circuit
16039 - If we've configured EntryNodes and our network goes away and/or all
16040 our entrynodes get marked down, optimistically retry them all when
16041 a new socks application request appears. Fixes bug 1882.
16042 - Always perform router selections using weighted relay bandwidth,
16043 even if we don't need a high capacity circuit at the time. Non-fast
16044 circuits now only differ from fast ones in that they can use relays
16045 not marked with the Fast flag. This "feature" could turn out to
16046 be a horrible bug; we should investigate more before it goes into
16048 - When we run out of directory information such that we can't build
16049 circuits, but then get enough that we can build circuits, log when
16050 we actually construct a circuit, so the user has a better chance of
16051 knowing what's going on. Fixes bug 1362.
16052 - Log SSL state transitions at debug level during handshake, and
16053 include SSL states in error messages. This may help debug future
16054 SSL handshake issues.
16056 o Minor features (directory authorities):
16057 - When a router changes IP address or port, authorities now launch
16058 a new reachability test for it. Implements ticket 1899.
16059 - Directory authorities now reject relays running any versions of
16060 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
16061 known bugs that keep RELAY_EARLY cells from working on rendezvous
16062 circuits. Followup to fix for bug 2081.
16063 - Directory authorities now reject relays running any version of Tor
16064 older than 0.2.0.26-rc. That version is the earliest that fetches
16065 current directory information correctly. Fixes bug 2156.
16066 - Directory authorities now do an immediate reachability check as soon
16067 as they hear about a new relay. This change should slightly reduce
16068 the time between setting up a relay and getting listed as running
16069 in the consensus. It should also improve the time between setting
16070 up a bridge and seeing use by bridge users.
16071 - Directory authorities no longer launch a TLS connection to every
16072 relay as they startup. Now that we have 2k+ descriptors cached,
16073 the resulting network hiccup is becoming a burden. Besides,
16074 authorities already avoid voting about Running for the first half
16075 hour of their uptime.
16076 - Directory authorities now log the source of a rejected POSTed v3
16077 networkstatus vote, so we can track failures better.
16078 - Backport code from 0.2.3.x that allows directory authorities to
16079 clean their microdescriptor caches. Needed to resolve bug 2230.
16081 o Minor features (hidden services):
16082 - Use computed circuit-build timeouts to decide when to launch
16083 parallel introduction circuits for hidden services. (Previously,
16084 we would retry after 15 seconds.)
16085 - Don't allow v0 hidden service authorities to act as clients.
16086 Required by fix for bug 3000.
16087 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
16088 by fix for bug 3000.
16089 - Make hidden services work better in private Tor networks by not
16090 requiring any uptime to join the hidden service descriptor
16091 DHT. Implements ticket 2088.
16092 - Log (at info level) when purging pieces of hidden-service-client
16093 state because of SIGNAL NEWNYM.
16095 o Minor features (controller interface):
16096 - New "GETINFO net/listeners/(type)" controller command to return
16097 a list of addresses and ports that are bound for listeners for a
16098 given connection type. This is useful when the user has configured
16099 "SocksPort auto" and the controller needs to know which port got
16100 chosen. Resolves another part of ticket 3076.
16101 - Have the controller interface give a more useful message than
16102 "Internal Error" in response to failed GETINFO requests.
16103 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
16104 event, to give information on the current rate of circuit timeouts
16105 over our stored history.
16106 - The 'EXTENDCIRCUIT' control port command can now be used with
16107 a circ id of 0 and no path. This feature will cause Tor to build
16108 a new 'fast' general purpose circuit using its own path selection
16110 - Added a BUILDTIMEOUT_SET controller event to describe changes
16111 to the circuit build timeout.
16112 - New controller command "getinfo config-text". It returns the
16113 contents that Tor would write if you send it a SAVECONF command,
16114 so the controller can write the file to disk itself.
16116 o Minor features (controller protocol):
16117 - Add a new ControlSocketsGroupWritable configuration option: when
16118 it is turned on, ControlSockets are group-writeable by the default
16119 group of the current user. Patch by Jérémy Bobbio; implements
16121 - Tor now refuses to create a ControlSocket in a directory that is
16122 world-readable (or group-readable if ControlSocketsGroupWritable
16123 is 0). This is necessary because some operating systems do not
16124 enforce permissions on an AF_UNIX sockets. Permissions on the
16125 directory holding the socket, however, seems to work everywhere.
16126 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
16127 not. This would lead to a cookie that is still not group readable.
16128 Closes bug 1843. Suggested by katmagic.
16129 - Future-proof the controller protocol a bit by ignoring keyword
16130 arguments we do not recognize.
16132 o Minor features (more useful logging):
16133 - Revise most log messages that refer to nodes by nickname to
16134 instead use the "$key=nickname at address" format. This should be
16135 more useful, especially since nicknames are less and less likely
16136 to be unique. Resolves ticket 3045.
16137 - When an HTTPS proxy reports "403 Forbidden", we now explain
16138 what it means rather than calling it an unexpected status code.
16139 Closes bug 2503. Patch from Michael Yakubovich.
16140 - Rate-limit a warning about failures to download v2 networkstatus
16141 documents. Resolves part of bug 1352.
16142 - Rate-limit the "your application is giving Tor only an IP address"
16143 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
16144 - Rate-limit "Failed to hand off onionskin" warnings.
16145 - When logging a rate-limited warning, we now mention how many messages
16146 got suppressed since the last warning.
16147 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
16148 2 no signature, 4 required" messages about consensus signatures
16149 easier to read, and make sure they get logged at the same severity
16150 as the messages explaining which keys are which. Fixes bug 1290.
16151 - Don't warn when we have a consensus that we can't verify because
16152 of missing certificates, unless those certificates are ones
16153 that we have been trying and failing to download. Fixes bug 1145.
16155 o Minor features (log domains):
16156 - Add documentation for configuring logging at different severities in
16157 different log domains. We've had this feature since 0.2.1.1-alpha,
16158 but for some reason it never made it into the manpage. Fixes
16160 - Make it simpler to specify "All log domains except for A and B".
16161 Previously you needed to say "[*,~A,~B]". Now you can just say
16163 - Add a "LogMessageDomains 1" option to include the domains of log
16164 messages along with the messages. Without this, there's no way
16165 to use log domains without reading the source or doing a lot
16167 - Add a new "Handshake" log domain for activities that happen
16168 during the TLS handshake.
16170 o Minor features (build process):
16171 - Make compilation with clang possible when using
16172 "--enable-gcc-warnings" by removing two warning options that clang
16173 hasn't implemented yet and by fixing a few warnings. Resolves
16175 - Detect platforms that brokenly use a signed size_t, and refuse to
16176 build there. Found and analyzed by doorss and rransom.
16177 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
16179 - Add support for statically linking zlib by specifying
16180 "--enable-static-zlib", to go with our support for statically
16181 linking openssl and libevent. Resolves bug 1358.
16182 - Instead of adding the svn revision to the Tor version string, report
16183 the git commit (when we're building from a git checkout).
16184 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
16186 - New --digests command-line switch to output the digests of the
16187 source files Tor was built with.
16188 - Generate our manpage and HTML documentation using Asciidoc. This
16189 change should make it easier to maintain the documentation, and
16190 produce nicer HTML. The build process fails if asciidoc cannot
16191 be found and building with asciidoc isn't disabled (via the
16192 "--disable-asciidoc" argument to ./configure. Skipping the manpage
16193 speeds up the build considerably.
16195 o Minor features (options / torrc):
16196 - Warn when the same option is provided more than once in a torrc
16197 file, on the command line, or in a single SETCONF statement, and
16198 the option is one that only accepts a single line. Closes bug 1384.
16199 - Warn when the user configures two HiddenServiceDir lines that point
16200 to the same directory. Bugfix on 0.0.6 (the version introducing
16201 HiddenServiceDir); fixes bug 3289.
16202 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
16203 do individual connection-level rate limiting of clients. The torrc
16204 config options with the same names trump the consensus params, if
16205 both are present. Replaces the old "bwconnrate" and "bwconnburst"
16206 consensus params which were broken from 0.2.2.7-alpha through
16207 0.2.2.14-alpha. Closes bug 1947.
16208 - New config option "WarnUnsafeSocks 0" disables the warning that
16209 occurs whenever Tor receives a socks handshake using a version of
16210 the socks protocol that can only provide an IP address (rather
16211 than a hostname). Setups that do DNS locally over Tor are fine,
16212 and we shouldn't spam the logs in that case.
16213 - New config option "CircuitStreamTimeout" to override our internal
16214 timeout schedule for how many seconds until we detach a stream from
16215 a circuit and try a new circuit. If your network is particularly
16216 slow, you might want to set this to a number like 60.
16217 - New options for SafeLogging to allow scrubbing only log messages
16218 generated while acting as a relay. Specify "SafeLogging relay" if
16219 you want to ensure that only messages known to originate from
16220 client use of the Tor process will be logged unsafely.
16221 - Time and memory units in the configuration file can now be set to
16222 fractional units. For example, "2.5 GB" is now a valid value for
16224 - Support line continuations in the torrc config file. If a line
16225 ends with a single backslash character, the newline is ignored, and
16226 the configuration value is treated as continuing on the next line.
16229 o Minor features (unit tests):
16230 - Revise our unit tests to use the "tinytest" framework, so we
16231 can run tests in their own processes, have smarter setup/teardown
16232 code, and so on. The unit test code has moved to its own
16233 subdirectory, and has been split into multiple modules.
16234 - Add a unit test for cross-platform directory-listing code.
16235 - Add some forgotten return value checks during unit tests. Found
16237 - Use GetTempDir to find the proper temporary directory location on
16238 Windows when generating temporary files for the unit tests. Patch
16241 o Minor features (misc):
16242 - The "torify" script now uses torsocks where available.
16243 - Make Libevent log messages get delivered to controllers later,
16244 and not from inside the Libevent log handler. This prevents unsafe
16245 reentrant Libevent calls while still letting the log messages
16247 - Certain Tor clients (such as those behind check.torproject.org) may
16248 want to fetch the consensus in an extra early manner. To enable this
16249 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
16250 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
16251 as only certain clients who must have this information sooner should
16253 - Expand homedirs passed to tor-checkkey. This should silence a
16254 coverity complaint about passing a user-supplied string into
16255 open() without checking it.
16256 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
16257 used on bridges, and it makes bridge scanning somewhat easier.
16258 - Create the /var/run/tor directory on startup on OpenSUSE if it is
16259 not already created. Patch from Andreas Stieger. Fixes bug 2573.
16261 o Minor bugfixes (relays):
16262 - When a relay decides that its DNS is too broken for it to serve
16263 as an exit server, it advertised itself as a non-exit, but
16264 continued to act as an exit. This could create accidental
16265 partitioning opportunities for users. Instead, if a relay is
16266 going to advertise reject *:* as its exit policy, it should
16267 really act with exit policy "reject *:*". Fixes bug 2366.
16268 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
16269 - Publish a router descriptor even if generating an extra-info
16270 descriptor fails. Previously we would not publish a router
16271 descriptor without an extra-info descriptor; this can cause fast
16272 exit relays collecting exit-port statistics to drop from the
16273 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
16274 - When we're trying to guess whether we know our IP address as
16275 a relay, we would log various ways that we failed to guess
16276 our address, but never log that we ended up guessing it
16277 successfully. Now add a log line to help confused and anxious
16278 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
16279 - For bandwidth accounting, calculate our expected bandwidth rate
16280 based on the time during which we were active and not in
16281 soft-hibernation during the last interval. Previously, we were
16282 also considering the time spent in soft-hibernation. If this
16283 was a long time, we would wind up underestimating our bandwidth
16284 by a lot, and skewing our wakeup time towards the start of the
16285 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
16286 - Demote a confusing TLS warning that relay operators might get when
16287 someone tries to talk to their ORPort. It is not the operator's
16288 fault, nor can they do anything about it. Fixes bug 1364; bugfix
16290 - Change "Application request when we're believed to be offline."
16291 notice to "Application request when we haven't used client
16292 functionality lately.", to clarify that it's not an error. Bugfix
16293 on 0.0.9.3; fixes bug 1222.
16295 o Minor bugfixes (bridges):
16296 - When a client starts or stops using bridges, never use a circuit
16297 that was built before the configuration change. This behavior could
16298 put at risk a user who uses bridges to ensure that her traffic
16299 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
16301 - Do not reset the bridge descriptor download status every time we
16302 re-parse our configuration or get a configuration change. Fixes
16303 bug 3019; bugfix on 0.2.0.3-alpha.
16304 - Users couldn't configure a regular relay to be their bridge. It
16305 didn't work because when Tor fetched the bridge descriptor, it found
16306 that it already had it, and didn't realize that the purpose of the
16307 descriptor had changed. Now we replace routers with a purpose other
16308 than bridge with bridge descriptors when fetching them. Bugfix on
16309 0.1.1.9-alpha. Fixes bug 1776.
16310 - In the special case where you configure a public exit relay as your
16311 bridge, Tor would be willing to use that exit relay as the last
16312 hop in your circuit as well. Now we fail that circuit instead.
16313 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
16315 o Minor bugfixes (clients):
16316 - We now ask the other side of a stream (the client or the exit)
16317 for more data on that stream when the amount of queued data on
16318 that stream dips low enough. Previously, we wouldn't ask the
16319 other side for more data until either it sent us more data (which
16320 it wasn't supposed to do if it had exhausted its window!) or we
16321 had completely flushed all our queued data. This flow control fix
16322 should improve throughput. Fixes bug 2756; bugfix on the earliest
16323 released versions of Tor (svn commit r152).
16324 - When a client finds that an origin circuit has run out of 16-bit
16325 stream IDs, we now mark it as unusable for new streams. Previously,
16326 we would try to close the entire circuit. Bugfix on 0.0.6.
16327 - Make it explicit that we don't cannibalize one-hop circuits. This
16328 happens in the wild, but doesn't turn out to be a problem because
16329 we fortunately don't use those circuits. Many thanks to outofwords
16330 for the initial analysis and to swissknife who confirmed that
16331 two-hop circuits are actually created.
16332 - Resolve an edge case in path weighting that could make us misweight
16333 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
16334 - Make the DNSPort option work with libevent 2.x. Don't alter the
16335 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
16337 o Minor bugfixes (directory authorities):
16338 - Make directory authorities more accurate at recording when
16339 relays that have failed several reachability tests became
16340 unreachable, so we can provide more accuracy at assigning Stable,
16341 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
16342 - Directory authorities are now more robust to hops back in time
16343 when calculating router stability. Previously, if a run of uptime
16344 or downtime appeared to be negative, the calculation could give
16345 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
16347 - Directory authorities will now attempt to download consensuses
16348 if their own efforts to make a live consensus have failed. This
16349 change means authorities that restart will fetch a valid
16350 consensus, and it means authorities that didn't agree with the
16351 current consensus will still fetch and serve it if it has enough
16352 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
16353 - Never vote for a server as "Running" if we have a descriptor for
16354 it claiming to be hibernating, and that descriptor was published
16355 more recently than our last contact with the server. Bugfix on
16356 0.2.0.3-alpha; fixes bug 911.
16357 - Directory authorities no longer change their opinion of, or vote on,
16358 whether a router is Running, unless they have themselves been
16359 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
16362 o Minor bugfixes (hidden services):
16363 - Log malformed requests for rendezvous descriptors as protocol
16364 warnings, not warnings. Also, use a more informative log message
16365 in case someone sees it at log level warning without prior
16366 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
16367 - Accept hidden service descriptors if we think we might be a hidden
16368 service directory, regardless of what our consensus says. This
16369 helps robustness, since clients and hidden services can sometimes
16370 have a more up-to-date view of the network consensus than we do,
16371 and if they think that the directory authorities list us a HSDir,
16372 we might actually be one. Related to bug 2732; bugfix on
16374 - Correct the warning displayed when a rendezvous descriptor exceeds
16375 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
16377 - Clients and hidden services now use HSDir-flagged relays for hidden
16378 service descriptor downloads and uploads even if the relays have no
16379 DirPort set and the client has disabled TunnelDirConns. This will
16380 eventually allow us to give the HSDir flag to relays with no
16381 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
16382 - Only limit the lengths of single HS descriptors, even when multiple
16383 HS descriptors are published to an HSDir relay in a single POST
16384 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
16386 o Minor bugfixes (controllers):
16387 - Allow GETINFO fingerprint to return a fingerprint even when
16388 we have not yet built a router descriptor. Fixes bug 3577;
16389 bugfix on 0.2.0.1-alpha.
16390 - Send a SUCCEEDED stream event to the controller when a reverse
16391 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
16392 discovered by katmagic.
16393 - Remove a trailing asterisk from "exit-policy/default" in the
16394 output of the control port command "GETINFO info/names". Bugfix
16396 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
16397 2917. Bugfix on 0.1.1.1-alpha.
16398 - When we restart our relay, we might get a successful connection
16399 from the outside before we've started our reachability tests,
16400 triggering a warning: "ORPort found reachable, but I have no
16401 routerinfo yet. Failing to inform controller of success." This
16402 bug was harmless unless Tor is running under a controller
16403 like Vidalia, in which case the controller would never get a
16404 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
16406 - When a controller changes TrackHostExits, remove mappings for
16407 hosts that should no longer have their exits tracked. Bugfix on
16409 - When a controller changes VirtualAddrNetwork, remove any mappings
16410 for hosts that were automapped to the old network. Bugfix on
16412 - When a controller changes one of the AutomapHosts* options, remove
16413 any mappings for hosts that should no longer be automapped. Bugfix
16415 - Fix an off-by-one error in calculating some controller command
16416 argument lengths. Fortunately, this mistake is harmless since
16417 the controller code does redundant NUL termination too. Found by
16418 boboper. Bugfix on 0.1.1.1-alpha.
16419 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
16420 would return "551 Internal error" rather than "552 Unrecognized key
16421 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
16422 - Don't spam the controller with events when we have no file
16423 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
16424 for log messages was already solved from bug 748.)
16425 - Emit a GUARD DROPPED controller event for a case we missed.
16426 - Ensure DNS requests launched by "RESOLVE" commands from the
16427 controller respect the __LeaveStreamsUnattached setconf options. The
16428 same goes for requests launched via DNSPort or transparent
16429 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
16431 o Minor bugfixes (config options):
16432 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
16433 Change the limit to 512 characters by removing base64 newlines.
16434 Fixes bug 2752. Fix by Michael Yakubovich.
16435 - Complain if PublishServerDescriptor is given multiple arguments that
16436 include 0 or 1. This configuration will be rejected in the future.
16437 Bugfix on 0.2.0.1-alpha; closes bug 1107.
16438 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
16439 Bugfix on 0.2.0.13-alpha; closes bug 928.
16441 o Minor bugfixes (log subsystem fixes):
16442 - When unable to format an address as a string, report its value
16443 as "???" rather than reusing the last formatted address. Bugfix
16445 - Be more consistent in our treatment of file system paths. "~" should
16446 get expanded to the user's home directory in the Log config option.
16447 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
16448 feature for the -f and --DataDirectory options.
16450 o Minor bugfixes (memory management):
16451 - Don't stack-allocate the list of supplementary GIDs when we're
16452 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
16453 could take up to 256K, which is way too much stack. Found by
16454 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
16455 - Save a couple bytes in memory allocation every time we escape
16456 certain characters in a string. Patch from Florian Zumbiehl.
16458 o Minor bugfixes (protocol correctness):
16459 - When checking for 1024-bit keys, check for 1024 bits, not 128
16460 bytes. This allows Tor to correctly discard keys of length 1017
16461 through 1023. Bugfix on 0.0.9pre5.
16462 - Require that introduction point keys and onion handshake keys
16463 have a public exponent of 65537. Starts to fix bug 3207; bugfix
16465 - Handle SOCKS messages longer than 128 bytes long correctly, rather
16466 than waiting forever for them to finish. Fixes bug 2330; bugfix
16467 on 0.2.0.16-alpha. Found by doorss.
16468 - Never relay a cell for a circuit we have already destroyed.
16469 Between marking a circuit as closeable and finally closing it,
16470 it may have been possible for a few queued cells to get relayed,
16471 even though they would have been immediately dropped by the next
16472 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
16473 - Never queue a cell for a circuit that's already been marked
16475 - Fix a spec conformance issue: the network-status-version token
16476 must be the first token in a v3 consensus or vote. Discovered by
16477 "parakeep". Bugfix on 0.2.0.3-alpha.
16478 - A networkstatus vote must contain exactly one signature. Spec
16479 conformance issue. Bugfix on 0.2.0.3-alpha.
16480 - When asked about a DNS record type we don't support via a
16481 client DNSPort, reply with NOTIMPL rather than an empty
16482 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
16483 - Make more fields in the controller protocol case-insensitive, since
16484 control-spec.txt said they were.
16486 o Minor bugfixes (log messages):
16487 - Fix a log message that said "bits" while displaying a value in
16488 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
16490 - Downgrade "no current certificates known for authority" message from
16491 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
16492 - Correctly describe errors that occur when generating a TLS object.
16493 Previously we would attribute them to a failure while generating a
16494 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
16496 - Fix an instance where a Tor directory mirror might accidentally
16497 log the IP address of a misbehaving Tor client. Bugfix on
16499 - Stop logging at severity 'warn' when some other Tor client tries
16500 to establish a circuit with us using weak DH keys. It's a protocol
16501 violation, but that doesn't mean ordinary users need to hear about
16502 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
16503 - If your relay can't keep up with the number of incoming create
16504 cells, it would log one warning per failure into your logs. Limit
16505 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
16507 o Minor bugfixes (build fixes):
16508 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
16509 - When warning about missing zlib development packages during compile,
16510 give the correct package names. Bugfix on 0.2.0.1-alpha.
16511 - Fix warnings that newer versions of autoconf produce during
16512 ./autogen.sh. These warnings appear to be harmless in our case,
16513 but they were extremely verbose. Fixes bug 2020.
16514 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
16517 o Minor bugfixes (portability):
16518 - Write several files in text mode, on OSes that distinguish text
16519 mode from binary mode (namely, Windows). These files are:
16520 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
16521 that collect those statistics; 'client_keys' and 'hostname' for
16522 hidden services that use authentication; and (in the tor-gencert
16523 utility) newly generated identity and signing keys. Previously,
16524 we wouldn't specify text mode or binary mode, leading to an
16525 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
16526 the DirRecordUsageByCountry option which would have triggered
16527 the assertion failure was added), although this assertion failure
16528 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
16529 - Selectively disable deprecation warnings on OS X because Lion
16530 started deprecating the shipped copy of openssl. Fixes bug 3643.
16531 - Use a wide type to hold sockets when built for 64-bit Windows.
16533 - Fix an issue that prevented static linking of libevent on
16534 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
16535 where we introduced the "--with-static-libevent" configure option.
16536 - Fix a bug with our locking implementation on Windows that couldn't
16537 correctly detect when a file was already locked. Fixes bug 2504,
16538 bugfix on 0.2.1.6-alpha.
16539 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
16541 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
16542 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
16545 o Minor bugfixes (code correctness):
16546 - Always NUL-terminate the sun_path field of a sockaddr_un before
16547 passing it to the kernel. (Not a security issue: kernels are
16548 smart enough to reject bad sockaddr_uns.) Found by Coverity;
16549 CID #428. Bugfix on Tor 0.2.0.3-alpha.
16550 - Make connection_printf_to_buf()'s behavior sane. Its callers
16551 expect it to emit a CRLF iff the format string ends with CRLF;
16552 it actually emitted a CRLF iff (a) the format string ended with
16553 CRLF or (b) the resulting string was over 1023 characters long or
16554 (c) the format string did not end with CRLF *and* the resulting
16555 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
16556 fixes part of bug 3407.
16557 - Make send_control_event_impl()'s behavior sane. Its callers
16558 expect it to always emit a CRLF at the end of the string; it
16559 might have emitted extra control characters as well. Bugfix on
16560 0.1.1.9-alpha; fixes another part of bug 3407.
16561 - Make crypto_rand_int() check the value of its input correctly.
16562 Previously, it accepted values up to UINT_MAX, but could return a
16563 negative number if given a value above INT_MAX+1. Found by George
16564 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
16565 - Fix a potential null-pointer dereference while computing a
16566 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
16568 - If we fail to compute the identity digest of a v3 legacy keypair,
16569 warn, and don't use a buffer-full of junk instead. Bugfix on
16570 0.2.1.1-alpha; fixes bug 3106.
16571 - Resolve an untriggerable issue in smartlist_string_num_isin(),
16572 where if the function had ever in the future been used to check
16573 for the presence of a too-large number, it would have given an
16574 incorrect result. (Fortunately, we only used it for 16-bit
16575 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
16576 - Be more careful about reporting the correct error from a failed
16577 connect() system call. Under some circumstances, it was possible to
16578 look at an incorrect value for errno when sending the end reason.
16579 Bugfix on 0.1.0.1-rc.
16580 - Correctly handle an "impossible" overflow cases in connection byte
16581 counting, where we write or read more than 4GB on an edge connection
16582 in a single second. Bugfix on 0.1.2.8-beta.
16583 - Avoid a double mark-for-free warning when failing to attach a
16584 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
16586 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
16587 found by "cypherpunks". This bug was introduced before the first
16588 Tor release, in svn commit r110.
16589 - Fix a bug in bandwidth history state parsing that could have been
16590 triggered if a future version of Tor ever changed the timing
16591 granularity at which bandwidth history is measured. Bugfix on
16592 Tor 0.1.1.11-alpha.
16593 - Add assertions to check for overflow in arguments to
16594 base32_encode() and base32_decode(); fix a signed-unsigned
16595 comparison there too. These bugs are not actually reachable in Tor,
16596 but it's good to prevent future errors too. Found by doorss.
16597 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
16599 - Set target port in get_interface_address6() correctly. Bugfix
16600 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
16601 - Fix an impossible-to-actually-trigger buffer overflow in relay
16602 descriptor generation. Bugfix on 0.1.0.15.
16603 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
16605 o Minor bugfixes (code improvements):
16606 - After we free an internal connection structure, overwrite it
16607 with a different memory value than we use for overwriting a freed
16608 internal circuit structure. Should help with debugging. Suggested
16610 - If OpenSSL fails to make a duplicate of a private or public key, log
16611 an error message and try to exit cleanly. May help with debugging
16612 if bug 1209 ever remanifests.
16613 - Some options used different conventions for uppercasing of acronyms
16614 when comparing manpage and source. Fix those in favor of the
16615 manpage, as it makes sense to capitalize acronyms.
16616 - Take a first step towards making or.h smaller by splitting out
16617 function definitions for all source files in src/or/. Leave
16618 structures and defines in or.h for now.
16619 - Remove a few dead assignments during router parsing. Found by
16621 - Don't use 1-bit wide signed bit fields. Found by coverity.
16622 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
16623 None of the cases where we did this before were wrong, but by making
16624 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
16625 - The memarea code now uses a sentinel value at the end of each area
16626 to make sure nothing writes beyond the end of an area. This might
16627 help debug some conceivable causes of bug 930.
16628 - Always treat failure to allocate an RSA key as an unrecoverable
16630 - Add some more defensive programming for architectures that can't
16631 handle unaligned integer accesses. We don't know of any actual bugs
16632 right now, but that's the best time to fix them. Fixes bug 1943.
16634 o Minor bugfixes (misc):
16635 - Fix a rare bug in rend_fn unit tests: we would fail a test when
16636 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
16637 on 0.2.0.10-alpha; fixes bug 1808.
16638 - Where available, use Libevent 2.0's periodic timers so that our
16639 once-per-second cleanup code gets called even more closely to
16640 once per second than it would otherwise. Fixes bug 943.
16641 - Ignore OutboundBindAddress when connecting to localhost.
16642 Connections to localhost need to come _from_ localhost, or else
16643 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
16645 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
16647 - If any of the v3 certs we download are unparseable, we should
16648 actually notice the failure so we don't retry indefinitely. Bugfix
16649 on 0.2.0.x; reported by "rotator".
16650 - When Tor fails to parse a descriptor of any kind, dump it to disk.
16651 Might help diagnosing bug 1051.
16652 - Make our 'torify' script more portable; if we have only one of
16653 'torsocks' or 'tsocks' installed, don't complain to the user;
16654 and explain our warning about tsocks better.
16655 - Fix some urls in the exit notice file and make it XHTML1.1 strict
16656 compliant. Based on a patch from Christian Kujau.
16658 o Documentation changes:
16659 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
16660 - Resolve all doxygen warnings except those for missing documentation.
16662 - Add doxygen documentation for more functions, fields, and types.
16663 - Convert the HACKING file to asciidoc, and add a few new sections
16664 to it, explaining how we use Git, how we make changelogs, and
16665 what should go in a patch.
16666 - Document the default socks host and port (127.0.0.1:9050) for
16668 - Removed some unnecessary files from the source distribution. The
16669 AUTHORS file has now been merged into the people page on the
16670 website. The roadmaps and design doc can now be found in the
16671 projects directory in svn.
16673 o Deprecated and removed features (config):
16674 - Remove the torrc.complete file. It hasn't been kept up to date
16675 and users will have better luck checking out the manpage.
16676 - Remove the HSAuthorityRecordStats option that version 0 hidden
16677 service authorities could use to track statistics of overall v0
16678 hidden service usage.
16679 - Remove the obsolete "NoPublish" option; it has been flagged
16680 as obsolete and has produced a warning since 0.1.1.18-rc.
16681 - Caches no longer download and serve v2 networkstatus documents
16682 unless FetchV2Networkstatus flag is set: these documents haven't
16683 haven't been used by clients or relays since 0.2.0.x. Resolves
16686 o Deprecated and removed features (controller):
16687 - The controller no longer accepts the old obsolete "addr-mappings/"
16688 or "unregistered-servers-" GETINFO values.
16689 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
16690 always on; using them is necessary for correct forward-compatible
16693 o Deprecated and removed features (misc):
16694 - Hidden services no longer publish version 0 descriptors, and clients
16695 do not request or use version 0 descriptors. However, the old hidden
16696 service authorities still accept and serve version 0 descriptors
16697 when contacted by older hidden services/clients.
16698 - Remove undocumented option "-F" from tor-resolve: it hasn't done
16699 anything since 0.2.1.16-rc.
16700 - Remove everything related to building the expert bundle for OS X.
16701 It has confused many users, doesn't work right on OS X 10.6,
16702 and is hard to get rid of once installed. Resolves bug 1274.
16703 - Remove support for .noconnect style addresses. Nobody was using
16704 them, and they provided another avenue for detecting Tor users
16705 via application-level web tricks.
16706 - When we fixed bug 1038 we had to put in a restriction not to send
16707 RELAY_EARLY cells on rend circuits. This was necessary as long
16708 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
16709 active. Now remove this obsolete check. Resolves bug 2081.
16710 - Remove workaround code to handle directory responses from servers
16711 that had bug 539 (they would send HTTP status 503 responses _and_
16712 send a body too). Since only server versions before
16713 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
16714 keep the workaround in place.
16715 - Remove the old 'fuzzy time' logic. It was supposed to be used for
16716 handling calculations where we have a known amount of clock skew and
16717 an allowed amount of unknown skew. But we only used it in three
16718 places, and we never adjusted the known/unknown skew values. This is
16719 still something we might want to do someday, but if we do, we'll
16720 want to do it differently.
16721 - Remove the "--enable-iphone" option to ./configure. According to
16722 reports from Marco Bonetti, Tor builds fine without any special
16723 tweaking on recent iPhone SDK versions.
16726 Changes in version 0.2.1.30 - 2011-02-23
16727 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
16728 change is a slight tweak to Tor's TLS handshake that makes relays
16729 and bridges that run this new version reachable from Iran again.
16730 We don't expect this tweak will win the arms race long-term, but it
16731 buys us time until we roll out a better solution.
16734 - Stop sending a CLOCK_SKEW controller status event whenever
16735 we fetch directory information from a relay that has a wrong clock.
16736 Instead, only inform the controller when it's a trusted authority
16737 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
16738 the rest of bug 1074.
16739 - Fix a bounds-checking error that could allow an attacker to
16740 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
16741 Found by "piebeer".
16742 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
16743 Tor would ignore their RelayBandwidthBurst setting,
16744 potentially using more bandwidth than expected. Bugfix on
16745 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
16746 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
16747 hidserv" in her torrc. The 'hidserv' argument never controlled
16748 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
16751 - Adjust our TLS Diffie-Hellman parameters to match those used by
16753 - Update to the February 1 2011 Maxmind GeoLite Country database.
16756 - Check for and reject overly long directory certificates and
16757 directory tokens before they have a chance to hit any assertions.
16758 Bugfix on 0.2.1.28. Found by "doorss".
16759 - Bring the logic that gathers routerinfos and assesses the
16760 acceptability of circuits into line. This prevents a Tor OP from
16761 getting locked in a cycle of choosing its local OR as an exit for a
16762 path (due to a .exit request) and then rejecting the circuit because
16763 its OR is not listed yet. It also prevents Tor clients from using an
16764 OR running in the same instance as an exit (due to a .exit request)
16765 if the OR does not meet the same requirements expected of an OR
16766 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
16768 o Packaging changes:
16769 - Stop shipping the Tor specs files and development proposal documents
16770 in the tarball. They are now in a separate git repository at
16771 git://git.torproject.org/torspec.git
16772 - Do not include Git version tags as though they are SVN tags when
16773 generating a tarball from inside a repository that has switched
16774 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
16777 Changes in version 0.2.1.29 - 2011-01-15
16778 Tor 0.2.1.29 continues our recent code security audit work. The main
16779 fix resolves a remote heap overflow vulnerability that can allow remote
16780 code execution. Other fixes address a variety of assert and crash bugs,
16781 most of which we think are hard to exploit remotely.
16783 o Major bugfixes (security):
16784 - Fix a heap overflow bug where an adversary could cause heap
16785 corruption. This bug probably allows remote code execution
16786 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
16788 - Prevent a denial-of-service attack by disallowing any
16789 zlib-compressed data whose compression factor is implausibly
16790 high. Fixes part of bug 2324; reported by "doorss".
16791 - Zero out a few more keys in memory before freeing them. Fixes
16792 bug 2384 and part of bug 2385. These key instances found by
16793 "cypherpunks", based on Andrew Case's report about being able
16794 to find sensitive data in Tor's memory space if you have enough
16795 permissions. Bugfix on 0.0.2pre9.
16797 o Major bugfixes (crashes):
16798 - Prevent calls to Libevent from inside Libevent log handlers.
16799 This had potential to cause a nasty set of crashes, especially
16800 if running Libevent with debug logging enabled, and running
16801 Tor with a controller watching for low-severity log messages.
16802 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
16803 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
16804 underflow errors there too. Fixes the other part of bug 2324.
16805 - Fix a bug where we would assert if we ever had a
16806 cached-descriptors.new file (or another file read directly into
16807 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
16808 on 0.2.1.25. Found by doorss.
16809 - Fix some potential asserts and parsing issues with grossly
16810 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
16813 o Minor bugfixes (other):
16814 - Fix a bug with handling misformed replies to reverse DNS lookup
16815 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
16816 bug reported by doorss.
16817 - Fix compilation on mingw when a pthreads compatibility library
16818 has been installed. (We don't want to use it, so we shouldn't
16819 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
16820 - Fix a bug where we would declare that we had run out of virtual
16821 addresses when the address space was only half-exhausted. Bugfix
16823 - Correctly handle the case where AutomapHostsOnResolve is set but
16824 no virtual addresses are available. Fixes bug 2328; bugfix on
16825 0.1.2.1-alpha. Bug found by doorss.
16826 - Correctly handle wrapping around when we run out of virtual
16827 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
16830 - Update to the January 1 2011 Maxmind GeoLite Country database.
16831 - Introduce output size checks on all of our decryption functions.
16834 - Tor does not build packages correctly with Automake 1.6 and earlier;
16835 added a check to Makefile.am to make sure that we're building with
16836 Automake 1.7 or later.
16837 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
16838 because we built it with a too-old version of automake. Thus that
16839 release broke ./configure --enable-openbsd-malloc, which is popular
16840 among really fast exit relays on Linux.
16843 Changes in version 0.2.1.28 - 2010-12-17
16844 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
16845 exploitable bugs. We also took this opportunity to change the IP address
16846 for one of our directory authorities, and to update the geoip database
16850 - Fix a remotely exploitable bug that could be used to crash instances
16851 of Tor remotely by overflowing on the heap. Remote-code execution
16852 hasn't been confirmed, but can't be ruled out. Everyone should
16853 upgrade. Bugfix on the 0.1.1 series and later.
16855 o Directory authority changes:
16856 - Change IP address and ports for gabelmoo (v3 directory authority).
16859 - Update to the December 1 2010 Maxmind GeoLite Country database.
16862 Changes in version 0.2.1.27 - 2010-11-23
16863 Yet another OpenSSL security patch broke its compatibility with Tor:
16864 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
16865 also took this opportunity to fix several crash bugs, integrate a new
16866 directory authority, and update the bundled GeoIP database.
16869 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
16870 No longer set the tlsext_host_name extension on server SSL objects;
16871 but continue to set it on client SSL objects. Our goal in setting
16872 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
16873 bugfix on 0.2.1.1-alpha.
16874 - Do not log messages to the controller while shrinking buffer
16875 freelists. Doing so would sometimes make the controller connection
16876 try to allocate a buffer chunk, which would mess up the internals
16877 of the freelist and cause an assertion failure. Fixes bug 1125;
16878 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
16879 - Learn our external IP address when we're a relay or bridge, even if
16880 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
16881 where we introduced bridge relays that don't need to publish to
16882 be useful. Fixes bug 2050.
16883 - Do even more to reject (and not just ignore) annotations on
16884 router descriptors received anywhere but from the cache. Previously
16885 we would ignore such annotations at first, but cache them to disk
16886 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
16887 - When you're using bridges and your network goes away and your
16888 bridges get marked as down, recover when you attempt a new socks
16889 connection (if the network is back), rather than waiting up to an
16890 hour to try fetching new descriptors for your bridges. Bugfix on
16891 0.2.0.3-alpha; fixes bug 1981.
16894 - Move to the November 2010 Maxmind GeoLite country db (rather
16895 than the June 2009 ip-to-country GeoIP db) for our statistics that
16896 count how many users relays are seeing from each country. Now we'll
16897 have more accurate data, especially for many African countries.
16899 o New directory authorities:
16900 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
16904 - Fix an assertion failure that could occur in directory caches or
16905 bridge users when using a very short voting interval on a testing
16906 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
16908 - Enforce multiplicity rules when parsing annotations. Bugfix on
16909 0.2.0.8-alpha. Found by piebeer.
16910 - Allow handshaking OR connections to take a full KeepalivePeriod
16911 seconds to handshake. Previously, we would close them after
16912 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
16913 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
16915 - When building with --enable-gcc-warnings on OpenBSD, disable
16916 warnings in system headers. This makes --enable-gcc-warnings
16917 pass on OpenBSD 4.8.
16920 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
16921 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
16922 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
16923 Servers can start sending this code when enough clients recognize
16924 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
16925 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
16926 Patch from mingw-san.
16929 - Remove the old debian/ directory from the main Tor distribution.
16930 The official Tor-for-debian git repository lives at the URL
16931 https://git.torproject.org/debian/tor.git
16932 - Stop shipping the old doc/website/ directory in the tarball. We
16933 changed the website format in late 2010, and what we shipped in
16934 0.2.1.26 really wasn't that useful anyway.
16937 Changes in version 0.2.1.26 - 2010-05-02
16938 Tor 0.2.1.26 addresses the recent connection and memory overload
16939 problems we've been seeing on relays, especially relays with their
16940 DirPort open. If your relay has been crashing, or you turned it off
16941 because it used too many resources, give this release a try.
16943 This release also fixes yet another instance of broken OpenSSL libraries
16944 that was causing some relays to drop out of the consensus.
16947 - Teach relays to defend themselves from connection overload. Relays
16948 now close idle circuits early if it looks like they were intended
16949 for directory fetches. Relays are also more aggressive about closing
16950 TLS connections that have no circuits on them. Such circuits are
16951 unlikely to be re-used, and tens of thousands of them were piling
16952 up at the fast relays, causing the relays to run out of sockets
16953 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
16954 their directory fetches over TLS).
16955 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
16956 that claim to be earlier than 0.9.8m, but which have in reality
16957 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
16958 behavior. Possible fix for some cases of bug 1346.
16959 - Directory mirrors were fetching relay descriptors only from v2
16960 directory authorities, rather than v3 authorities like they should.
16961 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
16962 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
16965 - Finally get rid of the deprecated and now harmful notion of "clique
16966 mode", where directory authorities maintain TLS connections to
16970 - In the util/threads test, no longer free the test_mutex before all
16971 worker threads have finished. Bugfix on 0.2.1.6-alpha.
16972 - The master thread could starve the worker threads quite badly on
16973 certain systems, causing them to run only partially in the allowed
16974 window. This resulted in test failures. Now the master thread sleeps
16975 occasionally for a few microseconds while the two worker-threads
16976 compete for the mutex. Bugfix on 0.2.0.1-alpha.
16979 Changes in version 0.2.1.25 - 2010-03-16
16980 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
16981 prevent relays from guessing their IP address correctly. It also fixes
16982 several minor potential security bugs.
16985 - Fix a regression from our patch for bug 1244 that caused relays
16986 to guess their IP address incorrectly if they didn't set Address
16987 in their torrc and/or their address fails to resolve. Bugfix on
16988 0.2.1.23; fixes bug 1269.
16989 - When freeing a session key, zero it out completely. We only zeroed
16990 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
16991 patched by ekir. Fixes bug 1254.
16994 - Fix a dereference-then-NULL-check sequence when publishing
16995 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
16997 - Fix another dereference-then-NULL-check sequence. Bugfix on
16998 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
16999 - Make sure we treat potentially not NUL-terminated strings correctly.
17000 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
17003 Changes in version 0.2.1.24 - 2010-02-21
17004 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
17008 - Work correctly out-of-the-box with even more vendor-patched versions
17009 of OpenSSL. In particular, make it so Debian and OS X don't need
17010 customized patches to run/build.
17013 Changes in version 0.2.1.23 - 2010-02-13
17014 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
17015 again on the latest OS X, and updates the location of a directory
17018 o Major bugfixes (performance):
17019 - We were selecting our guards uniformly at random, and then weighting
17020 which of our guards we'd use uniformly at random. This imbalance
17021 meant that Tor clients were severely limited on throughput (and
17022 probably latency too) by the first hop in their circuit. Now we
17023 select guards weighted by currently advertised bandwidth. We also
17024 automatically discard guards picked using the old algorithm. Fixes
17025 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
17028 - Make Tor work again on the latest OS X: when deciding whether to
17029 use strange flags to turn TLS renegotiation on, detect the OpenSSL
17030 version at run-time, not compile time. We need to do this because
17031 Apple doesn't update its dev-tools headers when it updates its
17032 libraries in a security patch.
17033 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
17034 that could happen on 32-bit platforms with 64-bit time_t. Also fix
17035 a memory leak when requesting a hidden service descriptor we've
17036 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
17040 - Refactor resolve_my_address() to not use gethostbyname() anymore.
17041 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
17044 - Avoid a mad rush at the beginning of each month when each client
17045 rotates half of its guards. Instead we spread the rotation out
17046 throughout the month, but we still avoid leaving a precise timestamp
17047 in the state file about when we first picked the guard. Improves
17048 over the behavior introduced in 0.1.2.17.
17051 Changes in version 0.2.1.22 - 2010-01-19
17052 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
17053 authorities -- it would tell you its whole history of bridge descriptors
17054 if you make the right directory request. This stable update also
17055 rotates two of the seven v3 directory authority keys and locations.
17057 o Directory authority changes:
17058 - Rotate keys (both v3 identity and relay identity) for moria1
17062 - Stop bridge directory authorities from answering dbg-stability.txt
17063 directory queries, which would let people fetch a list of all
17064 bridge identities they track. Bugfix on 0.2.1.6-alpha.
17067 Changes in version 0.2.1.21 - 2009-12-21
17068 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
17069 library. If you use Tor on Linux / Unix and you're getting SSL
17070 renegotiation errors, upgrading should help. We also recommend an
17071 upgrade if you're an exit relay.
17074 - Work around a security feature in OpenSSL 0.9.8l that prevents our
17075 handshake from working unless we explicitly tell OpenSSL that we
17076 are using SSL renegotiation safely. We are, of course, but OpenSSL
17077 0.9.8l won't work unless we say we are.
17078 - Avoid crashing if the client is trying to upload many bytes and the
17079 circuit gets torn down at the same time, or if the flip side
17080 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
17083 - Do not refuse to learn about authority certs and v2 networkstatus
17084 documents that are older than the latest consensus. This bug might
17085 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
17086 Spotted and fixed by xmux.
17087 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
17088 trigger platform-specific option misparsing case found by Coverity
17090 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
17091 trigger assert. Fixes bug 1173.
17094 Changes in version 0.2.1.20 - 2009-10-15
17095 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
17096 services at once, prepares for more performance improvements, and
17097 fixes a bunch of smaller bugs.
17099 The Windows and OS X bundles also include a more recent Vidalia,
17100 and switch from Privoxy to Polipo.
17102 The OS X installers are now drag and drop. It's best to un-install
17103 Tor/Vidalia and then install this new bundle, rather than upgrade. If
17104 you want to upgrade, you'll need to update the paths for Tor and Polipo
17105 in the Vidalia Settings window.
17108 - Send circuit or stream sendme cells when our window has decreased
17109 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
17110 by Karsten when testing the "reduce circuit window" performance
17111 patch. Bugfix on the 54th commit on Tor -- from July 2002,
17112 before the release of Tor 0.0.0. This is the new winner of the
17114 - Fix a remotely triggerable memory leak when a consensus document
17115 contains more than one signature from the same voter. Bugfix on
17117 - Avoid segfault in rare cases when finishing an introduction circuit
17118 as a client and finding out that we don't have an introduction key
17119 for it. Fixes bug 1073. Reported by Aaron Swartz.
17122 - Tor now reads the "circwindow" parameter out of the consensus,
17123 and uses that value for its circuit package window rather than the
17124 default of 1000 cells. Begins the implementation of proposal 168.
17126 o New directory authorities:
17127 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
17129 - Move moria1 and tonga to alternate IP addresses.
17132 - Fix a signed/unsigned compile warning in 0.2.1.19.
17133 - Fix possible segmentation fault on directory authorities. Bugfix on
17135 - Fix an extremely rare infinite recursion bug that could occur if
17136 we tried to log a message after shutting down the log subsystem.
17137 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
17138 - Fix an obscure bug where hidden services on 64-bit big-endian
17139 systems might mis-read the timestamp in v3 introduce cells, and
17140 refuse to connect back to the client. Discovered by "rotor".
17141 Bugfix on 0.2.1.6-alpha.
17142 - We were triggering a CLOCK_SKEW controller status event whenever
17143 we connect via the v2 connection protocol to any relay that has
17144 a wrong clock. Instead, we should only inform the controller when
17145 it's a trusted authority that claims our clock is wrong. Bugfix
17146 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
17147 - We were telling the controller about CHECKING_REACHABILITY and
17148 REACHABILITY_FAILED status events whenever we launch a testing
17149 circuit or notice that one has failed. Instead, only tell the
17150 controller when we want to inform the user of overall success or
17151 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
17153 - Don't warn when we're using a circuit that ends with a node
17154 excluded in ExcludeExitNodes, but the circuit is not used to access
17155 the outside world. This should help fix bug 1090. Bugfix on
17157 - Work around a small memory leak in some versions of OpenSSL that
17158 stopped the memory used by the hostname TLS extension from being
17162 - Add a "getinfo status/accepted-server-descriptor" controller
17163 command, which is the recommended way for controllers to learn
17164 whether our server descriptor has been successfully received by at
17165 least on directory authority. Un-recommend good-server-descriptor
17166 getinfo and status events until we have a better design for them.
17169 Changes in version 0.2.1.19 - 2009-07-28
17170 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
17174 - Make accessing hidden services on 0.2.1.x work right again.
17175 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
17176 part of patch provided by "optimist".
17179 - When a relay/bridge is writing out its identity key fingerprint to
17180 the "fingerprint" file and to its logs, write it without spaces. Now
17181 it will look like the fingerprints in our bridges documentation,
17182 and confuse fewer users.
17185 - Relays no longer publish a new server descriptor if they change
17186 their MaxAdvertisedBandwidth config option but it doesn't end up
17187 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
17188 fixes bug 1026. Patch from Sebastian.
17189 - Avoid leaking memory every time we get a create cell but we have
17190 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
17191 fixes bug 1034. Reported by BarkerJr.
17194 Changes in version 0.2.1.18 - 2009-07-24
17195 Tor 0.2.1.18 lays the foundations for performance improvements,
17196 adds status events to help users diagnose bootstrap problems, adds
17197 optional authentication/authorization for hidden services, fixes a
17198 variety of potential anonymity problems, and includes a huge pile of
17199 other features and bug fixes.
17201 o Major features (clients):
17202 - Start sending "bootstrap phase" status events to the controller,
17203 so it can keep the user informed of progress fetching directory
17204 information and establishing circuits. Also inform the controller
17205 if we think we're stuck at a particular bootstrap phase. Implements
17207 - Clients replace entry guards that were chosen more than a few months
17208 ago. This change should significantly improve client performance,
17209 especially once more people upgrade, since relays that have been
17210 a guard for a long time are currently overloaded.
17211 - Network status consensus documents and votes now contain bandwidth
17212 information for each relay. Clients use the bandwidth values
17213 in the consensus, rather than the bandwidth values in each
17214 relay descriptor. This approach opens the door to more accurate
17215 bandwidth estimates once the directory authorities start doing
17216 active measurements. Implements part of proposal 141.
17218 o Major features (relays):
17219 - Disable and refactor some debugging checks that forced a linear scan
17220 over the whole server-side DNS cache. These accounted for over 50%
17221 of CPU time on a relatively busy exit node's gprof profile. Also,
17222 disable some debugging checks that appeared in exit node profile
17223 data. Found by Jacob.
17224 - New DirPortFrontPage option that takes an html file and publishes
17225 it as "/" on the DirPort. Now relay operators can provide a
17226 disclaimer without needing to set up a separate webserver. There's
17227 a sample disclaimer in contrib/tor-exit-notice.html.
17229 o Major features (hidden services):
17230 - Make it possible to build hidden services that only certain clients
17231 are allowed to connect to. This is enforced at several points,
17232 so that unauthorized clients are unable to send INTRODUCE cells
17233 to the service, or even (depending on the type of authentication)
17234 to learn introduction points. This feature raises the bar for
17235 certain kinds of active attacks against hidden services. Design
17236 and code by Karsten Loesing. Implements proposal 121.
17237 - Relays now store and serve v2 hidden service descriptors by default,
17238 i.e., the new default value for HidServDirectoryV2 is 1. This is
17239 the last step in proposal 114, which aims to make hidden service
17240 lookups more reliable.
17242 o Major features (path selection):
17243 - ExitNodes and Exclude*Nodes config options now allow you to restrict
17244 by country code ("{US}") or IP address or address pattern
17245 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
17246 refinement to decide what config options should take priority if
17247 you ask to both use a particular node and exclude it.
17249 o Major features (misc):
17250 - When building a consensus, do not include routers that are down.
17251 This cuts down 30% to 40% on consensus size. Implements proposal
17253 - New TestingTorNetwork config option to allow adjustment of
17254 previously constant values that could slow bootstrapping. Implements
17255 proposal 135. Patch from Karsten.
17256 - Convert many internal address representations to optionally hold
17257 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
17258 elements. Make resolver code handle nameservers located at IPv6
17260 - More work on making our TLS handshake blend in: modify the list
17261 of ciphers advertised by OpenSSL in client mode to even more
17262 closely resemble a common web browser. We cheat a little so that
17263 we can advertise ciphers that the locally installed OpenSSL doesn't
17265 - Use the TLS1 hostname extension to more closely resemble browser
17268 o Security fixes (anonymity/entropy):
17269 - Never use a connection with a mismatched address to extend a
17270 circuit, unless that connection is canonical. A canonical
17271 connection is one whose address is authenticated by the router's
17272 identity key, either in a NETINFO cell or in a router descriptor.
17273 - Implement most of proposal 110: The first K cells to be sent
17274 along a circuit are marked as special "early" cells; only K "early"
17275 cells will be allowed. Once this code is universal, we can block
17276 certain kinds of denial-of-service attack by requiring that EXTEND
17277 commands must be sent using an "early" cell.
17278 - Resume using OpenSSL's RAND_poll() for better (and more portable)
17279 cross-platform entropy collection again. We used to use it, then
17280 stopped using it because of a bug that could crash systems that
17281 called RAND_poll when they had a lot of fds open. It looks like the
17282 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
17283 at startup, and to call RAND_poll() when we reseed later only if
17284 we have a non-buggy OpenSSL version.
17285 - When the client is choosing entry guards, now it selects at most
17286 one guard from a given relay family. Otherwise we could end up with
17287 all of our entry points into the network run by the same operator.
17288 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
17289 - Do not use or believe expired v3 authority certificates. Patch
17290 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
17291 - Drop begin cells to a hidden service if they come from the middle
17292 of a circuit. Patch from lark.
17293 - When we erroneously receive two EXTEND cells for the same circuit
17294 ID on the same connection, drop the second. Patch from lark.
17295 - Authorities now vote for the Stable flag for any router whose
17296 weighted MTBF is at least 5 days, regardless of the mean MTBF.
17297 - Clients now never report any stream end reason except 'MISC'.
17298 Implements proposal 148.
17300 o Major bugfixes (crashes):
17301 - Parse dates and IPv4 addresses in a locale- and libc-independent
17302 manner, to avoid platform-dependent behavior on malformed input.
17303 - Fix a crash that occurs on exit nodes when a nameserver request
17304 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
17305 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
17307 - Do not assume that a stack-allocated character array will be
17308 64-bit aligned on platforms that demand that uint64_t access is
17309 aligned. Possible fix for bug 604.
17310 - Resolve a very rare crash bug that could occur when the user forced
17311 a nameserver reconfiguration during the middle of a nameserver
17312 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
17313 - Avoid a "0 divided by 0" calculation when calculating router uptime
17314 at directory authorities. Bugfix on 0.2.0.8-alpha.
17315 - Fix an assertion bug in parsing policy-related options; possible fix
17317 - Rate-limit too-many-sockets messages: when they happen, they happen
17318 a lot and end up filling up the disk. Resolves bug 748.
17319 - Fix a race condition that could cause crashes or memory corruption
17320 when running as a server with a controller listening for log
17322 - Avoid crashing when we have a policy specified in a DirPolicy or
17323 SocksPolicy or ReachableAddresses option with ports set on it,
17324 and we re-load the policy. May fix bug 996.
17325 - Fix an assertion failure on 64-bit platforms when we allocated
17326 memory right up to the end of a memarea, then realigned the memory
17327 one step beyond the end. Fixes a possible cause of bug 930.
17328 - Protect the count of open sockets with a mutex, so we can't
17329 corrupt it when two threads are closing or opening sockets at once.
17330 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
17332 o Major bugfixes (clients):
17333 - Discard router descriptors as we load them if they are more than
17334 five days old. Otherwise if Tor is off for a long time and then
17335 starts with cached descriptors, it will try to use the onion keys
17336 in those obsolete descriptors when building circuits. Fixes bug 887.
17337 - When we choose to abandon a new entry guard because we think our
17338 older ones might be better, close any circuits pending on that
17339 new entry guard connection. This fix should make us recover much
17340 faster when our network is down and then comes back. Bugfix on
17341 0.1.2.8-beta; found by lodger.
17342 - When Tor clients restart after 1-5 days, they discard all their
17343 cached descriptors as too old, but they still use the cached
17344 consensus document. This approach is good for robustness, but
17345 bad for performance: since they don't know any bandwidths, they
17346 end up choosing at random rather than weighting their choice by
17347 speed. Fixed by the above feature of putting bandwidths in the
17350 o Major bugfixes (relays):
17351 - Relays were falling out of the networkstatus consensus for
17352 part of a day if they changed their local config but the
17353 authorities discarded their new descriptor as "not sufficiently
17354 different". Now directory authorities accept a descriptor as changed
17355 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
17356 patch by Sebastian.
17357 - Ensure that two circuits can never exist on the same connection
17358 with the same circuit ID, even if one is marked for close. This
17359 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
17360 - Directory authorities were neglecting to mark relays down in their
17361 internal histories if the relays fall off the routerlist without
17362 ever being found unreachable. So there were relays in the histories
17363 that haven't been seen for eight months, and are listed as being
17364 up for eight months. This wreaked havoc on the "median wfu" and
17365 "median mtbf" calculations, in turn making Guard and Stable flags
17366 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
17369 o Major bugfixes (hidden services):
17370 - When establishing a hidden service, introduction points that
17371 originate from cannibalized circuits were completely ignored
17372 and not included in rendezvous service descriptors. This might
17373 have been another reason for delay in making a hidden service
17374 available. Bugfix from long ago (0.0.9.x?)
17376 o Major bugfixes (memory and resource management):
17377 - Fixed some memory leaks -- some quite frequent, some almost
17378 impossible to trigger -- based on results from Coverity.
17379 - Speed up parsing and cut down on memory fragmentation by using
17380 stack-style allocations for parsing directory objects. Previously,
17381 this accounted for over 40% of allocations from within Tor's code
17382 on a typical directory cache.
17383 - Use a Bloom filter rather than a digest-based set to track which
17384 descriptors we need to keep around when we're cleaning out old
17385 router descriptors. This speeds up the computation significantly,
17386 and may reduce fragmentation.
17388 o New/changed config options:
17389 - Now NodeFamily and MyFamily config options allow spaces in
17390 identity fingerprints, so it's easier to paste them in.
17391 Suggested by Lucky Green.
17392 - Allow ports 465 and 587 in the default exit policy again. We had
17393 rejected them in 0.1.0.15, because back in 2005 they were commonly
17394 misconfigured and ended up as spam targets. We hear they are better
17395 locked down these days.
17396 - Make TrackHostExit mappings expire a while after their last use, not
17397 after their creation. Patch from Robert Hogan.
17398 - Add an ExcludeExitNodes option so users can list a set of nodes
17399 that should be be excluded from the exit node position, but
17400 allowed elsewhere. Implements proposal 151.
17401 - New --hush command-line option similar to --quiet. While --quiet
17402 disables all logging to the console on startup, --hush limits the
17403 output to messages of warning and error severity.
17404 - New configure/torrc options (--enable-geoip-stats,
17405 DirRecordUsageByCountry) to record how many IPs we've served
17406 directory info to in each country code, how many status documents
17407 total we've sent to each country code, and what share of the total
17408 directory requests we should expect to see.
17409 - Make outbound DNS packets respect the OutboundBindAddress setting.
17410 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
17411 - Allow separate log levels to be configured for different logging
17412 domains. For example, this allows one to log all notices, warnings,
17413 or errors, plus all memory management messages of level debug or
17414 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
17415 - Update to the "June 3 2009" ip-to-country file.
17417 o Minor features (relays):
17418 - Raise the minimum rate limiting to be a relay from 20000 bytes
17419 to 20480 bytes (aka 20KB/s), to match our documentation. Also
17420 update directory authorities so they always assign the Fast flag
17421 to relays with 20KB/s of capacity. Now people running relays won't
17422 suddenly find themselves not seeing any use, if the network gets
17424 - If we're a relay and we change our IP address, be more verbose
17425 about the reason that made us change. Should help track down
17426 further bugs for relays on dynamic IP addresses.
17427 - Exit servers can now answer resolve requests for ip6.arpa addresses.
17428 - Implement most of Proposal 152: allow specialized servers to permit
17429 single-hop circuits, and clients to use those servers to build
17430 single-hop circuits when using a specialized controller. Patch
17431 from Josh Albrecht. Resolves feature request 768.
17432 - When relays do their initial bandwidth measurement, don't limit
17433 to just our entry guards for the test circuits. Otherwise we tend
17434 to have multiple test circuits going through a single entry guard,
17435 which makes our bandwidth test less accurate. Fixes part of bug 654;
17436 patch contributed by Josh Albrecht.
17438 o Minor features (directory authorities):
17439 - Try not to open more than one descriptor-downloading connection
17440 to an authority at once. This should reduce load on directory
17441 authorities. Fixes bug 366.
17442 - Add cross-certification to newly generated certificates, so that
17443 a signing key is enough information to look up a certificate. Start
17444 serving certificates by <identity digest, signing key digest>
17445 pairs. Implements proposal 157.
17446 - When a directory authority downloads a descriptor that it then
17447 immediately rejects, do not retry downloading it right away. Should
17448 save some bandwidth on authorities. Fix for bug 888. Patch by
17450 - Directory authorities now serve a /tor/dbg-stability.txt URL to
17451 help debug WFU and MTBF calculations.
17452 - In directory authorities' approved-routers files, allow
17453 fingerprints with or without space.
17455 o Minor features (directory mirrors):
17456 - When a download gets us zero good descriptors, do not notify
17457 Tor that new directory information has arrived.
17458 - Servers support a new URL scheme for consensus downloads that
17459 allows the client to specify which authorities are trusted.
17460 The server then only sends the consensus if the client will trust
17461 it. Otherwise a 404 error is sent back. Clients use this
17462 new scheme when the server supports it (meaning it's running
17463 0.2.1.1-alpha or later). Implements proposal 134.
17465 o Minor features (bridges):
17466 - If the bridge config line doesn't specify a port, assume 443.
17467 This makes bridge lines a bit smaller and easier for users to
17469 - If we're using bridges and our network goes away, be more willing
17470 to forgive our bridges and try again when we get an application
17473 o Minor features (hidden services):
17474 - When the client launches an introduction circuit, retry with a
17475 new circuit after 30 seconds rather than 60 seconds.
17476 - Launch a second client-side introduction circuit in parallel
17477 after a delay of 15 seconds (based on work by Christian Wilms).
17478 - Hidden services start out building five intro circuits rather
17479 than three, and when the first three finish they publish a service
17480 descriptor using those. Now we publish our service descriptor much
17481 faster after restart.
17482 - Drop the requirement to have an open dir port for storing and
17483 serving v2 hidden service descriptors.
17485 o Minor features (build and packaging):
17486 - On Linux, use the prctl call to re-enable core dumps when the User
17488 - Try to make sure that the version of Libevent we're running with
17489 is binary-compatible with the one we built with. May address bug
17491 - Add a new --enable-local-appdata configuration switch to change
17492 the default location of the datadir on win32 from APPDATA to
17493 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
17494 entirely. Patch from coderman.
17495 - Build correctly against versions of OpenSSL 0.9.8 or later that
17496 are built without support for deprecated functions.
17497 - On platforms with a maximum syslog string length, truncate syslog
17498 messages to that length ourselves, rather than relying on the
17499 system to do it for us.
17500 - Automatically detect MacOSX versions earlier than 10.4.0, and
17501 disable kqueue from inside Tor when running with these versions.
17502 We previously did this from the startup script, but that was no
17503 help to people who didn't use the startup script. Resolves bug 863.
17504 - Build correctly when configured to build outside the main source
17505 path. Patch from Michael Gold.
17506 - Disable GCC's strict alias optimization by default, to avoid the
17507 likelihood of its introducing subtle bugs whenever our code violates
17508 the letter of C99's alias rules.
17509 - Change the contrib/tor.logrotate script so it makes the new
17510 logs as "_tor:_tor" rather than the default, which is generally
17511 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
17512 - Change our header file guard macros to be less likely to conflict
17513 with system headers. Adam Langley noticed that we were conflicting
17514 with log.h on Android.
17515 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
17516 and stop using a warning that had become unfixably verbose under
17518 - Use a lockfile to make sure that two Tor processes are not
17519 simultaneously running with the same datadir.
17520 - Allow OpenSSL to use dynamic locks if it wants.
17521 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
17523 o Minor features (controllers):
17524 - When generating circuit events with verbose nicknames for
17525 controllers, try harder to look up nicknames for routers on a
17526 circuit. (Previously, we would look in the router descriptors we had
17527 for nicknames, but not in the consensus.) Partial fix for bug 941.
17528 - New controller event NEWCONSENSUS that lists the networkstatus
17529 lines for every recommended relay. Now controllers like Torflow
17530 can keep up-to-date on which relays they should be using.
17531 - New controller event "clients_seen" to report a geoip-based summary
17532 of which countries we've seen clients from recently. Now controllers
17533 like Vidalia can show bridge operators that they're actually making
17535 - Add a 'getinfo status/clients-seen' controller command, in case
17536 controllers want to hear clients_seen events but connect late.
17537 - New CONSENSUS_ARRIVED event to note when a new consensus has
17538 been fetched and validated.
17539 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
17540 controllers to prevent SIGHUP from reloading the configuration.
17542 - Return circuit purposes in response to GETINFO circuit-status.
17544 - Serve the latest v3 networkstatus consensus via the control
17545 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
17546 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
17547 controller can query our current bootstrap state in case it attaches
17548 partway through and wants to catch up.
17549 - Provide circuit purposes along with circuit events to the controller.
17551 o Minor features (tools):
17552 - Do not have tor-resolve automatically refuse all .onion addresses;
17553 if AutomapHostsOnResolve is set in your torrc, this will work fine.
17554 - Add a -p option to tor-resolve for specifying the SOCKS port: some
17555 people find host:port too confusing.
17556 - Print the SOCKS5 error message string as well as the error code
17557 when a tor-resolve request fails. Patch from Jacob.
17559 o Minor bugfixes (memory and resource management):
17560 - Clients no longer cache certificates for authorities they do not
17561 recognize. Bugfix on 0.2.0.9-alpha.
17562 - Do not use C's stdio library for writing to log files. This will
17563 improve logging performance by a minute amount, and will stop
17564 leaking fds when our disk is full. Fixes bug 861.
17565 - Stop erroneous use of O_APPEND in cases where we did not in fact
17566 want to re-seek to the end of a file before every last write().
17567 - Fix a small alignment and memory-wasting bug on buffer chunks.
17569 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
17570 to avoid unused RAM in buffer chunks and memory pools.
17571 - Reduce the default smartlist size from 32 to 16; it turns out that
17572 most smartlists hold around 8-12 elements tops.
17573 - Make dumpstats() log the fullness and size of openssl-internal
17575 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
17576 patch to their OpenSSL, turn it on to save memory on servers. This
17577 patch will (with any luck) get included in a mainline distribution
17579 - Fix a memory leak when v3 directory authorities load their keys
17580 and cert from disk. Bugfix on 0.2.0.1-alpha.
17581 - Stop using malloc_usable_size() to use more area than we had
17582 actually allocated: it was safe, but made valgrind really unhappy.
17583 - Make the assert_circuit_ok() function work correctly on circuits that
17584 have already been marked for close.
17585 - Fix uninitialized size field for memory area allocation: may improve
17586 memory performance during directory parsing.
17588 o Minor bugfixes (clients):
17589 - Stop reloading the router list from disk for no reason when we
17590 run out of reachable directory mirrors. Once upon a time reloading
17591 it would set the 'is_running' flag back to 1 for them. It hasn't
17592 done that for a long time.
17593 - When we had picked an exit node for a connection, but marked it as
17594 "optional", and it turned out we had no onion key for the exit,
17595 stop wanting that exit and try again. This situation may not
17596 be possible now, but will probably become feasible with proposal
17597 158. Spotted by rovv. Fixes another case of bug 752.
17598 - Fix a bug in address parsing that was preventing bridges or hidden
17599 service targets from being at IPv6 addresses.
17600 - Do not remove routers as too old if we do not have any consensus
17601 document. Bugfix on 0.2.0.7-alpha.
17602 - When an exit relay resolves a stream address to a local IP address,
17603 do not just keep retrying that same exit relay over and
17604 over. Instead, just close the stream. Addresses bug 872. Bugfix
17605 on 0.2.0.32. Patch from rovv.
17606 - Made Tor a little less aggressive about deleting expired
17607 certificates. Partial fix for bug 854.
17608 - Treat duplicate certificate fetches as failures, so that we do
17609 not try to re-fetch an expired certificate over and over and over.
17610 - Do not say we're fetching a certificate when we'll in fact skip it
17611 because of a pending download.
17612 - If we have correct permissions on $datadir, we complain to stdout
17613 and fail to start. But dangerous permissions on
17614 $datadir/cached-status/ would cause us to open a log and complain
17615 there. Now complain to stdout and fail to start in both cases. Fixes
17616 bug 820, reported by seeess.
17618 o Minor bugfixes (bridges):
17619 - When we made bridge authorities stop serving bridge descriptors over
17620 unencrypted links, we also broke DirPort reachability testing for
17621 bridges. So bridges with a non-zero DirPort were printing spurious
17622 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
17623 - Don't allow a bridge to publish its router descriptor to a
17624 non-bridge directory authority. Fixes part of bug 932.
17625 - When we change to or from being a bridge, reset our counts of
17626 client usage by country. Fixes bug 932.
17628 o Minor bugfixes (relays):
17629 - Log correct error messages for DNS-related network errors on
17631 - Actually return -1 in the error case for read_bandwidth_usage().
17632 Harmless bug, since we currently don't care about the return value
17633 anywhere. Bugfix on 0.2.0.9-alpha.
17634 - Provide a more useful log message if bug 977 (related to buffer
17635 freelists) ever reappears, and do not crash right away.
17636 - We were already rejecting relay begin cells with destination port
17637 of 0. Now also reject extend cells with destination port or address
17638 of 0. Suggested by lark.
17639 - When we can't transmit a DNS request due to a network error, retry
17640 it after a while, and eventually transmit a failing response to
17641 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
17642 - Solve a bug that kept hardware crypto acceleration from getting
17643 enabled when accounting was turned on. Fixes bug 907. Bugfix on
17645 - When a canonical connection appears later in our internal list
17646 than a noncanonical one for a given OR ID, always use the
17647 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
17649 - Avoid some nasty corner cases in the logic for marking connections
17650 as too old or obsolete or noncanonical for circuits. Partial
17652 - Fix another interesting corner-case of bug 891 spotted by rovv:
17653 Previously, if two hosts had different amounts of clock drift, and
17654 one of them created a new connection with just the wrong timing,
17655 the other might decide to deprecate the new connection erroneously.
17656 Bugfix on 0.1.1.13-alpha.
17657 - If one win32 nameserver fails to get added, continue adding the
17658 rest, and don't automatically fail.
17659 - Fix a bug where an unreachable relay would establish enough
17660 reachability testing circuits to do a bandwidth test -- if
17661 we already have a connection to the middle hop of the testing
17662 circuit, then it could establish the last hop by using the existing
17663 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
17664 circuits no longer use entry guards in 0.2.1.3-alpha.
17666 o Minor bugfixes (directory authorities):
17667 - Limit uploaded directory documents to be 16M rather than 500K.
17668 The directory authorities were refusing v3 consensus votes from
17669 other authorities, since the votes are now 504K. Fixes bug 959;
17670 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
17671 - Directory authorities should never send a 503 "busy" response to
17672 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
17674 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
17675 headers. Bugfix on 0.2.0.10-alpha.
17677 o Minor bugfixes (hidden services):
17678 - When we can't find an intro key for a v2 hidden service descriptor,
17679 fall back to the v0 hidden service descriptor and log a bug message.
17680 Workaround for bug 1024.
17681 - In very rare situations new hidden service descriptors were
17682 published earlier than 30 seconds after the last change to the
17683 service. (We currently think that a hidden service descriptor
17684 that's been stable for 30 seconds is worth publishing.)
17685 - If a hidden service sends us an END cell, do not consider
17686 retrying the connection; just close it. Patch from rovv.
17687 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
17688 service directories if they have no advertised dir port. Bugfix
17691 o Minor bugfixes (tools):
17692 - In the torify(1) manpage, mention that tsocks will leak your
17695 o Minor bugfixes (controllers):
17696 - If the controller claimed responsibility for a stream, but that
17697 stream never finished making its connection, it would live
17698 forever in circuit_wait state. Now we close it after SocksTimeout
17699 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
17700 - Make DNS resolved controller events into "CLOSED", not
17701 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
17703 - The control port would close the connection before flushing long
17704 replies, such as the network consensus, if a QUIT command was issued
17705 before the reply had completed. Now, the control port flushes all
17706 pending replies before closing the connection. Also fix a spurious
17707 warning when a QUIT command is issued after a malformed or rejected
17708 AUTHENTICATE command, but before the connection was closed. Patch
17709 by Marcus Griep. Fixes bugs 1015 and 1016.
17710 - Fix a bug that made stream bandwidth get misreported to the
17713 o Deprecated and removed features:
17714 - The old "tor --version --version" command, which would print out
17715 the subversion "Id" of most of the source files, is now removed. It
17716 turned out to be less useful than we'd expected, and harder to
17718 - RedirectExits has been removed. It was deprecated since
17720 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
17721 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
17722 - Cell pools are now always enabled; --disable-cell-pools is ignored.
17723 - Directory mirrors no longer fetch the v1 directory or
17724 running-routers files. They are obsolete, and nobody asks for them
17725 anymore. This is the first step to making v1 authorities obsolete.
17726 - Take out the TestVia config option, since it was a workaround for
17727 a bug that was fixed in Tor 0.1.1.21.
17728 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
17729 HiddenServiceExcludeNodes as obsolete: they never worked properly,
17730 and nobody seems to be using them. Fixes bug 754. Bugfix on
17731 0.1.0.1-rc. Patch from Christian Wilms.
17732 - Remove all backward-compatibility code for relays running
17733 versions of Tor so old that they no longer work at all on the
17736 o Code simplifications and refactoring:
17737 - Tool-assisted documentation cleanup. Nearly every function or
17738 static variable in Tor should have its own documentation now.
17739 - Rename the confusing or_is_obsolete field to the more appropriate
17740 is_bad_for_new_circs, and move it to or_connection_t where it
17742 - Move edge-only flags from connection_t to edge_connection_t: not
17743 only is this better coding, but on machines of plausible alignment,
17744 it should save 4-8 bytes per connection_t. "Every little bit helps."
17745 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
17746 for consistency; keep old option working for backward compatibility.
17747 - Simplify the code for finding connections to use for a circuit.
17748 - Revise the connection_new functions so that a more typesafe variant
17749 exists. This will work better with Coverity, and let us find any
17750 actual mistakes we're making here.
17751 - Refactor unit testing logic so that dmalloc can be used sensibly
17752 with unit tests to check for memory leaks.
17753 - Move all hidden-service related fields from connection and circuit
17754 structure to substructures: this way they won't eat so much memory.
17755 - Squeeze 2-5% out of client performance (according to oprofile) by
17756 improving the implementation of some policy-manipulation functions.
17757 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
17758 be more efficient. Formerly it was quadratic in the number of
17759 servers; now it should be linear. Fixes bug 509.
17760 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
17761 and n_conn_id_digest fields into a separate structure that's
17762 only needed when the circuit has not yet attached to an n_conn.
17763 - Optimize out calls to time(NULL) that occur for every IO operation,
17764 or for every cell. On systems like Windows where time() is a
17765 slow syscall, this fix will be slightly helpful.
17768 Changes in version 0.2.0.35 - 2009-06-24
17770 - Avoid crashing in the presence of certain malformed descriptors.
17771 Found by lark, and by automated fuzzing.
17772 - Fix an edge case where a malicious exit relay could convince a
17773 controller that the client's DNS question resolves to an internal IP
17774 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
17777 - Finally fix the bug where dynamic-IP relays disappear when their
17778 IP address changes: directory mirrors were mistakenly telling
17779 them their old address if they asked via begin_dir, so they
17780 never got an accurate answer about their new address, so they
17781 just vanished after a day. For belt-and-suspenders, relays that
17782 don't set Address in their config now avoid using begin_dir for
17783 all direct connections. Should fix bugs 827, 883, and 900.
17784 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
17785 that would occur on some exit nodes when DNS failures and timeouts
17786 occurred in certain patterns. Fix for bug 957.
17789 - When starting with a cache over a few days old, do not leak
17790 memory for the obsolete router descriptors in it. Bugfix on
17791 0.2.0.33; fixes bug 672.
17792 - Hidden service clients didn't use a cached service descriptor that
17793 was older than 15 minutes, but wouldn't fetch a new one either,
17794 because there was already one in the cache. Now, fetch a v2
17795 descriptor unless the same descriptor was added to the cache within
17796 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
17799 Changes in version 0.2.0.34 - 2009-02-08
17800 Tor 0.2.0.34 features several more security-related fixes. You should
17801 upgrade, especially if you run an exit relay (remote crash) or a
17802 directory authority (remote infinite loop), or you're on an older
17803 (pre-XP) or not-recently-patched Windows (remote exploit).
17805 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
17806 have many known flaws, and nobody should be using them. You should
17807 upgrade. If you're using a Linux or BSD and its packages are obsolete,
17808 stop using those packages and upgrade anyway.
17811 - Fix an infinite-loop bug on handling corrupt votes under certain
17812 circumstances. Bugfix on 0.2.0.8-alpha.
17813 - Fix a temporary DoS vulnerability that could be performed by
17814 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
17815 - Avoid a potential crash on exit nodes when processing malformed
17816 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
17817 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
17818 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
17821 - Fix compilation on systems where time_t is a 64-bit integer.
17822 Patch from Matthias Drochner.
17823 - Don't consider expiring already-closed client connections. Fixes
17824 bug 893. Bugfix on 0.0.2pre20.
17827 Changes in version 0.2.0.33 - 2009-01-21
17828 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
17829 useful to users. It also finally fixes a bug where a relay or client
17830 that's been off for many days would take a long time to bootstrap.
17832 This update also fixes an important security-related bug reported by
17833 Ilja van Sprundel. You should upgrade. (We'll send out more details
17834 about the bug once people have had some time to upgrade.)
17837 - Fix a heap-corruption bug that may be remotely triggerable on
17838 some platforms. Reported by Ilja van Sprundel.
17841 - When a stream at an exit relay is in state "resolving" or
17842 "connecting" and it receives an "end" relay cell, the exit relay
17843 would silently ignore the end cell and not close the stream. If
17844 the client never closes the circuit, then the exit relay never
17845 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
17846 reported by "wood".
17847 - When sending CREATED cells back for a given circuit, use a 64-bit
17848 connection ID to find the right connection, rather than an addr:port
17849 combination. Now that we can have multiple OR connections between
17850 the same ORs, it is no longer possible to use addr:port to uniquely
17851 identify a connection.
17852 - Bridge relays that had DirPort set to 0 would stop fetching
17853 descriptors shortly after startup, and then briefly resume
17854 after a new bandwidth test and/or after publishing a new bridge
17855 descriptor. Bridge users that try to bootstrap from them would
17856 get a recent networkstatus but would get descriptors from up to
17857 18 hours earlier, meaning most of the descriptors were obsolete
17858 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
17859 - Prevent bridge relays from serving their 'extrainfo' document
17860 to anybody who asks, now that extrainfo docs include potentially
17861 sensitive aggregated client geoip summaries. Bugfix on
17863 - If the cached networkstatus consensus is more than five days old,
17864 discard it rather than trying to use it. In theory it could be
17865 useful because it lists alternate directory mirrors, but in practice
17866 it just means we spend many minutes trying directory mirrors that
17867 are long gone from the network. Also discard router descriptors as
17868 we load them if they are more than five days old, since the onion
17869 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
17872 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
17873 could make gcc generate non-functional binary search code. Bugfix
17875 - Build correctly on platforms without socklen_t.
17876 - Compile without warnings on solaris.
17877 - Avoid potential crash on internal error during signature collection.
17878 Fixes bug 864. Patch from rovv.
17879 - Correct handling of possible malformed authority signing key
17880 certificates with internal signature types. Fixes bug 880.
17881 Bugfix on 0.2.0.3-alpha.
17882 - Fix a hard-to-trigger resource leak when logging credential status.
17884 - When we can't initialize DNS because the network is down, do not
17885 automatically stop Tor from starting. Instead, we retry failed
17886 dns_init() every 10 minutes, and change the exit policy to reject
17887 *:* until one succeeds. Fixes bug 691.
17888 - Use 64 bits instead of 32 bits for connection identifiers used with
17889 the controller protocol, to greatly reduce risk of identifier reuse.
17890 - When we're choosing an exit node for a circuit, and we have
17891 no pending streams, choose a good general exit rather than one that
17892 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
17893 - Fix another case of assuming, when a specific exit is requested,
17894 that we know more than the user about what hosts it allows.
17895 Fixes one case of bug 752. Patch from rovv.
17896 - Clip the MaxCircuitDirtiness config option to a minimum of 10
17897 seconds. Warn the user if lower values are given in the
17898 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
17899 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
17900 user if lower values are given in the configuration. Bugfix on
17901 0.1.1.17-rc. Patch by Sebastian.
17902 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
17903 the cache because we already had a v0 descriptor with the same ID.
17904 Bugfix on 0.2.0.18-alpha.
17905 - Fix a race condition when freeing keys shared between main thread
17906 and CPU workers that could result in a memory leak. Bugfix on
17907 0.1.0.1-rc. Fixes bug 889.
17908 - Send a valid END cell back when a client tries to connect to a
17909 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
17910 840. Patch from rovv.
17911 - Check which hops rendezvous stream cells are associated with to
17912 prevent possible guess-the-streamid injection attacks from
17913 intermediate hops. Fixes another case of bug 446. Based on patch
17915 - If a broken client asks a non-exit router to connect somewhere,
17916 do not even do the DNS lookup before rejecting the connection.
17917 Fixes another case of bug 619. Patch from rovv.
17918 - When a relay gets a create cell it can't decrypt (e.g. because it's
17919 using the wrong onion key), we were dropping it and letting the
17920 client time out. Now actually answer with a destroy cell. Fixes
17921 bug 904. Bugfix on 0.0.2pre8.
17923 o Minor bugfixes (hidden services):
17924 - Do not throw away existing introduction points on SIGHUP. Bugfix on
17925 0.0.6pre1. Patch by Karsten. Fixes bug 874.
17928 - Report the case where all signatures in a detached set are rejected
17929 differently than the case where there is an error handling the
17931 - When we realize that another process has modified our cached
17932 descriptors, print out a more useful error message rather than
17933 triggering an assertion. Fixes bug 885. Patch from Karsten.
17934 - Implement the 0x20 hack to better resist DNS poisoning: set the
17935 case on outgoing DNS requests randomly, and reject responses that do
17936 not match the case correctly. This logic can be disabled with the
17937 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
17938 of servers that do not reliably preserve case in replies. See
17939 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
17941 - Check DNS replies for more matching fields to better resist DNS
17943 - Never use OpenSSL compression: it wastes RAM and CPU trying to
17944 compress cells, which are basically all encrypted, compressed, or
17948 Changes in version 0.2.0.32 - 2008-11-20
17949 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
17950 packages (and maybe other packages) noticed by Theo de Raadt, fixes
17951 a smaller security flaw that might allow an attacker to access local
17952 services, further improves hidden service performance, and fixes a
17953 variety of other issues.
17956 - The "User" and "Group" config options did not clear the
17957 supplementary group entries for the Tor process. The "User" option
17958 is now more robust, and we now set the groups to the specified
17959 user's primary group. The "Group" option is now ignored. For more
17960 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
17961 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
17962 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
17963 - The "ClientDNSRejectInternalAddresses" config option wasn't being
17964 consistently obeyed: if an exit relay refuses a stream because its
17965 exit policy doesn't allow it, we would remember what IP address
17966 the relay said the destination address resolves to, even if it's
17967 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
17970 - Fix a DOS opportunity during the voting signature collection process
17971 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
17973 o Major bugfixes (hidden services):
17974 - When fetching v0 and v2 rendezvous service descriptors in parallel,
17975 we were failing the whole hidden service request when the v0
17976 descriptor fetch fails, even if the v2 fetch is still pending and
17977 might succeed. Similarly, if the last v2 fetch fails, we were
17978 failing the whole hidden service request even if a v0 fetch is
17979 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
17980 - When extending a circuit to a hidden service directory to upload a
17981 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
17982 requests failed, because the router descriptor has not been
17983 downloaded yet. In these cases, do not attempt to upload the
17984 rendezvous descriptor, but wait until the router descriptor is
17985 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
17986 descriptor from a hidden service directory for which the router
17987 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
17991 - Fix several infrequent memory leaks spotted by Coverity.
17992 - When testing for libevent functions, set the LDFLAGS variable
17993 correctly. Found by Riastradh.
17994 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
17995 bootstrapping with tunneled directory connections. Bugfix on
17996 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
17997 - When asked to connect to A.B.exit:80, if we don't know the IP for A
17998 and we know that server B rejects most-but-not all connections to
17999 port 80, we would previously reject the connection. Now, we assume
18000 the user knows what they were asking for. Fixes bug 752. Bugfix
18001 on 0.0.9rc5. Diagnosed by BarkerJr.
18002 - If we overrun our per-second write limits a little, count this as
18003 having used up our write allocation for the second, and choke
18004 outgoing directory writes. Previously, we had only counted this when
18005 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
18006 Bugfix on 0.2.0.x (??).
18007 - Remove the old v2 directory authority 'lefkada' from the default
18008 list. It has been gone for many months.
18009 - Stop doing unaligned memory access that generated bus errors on
18010 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
18011 - Make USR2 log-level switch take effect immediately. Bugfix on
18014 o Minor bugfixes (controller):
18015 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
18016 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
18019 Changes in version 0.2.0.31 - 2008-09-03
18020 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
18021 a big bug we're seeing where in rare cases traffic from one Tor stream
18022 gets mixed into another stream, and fixes a variety of smaller issues.
18025 - Make sure that two circuits can never exist on the same connection
18026 with the same circuit ID, even if one is marked for close. This
18027 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
18028 - Relays now reject risky extend cells: if the extend cell includes
18029 a digest of all zeroes, or asks to extend back to the relay that
18030 sent the extend cell, tear down the circuit. Ideas suggested
18032 - If not enough of our entry guards are available so we add a new
18033 one, we might use the new one even if it overlapped with the
18034 current circuit's exit relay (or its family). Anonymity bugfix
18035 pointed out by rovv.
18038 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
18039 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
18040 - Correctly detect the presence of the linux/netfilter_ipv4.h header
18041 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
18042 - Pick size of default geoip filename string correctly on windows.
18043 Fixes bug 806. Bugfix on 0.2.0.30.
18044 - Make the autoconf script accept the obsolete --with-ssl-dir
18045 option as an alias for the actually-working --with-openssl-dir
18046 option. Fix the help documentation to recommend --with-openssl-dir.
18047 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
18048 - When using the TransPort option on OpenBSD, and using the User
18049 option to change UID and drop privileges, make sure to open
18050 /dev/pf before dropping privileges. Fixes bug 782. Patch from
18051 Christopher Davis. Bugfix on 0.1.2.1-alpha.
18052 - Try to attach connections immediately upon receiving a RENDEZVOUS2
18053 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
18054 on the client side when connecting to a hidden service. Bugfix
18055 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
18056 - When closing an application-side connection because its circuit is
18057 getting torn down, generate the stream event correctly. Bugfix on
18058 0.1.2.x. Anonymous patch.
18061 Changes in version 0.2.0.30 - 2008-07-15
18062 This new stable release switches to a more efficient directory
18063 distribution design, adds features to make connections to the Tor
18064 network harder to block, allows Tor to act as a DNS proxy, adds separate
18065 rate limiting for relayed traffic to make it easier for clients to
18066 become relays, fixes a variety of potential anonymity problems, and
18067 includes the usual huge pile of other features and bug fixes.
18069 o New v3 directory design:
18070 - Tor now uses a new way to learn about and distribute information
18071 about the network: the directory authorities vote on a common
18072 network status document rather than each publishing their own
18073 opinion. Now clients and caches download only one networkstatus
18074 document to bootstrap, rather than downloading one for each
18075 authority. Clients only download router descriptors listed in
18076 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
18078 - Set up moria1, tor26, and dizum as v3 directory authorities
18079 in addition to being v2 authorities. Also add three new ones:
18080 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
18081 dannenberg (run by CCC).
18082 - Switch to multi-level keys for directory authorities: now their
18083 long-term identity key can be kept offline, and they periodically
18084 generate a new signing key. Clients fetch the "key certificates"
18085 to keep up to date on the right keys. Add a standalone tool
18086 "tor-gencert" to generate key certificates. Implements proposal 103.
18087 - Add a new V3AuthUseLegacyKey config option to make it easier for
18088 v3 authorities to change their identity keys if another bug like
18089 Debian's OpenSSL RNG flaw appears.
18090 - Authorities and caches fetch the v2 networkstatus documents
18091 less often, now that v3 is recommended.
18093 o Make Tor connections stand out less on the wire:
18094 - Use an improved TLS handshake designed by Steven Murdoch in proposal
18095 124, as revised in proposal 130. The new handshake is meant to
18096 be harder for censors to fingerprint, and it adds the ability
18097 to detect certain kinds of man-in-the-middle traffic analysis
18098 attacks. The new handshake format includes version negotiation for
18099 OR connections as described in proposal 105, which will allow us
18100 to improve Tor's link protocol more safely in the future.
18101 - Enable encrypted directory connections by default for non-relays,
18102 so censor tools that block Tor directory connections based on their
18103 plaintext patterns will no longer work. This means Tor works in
18104 certain censored countries by default again.
18105 - Stop including recognizeable strings in the commonname part of
18106 Tor's x509 certificates.
18108 o Implement bridge relays:
18109 - Bridge relays (or "bridges" for short) are Tor relays that aren't
18110 listed in the main Tor directory. Since there is no complete public
18111 list of them, even an ISP that is filtering connections to all the
18112 known Tor relays probably won't be able to block all the bridges.
18113 See doc/design-paper/blocking.pdf and proposal 125 for details.
18114 - New config option BridgeRelay that specifies you want to be a
18115 bridge relay rather than a normal relay. When BridgeRelay is set
18116 to 1, then a) you cache dir info even if your DirPort ins't on,
18117 and b) the default for PublishServerDescriptor is now "bridge"
18118 rather than "v2,v3".
18119 - New config option "UseBridges 1" for clients that want to use bridge
18120 relays instead of ordinary entry guards. Clients then specify
18121 bridge relays by adding "Bridge" lines to their config file. Users
18122 can learn about a bridge relay either manually through word of
18123 mouth, or by one of our rate-limited mechanisms for giving out
18124 bridge addresses without letting an attacker easily enumerate them
18125 all. See https://www.torproject.org/bridges for details.
18126 - Bridge relays behave like clients with respect to time intervals
18127 for downloading new v3 consensus documents -- otherwise they
18128 stand out. Bridge users now wait until the end of the interval,
18129 so their bridge relay will be sure to have a new consensus document.
18131 o Implement bridge directory authorities:
18132 - Bridge authorities are like normal directory authorities, except
18133 they don't serve a list of known bridges. Therefore users that know
18134 a bridge's fingerprint can fetch a relay descriptor for that bridge,
18135 including fetching updates e.g. if the bridge changes IP address,
18136 yet an attacker can't just fetch a list of all the bridges.
18137 - Set up Tonga as the default bridge directory authority.
18138 - Bridge authorities refuse to serve bridge descriptors or other
18139 bridge information over unencrypted connections (that is, when
18140 responding to direct DirPort requests rather than begin_dir cells.)
18141 - Bridge directory authorities do reachability testing on the
18142 bridges they know. They provide router status summaries to the
18143 controller via "getinfo ns/purpose/bridge", and also dump summaries
18144 to a file periodically, so we can keep internal stats about which
18145 bridges are functioning.
18146 - If bridge users set the UpdateBridgesFromAuthority config option,
18147 but the digest they ask for is a 404 on the bridge authority,
18148 they fall back to contacting the bridge directly.
18149 - Bridges always use begin_dir to publish their server descriptor to
18150 the bridge authority using an anonymous encrypted tunnel.
18151 - Early work on a "bridge community" design: if bridge authorities set
18152 the BridgePassword config option, they will serve a snapshot of
18153 known bridge routerstatuses from their DirPort to anybody who
18154 knows that password. Unset by default.
18155 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
18156 report sanitized aggregated summaries in their extra-info documents
18157 privately to the bridge authority, listing which countries are
18158 able to reach them. We hope this mechanism will let us learn when
18159 certain countries start trying to block bridges.
18160 - Bridge authorities write bridge descriptors to disk, so they can
18161 reload them after a reboot. They can also export the descriptors
18162 to other programs, so we can distribute them to blocked users via
18163 the BridgeDB interface, e.g. via https://bridges.torproject.org/
18164 and bridges@torproject.org.
18166 o Tor can be a DNS proxy:
18167 - The new client-side DNS proxy feature replaces the need for
18168 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
18169 for DNS requests on port 9999, use the Tor network to resolve them
18170 anonymously, and send the reply back like a regular DNS server.
18171 The code still only implements a subset of DNS.
18172 - Add a new AutomapHostsOnResolve option: when it is enabled, any
18173 resolve request for hosts matching a given pattern causes Tor to
18174 generate an internal virtual address mapping for that host. This
18175 allows DNSPort to work sensibly with hidden service users. By
18176 default, .exit and .onion addresses are remapped; the list of
18177 patterns can be reconfigured with AutomapHostsSuffixes.
18178 - Add an "-F" option to tor-resolve to force a resolve for a .onion
18179 address. Thanks to the AutomapHostsOnResolve option, this is no
18180 longer a completely silly thing to do.
18182 o Major features (relay usability):
18183 - New config options RelayBandwidthRate and RelayBandwidthBurst:
18184 a separate set of token buckets for relayed traffic. Right now
18185 relayed traffic is defined as answers to directory requests, and
18186 OR connections that don't have any local circuits on them. See
18187 proposal 111 for details.
18188 - Create listener connections before we setuid to the configured
18189 User and Group. Now non-Windows users can choose port values
18190 under 1024, start Tor as root, and have Tor bind those ports
18191 before it changes to another UID. (Windows users could already
18193 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
18194 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
18195 on "vserver" accounts. Patch from coderman.
18197 o Major features (directory authorities):
18198 - Directory authorities track weighted fractional uptime and weighted
18199 mean-time-between failures for relays. WFU is suitable for deciding
18200 whether a node is "usually up", while MTBF is suitable for deciding
18201 whether a node is "likely to stay up." We need both, because
18202 "usually up" is a good requirement for guards, while "likely to
18203 stay up" is a good requirement for long-lived connections.
18204 - Directory authorities use a new formula for selecting which relays
18205 to advertise as Guards: they must be in the top 7/8 in terms of
18206 how long we have known about them, and above the median of those
18207 nodes in terms of weighted fractional uptime.
18208 - Directory authorities use a new formula for selecting which relays
18209 to advertise as Stable: when we have 4 or more days of data, use
18210 median measured MTBF rather than median declared uptime. Implements
18212 - Directory authorities accept and serve "extra info" documents for
18213 routers. Routers now publish their bandwidth-history lines in the
18214 extra-info docs rather than the main descriptor. This step saves
18215 60% (!) on compressed router descriptor downloads. Servers upload
18216 extra-info docs to any authority that accepts them; directory
18217 authorities now allow multiple router descriptors and/or extra
18218 info documents to be uploaded in a single go. Authorities, and
18219 caches that have been configured to download extra-info documents,
18220 download them as needed. Implements proposal 104.
18221 - Authorities now list relays who have the same nickname as
18222 a different named relay, but list them with a new flag:
18223 "Unnamed". Now we can make use of relays that happen to pick the
18224 same nickname as a server that registered two years ago and then
18225 disappeared. Implements proposal 122.
18226 - Store routers in a file called cached-descriptors instead of in
18227 cached-routers. Initialize cached-descriptors from cached-routers
18228 if the old format is around. The new format allows us to store
18229 annotations along with descriptors, to record the time we received
18230 each descriptor, its source, and its purpose: currently one of
18231 general, controller, or bridge.
18233 o Major features (other):
18234 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
18235 Tor can warn and/or refuse connections to ports commonly used with
18236 vulnerable-plaintext protocols. Currently we warn on ports 23,
18237 109, 110, and 143, but we don't reject any. Based on proposal 129
18238 by Kevin Bauer and Damon McCoy.
18239 - Integrate Karsten Loesing's Google Summer of Code project to publish
18240 hidden service descriptors on a set of redundant relays that are a
18241 function of the hidden service address. Now we don't have to rely
18242 on three central hidden service authorities for publishing and
18243 fetching every hidden service descriptor. Implements proposal 114.
18244 - Allow tunnelled directory connections to ask for an encrypted
18245 "begin_dir" connection or an anonymized "uses a full Tor circuit"
18246 connection independently. Now we can make anonymized begin_dir
18247 connections for (e.g.) more secure hidden service posting and
18250 o Major bugfixes (crashes and assert failures):
18251 - Stop imposing an arbitrary maximum on the number of file descriptors
18252 used for busy servers. Bug reported by Olaf Selke; patch from
18254 - Avoid possible failures when generating a directory with routers
18255 with over-long versions strings, or too many flags set.
18256 - Fix a rare assert error when we're closing one of our threads:
18257 use a mutex to protect the list of logs, so we never write to the
18258 list as it's being freed. Fixes the very rare bug 575, which is
18259 kind of the revenge of bug 222.
18260 - Avoid segfault in the case where a badly behaved v2 versioning
18261 directory sends a signed networkstatus with missing client-versions.
18262 - When we hit an EOF on a log (probably because we're shutting down),
18263 don't try to remove the log from the list: just mark it as
18264 unusable. (Bulletproofs against bug 222.)
18266 o Major bugfixes (code security fixes):
18267 - Detect size overflow in zlib code. Reported by Justin Ferguson and
18269 - Rewrite directory tokenization code to never run off the end of
18270 a string. Fixes bug 455. Patch from croup.
18271 - Be more paranoid about overwriting sensitive memory on free(),
18272 as a defensive programming tactic to ensure forward secrecy.
18274 o Major bugfixes (anonymity fixes):
18275 - Reject requests for reverse-dns lookup of names that are in
18276 a private address space. Patch from lodger.
18277 - Never report that we've used more bandwidth than we're willing to
18278 relay: it leaks how much non-relay traffic we're using. Resolves
18280 - As a client, do not believe any server that tells us that an
18281 address maps to an internal address space.
18282 - Warn about unsafe ControlPort configurations.
18283 - Directory authorities now call routers Fast if their bandwidth is
18284 at least 100KB/s, and consider their bandwidth adequate to be a
18285 Guard if it is at least 250KB/s, no matter the medians. This fix
18286 complements proposal 107.
18287 - Directory authorities now never mark more than 2 servers per IP as
18288 Valid and Running (or 5 on addresses shared by authorities).
18289 Implements proposal 109, by Kevin Bauer and Damon McCoy.
18290 - If we're a relay, avoid picking ourselves as an introduction point,
18291 a rendezvous point, or as the final hop for internal circuits. Bug
18292 reported by taranis and lodger.
18293 - Exit relays that are used as a client can now reach themselves
18294 using the .exit notation, rather than just launching an infinite
18295 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
18296 - Fix a bug where, when we were choosing the 'end stream reason' to
18297 put in our relay end cell that we send to the exit relay, Tor
18298 clients on Windows were sometimes sending the wrong 'reason'. The
18299 anonymity problem is that exit relays may be able to guess whether
18300 the client is running Windows, thus helping partition the anonymity
18301 set. Down the road we should stop sending reasons to exit relays,
18302 or otherwise prevent future versions of this bug.
18303 - Only update guard status (usable / not usable) once we have
18304 enough directory information. This was causing us to discard all our
18305 guards on startup if we hadn't been running for a few weeks. Fixes
18307 - When our directory information has been expired for a while, stop
18308 being willing to build circuits using it. Fixes bug 401.
18310 o Major bugfixes (peace of mind for relay operators)
18311 - Non-exit relays no longer answer "resolve" relay cells, so they
18312 can't be induced to do arbitrary DNS requests. (Tor clients already
18313 avoid using non-exit relays for resolve cells, but now servers
18314 enforce this too.) Fixes bug 619. Patch from lodger.
18315 - When we setconf ClientOnly to 1, close any current OR and Dir
18316 listeners. Reported by mwenge.
18318 o Major bugfixes (other):
18319 - If we only ever used Tor for hidden service lookups or posts, we
18320 would stop building circuits and start refusing connections after
18321 24 hours, since we falsely believed that Tor was dormant. Reported
18323 - Add a new __HashedControlSessionPassword option for controllers
18324 to use for one-off session password hashes that shouldn't get
18325 saved to disk by SAVECONF --- Vidalia users were accumulating a
18326 pile of HashedControlPassword lines in their torrc files, one for
18327 each time they had restarted Tor and then clicked Save. Make Tor
18328 automatically convert "HashedControlPassword" to this new option but
18329 only when it's given on the command line. Partial fix for bug 586.
18330 - Patch from "Andrew S. Lists" to catch when we contact a directory
18331 mirror at IP address X and he says we look like we're coming from
18332 IP address X. Otherwise this would screw up our address detection.
18333 - Reject uploaded descriptors and extrainfo documents if they're
18334 huge. Otherwise we'll cache them all over the network and it'll
18335 clog everything up. Suggested by Aljosha Judmayer.
18336 - When a hidden service was trying to establish an introduction point,
18337 and Tor *did* manage to reuse one of the preemptively built
18338 circuits, it didn't correctly remember which one it used,
18339 so it asked for another one soon after, until there were no
18340 more preemptive circuits, at which point it launched one from
18341 scratch. Bugfix on 0.0.9.x.
18343 o Rate limiting and load balancing improvements:
18344 - When we add data to a write buffer in response to the data on that
18345 write buffer getting low because of a flush, do not consider the
18346 newly added data as a candidate for immediate flushing, but rather
18347 make it wait until the next round of writing. Otherwise, we flush
18348 and refill recursively, and a single greedy TLS connection can
18349 eat all of our bandwidth.
18350 - When counting the number of bytes written on a TLS connection,
18351 look at the BIO actually used for writing to the network, not
18352 at the BIO used (sometimes) to buffer data for the network.
18353 Looking at different BIOs could result in write counts on the
18354 order of ULONG_MAX. Fixes bug 614.
18355 - If we change our MaxAdvertisedBandwidth and then reload torrc,
18356 Tor won't realize it should publish a new relay descriptor. Fixes
18357 bug 688, reported by mfr.
18358 - Avoid using too little bandwidth when our clock skips a few seconds.
18359 - Choose which bridge to use proportional to its advertised bandwidth,
18360 rather than uniformly at random. This should speed up Tor for
18361 bridge users. Also do this for people who set StrictEntryNodes.
18363 o Bootstrapping faster and building circuits more intelligently:
18364 - Fix bug 660 that was preventing us from knowing that we should
18365 preemptively build circuits to handle expected directory requests.
18366 - When we're checking if we have enough dir info for each relay
18367 to begin establishing circuits, make sure that we actually have
18368 the descriptor listed in the consensus, not just any descriptor.
18369 - Correctly notify one-hop connections when a circuit build has
18370 failed. Possible fix for bug 669. Found by lodger.
18371 - Clients now hold circuitless TLS connections open for 1.5 times
18372 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
18373 rebuild a new circuit over them within that timeframe. Previously,
18374 they held them open only for KeepalivePeriod (5 minutes).
18376 o Performance improvements (memory):
18377 - Add OpenBSD malloc code from "phk" as an optional malloc
18378 replacement on Linux: some glibc libraries do very poorly with
18379 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
18380 ./configure to get the replacement malloc code.
18381 - Switch our old ring buffer implementation for one more like that
18382 used by free Unix kernels. The wasted space in a buffer with 1mb
18383 of data will now be more like 8k than 1mb. The new implementation
18384 also avoids realloc();realloc(); patterns that can contribute to
18385 memory fragmentation.
18386 - Change the way that Tor buffers data that it is waiting to write.
18387 Instead of queueing data cells in an enormous ring buffer for each
18388 client->OR or OR->OR connection, we now queue cells on a separate
18389 queue for each circuit. This lets us use less slack memory, and
18390 will eventually let us be smarter about prioritizing different kinds
18392 - Reference-count and share copies of address policy entries; only 5%
18393 of them were actually distinct.
18394 - Tune parameters for cell pool allocation to minimize amount of
18396 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
18397 for every single inactive connection_t. Free items from the
18398 4k/16k-buffer free lists when they haven't been used for a while.
18399 - Make memory debugging information describe more about history
18400 of cell allocation, so we can help reduce our memory use.
18401 - Be even more aggressive about releasing RAM from small
18402 empty buffers. Thanks to our free-list code, this shouldn't be too
18403 performance-intensive.
18404 - Log malloc statistics from mallinfo() on platforms where it exists.
18405 - Use memory pools to allocate cells with better speed and memory
18406 efficiency, especially on platforms where malloc() is inefficient.
18407 - Add a --with-tcmalloc option to the configure script to link
18408 against tcmalloc (if present). Does not yet search for non-system
18411 o Performance improvements (socket management):
18412 - Count the number of open sockets separately from the number of
18413 active connection_t objects. This will let us avoid underusing
18414 our allocated connection limit.
18415 - We no longer use socket pairs to link an edge connection to an
18416 anonymous directory connection or a DirPort test connection.
18417 Instead, we track the link internally and transfer the data
18418 in-process. This saves two sockets per "linked" connection (at the
18419 client and at the server), and avoids the nasty Windows socketpair()
18421 - We were leaking a file descriptor if Tor started with a zero-length
18422 cached-descriptors file. Patch by "freddy77".
18424 o Performance improvements (CPU use):
18425 - Never walk through the list of logs if we know that no log target
18426 is interested in a given message.
18427 - Call routerlist_remove_old_routers() much less often. This should
18428 speed startup, especially on directory caches.
18429 - Base64 decoding was actually showing up on our profile when parsing
18430 the initial descriptor file; switch to an in-process all-at-once
18431 implementation that's about 3.5x times faster than calling out to
18433 - Use a slightly simpler string hashing algorithm (copying Python's
18434 instead of Java's) and optimize our digest hashing algorithm to take
18435 advantage of 64-bit platforms and to remove some possibly-costly
18437 - When implementing AES counter mode, update only the portions of the
18438 counter buffer that need to change, and don't keep separate
18439 network-order and host-order counters on big-endian hosts (where
18440 they are the same).
18441 - Add an in-place version of aes_crypt() so that we can avoid doing a
18442 needless memcpy() call on each cell payload.
18443 - Use Critical Sections rather than Mutexes for synchronizing threads
18444 on win32; Mutexes are heavier-weight, and designed for synchronizing
18447 o Performance improvements (bandwidth use):
18448 - Don't try to launch new descriptor downloads quite so often when we
18449 already have enough directory information to build circuits.
18450 - Version 1 directories are no longer generated in full. Instead,
18451 authorities generate and serve "stub" v1 directories that list
18452 no servers. This will stop Tor versions 0.1.0.x and earlier from
18453 working, but (for security reasons) nobody should be running those
18455 - Avoid going directly to the directory authorities even if you're a
18456 relay, if you haven't found yourself reachable yet or if you've
18457 decided not to advertise your dirport yet. Addresses bug 556.
18458 - If we've gone 12 hours since our last bandwidth check, and we
18459 estimate we have less than 50KB bandwidth capacity but we could
18460 handle more, do another bandwidth test.
18461 - Support "If-Modified-Since" when answering HTTP requests for
18462 directories, running-routers documents, and v2 and v3 networkstatus
18463 documents. (There's no need to support it for router descriptors,
18464 since those are downloaded by descriptor digest.)
18465 - Stop fetching directory info so aggressively if your DirPort is
18466 on but your ORPort is off; stop fetching v2 dir info entirely.
18467 You can override these choices with the new FetchDirInfoEarly
18470 o Changed config option behavior (features):
18471 - Configuration files now accept C-style strings as values. This
18472 helps encode characters not allowed in the current configuration
18473 file format, such as newline or #. Addresses bug 557.
18474 - Add hidden services and DNSPorts to the list of things that make
18475 Tor accept that it has running ports. Change starting Tor with no
18476 ports from a fatal error to a warning; we might change it back if
18477 this turns out to confuse anybody. Fixes bug 579.
18478 - Make PublishServerDescriptor default to 1, so the default doesn't
18479 have to change as we invent new directory protocol versions.
18480 - Allow people to say PreferTunnelledDirConns rather than
18481 PreferTunneledDirConns, for those alternate-spellers out there.
18482 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
18483 accommodate the growing number of servers that use the default
18484 and are reaching it.
18485 - Make it possible to enable HashedControlPassword and
18486 CookieAuthentication at the same time.
18487 - When a TrackHostExits-chosen exit fails too many times in a row,
18488 stop using it. Fixes bug 437.
18490 o Changed config option behavior (bugfixes):
18491 - Do not read the configuration file when we've only been told to
18492 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
18493 based on patch from Sebastian Hahn.
18494 - Actually validate the options passed to AuthDirReject,
18495 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
18496 - Make "ClientOnly 1" config option disable directory ports too.
18497 - Don't stop fetching descriptors when FetchUselessDescriptors is
18498 set, even if we stop asking for circuits. Bug reported by tup
18500 - Servers used to decline to publish their DirPort if their
18501 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
18502 they look only at BandwidthRate and RelayBandwidthRate.
18503 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
18504 minus 1 byte: the actual maximum declared bandwidth.
18505 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
18506 - Make the NodeFamilies config option work. (Reported by
18507 lodger -- it has never actually worked, even though we added it
18509 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
18510 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
18512 o New config options:
18513 - New configuration options AuthDirMaxServersPerAddr and
18514 AuthDirMaxServersperAuthAddr to override default maximum number
18515 of servers allowed on a single IP address. This is important for
18516 running a test network on a single host.
18517 - Three new config options (AlternateDirAuthority,
18518 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
18519 user selectively replace the default directory authorities by type,
18520 rather than the all-or-nothing replacement that DirServer offers.
18521 - New config options AuthDirBadDir and AuthDirListBadDirs for
18522 authorities to mark certain relays as "bad directories" in the
18523 networkstatus documents. Also supports the "!baddir" directive in
18524 the approved-routers file.
18525 - New config option V2AuthoritativeDirectory that all v2 directory
18526 authorities must set. This lets v3 authorities choose not to serve
18527 v2 directory information.
18529 o Minor features (other):
18530 - When we're not serving v2 directory information, there is no reason
18531 to actually keep any around. Remove the obsolete files and directory
18532 on startup if they are very old and we aren't going to serve them.
18533 - When we negotiate a v2 link-layer connection (not yet implemented),
18534 accept RELAY_EARLY cells and turn them into RELAY cells if we've
18535 negotiated a v1 connection for their next step. Initial steps for
18537 - When we have no consensus, check FallbackNetworkstatusFile (defaults
18538 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
18539 we can start out knowing some directory caches. We don't ship with
18540 a fallback consensus by default though, because it was making
18541 bootstrapping take too long while we tried many down relays.
18542 - Authorities send back an X-Descriptor-Not-New header in response to
18543 an accepted-but-discarded descriptor upload. Partially implements
18545 - If we find a cached-routers file that's been sitting around for more
18546 than 28 days unmodified, then most likely it's a leftover from
18547 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
18549 - When we (as a cache) download a descriptor because it was listed
18550 in a consensus, remember when the consensus was supposed to expire,
18551 and don't expire the descriptor until then.
18552 - Optionally (if built with -DEXPORTMALLINFO) export the output
18553 of mallinfo via http, as tor/mallinfo.txt. Only accessible
18555 - Tag every guard node in our state file with the version that
18556 we believe added it, or with our own version if we add it. This way,
18557 if a user temporarily runs an old version of Tor and then switches
18558 back to a new one, she doesn't automatically lose her guards.
18559 - When somebody requests a list of statuses or servers, and we have
18560 none of those, return a 404 rather than an empty 200.
18561 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
18563 - Add an HSAuthorityRecordStats option that hidden service authorities
18564 can use to track statistics of overall hidden service usage without
18565 logging information that would be as useful to an attacker.
18566 - Allow multiple HiddenServicePort directives with the same virtual
18567 port; when they occur, the user is sent round-robin to one
18568 of the target ports chosen at random. Partially fixes bug 393 by
18569 adding limited ad-hoc round-robining.
18570 - Revamp file-writing logic so we don't need to have the entire
18571 contents of a file in memory at once before we write to disk. Tor,
18574 o Minor bugfixes (other):
18575 - Alter the code that tries to recover from unhandled write
18576 errors, to not try to flush onto a socket that's given us
18578 - Directory mirrors no longer include a guess at the client's IP
18579 address if the connection appears to be coming from the same /24
18580 network; it was producing too many wrong guesses.
18581 - If we're trying to flush the last bytes on a connection (for
18582 example, when answering a directory request), reset the
18583 time-to-give-up timeout every time we manage to write something
18585 - Reject router descriptors with out-of-range bandwidthcapacity or
18586 bandwidthburst values.
18587 - If we can't expand our list of entry guards (e.g. because we're
18588 using bridges or we have StrictEntryNodes set), don't mark relays
18589 down when they fail a directory request. Otherwise we're too quick
18590 to mark all our entry points down.
18591 - Authorities no longer send back "400 you're unreachable please fix
18592 it" errors to Tor servers that aren't online all the time. We're
18593 supposed to tolerate these servers now.
18594 - Let directory authorities startup even when they can't generate
18595 a descriptor immediately, e.g. because they don't know their
18597 - Correctly enforce that elements of directory objects do not appear
18598 more often than they are allowed to appear.
18599 - Stop allowing hibernating servers to be "stable" or "fast".
18600 - On Windows, we were preventing other processes from reading
18601 cached-routers while Tor was running. (Reported by janbar)
18602 - Check return values from pthread_mutex functions.
18603 - When opening /dev/null in finish_daemonize(), do not pass the
18604 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
18605 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
18607 o Controller features:
18608 - The GETCONF command now escapes and quotes configuration values
18609 that don't otherwise fit into the torrc file.
18610 - The SETCONF command now handles quoted values correctly.
18611 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
18612 ask about source, timestamp of arrival, purpose, etc. We need
18613 something like this to help Vidalia not do GeoIP lookups on bridge
18615 - Allow multiple HashedControlPassword config lines, to support
18616 multiple controller passwords.
18617 - Accept LF instead of CRLF on controller, since some software has a
18618 hard time generating real Internet newlines.
18619 - Add GETINFO values for the server status events
18620 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
18622 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
18623 GETINFO for Torstat to use until it can switch to using extrainfos.
18624 - New config option CookieAuthFile to choose a new location for the
18625 cookie authentication file, and config option
18626 CookieAuthFileGroupReadable to make it group-readable.
18627 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
18628 match requests to applications. Patch from Robert Hogan.
18629 - Add a RESOLVE command to launch hostname lookups. Original patch
18631 - Add GETINFO status/enough-dir-info to let controllers tell whether
18632 Tor has downloaded sufficient directory information. Patch from Tup.
18633 - You can now use the ControlSocket option to tell Tor to listen for
18634 controller connections on Unix domain sockets on systems that
18635 support them. Patch from Peter Palfrader.
18636 - New "GETINFO address-mappings/*" command to get address mappings
18637 with expiry information. "addr-mappings/*" is now deprecated.
18639 - Add a new config option __DisablePredictedCircuits designed for
18640 use by the controller, when we don't want Tor to build any circuits
18642 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
18643 so we can exit from the middle of the circuit.
18644 - Implement "getinfo status/circuit-established".
18645 - Implement "getinfo status/version/..." so a controller can tell
18646 whether the current version is recommended, and whether any versions
18647 are good, and how many authorities agree. Patch from "shibz".
18648 - Controllers should now specify cache=no or cache=yes when using
18649 the +POSTDESCRIPTOR command.
18650 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
18651 Robert Hogan. Fixes the first part of bug 681.
18652 - When reporting clock skew, and we know that the clock is _at least
18653 as skewed_ as some value, but we don't know the actual value,
18654 report the value as a "minimum skew."
18656 o Controller bugfixes:
18657 - Generate "STATUS_SERVER" events rather than misspelled
18658 "STATUS_SEVER" events. Caught by mwenge.
18659 - Reject controller commands over 1MB in length, so rogue
18660 processes can't run us out of memory.
18661 - Change the behavior of "getinfo status/good-server-descriptor"
18662 so it doesn't return failure when any authority disappears.
18663 - Send NAMESERVER_STATUS messages for a single failed nameserver
18665 - When the DANGEROUS_VERSION controller status event told us we're
18666 running an obsolete version, it used the string "OLD" to describe
18667 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
18668 "OBSOLETE" in both cases.
18669 - Respond to INT and TERM SIGNAL commands before we execute the
18670 signal, in case the signal shuts us down. We had a patch in
18671 0.1.2.1-alpha that tried to do this by queueing the response on
18672 the connection's buffer before shutting down, but that really
18673 isn't the same thing at all. Bug located by Matt Edman.
18674 - Provide DNS expiry times in GMT, not in local time. For backward
18675 compatibility, ADDRMAP events only provide GMT expiry in an extended
18676 field. "GETINFO address-mappings" always does the right thing.
18677 - Use CRLF line endings properly in NS events.
18678 - Make 'getinfo fingerprint' return a 551 error if we're not a
18679 server, so we match what the control spec claims we do. Reported
18681 - Fix a typo in an error message when extendcircuit fails that
18682 caused us to not follow the \r\n-based delimiter protocol. Reported
18684 - When tunneling an encrypted directory connection, and its first
18685 circuit fails, do not leave it unattached and ask the controller
18686 to deal. Fixes the second part of bug 681.
18687 - Treat some 403 responses from directory servers as INFO rather than
18688 WARN-severity events.
18690 o Portability / building / compiling:
18691 - When building with --enable-gcc-warnings, check for whether Apple's
18692 warning "-Wshorten-64-to-32" is available.
18693 - Support compilation to target iPhone; patch from cjacker huang.
18694 To build for iPhone, pass the --enable-iphone option to configure.
18695 - Port Tor to build and run correctly on Windows CE systems, using
18696 the wcecompat library. Contributed by Valerio Lupi.
18697 - Detect non-ASCII platforms (if any still exist) and refuse to
18698 build there: some of our code assumes that 'A' is 65 and so on.
18699 - Clear up some MIPSPro compiler warnings.
18700 - Make autoconf search for libevent, openssl, and zlib consistently.
18701 - Update deprecated macros in configure.in.
18702 - When warning about missing headers, tell the user to let us
18703 know if the compile succeeds anyway, so we can downgrade the
18705 - Include the current subversion revision as part of the version
18706 string: either fetch it directly if we're in an SVN checkout, do
18707 some magic to guess it if we're in an SVK checkout, or use
18708 the last-detected version if we're building from a .tar.gz.
18709 Use this version consistently in log messages.
18710 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
18711 - Read resolv.conf files correctly on platforms where read() returns
18712 partial results on small file reads.
18713 - Build without verbose warnings even on gcc 4.2 and 4.3.
18714 - On Windows, correctly detect errors when listing the contents of
18715 a directory. Fix from lodger.
18716 - Run 'make test' as part of 'make dist', so we stop releasing so
18717 many development snapshots that fail their unit tests.
18718 - Add support to detect Libevent versions in the 1.4.x series
18720 - Add command-line arguments to unit-test executable so that we can
18721 invoke any chosen test from the command line rather than having
18722 to run the whole test suite at once; and so that we can turn on
18723 logging for the unit tests.
18724 - Do not automatically run configure from autogen.sh. This
18725 non-standard behavior tended to annoy people who have built other
18727 - Fix a macro/CPP interaction that was confusing some compilers:
18728 some GCCs don't like #if/#endif pairs inside macro arguments.
18730 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
18731 Fixes bug 704; fix from Steven Murdoch.
18732 - Correctly detect transparent proxy support on Linux hosts that
18733 require in.h to be included before netfilter_ipv4.h. Patch
18736 o Logging improvements:
18737 - When we haven't had any application requests lately, don't bother
18738 logging that we have expired a bunch of descriptors.
18739 - When attempting to open a logfile fails, tell us why.
18740 - Only log guard node status when guard node status has changed.
18741 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
18742 make "INFO" 75% less verbose.
18743 - When SafeLogging is disabled, log addresses along with all TLS
18745 - Report TLS "zero return" case as a "clean close" and "IO error"
18746 as a "close". Stop calling closes "unexpected closes": existing
18747 Tors don't use SSL_close(), so having a connection close without
18748 the TLS shutdown handshake is hardly unexpected.
18749 - When we receive a consensus from the future, warn about skew.
18750 - Make "not enough dir info yet" warnings describe *why* Tor feels
18751 it doesn't have enough directory info yet.
18752 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
18753 consumers. (We already do this on HUP.)
18754 - Give more descriptive well-formedness errors for out-of-range
18755 hidden service descriptor/protocol versions.
18756 - Stop recommending that every server operator send mail to tor-ops.
18757 Resolves bug 597. Bugfix on 0.1.2.x.
18758 - Improve skew reporting: try to give the user a better log message
18759 about how skewed they are, and how much this matters.
18760 - New --quiet command-line option to suppress the default console log.
18761 Good in combination with --hash-password.
18762 - Don't complain that "your server has not managed to confirm that its
18763 ports are reachable" if we haven't been able to build any circuits
18765 - Detect the reason for failing to mmap a descriptor file we just
18766 wrote, and give a more useful log message. Fixes bug 533.
18767 - Always prepend "Bug: " to any log message about a bug.
18768 - When dumping memory usage, list bytes used in buffer memory
18770 - When running with dmalloc, dump more stats on hup and on exit.
18771 - Put a platform string (e.g. "Linux i686") in the startup log
18772 message, so when people paste just their logs, we know if it's
18773 OpenBSD or Windows or what.
18774 - When logging memory usage, break down memory used in buffers by
18776 - When we are reporting the DirServer line we just parsed, we were
18777 logging the second stanza of the key fingerprint, not the first.
18778 - Even though Windows is equally happy with / and \ as path separators,
18779 try to use \ consistently on Windows and / consistently on Unix: it
18780 makes the log messages nicer.
18781 - On OSX, stop warning the user that kqueue support in libevent is
18782 "experimental", since it seems to have worked fine for ages.
18784 o Contributed scripts and tools:
18785 - Update linux-tor-prio.sh script to allow QoS based on the uid of
18786 the Tor process. Patch from Marco Bonetti with tweaks from Mike
18788 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
18789 Unix users an easy way to script their Tor process (e.g. by
18790 adjusting bandwidth based on the time of the day).
18791 - In the exitlist script, only consider the most recently published
18792 server descriptor for each server. Also, when the user requests
18793 a list of servers that _reject_ connections to a given address,
18794 explicitly exclude the IPs that also have servers that accept
18795 connections to that address. Resolves bug 405.
18796 - Include a new contrib/tor-exit-notice.html file that exit relay
18797 operators can put on their website to help reduce abuse queries.
18799 o Newly deprecated features:
18800 - The status/version/num-versioning and status/version/num-concurring
18801 GETINFO controller options are no longer useful in the v3 directory
18802 protocol: treat them as deprecated, and warn when they're used.
18803 - The RedirectExits config option is now deprecated.
18805 o Removed features:
18806 - Drop the old code to choke directory connections when the
18807 corresponding OR connections got full: thanks to the cell queue
18808 feature, OR conns don't get full any more.
18809 - Remove the old "dns worker" server DNS code: it hasn't been default
18810 since 0.1.2.2-alpha, and all the servers are using the new
18812 - Remove the code to generate the oldest (v1) directory format.
18813 - Remove support for the old bw_accounting file: we've been storing
18814 bandwidth accounting information in the state file since
18815 0.1.2.5-alpha. This may result in bandwidth accounting errors
18816 if you try to upgrade from 0.1.1.x or earlier, or if you try to
18817 downgrade to 0.1.1.x or earlier.
18818 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
18819 it, it had no AES, and it hasn't seen any security patches since
18821 - Stop overloading the circuit_t.onionskin field for both "onionskin
18822 from a CREATE cell that we are waiting for a cpuworker to be
18823 assigned" and "onionskin from an EXTEND cell that we are going to
18824 send to an OR as soon as we are connected". Might help with bug 600.
18825 - Remove the tor_strpartition() function: its logic was confused,
18826 and it was only used for one thing that could be implemented far
18828 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
18829 and TorControl.py, as they use the old v0 controller protocol,
18830 and are obsoleted by TorFlow anyway.
18831 - Drop support for v1 rendezvous descriptors, since we never used
18832 them anyway, and the code has probably rotted by now. Based on
18833 patch from Karsten Loesing.
18834 - Stop allowing address masks that do not correspond to bit prefixes.
18835 We have warned about these for a really long time; now it's time
18836 to reject them. (Patch from croup.)
18837 - Remove an optimization in the AES counter-mode code that assumed
18838 that the counter never exceeded 2^68. When the counter can be set
18839 arbitrarily as an IV (as it is by Karsten's new hidden services
18840 code), this assumption no longer holds.
18841 - Disable the SETROUTERPURPOSE controller command: it is now
18845 Changes in version 0.1.2.19 - 2008-01-17
18846 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
18847 exit policy a little bit more conservative so it's safer to run an
18848 exit relay on a home system, and fixes a variety of smaller issues.
18851 - Exit policies now reject connections that are addressed to a
18852 relay's public (external) IP address too, unless
18853 ExitPolicyRejectPrivate is turned off. We do this because too
18854 many relays are running nearby to services that trust them based
18855 on network address.
18858 - When the clock jumps forward a lot, do not allow the bandwidth
18859 buckets to become negative. Fixes bug 544.
18860 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
18861 on every successful resolve. Reported by Mike Perry.
18862 - Purge old entries from the "rephist" database and the hidden
18863 service descriptor database even when DirPort is zero.
18864 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
18865 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
18866 crashing or mis-answering these requests.
18867 - When we decide to send a 503 response to a request for servers, do
18868 not then also send the server descriptors: this defeats the whole
18869 purpose. Fixes bug 539.
18872 - Changing the ExitPolicyRejectPrivate setting should cause us to
18873 rebuild our server descriptor.
18874 - Fix handling of hex nicknames when answering controller requests for
18875 networkstatus by name, or when deciding whether to warn about
18876 unknown routers in a config option. (Patch from mwenge.)
18877 - Fix a couple of hard-to-trigger autoconf problems that could result
18878 in really weird results on platforms whose sys/types.h files define
18879 nonstandard integer types.
18880 - Don't try to create the datadir when running --verify-config or
18881 --hash-password. Resolves bug 540.
18882 - If we were having problems getting a particular descriptor from the
18883 directory caches, and then we learned about a new descriptor for
18884 that router, we weren't resetting our failure count. Reported
18886 - Although we fixed bug 539 (where servers would send HTTP status 503
18887 responses _and_ send a body too), there are still servers out there
18888 that haven't upgraded. Therefore, make clients parse such bodies
18889 when they receive them.
18890 - Run correctly on systems where rlim_t is larger than unsigned long.
18891 This includes some 64-bit systems.
18892 - Run correctly on platforms (like some versions of OS X 10.5) where
18893 the real limit for number of open files is OPEN_FILES, not rlim_max
18894 from getrlimit(RLIMIT_NOFILES).
18895 - Avoid a spurious free on base64 failure.
18896 - Avoid segfaults on certain complex invocations of
18897 router_get_by_hexdigest().
18898 - Fix rare bug on REDIRECTSTREAM control command when called with no
18899 port set: it could erroneously report an error when none had
18903 Changes in version 0.1.2.18 - 2007-10-28
18904 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
18905 hidden service introduction that were causing huge delays, and a big
18906 bug that was causing some servers to disappear from the network status
18907 lists for a few hours each day.
18909 o Major bugfixes (crashes):
18910 - If a connection is shut down abruptly because of something that
18911 happened inside connection_flushed_some(), do not call
18912 connection_finished_flushing(). Should fix bug 451:
18913 "connection_stop_writing: Assertion conn->write_event failed"
18914 Bugfix on 0.1.2.7-alpha.
18915 - Fix possible segfaults in functions called from
18916 rend_process_relay_cell().
18918 o Major bugfixes (hidden services):
18919 - Hidden services were choosing introduction points uniquely by
18920 hexdigest, but when constructing the hidden service descriptor
18921 they merely wrote the (potentially ambiguous) nickname.
18922 - Clients now use the v2 intro format for hidden service
18923 connections: they specify their chosen rendezvous point by identity
18924 digest rather than by (potentially ambiguous) nickname. These
18925 changes could speed up hidden service connections dramatically.
18927 o Major bugfixes (other):
18928 - Stop publishing a new server descriptor just because we get a
18929 HUP signal. This led (in a roundabout way) to some servers getting
18930 dropped from the networkstatus lists for a few hours each day.
18931 - When looking for a circuit to cannibalize, consider family as well
18932 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
18933 circuit cannibalization).
18934 - When a router wasn't listed in a new networkstatus, we were leaving
18935 the flags for that router alone -- meaning it remained Named,
18936 Running, etc -- even though absence from the networkstatus means
18937 that it shouldn't be considered to exist at all anymore. Now we
18938 clear all the flags for routers that fall out of the networkstatus
18939 consensus. Fixes bug 529.
18942 - Don't try to access (or alter) the state file when running
18943 --list-fingerprint or --verify-config or --hash-password. Resolves
18945 - When generating information telling us how to extend to a given
18946 router, do not try to include the nickname if it is
18947 absent. Resolves bug 467.
18948 - Fix a user-triggerable segfault in expand_filename(). (There isn't
18949 a way to trigger this remotely.)
18950 - When sending a status event to the controller telling it that an
18951 OR address is reachable, set the port correctly. (Previously we
18952 were reporting the dir port.)
18953 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
18954 command. Bugfix on 0.1.2.17.
18955 - When loading bandwidth history, do not believe any information in
18956 the future. Fixes bug 434.
18957 - When loading entry guard information, do not believe any information
18959 - When we have our clock set far in the future and generate an
18960 onion key, then re-set our clock to be correct, we should not stop
18961 the onion key from getting rotated.
18962 - On some platforms, accept() can return a broken address. Detect
18963 this more quietly, and deal accordingly. Fixes bug 483.
18964 - It's not actually an error to find a non-pending entry in the DNS
18965 cache when canceling a pending resolve. Don't log unless stuff
18966 is fishy. Resolves bug 463.
18967 - Don't reset trusted dir server list when we set a configuration
18968 option. Patch from Robert Hogan.
18971 Changes in version 0.1.2.17 - 2007-08-30
18972 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
18973 X bundles. Vidalia 0.0.14 makes authentication required for the
18974 ControlPort in the default configuration, which addresses important
18975 security risks. Everybody who uses Vidalia (or another controller)
18978 In addition, this Tor update fixes major load balancing problems with
18979 path selection, which should speed things up a lot once many people
18982 o Major bugfixes (security):
18983 - We removed support for the old (v0) control protocol. It has been
18984 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
18985 become more of a headache than it's worth.
18987 o Major bugfixes (load balancing):
18988 - When choosing nodes for non-guard positions, weight guards
18989 proportionally less, since they already have enough load. Patch
18991 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
18992 will allow fast Tor servers to get more attention.
18993 - When we're upgrading from an old Tor version, forget our current
18994 guards and pick new ones according to the new weightings. These
18995 three load balancing patches could raise effective network capacity
18996 by a factor of four. Thanks to Mike Perry for measurements.
18998 o Major bugfixes (stream expiration):
18999 - Expire not-yet-successful application streams in all cases if
19000 they've been around longer than SocksTimeout. Right now there are
19001 some cases where the stream will live forever, demanding a new
19002 circuit every 15 seconds. Fixes bug 454; reported by lodger.
19004 o Minor features (controller):
19005 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
19006 is valid before any authentication has been received. It tells
19007 a controller what kind of authentication is expected, and what
19008 protocol is spoken. Implements proposal 119.
19010 o Minor bugfixes (performance):
19011 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
19012 greatly speeding up loading cached-routers from disk on startup.
19013 - Disable sentinel-based debugging for buffer code: we squashed all
19014 the bugs that this was supposed to detect a long time ago, and now
19015 its only effect is to change our buffer sizes from nice powers of
19016 two (which platform mallocs tend to like) to values slightly over
19017 powers of two (which make some platform mallocs sad).
19019 o Minor bugfixes (misc):
19020 - If exit bandwidth ever exceeds one third of total bandwidth, then
19021 use the correct formula to weight exit nodes when choosing paths.
19022 Based on patch from Mike Perry.
19023 - Choose perfectly fairly among routers when choosing by bandwidth and
19024 weighting by fraction of bandwidth provided by exits. Previously, we
19025 would choose with only approximate fairness, and correct ourselves
19026 if we ran off the end of the list.
19027 - If we require CookieAuthentication but we fail to write the
19028 cookie file, we would warn but not exit, and end up in a state
19029 where no controller could authenticate. Now we exit.
19030 - If we require CookieAuthentication, stop generating a new cookie
19031 every time we change any piece of our config.
19032 - Refuse to start with certain directory authority keys, and
19033 encourage people using them to stop.
19034 - Terminate multi-line control events properly. Original patch
19036 - Fix a minor memory leak when we fail to find enough suitable
19037 servers to choose a circuit.
19038 - Stop leaking part of the descriptor when we run into a particularly
19039 unparseable piece of it.
19042 Changes in version 0.1.2.16 - 2007-08-01
19043 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
19044 remote attacker in certain situations to rewrite the user's torrc
19045 configuration file. This can completely compromise anonymity of users
19046 in most configurations, including those running the Vidalia bundles,
19047 TorK, etc. Or worse.
19049 o Major security fixes:
19050 - Close immediately after missing authentication on control port;
19051 do not allow multiple authentication attempts.
19054 Changes in version 0.1.2.15 - 2007-07-17
19055 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
19056 problems, fixes compilation on BSD, and fixes a variety of other
19057 bugs. Everybody should upgrade.
19059 o Major bugfixes (compilation):
19060 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
19062 o Major bugfixes (crashes):
19063 - Try even harder not to dereference the first character after
19064 an mmap(). Reported by lodger.
19065 - Fix a crash bug in directory authorities when we re-number the
19066 routerlist while inserting a new router.
19067 - When the cached-routers file is an even multiple of the page size,
19068 don't run off the end and crash. (Fixes bug 455; based on idea
19070 - Fix eventdns.c behavior on Solaris: It is critical to include
19071 orconfig.h _before_ sys/types.h, so that we can get the expected
19072 definition of _FILE_OFFSET_BITS.
19074 o Major bugfixes (security):
19075 - Fix a possible buffer overrun when using BSD natd support. Bug
19077 - When sending destroy cells from a circuit's origin, don't include
19078 the reason for tearing down the circuit. The spec says we didn't,
19079 and now we actually don't. Reported by lodger.
19080 - Keep streamids from different exits on a circuit separate. This
19081 bug may have allowed other routers on a given circuit to inject
19082 cells into streams. Reported by lodger; fixes bug 446.
19083 - If there's a never-before-connected-to guard node in our list,
19084 never choose any guards past it. This way we don't expand our
19085 guard list unless we need to.
19087 o Minor bugfixes (guard nodes):
19088 - Weight guard selection by bandwidth, so that low-bandwidth nodes
19089 don't get overused as guards.
19091 o Minor bugfixes (directory):
19092 - Correctly count the number of authorities that recommend each
19093 version. Previously, we were under-counting by 1.
19094 - Fix a potential crash bug when we load many server descriptors at
19095 once and some of them make others of them obsolete. Fixes bug 458.
19097 o Minor bugfixes (hidden services):
19098 - Stop tearing down the whole circuit when the user asks for a
19099 connection to a port that the hidden service didn't configure.
19102 o Minor bugfixes (misc):
19103 - On Windows, we were preventing other processes from reading
19104 cached-routers while Tor was running. Reported by janbar.
19105 - Fix a possible (but very unlikely) bug in picking routers by
19106 bandwidth. Add a log message to confirm that it is in fact
19107 unlikely. Patch from lodger.
19108 - Backport a couple of memory leak fixes.
19109 - Backport miscellaneous cosmetic bugfixes.
19112 Changes in version 0.1.2.14 - 2007-05-25
19113 Tor 0.1.2.14 changes the addresses of two directory authorities (this
19114 change especially affects those who serve or use hidden services),
19115 and fixes several other crash- and security-related bugs.
19117 o Directory authority changes:
19118 - Two directory authorities (moria1 and moria2) just moved to new
19119 IP addresses. This change will particularly affect those who serve
19120 or use hidden services.
19122 o Major bugfixes (crashes):
19123 - If a directory server runs out of space in the connection table
19124 as it's processing a begin_dir request, it will free the exit stream
19125 but leave it attached to the circuit, leading to unpredictable
19126 behavior. (Reported by seeess, fixes bug 425.)
19127 - Fix a bug in dirserv_remove_invalid() that would cause authorities
19128 to corrupt memory under some really unlikely scenarios.
19129 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
19130 - Avoid segfaults when reading from mmaped descriptor file. (Reported
19133 o Major bugfixes (security):
19134 - When choosing an entry guard for a circuit, avoid using guards
19135 that are in the same family as the chosen exit -- not just guards
19136 that are exactly the chosen exit. (Reported by lodger.)
19138 o Major bugfixes (resource management):
19139 - If a directory authority is down, skip it when deciding where to get
19140 networkstatus objects or descriptors. Otherwise we keep asking
19141 every 10 seconds forever. Fixes bug 384.
19142 - Count it as a failure if we fetch a valid network-status but we
19143 don't want to keep it. Otherwise we'll keep fetching it and keep
19144 not wanting to keep it. Fixes part of bug 422.
19145 - If all of our dirservers have given us bad or no networkstatuses
19146 lately, then stop hammering them once per minute even when we
19147 think they're failed. Fixes another part of bug 422.
19150 - Actually set the purpose correctly for descriptors inserted with
19151 purpose=controller.
19152 - When we have k non-v2 authorities in our DirServer config,
19153 we ignored the last k authorities in the list when updating our
19155 - Correctly back-off from requesting router descriptors that we are
19156 having a hard time downloading.
19157 - Read resolv.conf files correctly on platforms where read() returns
19158 partial results on small file reads.
19159 - Don't rebuild the entire router store every time we get 32K of
19160 routers: rebuild it when the journal gets very large, or when
19161 the gaps in the store get very large.
19164 - When routers publish SVN revisions in their router descriptors,
19165 authorities now include those versions correctly in networkstatus
19167 - Warn when using a version of libevent before 1.3b to run a server on
19168 OSX or BSD: these versions interact badly with userspace threads.
19171 Changes in version 0.1.2.13 - 2007-04-24
19172 This release features some major anonymity fixes, such as safer path
19173 selection; better client performance; faster bootstrapping, better
19174 address detection, and better DNS support for servers; write limiting as
19175 well as read limiting to make servers easier to run; and a huge pile of
19176 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
19178 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
19179 of the Freenode IRC network, remembering his patience and vision for
19180 free speech on the Internet.
19182 o Major features, client performance:
19183 - Weight directory requests by advertised bandwidth. Now we can
19184 let servers enable write limiting but still allow most clients to
19185 succeed at their directory requests. (We still ignore weights when
19186 choosing a directory authority; I hope this is a feature.)
19187 - Stop overloading exit nodes -- avoid choosing them for entry or
19188 middle hops when the total bandwidth available from non-exit nodes
19189 is much higher than the total bandwidth available from exit nodes.
19190 - Rather than waiting a fixed amount of time between retrying
19191 application connections, we wait only 10 seconds for the first,
19192 10 seconds for the second, and 15 seconds for each retry after
19193 that. Hopefully this will improve the expected user experience.
19194 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
19195 to open a stream fails; now we do in more cases. This should
19196 make clients able to find a good exit faster in some cases, since
19197 unhandleable requests will now get an error rather than timing out.
19199 o Major features, client functionality:
19200 - Implement BEGIN_DIR cells, so we can connect to a directory
19201 server via TLS to do encrypted directory requests rather than
19202 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
19203 config options if you like. For now, this feature only works if
19204 you already have a descriptor for the destination dirserver.
19205 - Add support for transparent application connections: this basically
19206 bundles the functionality of trans-proxy-tor into the Tor
19207 mainline. Now hosts with compliant pf/netfilter implementations
19208 can redirect TCP connections straight to Tor without diverting
19209 through SOCKS. (Based on patch from tup.)
19210 - Add support for using natd; this allows FreeBSDs earlier than
19211 5.1.2 to have ipfw send connections through Tor without using
19212 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
19214 o Major features, servers:
19215 - Setting up a dyndns name for your server is now optional: servers
19216 with no hostname or IP address will learn their IP address by
19217 asking the directory authorities. This code only kicks in when you
19218 would normally have exited with a "no address" error. Nothing's
19219 authenticated, so use with care.
19220 - Directory servers now spool server descriptors, v1 directories,
19221 and v2 networkstatus objects to buffers as needed rather than en
19222 masse. They also mmap the cached-routers files. These steps save
19224 - Stop requiring clients to have well-formed certificates, and stop
19225 checking nicknames in certificates. (Clients have certificates so
19226 that they can look like Tor servers, but in the future we might want
19227 to allow them to look like regular TLS clients instead. Nicknames
19228 in certificates serve no purpose other than making our protocol
19229 easier to recognize on the wire.) Implements proposal 106.
19231 o Improvements on DNS support:
19232 - Add "eventdns" asynchronous dns library originally based on code
19233 from Adam Langley. Now we can discard the old rickety dnsworker
19234 concept, and support a wider variety of DNS functions. Allows
19235 multithreaded builds on NetBSD and OpenBSD again.
19236 - Add server-side support for "reverse" DNS lookups (using PTR
19237 records so clients can determine the canonical hostname for a given
19238 IPv4 address). Only supported by servers using eventdns; servers
19239 now announce in their descriptors if they don't support eventdns.
19240 - Workaround for name servers (like Earthlink's) that hijack failing
19241 DNS requests and replace the no-such-server answer with a "helpful"
19242 redirect to an advertising-driven search portal. Also work around
19243 DNS hijackers who "helpfully" decline to hijack known-invalid
19244 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
19245 lets you turn it off.
19246 - Servers now check for the case when common DNS requests are going to
19247 wildcarded addresses (i.e. all getting the same answer), and change
19248 their exit policy to reject *:* if it's happening.
19249 - When asked to resolve a hostname, don't use non-exit servers unless
19250 requested to do so. This allows servers with broken DNS to be
19251 useful to the network.
19252 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
19253 useless IPv6 DNS resolves.
19254 - Specify and implement client-side SOCKS5 interface for reverse DNS
19255 lookups (see doc/socks-extensions.txt). Also cache them.
19256 - When we change nameservers or IP addresses, reset and re-launch
19257 our tests for DNS hijacking.
19259 o Improvements on reachability testing:
19260 - Servers send out a burst of long-range padding cells once they've
19261 established that they're reachable. Spread them over 4 circuits,
19262 so hopefully a few will be fast. This exercises bandwidth and
19263 bootstraps them into the directory more quickly.
19264 - When we find our DirPort to be reachable, publish a new descriptor
19265 so we'll tell the world (reported by pnx).
19266 - Directory authorities now only decide that routers are reachable
19267 if their identity keys are as expected.
19268 - Do DirPort reachability tests less often, since a single test
19269 chews through many circuits before giving up.
19270 - Avoid some false positives during reachability testing: don't try
19271 to test via a server that's on the same /24 network as us.
19272 - Start publishing one minute or so after we find our ORPort
19273 to be reachable. This will help reduce the number of descriptors
19274 we have for ourselves floating around, since it's quite likely
19275 other things (e.g. DirPort) will change during that minute too.
19276 - Routers no longer try to rebuild long-term connections to directory
19277 authorities, and directory authorities no longer try to rebuild
19278 long-term connections to all servers. We still don't hang up
19279 connections in these two cases though -- we need to look at it
19280 more carefully to avoid flapping, and we likely need to wait til
19281 0.1.1.x is obsolete.
19283 o Improvements on rate limiting:
19284 - Enable write limiting as well as read limiting. Now we sacrifice
19285 capacity if we're pushing out lots of directory traffic, rather
19286 than overrunning the user's intended bandwidth limits.
19287 - Include TLS overhead when counting bandwidth usage; previously, we
19288 would count only the bytes sent over TLS, but not the bytes used
19290 - Servers decline directory requests much more aggressively when
19291 they're low on bandwidth. Otherwise they end up queueing more and
19292 more directory responses, which can't be good for latency.
19293 - But never refuse directory requests from local addresses.
19294 - Be willing to read or write on local connections (e.g. controller
19295 connections) even when the global rate limiting buckets are empty.
19296 - Flush local controller connection buffers periodically as we're
19297 writing to them, so we avoid queueing 4+ megabytes of data before
19299 - Revise and clean up the torrc.sample that we ship with; add
19300 a section for BandwidthRate and BandwidthBurst.
19302 o Major features, NT services:
19303 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
19304 command-line flag so that admins can override the default by saying
19305 "tor --service install --user "SomeUser"". This will not affect
19306 existing installed services. Also, warn the user that the service
19307 will look for its configuration file in the service user's
19308 %appdata% directory. (We can't do the "hardwire the user's appdata
19309 directory" trick any more, since we may not have read access to that
19311 - Support running the Tor service with a torrc not in the same
19312 directory as tor.exe and default to using the torrc located in
19313 the %appdata%\Tor\ of the user who installed the service. Patch
19315 - Add an --ignore-missing-torrc command-line option so that we can
19316 get the "use sensible defaults if the configuration file doesn't
19317 exist" behavior even when specifying a torrc location on the
19319 - When stopping an NT service, wait up to 10 sec for it to actually
19320 stop. (Patch from Matt Edman; resolves bug 295.)
19322 o Directory authority improvements:
19323 - Stop letting hibernating or obsolete servers affect uptime and
19325 - Stop listing hibernating servers in the v1 directory.
19326 - Authorities no longer recommend exits as guards if this would shift
19327 too much load to the exit nodes.
19328 - Authorities now specify server versions in networkstatus. This adds
19329 about 2% to the size of compressed networkstatus docs, and allows
19330 clients to tell which servers support BEGIN_DIR and which don't.
19331 The implementation is forward-compatible with a proposed future
19332 protocol version scheme not tied to Tor versions.
19333 - DirServer configuration lines now have an orport= option so
19334 clients can open encrypted tunnels to the authorities without
19335 having downloaded their descriptors yet. Enabled for moria1,
19336 moria2, tor26, and lefkada now in the default configuration.
19337 - Add a BadDirectory flag to network status docs so that authorities
19338 can (eventually) tell clients about caches they believe to be
19339 broken. Not used yet.
19340 - Allow authorities to list nodes as bad exits in their
19341 approved-routers file by fingerprint or by address. If most
19342 authorities set a BadExit flag for a server, clients don't think
19343 of it as a general-purpose exit. Clients only consider authorities
19344 that advertise themselves as listing bad exits.
19345 - Patch from Steve Hildrey: Generate network status correctly on
19346 non-versioning dirservers.
19347 - Have directory authorities allow larger amounts of drift in uptime
19348 without replacing the server descriptor: previously, a server that
19349 restarted every 30 minutes could have 48 "interesting" descriptors
19351 - Reserve the nickname "Unnamed" for routers that can't pick
19352 a hostname: any router can call itself Unnamed; directory
19353 authorities will never allocate Unnamed to any particular router;
19354 clients won't believe that any router is the canonical Unnamed.
19356 o Directory mirrors and clients:
19357 - Discard any v1 directory info that's over 1 month old (for
19358 directories) or over 1 week old (for running-routers lists).
19359 - Clients track responses with status 503 from dirservers. After a
19360 dirserver has given us a 503, we try not to use it until an hour has
19361 gone by, or until we have no dirservers that haven't given us a 503.
19362 - When we get a 503 from a directory, and we're not a server, we no
19363 longer count the failure against the total number of failures
19364 allowed for the object we're trying to download.
19365 - Prepare for servers to publish descriptors less often: never
19366 discard a descriptor simply for being too old until either it is
19367 recommended by no authorities, or until we get a better one for
19368 the same router. Make caches consider retaining old recommended
19369 routers for even longer.
19370 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
19371 headers for content, so that we can work better in the presence of
19372 caching HTTP proxies.
19373 - Stop fetching descriptors if you're not a dir mirror and you
19374 haven't tried to establish any circuits lately. (This currently
19375 causes some dangerous behavior, because when you start up again
19376 you'll use your ancient server descriptors.)
19378 o Major fixes, crashes:
19379 - Stop crashing when the controller asks us to resetconf more than
19380 one config option at once. (Vidalia 0.0.11 does this.)
19381 - Fix a longstanding obscure crash bug that could occur when we run
19382 out of DNS worker processes, if we're not using eventdns. (Resolves
19384 - Fix an assert that could trigger if a controller quickly set then
19385 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
19386 - Avoid crash when telling controller about stream-status and a
19387 stream is detached.
19388 - Avoid sending junk to controllers or segfaulting when a controller
19389 uses EVENT_NEW_DESC with verbose nicknames.
19390 - Stop triggering asserts if the controller tries to extend hidden
19391 service circuits (reported by mwenge).
19392 - If we start a server with ClientOnly 1, then set ClientOnly to 0
19393 and hup, stop triggering an assert based on an empty onion_key.
19394 - Mask out all signals in sub-threads; only the libevent signal
19395 handler should be processing them. This should prevent some crashes
19396 on some machines using pthreads. (Patch from coderman.)
19397 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
19399 o Major fixes, anonymity/security:
19400 - Automatically avoid picking more than one node from the same
19401 /16 network when constructing a circuit. Add an
19402 "EnforceDistinctSubnets" option to let people disable it if they
19403 want to operate private test networks on a single subnet.
19404 - When generating bandwidth history, round down to the nearest
19405 1k. When storing accounting data, round up to the nearest 1k.
19406 - When we're running as a server, remember when we last rotated onion
19407 keys, so that we will rotate keys once they're a week old even if
19408 we never stay up for a week ourselves.
19409 - If a client asked for a server by name, and there's a named server
19410 in our network-status but we don't have its descriptor yet, we
19411 could return an unnamed server instead.
19412 - Reject (most) attempts to use Tor circuits with length one. (If
19413 many people start using Tor as a one-hop proxy, exit nodes become
19414 a more attractive target for compromise.)
19415 - Just because your DirPort is open doesn't mean people should be
19416 able to remotely teach you about hidden service descriptors. Now
19417 only accept rendezvous posts if you've got HSAuthoritativeDir set.
19418 - Fix a potential race condition in the rpm installer. Found by
19420 - Do not log IPs with TLS failures for incoming TLS
19421 connections. (Fixes bug 382.)
19423 o Major fixes, other:
19424 - If our system clock jumps back in time, don't publish a negative
19425 uptime in the descriptor.
19426 - When we start during an accounting interval before it's time to wake
19427 up, remember to wake up at the correct time. (May fix bug 342.)
19428 - Previously, we would cache up to 16 old networkstatus documents
19429 indefinitely, if they came from nontrusted authorities. Now we
19430 discard them if they are more than 10 days old.
19431 - When we have a state file we cannot parse, tell the user and
19432 move it aside. Now we avoid situations where the user starts
19433 Tor in 1904, Tor writes a state file with that timestamp in it,
19434 the user fixes her clock, and Tor refuses to start.
19435 - Publish a new descriptor after we hup/reload. This is important
19436 if our config has changed such that we'll want to start advertising
19437 our DirPort now, etc.
19438 - If we are using an exit enclave and we can't connect, e.g. because
19439 its webserver is misconfigured to not listen on localhost, then
19440 back off and try connecting from somewhere else before we fail.
19442 o New config options or behaviors:
19443 - When EntryNodes are configured, rebuild the guard list to contain,
19444 in order: the EntryNodes that were guards before; the rest of the
19445 EntryNodes; the nodes that were guards before.
19446 - Do not warn when individual nodes in the configuration's EntryNodes,
19447 ExitNodes, etc are down: warn only when all possible nodes
19448 are down. (Fixes bug 348.)
19449 - Put a lower-bound on MaxAdvertisedBandwidth.
19450 - Start using the state file to store bandwidth accounting data:
19451 the bw_accounting file is now obsolete. We'll keep generating it
19452 for a while for people who are still using 0.1.2.4-alpha.
19453 - Try to batch changes to the state file so that we do as few
19454 disk writes as possible while still storing important things in
19456 - The state file and the bw_accounting file get saved less often when
19457 the AvoidDiskWrites config option is set.
19458 - Make PIDFile work on Windows.
19459 - Add internal descriptions for a bunch of configuration options:
19460 accessible via controller interface and in comments in saved
19462 - Reject *:563 (NNTPS) in the default exit policy. We already reject
19463 NNTP by default, so this seems like a sensible addition.
19464 - Clients now reject hostnames with invalid characters. This should
19465 avoid some inadvertent info leaks. Add an option
19466 AllowNonRFC953Hostnames to disable this behavior, in case somebody
19467 is running a private network with hosts called @, !, and #.
19468 - Check for addresses with invalid characters at the exit as well,
19469 and warn less verbosely when they fail. You can override this by
19470 setting ServerDNSAllowNonRFC953Addresses to 1.
19471 - Remove some options that have been deprecated since at least
19472 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
19473 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
19474 to set log options. Mark PathlenCoinWeight as obsolete.
19475 - Stop accepting certain malformed ports in configured exit policies.
19476 - When the user uses bad syntax in the Log config line, stop
19477 suggesting other bad syntax as a replacement.
19478 - Add new config option "ResolvConf" to let the server operator
19479 choose an alternate resolve.conf file when using eventdns.
19480 - If one of our entry guards is on the ExcludeNodes list, or the
19481 directory authorities don't think it's a good guard, treat it as
19482 if it were unlisted: stop using it as a guard, and throw it off
19483 the guards list if it stays that way for a long time.
19484 - Allow directory authorities to be marked separately as authorities
19485 for the v1 directory protocol, the v2 directory protocol, and
19486 as hidden service directories, to make it easier to retire old
19487 authorities. V1 authorities should set "HSAuthoritativeDir 1"
19488 to continue being hidden service authorities too.
19489 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
19490 - Make TrackExitHosts case-insensitive, and fix the behavior of
19491 ".suffix" TrackExitHosts items to avoid matching in the middle of
19493 - New DirPort behavior: if you have your dirport set, you download
19494 descriptors aggressively like a directory mirror, whether or not
19495 your ORPort is set.
19498 - Create a new file ReleaseNotes which was the old ChangeLog. The
19499 new ChangeLog file now includes the notes for all development
19501 - Add a new address-spec.txt document to describe our special-case
19502 addresses: .exit, .onion, and .noconnnect.
19503 - Fork the v1 directory protocol into its own spec document,
19504 and mark dir-spec.txt as the currently correct (v2) spec.
19506 o Packaging, porting, and contrib
19507 - "tor --verify-config" now exits with -1(255) or 0 depending on
19508 whether the config options are bad or good.
19509 - The Debian package now uses --verify-config when (re)starting,
19510 to distinguish configuration errors from other errors.
19511 - Adapt a patch from goodell to let the contrib/exitlist script
19512 take arguments rather than require direct editing.
19513 - Prevent the contrib/exitlist script from printing the same
19514 result more than once.
19515 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
19516 - In the hidden service example in torrc.sample, stop recommending
19517 esoteric and discouraged hidden service options.
19518 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
19519 values before failing, and always enables eventdns.
19520 - Try to detect Windows correctly when cross-compiling.
19521 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
19522 Try to fix this in configure.in by checking for most functions
19523 before we check for libevent.
19524 - Update RPMs to require libevent 1.2.
19525 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
19526 or later. Log when we are doing this, so we can diagnose it when
19527 it fails. (Also, recommend libevent 1.1b for kqueue and
19528 win32 methods; deprecate libevent 1.0b harder; make libevent
19529 recommendation system saner.)
19530 - Build with recent (1.3+) libevents on platforms that do not
19531 define the nonstandard types "u_int8_t" and friends.
19532 - Remove architecture from OS X builds. The official builds are
19533 now universal binaries.
19534 - Run correctly on OS X platforms with case-sensitive filesystems.
19535 - Correctly set maximum connection limit on Cygwin. (This time
19537 - Start compiling on MinGW on Windows (patches from Mike Chiussi
19539 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
19540 - Finally fix the openssl warnings from newer gccs that believe that
19541 ignoring a return value is okay, but casting a return value and
19542 then ignoring it is a sign of madness.
19543 - On architectures where sizeof(int)>4, still clamp declarable
19544 bandwidth to INT32_MAX.
19546 o Minor features, controller:
19547 - Warn the user when an application uses the obsolete binary v0
19548 control protocol. We're planning to remove support for it during
19549 the next development series, so it's good to give people some
19551 - Add STREAM_BW events to report per-entry-stream bandwidth
19552 use. (Patch from Robert Hogan.)
19553 - Rate-limit SIGNEWNYM signals in response to controllers that
19554 impolitely generate them for every single stream. (Patch from
19555 mwenge; closes bug 394.)
19556 - Add a REMAP status to stream events to note that a stream's
19557 address has changed because of a cached address or a MapAddress
19559 - Make REMAP stream events have a SOURCE (cache or exit), and
19560 make them generated in every case where we get a successful
19561 connected or resolved cell.
19562 - Track reasons for OR connection failure; make these reasons
19563 available via the controller interface. (Patch from Mike Perry.)
19564 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
19565 can learn when clients are sending malformed hostnames to Tor.
19566 - Specify and implement some of the controller status events.
19567 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
19568 - Reimplement GETINFO so that info/names stays in sync with the
19570 - Implement "GETINFO fingerprint".
19571 - Implement "SETEVENTS GUARD" so controllers can get updates on
19572 entry guard status as it changes.
19573 - Make all connections to addresses of the form ".noconnect"
19574 immediately get closed. This lets application/controller combos
19575 successfully test whether they're talking to the same Tor by
19576 watching for STREAM events.
19577 - Add a REASON field to CIRC events; for backward compatibility, this
19578 field is sent only to controllers that have enabled the extended
19579 event format. Also, add additional reason codes to explain why
19580 a given circuit has been destroyed or truncated. (Patches from
19582 - Add a REMOTE_REASON field to extended CIRC events to tell the
19583 controller why a remote OR told us to close a circuit.
19584 - Stream events also now have REASON and REMOTE_REASON fields,
19585 working much like those for circuit events.
19586 - There's now a GETINFO ns/... field so that controllers can ask Tor
19587 about the current status of a router.
19588 - A new event type "NS" to inform a controller when our opinion of
19589 a router's status has changed.
19590 - Add a GETINFO events/names and GETINFO features/names so controllers
19591 can tell which events and features are supported.
19592 - A new CLEARDNSCACHE signal to allow controllers to clear the
19593 client-side DNS cache without expiring circuits.
19594 - Fix CIRC controller events so that controllers can learn the
19595 identity digests of non-Named servers used in circuit paths.
19596 - Let controllers ask for more useful identifiers for servers. Instead
19597 of learning identity digests for un-Named servers and nicknames
19598 for Named servers, the new identifiers include digest, nickname,
19599 and indication of Named status. Off by default; see control-spec.txt
19600 for more information.
19601 - Add a "getinfo address" controller command so it can display Tor's
19602 best guess to the user.
19603 - New controller event to alert the controller when our server
19604 descriptor has changed.
19605 - Give more meaningful errors on controller authentication failure.
19606 - Export the default exit policy via the control port, so controllers
19607 don't need to guess what it is / will be later.
19609 o Minor bugfixes, controller:
19610 - When creating a circuit via the controller, send a 'launched'
19611 event when we're done, so we follow the spec better.
19612 - Correct the control spec to match how the code actually responds
19613 to 'getinfo addr-mappings/*'. Reported by daejees.
19614 - The control spec described a GUARDS event, but the code
19615 implemented a GUARD event. Standardize on GUARD, but let people
19616 ask for GUARDS too. Reported by daejees.
19617 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
19618 clear the corresponding on_circuit variable, and remember later
19619 that we don't need to send a redundant CLOSED event. (Resolves part
19621 - Report events where a resolve succeeded or where we got a socks
19622 protocol error correctly, rather than calling both of them
19624 - Change reported stream target addresses to IP consistently when
19625 we finally get the IP from an exit node.
19626 - Send log messages to the controller even if they happen to be very
19628 - Flush ERR-level controller status events just like we currently
19629 flush ERR-level log events, so that a Tor shutdown doesn't prevent
19630 the controller from learning about current events.
19631 - Report the circuit number correctly in STREAM CLOSED events. Bug
19632 reported by Mike Perry.
19633 - Do not report bizarre values for results of accounting GETINFOs
19634 when the last second's write or read exceeds the allotted bandwidth.
19635 - Report "unrecognized key" rather than an empty string when the
19636 controller tries to fetch a networkstatus that doesn't exist.
19637 - When the controller does a "GETINFO network-status", tell it
19638 about even those routers whose descriptors are very old, and use
19639 long nicknames where appropriate.
19640 - Fix handling of verbose nicknames with ORCONN controller events:
19641 make them show up exactly when requested, rather than exactly when
19643 - Controller signals now work on non-Unix platforms that don't define
19644 SIGUSR1 and SIGUSR2 the way we expect.
19645 - Respond to SIGNAL command before we execute the signal, in case
19646 the signal shuts us down. Suggested by Karsten Loesing.
19647 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
19649 o Minor features, code performance:
19650 - Major performance improvement on inserting descriptors: change
19651 algorithm from O(n^2) to O(n).
19652 - Do not rotate onion key immediately after setting it for the first
19654 - Call router_have_min_dir_info half as often. (This is showing up in
19655 some profiles, but not others.)
19656 - When using GCC, make log_debug never get called at all, and its
19657 arguments never get evaluated, when no debug logs are configured.
19658 (This is showing up in some profiles, but not others.)
19659 - Statistics dumped by -USR2 now include a breakdown of public key
19660 operations, for profiling.
19661 - Make the common memory allocation path faster on machines where
19662 malloc(0) returns a pointer.
19663 - Split circuit_t into origin_circuit_t and or_circuit_t, and
19664 split connection_t into edge, or, dir, control, and base structs.
19665 These will save quite a bit of memory on busy servers, and they'll
19666 also help us track down bugs in the code and bugs in the spec.
19667 - Use OpenSSL's AES implementation on platforms where it's faster.
19668 This could save us as much as 10% CPU usage.
19670 o Minor features, descriptors and descriptor handling:
19671 - Avoid duplicate entries on MyFamily line in server descriptor.
19672 - When Tor receives a router descriptor that it asked for, but
19673 no longer wants (because it has received fresh networkstatuses
19674 in the meantime), do not warn the user. Cache the descriptor if
19675 we're a cache; drop it if we aren't.
19676 - Servers no longer ever list themselves in their "family" line,
19677 even if configured to do so. This makes it easier to configure
19678 family lists conveniently.
19680 o Minor fixes, confusing/misleading log messages:
19681 - Display correct results when reporting which versions are
19682 recommended, and how recommended they are. (Resolves bug 383.)
19683 - Inform the server operator when we decide not to advertise a
19684 DirPort due to AccountingMax enabled or a low BandwidthRate.
19685 - Only include function names in log messages for info/debug messages.
19686 For notice/warn/err, the content of the message should be clear on
19687 its own, and printing the function name only confuses users.
19688 - Remove even more protocol-related warnings from Tor server logs,
19689 such as bad TLS handshakes and malformed begin cells.
19690 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
19691 when the IP address is mapped through MapAddress to a hostname.
19692 - Fix misleading log messages: an entry guard that is "unlisted",
19693 as well as not known to be "down" (because we've never heard
19694 of it), is not therefore "up".
19696 o Minor fixes, old/obsolete behavior:
19697 - Start assuming we can use a create_fast cell if we don't know
19698 what version a router is running.
19699 - We no longer look for identity and onion keys in "identity.key" and
19700 "onion.key" -- these were replaced by secret_id_key and
19701 secret_onion_key in 0.0.8pre1.
19702 - We no longer require unrecognized directory entries to be
19704 - Drop compatibility with obsolete Tors that permit create cells
19705 to have the wrong circ_id_type.
19706 - Remove code to special-case "-cvs" ending, since it has not
19707 actually mattered since 0.0.9.
19708 - Don't re-write the fingerprint file every restart, unless it has
19711 o Minor fixes, misc client-side behavior:
19712 - Always remove expired routers and networkstatus docs before checking
19713 whether we have enough information to build circuits. (Fixes
19715 - When computing clock skew from directory HTTP headers, consider what
19716 time it was when we finished asking for the directory, not what
19718 - Make our socks5 handling more robust to broken socks clients:
19719 throw out everything waiting on the buffer in between socks
19720 handshake phases, since they can't possibly (so the theory
19721 goes) have predicted what we plan to respond to them.
19722 - Expire socks connections if they spend too long waiting for the
19723 handshake to finish. Previously we would let them sit around for
19724 days, if the connecting application didn't close them either.
19725 - And if the socks handshake hasn't started, don't send a
19726 "DNS resolve socks failed" handshake reply; just close it.
19727 - If the user asks to use invalid exit nodes, be willing to use
19729 - Track unreachable entry guards correctly: don't conflate
19730 'unreachable by us right now' with 'listed as down by the directory
19731 authorities'. With the old code, if a guard was unreachable by us
19732 but listed as running, it would clog our guard list forever.
19733 - Behave correctly in case we ever have a network with more than
19734 2GB/s total advertised capacity.
19735 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
19736 - Fix a memory leak when we ask for "all" networkstatuses and we
19737 get one we don't recognize.
19740 Changes in version 0.1.1.26 - 2006-12-14
19741 o Security bugfixes:
19742 - Stop sending the HttpProxyAuthenticator string to directory
19743 servers when directory connections are tunnelled through Tor.
19744 - Clients no longer store bandwidth history in the state file.
19745 - Do not log introduction points for hidden services if SafeLogging
19749 - Fix an assert failure when a directory authority sets
19750 AuthDirRejectUnlisted and then receives a descriptor from an
19751 unlisted router (reported by seeess).
19754 Changes in version 0.1.1.25 - 2006-11-04
19756 - When a client asks us to resolve (rather than connect to)
19757 an address, and we have a cached answer, give them the cached
19758 answer. Previously, we would give them no answer at all.
19759 - We were building exactly the wrong circuits when we predict
19760 hidden service requirements, meaning Tor would have to build all
19761 its circuits on demand.
19762 - If none of our live entry guards have a high uptime, but we
19763 require a guard with a high uptime, try adding a new guard before
19764 we give up on the requirement. This patch should make long-lived
19765 connections more stable on average.
19766 - When testing reachability of our DirPort, don't launch new
19767 tests when there's already one in progress -- unreachable
19768 servers were stacking up dozens of testing streams.
19770 o Security bugfixes:
19771 - When the user sends a NEWNYM signal, clear the client-side DNS
19772 cache too. Otherwise we continue to act on previous information.
19775 - Avoid a memory corruption bug when creating a hash table for
19777 - Avoid possibility of controller-triggered crash when misusing
19778 certain commands from a v0 controller on platforms that do not
19779 handle printf("%s",NULL) gracefully.
19780 - Avoid infinite loop on unexpected controller input.
19781 - Don't log spurious warnings when we see a circuit close reason we
19782 don't recognize; it's probably just from a newer version of Tor.
19783 - Add Vidalia to the OS X uninstaller script, so when we uninstall
19784 Tor/Privoxy we also uninstall Vidalia.
19787 Changes in version 0.1.1.24 - 2006-09-29
19789 - Allow really slow clients to not hang up five minutes into their
19790 directory downloads (suggested by Adam J. Richter).
19791 - Fix major performance regression from 0.1.0.x: instead of checking
19792 whether we have enough directory information every time we want to
19793 do something, only check when the directory information has changed.
19794 This should improve client CPU usage by 25-50%.
19795 - Don't crash if, after a server has been running for a while,
19796 it can't resolve its hostname.
19797 - When a client asks us to resolve (not connect to) an address,
19798 and we have a cached answer, give them the cached answer.
19799 Previously, we would give them no answer at all.
19802 - Allow Tor to start when RunAsDaemon is set but no logs are set.
19803 - Don't crash when the controller receives a third argument to an
19804 "extendcircuit" request.
19805 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
19806 response; fix error code when "getinfo dir/status/" fails.
19807 - Fix configure.in to not produce broken configure files with
19808 more recent versions of autoconf. Thanks to Clint for his auto*
19810 - Fix security bug on NetBSD that could allow someone to force
19811 uninitialized RAM to be sent to a server's DNS resolver. This
19812 only affects NetBSD and other platforms that do not bounds-check
19814 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
19815 methods: these are known to be buggy.
19816 - If we're a directory mirror and we ask for "all" network status
19817 documents, we would discard status documents from authorities
19818 we don't recognize.
19821 Changes in version 0.1.1.23 - 2006-07-30
19823 - Fast Tor servers, especially exit nodes, were triggering asserts
19824 due to a bug in handling the list of pending DNS resolves. Some
19825 bugs still remain here; we're hunting them.
19826 - Entry guards could crash clients by sending unexpected input.
19827 - More fixes on reachability testing: if you find yourself reachable,
19828 then don't ever make any client requests (so you stop predicting
19829 circuits), then hup or have your clock jump, then later your IP
19830 changes, you won't think circuits are working, so you won't try to
19831 test reachability, so you won't publish.
19834 - Avoid a crash if the controller does a resetconf firewallports
19835 and then a setconf fascistfirewall=1.
19836 - Avoid an integer underflow when the dir authority decides whether
19837 a router is stable: we might wrongly label it stable, and compute
19838 a slightly wrong median stability, when a descriptor is published
19840 - Fix a place where we might trigger an assert if we can't build our
19841 own server descriptor yet.
19844 Changes in version 0.1.1.22 - 2006-07-05
19846 - Fix a big bug that was causing servers to not find themselves
19847 reachable if they changed IP addresses. Since only 0.1.1.22+
19848 servers can do reachability testing correctly, now we automatically
19849 make sure to test via one of these.
19850 - Fix to allow clients and mirrors to learn directory info from
19851 descriptor downloads that get cut off partway through.
19852 - Directory authorities had a bug in deciding if a newly published
19853 descriptor was novel enough to make everybody want a copy -- a few
19854 servers seem to be publishing new descriptors many times a minute.
19856 - Fix a rare bug that was causing some servers to complain about
19857 "closing wedged cpuworkers" and skip some circuit create requests.
19858 - Make the Exit flag in directory status documents actually work.
19861 Changes in version 0.1.1.21 - 2006-06-10
19862 o Crash and assert fixes from 0.1.1.20:
19863 - Fix a rare crash on Tor servers that have enabled hibernation.
19864 - Fix a seg fault on startup for Tor networks that use only one
19865 directory authority.
19866 - Fix an assert from a race condition that occurs on Tor servers
19867 while exiting, where various threads are trying to log that they're
19868 exiting, and delete the logs, at the same time.
19869 - Make our unit tests pass again on certain obscure platforms.
19872 - Add support for building SUSE RPM packages.
19873 - Speed up initial bootstrapping for clients: if we are making our
19874 first ever connection to any entry guard, then don't mark it down
19876 - When only one Tor server in the network is labelled as a guard,
19877 and we've already picked him, we would cycle endlessly picking him
19878 again, being unhappy about it, etc. Now we specifically exclude
19879 current guards when picking a new guard.
19880 - Servers send create cells more reliably after the TLS connection
19881 is established: we were sometimes forgetting to send half of them
19882 when we had more than one pending.
19883 - If we get a create cell that asks us to extend somewhere, but the
19884 Tor server there doesn't match the expected digest, we now send
19885 a destroy cell back, rather than silently doing nothing.
19886 - Make options->RedirectExit work again.
19887 - Make cookie authentication for the controller work again.
19888 - Stop being picky about unusual characters in the arguments to
19889 mapaddress. It's none of our business.
19890 - Add a new config option "TestVia" that lets you specify preferred
19891 middle hops to use for test circuits. Perhaps this will let me
19892 debug the reachability problems better.
19894 o Log / documentation fixes:
19895 - If we're a server and some peer has a broken TLS certificate, don't
19896 log about it unless ProtocolWarnings is set, i.e., we want to hear
19897 about protocol violations by others.
19898 - Fix spelling of VirtualAddrNetwork in man page.
19899 - Add a better explanation at the top of the autogenerated torrc file
19900 about what happened to our old torrc.
19903 Changes in version 0.1.1.20 - 2006-05-23
19904 o Crash and assert fixes from 0.1.0.17:
19905 - Fix assert bug in close_logs() on exit: when we close and delete
19906 logs, remove them all from the global "logfiles" list.
19907 - Fix an assert error when we're out of space in the connection_list
19908 and we try to post a hidden service descriptor (reported by Peter
19910 - Fix a rare assert error when we've tried all intro points for
19911 a hidden service and we try fetching the service descriptor again:
19912 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
19913 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
19914 out and refuse the setconf if it would fail.
19915 - If you specify a relative torrc path and you set RunAsDaemon in
19916 your torrc, then it chdir()'s to the new directory. If you then
19917 HUP, it tries to load the new torrc location, fails, and exits.
19918 The fix: no longer allow a relative path to torrc when using -f.
19919 - Check for integer overflows in more places, when adding elements
19920 to smartlists. This could possibly prevent a buffer overflow
19921 on malicious huge inputs.
19923 o Security fixes, major:
19924 - When we're printing strings from the network, don't try to print
19925 non-printable characters. Now we're safer against shell escape
19926 sequence exploits, and also against attacks to fool users into
19927 misreading their logs.
19928 - Implement entry guards: automatically choose a handful of entry
19929 nodes and stick with them for all circuits. Only pick new guards
19930 when the ones you have are unsuitable, and if the old guards
19931 become suitable again, switch back. This will increase security
19932 dramatically against certain end-point attacks. The EntryNodes
19933 config option now provides some hints about which entry guards you
19934 want to use most; and StrictEntryNodes means to only use those.
19935 Fixes CVE-2006-0414.
19936 - Implement exit enclaves: if we know an IP address for the
19937 destination, and there's a running Tor server at that address
19938 which allows exit to the destination, then extend the circuit to
19939 that exit first. This provides end-to-end encryption and end-to-end
19940 authentication. Also, if the user wants a .exit address or enclave,
19941 use 4 hops rather than 3, and cannibalize a general circ for it
19943 - Obey our firewall options more faithfully:
19944 . If we can't get to a dirserver directly, try going via Tor.
19945 . Don't ever try to connect (as a client) to a place our
19946 firewall options forbid.
19947 . If we specify a proxy and also firewall options, obey the
19948 firewall options even when we're using the proxy: some proxies
19949 can only proxy to certain destinations.
19950 - Make clients regenerate their keys when their IP address changes.
19951 - For the OS X package's modified privoxy config file, comment
19952 out the "logfile" line so we don't log everything passed
19954 - Our TLS handshakes were generating a single public/private
19955 keypair for the TLS context, rather than making a new one for
19956 each new connection. Oops. (But we were still rotating them
19957 periodically, so it's not so bad.)
19958 - When we were cannibalizing a circuit with a particular exit
19959 node in mind, we weren't checking to see if that exit node was
19960 already present earlier in the circuit. Now we are.
19961 - Require server descriptors to list IPv4 addresses -- hostnames
19962 are no longer allowed. This also fixes potential vulnerabilities
19963 to servers providing hostnames as their address and then
19964 preferentially resolving them so they can partition users.
19965 - Our logic to decide if the OR we connected to was the right guy
19966 was brittle and maybe open to a mitm for invalid routers.
19968 o Security fixes, minor:
19969 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
19970 Ian Goldberg can prove things about our handshake protocol more
19972 - Make directory authorities generate a separate "guard" flag to
19973 mean "would make a good entry guard". Clients now honor the
19974 is_guard flag rather than looking at is_fast or is_stable.
19975 - Try to list MyFamily elements by key, not by nickname, and warn
19976 if we've not heard of a server.
19977 - Start using RAND_bytes rather than RAND_pseudo_bytes from
19978 OpenSSL. Also, reseed our entropy every hour, not just at
19979 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
19980 - Refuse server descriptors where the fingerprint line doesn't match
19981 the included identity key. Tor doesn't care, but other apps (and
19982 humans) might actually be trusting the fingerprint line.
19983 - We used to kill the circuit when we receive a relay command we
19984 don't recognize. Now we just drop that cell.
19985 - Fix a bug found by Lasse Overlier: when we were making internal
19986 circuits (intended to be cannibalized later for rendezvous and
19987 introduction circuits), we were picking them so that they had
19988 useful exit nodes. There was no need for this, and it actually
19989 aids some statistical attacks.
19990 - Start treating internal circuits and exit circuits separately.
19991 It's important to keep them separate because internal circuits
19992 have their last hops picked like middle hops, rather than like
19993 exit hops. So exiting on them will break the user's expectations.
19994 - Fix a possible way to DoS dirservers.
19995 - When the client asked for a rendezvous port that the hidden
19996 service didn't want to provide, we were sending an IP address
19997 back along with the end cell. Fortunately, it was zero. But stop
20000 o Packaging improvements:
20001 - Implement --with-libevent-dir option to ./configure. Improve
20002 search techniques to find libevent, and use those for openssl too.
20003 - Fix a couple of bugs in OpenSSL detection. Deal better when
20004 there are multiple SSLs installed with different versions.
20005 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
20006 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
20008 - Make unit tests (and other invocations that aren't the real Tor)
20009 run without launching listeners, creating subdirectories, and so on.
20010 - The OS X installer was adding a symlink for tor_resolve but
20011 the binary was called tor-resolve (reported by Thomas Hardly).
20012 - Now we can target arch and OS in rpm builds (contributed by
20013 Phobos). Also make the resulting dist-rpm filename match the
20015 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
20016 if you log to syslog and want something other than LOG_DAEMON.
20017 - Fix the torify (tsocks) config file to not use Tor for localhost
20019 - Start shipping socks-extensions.txt, tor-doc-unix.html,
20020 tor-doc-server.html, and stylesheet.css in the tarball.
20021 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
20022 They are useless now.
20023 - Add Peter Palfrader's contributed check-tor script. It lets you
20024 easily check whether a given server (referenced by nickname)
20025 is reachable by you.
20026 - Add BSD-style contributed startup script "rc.subr" from Peter
20029 o Directory improvements -- new directory protocol:
20030 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
20031 - Authorities and caches publish individual descriptors (by
20032 digest, by fingerprint, by "all", and by "tell me yours").
20033 - Clients don't download or use the old directory anymore. Now they
20034 download network-statuses from the directory authorities, and
20035 fetch individual server descriptors as needed from mirrors.
20036 - Clients don't download descriptors of non-running servers.
20037 - Download descriptors by digest, not by fingerprint. Caches try to
20038 download all listed digests from authorities; clients try to
20039 download "best" digests from caches. This avoids partitioning
20040 and isolating attacks better.
20041 - Only upload a new server descriptor when options change, 18
20042 hours have passed, uptime is reset, or bandwidth changes a lot.
20043 - Directory authorities silently throw away new descriptors that
20044 haven't changed much if the timestamps are similar. We do this to
20045 tolerate older Tor servers that upload a new descriptor every 15
20046 minutes. (It seemed like a good idea at the time.)
20047 - Clients choose directory servers from the network status lists,
20048 not from their internal list of router descriptors. Now they can
20049 go to caches directly rather than needing to go to authorities
20050 to bootstrap the first set of descriptors.
20051 - When picking a random directory, prefer non-authorities if any
20053 - Add a new flag to network-status indicating whether the server
20054 can answer v2 directory requests too.
20055 - Directory mirrors now cache up to 16 unrecognized network-status
20056 docs, so new directory authorities will be cached too.
20057 - Stop parsing, storing, or using running-routers output (but
20058 mirrors still cache and serve it).
20059 - Clients consider a threshold of "versioning" directory authorities
20060 before deciding whether to warn the user that he's obsolete.
20061 - Authorities publish separate sorted lists of recommended versions
20062 for clients and for servers.
20063 - Change DirServers config line to note which dirs are v1 authorities.
20064 - Put nicknames on the DirServer line, so we can refer to them
20065 without requiring all our users to memorize their IP addresses.
20066 - Remove option when getting directory cache to see whether they
20067 support running-routers; they all do now. Replace it with one
20068 to see whether caches support v2 stuff.
20069 - Stop listing down or invalid nodes in the v1 directory. This
20070 reduces its bulk by about 1/3, and reduces load on mirrors.
20071 - Mirrors no longer cache the v1 directory as often.
20072 - If we as a directory mirror don't know of any v1 directory
20073 authorities, then don't try to cache any v1 directories.
20075 o Other directory improvements:
20076 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
20077 fifth authoritative directory servers.
20078 - Directory authorities no longer require an open connection from
20079 a server to consider him "reachable". We need this change because
20080 when we add new directory authorities, old servers won't know not
20081 to hang up on them.
20082 - Dir authorities now do their own external reachability testing
20083 of each server, and only list as running the ones they found to
20084 be reachable. We also send back warnings to the server's logs if
20085 it uploads a descriptor that we already believe is unreachable.
20086 - Spread the directory authorities' reachability testing over the
20087 entire testing interval, so we don't try to do 500 TLS's at once
20089 - Make the "stable" router flag in network-status be the median of
20090 the uptimes of running valid servers, and make clients pay
20091 attention to the network-status flags. Thus the cutoff adapts
20092 to the stability of the network as a whole, making IRC, IM, etc
20093 connections more reliable.
20094 - Make the v2 dir's "Fast" flag based on relative capacity, just
20095 like "Stable" is based on median uptime. Name everything in the
20096 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
20097 - Retry directory requests if we fail to get an answer we like
20098 from a given dirserver (we were retrying before, but only if
20099 we fail to connect).
20100 - Return a robots.txt on our dirport to discourage google indexing.
20102 o Controller protocol improvements:
20103 - Revised controller protocol (version 1) that uses ascii rather
20104 than binary: tor/doc/control-spec.txt. Add supporting libraries
20105 in python and java and c# so you can use the controller from your
20106 applications without caring how our protocol works.
20107 - Allow the DEBUG controller event to work again. Mark certain log
20108 entries as "don't tell this to controllers", so we avoid cycles.
20109 - New controller function "getinfo accounting", to ask how
20110 many bytes we've used in this time period.
20111 - Add a "resetconf" command so you can set config options like
20112 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
20113 a config option in the torrc with no value, then it clears it
20114 entirely (rather than setting it to its default).
20115 - Add a "getinfo config-file" to tell us where torrc is. Also
20116 expose guard nodes, config options/names.
20117 - Add a "quit" command (when when using the controller manually).
20118 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
20119 stop using any currently-dirty circuits for new streams, so we
20120 don't link new actions to old actions. This also occurs on HUP
20121 or "signal reload".
20122 - If we would close a stream early (e.g. it asks for a .exit that
20123 we know would refuse it) but the LeaveStreamsUnattached config
20124 option is set by the controller, then don't close it.
20125 - Add a new controller event type "authdir_newdescs" that allows
20126 controllers to get all server descriptors that were uploaded to
20127 a router in its role as directory authority.
20128 - New controller option "getinfo desc/all-recent" to fetch the
20129 latest server descriptor for every router that Tor knows about.
20130 - Fix the controller's "attachstream 0" command to treat conn like
20131 it just connected, doing address remapping, handling .exit and
20132 .onion idioms, and so on. Now we're more uniform in making sure
20133 that the controller hears about new and closing connections.
20134 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
20135 the controller. Also, rotate dns and cpu workers if the controller
20136 changes options that will affect them; and initialize the dns
20137 worker cache tree whether or not we start out as a server.
20138 - Add a new circuit purpose 'controller' to let the controller ask
20139 for a circuit that Tor won't try to use. Extend the "extendcircuit"
20140 controller command to let you specify the purpose if you're starting
20141 a new circuit. Add a new "setcircuitpurpose" controller command to
20142 let you change a circuit's purpose after it's been created.
20143 - Let the controller ask for "getinfo dir/server/foo" so it can ask
20144 directly rather than connecting to the dir port. "getinfo
20145 dir/status/foo" also works, but currently only if your DirPort
20147 - Let the controller tell us about certain router descriptors
20148 that it doesn't want Tor to use in circuits. Implement
20149 "setrouterpurpose" and modify "+postdescriptor" to do this.
20150 - If the controller's *setconf commands fail, collect an error
20151 message in a string and hand it back to the controller -- don't
20152 just tell them to go read their logs.
20154 o Scalability, resource management, and performance:
20155 - Fix a major load balance bug: we were round-robin reading in 16 KB
20156 chunks, and servers with bandwidthrate of 20 KB, while downloading
20157 a 600 KB directory, would starve their other connections. Now we
20158 try to be a bit more fair.
20159 - Be more conservative about whether to advertise our DirPort.
20160 The main change is to not advertise if we're running at capacity
20161 and either a) we could hibernate ever or b) our capacity is low
20162 and we're using a default DirPort.
20163 - We weren't cannibalizing circuits correctly for
20164 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
20165 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
20166 build those from scratch. This should make hidden services faster.
20167 - Predict required circuits better, with an eye toward making hidden
20168 services faster on the service end.
20169 - Compress exit policies even more: look for duplicate lines and
20171 - Generate 18.0.0.0/8 address policy format in descs when we can;
20172 warn when the mask is not reducible to a bit-prefix.
20173 - There used to be two ways to specify your listening ports in a
20174 server descriptor: on the "router" line and with a separate "ports"
20175 line. Remove support for the "ports" line.
20176 - Reduce memory requirements in our structs by changing the order
20177 of fields. Replace balanced trees with hash tables. Inline
20178 bottleneck smartlist functions. Add a "Map from digest to void*"
20179 abstraction so we can do less hex encoding/decoding, and use it
20180 in router_get_by_digest(). Many other CPU and memory improvements.
20181 - Allow tor_gzip_uncompress to extract as much as possible from
20182 truncated compressed data. Try to extract as many
20183 descriptors as possible from truncated http responses (when
20184 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
20185 - Make circ->onionskin a pointer, not a static array. moria2 was using
20186 125000 circuit_t's after it had been up for a few weeks, which
20187 translates to 20+ megs of wasted space.
20188 - The private half of our EDH handshake keys are now chosen out
20189 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
20190 - Stop doing the complex voodoo overkill checking for insecure
20191 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
20192 - Do round-robin writes for TLS of at most 16 kB per write. This
20193 might be more fair on loaded Tor servers.
20194 - Do not use unaligned memory access on alpha, mips, or mipsel.
20195 It *works*, but is very slow, so we treat them as if it doesn't.
20197 o Other bugfixes and improvements:
20198 - Start storing useful information to $DATADIR/state, so we can
20199 remember things across invocations of Tor. Retain unrecognized
20200 lines so we can be forward-compatible, and write a TorVersion line
20201 so we can be backward-compatible.
20202 - If ORPort is set, Address is not explicitly set, and our hostname
20203 resolves to a private IP address, try to use an interface address
20204 if it has a public address. Now Windows machines that think of
20205 themselves as localhost can guess their address.
20206 - Regenerate our local descriptor if it's dirty and we try to use
20207 it locally (e.g. if it changes during reachability detection).
20208 This was causing some Tor servers to keep publishing the same
20209 initial descriptor forever.
20210 - Tor servers with dynamic IP addresses were needing to wait 18
20211 hours before they could start doing reachability testing using
20212 the new IP address and ports. This is because they were using
20213 the internal descriptor to learn what to test, yet they were only
20214 rebuilding the descriptor once they decided they were reachable.
20215 - It turns out we couldn't bootstrap a network since we added
20216 reachability detection in 0.1.0.1-rc. Good thing the Tor network
20217 has never gone down. Add an AssumeReachable config option to let
20218 servers and authorities bootstrap. When we're trying to build a
20219 high-uptime or high-bandwidth circuit but there aren't enough
20220 suitable servers, try being less picky rather than simply failing.
20221 - Newly bootstrapped Tor networks couldn't establish hidden service
20222 circuits until they had nodes with high uptime. Be more tolerant.
20223 - Really busy servers were keeping enough circuits open on stable
20224 connections that they were wrapping around the circuit_id
20225 space. (It's only two bytes.) This exposed a bug where we would
20226 feel free to reuse a circuit_id even if it still exists but has
20227 been marked for close. Try to fix this bug. Some bug remains.
20228 - When we fail to bind or listen on an incoming or outgoing
20229 socket, we now close it before refusing, rather than just
20230 leaking it. (Thanks to Peter Palfrader for finding.)
20231 - Fix a file descriptor leak in start_daemon().
20232 - On Windows, you can't always reopen a port right after you've
20233 closed it. So change retry_listeners() to only close and re-open
20234 ports that have changed.
20235 - Workaround a problem with some http proxies that refuse GET
20236 requests that specify "Content-Length: 0". Reported by Adrian.
20237 - Recover better from TCP connections to Tor servers that are
20238 broken but don't tell you (it happens!); and rotate TLS
20239 connections once a week.
20240 - Fix a scary-looking but apparently harmless bug where circuits
20241 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
20242 servers, and never switch to state CIRCUIT_STATE_OPEN.
20243 - Check for even more Windows version flags when writing the platform
20244 string in server descriptors, and note any we don't recognize.
20245 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
20246 get a better idea of why their circuits failed. Not used yet.
20247 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
20248 We don't use them yet, but maybe one day our DNS resolver will be
20249 able to discover them.
20250 - Let people type "tor --install" as well as "tor -install" when they
20251 want to make it an NT service.
20252 - Looks like we were never delivering deflated (i.e. compressed)
20253 running-routers lists, even when asked. Oops.
20254 - We were leaking some memory every time the client changed IPs.
20255 - Clean up more of the OpenSSL memory when exiting, so we can detect
20256 memory leaks better.
20257 - Never call free() on tor_malloc()d memory. This will help us
20258 use dmalloc to detect memory leaks.
20259 - Some Tor servers process billions of cells per day. These
20260 statistics are now uint64_t's.
20261 - Check [X-]Forwarded-For headers in HTTP requests when generating
20262 log messages. This lets people run dirservers (and caches) behind
20263 Apache but still know which IP addresses are causing warnings.
20264 - Fix minor integer overflow in calculating when we expect to use up
20265 our bandwidth allocation before hibernating.
20266 - Lower the minimum required number of file descriptors to 1000,
20267 so we can have some overhead for Valgrind on Linux, where the
20268 default ulimit -n is 1024.
20269 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
20270 and its existence is confusing some users.
20272 o Config option fixes:
20273 - Add a new config option ExitPolicyRejectPrivate which defaults
20274 to on. Now all exit policies will begin with rejecting private
20275 addresses, unless the server operator explicitly turns it off.
20276 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
20277 - Add new ReachableORAddresses and ReachableDirAddresses options
20278 that understand address policies. FascistFirewall is now a synonym
20279 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
20280 - Start calling it FooListenAddress rather than FooBindAddress,
20281 since few of our users know what it means to bind an address
20283 - If the user gave Tor an odd number of command-line arguments,
20284 we were silently ignoring the last one. Now we complain and fail.
20285 This wins the oldest-bug prize -- this bug has been present since
20286 November 2002, as released in Tor 0.0.0.
20287 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
20288 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
20289 it would silently ignore the 6668.
20290 - If we get a linelist or linelist_s config option from the torrc,
20291 e.g. ExitPolicy, and it has no value, warn and skip rather than
20292 silently resetting it to its default.
20293 - Setconf was appending items to linelists, not clearing them.
20294 - Add MyFamily to torrc.sample in the server section, so operators
20295 will be more likely to learn that it exists.
20296 - Make ContactInfo mandatory for authoritative directory servers.
20297 - MaxConn has been obsolete for a while now. Document the ConnLimit
20298 config option, which is a *minimum* number of file descriptors
20299 that must be available else Tor refuses to start.
20300 - Get rid of IgnoreVersion undocumented config option, and make us
20301 only warn, never exit, when we're running an obsolete version.
20302 - Make MonthlyAccountingStart config option truly obsolete now.
20303 - Correct the man page entry on TrackHostExitsExpire.
20304 - Let directory authorities start even if they don't specify an
20305 Address config option.
20306 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
20307 reflect the updated flags in our v2 dir protocol.
20309 o Config option features:
20310 - Add a new config option FastFirstHopPK (on by default) so clients
20311 do a trivial crypto handshake for their first hop, since TLS has
20312 already taken care of confidentiality and authentication.
20313 - Let the user set ControlListenAddress in the torrc. This can be
20314 dangerous, but there are some cases (like a secured LAN) where it
20316 - New config options to help controllers: FetchServerDescriptors
20317 and FetchHidServDescriptors for whether to fetch server
20318 info and hidserv info or let the controller do it, and
20319 PublishServerDescriptor and PublishHidServDescriptors.
20320 - Also let the controller set the __AllDirActionsPrivate config
20321 option if you want all directory fetches/publishes to happen via
20322 Tor (it assumes your controller bootstraps your circuits).
20323 - Add "HardwareAccel" config option: support for crypto hardware
20324 accelerators via OpenSSL. Off by default, until we find somebody
20325 smart who can test it for us. (It appears to produce seg faults
20326 in at least some cases.)
20327 - New config option "AuthDirRejectUnlisted" for directory authorities
20328 as a panic button: if we get flooded with unusable servers we can
20329 revert to only listing servers in the approved-routers file.
20330 - Directory authorities can now reject/invalidate by key and IP,
20331 with the config options "AuthDirInvalid" and "AuthDirReject", or
20332 by marking a fingerprint as "!reject" or "!invalid" (as its
20333 nickname) in the approved-routers file. This is useful since
20334 currently we automatically list servers as running and usable
20335 even if we know they're jerks.
20336 - Add a new config option TestSocks so people can see whether their
20337 applications are using socks4, socks4a, socks5-with-ip, or
20338 socks5-with-fqdn. This way they don't have to keep mucking
20339 with tcpdump and wondering if something got cached somewhere.
20340 - Add "private:*" as an alias in configuration for policies. Now
20341 you can simplify your exit policy rather than needing to list
20342 every single internal or nonroutable network space.
20343 - Accept "private:*" in routerdesc exit policies; not generated yet
20344 because older Tors do not understand it.
20345 - Add configuration option "V1AuthoritativeDirectory 1" which
20346 moria1, moria2, and tor26 have set.
20347 - Implement an option, VirtualAddrMask, to set which addresses
20348 get handed out in response to mapaddress requests. This works
20349 around a bug in tsocks where 127.0.0.0/8 is never socksified.
20350 - Add a new config option FetchUselessDescriptors, off by default,
20351 for when you plan to run "exitlist" on your client and you want
20352 to know about even the non-running descriptors.
20353 - SocksTimeout: How long do we let a socks connection wait
20354 unattached before we fail it?
20355 - CircuitBuildTimeout: Cull non-open circuits that were born
20356 at least this many seconds ago.
20357 - CircuitIdleTimeout: Cull open clean circuits that were born
20358 at least this many seconds ago.
20359 - New config option SafeSocks to reject all application connections
20360 using unsafe socks protocols. Defaults to off.
20362 o Improved and clearer log messages:
20363 - Reduce clutter in server logs. We're going to try to make
20364 them actually usable now. New config option ProtocolWarnings that
20365 lets you hear about how _other Tors_ are breaking the protocol. Off
20367 - Divide log messages into logging domains. Once we put some sort
20368 of interface on this, it will let people looking at more verbose
20369 log levels specify the topics they want to hear more about.
20370 - Log server fingerprint on startup, so new server operators don't
20371 have to go hunting around their filesystem for it.
20372 - Provide dire warnings to any users who set DirServer manually;
20373 move it out of torrc.sample and into torrc.complete.
20374 - Make the log message less scary when all the dirservers are
20375 temporarily unreachable.
20376 - When tor_socketpair() fails in Windows, give a reasonable
20377 Windows-style errno back.
20378 - Improve tor_gettimeofday() granularity on windows.
20379 - We were printing the number of idle dns workers incorrectly when
20381 - Handle duplicate lines in approved-routers files without warning.
20382 - We were whining about using socks4 or socks5-with-local-lookup
20383 even when it's an IP address in the "virtual" range we designed
20384 exactly for this case.
20385 - Check for named servers when looking them up by nickname;
20386 warn when we're calling a non-named server by its nickname;
20387 don't warn twice about the same name.
20388 - Downgrade the dirserver log messages when whining about
20390 - Correct "your server is reachable" log entries to indicate that
20391 it was self-testing that told us so.
20392 - If we're trying to be a Tor server and running Windows 95/98/ME
20393 as a server, explain that we'll likely crash.
20394 - Provide a more useful warn message when our onion queue gets full:
20395 the CPU is too slow or the exit policy is too liberal.
20396 - Don't warn when we receive a 503 from a dirserver/cache -- this
20397 will pave the way for them being able to refuse if they're busy.
20398 - When we fail to bind a listener, try to provide a more useful
20399 log message: e.g., "Is Tor already running?"
20400 - Only start testing reachability once we've established a
20401 circuit. This will make startup on dir authorities less noisy.
20402 - Don't try to upload hidden service descriptors until we have
20403 established a circuit.
20404 - Tor didn't warn when it failed to open a log file.
20405 - Warn when listening on a public address for socks. We suspect a
20406 lot of people are setting themselves up as open socks proxies,
20407 and they have no idea that jerks on the Internet are using them,
20408 since they simply proxy the traffic into the Tor network.
20409 - Give a useful message when people run Tor as the wrong user,
20410 rather than telling them to start chowning random directories.
20411 - Fix a harmless bug that was causing Tor servers to log
20412 "Got an end because of misc error, but we're not an AP. Closing."
20413 - Fix wrong log message when you add a "HiddenServiceNodes" config
20414 line without any HiddenServiceDir line (reported by Chris Thomas).
20415 - Directory authorities now stop whining so loudly about bad
20416 descriptors that they fetch from other dirservers. So when there's
20417 a log complaint, it's for sure from a freshly uploaded descriptor.
20418 - When logging via syslog, include the pid whenever we provide
20419 a log entry. Suggested by Todd Fries.
20420 - When we're shutting down and we do something like try to post a
20421 server descriptor or rendezvous descriptor, don't complain that
20422 we seem to be unreachable. Of course we are, we're shutting down.
20423 - Change log line for unreachability to explicitly suggest /etc/hosts
20424 as the culprit. Also make it clearer what IP address and ports we're
20425 testing for reachability.
20426 - Put quotes around user-supplied strings when logging so users are
20427 more likely to realize if they add bad characters (like quotes)
20429 - NT service patch from Matt Edman to improve error messages on Win32.
20432 Changes in version 0.1.0.17 - 2006-02-17
20433 o Crash bugfixes on 0.1.0.x:
20434 - When servers with a non-zero DirPort came out of hibernation,
20435 sometimes they would trigger an assert.
20437 o Other important bugfixes:
20438 - On platforms that don't have getrlimit (like Windows), we were
20439 artificially constraining ourselves to a max of 1024
20440 connections. Now just assume that we can handle as many as 15000
20441 connections. Hopefully this won't cause other problems.
20443 o Backported features:
20444 - When we're a server, a client asks for an old-style directory,
20445 and our write bucket is empty, don't give it to him. This way
20446 small servers can continue to serve the directory *sometimes*,
20447 without getting overloaded.
20448 - Whenever you get a 503 in response to a directory fetch, try
20449 once more. This will become important once servers start sending
20450 503's whenever they feel busy.
20451 - Fetch a new directory every 120 minutes, not every 40 minutes.
20452 Now that we have hundreds of thousands of users running the old
20453 directory algorithm, it's starting to hurt a lot.
20454 - Bump up the period for forcing a hidden service descriptor upload
20455 from 20 minutes to 1 hour.
20458 Changes in version 0.1.0.16 - 2006-01-02
20459 o Crash bugfixes on 0.1.0.x:
20460 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
20461 corrupting the heap, losing FDs, or crashing when we need to resize
20462 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
20463 - It turns out sparc64 platforms crash on unaligned memory access
20464 too -- so detect and avoid this.
20465 - Handle truncated compressed data correctly (by detecting it and
20467 - Fix possible-but-unlikely free(NULL) in control.c.
20468 - When we were closing connections, there was a rare case that
20469 stomped on memory, triggering seg faults and asserts.
20470 - Avoid potential infinite recursion when building a descriptor. (We
20471 don't know that it ever happened, but better to fix it anyway.)
20472 - We were neglecting to unlink marked circuits from soon-to-close OR
20473 connections, which caused some rare scribbling on freed memory.
20474 - Fix a memory stomping race bug when closing the joining point of two
20475 rendezvous circuits.
20476 - Fix an assert in time parsing found by Steven Murdoch.
20478 o Other bugfixes on 0.1.0.x:
20479 - When we're doing reachability testing, provide more useful log
20480 messages so the operator knows what to expect.
20481 - Do not check whether DirPort is reachable when we are suppressing
20482 advertising it because of hibernation.
20483 - When building with -static or on Solaris, we sometimes needed -ldl.
20484 - One of the dirservers (tor26) changed its IP address.
20485 - When we're deciding whether a stream has enough circuits around
20486 that can handle it, count the freshly dirty ones and not the ones
20487 that are so dirty they won't be able to handle it.
20488 - When we're expiring old circuits, we had a logic error that caused
20489 us to close new rendezvous circuits rather than old ones.
20490 - Give a more helpful log message when you try to change ORPort via
20491 the controller: you should upgrade Tor if you want that to work.
20492 - We were failing to parse Tor versions that start with "Tor ".
20493 - Tolerate faulty streams better: when a stream fails for reason
20494 exitpolicy, stop assuming that the router is lying about his exit
20495 policy. When a stream fails for reason misc, allow it to retry just
20496 as if it was resolvefailed. When a stream has failed three times,
20497 reset its failure count so we can try again and get all three tries.
20500 Changes in version 0.1.0.15 - 2005-09-23
20501 o Bugfixes on 0.1.0.x:
20502 - Reject ports 465 and 587 (spam targets) in default exit policy.
20503 - Don't crash when we don't have any spare file descriptors and we
20504 try to spawn a dns or cpu worker.
20505 - Get rid of IgnoreVersion undocumented config option, and make us
20506 only warn, never exit, when we're running an obsolete version.
20507 - Don't try to print a null string when your server finds itself to
20508 be unreachable and the Address config option is empty.
20509 - Make the numbers in read-history and write-history into uint64s,
20510 so they don't overflow and publish negatives in the descriptor.
20511 - Fix a minor memory leak in smartlist_string_remove().
20512 - We were only allowing ourselves to upload a server descriptor at
20513 most every 20 minutes, even if it changed earlier than that.
20514 - Clean up log entries that pointed to old URLs.
20517 Changes in version 0.1.0.14 - 2005-08-08
20518 o Bugfixes on 0.1.0.x:
20519 - Fix the other half of the bug with crypto handshakes
20521 - Fix an assert trigger if you send a 'signal term' via the
20522 controller when it's listening for 'event info' messages.
20525 Changes in version 0.1.0.13 - 2005-08-04
20526 o Bugfixes on 0.1.0.x:
20527 - Fix a critical bug in the security of our crypto handshakes.
20528 - Fix a size_t underflow in smartlist_join_strings2() that made
20529 it do bad things when you hand it an empty smartlist.
20530 - Fix Windows installer to ship Tor license (thanks to Aphex for
20531 pointing out this oversight) and put a link to the doc directory
20533 - Explicitly set no-unaligned-access for sparc: it turns out the
20534 new gcc's let you compile broken code, but that doesn't make it
20538 Changes in version 0.1.0.12 - 2005-07-18
20539 o New directory servers:
20540 - tor26 has changed IP address.
20542 o Bugfixes on 0.1.0.x:
20543 - Fix a possible double-free in tor_gzip_uncompress().
20544 - When --disable-threads is set, do not search for or link against
20545 pthreads libraries.
20546 - Don't trigger an assert if an authoritative directory server
20547 claims its dirport is 0.
20548 - Fix bug with removing Tor as an NT service: some people were
20549 getting "The service did not return an error." Thanks to Matt
20553 Changes in version 0.1.0.11 - 2005-06-30
20554 o Bugfixes on 0.1.0.x:
20555 - Fix major security bug: servers were disregarding their
20556 exit policies if clients behaved unexpectedly.
20557 - Make OS X init script check for missing argument, so we don't
20558 confuse users who invoke it incorrectly.
20559 - Fix a seg fault in "tor --hash-password foo".
20560 - The MAPADDRESS control command was broken.
20563 Changes in version 0.1.0.10 - 2005-06-14
20565 - Make NT services work and start on startup on Win32 (based on
20566 patch by Matt Edman). See the FAQ entry for details.
20567 - Make 'platform' string in descriptor more accurate for Win32
20568 servers, so it's not just "unknown platform".
20569 - REUSEADDR on normal platforms means you can rebind to the port
20570 right after somebody else has let it go. But REUSEADDR on Win32
20571 means you can bind to the port _even when somebody else already
20572 has it bound_! So, don't do that on Win32.
20573 - Clean up the log messages when starting on Win32 with no config
20575 - Allow seeding the RNG on Win32 even when you're not running as
20576 Administrator. If seeding the RNG on Win32 fails, quit.
20578 o Assert / crash bugs:
20579 - Refuse relay cells that claim to have a length larger than the
20580 maximum allowed. This prevents a potential attack that could read
20581 arbitrary memory (e.g. keys) from an exit server's process
20583 - If unofficial Tor clients connect and send weird TLS certs, our
20584 Tor server triggers an assert. Stop asserting, and start handling
20585 TLS errors better in other situations too.
20586 - Fix a race condition that can trigger an assert when we have a
20587 pending create cell and an OR connection attempt fails.
20590 - Use pthreads for worker processes rather than forking. This was
20591 forced because when we forked, we ended up wasting a lot of
20592 duplicate ram over time.
20593 - Also switch to foo_r versions of some library calls to allow
20594 reentry and threadsafeness.
20595 - Implement --disable-threads configure option. Disable threads on
20596 netbsd and openbsd by default, because they have no reentrant
20597 resolver functions (!), and on solaris since it has other
20599 - Fix possible bug on threading platforms (e.g. win32) which was
20600 leaking a file descriptor whenever a cpuworker or dnsworker died.
20601 - Fix a minor memory leak when somebody establishes an introduction
20602 point at your Tor server.
20603 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
20605 - Add ./configure --with-dmalloc option, to track memory leaks.
20606 - And try to free all memory on closing, so we can detect what
20609 o Protocol correctness:
20610 - When we've connected to an OR and handshaked but didn't like
20611 the result, we were closing the conn without sending destroy
20612 cells back for pending circuits. Now send those destroys.
20613 - Start sending 'truncated' cells back rather than destroy cells
20614 if the circuit closes in front of you. This means we won't have
20615 to abandon partially built circuits.
20616 - Handle changed router status correctly when dirserver reloads
20617 fingerprint file. We used to be dropping all unverified descriptors
20618 right then. The bug was hidden because we would immediately
20619 fetch a directory from another dirserver, which would include the
20620 descriptors we just dropped.
20621 - Revise tor-spec to add more/better stream end reasons.
20622 - Revise all calls to connection_edge_end to avoid sending 'misc',
20623 and to take errno into account where possible.
20624 - Client now retries when streams end early for 'hibernating' or
20625 'resource limit' reasons, rather than failing them.
20626 - Try to be more zealous about calling connection_edge_end when
20627 things go bad with edge conns in connection.c.
20629 o Robustness improvements:
20630 - Better handling for heterogeneous / unreliable nodes:
20631 - Annotate circuits with whether they aim to contain high uptime
20632 nodes and/or high capacity nodes. When building circuits, choose
20634 - This means that every single node in an intro rend circuit,
20635 not just the last one, will have a minimum uptime.
20636 - New config option LongLivedPorts to indicate application streams
20637 that will want high uptime circuits.
20638 - Servers reset uptime when a dir fetch entirely fails. This
20639 hopefully reflects stability of the server's network connectivity.
20640 - If somebody starts his tor server in Jan 2004 and then fixes his
20641 clock, don't make his published uptime be a year.
20642 - Reset published uptime when we wake up from hibernation.
20643 - Introduce a notion of 'internal' circs, which are chosen without
20644 regard to the exit policy of the last hop. Intro and rendezvous
20645 circs must be internal circs, to avoid leaking information. Resolve
20646 and connect streams can use internal circs if they want.
20647 - New circuit pooling algorithm: keep track of what destination ports
20648 we've used recently (start out assuming we'll want to use 80), and
20649 make sure to have enough circs around to satisfy these ports. Also
20650 make sure to have 2 internal circs around if we've required internal
20651 circs lately (and with high uptime if we've seen that lately too).
20652 - Turn addr_policy_compare from a tristate to a quadstate; this should
20653 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
20654 for google.com" problem.
20655 - When a client asks us for a dir mirror and we don't have one,
20656 launch an attempt to get a fresh one.
20657 - First cut at support for "create-fast" cells. Clients can use
20658 these when extending to their first hop, since the TLS already
20659 provides forward secrecy and authentication. Not enabled on
20662 o Reachability testing.
20663 - Your Tor server will automatically try to see if its ORPort and
20664 DirPort are reachable from the outside, and it won't upload its
20665 descriptor until it decides at least ORPort is reachable (when
20666 DirPort is not yet found reachable, publish it as zero).
20667 - When building testing circs for ORPort testing, use only
20668 high-bandwidth nodes, so fewer circuits fail.
20669 - Notice when our IP changes, and reset stats/uptime/reachability.
20670 - Authdirservers don't do ORPort reachability detection, since
20671 they're in clique mode, so it will be rare to find a server not
20672 already connected to them.
20673 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
20677 - Now we allow two unverified servers with the same nickname
20678 but different keys. But if a nickname is verified, only that
20679 nickname+key are allowed.
20680 - If you're an authdirserver connecting to an address:port,
20681 and it's not the OR you were expecting, forget about that
20682 descriptor. If he *was* the one you were expecting, then forget
20683 about all other descriptors for that address:port.
20684 - Allow servers to publish descriptors from 12 hours in the future.
20685 Corollary: only whine about clock skew from the dirserver if
20686 he's a trusted dirserver (since now even verified servers could
20687 have quite wrong clocks).
20688 - Require servers that use the default dirservers to have public IP
20689 addresses. We have too many servers that are configured with private
20690 IPs and their admins never notice the log entries complaining that
20691 their descriptors are being rejected.
20693 o Efficiency improvements:
20694 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
20695 and /dev/poll), and hopefully work better on Windows too.
20696 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
20697 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
20698 - Find libevent even if it's hiding in /usr/local/ and your
20699 CFLAGS and LDFLAGS don't tell you to look there.
20700 - Be able to link with libevent as a shared library (the default
20701 after 1.0d), even if it's hiding in /usr/local/lib and even
20702 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
20703 assuming you're running gcc. Otherwise fail and give a useful
20705 - Switch to a new buffer management algorithm, which tries to avoid
20706 reallocing and copying quite as much. In first tests it looks like
20707 it uses *more* memory on average, but less cpu.
20708 - Switch our internal buffers implementation to use a ring buffer,
20709 to hopefully improve performance for fast servers a lot.
20710 - Reenable the part of the code that tries to flush as soon as an
20711 OR outbuf has a full TLS record available. Perhaps this will make
20712 OR outbufs not grow as huge except in rare cases, thus saving lots
20713 of CPU time plus memory.
20714 - Improve performance for dirservers: stop re-parsing the whole
20715 directory every time you regenerate it.
20716 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
20717 it much faster to look up a circuit for each relay cell.
20718 - Remove most calls to assert_all_pending_dns_resolves_ok(),
20719 since they're eating our cpu on exit nodes.
20720 - Stop wasting time doing a case insensitive comparison for every
20721 dns name every time we do any lookup. Canonicalize the names to
20722 lowercase when you first see them.
20725 - Handle unavailable hidden services better. Handle slow or busy
20726 hidden services better.
20727 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
20728 circ as necessary, if there are any completed ones lying around
20729 when we try to launch one.
20730 - Make hidden services try to establish a rendezvous for 30 seconds
20731 after fetching the descriptor, rather than for n (where n=3)
20732 attempts to build a circuit.
20733 - Adjust maximum skew and age for rendezvous descriptors: let skew
20734 be 48 hours rather than 90 minutes.
20735 - Reject malformed .onion addresses rather then passing them on as
20736 normal web requests.
20739 - More Tor controller support. See
20740 http://tor.eff.org/doc/control-spec.txt for all the new features,
20741 including signals to emulate unix signals from any platform;
20742 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
20743 closestream; closecircuit; etc.
20744 - Encode hashed controller passwords in hex instead of base64,
20745 to make it easier to write controllers.
20746 - Revise control spec and implementation to allow all log messages to
20747 be sent to controller with their severities intact (suggested by
20748 Matt Edman). Disable debug-level logs while delivering a debug-level
20749 log to the controller, to prevent loop. Update TorControl to handle
20750 new log event types.
20752 o New config options/defaults:
20753 - Begin scrubbing sensitive strings from logs by default. Turn off
20754 the config option SafeLogging if you need to do debugging.
20755 - New exit policy: accept most low-numbered ports, rather than
20756 rejecting most low-numbered ports.
20757 - Put a note in the torrc about abuse potential with the default
20759 - Add support for CONNECTing through https proxies, with "HttpsProxy"
20761 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
20762 based on patch from Adam Langley (basic auth only).
20763 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
20764 the fast servers that have been joining lately. (Clients are now
20765 willing to load balance over up to 2 MB of advertised bandwidth
20767 - New config option MaxAdvertisedBandwidth which lets you advertise
20768 a low bandwidthrate (to not attract as many circuits) while still
20769 allowing a higher bandwidthrate in reality.
20770 - Require BandwidthRate to be at least 20kB/s for servers.
20771 - Add a NoPublish config option, so you can be a server (e.g. for
20772 testing running Tor servers in other Tor networks) without
20773 publishing your descriptor to the primary dirservers.
20774 - Add a new AddressMap config directive to rewrite incoming socks
20775 addresses. This lets you, for example, declare an implicit
20776 required exit node for certain sites.
20777 - Add a new TrackHostExits config directive to trigger addressmaps
20778 for certain incoming socks addresses -- for sites that break when
20779 your exit keeps changing (based on patch from Mike Perry).
20780 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
20781 which describes how often we retry making new circuits if current
20782 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
20783 how long we're willing to make use of an already-dirty circuit.
20784 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
20785 a config option "ShutdownWaitLength" (when using kill -INT on
20787 - Fix an edge case in parsing config options: if they say "--"
20788 on the commandline, it's not a config option (thanks weasel).
20789 - New config option DirAllowPrivateAddresses for authdirservers.
20790 Now by default they refuse router descriptors that have non-IP or
20791 private-IP addresses.
20792 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
20793 smart" default value: low for servers and high for clients.
20794 - Some people were putting "Address " in their torrc, and they had
20795 a buggy resolver that resolved " " to 0.0.0.0. Oops.
20796 - If DataDir is ~/.tor, and that expands to /.tor, then default to
20797 LOCALSTATEDIR/tor instead.
20798 - Implement --verify-config command-line option to check if your torrc
20799 is valid without actually launching Tor.
20801 o Logging improvements:
20802 - When dirservers refuse a server descriptor, we now log its
20803 contactinfo, platform, and the poster's IP address.
20804 - Only warn once per nickname from add_nickname_list_to_smartlist()
20805 per failure, so an entrynode or exitnode choice that's down won't
20807 - When we're connecting to an OR and he's got a different nickname/key
20808 than we were expecting, only complain loudly if we're an OP or a
20809 dirserver. Complaining loudly to the OR admins just confuses them.
20810 - Whine at you if you're a server and you don't set your contactinfo.
20811 - Warn when exit policy implicitly allows local addresses.
20812 - Give a better warning when some other server advertises an
20813 ORPort that is actually an apache running ssl.
20814 - If we get an incredibly skewed timestamp from a dirserver mirror
20815 that isn't a verified OR, don't warn -- it's probably him that's
20817 - When a dirserver causes you to give a warn, mention which dirserver
20819 - Initialize libevent later in the startup process, so the logs are
20820 already established by the time we start logging libevent warns.
20821 - Use correct errno on win32 if libevent fails.
20822 - Check and warn about known-bad/slow libevent versions.
20823 - Stop warning about sigpipes in the logs. We're going to
20824 pretend that getting these occasionally is normal and fine.
20826 o New contrib scripts:
20827 - New experimental script tor/contrib/exitlist: a simple python
20828 script to parse directories and find Tor nodes that exit to listed
20830 - New experimental script tor/contrib/ExerciseServer.py (needs more
20831 work) that uses the controller interface to build circuits and
20832 fetch pages over them. This will help us bootstrap servers that
20833 have lots of capacity but haven't noticed it yet.
20834 - New experimental script tor/contrib/PathDemo.py (needs more work)
20835 that uses the controller interface to let you choose whole paths
20837 "<hostname>.<path,separated by dots>.<length of path>.path"
20838 - New contributed script "privoxy-tor-toggle" to toggle whether
20839 Privoxy uses Tor. Seems to be configured for Debian by default.
20840 - Have torctl.in/tor.sh.in check for location of su binary (needed
20844 - chdir() to your datadirectory at the *end* of the daemonize process,
20845 not the beginning. This was a problem because the first time you
20846 run tor, if your datadir isn't there, and you have runasdaemon set
20847 to 1, it will try to chdir to it before it tries to create it. Oops.
20848 - Fix several double-mark-for-close bugs, e.g. where we were finding
20849 a conn for a cell even if that conn is already marked for close.
20850 - Stop most cases of hanging up on a socks connection without sending
20852 - Fix a bug in the RPM package: set home directory for _tor to
20853 something more reasonable when first installing.
20854 - Stop putting nodename in the Platform string in server descriptors.
20855 It doesn't actually help, and it is confusing/upsetting some people.
20856 - When using preferred entry or exit nodes, ignore whether the
20857 circuit wants uptime or capacity. They asked for the nodes, they
20859 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
20860 artificially capped at 500kB.
20861 - Cache local dns resolves correctly even when they're .exit
20863 - If we're hibernating and we get a SIGINT, exit immediately.
20864 - tor-resolve requests were ignoring .exit if there was a working circuit
20865 they could use instead.
20866 - Pay more attention to the ClientOnly config option.
20867 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
20868 installer screens; and don't put stuff into StartupItems unless
20869 the user asks you to.
20872 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
20873 rather than just rejecting it.
20874 - If our clock jumps forward by 100 seconds or more, assume something
20875 has gone wrong with our network and abandon all not-yet-used circs.
20876 - When an application is using socks5, give him the whole variety of
20877 potential socks5 responses (connect refused, host unreachable, etc),
20878 rather than just "success" or "failure".
20879 - A more sane version numbering system. See
20880 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
20881 - Change version parsing logic: a version is "obsolete" if it is not
20882 recommended and (1) there is a newer recommended version in the
20883 same series, or (2) there are no recommended versions in the same
20884 series, but there are some recommended versions in a newer series.
20885 A version is "new" if it is newer than any recommended version in
20887 - Report HTTP reasons to client when getting a response from directory
20888 servers -- so you can actually know what went wrong.
20889 - Reject odd-looking addresses at the client (e.g. addresses that
20890 contain a colon), rather than having the server drop them because
20892 - Stop publishing socksport in the directory, since it's not
20893 actually meant to be public. For compatibility, publish a 0 there
20895 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
20896 cookies to disk and doesn't log each web request to disk. (Thanks
20897 to Brett Carrington for pointing this out.)
20898 - Add OSX uninstall instructions. An actual uninstall script will
20900 - Add "opt hibernating 1" to server descriptor to make it clearer
20901 whether the server is hibernating.
20904 Changes in version 0.0.9.10 - 2005-06-16
20905 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
20906 - Refuse relay cells that claim to have a length larger than the
20907 maximum allowed. This prevents a potential attack that could read
20908 arbitrary memory (e.g. keys) from an exit server's process
20912 Changes in version 0.0.9.9 - 2005-04-23
20913 o Bugfixes on 0.0.9.x:
20914 - If unofficial Tor clients connect and send weird TLS certs, our
20915 Tor server triggers an assert. This release contains a minimal
20916 backport from the broader fix that we put into 0.1.0.4-rc.
20919 Changes in version 0.0.9.8 - 2005-04-07
20920 o Bugfixes on 0.0.9.x:
20921 - We have a bug that I haven't found yet. Sometimes, very rarely,
20922 cpuworkers get stuck in the 'busy' state, even though the cpuworker
20923 thinks of itself as idle. This meant that no new circuits ever got
20924 established. Here's a workaround to kill any cpuworker that's been
20925 busy for more than 100 seconds.
20928 Changes in version 0.0.9.7 - 2005-04-01
20929 o Bugfixes on 0.0.9.x:
20930 - Fix another race crash bug (thanks to Glenn Fink for reporting).
20931 - Compare identity to identity, not to nickname, when extending to
20932 a router not already in the directory. This was preventing us from
20933 extending to unknown routers. Oops.
20934 - Make sure to create OS X Tor user in <500 range, so we aren't
20935 creating actual system users.
20936 - Note where connection-that-hasn't-sent-end was marked, and fix
20937 a few really loud instances of this harmless bug (it's fixed more
20941 Changes in version 0.0.9.6 - 2005-03-24
20942 o Bugfixes on 0.0.9.x (crashes and asserts):
20943 - Add new end stream reasons to maintenance branch. Fix bug where
20944 reason (8) could trigger an assert. Prevent bug from recurring.
20945 - Apparently win32 stat wants paths to not end with a slash.
20946 - Fix assert triggers in assert_cpath_layer_ok(), where we were
20947 blowing away the circuit that conn->cpath_layer points to, then
20948 checking to see if the circ is well-formed. Backport check to make
20949 sure we dont use the cpath on a closed connection.
20950 - Prevent circuit_resume_edge_reading_helper() from trying to package
20951 inbufs for marked-for-close streams.
20952 - Don't crash on hup if your options->address has become unresolvable.
20953 - Some systems (like OS X) sometimes accept() a connection and tell
20954 you the remote host is 0.0.0.0:0. If this happens, due to some
20955 other mis-features, we get confused; so refuse the conn for now.
20957 o Bugfixes on 0.0.9.x (other):
20958 - Fix harmless but scary "Unrecognized content encoding" warn message.
20959 - Add new stream error reason: TORPROTOCOL reason means "you are not
20960 speaking a version of Tor I understand; say bye-bye to your stream."
20961 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
20962 into the future, now that we are more tolerant of skew. This
20963 resolves a bug where a Tor server would refuse to cache a directory
20964 because all the directories it gets are too far in the future;
20965 yet the Tor server never logs any complaints about clock skew.
20966 - Mac packaging magic: make man pages useable, and do not overwrite
20967 existing torrc files.
20968 - Make OS X log happily to /var/log/tor/tor.log
20971 Changes in version 0.0.9.5 - 2005-02-22
20972 o Bugfixes on 0.0.9.x:
20973 - Fix an assert race at exit nodes when resolve requests fail.
20974 - Stop picking unverified dir mirrors--it only leads to misery.
20975 - Patch from Matt Edman to make NT services work better. Service
20976 support is still not compiled into the executable by default.
20977 - Patch from Dmitri Bely so the Tor service runs better under
20978 the win32 SYSTEM account.
20979 - Make tor-resolve actually work (?) on Win32.
20980 - Fix a sign bug when getrlimit claims to have 4+ billion
20981 file descriptors available.
20982 - Stop refusing to start when bandwidthburst == bandwidthrate.
20983 - When create cells have been on the onion queue more than five
20984 seconds, just send back a destroy and take them off the list.
20987 Changes in version 0.0.9.4 - 2005-02-03
20988 o Bugfixes on 0.0.9:
20989 - Fix an assert bug that took down most of our servers: when
20990 a server claims to have 1 GB of bandwidthburst, don't
20992 - Don't crash as badly if we have spawned the max allowed number
20993 of dnsworkers, or we're out of file descriptors.
20994 - Block more file-sharing ports in the default exit policy.
20995 - MaxConn is now automatically set to the hard limit of max
20996 file descriptors we're allowed (ulimit -n), minus a few for
20998 - Give a clearer message when servers need to raise their
20999 ulimit -n when they start running out of file descriptors.
21000 - SGI Compatibility patches from Jan Schaumann.
21001 - Tolerate a corrupt cached directory better.
21002 - When a dirserver hasn't approved your server, list which one.
21003 - Go into soft hibernation after 95% of the bandwidth is used,
21004 not 99%. This is especially important for daily hibernators who
21005 have a small accounting max. Hopefully it will result in fewer
21006 cut connections when the hard hibernation starts.
21007 - Load-balance better when using servers that claim more than
21008 800kB/s of capacity.
21009 - Make NT services work (experimental, only used if compiled in).
21012 Changes in version 0.0.9.3 - 2005-01-21
21013 o Bugfixes on 0.0.9:
21014 - Backport the cpu use fixes from main branch, so busy servers won't
21015 need as much processor time.
21016 - Work better when we go offline and then come back, or when we
21017 run Tor at boot before the network is up. We do this by
21018 optimistically trying to fetch a new directory whenever an
21019 application request comes in and we think we're offline -- the
21020 human is hopefully a good measure of when the network is back.
21021 - Backport some minimal hidserv bugfixes: keep rend circuits open as
21022 long as you keep using them; actually publish hidserv descriptors
21023 shortly after they change, rather than waiting 20-40 minutes.
21024 - Enable Mac startup script by default.
21025 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
21026 - When you update AllowUnverifiedNodes or FirewallPorts via the
21027 controller's setconf feature, we were always appending, never
21029 - When you update HiddenServiceDir via setconf, it was screwing up
21030 the order of reading the lines, making it fail.
21031 - Do not rewrite a cached directory back to the cache; otherwise we
21032 will think it is recent and not fetch a newer one on startup.
21033 - Workaround for webservers that lie about Content-Encoding: Tor
21034 now tries to autodetect compressed directories and compression
21035 itself. This lets us Proxypass dir fetches through apache.
21038 Changes in version 0.0.9.2 - 2005-01-04
21039 o Bugfixes on 0.0.9 (crashes and asserts):
21040 - Fix an assert on startup when the disk is full and you're logging
21042 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
21043 style address, then we'd crash.
21044 - Fix an assert trigger when the running-routers string we get from
21045 a dirserver is broken.
21046 - Make worker threads start and run on win32. Now win32 servers
21048 - Bandaid (not actually fix, but now it doesn't crash) an assert
21049 where the dns worker dies mysteriously and the main Tor process
21050 doesn't remember anything about the address it was resolving.
21052 o Bugfixes on 0.0.9 (Win32):
21053 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
21054 name out of the warning/assert messages.
21055 - Fix a superficial "unhandled error on read" bug on win32.
21056 - The win32 installer no longer requires a click-through for our
21057 license, since our Free Software license grants rights but does not
21059 - Win32: When connecting to a dirserver fails, try another one
21060 immediately. (This was already working for non-win32 Tors.)
21061 - Stop trying to parse $HOME on win32 when hunting for default
21063 - Make tor-resolve.c work on win32 by calling network_init().
21065 o Bugfixes on 0.0.9 (other):
21066 - Make 0.0.9.x build on Solaris again.
21067 - Due to a fencepost error, we were blowing away the \n when reporting
21068 confvalue items in the controller. So asking for multiple config
21069 values at once couldn't work.
21070 - When listing circuits that are pending on an opening OR connection,
21071 if we're an OR we were listing circuits that *end* at us as
21072 being pending on every listener, dns/cpu worker, etc. Stop that.
21073 - Dirservers were failing to create 'running-routers' or 'directory'
21074 strings if we had more than some threshold of routers. Fix them so
21075 they can handle any number of routers.
21076 - Fix a superficial "Duplicate mark for close" bug.
21077 - Stop checking for clock skew for OR connections, even for servers.
21078 - Fix a fencepost error that was chopping off the last letter of any
21079 nickname that is the maximum allowed nickname length.
21080 - Update URLs in log messages so they point to the new website.
21081 - Fix a potential problem in mangling server private keys while
21082 writing to disk (not triggered yet, as far as we know).
21083 - Include the licenses for other free software we include in Tor,
21084 now that we're shipping binary distributions more regularly.
21087 Changes in version 0.0.9.1 - 2004-12-15
21088 o Bugfixes on 0.0.9:
21089 - Make hibernation actually work.
21090 - Make HashedControlPassword config option work.
21091 - When we're reporting event circuit status to a controller,
21092 don't use the stream status code.
21095 Changes in version 0.0.9 - 2004-12-12
21096 o Bugfixes on 0.0.8.1 (Crashes and asserts):
21097 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
21098 write() call will fail and we handle it there.
21099 - When we run out of disk space, or other log writing error, don't
21100 crash. Just stop logging to that log and continue.
21101 - Fix isspace() and friends so they still make Solaris happy
21102 but also so they don't trigger asserts on win32.
21103 - Fix assert failure on malformed socks4a requests.
21104 - Fix an assert bug where a hidden service provider would fail if
21105 the first hop of his rendezvous circuit was down.
21106 - Better handling of size_t vs int, so we're more robust on 64
21109 o Bugfixes on 0.0.8.1 (Win32):
21110 - Make windows sockets actually non-blocking (oops), and handle
21111 win32 socket errors better.
21112 - Fix parse_iso_time on platforms without strptime (eg win32).
21113 - win32: when being multithreaded, leave parent fdarray open.
21114 - Better handling of winsock includes on non-MSV win32 compilers.
21115 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
21117 - Make unit tests work on win32.
21119 o Bugfixes on 0.0.8.1 (Path selection and streams):
21120 - Calculate timeout for waiting for a connected cell from the time
21121 we sent the begin cell, not from the time the stream started. If
21122 it took a long time to establish the circuit, we would time out
21123 right after sending the begin cell.
21124 - Fix router_compare_addr_to_addr_policy: it was not treating a port
21125 of * as always matching, so we were picking reject *:* nodes as
21126 exit nodes too. Oops.
21127 - When read() failed on a stream, we would close it without sending
21128 back an end. So 'connection refused' would simply be ignored and
21129 the user would get no response.
21130 - Stop a sigpipe: when an 'end' cell races with eof from the app,
21131 we shouldn't hold-open-until-flush if the eof arrived first.
21132 - Let resolve conns retry/expire also, rather than sticking around
21134 - Fix more dns related bugs: send back resolve_failed and end cells
21135 more reliably when the resolve fails, rather than closing the
21136 circuit and then trying to send the cell. Also attach dummy resolve
21137 connections to a circuit *before* calling dns_resolve(), to fix
21138 a bug where cached answers would never be sent in RESOLVED cells.
21140 o Bugfixes on 0.0.8.1 (Circuits):
21141 - Finally fix a bug that's been plaguing us for a year:
21142 With high load, circuit package window was reaching 0. Whenever
21143 we got a circuit-level sendme, we were reading a lot on each
21144 socket, but only writing out a bit. So we would eventually reach
21145 eof. This would be noticed and acted on even when there were still
21146 bytes sitting in the inbuf.
21147 - Use identity comparison, not nickname comparison, to choose which
21148 half of circuit-ID-space each side gets to use. This is needed
21149 because sometimes we think of a router as a nickname, and sometimes
21150 as a hex ID, and we can't predict what the other side will do.
21152 o Bugfixes on 0.0.8.1 (Other):
21153 - Fix a whole slew of memory leaks.
21154 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
21155 - If we are using select, make sure we stay within FD_SETSIZE.
21156 - When poll() is interrupted, we shouldn't believe the revents values.
21157 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
21158 and smartlist_len, which are two major profiling offenders.
21159 - If do_hup fails, actually notice.
21160 - Flush the log file descriptor after we print "Tor opening log file",
21161 so we don't see those messages days later.
21162 - Hidden service operators now correctly handle version 1 style
21163 INTRODUCE1 cells (nobody generates them still, so not a critical
21165 - Handle more errnos from accept() without closing the listener.
21166 Some OpenBSD machines were closing their listeners because
21167 they ran out of file descriptors.
21168 - Some people had wrapped their tor client/server in a script
21169 that would restart it whenever it died. This did not play well
21170 with our "shut down if your version is obsolete" code. Now people
21171 don't fetch a new directory if their local cached version is
21173 - Make our autogen.sh work on ksh as well as bash.
21174 - Better torrc example lines for dirbindaddress and orbindaddress.
21175 - Improved bounds checking on parsed ints (e.g. config options and
21176 the ones we find in directories.)
21177 - Stop using separate defaults for no-config-file and
21178 empty-config-file. Now you have to explicitly turn off SocksPort,
21179 if you don't want it open.
21180 - We were starting to daemonize before we opened our logs, so if
21181 there were any problems opening logs, we would complain to stderr,
21182 which wouldn't work, and then mysteriously exit.
21183 - If a verified OR connects to us before he's uploaded his descriptor,
21184 or we verify him and hup but he still has the original TLS
21185 connection, then conn->nickname is still set like he's unverified.
21187 o Code security improvements, inspired by Ilja:
21188 - tor_snprintf wrapper over snprintf with consistent (though not C99)
21190 - Replace sprintf with tor_snprintf. (I think they were all safe, but
21192 - Replace strcpy/strncpy with strlcpy in more places.
21193 - Avoid strcat; use tor_snprintf or strlcat instead.
21195 o Features (circuits and streams):
21196 - New circuit building strategy: keep a list of ports that we've
21197 used in the past 6 hours, and always try to have 2 circuits open
21198 or on the way that will handle each such port. Seed us with port
21199 80 so web users won't complain that Tor is "slow to start up".
21200 - Make kill -USR1 dump more useful stats about circuits.
21201 - When warning about retrying or giving up, print the address, so
21202 the user knows which one it's talking about.
21203 - If you haven't used a clean circuit in an hour, throw it away,
21204 just to be on the safe side. (This means after 6 hours a totally
21205 unused Tor client will have no circuits open.)
21206 - Support "foo.nickname.exit" addresses, to let Alice request the
21207 address "foo" as viewed by exit node "nickname". Based on a patch
21208 from Geoff Goodell.
21209 - If your requested entry or exit node has advertised bandwidth 0,
21211 - Be more greedy about filling up relay cells -- we try reading again
21212 once we've processed the stuff we read, in case enough has arrived
21213 to fill the last cell completely.
21214 - Refuse application socks connections to port 0.
21215 - Use only 0.0.9pre1 and later servers for resolve cells.
21217 o Features (bandwidth):
21218 - Hibernation: New config option "AccountingMax" lets you
21219 set how many bytes per month (in each direction) you want to
21220 allow your server to consume. Rather than spreading those
21221 bytes out evenly over the month, we instead hibernate for some
21222 of the month and pop up at a deterministic time, work until
21223 the bytes are consumed, then hibernate again. Config option
21224 "MonthlyAccountingStart" lets you specify which day of the month
21225 your billing cycle starts on.
21226 - Implement weekly/monthly/daily accounting: now you specify your
21227 hibernation properties by
21228 AccountingMax N bytes|KB|MB|GB|TB
21229 AccountingStart day|week|month [day] HH:MM
21230 Defaults to "month 1 0:00".
21231 - Let bandwidth and interval config options be specified as 5 bytes,
21232 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
21234 o Features (directories):
21235 - New "router-status" line in directory, to better bind each verified
21236 nickname to its identity key.
21237 - Clients can ask dirservers for /dir.z to get a compressed version
21238 of the directory. Only works for servers running 0.0.9, of course.
21239 - Make clients cache directories and use them to seed their router
21240 lists at startup. This means clients have a datadir again.
21241 - Respond to content-encoding headers by trying to uncompress as
21243 - Clients and servers now fetch running-routers; cache
21244 running-routers; compress running-routers; serve compressed
21246 - Make moria2 advertise a dirport of 80, so people behind firewalls
21247 will be able to get a directory.
21248 - Http proxy support
21249 - Dirservers translate requests for http://%s:%d/x to /x
21250 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
21251 be routed through this host.
21252 - Clients ask for /tor/x rather than /x for new enough dirservers.
21253 This way we can one day coexist peacefully with apache.
21254 - Clients specify a "Host: %s%d" http header, to be compatible
21255 with more proxies, and so running squid on an exit node can work.
21256 - Protect dirservers from overzealous descriptor uploading -- wait
21257 10 seconds after directory gets dirty, before regenerating.
21259 o Features (packages and install):
21260 - Add NSI installer contributed by J Doe.
21261 - Apply NT service patch from Osamu Fujino. Still needs more work.
21262 - Commit VC6 and VC7 workspace/project files.
21263 - Commit a tor.spec for making RPM files, with help from jbash.
21264 - Add contrib/torctl.in contributed by Glenn Fink.
21265 - Make expand_filename handle ~ and ~username.
21266 - Use autoconf to enable largefile support where necessary. Use
21267 ftello where available, since ftell can fail at 2GB.
21268 - Ship src/win32/ in the tarball, so people can use it to build.
21269 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
21272 o Features (ui controller):
21273 - Control interface: a separate program can now talk to your
21274 client/server over a socket, and get/set config options, receive
21275 notifications of circuits and streams starting/finishing/dying,
21276 bandwidth used, etc. The next step is to get some GUIs working.
21277 Let us know if you want to help out. See doc/control-spec.txt .
21278 - Ship a contrib/tor-control.py as an example script to interact
21279 with the control port.
21280 - "tor --hash-password zzyxz" will output a salted password for
21281 use in authenticating to the control interface.
21282 - Implement the control-spec's SAVECONF command, to write your
21283 configuration to torrc.
21284 - Get cookie authentication for the controller closer to working.
21285 - When set_conf changes our server descriptor, upload a new copy.
21286 But don't upload it too often if there are frequent changes.
21288 o Features (config and command-line):
21289 - Deprecate unofficial config option abbreviations, and abbreviations
21290 not on the command line.
21291 - Configuration infrastructure support for warning on obsolete
21293 - Give a slightly more useful output for "tor -h".
21294 - Break DirFetchPostPeriod into:
21295 - DirFetchPeriod for fetching full directory,
21296 - StatusFetchPeriod for fetching running-routers,
21297 - DirPostPeriod for posting server descriptor,
21298 - RendPostPeriod for posting hidden service descriptors.
21299 - New log format in config:
21300 "Log minsev[-maxsev] stdout|stderr|syslog" or
21301 "Log minsev[-maxsev] file /var/foo"
21302 - DirPolicy config option, to let people reject incoming addresses
21303 from their dirserver.
21304 - "tor --list-fingerprint" will list your identity key fingerprint
21306 - Make tor --version --version dump the cvs Id of every file.
21307 - New 'MyFamily nick1,...' config option for a server to
21308 specify other servers that shouldn't be used in the same circuit
21309 with it. Only believed if nick1 also specifies us.
21310 - New 'NodeFamily nick1,nick2,...' config option for a client to
21311 specify nodes that it doesn't want to use in the same circuit.
21312 - New 'Redirectexit pattern address:port' config option for a
21313 server to redirect exit connections, e.g. to a local squid.
21314 - Add "pass" target for RedirectExit, to make it easier to break
21315 out of a sequence of RedirectExit rules.
21316 - Make the dirservers file obsolete.
21317 - Include a dir-signing-key token in directories to tell the
21318 parsing entity which key is being used to sign.
21319 - Remove the built-in bulky default dirservers string.
21320 - New config option "Dirserver %s:%d [fingerprint]", which can be
21321 repeated as many times as needed. If no dirservers specified,
21322 default to moria1,moria2,tor26.
21323 - Make 'Routerfile' config option obsolete.
21324 - Discourage people from setting their dirfetchpostperiod more often
21325 than once per minute.
21327 o Features (other):
21328 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
21329 get back to normal.)
21330 - Accept *:706 (silc) in default exit policy.
21331 - Implement new versioning format for post 0.1.
21332 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
21333 log more informatively.
21334 - Check clock skew for verified servers, but allow unverified
21335 servers and clients to have any clock skew.
21336 - Make sure the hidden service descriptors are at a random offset
21337 from each other, to hinder linkability.
21338 - Clients now generate a TLS cert too, in preparation for having
21339 them act more like real nodes.
21340 - Add a pure-C tor-resolve implementation.
21341 - Use getrlimit and friends to ensure we can reach MaxConn (currently
21342 1024) file descriptors.
21343 - Raise the max dns workers from 50 to 100.
21346 Changes in version 0.0.8.1 - 2004-10-13
21348 - Fix a seg fault that can be triggered remotely for Tor
21349 clients/servers with an open dirport.
21350 - Fix a rare assert trigger, where routerinfos for entries in
21351 our cpath would expire while we're building the path.
21352 - Fix a bug in OutboundBindAddress so it (hopefully) works.
21353 - Fix a rare seg fault for people running hidden services on
21354 intermittent connections.
21355 - Fix a bug in parsing opt keywords with objects.
21356 - Fix a stale pointer assert bug when a stream detaches and
21358 - Fix a string format vulnerability (probably not exploitable)
21359 in reporting stats locally.
21360 - Fix an assert trigger: sometimes launching circuits can fail
21361 immediately, e.g. because too many circuits have failed recently.
21362 - Fix a compile warning on 64 bit platforms.
21365 Changes in version 0.0.8 - 2004-08-25
21367 - Made our unit tests compile again on OpenBSD 3.5, and tor
21368 itself compile again on OpenBSD on a sparc64.
21369 - We were neglecting milliseconds when logging on win32, so
21370 everything appeared to happen at the beginning of each second.
21371 - Check directory signature _before_ you decide whether you're
21372 you're running an obsolete version and should exit.
21373 - Check directory signature _before_ you parse the running-routers
21374 list to decide who's running.
21375 - Check return value of fclose while writing to disk, so we don't
21376 end up with broken files when servers run out of disk space.
21377 - Port it to SunOS 5.9 / Athena
21378 - Fix two bugs in saving onion keys to disk when rotating, so
21379 hopefully we'll get fewer people using old onion keys.
21380 - Remove our mostly unused -- and broken -- hex_encode()
21381 function. Use base16_encode() instead. (Thanks to Timo Lindfors
21382 for pointing out this bug.)
21383 - Only pick and establish intro points after we've gotten a
21385 - Fix assert triggers: if the other side returns an address 0.0.0.0,
21386 don't put it into the client dns cache.
21387 - If a begin failed due to exit policy, but we believe the IP
21388 address should have been allowed, switch that router to exitpolicy
21389 reject *:* until we get our next directory.
21391 o Protocol changes:
21392 - 'Extend' relay cell payloads now include the digest of the
21393 intended next hop's identity key. Now we can verify that we're
21394 extending to the right router, and also extend to routers we
21395 hadn't heard of before.
21398 - Tor nodes can now act as relays (with an advertised ORPort)
21399 without being manually verified by the dirserver operators.
21400 - Uploaded descriptors of unverified routers are now accepted
21401 by the dirservers, and included in the directory.
21402 - Verified routers are listed by nickname in the running-routers
21403 list; unverified routers are listed as "$<fingerprint>".
21404 - We now use hash-of-identity-key in most places rather than
21405 nickname or addr:port, for improved security/flexibility.
21406 - AllowUnverifiedNodes config option to let circuits choose no-name
21407 routers in entry,middle,exit,introduction,rendezvous positions.
21408 Allow middle and rendezvous positions by default.
21409 - When picking unverified routers, skip those with low uptime and/or
21410 low bandwidth, depending on what properties you care about.
21411 - ClientOnly option for nodes that never want to become servers.
21412 - Directory caching.
21413 - "AuthoritativeDir 1" option for the official dirservers.
21414 - Now other nodes (clients and servers) will cache the latest
21415 directory they've pulled down.
21416 - They can enable their DirPort to serve it to others.
21417 - Clients will pull down a directory from any node with an open
21418 DirPort, and check the signature/timestamp correctly.
21419 - Authoritative dirservers now fetch directories from other
21420 authdirservers, to stay better synced.
21421 - Running-routers list tells who's down also, along with noting
21422 if they're verified (listed by nickname) or unverified (listed
21424 - Allow dirservers to serve running-router list separately.
21425 This isn't used yet.
21426 - You can now fetch $DIRURL/running-routers to get just the
21427 running-routers line, not the whole descriptor list. (But
21428 clients don't use this yet.)
21429 - Clients choose nodes proportional to advertised bandwidth.
21430 - Clients avoid using nodes with low uptime as introduction points.
21431 - Handle servers with dynamic IP addresses: don't just replace
21432 options->Address with the resolved one at startup, and
21433 detect our address right before we make a routerinfo each time.
21434 - 'FascistFirewall' option to pick dirservers and ORs on specific
21435 ports; plus 'FirewallPorts' config option to tell FascistFirewall
21436 which ports are open. (Defaults to 80,443)
21437 - Try other dirservers immediately if the one you try is down. This
21438 should tolerate down dirservers better now.
21439 - ORs connect-on-demand to other ORs
21440 - If you get an extend cell to an OR you're not connected to,
21441 connect, handshake, and forward the create cell.
21442 - The authoritative dirservers stay connected to everybody,
21443 and everybody stays connected to 0.0.7 servers, but otherwise
21444 clients/servers expire unused connections after 5 minutes.
21445 - When servers get a sigint, they delay 30 seconds (refusing new
21446 connections) then exit. A second sigint causes immediate exit.
21447 - File and name management:
21448 - Look for .torrc if no CONFDIR "torrc" is found.
21449 - If no datadir is defined, then choose, make, and secure ~/.tor
21451 - If torrc not found, exitpolicy reject *:*.
21452 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
21453 - If no nickname is defined, derive default from hostname.
21454 - Rename secret key files, e.g. identity.key -> secret_id_key,
21455 to discourage people from mailing their identity key to tor-ops.
21456 - Refuse to build a circuit before the directory has arrived --
21457 it won't work anyway, since you won't know the right onion keys
21459 - Parse tor version numbers so we can do an is-newer-than check
21460 rather than an is-in-the-list check.
21461 - New socks command 'resolve', to let us shim gethostbyname()
21463 - A 'tor_resolve' script to access the socks resolve functionality.
21464 - A new socks-extensions.txt doc file to describe our
21465 interpretation and extensions to the socks protocols.
21466 - Add a ContactInfo option, which gets published in descriptor.
21467 - Write tor version at the top of each log file
21468 - New docs in the tarball:
21470 - Document that you should proxy your SSL traffic too.
21471 - Log a warning if the user uses an unsafe socks variant, so people
21472 are more likely to learn about privoxy or socat.
21473 - Log a warning if you're running an unverified server, to let you
21474 know you might want to get it verified.
21475 - Change the default exit policy to reject the default edonkey,
21476 kazaa, gnutella ports.
21477 - Add replace_file() to util.[ch] to handle win32's rename().
21478 - Publish OR uptime in descriptor (and thus in directory) too.
21479 - Remember used bandwidth (both in and out), and publish 15-minute
21480 snapshots for the past day into our descriptor.
21481 - Be more aggressive about trying to make circuits when the network
21482 has changed (e.g. when you unsuspend your laptop).
21483 - Check for time skew on http headers; report date in response to
21485 - If the entrynode config line has only one node, don't pick it as
21487 - Add strict{entry|exit}nodes config options. If set to 1, then
21488 we refuse to build circuits that don't include the specified entry
21490 - OutboundBindAddress config option, to bind to a specific
21491 IP address for outgoing connect()s.
21492 - End truncated log entries (e.g. directories) with "[truncated]".
21495 Changes in version 0.0.7.3 - 2004-08-12
21496 o Stop dnsworkers from triggering an assert failure when you
21497 ask them to resolve the host "".
21500 Changes in version 0.0.7.2 - 2004-07-07
21501 o A better fix for the 0.0.0.0 problem, that will hopefully
21502 eliminate the remaining related assertion failures.
21505 Changes in version 0.0.7.1 - 2004-07-04
21506 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
21507 since internally we use 0.0.0.0 to signify "not yet resolved".
21510 Changes in version 0.0.7 - 2004-06-07
21511 o Fixes for crashes and other obnoxious bugs:
21512 - Fix an epipe bug: sometimes when directory connections failed
21513 to connect, we would give them a chance to flush before closing
21515 - When we detached from a circuit because of resolvefailed, we
21516 would immediately try the same circuit twice more, and then
21517 give up on the resolve thinking we'd tried three different
21519 - Limit the number of intro circuits we'll attempt to build for a
21520 hidden service per 15-minute period.
21521 - Check recommended-software string *early*, before actually parsing
21522 the directory. Thus we can detect an obsolete version and exit,
21523 even if the new directory format doesn't parse.
21524 o Fixes for security bugs:
21525 - Remember which nodes are dirservers when you startup, and if a
21526 random OR enables his dirport, don't automatically assume he's
21527 a trusted dirserver.
21529 - Directory connections were asking the wrong poll socket to
21530 start writing, and not asking themselves to start writing.
21531 - When we detached from a circuit because we sent a begin but
21532 didn't get a connected, we would use it again the first time;
21533 but after that we would correctly switch to a different one.
21534 - Stop warning when the first onion decrypt attempt fails; they
21535 will sometimes legitimately fail now that we rotate keys.
21536 - Override unaligned-access-ok check when $host_cpu is ia64 or
21537 arm. Apparently they allow it but the kernel whines.
21538 - Dirservers try to reconnect periodically too, in case connections
21540 - Fix some memory leaks in directory servers.
21541 - Allow backslash in Win32 filenames.
21542 - Made Tor build complain-free on FreeBSD, hopefully without
21543 breaking other BSD builds. We'll see.
21544 - Check directory signatures based on name of signer, not on whom
21545 we got the directory from. This will let us cache directories more
21547 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
21550 - Doxygen markup on all functions and global variables.
21551 - Make directory functions update routerlist, not replace it. So
21552 now directory disagreements are not so critical a problem.
21553 - Remove the upper limit on number of descriptors in a dirserver's
21554 directory (not that we were anywhere close).
21555 - Allow multiple logfiles at different severity ranges.
21556 - Allow *BindAddress to specify ":port" rather than setting *Port
21557 separately. Allow multiple instances of each BindAddress config
21558 option, so you can bind to multiple interfaces if you want.
21559 - Allow multiple exit policy lines, which are processed in order.
21560 Now we don't need that huge line with all the commas in it.
21561 - Enable accept/reject policies on SOCKS connections, so you can bind
21562 to 0.0.0.0 but still control who can use your OP.
21563 - Updated the man page to reflect these features.
21566 Changes in version 0.0.6.2 - 2004-05-16
21567 o Our integrity-checking digest was checking only the most recent cell,
21568 not the previous cells like we'd thought.
21569 Thanks to Stefan Mark for finding the flaw!
21572 Changes in version 0.0.6.1 - 2004-05-06
21573 o Fix two bugs in our AES counter-mode implementation (this affected
21574 onion-level stream encryption, but not TLS-level). It turns
21575 out we were doing something much more akin to a 16-character
21576 polyalphabetic cipher. Oops.
21577 Thanks to Stefan Mark for finding the flaw!
21578 o Retire moria3 as a directory server, and add tor26 as a directory
21582 Changes in version 0.0.6 - 2004-05-02
21584 - Hidden services and rendezvous points are implemented. Go to
21585 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
21586 hidden services. (This only works via a socks4a proxy such as
21587 Privoxy, and currently it's quite slow.)
21588 - We now rotate link (tls context) keys and onion keys.
21589 - CREATE cells now include oaep padding, so you can tell
21590 if you decrypted them correctly.
21591 - Retry stream correctly when we fail to connect because of
21592 exit-policy-reject (should try another) or can't-resolve-address.
21593 - When we hup a dirserver and we've *removed* a server from the
21594 approved-routers list, now we remove that server from the
21595 in-memory directories too.
21596 - Add bandwidthburst to server descriptor.
21597 - Directories now say which dirserver signed them.
21598 - Use a tor_assert macro that logs failed assertions too.
21599 - Since we don't support truncateds much, don't bother sending them;
21600 just close the circ.
21601 - Fetch randomness from /dev/urandom better (not via fopen/fread)
21602 - Better debugging for tls errors
21603 - Set Content-Type on the directory and hidserv descriptor.
21604 - Remove IVs from cipher code, since AES-ctr has none.
21606 - Fix an assert trigger for exit nodes that's been plaguing us since
21607 the days of 0.0.2prexx (thanks weasel!)
21608 - Fix a bug where we were closing tls connections intermittently.
21609 It turns out openssl keeps its errors around -- so if an error
21610 happens, and you don't ask about it, and then another openssl
21611 operation happens and succeeds, and you ask if there was an error,
21612 it tells you about the first error.
21613 - Fix a bug that's been lurking since 27 may 03 (!)
21614 When passing back a destroy cell, we would use the wrong circ id.
21615 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
21616 - Some versions of openssl have an SSL_pending function that erroneously
21617 returns bytes when there is a non-application record pending.
21618 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
21619 o We were using an array of length zero in a few places.
21620 o Win32's gethostbyname can't resolve an IP to an IP.
21621 o Win32's close can't close a socket.
21622 o Handle windows socket errors correctly.
21624 - check for <sys/limits.h> so we build on FreeBSD again, and
21625 <machine/limits.h> for NetBSD.
21628 Changes in version 0.0.5 - 2004-03-30
21629 o Install torrc as torrc.sample -- we no longer clobber your
21631 o Fix mangled-state bug in directory fetching (was causing sigpipes).
21632 o Only build circuits after we've fetched the directory: clients were
21633 using only the directory servers before they'd fetched a directory.
21634 This also means longer startup time; so it goes.
21635 o Fix an assert trigger where an OP would fail to handshake, and we'd
21636 expect it to have a nickname.
21637 o Work around a tsocks bug: do a socks reject when AP connection dies
21638 early, else tsocks goes into an infinite loop.
21639 o Hold socks connection open until reply is flushed (if possible)
21640 o Make exit nodes resolve IPs to IPs immediately, rather than asking
21641 the dns farm to do it.
21642 o Fix c99 aliasing warnings in rephist.c
21643 o Don't include server descriptors that are older than 24 hours in the
21645 o Give socks 'reject' replies their whole 15s to attempt to flush,
21646 rather than seeing the 60s timeout and assuming the flush had failed.
21647 o Clean automake droppings from the cvs repository
21648 o Add in a 'notice' log level for things the operator should hear
21649 but that aren't warnings
21652 Changes in version 0.0.4 - 2004-03-26
21653 o When connecting to a dirserver or OR and the network is down,
21657 Changes in version 0.0.3 - 2004-03-26
21658 o Warn and fail if server chose a nickname with illegal characters
21659 o Port to Solaris and Sparc:
21660 - include missing header fcntl.h
21661 - have autoconf find -lsocket -lnsl automatically
21662 - deal with hardware word alignment
21663 - make uname() work (solaris has a different return convention)
21664 - switch from using signal() to sigaction()
21665 o Preliminary work on reputation system:
21666 - Keep statistics on success/fail of connect attempts; they're published
21667 by kill -USR1 currently.
21668 - Add a RunTesting option to try to learn link state by creating test
21669 circuits, even when SocksPort is off.
21670 - Remove unused open circuits when there are too many.
21673 Changes in version 0.0.2 - 2004-03-19
21674 - Include strlcpy and strlcat for safer string ops
21675 - define INADDR_NONE so we compile (but still not run) on solaris
21678 Changes in version 0.0.2pre27 - 2004-03-14
21680 - Allow internal tor networks (we were rejecting internal IPs,
21681 now we allow them if they're set explicitly).
21682 - And fix a few endian issues.
21685 Changes in version 0.0.2pre26 - 2004-03-14
21687 - If a stream times out after 15s without a connected cell, don't
21688 try that circuit again: try a new one.
21689 - Retry streams at most 4 times. Then give up.
21690 - When a dirserver gets a descriptor from an unknown router, it
21691 logs its fingerprint (so the dirserver operator can choose to
21692 accept it even without mail from the server operator).
21693 - Inform unapproved servers when we reject their descriptors.
21694 - Make tor build on Windows again. It works as a client, who knows
21696 - Clearer instructions in the torrc for how to set up a server.
21697 - Be more efficient about reading fd's when our global token bucket
21698 (used for rate limiting) becomes empty.
21700 - Stop asserting that computers always go forward in time. It's
21702 - When we sent a cell (e.g. destroy) and then marked an OR connection
21703 expired, we might close it before finishing a flush if the other
21704 side isn't reading right then.
21705 - Don't allow dirservers to start if they haven't defined
21706 RecommendedVersions
21707 - We were caching transient dns failures. Oops.
21708 - Prevent servers from publishing an internal IP as their address.
21709 - Address a strcat vulnerability in circuit.c
21712 Changes in version 0.0.2pre25 - 2004-03-04
21714 - Put the OR's IP in its router descriptor, not its fqdn. That way
21715 we'll stop being stalled by gethostbyname for nodes with flaky dns,
21718 - If the user typed in an address that didn't resolve, the server
21722 Changes in version 0.0.2pre24 - 2004-03-03
21724 - Fix an assertion failure in dns.c, where we were trying to dequeue
21725 a pending dns resolve even if it wasn't pending
21726 - Fix a spurious socks5 warning about still trying to write after the
21727 connection is finished.
21728 - Hold certain marked_for_close connections open until they're finished
21729 flushing, rather than losing bytes by closing them too early.
21730 - Correctly report the reason for ending a stream
21731 - Remove some duplicate calls to connection_mark_for_close
21732 - Put switch_id and start_daemon earlier in the boot sequence, so it
21733 will actually try to chdir() to options.DataDirectory
21734 - Make 'make test' exit(1) if a test fails; fix some unit tests
21735 - Make tor fail when you use a config option it doesn't know about,
21736 rather than warn and continue.
21737 - Make --version work
21738 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
21741 Changes in version 0.0.2pre23 - 2004-02-29
21743 - Print a statement when the first circ is finished, so the user
21744 knows it's working.
21745 - If a relay cell is unrecognized at the end of the circuit,
21746 send back a destroy. (So attacks to mutate cells are more
21748 - New config option 'excludenodes' to avoid certain nodes for circuits.
21749 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
21750 so you can collect coredumps there.
21752 - Fix a bug in tls flushing where sometimes data got wedged and
21753 didn't flush until more data got sent. Hopefully this bug was
21754 a big factor in the random delays we were seeing.
21755 - Make 'connected' cells include the resolved IP, so the client
21756 dns cache actually gets populated.
21757 - Disallow changing from ORPort=0 to ORPort>0 on hup.
21758 - When we time-out on a stream and detach from the circuit, send an
21759 end cell down it first.
21760 - Only warn about an unknown router (in exitnodes, entrynodes,
21761 excludenodes) after we've fetched a directory.
21764 Changes in version 0.0.2pre22 - 2004-02-26
21766 - Servers publish less revealing uname information in descriptors.
21767 - More memory tracking and assertions, to crash more usefully when
21769 - If the default torrc isn't there, just use some default defaults.
21770 Plus provide an internal dirservers file if they don't have one.
21771 - When the user tries to use Tor as an http proxy, give them an http
21772 501 failure explaining that we're a socks proxy.
21773 - Dump a new router.desc on hup, to help confused people who change
21774 their exit policies and then wonder why router.desc doesn't reflect
21776 - Clean up the generic tor.sh init script that we ship with.
21778 - If the exit stream is pending on the resolve, and a destroy arrives,
21779 then the stream wasn't getting removed from the pending list. I
21780 think this was the one causing recent server crashes.
21781 - Use a more robust poll on OSX 10.3, since their poll is flaky.
21782 - When it couldn't resolve any dirservers, it was useless from then on.
21783 Now it reloads the RouterFile (or default dirservers) if it has no
21785 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
21786 many users don't even *have* a /usr/local/sbin/.
21789 Changes in version 0.0.2pre21 - 2004-02-18
21791 - There's a ChangeLog file that actually reflects the changelog.
21792 - There's a 'torify' wrapper script, with an accompanying
21793 tor-tsocks.conf, that simplifies the process of using tsocks for
21794 tor. It even has a man page.
21795 - The tor binary gets installed to sbin rather than bin now.
21796 - Retry streams where the connected cell hasn't arrived in 15 seconds
21797 - Clean up exit policy handling -- get the default out of the torrc,
21798 so we can update it without forcing each server operator to fix
21800 - Allow imaps and pop3s in default exit policy
21802 - Prevent picking middleman nodes as the last node in the circuit
21805 Changes in version 0.0.2pre20 - 2004-01-30
21807 - We now have a deb package, and it's in debian unstable. Go to
21808 it, apt-getters. :)
21809 - I've split the TotalBandwidth option into BandwidthRate (how many
21810 bytes per second you want to allow, long-term) and
21811 BandwidthBurst (how many bytes you will allow at once before the cap
21812 kicks in). This better token bucket approach lets you, say, set
21813 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
21814 performance while not exceeding your monthly bandwidth quota.
21815 - Push out a tls record's worth of data once you've got it, rather
21816 than waiting until you've read everything waiting to be read. This
21817 may improve performance by pipelining better. We'll see.
21818 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
21819 from failed circuits (if they haven't been connected yet) and attach
21821 - Expire old streams that haven't managed to connect. Some day we'll
21822 have them reattach to new circuits instead.
21825 - Fix several memory leaks that were causing servers to become bloated
21827 - Fix a few very rare assert triggers. A few more remain.
21828 - Setuid to User _before_ complaining about running as root.
21831 Changes in version 0.0.2pre19 - 2004-01-07
21833 - Fix deadlock condition in dns farm. We were telling a child to die by
21834 closing the parent's file descriptor to him. But newer children were
21835 inheriting the open file descriptor from the parent, and since they
21836 weren't closing it, the socket never closed, so the child never read
21837 eof, so he never knew to exit. Similarly, dns workers were holding
21838 open other sockets, leading to all sorts of chaos.
21839 - New cleaner daemon() code for forking and backgrounding.
21840 - If you log to a file, it now prints an entry at the top of the
21841 logfile so you know it's working.
21842 - The onionskin challenge length was 30 bytes longer than necessary.
21843 - Started to patch up the spec so it's not quite so out of date.
21846 Changes in version 0.0.2pre18 - 2004-01-02
21848 - Fix endian issues with the 'integrity' field in the relay header.
21849 - Fix a potential bug where connections in state
21850 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
21853 Changes in version 0.0.2pre17 - 2003-12-30
21855 - Made --debuglogfile (or any second log file, actually) work.
21856 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
21857 adversary could force us into an infinite loop.
21860 - Each onionskin handshake now includes a hash of the computed key,
21861 to prove the server's identity and help perfect forward secrecy.
21862 - Changed cell size from 256 to 512 bytes (working toward compatibility
21864 - Changed cell length to 2 bytes, and moved it to the relay header.
21865 - Implemented end-to-end integrity checking for the payloads of
21867 - Separated streamid from 'recognized' (otherwise circuits will get
21868 messed up when we try to have streams exit from the middle). We
21869 use the integrity-checking to confirm that a cell is addressed to
21871 - Randomize the initial circid and streamid values, so an adversary who
21872 breaks into a node can't learn how many circuits or streams have
21876 Changes in version 0.0.2pre16 - 2003-12-14
21878 - Fixed a bug that made HUP trigger an assert
21879 - Fixed a bug where a circuit that immediately failed wasn't being
21880 counted as a failed circuit in counting retries.
21883 - Now we close the circuit when we get a truncated cell: otherwise we're
21884 open to an anonymity attack where a bad node in the path truncates
21885 the circuit and then we open streams at him.
21886 - Add port ranges to exit policies
21887 - Add a conservative default exit policy
21888 - Warn if you're running tor as root
21889 - on HUP, retry OR connections and close/rebind listeners
21890 - options.EntryNodes: try these nodes first when picking the first node
21891 - options.ExitNodes: if your best choices happen to include any of
21892 your preferred exit nodes, you choose among just those preferred
21894 - options.ExcludedNodes: nodes that are never picked in path building
21897 Changes in version 0.0.2pre15 - 2003-12-03
21898 o Robustness and bugfixes:
21899 - Sometimes clients would cache incorrect DNS resolves, which would
21900 really screw things up.
21901 - An OP that goes offline would slowly leak all its sockets and stop
21903 - A wide variety of bugfixes in exit node selection, exit policy
21904 handling, and processing pending streams when a new circuit is
21906 - Pick nodes for a path only from those the directory says are up
21907 - Choose randomly from all running dirservers, not always the first one
21908 - Increase allowed http header size for directory fetch.
21909 - Stop writing to stderr (if we're daemonized it will be closed).
21910 - Enable -g always, so cores will be more useful to me.
21911 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
21914 - Wrote a man page. It lists commonly used options.
21917 - Change default loglevel to warn.
21918 - Make PidFile default to null rather than littering in your CWD.
21919 - OnionRouter config option is now obsolete. Instead it just checks
21921 - Moved to a single unified torrc file for both clients and servers.
21924 Changes in version 0.0.2pre14 - 2003-11-29
21925 o Robustness and bugfixes:
21926 - Force the admin to make the DataDirectory himself
21927 - to get ownership/permissions right
21928 - so clients no longer make a DataDirectory and then never use it
21929 - fix bug where a client who was offline for 45 minutes would never
21930 pull down a directory again
21931 - fix (or at least hide really well) the dns assert bug that was
21932 causing server crashes
21933 - warnings and improved robustness wrt clockskew for certs
21934 - use the native daemon(3) to daemonize, when available
21935 - exit if bind() fails
21936 - exit if neither socksport nor orport is defined
21937 - include our own tor_timegm (Win32 doesn't have its own)
21938 - bugfix for win32 with lots of connections
21939 - fix minor bias in PRNG
21940 - make dirserver more robust to corrupt cached directory
21943 - Wrote the design document (woo)
21945 o Circuit building and exit policies:
21946 - Circuits no longer try to use nodes that the directory has told them
21948 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
21949 bitcounts (18.0.0.0/8).
21950 - Make AP connections standby for a circuit if no suitable circuit
21951 exists, rather than failing
21952 - Circuits choose exit node based on addr/port, exit policies, and
21953 which AP connections are standing by
21954 - Bump min pathlen from 2 to 3
21955 - Relay end cells have a payload to describe why the stream ended.
21956 - If the stream failed because of exit policy, try again with a new
21958 - Clients have a dns cache to remember resolved addresses.
21959 - Notice more quickly when we have no working circuits
21962 - APPort is now called SocksPort
21963 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
21965 - RecommendedVersions is now a config variable rather than
21966 hardcoded (for dirservers)
21967 - Reloads config on HUP
21968 - Usage info on -h or --help
21969 - If you set User and Group config vars, it'll setu/gid to them.
21971 Changes in version 0.0.2pre13 - 2003-10-19
21972 o General stability:
21973 - SSL_write no longer fails when it returns WANTWRITE and the number
21974 of bytes in the buf has changed by the next SSL_write call.
21975 - Fix segfault fetching directory when network is down
21976 - Fix a variety of minor memory leaks
21977 - Dirservers reload the fingerprints file on HUP, so I don't have
21978 to take down the network when I approve a new router
21979 - Default server config file has explicit Address line to specify fqdn
21982 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
21983 - Make listener connections not ever alloc bufs
21985 o Autoconf improvements:
21986 - don't clobber an external CFLAGS in ./configure
21987 - Make install now works
21988 - create var/lib/tor on make install
21989 - autocreate a tor.sh initscript to help distribs
21990 - autocreate the torrc and sample-server-torrc with correct paths
21992 o Log files and Daemonizing now work:
21993 - If --DebugLogFile is specified, log to it at -l debug
21994 - If --LogFile is specified, use it instead of commandline
21995 - If --RunAsDaemon is set, tor forks and backgrounds on startup